Central Control Specification

Table of Contents

PART 1 - Irrigation Central Control..........................................................2

1.1 Irrigation Central Control Software Subscriptions.......................................2

1.2 Irrigation Central Control Software Compatibility......................................2

1.3 Irrigation Central Control Software Functionality.......................................3

1.4 Virtual Irrigation Controller Access...............................................................5

1.5 Weather-Based Watering.................................................................................5

1.6 Remote Control of the Irrigation Controller..................................................6

1.7 Irrigation Central Control Software on a Self-hosted Server......................6

1.8 Security..............................................................................................................7

PART 2 - Irrigation Central Control Communication Interfaces............8

2.1 Ethernet Connection.........................................................................................8

2.2 Wi-Fi Module....................................................................................................8

2.3 Wi-Fi Antenna Options....................................................................................9

2.4 GPRS Cell Modem............................................................................................9

2.5 GPRS Cell Modem Antenna Options............................................................10

2.6 Ethernet Radio................................................................................................10

2.7 Ethernet Radio Antenna Options..................................................................12

1

PART 1 - Irrigation Central Control

1.1 Irrigation Central Control Software Subscriptions

A. Access to the cloud-based irrigation central control software shall give the user the ability to communicate with and control irrigation controllers from any location over an Internet connection.

B. Access to the irrigation central control software shall be by yearly subscription.

C. The subscription shall be associated with a controller and all controllers belonging to a company shall be set to the same subscription level.

D. The subscription shall determine what irrigation central control software and remote control features a user has access to.

1. The lowest access level shall be available at no charge for one user and one irrigation controller.

a. At the lowest access level, users shall have the ability to use virtual irrigation controller access and to manually turn zones on and off from any web-enabled mobile device.

2. The medium access level shall have a yearly subscription fee and shall allow an unlimited number of users access to one irrigation controller.

a. At the medium access level, users shall have access to all irrigation central control software functions except weather-based watering.

b. At the medium access level, users shall have ability to turn zones on and off, start and stop programs, and initiate rain delays from any web-enabled mobile device.

3. The highest access level shall have a yearly subscription fee and shall allow an unlimited number of users access to one irrigation controller.

a. At the highest access level, users shall have access to all irrigation central control software functions including weather-based watering.

b. At the highest access level, users shall have the ability to turn zones on and off, start and stop programs, initiate rain delays, perform valve diagnostics, geo-locate all devices, and view real-time soil moisture and flow sensor readings from any web-enabled mobile device.

1.2 Irrigation Central Control Software Compatibility

2

A. The user shall be able to access the irrigation central control software via a secure WebSocket over an Internet connection with the most current version of the following web browsers:

1. Mozilla Firefox

2. Google Chrome

3. Safari

1.3 Irrigation Central Control Software Functionality

A. At the medium access level, the irrigation central control software shall include the following end user features:

1. Two levels of user access

a. Company admin user

b. Default user

2. A map-based interface that provides the following functionality:

a. Check the status of any controller, device, or zone

b. Find the location of your controllers, devices, and zones

c. Start/stop a zone

d. Test devices and zones

e. Display a graph for devices and zones

f. Set a rain delay

g. Zoom in/out and move the map view

h. Switch between a street map view, satellite view, and terrain view

i. Set geo-location for any controller, zone, or other device

3. A quick view of the status of all zones with color-coded statuses and descriptions, including:

a. Real-time color-coded status for all zones and programs

b. Complete list of current alarms and messages

c. Ability to delete/clear any current alarm or message

d. Current status and value for all sensing devices

3

4. Add and fully configure all zones and programs, including:

a. Enable/disable zones

b. Change zone type

c. Assign a program

d. Adjust water time

e. Adjust cycle and soak times

f. Program soil moisture sensors

g. Program master valves

h. Program flow sensors

i. Configure mainlines

j. Set all program schedules

k. Set all program configurations including per-program configuration of:

1) Program stop/start conditions

