Last updated: January 2025 | Technical Level: Intermediate to Advanced
—Table of Contents
- Introduction: Why Siemens LOGO! for Building Automation
- Project 1: HVAC Zone Control System Failure
- Project 2: Lighting Control Network Interference
- Project 3: Temperature Regulation Oscillation
- Common Problems & Solutions Quick Reference
- Maintenance Best Practices
- Frequently Asked Questions
- Conclusion
Introduction: Why Siemens LOGO! for Building Automation
The Siemens LOGO! programmable logic controller has become a cornerstone device in modern building automation projects. Its compact design, flexible programming capabilities, and cost-effectiveness make it ideal for HVAC control, lighting control, and energy management applications. However, as with any automation system, proper troubleshooting and maintenance are critical for optimal performance.
This article presents three real-world project case studies that demonstrate common challenges encountered in LOGO! building automation installations. Each project follows our problem-solution framework: Problem → Analysis → Solution → Verification → Tips. By studying these examples, you’ll gain practical knowledge applicable to your own installations.
Project 1: HVAC Zone Control System Failure
Problem
A commercial office building with four independent HVAC zones experienced simultaneous system failures. Each zone featured a LOGO! controller managing fan coils, dampers, and temperature sensors. Building occupants reported complete HVAC shutdown during peak summer hours, causing significant discomfort and productivity loss.
Symptoms observed:
- All four LOGO! controllers displayed fault indicators
- No communication between zone controllers and central BMS
- Temperature sensors reporting erratic readings
- System failed to respond to any manual or automated commands
Analysis
Our diagnostic approach revealed a multi-layered issue:
- Power supply degradation: The 24V DC power supply unit had developed voltage fluctuation under load conditions. When all four zone controllers simultaneously demanded full power for damper actuators, voltage dropped below the minimum threshold (below 20.4V), causing controllers to reset.
- Missing surge protection: Voltage spikes from the building’s electrical system had damaged the analog input modules on three of the four controllers.
- Network topology issue: The Ethernet network used a daisy-chain topology without proper segmentation, causing broadcast storms when multiple controllers attempted simultaneous communication.
Solution
We implemented a comprehensive fix following these steps:
- Upgraded power supply: Replaced the single 5A power supply with dual redundant 10A units configured for load sharing. This ensured adequate headroom for peak demand periods.
- Added surge protection: Installed DIN-rail mounted surge suppressors on both the power and communication lines to the controllers.
- Reconfigured network: Implemented a star topology with an industrial Ethernet switch, separating the LOGO! network from the general building network using VLANs.
- Replaced damaged modules: Substituted the damaged analog input modules and recalibrated all temperature sensors using the LOGO! software’s built-in calibration function.
LOGO! Program Modification:
// LOGO! Ladder Logic - HVAC Zone Control (Simplified) // Network 1: Temperature Reading & Validation // Block N1: AI1 (Temperature Sensor) → Connected to analog amplifier // Block N2: Analog Threshold → Triggers alarm if temp outside valid range (0-50°C) // Network 2: Power Supply Monitoring // Block N3: Analog threshold → Monitors voltage via analog input // If voltage < 20.4V → Trigger system shutdown & alarm // Network 3: Zone Control Logic // Block N4: Analog comparator → Compare setpoint vs actual temp // Block N5: PI controller → Output to damper actuator (0-10V) // Block N6: Timer → Fan delay after damper command
Verification
Following implementation, we conducted a 72-hour continuous monitoring test:
- Voltage stability maintained at 23.8-24.2V under all load conditions
- Temperature readings remained accurate within ±0.3°C
- Network communication latency reduced from 450ms to under 50ms
- No system failures during simulated peak demand scenarios
Tips from the Field
- Size power supplies at 150% of calculated maximum load
- Implement network segmentation for critical building systems
- Use shielded cables for analog sensor wiring
- Regularly backup LOGO! programs to external storage
Project 2: Lighting Control Network Interference
Problem
A retail shopping center implemented a LOG0!-based lighting control system managing 150+ luminaires across multiple zones. After initial successful deployment, the system began experiencing random zone-wide lighting failures, particularly during evening hours when occupancy sensors triggered.
Symptoms observed:
- Random zones would switch to full brightness or complete darkness
- Occupancy sensors appeared unresponsive
- Manual override switches caused unpredictable behavior
- System logs showed communication timeouts
Analysis
Investigation revealed a combination of electromagnetic interference (EMI) and software logic issues:
- EMI from dimmer modules: The phase-cut dimmer modules installed for theatrical lighting created significant electrical noise on the shared power circuit, corrupting the LOGO! communication signals.
- Ground loop issues: Inconsistent grounding between the LOGO! controller and the occupancy sensor network introduced common-mode noise.
- Program logic race condition: The ladder logic contained competing timer functions for occupancy and manual override, causing unpredictable execution order.
Solution
We addressed both hardware and software issues:
- Isolated power circuits: Installed dedicated 20A circuits for the dimmer modules, completely separate from the LOGO! controller power supply.
- Added EMI filtering: Installed EMI suppression filters on all power inputs to the LOGO! controllers and implemented ferrite beads on communication cables.
- Improved grounding: Created a single-point ground system for all building automation equipment, eliminating ground loops.
- Rewrote control logic: Restructured the LOGO! program to use a deterministic state machine approach:
Improved LOGO! Program Structure:
// LOGO! FBD - Lighting Control State Machine // Constants CONSTANT: ManualMode = 0 CONSTANT: Occupied = 1 CONSTANT: Unoccupied = 2 CONSTANT: Transition = 3 // State Memory M1: Memory Bit → Stores current state // Priority Logic (Manual Override has highest priority) I1: Manual Switch → Set/Reset Flip-Flop → M1 I2: Occupancy Sensor → AND with NOT(Manual Mode) → State transition // Timer Management T1: On-Delay (5 min) → Occupancy → Full light level T2: Off-Delay (15 min) → After last occupancy → Fade to 20% // Output Control Q1: Relay Output → Lighting contactor Q2: 0-10V Output → Dimming signal
Verification
The corrected system underwent rigorous testing:
- 30-day continuous operation with zero unexpected failures
- Proper response to all occupancy scenarios (entry, exit, linger)
- Manual override functioned correctly without affecting automated logic
- Dimmer operation remained stable during simultaneous full-load conditions
Tips from the Field
- Always separate noisy loads (dimmers, motors) from control circuit power
- Use shielded twisted-pair cables for all analog signals
- Implement state machines rather than combinational logic for complex control
- Document all manual override conditions in building management software
Project 3: Temperature Regulation Oscillation
Problem
A healthcare facility's patient room temperature control system using LOGO! for HVAC management exhibited severe temperature oscillation. Room temperatures fluctuated between 18°C and 26°C despite the setpoint being 22°C, causing patient complaints and potential infection control concerns.
Symptoms observed:
- Heating and cooling stages activated simultaneously at times
- Temperature cycling period of approximately 20 minutes
- Actuator wear indicators showing excessive cycling
- No apparent response to PI controller settings
Analysis
Root cause analysis identified three contributing factors:
- Oversized actuator: The heating/cooling coil actuators were significantly oversized for the room's thermal mass, causing rapid over-correction when activated.
- Incorrect PI parameters: The default PI controller parameters in the LOGO! were not optimized for the slow response time of the hydronic heating/cooling system.
- Deadband too narrow: The temperature deadband was set to ±0.5°C, which was too tight for the system's natural variations and actuator response time.
Solution
We implemented a systematic approach:
- PI controller tuning: Adjusted the LOGO! PI controller parameters:
- Increased proportional gain (Kp) from 1.0 to 2.5
- Increased integral time (Tn) from 60 seconds to 300 seconds
- This created a slower, more gradual response appropriate for hydronic systems
- Expanded deadband: Widened the temperature deadband to ±2.0°C to allow natural temperature variations without triggering actuators
- Added output rate limiting: Implemented software-based rate limiting on the analog output to prevent actuator "hunting"
- Replaced actuators: Installed properly sized actuators with built-in positioning feedback
Optimized LOGO! PI Configuration:
| Parameter | Original Value | Optimized Value | Rationale |
|---|---|---|---|
| Proportional Gain (Kp) | 1.0 | 2.5 | Increases system responsiveness |
| Integral Time (Tn) | 60 sec | 300 sec | Reduces overshoot for slow systems |
| Deadband | ±0.5°C | ±2.0°C | Prevents unnecessary cycling |
| Output Rate Limit | None | 10%/min | Prevents actuator hunting |
Verification
Post-implementation monitoring demonstrated dramatic improvement:
- Temperature stability maintained within ±1.0°C of setpoint
- Complete temperature cycle extended to 4+ hours (normal for occupied spaces)
- Actuator cycling reduced by 85%
- Patient comfort scores improved significantly
Tips from the Field
- Always tune PI controllers to match the physical system response time
- Allow adequate deadband for systems with slow response times
- Implement rate limiting for valve and damper actuators
- Consider adding outdoor temperature compensation for large buildings
Common Problems & Solutions Quick Reference
| Problem Category | Common Symptoms | Recommended Solution |
|---|---|---|
| Power Issues | Random resets, erratic behavior | Upgrade supply, add surge protection |
| Communication | Timeouts, lost data, slow response | Check cabling, verify IP settings, add switches |
| Analog Signals | Erratic readings, sensor failures | Check shielding, verify 4-20mA loop, replace sensors |
| Logic Errors | Unexpected outputs, timing issues | Review program, add state machine logic |
| Environmental | Condensation, temperature extremes | Use IP65 enclosures, add climate control |
Maintenance Best Practices
Preventive maintenance is essential for long-term reliability of Siemens LOGO! building automation systems. The following schedule represents industry best practices:
Weekly Maintenance Tasks
- Review system event logs for warnings and errors
- Verify network communication status on all controllers
- Check physical condition of controllers and wiring
Monthly Maintenance Tasks
- Calibrate analog sensors (temperature, pressure, humidity)
- Verify battery backup functionality (if equipped)
- Test manual override functions on all controlled systems
- Review energy consumption data for anomalies
Quarterly Maintenance Tasks
- Backup all LOGO! programs and store in multiple locations
- Inspect and tighten all electrical connections
- Clean controller enclosures and ventilation openings
- Test all alarm notification systems
Annual Maintenance Tasks
- Complete firmware updates (test in isolated environment first)
- Perform comprehensive system stress testing
- Review and update control sequences as needed
- Document any system modifications
Frequently Asked Questions
Can Siemens LOGO! integrate with BACnet building management systems?
Yes, LOGO! 8.3 devices with Ethernet connectivity can communicate via Modbus TCP/IP, which can be gateway-converted to BACnet/IP using third-party protocol converters. For direct BACnet support, consider the Siemens PAC series, but LOGO! remains cost-effective for smaller applications.
What's the maximum number of LOGO! controllers in a network?
Theoretically, you can network up to 16 LOGO! devices using Ethernet. However, practical implementations typically limit each network segment to 8-10 controllers for optimal performance. For larger installations, use industrial Ethernet switches with VLAN capability to create multiple segments.
How do I troubleshoot communication failures between LOGO! controllers?
Start with physical layer diagnostics: verify cable integrity, check LED status indicators, and confirm IP addresses are on the same subnet. Then verify the LOGO! program includes proper network connection blocks (Net Link) for each controller. Use ping tests and LOGO! Soft Comfort's online diagnostics for detailed troubleshooting.
Can I program LOGO! using structured text or only ladder/FBD?
LOGO! Soft Comfort supports both Ladder Logic (LAD) and Function Block Diagram (FBD) programming. Structured Text is not natively supported in LOGO! For more complex applications requiring structured text, consider Siemens S7-1200 or S7-1500 PLCs. However, FBD in LOGO! can accomplish most building automation tasks effectively.
What replacement batteries does LOGO! use, and how often should they be replaced?
LOGO! uses a CR2032 lithium battery for memory backup. Under normal conditions, battery life is approximately 2-3 years. However, we recommend annual replacement in critical building automation applications to ensure uninterrupted program retention during power outages. Always backup programs before battery replacement.
Conclusion
Siemens LOGO! controllers provide an excellent foundation for building automation projects when properly specified, installed, and maintained. The three project case studies presented in this article illustrate common challenges: power supply issues, electromagnetic interference, and control loop tuning.
By following the troubleshooting methodology—Problem → Analysis → Solution → Verification—you can systematically resolve issues and optimize system performance. Remember these key principles:
- Always size power supplies adequately and protect against surges
- Separate control circuits from noisy loads
- Tune PI controllers to match system response characteristics
- Implement preventive maintenance schedules
- Document all modifications and maintain program backups
Whether you're implementing HVAC control, lighting control, or integrated building management, Siemens LOGO! offers the flexibility and reliability required for modern smart buildings.
---Ready to Optimize Your Building Automation Systems?
Get expert guidance on your Siemens LOGO! projects. Our team of certified automation specialists can help with system design, troubleshooting, and maintenance.
About the Author
James Morrison, PE, CxA is a licensed Professional Engineer and Certified Commissioning Authority with over 15 years of experience in building automation and industrial automation systems. He has designed and commissioned HVAC control systems, lighting control systems, and integrated building management systems for commercial, healthcare, and industrial facilities throughout North America. James specializes in Siemens, Johnson Controls, and Schneider Electric platforms.
© 2025 Industrial Automation Solutions. All rights reserved. | Privacy Policy | Terms of Service

