Alert Name | Type | Description | Notes |
Two wire state change | Notice | NLP's 2-Wire state has changed. Possible states include On, Off, Short Finding & Leak Finding. | This is most helpful to prevent a controller from remaining in an unintended mode accidentally. All modes besides "On" will prevent irrigation. |
Water engine state change | Notice | NLP's Controller / Water engine state has changed. Possible states include Auto, Manual, Paused, 2-Wire Non-Operational & Raining (requires rain sensor). | This is a good general "FYI" notice to keep track of controller behavior. |
Water engine station wilting point | Warning | 1 or more MAD stations has reached wilt point. | Only relevant for MAD-based stations. Use the NLP's Simulation to predict when a station will reach wilt point (uses historical ET). |
Water engine station error | Error | 1 or more stations did not activate when called to run (Station Error 3000). | Station Errors are shown on the controller dashboard. The NG will provide a specific reason for station start issues. |
Water engine flow valve error | Error | Master valve decoder failure. | This notice should always be enabled when adding a master valve, booster, or pump start relay. |
Water engine flow rule state change | Warning | For any active flow rule (Flow Deviation, Unscheduled Flow, No Flow), state has changed from OK to error state / vice-versa. | Enable this notice to receive notice of any flow-related issues. Unless Automatic Action is enabled, flow rule states are notice-only. |
Two wire error | Error | A 2-Wire error has been triggered. Possible errors include 2-Wire Time out (1000), 2-Wire Communication Error (1001), 2-Wire Not Operational (1002), 2-Wire Load Too High (1003). | This is a recommended notice to enable. In cases of a dead short (1003 for extended time), a customer may recieve a high volume of notices due to the controller attempting to "work through" the short. Tucor recommends temporarily marking the alert as passive if this occurs. |
Logic engine action error | Error | Logic engine execution has failed. | Contact Tucor. |
Invalid IO Config | Error | IO configuration has been misapplied. I.e. Sensor decoder has been configured has an output decoder (NG). | Contact Tucor. |
Program state | Notice | Program state has changed. Possible program states include Idiling, Started, Inactive. | A user will recieve an alert any time a program starts & stops. This can result in a high volume of notices. |
Program not completed | Notice | A program has not completed it's entire runtime in a given water window. | Good for users with tight water windows, long run times or that use ET, Water Budget, or MAD to determine if irrigation completed as intended. Assuming water window cannot be extended, use the NLP's Auto program strategy to maximize station run. |
Start time overrun | Notice | A program with stop time override enabled has extended past the stop time. | This is only relevant for customers using "override stop time". This notice may be helpful if you use a 24-hour water window & would like notice if your schedule extends beyond 24 hours. |
Overlapping program | Notice | Two or more programs will overlap run. | This notice is helpful for customers with limited hydraulic capacity that cannot overlap programs. The NLP's max station run & hydraulic logic are designed for this purpose. The NLP can run up to 40 stations simultaneously. |
Interface / controller online state change | Warning | NLP's state has changed from online to offline or vice versa. | Recommended to enable. Users that see this often should resolve signal issues or check power supply for "brown-outs". The NLP will run offline. |
ET source change | Notice | NLP ET source has changed. There are 5 total possible sources. | This is most helpful to determine when the NLP has reverted from a live ET source to Historical ET. The NLP automatically reverts to a Historical ET source after 3 hours of no connection. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article