All attention messages on the ACC2 controller create logs. The first step to understanding any problem or message is to click the soft key for View Logs or access the logs from the Diagnostics menu on the controller. If the controller is connected to Centralus™, these messages are displayed in the software as well.
There are 3 types of logs and a filter function to narrow the number of logs displayed.
The controller will store up to 250 alarm logs, with date and time, beginning with the most recent alarm.
| Alarm | SMS | Description |
|---|---|---|
| StationSizeZero | Yes | Not detecting any station or decoder modules. The Station size is 0. |
| Lowvoltagfault | Yes | The primary AC power to the controller is too low (below 105 VAC). |
| RTC (Real Time Clock) | N/A | There can be a fault in the clock, and/or the CR2032 battery is dead or missing. |
| MainSafeFlowZoneFlowAlarm Detected | Yes | Overflow/Underflow/No Flow detected with a MainSafe. |
| StationFlowAlarmDetected (*) | N/A | Overflow/Underflow/No Flow detected for station. |
| DecoderModuleOverloaded | Yes | The decoder module's maximum current load has exceeded (1800mA on 1.2Hz). |
| StationFaultDetected | Yes | Overcurrent was detected for a station that exceeded 800mA. |
| PMVFaultDetected | Yes | Overcurrent detected for a Pump or master valve that exceeded 800mA. |
| WeatherSensorCommsFault Detected | Yes | No communication with a sensor. |
| MaximumTransformerCurrent Exceeded | N/A | Overcurrent detected on the internal transformer. Exceeding 1Amp on 50/60 Hz |
| CANBusFaultDetected | Yes | The Can Bus error message could be a fault in either the power supply board chip, decoder module, or a conventional module since they all have CAN chips (the exception is the flow module). |
| WeatherSensorAlarmDetected | N/A | Sensor status has changed from inactive to active. |
| NWWViolationDetected | Yes | A No Water Window schedule is active. |
| SensorDecoderFault | N/A | The sensor decoder is not programmed correctly or detected on the two-wire path. |
| PowerOutage | N/A | This fault is generated when the power is restored. |
| ClikSensorAlarmDetected | N/A | Clik sensor is active. |
A Flow Alarm is a "critical alarm" in Centralus, meaning the flow zone will no longer irrigate until the condition is cleared. When a master valve is installed, flooding and damage from broken pipes are prevented.
However, some flow alarms are nuisance alarms, and they must be cleared to resume normal irrigation.
A controller with a flow alarm will appear with the alarm indication in the controller list:
- When you select the alarmed controller, the Alarms and Logs view automatically opens. If the critical alarms are flow alarms, the Clear All Flow Alarms button appears.
- Press the button to clear the flow alarms. Remember that if the pipe is broken and has not been repaired, the alarm will occur again when irrigation resumes.
- Centralus will post a reminder of this, and ask you to confirm that you want to clear it. Press the button to continue, and Centralus will show that the command is being sent.
If you receive the green "Successful" message after a few seconds, the flow alarm(s) will be cleared. If the command is unsuccessful, you can try to clear it again.
Adjusting the station and flow zone characteristics at the controller panel can reduce or mitigate most false alarms.
Other significant messages that are not technically alarms are stored in the controller logs (up to 250 events). They are also arranged by date and time, with the most recent log first.
Station logs record every single event that occurs in the controller (up to 1500 events), beginning with the most recent. This can be useful for advanced troubleshooting or to verify that a station actually watered.
Still need help? We're here.
Tell us what you need support with and we'll find the best solution for you.