2) Smart watering based on soil moisture sensors

3) Water sources

4) Master valves

5) Water days

6) Water windows

5. Add textual descriptions for all controllers, zones, sensors, flow devices, master valves, points of connection, and mainlines.

a. All descriptions that are set through the irrigation central control software shall be saved and displayed in the controller.

b. These descriptions shall be visible in all appropriate displays and reports, including on the front panel of controllers.

6. Perform the following manual operations:

a. Learn flow

b. Calibrate soil moisture sensors

c. Run zones and programs

4

d. Test devices

7. View soil moisture and run-time graphs for any/all zones and soil moisture sensors

8. Schedule rain delays and pause events

9. Clear rain delays and pause conditions

10. Update controller firmware

B. The medium access level of the irrigation central control software shall have a company administrator’s interface that provides the following functionality:

1. Add/edit/delete users, sites, and controllers

2. Configure users’ access levels

3. Assign users to controllers

4. Maintain company details

5. Configure alert, alarm, and report subscriptions for all users

6. Change or reset all company users’ passwords

C. The medium access level of the irrigation central control software shall have a user administrator’s interface that provides the following functionality:

1. Edit user preferences

2. Change alert, alarm, and report subscriptions

3. View assigned controllers

4. Change password

D. The medium access level of the irrigation central control software shall generate the following alerts/reports as an email or in PDF format for any date range:

1. Water Usage

2. Zones Activity

3. Zone Run Time

4. Moisture Levels

5. Flow Meter Totals

E. The medium access level of the irrigation central control software shall be able to relay all alerts/alarms generated by the controller.

F. The medium access level of the irrigation central control software shall enable users to subscribe to alerts, alarms, and reports.

5

1. Users shall be able to have alerts, alarms, and reports sent by text message, email, or both.

2. Users shall be able to subscribe on a priority basis.

3. Users shall be able to configure what time(s) of day the alerts are received.

4. The company admin shall be able to configure subscriptions for all users.

G. The medium access level of the irrigation central control software shall make alerts, alarms, and reports available on demand.

H. The highest access level of the irrigation central control software shall include all medium-level features and the following weather-based watering features:

1. Connect a weather station and assign it to a controller

2. Configure hydrozone properties

3. Enable zones on the irrigation controller to use weather-based watering

4. Configure programs on the irrigation controller to use weather-based watering

5. Check the calculated ETo amount in the irrigation central control software

6. Display weather station information from the map in the irrigation central control software

1.4 Virtual Irrigation Controller Access

A. Virtual irrigation controller access shall be available through the irrigation central control software.

B. Virtual irrigation controller access shall provide a virtual view of the irrigation controller and shall enable the user to operate the controller just as if he/she were standing in front of it.

1. Virtual irrigation controller access shall match the controller’s display screen in real-time or near real-time as supported by the controller’s connection speed.

2. Virtual irrigation controller access shall support all buttons and/or dial positions available at the controller.

3. Virtual irrigation controller access shall honor controller PIN security as if the user were at the controller.

4. Multiple simultaneous users to the same controller shall be supported on the virtual irrigation controller access.

5. Virtual irrigation controller access shall allow technical support to access any controller when authorized by the customer for customer support purposes.

6

1.5 Weather-Based Watering

A. Weather-based watering shall be available through the irrigation central control software with the highest access level.

