Release Notes — November 24, 2016

Product Manager

Created: ; updated: .

Improvements to Monitor

We have made some improvements to the appearance of Monitor to improve the ease of use and readability of information displayed in Monitor Cards. Several small changes have been made to the way the cards appear, and some small but significant improvements have been made to the way the cards work and operate when being loaded, expanded and collapsed.

Improvements to Schedule

Block 'Unhealthy' units from being scheduled

When you are creating a new schedule, you will now be prevented from placing items in a schedule where the equipment is considered to be unhealthy. The specific criteria that will prevent scheduling are:

  • Devices that have errors such as communications problems between the field unit and the actuator, pump or value
  • Field units that have low battery levels. The state of charge must be above 60%

Reduce time to fail on scheduled items

For iRiser style linear actuator based irrigation items that have a shorter travel time (less than 2 minutes) the time the scheduling engine will wait before marking the unit as failed has been reduced to 5 minutes. This allows for more recovery and auto-skip time and helps ensure a schedule will recover by moving on to the next item before the previous item has closed and risking over-pressure shutdown of the pump. To take advantage of this, please ensure you have the 'auto-skip' feature selected in your personal settings in Observant Global.

Scheduling: better recognition of jammed actuators that failed to open

In some instances, the scheduling system did not properly recognise a failure due to current overload when opening a scheduled item. This would incorrectly mark the item as open, even though it was not. The system will now more accurately recognise an item that fails to open due to current overload and mark the item as having failed to open.

Display common failure causes in Schedule

We have improved the description of the failure causes in items that fail in order to better explain the reason why the item failed to be scheduled.

Have more questions? Submit a request
Powered by Zendesk