Maintenance and updates
Keeping the unit healthy: routine care, the measurement log, backups and a factory reset.
This page covers keeping the unit healthy: routine care, the measurement log, backups and a factory reset.
Firmware updates and the initial provisioning of a board are carried out by DSH Belgium.
Routine care
| Interval | Task |
|---|---|
| Every day | Read the alarm list on the screen. Acknowledge anything that has been latched |
| Every week | Check the water temperature and the conductivity against the thresholds you set |
| Every month | Check the flush actually ran: Next flush in should have counted down |
| Every year, or after 2000 pump hours | Carry out the maintenance, then acknowledge it so the counter restarts |
The maintenance alarm is what tells you when the year is up. It appears when the maintenance countdown reaches zero, or when more than 2000 pump hours have passed since the last acknowledgement.
What the maintenance involves
- Clean or replace the atomisation nozzles and the water filter.
- Check the water supply and the drain.
- Check the flush drain valve opens and closes.
- Check that the water flow sensor and the pressure sensors read sensibly.
- Acknowledge the maintenance so the counters restart.
To acknowledge it:
- on the screen, press Reset on the
Maintenance Requiredcard of the alarms screen; - over the fieldbus, write
1to theMAINTENANCEregister.
The web interface does not have a button for this. See Status and alarms.
Flushing
Flushing is part of routine care and it runs by itself. You can also start one by hand — see Using the product.
If the unit flushes but the conductivity stays high, the problem is the water, not the flushing.
Logs and history
The controller keeps a running log of its measurements in its own non-volatile memory. It records one entry per minute, together with the operating mode and the alarm state.
The full log can also be read over the fieldbus.
The controller also keeps the last 50 alarm events, with their timestamps. The screen shows them under ALARM HISTORY and the web interface shows them in the Alarm log card.
Backing up the settings
The controller has no built-in export function. To save a copy of the configuration:
- Read the configuration registers over Modbus and write them down, or
- photograph the Configuration page and the System card.
The settings that matter most for a restore are: the network settings, the fieldbus settings, the demand source, the alarm thresholds, the flush settings, and the valve step values.
To restore, write the values back and then save the configuration.
Saving settings
Settings changed on the screen or in the web interface are stored in the controller's non-volatile memory straight away.
Settings written over Modbus or BACnet are not stored until you ask for it. After
writing configuration registers over the fieldbus, write 1 to the SAVE_CONFIG
register. The controller stores the configuration and resets the register to 0 when it
is done.
The screen sends the save request for you.
Factory reset
A factory reset erases the controller's entire non-volatile memory: settings, the measurement log and the alarm history. The controller then restarts.
Warning
A factory reset destroys the measurement history and the alarm history. Do it only when you have a copy of the settings you need.
- Write
42838(hexadecimal0xA74E) to theFACTORY_RESETregister (address 302) over Modbus, BACnet or USB. - The controller erases its memory and restarts.
If the value written is not the right one, the controller ignores it and puts the register
back to 0.
After the reset the unit comes up with the factory defaults: a fixed address of
192.168.1.195, Modbus ID 1, the demand source set to 0-10V demand, and the operating
mode Standby.
Next steps
- Troubleshooting — what to do when something does not work.
- Connectivity — reaching the unit over the network or the fieldbus.