1. Weather-based watering shall enable the user to connect a weather station in the area (available in Weather Underground's weather station network) to the irrigation central control software.

2. Weather-based watering shall enable the user to assign a connected weather station to an irrigation controller.

3. Weather-based watering shall apply the real-time weather data from the weather station and the configurable zone properties to a standardized evapotranspiration (ET) equation.

4. Weather-based watering shall calculate an estimated loss of moisture from the root zone, and then the irrigation controller shall use the calculated value to adjust the runtime in order to apply enough water to replace that lost moisture.

5. Weather-based watering shall enable users to configure irrigation controller programs and zones to use weather-based watering.

1.6 Remote Control of the Irrigation Controller

A. Users of the irrigation central control software shall be able to use any web-enabled mobile phone or other mobile device as a remote control.

B. The user's the irrigation central control software account level shall determine the remote control features that are available.

1. At the lowest access level, users shall have the ability to turn zones on and off from any web-enabled mobile device.

2. At the medium access level, users shall have the ability to turn zones on and off, start and stop programs, and initiate rain delays from any web-enabled mobile device.

3. At the highest access level, users shall have the ability to turn zones on and off, start and stop programs, initiate rain delays, perform valve diagnostics, geo-locate all devices, and view real-time soil moisture and flow sensor readings from any web-enabled mobile device.

1.7 Irrigation Central Control Software on a Self-hosted Server

A. The irrigation central control software shall be available on a self-hosted server in the following configurations:

7

1. Pre-installed on solid state server module hardware

a. Intel™ Next Unit of Computing™ (NUC) box

b. Fully web manageable after initial configuration

2. As a virtual machine image suitable for installation in rack mount server environments

a. Requires a minimum of 4GB of RAM, 120GB of disk space, and an Intel i3 class processor or equivalent

b. Fully web manageable after initial configuration

B. The irrigation central control software server shall require access to the Internet to access and display satellite map data.

C. The irrigation central control software server shall require an externally accessible static IP address or hostname if external access is desired:

1. To allow remote desktop and laptop users to access the system, or

2. To allow mobile devices to access the server

D. The irrigation central control software server shall enable users to operate their controllers through a web-based (browser-based) interface, and the controllers are connected through web-based ports (HTML-5 standard, WebSocket Protocol).

1. All traffic is TCP/IP with varying media types (cell, wireless, packet-radio) as needed along the route.

2. The server routes communication, performs maintenance tasks, stores watering logs and information, and enables remote updating and configuration.

E. Networking

1. All communication to/from clients (browsers) and controllers shall be done securely over SSL port 443.

a. Controllers shall be required to talk to the server on that port.

b. There shall be no requirement for opening firewall pinholes or configuring port mapping at an off-site facility, unless outgoing connections on port 443 are specifically blocked.

c. There shall be no special configuration required on the controller side when the controller is connected to an Ethernet port that can get out to the Internet.

F. Software updates shall be available for a yearly fee.

8

1. This fee also covers remote support, as long as remote access is provided for technical support.

1.8 Security

1. Security measures common to cloud-based irrigation central control software and self-hosted irrigation central control software

a. All IP traffic between the web-browser client and the irrigation central control software server shall be SSL-encrypted.

b. Firewall shall be established by Linux kernel IPTABLES (statewise). The only port essential to be opened is 443.

c. Clients (browsers) shall be allowed to remain connected indefinitely or can be logged off and dropped.

d. Controllers shall be able to connect to the IP address of a single assigned irrigation central control software server (programmable).

2. Security measures specific to cloud-based irrigation central control software

a. All data shall be stored on a database server (mySQL) that is not externally accessible other than through activities and reports available through SSL-encrypted web access.

b. External access to the server is available using pre-shared keys by administrative employees only from known IP addresses.

c. Controllers initiate all connections to the server and will not accept any external connections.

d. The irrigation central control software server shall require controllers to be authorized in order to connect to the server.

e. The irrigation central control software server shall generate authorization PINs for controllers that are attempting to connect.

1) The authorization PIN shall be displayed on the controller’s front panel.

2) Company admins shall use the authorization PIN to connect controllers to their company.

f. The irrigation central control software server shall track and manage controller connections using the unique MAC address of each controller.

3. Security measures specific to self-hosted irrigation central control software

9

a. All data shall be stored on a local database server (mySQL). Traffic is internal only to local drive. There is no database access from external connections.

b. Industry standard Apache web security shall be employed. Further access controls shall be supported to manage access via IP, network, or MAC address through the .htaccess facility of Apache.

