.png)
Automating Ventilation with PLCs Sensors and VSDs
Ventilation loads rarely stay still. A workshop may be quiet at 7 am, busy by mid-morning, then running only a few processes after lunch. A pump room may heat up slowly through the day. A battery charging area may need more airflow during certain operating periods. If fans run at full speed all day, the system wastes energy, creates noise and gives operators little useful feedback about what is happening.
A well-designed control system can do better. By connecting environmental sensors to a PLC, then controlling fan speed through variable speed drives, ventilation can respond to real conditions rather than a fixed schedule. The key is to design the system with clear thresholds, sensible operating limits, reliable feedback and a safe path for manual control.
This article covers how general ventilation control can work, where it helps, and where it must not be confused with dedicated safety-rated gas detection or protective systems.
Why fixed-speed ventilation often falls short
Traditional ventilation systems often use one of three control methods:
Fans run whenever the plant is occupied
Fans run on a timer
Fans run at a fixed speed when a process starts
These methods are simple, but they rarely match the real ventilation demand. A fan may run hard when the space is already within acceptable limits. At other times, it may not respond quickly enough to rising temperature, humidity, dust or fumes.
Variable speed control changes the picture. A VSD allows the fan to ramp up and down instead of switching only between off and full speed. The PLC can read sensor values, compare them with setpoints, then send an analogue speed reference or network command to the drive.
That gives the control system several useful options:
Run fans at a low background speed during normal operation
Increase airflow when temperature, humidity or air quality changes
Reduce speed once conditions return to the normal range
Show operators why the system is running
Alarm when readings move outside expected limits
Record trends for maintenance and review
The goal is not to make ventilation complicated. The goal is to make fan operation match the actual need of the area.
How a PLC-based ventilation system is usually arranged
A typical system for Automating Ventilation with PLCs Sensors and VSDs includes four main layers.
The first layer is measurement. Environmental sensors monitor the condition of the space or duct. These signals may be analogue, digital or sent over a fieldbus network.
The second layer is control. The PLC reads the inputs, applies filtering or validation, compares the readings with thresholds, then decides how the fans should run.
The third layer is actuation. The PLC commands a VSD, damper actuator, contactor or other field device. For fan speed control, the VSD is usually the main output device.
The fourth layer is operator feedback. A local HMI, SCADA system or indicator panel shows status, alarms, measured values and manual control options.
A simple arrangement may have one sensor, one PLC and one fan drive. A larger installation may have several zones, multiple fans, duty and standby arrangements, and separate extract and supply systems.
Good design keeps the logic understandable. Operators and maintenance technicians should be able to see what the system is doing and why.
Choosing the right environmental sensors
Sensor selection drives the quality of the whole system. If the measured value is unreliable, the PLC can only make poor decisions faster.
The right sensor depends on what the ventilation system is trying to manage.
Measurement | Common use | Design considerations |
Temperature | Heat removal in plant rooms, workshops and enclosures | Place sensors away from direct heat sources unless measuring that source is the goal |
Humidity | Moisture control in washdown areas, storage spaces or process rooms | Allow for slow response in large spaces and protect sensors from water spray |
CO₂ | Occupancy-based ventilation in occupied areas | Useful for general air quality, not a substitute for hazardous gas detection |
VOCs | General indication of changing air quality | Readings can be broad and affected by many compounds |
Differential pressure | Filter monitoring or room pressure control | Requires correct tubing, tapping points and maintenance access |
Particulate matter | Dust or airborne particle indication | Sensor location and cleaning access matter |
Airflow or duct pressure | Proving ventilation performance | Helps confirm the fan is producing the expected result |
For general ventilation, sensors should be chosen for the operating environment. That includes temperature range, humidity exposure, dust, vibration and cleaning methods. Industrial spaces can be hard on delicate instruments.
Sensor placement also matters. A wall-mounted sensor beside an open roller door may not represent the room. A duct sensor too close to a bend may see unstable airflow. A temperature sensor above a motor may read higher than the broader space.
A useful design question is simple: what decision will this measurement support? If the answer is unclear, the sensor may add noise rather than value.
Setting thresholds that operators can understand
A ventilation control system needs thresholds that make sense in both engineering and operational terms. These values should not be hidden in code with unclear names. They should be documented and, where suitable, visible on the HMI.
A common approach uses several bands rather than one trigger point.
For example, a temperature-based system might use:
Normal band Fan runs at minimum ventilation speed
Elevated band Fan speed increases gradually
High band Fan runs at maximum allowed speed and shows a warning
Fault band Alarm activates if values exceed expected operating limits or the sensor signal is invalid
The same idea can apply to humidity, pressure or general air quality sensors. The PLC can scale the fan speed between a low and high value, or it can step between preset speeds.
Hysteresis is usually needed. Without it, the fan may hunt up and down when the measured value sits close to a threshold. For example, the fan may turn on at 30 °C and stay on until the temperature falls below 28 °C. That small gap prevents rapid cycling.
Time delays also help. A short delay can stop the fan from responding to a single spike caused by a door opening, a passing vehicle or a brief process event. The delay should be long enough to reject nuisance changes, but not so long that the system misses a real trend.
The best thresholds are easy to explain:
If the room warms up, the fan speeds up. If the room returns to normal, the fan slows down. If the reading is outside the expected range, the operator sees an alarm.
That level of clarity helps during commissioning, troubleshooting and daily use.
Using VSDs to control fan speed properly
A VSD gives fine control over the fan motor, but it needs sensible limits. Running a fan too slowly may fail to move enough air, affect motor cooling or create unstable airflow. Running too fast may exceed duct design, increase noise or overload equipment.
A good PLC and VSD design will define:
Minimum speed for effective ventilation
Maximum speed for the fan, duct and process
Acceleration and deceleration ramps
Drive fault handling
Motor protection settings
Run feedback and proof of operation
Local isolation and safe maintenance procedures
The PLC should not assume that a fan is running just because it has sent a start command. Feedback matters. Common feedback signals include VSD running status, fault status, motor current, airflow switch status or duct pressure.
For critical general ventilation functions, airflow proving can be useful. If the PLC starts a fan but sees no pressure change or airflow proof, it can raise an alarm. That helps detect belt failures, blocked filters, closed dampers or drive faults.
VSD control can also reduce mechanical stress. Smooth starts and stops are easier on belts, bearings and ductwork than direct-on-line starting. Lower fan speed can also reduce noise during periods of low demand.
Energy savings can be significant in suitable applications because fan power changes strongly with speed. The actual saving depends on the fan, duct system, operating hours and process requirements, so it should be assessed for each site rather than assumed.
Designing useful operator feedback
Automation should not make the system mysterious. Operators need to know what the ventilation system is doing, what condition caused it, and whether intervention is needed.
A clear HMI page or local display might show:
Current sensor values
Fan speed command as a percentage
Fan run status
VSD fault status
Active control mode
Alarm messages
Manual override status
Time and date of recent alarms
Control mode labels should be plain. `Auto`, `Manual`, `Fault`, `Sensor Failed` and `High Temperature Ventilation` are easier to understand than vague internal tags.
Alarm messages should point to the likely issue. “Fan 2 failed to prove airflow” is more useful than “Vent fault”. “Temperature sensor signal out of range” is more useful than “Analogue input fault”.
Trends can also help. A temperature graph may show that heat builds up after a certain machine starts. A duct pressure trend may show filters slowly blocking. A fan speed trend may reveal that the system now runs near maximum for much of the day, which may mean the original ventilation design no longer matches the process.
Manual override needs clear rules
Manual control is often needed for cleaning, maintenance, commissioning and unusual operating conditions. It should be designed carefully, not added as an afterthought.
A basic system may allow an authorised operator to select:
Automatic control
Manual fan start
Manual fan stop
Manual speed setpoint
The PLC should make the current mode obvious. If a fan is in manual, the HMI should show it clearly. If manual mode overrides automatic demand, the system should record or alarm that state where appropriate.
Manual override should still respect hard operating limits. For example, a manual speed command should not exceed the maximum safe fan speed. A stop command may be restricted if the system has a required post-run period, thermal purge or other process need.
Access control can help. Not every operator needs permission to change thresholds or force outputs. A practical design may allow general operators to view status and acknowledge alarms, while supervisors or maintenance staff can adjust setpoints within approved ranges.
The most important principle is that manual control must not hide a dangerous condition. If an abnormal environmental reading is present, the system should still display it even when the fan is in manual.
Separating general ventilation from safety-rated protection
This distinction is critical. A PLC-controlled ventilation system using environmental sensors can be suitable for comfort, heat removal, humidity control, process support or general air quality management. It is not automatically suitable for hazardous gas protection, explosive atmosphere control or life safety functions.
Applications involving toxic gases, flammable gases, oxygen depletion, confined spaces or legally defined hazardous areas may require dedicated equipment and design methods. These may include:
Certified gas detectors
Safety-rated controllers
Independent alarm systems
Forced extraction with verified performance
Emergency shutdown functions
Hazardous area rated equipment
Compliance with relevant Australian Standards and site requirements
Formal risk assessment and validation
A general CO₂ or VOC sensor connected to a standard PLC does not become a safety system simply because it can start a fan. Safety functions require careful design, suitable hardware, defined performance levels, testing and maintenance.
This does not mean PLC-based ventilation control has no place near higher-risk processes. It may still support normal ventilation and provide useful operating data. The safety system, where required, should be designed as a separate protective layer or as part of a properly engineered safety architecture.
When in doubt, treat the ventilation control system as a general control system and seek specialist advice for hazardous gas or life safety requirements.
Commissioning should prove the whole chain
Commissioning is more than checking that the fan starts. The whole measurement and control chain should be tested.
A practical commissioning process checks:
Sensor scaling in the PLC
Displayed engineering units
Threshold values and hysteresis
VSD speed reference and actual speed
Fan rotation and airflow direction
Run and fault feedback
Alarm messages
Manual mode behaviour
Power loss recovery
Sensor failure response
Simulated inputs are useful. A technician can apply known analogue values to confirm that the PLC reads and displays the correct temperature, humidity or pressure. For live process sensors, controlled testing may be needed.
The team should also test failure modes. What happens if a sensor cable breaks? What happens if the VSD trips? What happens after power is restored? The answers should match the design intent, not surprise the operator later.
Clear documentation helps the system remain maintainable. At a minimum, the site should have current drawings, PLC descriptions, setpoint lists, alarm lists and VSD parameter records.
Maintenance keeps the control system trustworthy
Ventilation automation can drift over time if sensors are ignored. Dust builds up. Filters block. Dampers stick. Sensors age. Process layouts change.
A maintenance plan should cover both mechanical and control equipment. That may include cleaning sensor housings, checking calibration, inspecting ductwork, confirming damper movement, reviewing VSD faults and testing alarms.
Trends can guide maintenance. If the fan speed has increased over months for the same temperature conditions, the system may be fighting blocked filters or reduced airflow. If humidity readings stay flat through obvious process changes, the sensor may have failed or become contaminated.
Setpoints should also be reviewed when the plant changes. New equipment, extended operating hours or altered process materials can change the ventilation load. A system that worked well at commissioning may need adjustment later.
The best systems make maintenance easier by showing clear faults and preserving useful history. A hidden problem becomes a visible one before it turns into downtime.
A good ventilation control system is predictable
The strongest PLC-based ventilation systems are not the most complex. They are the ones that measure the right conditions, act within known limits and explain their behaviour clearly.
A sound design uses suitable sensors, documented thresholds, VSD speed limits, reliable feedback and well-managed manual override. It also draws a firm line between general ventilation control and safety-rated gas or life safety protection.
When ventilation demand changes through the day, automatic control can reduce waste, improve comfort and give operators better information. The real value comes from making the system predictable, testable and easy to maintain.
