Doc Number: ARA2023-00003 Rev A Date: March 30, 2023
Release Overview
The Arable Mobile 4.7.0 release is introducing a new cross-sites view of the water balance of your fields with a breakdown into its components (evapotranspiration, precipitation data and irrigation). A new ability to track and record irrigation events is part of this upgrade as well as to set a deficit irrigation schedule per growth stages.
The Water Insights feature also offers a view of the field's soil moisture level including available water content that can be mapped to field capacity, permanent wilting point and refill thresholds. A new depth of interest selection option is added here.
Water Insights is available for both Mark 2 & Mark 3 users as an add-on subscription and is using GEMs pressure switches and Sentek soil probes in the field. Contact your Sales Representative or Customer Success to get started.
We hope you will enjoy this new release. We always welcome your feedback through Customer Success (support@arable.com) or via your account manager.
|
Date |
March 30, 2023 |
|
Scope |
General Release |
|
OS Support |
Android 10, 11, 12, 13; iOS 15, 16 |
|
Language Support |
English; Mobile: English, Spanish, Portuguese, French, German, Ukrainian and Polish |
|
Screen Size & Resolution |
Minimum 540 x 960 pts screen resolution and 4.5” screen size |
|
Type of Release |
Minor Release |
|
Version |
iOS 4.7.0, Android 4.7.0 |
Change Log
New Features
|
Description |
|
Water Insights Single Site View: Deep dive into a site's water usage and demand displayed in tabular data. Displays are across daily, weekly, and growth stage aggregations. Key metrics: Water balance change, Replacement ETc, Proximity to Refill Threshold, Heat Stress Hours, Irrigation Runtime Hours, and Precipitation Measurements can be selected to be displayed 3 at a time. Configuration Completeness For all measurements to populate an account must have the following preset parameters configured in the Arable Web App:
Precipitation The amount of rainfall on the site for the measurement period. If multiple Mark deployments were associated with the site for the same period, the rainfall measurements are averaged. Replacement ETc The percentage of ETc that you would like to irrigate. It can be configured by clicking on the three dots on the right hand side of this modal. For instance, in order to irrigate to replace 80% of your observed ETc you may set the value for your current growth stage at 80. Values between 0-200 are accepted. Water Balance Change A calculation of the precipitation plus irrigation minus crop evapotranspiration over the duration selected. Heat Stress Hours The accumulated number of daylight hours during which the air temperature is above the GDD max temperature threshold for the crop at the site for the period selected. If the GDD max temperature threshold is not defined for the crop in the system, then a default of 96°F is used. Irrigation Runtime Hours For the last 7 days: If sites have received over 21 hours of irrigation they are colored dark blue. If they have received between 5 and 20 hours they are colored blue, and if they have received 4 or less hours they will be colored light blue. Sites that do not have pressure switches will not be included in the status bar. Proximity to Refill Threshold The distance to the soil moisture refill point for a site expressed as a percentage. This equals the mean soil moisture for the measurement period (as a percentage of field capacity) minus the refill threshold. This will appear blank if no soil probe is attached or if the soil moisture measurement has not been configured in the soil moisture graph below. This value is configured in the Water tab for each site with a soil moisture probe. |
|
Water Insights Multi-Site View: Comparative view of fleetwide sites water usage and demand displayed in tabular data. Displays are across 7 day accumulations. Accessible under List view. Key metrics: Irrigation to replace ETc, Last irrigation runtime, Proximity to Refill Threshold Measurements can be selected to be displayed 3 at a time. Note: the measurements of the Multi-site views will only render if the configuration completeness steps of the single-site are met first. Irrigation to Replace ETc The irrigation system runtime needed to meet the defined Replacement ETc. The Replacement ET % is set in the Arable Web Water page, Water Balance visual. It will default to 100% if a Growth Stage is defined for the measurement period and otherwise it will be 0%. This value will only populate if a flow rate for a Gems Pressure Switch has been configured. Last Irrigation Runtime The date and amount when an irrigation event was last observed using data from the pressure switch or from data which was manually entered on the Water tab for that site. Proximity to Refill Threshold The distance to the soil moisture refill point for a site expressed as a percentage. This equals the mean soil moisture for the measurement period (as a percentage of field capacity) minus the refill threshold. This will appear blank if no soil probe is attached or if the soil moisture measurement has not been configured in the soil moisture graph below. This value is configured in the Water tab for each site with a soil moisture probe. |
Defect Fixes
|
Description |
|
Previously it could have taken 6-7 seconds until all the alerts changed state after the user marked All Notifications as Read in Mobile. This is now imminent. |
|
The drop-down label for Spray Timing in Spanish has been changed from Ventana de riego to Ventana de Spray. |
Known Issues
|
Description |
|
For customers that are trying out our new Water feature on site-view, the GEMS pressure switch needs to be selected on the analog port in order to capture irrigation runtime data from the drip irrigation line. This means that there will be no wind direction provided in the user interface even if you have an anemometer connected. However, you can still validate and see wind speed data from the Bridge pulse port. |
|
In the new Water Views, after a Gems sensor is configured the values for the readings will display in the Multi-site View as runtimes. However, the first Irrigation amount will not be added to the Water Balance or Irrigation details measurements in the Single Site views. All irrigation events after the first event will be recorded in both the Single Site views as amounts and in the Multi Site views as runtimes. |
|
For the Single Site and Multi Site views of Water, the Irrigation to Replace ETc value will not populate if no Irrigation event has taken place within the previous seven days. |
|
For the Multi-site Views, the Last Irrigation Runtime is displaying the hours for the last irrigation event that took place. If a given day had multiple irrigated events, the display would only be of the most recent one, not the aggregation for the day. |
|
For Irrigation events, if a flow rate was improperly configured there is no way to go back and correct previous readings with a new flow rate to reflect accurate applied irrigation measurements. |
|
If the Mark anemometer is not detecting any wind, then this is shown in the user interface as “--” wind in the Map and List. In the Spray Timing details page such hours are falling back to remote sensed wind. We will improve this in a future release and show “0” wind speed instead. |
|
The max/min temperature readings on the Weather list, Daily tab show observed data only for today, while the individual location details screens for Heat Spikes and Frost Events take into account both observed and forecasted hours for the current day. |
|
The remote-sensed temperature data can show a difference between hourly and daily max/min temperature, as they are measured slightly differently. For the remote-sensed enhanced forecast, the hourly values represent the projected temperature at that forecast time (usually top of the hour). However, the max/min temps often occur within the hour and the daily forecast products capture that. There is currently no short-term solution for this discrepancy. |
|
The local Mark max/min temperature for the hour is taken as the max/min of all 5-min interval readings during that hour. Meanwhile, the current temperature is the average for the last hour, creating a discrepancy between the two values during weather alerts. We are investigating whether relying on a 5-min interval for Tmin/Tmax is vulnerable to noise, and if so, will change this algorithm. |
|
Terms & Conditions are e-mailed in English, regardless of what language is registered. A link to alternative languages is provided in the email. |
|
The alerts in the My Alerts log are shown in English even if another language is selected in Arable Mobile. |
|
Push notifications are presented based on the language configured on the phone and not the language set in Arable Mobile. |
|
When clicking on a notification, the app will navigate to either the Heat Spikes or Frost Events screens, but won’t open the hourly records to point out the current-hour row. |
|
Even for a site in which a device is in “Excluded” state, it will generate a "Delayed Data" alert for this site if more than 12 hours without sync. |
|
For a site user, alerts are not displayed as per the team selection and unable to be marked as read when a team is selected in Mobile. |
|
The Mobile App is showing the deployment name based on browser rather than local device time. |
|
In certain conditions, the daily tdew is wrongly aggregated and does not match the hourly values. |