c. Controllers only listen to the assigned server, only over the WebSocket Protocol (not HTTP), and only through encrypted traffic.

d. Controllers/clients need not respond over the same Ethernet device on the server. In some standalone situations, it may be preferable to have controllers on their own Internet-isolated network.

e. Webmin (a web-based system configuration and management tool) shall be enabled by default on a specified SSL (https) port 10001. Webmin access shall be capable of being disabled from external access (i.e., localhost only) or disabled entirely.

PART 2 - Irrigation Central Control Communication Interfaces

A. The irrigation controllers shall be capable of a single or a combination of communication modes:

1. Ethernet connection

2. Wi-Fi module

3. Cell modem

4. Ethernet radio

B. All irrigation controllers shall be capable of directly receiving, storing, and performing commands uploaded from a remote connection.

2.1 Ethernet Connection

A. The irrigation controller shall have a built-in Ethernet port. No additional hardware shall be required for Ethernet-based communication.

2.2 Wi-Fi Module

A. All Wi-Fi modules shall be installed per manufacturer’s specifications.

10

1. The Wi-Fi module shall come as an option installed in a high capacity wall mount controller cabinet.

2. The Wi-Fi module shall come as an option installed in a pedestal controller enclosure.

B. Power Supply

1. 120 VAC

2. An external adapter is included.

C. Power Input Requirements

1. 9 – 30 VDC (2 W maximum) provided by the irrigation controller

2. DC input

D. Operating temperature range

1. -40°F to 158°F (-40°C to 70°C)

E. Relative humidity

1. 0 to 95% non-condensing, 40% to 60% recommended

2.3 Wi-Fi Antenna Options

A. The following antenna options shall be available for use with Wi-Fi communication:

1. The 3dB “salt shaker” antenna shall be factory mounted on the enclosure unless a site survey of radio signal strength indicated that a different antenna option was required.

2. An omnidirectional high gain antenna shall be available as an option. This antenna shall include brackets for mast-mounting and a waterproof pipe/conduit mount connector. This antenna shall connect to an internal N-type bulkhead. This antenna shall require a compatible LMR-400 low loss cable.

3. A directional high gain antenna shall be available as an option. This antenna shall include brackets for mast-mounting. The antenna connects to the internal N-type bulkhead. This antenna shall require a compatible LMR-400 low loss cable.

2.4 GPRS Cell Modem

A. All GPRS cell modems shall be installed per manufacturer’s specifications.

1. The GPRS cell modem shall come as an option installed in a high capacity wall mount controller cabinet.

11

2. The GPRS cell modem shall come as an option installed in a pedestal controller enclosure.

B. Cell modems operate on the AT&T network and require a yearly data fee.

C. Power and communication shall be supplied to the cell modem by the top 5-pin terminal block on right end of the controller board on the irrigation controller.

D. Operating temperature range

1. -22º to +158º F (-30º to +70º C)

E. Relative humidity

1. 20% to 90% non-condensing

2.5 GPRS Cell Modem Antenna Options

A. The following antenna options shall be available for use with cell modem communication:

1. The 3dB “salt shaker” antenna shall be factory mounted on the enclosure unless a site survey of radio signal strength indicated that a different antenna option was required.

2. An omnidirectional high gain antenna shall be available as an option. This antenna shall include brackets for mast-mounting and a waterproof pipe/conduit mount connector. This antenna shall connect to an internal N-type bulkhead. This antenna shall require a compatible LMR-400 low loss cable.

3. A directional high gain antenna shall be available as an option. This antenna shall include brackets for mast-mounting. The antenna connects to the internal N-type bulkhead. This antenna shall require a compatible LMR-400 low loss cable.

2.6 Ethernet Radio

A. The customer shall ensure that a Radio Site Survey is performed by a certified surveyor before ordering or installing radio equipment.

1. The installation contractor shall demonstrate that the installation and radio network performance meets or exceeds all specifications and site survey results.

