Quick answer: To connect a cabinet or BESS dehumidifier to a battery management system (BMS), energy management system (EMS) or SCADA, start with a signal list: which environmental readings (temperature, RH, dew point), equipment states (running, defrost, drain status) and alarms the system must receive, and whether it only reads data or can also start, stop or change setpoints. Most industrial units use dry contacts for simple run/fault signals and RS485 with Modbus RTU for data. Get the supplier's register map, agree the communication settings, and test every signal and failure case during commissioning.
Quick answer
- Ask for: register map, baud rate/parity/address, data types and scaling.
- Decide: read-only monitoring, or remote control too.
- Test: every signal, alarm and communication loss before handover.
Signals to request
| Category | Typical signals |
|---|---|
| Environment | Cabinet temperature, RH, calculated dew point |
| Equipment state | Running, standby, defrost (compressor units), fan state |
| Alarms | Unit fault, high humidity, sensor fault, drain blocked or full, over-temperature |
| Settings (if writable) | RH or dew-point setpoint, enable/disable |
| Counters | Running hours, compressor starts |
RS485 and Modbus basics
- RS485 is the physical layer: a two-wire (plus reference) bus that can link many devices over long distances.
- Modbus RTU is a common protocol over RS485; each device has an address, and data are read from or written to numbered registers. The Modbus Organization publishes the protocol specification (Modbus.org; Modbus protocol specification).
- Agree baud rate, parity, stop bits, address, and for each register its function code, data type, scaling and units (for example RH in 0.1 % steps).
- Use twisted-pair cable, correct termination at the ends of the bus, and avoid stubs.
Read-only or remote control?
| Mode | Pros | Cons |
|---|---|---|
| Read-only monitoring | Simple; the unit controls itself locally; safe on communication loss | Setpoints changed only on site |
| Remote control (write setpoints, enable/disable) | Central coordination with HVAC and cycle state | Must define what happens on communication loss; cyber and change control |
Define the fallback: on loss of communication, the dehumidifier should continue on its local setpoint.
Coordination with other systems
- HVAC and liquid cooling control temperature; the dehumidifier controls moisture. Share dew point so the EMS can see condensation margin.
- Fire and gas detection systems override normal operation according to the safety design.
- Avoid two controllers changing the same setpoint.
Data worth trending
- Dew point vs coldest surface temperature (if measured).
- RH and temperature at the dehumidifier and elsewhere in the enclosure.
- Running hours per day: rising run time can signal leakage or a fault.
- Alarm history and drain events.
Commissioning the interface
- Confirm wiring, termination, address and settings.
- Read every register and compare with local display values.
- Force each alarm (sensor unplugged, drain switch) and confirm the BMS/EMS receives it.
- Test write commands if remote control is used.
- Disconnect communication and confirm the unit's fallback and the BMS alarm.
- Record the final register map and settings.
Our electrical cabinet dehumidifiers and energy storage dehumidifiers: ask us for the signal and interface options of each model. See also industrial dehumidifier BMS and alarms.
FAQ
Frequently asked questions
Can a dehumidifier connect to a BMS?
Yes, typically by dry contacts for run/fault and RS485 Modbus RTU for data, depending on the model.
What is a Modbus register map?
A list of the device's data points, their addresses, data types, scaling and whether they can be read or written.
What should happen if communication fails?
The dehumidifier should keep running on its local setpoint, and the BMS should raise a communication alarm.
Sources
- Modbus Organization, Introduction to Modbus; Modbus application protocol specification.
