---
title: "Alarm Dictionary"
canonical: "https://farmconnect.docs.rubiconwater.com/space/FCKB/2205876303/Alarm%20Dictionary"
format: markdown
---
Many data points in the FarmConnect system have alarms enabled by default to provide value to the user as a warning or indicator. Other data points do not have alarms enabled by default but the user can enable and configure an alarm if useful.
Check the below page for your device to find out more about default enabled alarms, their purpose and how to resolve.
> Macro (children)
> Macro (hiddenfragment-macro)
>
> **Added some data from various sources which may or may not be useful.**
>
> I came up with a different table from the templates:
>
> | | | | | | | | |
> | --- | --- | --- | --- | --- | --- | --- | --- |
> | Template | Tag | Description | Alarm Group | HH | H | L | LL |
> | aquaspy150cmProbe | FC_COMM_FAIL | Device Comms Fail | SET | 0 | 0 | 0 | 0 |
> | aquaspy150cmProbe | FC_SM_SUM | Summated Soil Moisture | | 1950 | 1950 | 0 | 0 |
> | aquaspy150cmProbe | FC_SM_SUM_VSM | Summated Soil Moisture (VSM) | | 1500 | 1500 | 0 | 0 |
> | advancedStopGate | FC_IM_COMMS_FAIL | Comms fail | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_IM_BATT_VOLTAGE | Battery voltage | LL | 16 | 15 | 11 | 10.5 |
> | advancedStopGate | FC_GATE_COMMISSIONED | Shows if solar node believes imotor has been comissioned | | 1 | 1 | 1 | 1 |
> | advancedStopGate | FC_SETPOINT_FAIL | Failed to reach setpoint | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_IM_OVERTORQUE | Gate overtorque | HH | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_GATE_STATUS_GATE_OUT_OF_SERVICE | Gate out of service | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_WATER_LEAK | Water leak alarm | | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_POWER_FAILURE_DETECTED | Shows if solar node believes power failure is detected | | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_GATE_STATUS_OUT_OF_POSITION | Gate out of position | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_MOTOR_STATUS_WRONG_GATE_MOVEMENT_ALARM | Incorrect gate movement direction | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_HALL_SENSOR_INTEGRITY_ERROR | Shows if sensor integrity error is detected | | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_NO_MOVEMENT | No gate movement detected | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_BRUSHED_INTEGRITY_ERROR | Shows if brushed integrity error is detected | | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_HALL_SENSOR_ERROR | Shows if hall sensor error is detected | | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_GATE_STATUS_OVERTORQUED_LOCKED | Gate overtorque locked | SET | 0 | 0 | 0 | 0 |
> | advancedStopGate | FC_MOTOR_IS_UNLOADED | Low Current Closure | | 0 | 0 | 0 | 0 |
> | bladeValve | FC_IM_COMMS_FAIL | Comms fail | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_IM_BATT_VOLTAGE | Battery voltage | LL | 16 | 15 | 11 | 10.5 |
> | bladeValve | FC_GATE_COMMISSIONED | Shows if solar node believes imotor has been comissioned | | 1 | 1 | 1 | 1 |
> | bladeValve | FC_SETPOINT_FAIL | Failed to reach setpoint | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_IM_OVERTORQUE | Gate overtorque | HH | 0 | 0 | 0 | 0 |
> | bladeValve | FC_GATE_STATUS_GATE_OUT_OF_SERVICE | Gate out of service | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_WATER_LEAK | Water leak alarm | | 0 | 0 | 0 | 0 |
> | bladeValve | FC_POWER_FAILURE_DETECTED | Shows if solar node believes power failure is detected | | 0 | 0 | 0 | 0 |
> | bladeValve | FC_GATE_STATUS_OUT_OF_POSITION | Gate out of position | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_MOTOR_STATUS_WRONG_GATE_MOVEMENT_ALARM | Incorrect gate movement direction | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_HALL_SENSOR_INTEGRITY_ERROR | Shows if sensor integrity error is detected | | 0 | 0 | 0 | 0 |
> | bladeValve | FC_NO_MOVEMENT | No gate movement detected | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_BRUSHED_INTEGRITY_ERROR | Shows if brushed integrity error is detected | | 0 | 0 | 0 | 0 |
> | bladeValve | FC_HALL_SENSOR_ERROR | Shows if hall sensor error is detected | | 0 | 0 | 0 | 0 |
> | bladeValve | FC_GATE_STATUS_OVERTORQUED_LOCKED | Gate overtorque locked | SET | 0 | 0 | 0 | 0 |
> | bladeValve | FC_MOTOR_IS_UNLOADED | Low Current Closure | | 0 | 0 | 0 | 0 |
> | riserDrive | FC_IM_COMMS_FAIL | Comms fail | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_IM_BATT_VOLTAGE | Battery voltage | LL | 16 | 15 | 11 | 10.5 |
> | riserDrive | FC_GATE_COMMISSIONED | Shows if solar node believes imotor has been comissioned | | 1 | 1 | 1 | 1 |
> | riserDrive | FC_SETPOINT_FAIL | Failed to reach setpoint | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_IM_OVERTORQUE | Gate overtorque | HH | 0 | 0 | 0 | 0 |
> | riserDrive | FC_GATE_STATUS_GATE_OUT_OF_SERVICE | Gate out of service | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_WATER_LEAK | Water leak alarm | | 0 | 0 | 0 | 0 |
> | riserDrive | FC_POWER_FAILURE_DETECTED | Shows if solar node believes power failure is detected | | 0 | 0 | 0 | 0 |
> | riserDrive | FC_GATE_STATUS_OUT_OF_POSITION | Gate out of position | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_MOTOR_STATUS_WRONG_GATE_MOVEMENT_ALARM | Incorrect gate movement direction | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_HALL_SENSOR_INTEGRITY_ERROR | Shows if sensor integrity error is detected | | 0 | 0 | 0 | 0 |
> | riserDrive | FC_NO_MOVEMENT | No gate movement detected | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_BRUSHED_INTEGRITY_ERROR | Shows if brushed integrity error is detected | | 0 | 0 | 0 | 0 |
> | riserDrive | FC_HALL_SENSOR_ERROR | Shows if hall sensor error is detected | | 0 | 0 | 0 | 0 |
> | riserDrive | FC_GATE_STATUS_OVERTORQUED_LOCKED | Gate overtorque locked | SET | 0 | 0 | 0 | 0 |
> | riserDrive | FC_MOTOR_IS_UNLOADED | Low Current Closure | | 0 | 0 | 0 | 0 |
> | rubiconETWS | FC_COMM_FAIL | Device comms fail | HH | 0 | 0 | 0 | 0 |
> | sentek90cmProbe | FC_COMM_FAIL | Device Comms Fail | SET | 0 | 0 | 0 | 0 |
> | sentek90cmProbe | FC_SM_SUM | Summated Soil Moisture | | 1300 | 1300 | 0 | 0 |
> | sentek90cmProbe | FC_SM_SUM_VSM | Summated Soil Moisture (VSM) | | 1000 | 1000 | 0 | 0 |
> | sentekSdi12Probe | FC_COMM_FAIL | Device comms fail | SET | 0 | 0 | 0 | 0 |
> | sentekSdi12Probe | FC_SM_SUM | Summated soil moisture | | 1300 | 1300 | 0 | 0 |
> | sentekSdi12Probe | FC_SM_SUM_VSM | Summated soil moisture (VSM) | | 1000 | 1000 | 0 | 0 |
> | siemensMag8000 | FC_COMM_FAIL | Device comms fail | HH | 0 | 0 | 0 | 0 |
> | smartFrontSensor | FC_COMM_FAIL | Device Comms Fail | SET | 0 | 0 | 0 | 0 |
> | smartFrontSensor | FC_TIMEOUT_ERROR | SmartFront Detection Timed Out | | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_IM_COMMS_FAIL | Comms fail | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_IM_BATT_VOLTAGE | Battery voltage | LL | 16 | 15 | 11 | 10.5 |
> | smartStopGate | FC_GATE_COMMISSIONED | Shows if solar node believes imotor has been comissioned | | 1 | 1 | 1 | 1 |
> | smartStopGate | FC_SETPOINT_FAIL | Failed to reach setpoint | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_IM_OVERTORQUE | Gate overtorque | HH | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_GATE_STATUS_GATE_OUT_OF_SERVICE | Gate out of service | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_WATER_LEAK | Water leak alarm | | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_POWER_FAILURE_DETECTED | Shows if solar node believes power failure is detected | | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_GATE_STATUS_OUT_OF_POSITION | Gate out of position | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_MOTOR_STATUS_WRONG_GATE_MOVEMENT_ALARM | Incorrect gate movement direction | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_HALL_SENSOR_INTEGRITY_ERROR | Shows if sensor integrity error is detected | | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_NO_MOVEMENT | No gate movement detected | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_BRUSHED_INTEGRITY_ERROR | Shows if brushed integrity error is detected | | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_HALL_SENSOR_ERROR | Shows if hall sensor error is detected | | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_GATE_STATUS_OVERTORQUED_LOCKED | Gate overtorque locked | SET | 0 | 0 | 0 | 0 |
> | smartStopGate | FC_MOTOR_IS_UNLOADED | Low Current Closure | | 0 | 0 | 0 | 0 |
> | sonarayFlowMeter | FC_COMM_FAIL | Device comms fail | HH | 0 | 0 | 0 | 0 |
> | sonarayFlowMeter | FC_S_FLOW_VAL | Current flow rate of the gate | | | | | |
> | standardSmartMeter | FC_COMM_FAIL | Device Comms Fail | HH | 0 | 0 | 0 | 0 |
> | standardSmartMeter | FC_S_FLOW_VAL | Current flow rate of the gate | | 40 | 40 | 0 | 0 |
> | standardSmartMeter | FC_S_GATE_OPEN_MM | Current mm open of the gate | | 100 | 100 | 0 | 0 |
> | standardSmartMeter | FC_S_GATE_OPEN_MM_IMP | Current mm open of the gate (Inch) | | 100 | 100 | 0 | 0 |
> | standardSmartMeter | FC_S_FLOW_VAL_IMP | Current flow rate of the gate (cfs) | | 40 | 40 | 0 | 0 |
> | vsdPump | FC_MOTOR_STATUS | Motor Status | | 2 | 2 | 0 | 0 |
> | waterLevelSensor | FC_WLS_COMMS_FAIL | Comms fail | SET | 0 | 0 | 0 | 0 |
> | feritSolarNode | FC_PM_BATTERY_VOLTAGE | Battery voltage | SET | 25 | 25 | 11.5 | 9 |
> | feritSolarNode | FC_OVERTEMP_ALARM | Overtemp alarm | | 0 | 0 | 0 | 0 |
> | feritSolarNode | COMM_STATUS | Communication status | HH | 2 | 2 | 0 | 0 |
>
> **These are the tags in the tag database that have alarm troubleshooting info attached (I’ve just included them all so most aren’t relevant to FC). I have a spreadsheet with more columns in it if necessary (eg tag description, objects etc)**
>
> | | | | |
> | --- | --- | --- | --- |
> | TAG_NAME | POSSIBLE_CAUSES | ACTIONS | FURTHER_INFORMATION |
> | G1_OOS | Possible Causes:
> A) Can be caused by gate overtorque alarm (Gx_OVTRQ).
> B) No movement detected alarm (Gx_NO_MOVE).
> C) Gate movement in wrong direction alarm (Gx_MOV_DIRN).
> D) Low battery voltage based errors,
> E) Solardrive processor based errors
> F) SDB fusing event - from short circuit or lightning strike. | A) See Gx_OVTRQ alarm info.
> B) See Gx_NO_MOVE alarm info.
> C) See Gx_MOV_DIRN alarm info.
> D) Check battery voltage and check BATT_VOLT alarm info if low.
> E) Check pedestal for SDB alarms???? SDB_FAULT alarm???
> F) Check pedestal for fusing alarm.
> Check wiring for short circuits.
> If lightning strike suspected, assess site earthing??? |
> | G1_OVTRQ | On last gate movement motor drew too much current so was stopped.
> A) Obstruction under undershot gate (SlipGate/SlipMeter/PikoMeter) preventing it from closing.
> B) Too much friction on gate.
> C) Maximum current draw limit set too low.
> D) Obstruction/silt/rocks downstream of FlumeGate preventing it from lowering fully.
> E) Undershot gate has not been operated for years and is stuck closed. | A) Could try to open gate extra to attempt to flush obstruction away. Otherwise, site visit to check for obstruction under the gate and clear.
> B) Inspect frame to ensure straight. Lubricate seals. If undershot gate seals can be loosened.
> C) Check maximum current limit tag against design for the model gate.
> D) Inspect site for silt, rocks etc preventing gate from fully opening. Clear if can. If permanent obstruction, re-callibrate gate so maximum gate opening is above the obstuction.
> E) Check for silt buildup against gate and clear.
> Get gate moving by either retrying multiple times or manually assisting gate to move or temporarily raising maximum current limit. Once gate moves, it should be free to move again without overtorquing. Remember to return maximum current limit to previous lower value. |
> | G1_SDB_COMM_STATUS | This alarm is set by the RTU when it cannot communicate to the SDB. This means no remote control of the gate and any gate or power data in the RTU is not up to date.
> Possible causes:
> A) Modbus wiring / loom issues. Note if this is the cause, the gate is likely still operable via the pedestal.
> B) SDB failure
> C) Battery / Power Supply failure of a slave gate in a multi-gate FlumeGate or SlipGate site.
> D) RTU configuration issue
> E) SDB modbus address misconfigured | A) Check wiring.
> B) Check SDB.
> C) Check battery / power supply.
> D) Check which port SDB loom is plugged into and ensure RTU site configuration file matches.
> E) Check SDB modbus address in pedestal is correct. |
> | G1_SDB_FAULT | Fault with the SDB affecting ability to communicate to encoder. | If monitoring site only (no gate), alarm can be ignored. Otherwise, check SDB is configured correctly. Otherwise, replace SDB. |
> | G1_SDB_MOTOR_DISCONNECT | A) Battery voltage is low and below the SDB's motor disconnect threshold. Threshold is typically (subject to change) 11V for a lead acid battery or 12.4V for a Lithium ion battery.
> B) Battery voltage was low and has recovered but on SCADA alarm is still on because RTU was not communicating when alarm cleared.
> C) Incorrect configuation of Motor Disconnect threshold for battery installed. | A) See BATT_VOLT tag alarm info for causes and related actions of low battery voltage.
> B) Poll alarm to clear.
> C) Check Motor Disconnect theshold configured against recommendation for battery type installed. |
> | INSUFFICIENT_PATHS | Sonaray board in SlipMeter/PikoMeter/BladeMeter does not have enough paths functioning to calculate flow accurately. When this alarm occurs, Sonaray holds processed flow static. Raw flow can be used to see Sonaray's estimated flow based on functioning paths.
> Possible causes:
> A) Water depth below minimum number of planes to measure flow.
> B) Obstruction in box/pipe blocking transducers.
> C) Aquatic growth on Sonaray transducers.
> D) Water level measurement error causing Sonaray to think extra planes submerged below water when they are not.
> E) Sonaray maximum velocity limit set too low for hydraulic scenario.
> F) Hydraulic problem causing bubles or drawdown inside box/pipe, even though box/pipe is fully submerged, causing top transducer planes not to measure.
> G) Fault with transducer hardware. | A) Raise water level if it is too low, otherwise ignore alarm.
> B) Check box/pipe for obstructions such as weeds or silt and clear. If cannot access box/pipe, can try to open gate extra to atttempt to flush through obstruction.
> C) Clean transducers.
> D) Check for water level sensor alarms and resolve.
> Check water level datum is correct for model SlipMeter/PikoMeter and level sensor spacer installed.
> Check Minimum Gate Elevation tag is correct distance below site datum for SlipMeter/PikoMeter model installed.
> Check Sonaray Water Level datum tag (SONARAY_WL_DATUM) is set correctly. For SlipMeters/PikoMeters with RTU software version > 5.043, set to zero. For lower versions, preferably upgrade RTU software to latest and set to zero. Otherwise, set appropriate offset value to convert water level into Sonaray depth.
> E) Check path velocities. If non-symetrical and with a mix of high and low velocities, with high velocities more than 60% of maximum velocity limit, raise Sonaray's maximum velocity limit to see if this resolves the issue.
> F) Check insufficient path tag / velocity paths to see if top paths are excluded / stop functioning at higher velocities / flow rates. Test if closing off the gate reduces the turbulence and restores functioning of the top planes. If so, consider operating SlipMeter/PikoMeter at the lower flows. Otherwise, discuss with Rubicon options how to alter entry hydraulics
> G) Discuss options with Rubicon, depending on model, may need to pull out SlipMeter/PikoMeter/BladeMeter to access transducers. |
> | LEAKAGE_ALARM | A) Leakage under/around gate/valve.
> B) Gate/valve position incorrect causing Sonaray to think gate is closed when it is not.
> C) False high flow measurement.
> D) Leakage alarm thresholds set too tight. | A) Check if gate/valve is actually closed and leakage is occurring. Resolve source of leak.
> B) Check if gate/valve position is zero indicating closed but is physically still open. If so, re-reference / re-calibrate gate/valve position.
> C) Check velocity paths (may need to configure bursting of them first) to work out where the false high flow measurement is coming from.
> D) If none of the above problems, leakage alarm thresholda may be set too tight. Consider raising them. |
> | LOW_FLOW | A) SlipMeter/PikoMeter/BladeMeter left open but the flow is too low to measure.
> B) Flow setpoint of SlipMeter/PikoMeter/BladeMeter is below or slightly above the low flow threshold, causing gate to open and close and LOW_FLOW alarm to toggle on and off.
> C) Under measurement of flow. | A) Close gate/valve if it does not need to be open.
> B) If operating site in flow control, consider operating in Position control instead at a low opening.
> Consider if flow measurement / flow control is needed at this low flow, consider lowering the low flow cut-off threshold. Note this may introduce meter creep if the gate/valve is left open when there is no actual flow.
> C) Check flow measurement is reasonable for actual flow observed. Check velocity paths for extreme negative values / outliers. |
> | MAX_FLOW_EXCEEDED | A) Max flow threshold set too low for installation / operating conditions. This may be the case if the head across the SlipMeter/PikoMeter is high or a tall model variant is in use.
> B) Faulty Sonaray flow measurement causing over-measurement of flow. | A) Determine if site can or should be passing a flow 25% below the maximum flow threshold or higher. If so, increase the maximum flow threshold at least 25% above the expected highest maximum flow reading.
> B) Investigate Sonaray path velocities and flow measurement. |
> | PEER_COMM_STATUS | Peer communications will fail if:
> A) Thee peer site has a site power or communication issue.
> B) The peer site has an upstream level sensor fault
> C) The site or peer site's peer communication tags / site tables are not configured correctly.
> D) If the peer site is on a different line and the peer site is missing or has an incorrect network config file
> E) If the site's or peer site's radio is not configured for peer communications | A) Check you can communicate to the peer site via SCADA. If not, resolve its communication issue. See COMM_STATUS alarm info for further advice.
> B) Check peer site's USS_STATUS alarm and resolve it.
> C) If dynamic site tables are being used for the system, check dynamic site talble tags at site and peer site have correct information and dynamic site table is enabled. Else, check site and peer site have correct static site table via STS.
> D) Use STS to check network config files at site and peer site and download up to date ones if those present are incorrect of missing.
> E) Check radio's of site and peer site are programmed for peer comms. Reconfigue if not. |
> | PIPE_NOT_FULL_ALARM | Pipe not full affects BladeMeter flow measurement and control. Possible causes:
> A) Water depth inside BladeMeter is low.
> B) Air entrapment/bubble inside BladeMeter affecting pipe not full sensor.
> C) Fault with pipe not full sensor. | A) Consider closing off BladeMeter valve to bring water level up.
> Check supply to pipe-system BladeMeter comes out of.
> B) Flush BladeMeter to attempt to clear. If pipe not full sensor is at top of pipe, offsetting to the side slightly may bring it below air bubbles???
> C) Investigate sensor. |
> | PRESET_FN_MISSING | Moscad-M RTU is missing its preset application file. This will cause presets not to work. | Install all required application software files for Moscad-M build. |
> | PS_COMM_FAILURES | Preset service trying to write set a control preset for a site but communication is not going through. | Check there is an order set to start/stop/change flowrate soon but there is no corresponding preset. In this case, be aware gate won't start/stop etc based on order. Potential manual or local intervention may be required.
> See COMM_STATUS alarm info for further advice about resolving communication problems. |
> | RTU_TIME_NOT_SET | Possible causes:
> A) Recent restart of RTU and time not set yet.
> B) No time synching enabled for system and time never set. | A and B)
> Beware RTU will not act on any Presets actions on time unless this is resolved, so check presets if cannot/don't resolve.
> Set time in RTU via SiteConnect / SCADAConnect Set RTU Time function.
> B) If alarm has been on for considerable time or the alarm widespread issue across many sites, check whether time synching of RTUs is enabled for the system. |
> | SDB_FAULT | Internal fault within SDB. Main SDB CPU is not able to communicate with the Secondary SDB CPU. | If monitoring site only (no gate), alarm can be ignored.
> Otherwise, replace SDB. |
> | SDB_RTU_DISCONNECT | A) Battery voltage is low and below the SDB's RTU disconnect threshold. Threshold is typically 10.5V for a lead acid battery or 12V for a Lithium ion battery.
> B) Battery voltage was low and has recovered but on SCADA alarm is still on because RTU was not communicating when alarm cleared.
> C) Legacy SDB version (<6.50) software bug where SDB_RTU_DISCONNECT alarm does not clear after power startup.
> D) Incorrect configuation of RTU/radio Disconnect threshold for battery installed. | A) See BATT_VOLT tag alarm info for causes and related actions of low battery voltage.
> B) Poll alarm to clear.
> C) If SDB software version < 6.50 and battery voltage has recovered and polling does not clear alarm, updgrade to latest SDB software.
> D) Check RTU/radio Disconnect theshold configured against recommendation for battery type installed. |
> | SITE_OPER_STATUS | A) Outlet/turnout taking water when no flow ordered.
> B) Outlet/turnout not taking water when no flow ordered.
> C) Outlet/turnout taking significantly less water than ordered.
> D) Outlet/turnout taking significantly more water than ordered.
> E) Checking of orders configured for a system where farmers do not place orders. | A-D) Assess if outlet/turnout is operating in line with its order and whether farmer should be contacted to ammend order or flow extraction.
> E) Ask Rubicon to disable checking of outlet/turnout flows against orders. |
> | SITES_TBL_NOT_LOADED | Bursting may not work if the RTU has no sites table. Possible causes:
> A) No static or dynamic sites table loaded or configured in RTU.
> B) Dynamic sites table configured but USE_DYNAMIC_SITES_TBL tag disabled (=0) ????? | A) Load dynamic or static sites table with gateway link id and line information. Include any other peer sites the RTU needs to communicate with.
> B) Check GW1_SITE_ID and GW1_LINK_ID tags are configured correctly with gateway information and set USE_DYNAMIC_SITES_TBL to enabled (=1). |
> | ACU_STORAGE_FULL | A) An excessive flow rate has been recorded by the Sonaray Board causing the volume recorded in the Sonaray Volume register to exceed 114000 ML B) The Sonaray has been installed for some time (typically many years) and the volume has exceeded 114000ML | A) Reprogram the Sonaray Board with the latest firmware to reset the Volume register to zero B) Consider adjusting the volume increment backup rate to a value higher than default of 0.1 ML. This can be done by an Ad Hoc Sonaray register write | [https://rubiconwater.atlassian.net/wiki/spaces/PSG/pages/1844314113](https://rubiconwater.atlassian.net/wiki/spaces/PSG/pages/1844314113) |
> | AI1_FAIL_STATUS | Analog Input 1 signal is outside expected range. Likley causes:
> A) Analog instrument is not installed
> B) Analog instrument wiring to the RTU fault/fused
> C) Analog instrument problem
> D) Analog Intrument poser supply fault/fused
> E) RTU Analog input card fault | A) Install AI instrument or disabale Tag AI1_ENABLE_STATUS (Set = 0)
> B) Check AI instrument wiring to RTU.
> C) Check AI instrument is working and current output is in 4-20mA range.
> D) Check Voltage supply to Analog Instrument (expect DC 12 or 24V)
> E) Check RTU Configuration supports an AI card and/or check RTU error logger and replace RTU Analog Board if faulty. |
> | AI2_FAIL_STATUS | Analog Input 2 signal is outside expected range. Likley causes:
> A) Analog instrument is not installed
> B) Analog instrument wiring to the RTU fault/fused
> C) Analog instrument problem D) Analog Intrument poser supply fault/fused E) RTU Analog input card fault | A) Install AI instrument or disabale Tag AI2_ENABLE_STATUS (Set = 0)
> B) Check AI instrument wiring to RTU.
> C) Check AI instrument is working and current output is in 4-20mA range. D) Check Voltage supply to Analog Instrument (expect DC 12 or 24V) E) Check RTU Configuration supports an AI card and/or check RTU error logger and replace RTU Analog Board if faulty. |
> | BATT_VOLT | Low battery voltage could be caused by:
> A) Solar panel issue - missing, obstructed, shaded.
> B) Battery charging issues - wiring or fault with battery
> C) Excessive gate movements.
> D) Too many cloudy days / shorter winter sunlight days.
> E) Additional non-standard equipment attached to current drawing exta current | Actions:
> A) Check solar panel is present. Clean it. Check for shading and clear or reposition. Check angle to sun is correct and adjust if necessary.
> B) Check wiring to battey. If battery won't charge/retain charge then replace.
> C) SCADAConnect investigation of gate movements.
> Check for noisy level or flow measurements causing excessive gate movements are fix at source.
> Check flow controller loop timer, deadbands and for a SlipMeter/PikoMeter/BladeMeter/SlipGate-M other flow controller tuning parameters.
> For a multi-FlumeGate site, activate low movement flow allocation algorithm (need RTU softwave version 5.06+).
> D) Consider hibernating site over winter if no water is in the canal. Consider if gate movements can be reduced or other load shedding to reduce drain on battery. Consider an additional battery.
> E) Identify any extra equipment and their current draw. Consider if equipment is needed or there are lower power alternatives. Consider larger/extra battery / solar panel. |
> | BURST_STATUS | Burst status alarm indicates site has burst more than its limit in a minute and will inhibit further bursting until the burst rate drops below the limit. Possible causes:
> A) Faulty sensor readings spiking or jumping around causing excessive level or flow tag changes and bursts.
> B) Flow, level, volume or gate movement COS tags set too low.
> C) An alarm is toggling on and off excessively.
> D) Other tags are being bursting excessively. | A) Review level and flow historical data to identify false readings. Correct fix any faulty sensors found.
> B) Review level, flow, volume and gate movement historic data to identify tag which is burst excessively. Check corresponding COS settings are set appropriately.
> C) Check alarm history for the site to identify alarms with high alarm counts. Rectify the cause of any frequently occuring alarms found.
> D) If it is unclear which tag(s) are being burst, use the Comms Monitor program in SCADAConnect to monitor burst traffic to identify the tag being burst excessively. |
> | COMM_STATUS | A) Site Power issue
> B) Site antenna/radio/connection issue
> C) RTU issue
> D) Gateway / node configuration issue
> E) Weak signal issue
> F) Node or gateway wide comms issue | A) Look on SCADA for signs of low power. Go to site to diagnose and rectify. Refer to BATT_VOLT alarm info for possible causes and actions.
> B) Site visit to check radio, antenna and connections.
> If GSM modem is in use, check it is functioning and programmed correctly.
> C) Check RTU is functioning.
> Check site config file is correct.
> If ip config file or network config files are required, check they are present and correct.
> D) Check gateway has site in site table.
> E) Check RSSI strength.
> Check for line of sight obstruction between site and node such as trees and consider if it can be cleared.
> If yagi antenna, check direction.
> If omni-directional antenna, consider swapping for a yagi antenna.
> Consider changing the node the site connects to.
> F) If many/all sites for a node or gateway are not communicating, resolve node/gateway issue. |
> | CTRL_SUSPENDED | When CTRL_SUSPENDED=1 the controller has been suspended, that is the controller cannot meet its control objective and the controller will not move the gate.
Possible Causes:
> A) No gates available for control. A gate may be unavaible for control because of:
> i) a G1_OOS or G1_SDB_COMM_STATUS or G1_COMMISSION alarm or
> ii) because it is in Manual Mode (G1_MANUAL tag) or
> iii) it is in Local Manual or Local Position mode (G1_LOC_REMOTE tag).
> B) FLOW_METER_COMMS alarm if site is a SlipMeter or PikoMeter or BladeMeter or SlipGate-M.
> C) USS_STATUS alarm if site is operating in upstream level control or if it is a FlumeGate or SlipGate-R site.
> D) DSS_STATUS alarm if site it is operating in downstream level control.
> E) PEER_COMM_STATUS alarm if site is operating in TCC or Distant upstream level control. | As gate will not move when control suspended, monitor canal and take over manual control if needed.
Actions to investigate the cause:
> A) i) Check for alarms on gates such as G1_OOS or G1_SDB_COMM_STATUS or G1_COMMISSION and resolve those.
> ii) If gate is in manual mode can be made operational, change G1_MANUAL tag state to Auto mode.
> iii) If gate is in Local Manual or Local Position mode and can be made operational, go to site and put the gate into remote mode via the pedestal.
B) to E) Check alarm info of corresponding alarm for potential causes and actions. | alarmInfo |
> | DI1_STATUS | A) Level sensor has no power - fault with SDB power supply.
> B) Level sensor fault.
> C) Modbus comms / wiring fault between RTU and level sensor. | A) Check power to sensor onsite.
> B) Cycle power to level sensor in case it restarts. Otherwise, check level sensor is working onsite.
> C) Check / replace / fix looms and connections between RTU and level sensor. |
> | DROWN_ALARM | Drown alarm is caused by FlumeGate with head loss less than configured minimum head (DROWN_MIN).
> A) FlumeGate operating submerged in low head conditions
> B) faulty level sensor readings affecting head calculations
> C) DROWN_MIN threshold set too high |
> | DSL_SENS_ERROR | Alarm is set when discrepancy between primary and secondary level sensors is greater than threshold (LEV_SEN_ERROR_DB tag). Possible causes:
> A) Primary or secondary level sensor datums not set correctly, causing an offset.
> B) Primary or secondary level sensor reading incorrect value.
> C) Hydraulics at site causes water level to be higher on one side than the other. E.g. when site is on bend in canal, water will be higher on the outside of the bend at high flows. | A) Check level sensor datums are correct for gate model, spacer installed. Check micron level sensors are sitting directly on pin (or spacer on pin).
> For multi-gate sites where level sensor is on a slave gate, check site datum of slaves gates are correct relative to master gate.
> B) Check level sensors reading correctly.
> C) Check hydraulics at site to detemine expected variation between water level readings and raise threshold higher than expected variations in water levels. |
> | DSL1_OLD_AGE | Level sensor has not measured any new values in a predefined amount of time set in the level sensor.
> A) Level sensor is not in water.
> B) Debris/obstruction in level sensor.
> C) Stilling well blocked.
> D) Faulty level sensor hardware
> E) Electrical noise interference | A) Check if level sensor is in water.
> Raise water level if it is too low.
> Or if no alarm required when water level is this low, this alarm can be inhibited by the DSL1_OLD_AGE_INHIBIT tag (RTU software v5.05????+ required.)
> Or if low water levels need to be measured, consider if water level sensor can be lowered, or an additional submergable micron level sensor is required, or a longer range level sensor can be installed.
> B) Clean level sensor thoroughly. Separate ranging tube from sensor head. Then push wet rag down through micron level sensor ranging chamber to clean, until it comes out the other end. Clean or replace bottom and side filters.
> C) Remove level sensor from stilling well. Then blow compressed air down stilling well to flush out any blockage.
> D) If other causes eliminated, replace sensor.
> E) Investigate onsite. |
> | DSL1_SENS_OOR | A) Raw water level below below configured minimum raw water level (DSL1_MIN_READING tag).
> B) Raw water level above configured maximum raw water level (DSL1_MAX_READING tag) or above 50mm below micron level sensor reference level.
> C) Level sensor datum not configured correctly causing water level reading to be higher than the site datum (SITE_DATUM tag).
> D) Faulty water level reading resulting in one of the above thresholds being breached. | A) Raise water level if it is too low.
> Or if alarm for water level reading is not needed, lower the minimum raw water level to the required level. It can be set to -1 so this alarm never triggers.
> Or if low water levels need to be measured, consider if water level sensor can be lowered, or an additional submergable micron level sensor is required, or a longer range level sensor can be installed.
> B) Lower water level.
> Of if water levels this high need to be measured, raise water level sensor.
> C) Check level sensor datum is as per model and spacer installed. If externally installed, check level sensor datum is the distance from the Site Datum to the level at which the sensor reads zero.
> D) Inspect and clean level sensor. If issue persists after thorough cleaning, replace sensor. |
> | DSL1_SENS_STATUS | Possible causes:
> A) Modbus wiring causing no comms to sensor problem
> B) Sensor fault causing sensor not to respond
> C) Sensor power issue
> D) No water level sensor installed.
> E) Level sensor modbus address is incorrect. 101 = Primary upstream, 102 = Primary secondary, 103 = secondary upstream, 104 = secondary downstream.
> F) If analog input level sensor, AI configuration error.
> G) Mapped analog input level sensor problem causing AIx_FAIL_STATUS alarm. | A) Check wiring between level sensor and RTU.
> B) Check sensor is working. Can try cyclying power to sensor to see if this restores sensor functionality.
> C) Check voltage supply to level sensor
> D) Install level sensor and configure appropriately.
> E) Check level sensor modbus address is correct for level sensor location.
> F) Check AIx_ENABLE_STATUS tag is set.
> Check AIx_LEV_MAPPING tag is set to 102 to map the analog input to the downstream water level.
> G) Check corresponding AIx_FAIL_STATUS tag. If set, refer to AIx_FAIL_STATUS alarm info. |
> | DSL2_SENS_OOR | A) Raw water level below below configured minimum raw water level (DSL2_MIN_READING tag).
> B) Raw water level above configured maximum raw water level (DSL2_MAX_READING tag) or above 50mm below micron level sensor reference level.
> C) Level sensor datum not configured correctly causing water level reading to be higher than the site datum (SITE_DATUM tag).
> D) Faulty water level reading resulting in one of the above thresholds being breached. | A) Raise water level if it is too low.
> Or if alarm for water level reading is not needed, lower the minimum raw water level to the required level. It can be set to -1 so this alarm never triggers.
> Or if low water levels need to be measured, consider if water level sensor can be lowered, or an additional submergable micron level sensor is required, or a longer range level sensor can be installed.
> B) Lower water level.
> Of if water levels this high need to be measured, raise water level sensor.
> C) Check level sensor datum is as per model and spacer installed. If externally installed, check level sensor datum is the distance from the Site Datum to the level at which the sensor reads zero.
> D) Inspect and clean level sensor. If issue persists after thorough cleaning, replace sensor. |
> | DSL2_SENS_STATUS | Possible causes:
> A) Modbus wiring causing no comms to sensor problem
> B) Sensor fault causing sensor not to respond
> C) Sensor power issue
> D) No water level sensor installed.
> E) Level sensor modbus address is incorrect. 101 = Primary upstream, 102 = Primary secondary, 103 = secondary upstream, 104 = secondary downstream.
> F) If analog input level sensor, AI configuration error.
> G) Mapped analog input level sensor problem causing AIx_FAIL_STATUS alarm. | A) Check wiring between level sensor and RTU.
> B) Check sensor is working. Can try cyclying power to sensor to see if this restores sensor functionality.
> C) Check voltage supply to level sensor
> D) Install level sensor and configure appropriately.
> E) Check level sensor modbus address is correct for level sensor location.
> F) Check AIx_ENABLE_STATUS tag is set.
> Check AIx_LEV_MAPPING tag is set to 102 to map the analog input to the downstream water level.
> G) Check corresponding AIx_FAIL_STATUS tag. If set, refer to AIx_FAIL_STATUS alarm info. |
> | DSS_STATUS | Possible causes:
> A) DSL1_SENS_STATUS alarm, sensor not communicating to RTU.
> B) Sensor out of range alarm DSL1_SENS_OOR.
> C) Sensor old age alarm, DSL1_OLD_AGE alarm.
> D) No level sensor enabled or configured.
> E) If EMG site and level sensor is attached to a different site/gate, EMG level sensor sharing not setup correctly or EMG comms not working. | A) See DSL1_SENS_STATUS alarm info.
> B) See DSL1_SENS_OOR alarm info.
> C) See DSL1_OLD_AGE alarm info.
> D) If sensor is installed, enable it via the DSL1_SENS_ENABLE tag.
> E) Ensure EMG sites are communicating and EMG level sensor sharing is configured correctly. |
> | FAILED_TO_CLOSE | A) Limit switch detection problem.
> B) Actuation problem.
> C) Blown fuse on motor power circuit. | Check onsite if valve is actually closed.
> A) If closed, check limit switch and digital input to RTU.
> B) If not closed, test actuation system and diagnose any problems preventing valve closing.
> C) Check motor power circuit fuse and replace if blown. |
> | FAILED_TO_OPEN | A) Limit switch detection problem.
> B) Actuation problem.
> C) Blown fuse on motor power circuit. | Check onsite if valve is actually closed.
> A) If closed, check limit switch and digital input to RTU.
> B) If not closed, test actuation system and diagnose any problems preventing valve closing.
> C) Check motor power circuit fuse and replace if blown. |
> | FM_COMM_STATUS | RTU to flow meter modbus comms failure. Whilst this alarm is active, flow measurement and any flow meter tags will not be updated in the RTU and hence values polled via SCADA will be old. Possible causes:
> A) RTU to flow meter wiring fault.
> B) Flow meter power fault.
> C) Flow meter fault.
> D) Misconfiguration of RTU
> E) Misconfiguration of flow meter | A) Assess wiring between RTU and flow meter.
> B) Check if flow meter power supply is working.
> C) Check if flow meter is functioning.
> D) Check RTU has correct application files and site configuation port settings in RTU are correct.
> E) Check serial port settings match requirements for communication to RTU. |
> | FUSE_BLOWN | Butterfly valve or Penstock with analog input wiring/connection issue. | Check wiring between analog board and actuator for damage or moisture/corrosion. |
> | G1_COMMISSION | A) Intemittent alarm due to RTU reboot caused by on site works.
> B) Intermittent alarm due to RTU reboot caued by power issue.
> C) Intermittent alarm due to RTU reboot caused by fusing issue.
> D) Persistent alarm due to SDB loss of power.
> E) Gate was never commissioned. | A) Check if onsite works were conducted at the time of the alarm.
> B) Check low BATT_VOLT alarm info for causes and actions.
> C) Check for fusing alarm on pedestal. Check wiring and components for electrical short problems.
> D) Check low BATT_VOLT alarm info for causes and actions.
> E) Follow gate commissioning procedure. |
> | G1_LOC_REM | The alarm indicates that the site is in local mode. Whilst in local mode, the site cannot be operated remotely via SCADA and any will not act on any Presets.
> A) Gate was left in local mode last time it was visited.
> B) SDB has lost power and started up in local mode. | A) If gate does not need to be in Local mode, visit site and put into remote mode via the pedestal.
> B) Visit site to investigate the cause of the power loss. Loose power cable? Fusing issue? Battery issue? |
> | G1_MB_LEAK_STATUS | Possible Causes:
> A) Water ingress into motor board housing
> B) Faulty or over-sensitive water detection sensor | Site visit. Open the motor board assembly housing and check for signs of water ingress and damage.
> A) If signs of water ingress of damage found, check/inspect seals/gaskets and motorboard and replace any damaged components.
> B) Otherwise, replace water detection sensor |
> | G1_MECH_ACT_FAIL | Gate closes and closing torque has not been detected. Possible causes:
> A) Mechanical failure
> B) Gate positioning problem | Site visit and inspection.
> A) Attempt to move gate and check if it actually moves. If it does not move diagnose mechanical problem.
> B) Check gate position is correct. If not re-reference and check gate closes correctly without futher alarms. If position measurement is still incorrect, check encoder. |
> | G1_MOV_DIRN | Motor wiring reversed. | Physcially reverse wiring of motor or change actuation direction in pedestal. |
> | G1_NO_MOVE | A) Wiring problem
> B) Encoder problem
> C) Motor problem | Move gate and check if motor turns. If it turns but position does not update, then is encoder problem and not a motor problem.
> If motor does not turn, then could be motor problem or motor wiring problem. Check wiring before replacing motor or encoder. |
> | SYSIDENT_ENABLED | Someone has configured extra 1 minute bursting of level, flow and gate elevation data. This is usually done for the purpose of pool hydraulics testing. | If no pool hydraulic testing is required, this tag can be set to disabled. |
> | USL_SENS_ERROR | Alarm is set when discrepancy between primary and secondary level sensors is greater than threshold (LEV_SEN_ERROR_DB tag). Possible causes:
> A) Primary or secondary level sensor datums not set correctly, causing an offset.
> B) Primary or secondary level sensor reading incorrect value.
> C) Hydraulics at site causes water level to be higher on one side than the other. E.g. when site is on bend in canal, water will be higher on the outside of the bend at high flows. | A) Check level sensor datums are correct for gate model, spacer installed. Check micron level sensors are sitting directly on pin (or spacer on pin).
> For multi-gate sites where level sensor is on a slave gate, check site datum of slaves gates are correct relative to master gate.
> B) Check level sensors reading correctly.
> C) Check hydraulics at site to detemine expected variation between water level readings and raise threshold higher than expected variations in water levels. |
> | USL_VAL | Alarm triggered by SCADA system when water level is below or above configured low or high alarm limit thresholds.
> A) Water level in pool is too high.
> B) Water level in pool is too low.
> C) Alarm limit thresholds set too tight for water level conditions.
> D) Faulty level sensor behaviour.
> E) Canal obstructed due to silt buildup, aquatic growth, blocked culverts, object in canal, causing large hydraulic wedges to be built up at higher flows leading to low or high water levels. | A) Operational issue. Operational issue. Monitor water level and assess if intervention is required which could include decreasing pool inflow or increasing pool outflow.
> B) Operational issue. Assess if intervention is required which could include increasing pool inflow or decreasing pool outflow.
> C) Consider meaning of alarm limits, canal freeboard levels, measuring range of level sensors, turnout supply levels and at what levels monitoring or intervention may be required. Adjust alarm limits if required.
> D) Trend historical water levels too look for signs of un-realistic water level changes e.g. large spikes.
> E) Assess canal condition and clear/clean if needed. |
> | USL1_OLD_AGE | Level sensor has not measured any new values in a predefined amount of time set in the level sensor.
> A) Level sensor is not in water.
> B) Debris/obstruction in level sensor.
> C) Faulty level sensor hardware
> D) Electrical noise interference | A) Check if level sensor is in water.
> Raise water level if it is too low.
> Or if no alarm required when water level is this low, this alarm can be inhibited by the USL1_OLD_AGE_INHIBIT tag (RTU software v5.05????+ required.)
> Or if low water levels need to be measured, consider if water level sensor can be lowered, or an additional submergable micron level sensor is required, or a longer range level sensor can be installed.
> B) Clean level sensor thoroughly. Poke wet rag down micron level sensor ranging tube to clean.
> C) If other causes eliminated, replace sensor. Send faulty sensor to Rubicon for analysis.
> D) Investigate onsite. |
> | USL1_SENS_OOR | A) Raw water level below below configured minimum raw water level (USL1_MIN_READING tag).
> B) Raw water level above configured maximum raw water level (USL1_MAX_READING tag) or above 50mm below micron level sensor reference level.
> C) Level sensor datum not configured correctly causing water level reading to be higher than the site datum (SITE_DATUM tag).
> D) Faulty water level reading resulting in one of the above thresholds being breached. | A) Raise water level if it is too low.
> Or if alarm for water level reading is not needed, lower the minimum raw water level to the required level. It can be set to -1 so this alarm never triggers.
> Or if low water levels need to be measured, consider if water level sensor can be lowered, or an additional submergable micron level sensor is required, or a longer range level sensor can be installed.
> B) Lower water level.
> Of if water levels this high need to be measured, raise water level sensor.
> C) Check level sensor datum is as per model and spacer installed. If externally installed, check level sensor datum is the distance from the Site Datum to the level at which the sensor reads zero.
> D) Inspect and clean level sensor. If issue persists after thorough cleaning, replace sensor. |
> | USL2_OLD_AGE | Possible causes:
> A) Modbus wiring causing no comms to sensor problem
> B) Sensor fault causing sensor not to respond
> C) Sensor power issue
> D) No water level sensor installed.
> E) If analog input level sensor, AI configuration error.
> F) Mapped analog input level sensor problem causing AIx_FAIL_STATUS alarm. | A) Check wiring between level sensor and RTU.
> B) Check sensor is working.
> C) Check voltage supply to level sensor
> D) Install level sensor and set the
> E) Check AIx_ENABLE_STATUS tag is set.
> Check AIx_LEV_MAPPING tag is set to 102 to map the analog input to the downstream water level.
> F) Check corresponding AIx_FAIL_STATUS tag. If set, refer to AIx_FAIL_STATUS alarm info. |
> | USL2_SENS_OOR | A) Raw water level below below configured minimum raw water level (USL2_MIN_READING tag).
> B) Raw water level above configured maximum raw water level (USL2_MAX_READING tag) or above 50mm below micron level sensor reference level.
> C) Level sensor datum not configured correctly causing water level reading to be higher than the site datum (SITE_DATUM tag).
> D) Faulty water level reading resulting in one of the above thresholds being breached. | A) Raise water level if it is too low.
> Or if alarm for water level reading is not needed, lower the minimum raw water level to the required level. It can be set to -1 so this alarm never triggers.
> Or if low water levels need to be measured, consider if water level sensor can be lowered, or an additional submergable micron level sensor is required, or a longer range level sensor can be installed.
> B) Lower water level.
> Of if water levels this high need to be measured, raise water level sensor.
> C) Check level sensor datum is as per model and spacer installed. If externally installed, check level sensor datum is the distance from the Site Datum to the level at which the sensor reads zero.
> D) Inspect and clean level sensor. If issue persists after thorough cleaning, replace sensor. |
> | USL2_SENS_STATUS | Possible causes:
> A) Modbus wiring causing no comms to sensor problem
> B) Sensor fault causing sensor not to respond
> C) Sensor power issue
> D) No water level sensor installed.
> E) Level sensor modbus address is incorrect. 101 = Primary upstream, 102 = Primary secondary, 103 = secondary upstream, 104 = secondary downstream.
> F) If analog input level sensor, AI configuration error.
> G) Mapped analog input level sensor problem causing AIx_FAIL_STATUS alarm. | A) Check wiring between level sensor and RTU.
> B) Check sensor is working. Can try cyclying power to sensor to see if this restores sensor functionality.
> C) Check voltage supply to level sensor
> D) Install level sensor and configure appropriately.
> E) Check level sensor modbus address is correct for level sensor location.
> F) Check AIx_ENABLE_STATUS tag is set.
> Check AIx_LEV_MAPPING tag is set to 102 to map the analog input to the downstream water level.
> G) Check corresponding AIx_FAIL_STATUS tag. If set, refer to AIx_FAIL_STATUS alarm info. |
> | USS_STATUS | Possible causes:
> A) DSL1_SENS_STATUS alarm, sensor not communicating to RTU.
> B) Sensor out of range alarm DSL1_SENS_OOR.
> C) Sensor old age alarm, DSL1_OLD_AGE alarm.
> D) No level sensor enabled or configured.
> E) If EMG site and level sensor is attached to a different site/gate, EMG level sensor sharing not setup correctly or EMG comms not working. | A) See DSL1_SENS_STATUS alarm info.
> B) See DSL1_SENS_OOR alarm info.
> C) See DSL1_OLD_AGE alarm info.
> D) If sensor is installed, enable it via the DSL1_SENS_ENABLE tag.
> E) Ensure EMG sites are communicating and EMG level sensor sharing is configured correctly. |
> | USWLS_COMMS_ERR | A) For PikoMeters, SMB models, SMA-450 models, RTU is not communicating water level to Sonaray board.
> B) For older SlipMeter models, the upstream water level not functioning. | A) Check RTU is configured to tell Sonaray the water level. I.e. Sonaray ENABLE_WL_UPDATE tag is set (1).
> B) Check for upstream water level sensor alarms and corresponding alarm info to resolve. |
>
> Tags with default alarms set