B. All Ethernet radios shall be installed per manufacturer’s specifications.

1. The Ethernet radio shall come as an option, installed in a high capacity wall mount controller.

12

2. The Ethernet radio shall come as an option, installed in a pedestal controller enclosure.

3. The Ethernet radio shall come as an option, installed in a separate wall mount cabinet.

a. Every Ethernet radio configuration shall require at least one radio that is configured as a Gateway.

C. Transmitter

1. Frequency Range: 902 to 928 MHz

2. Output Power: 5 mW to 1 Watt

3. Data Link Range: 60 miles, Clear Line of Sight

4. Modulation: 2 level GFSK

5. RF Data Rate: 115.2 kbps Standard Speed, 153.6 kbps High Speed

6. Occupied Bandwidth: 230.4 kHz

7. Hopping Patterns: 15 per band, 105 total, user selectable

8. Hopping Channels: 112

9. Frequency Zones: 16 zones, 7-8 channels per zone

D. Receiver

1. Sensitivity:

a. -108 dBm, at Standard Speed, 1x10-4 BER

b. -104 dBm, at High Speed, 1x10-4 BER

2. IF Selectivity: 20 dB at fc ±230 kHz

E. Data Transmission

1. Error Detection: 32 bit CRC, retransmit on error

2. Data Security: AES 128 bit encryption and FHSS Technology

3. Data Throughput: 80 kbps Standard Speed, 115.2 kbps High Speed

4. Serial Data Interface:

a. RS232/RS422/RS485 Programmable

b. 2x 9-pin D-sub (DE-9) male connectors

5. Ethernet Data Interface:

a. 802.3, TCP, UDP, DHCP, ICMP, ARP, Multicast, TFTP, DNP3 over TCP

b. 1x RJ-45, 10/100 Base T, Auto Crossover

13

F. Environment

1. Operating temperature: -40° F to +167° F (-40° C to +75° C)

2. Operating Humidity: 0 to 95%

G. Power

1. Operating Voltage

a. +6 to +30 VDC

2. Power Input Requirements

a. The Ethernet radio shall come standard with a 5-pin connector that plugs into one of the 5-pin terminal blocks on right end of the controller board available on compatible irrigation controllers.

H. Radio Network

1. Maximum number of radios in a network:

a. One Gateway radio and up to 34 Endpoint radios, for a total of 35 radios

b. If a Repeater is required in the network topology, the maximum number of radios is 15, including Repeaters

2. Maximum number of Repeaters between a Gateway and an Endpoint: 1

3. Maximum distance between radios: 1 mile

4. Required Noise Margin: The Signal shall be at least 20 dB higher than the Noise (Delta)

5. Each radio unit shall have a unique static IP (internet protocol) address assigned to it.

2.7 Ethernet Radio Antenna Options

A. The following antenna options shall be available for use with Ethernet radio communication:

1. The 3dB “salt shaker” antenna shall be factory mounted on the enclosure unless the site survey of radio signal strength indicates that a different antenna option is required.

2. An omnidirectional high gain antenna shall be available as an option.

a. This antenna shall include brackets for mast-mounting, waterproof pipe/conduit mount connector.

b. This antenna shall connect to an internal N-type bulkhead.

14

3. A directional high gain antenna shall be available as an option.

a. This antenna shall include brackets for mast-mounting.

b. The antenna shall connect to the internal N-type bulkhead.

B. High Gain Antenna Installation

1. Each antenna shall have 10 feet of vertical separation from other antennas.

2. All antennas shall be polarized the same.

3. Lightning arrestors shall be installed according to manufacturer installation guidelines and precautions.

4. The antenna shall be grounded appropriately following all manufacturer installation guidelines and precautions.

5. The antenna shall require a compatible LMR-400 low loss cable.

6. All antenna connections shall be weatherproofed.

7. All connections shall have strain relief.

8. All cables shall be secured with tie wraps.

REV 5.5.2023

15