==== System ====
{{indexmenu_n>810}}
The System tab provides meta data, performance metrics, and user defined settings individual ezeio controllers. The window is divided in half with System information on the left and System settings on the right. We recommend naming the each ezeio and setting the time zone, all additional system settings are optional.
=== System Settings ===
**System name**
**Time zone**
Listed alphabetically by, **continent or ocean**, then **city** (preceded by state in some cases). Also shown is the hour/s ahead or behind UTC.
**Note**
This text is displayed in the Controller table on the on the Manage level. It can also be sent in alarm messages by using the Message template tag [EZENOTE].
**System location**
The displayed location of an ezeio is determined by one of the four methods detailed below. A GPS receiver can be purchased from eze System, Inc. if high accuracy is required for mobile applications.
|**Method**||**Accuracy**|
|Cell tower proximity | Auto location default __if no GPS receiver connected__ | 0-5 miles|
|IP location (Ethernet) | Auto location default __if no GPS & no cellular connection__ | Region|
|GPS sensor | Auto location default if connected| 1 to 10 meters |
|Manual location | Overrides Auto location defaults if box is unchecked | user defined |
**Condition to enable fast log**
The default logging rate of an ezeio MkII is 10 minutes. Service upgrade options allow for data logging rates as fast as 5 seconds. This provides high data resolution, but also create a massive amount of data to sort through. This feature allows fast logging to be selective based on conditions. For example; you may wish to closely monitor water quality readings above a specific flow rate or only during business hours. //This feature utilizes the same Expression engine employed for Fields and alarms.// Simply enter an expression like f(3) > 15 or sch(2) and __all Fields__ with Logging intervals set higher than 10 minutes will begin recording at their selected rate. They will continue fast logging as long as the condition is true.
**Low-power hibernation mode**
The ezeio MkII is very efficient and under normal operation the average power consumption is less than one Watt for the ezeio itself. For some solar powered installations the quality and quantity of sun light can vary dramatically, making even a 1 Watt draw unsustainable.
The hibernation feature reduces the ezeio's __average__ power consumption to less than 0.1W. Note that the peak power requirement does not change.
Hibernation negates many of the ezeio's capabilities such as automation and alarms.
To enter hibernation, the server must send a command to the ezeio telling it to start a hibernation cycle. The ezeio will wait until the next 10-minute data log had been collected, and then power down.
Note that no processing is taking place while the ezeio is powered down.
Every 10 minutes, the ezeio will power up for a few seconds to collect a new data sample and then automatically power down again. When one hour has passed since the hibernation command was issued, the ezeio will power up normally and connect to the servers and upload the collected data. This completes a hibernation cycle.
To continue hibernating, the server must issue a new hibernation command to the ezeio. This server-driven strategy is design to avoid any system failure or misconfiguration that would cause the ezeio to become unavailable by continuously hibernating. Note that the ezeio must be able to reliably communicate for hibernation to work. If the ezeio can't connect at least once every hour, it will exit hibernation and continue to run normally.
The following hibernation modes are available
| Normal Mode | No hibernation commands are sent. If already in a hibernation cycle, the ezeio should connect normally within 1 hour. |
| 1 Hour Hibernation | The servers will issue a hibernation command automatically each time the ezeio checks in. |
| Controller Request | The ezeio can issue a request using special drivers or the script command [[ezeio2:scriptref:requesthibernate|requestHibernate]]. If set to Controller Request, the servers will grant the request, and issue the hibernation command. |
**Important notes regarding hibernation**
* Local logic (alarms, scripts etc) are NOT running during hibernation.
* Communication with the ezeio during hibernation is not possible.
* When cancelling hibernation, it may take up to 1h for the ezeio to reconnect.
* Power will flow from the barrel jack to the 'batt' and +V terminals during hibernation.
* +5V and any outputs will be powered off during hibernation.
=== Hardware Settings ===
**Pulse threshold**
The default __auto__ setting will work to read most pulse outputs. This setting finds the average voltage of the pulses emitted by the connected meter and that average is used as the threshold. You should not change this setting unless you know the voltage range of the pulses. If you have trouble registering a pulse on the ezeio, review the documentation provided by the meter manufacture to confirm the wiring and whether an excitation voltage is required.
**Pulse debounce**
Dry contact pulse mechanisms can bounce when making contact generating multiple pulses. To eliminate these unwanted/erroneous pulses we apply a filter that eliminates additional pulses occurring within a specified window of time. The default filter is 5 milliseconds. Check your meters documentation to see if the pulse rate and expected flow require the use of a different debounce filter.
=== Modbus TCP settings ===
**Server & Client ports**
Default setting is 502 on both server and client. This is the standard port number established by Modbus.org. To disable the Modbus/TCP server, set the server port to 0 (zero).
=== Ethernet settings ===
**IP**
The local IP of this ezeio device. Leave blank to use DHCP automatic assignment.
**DNS**
Only significant if the IP is set. This should be the IP address of a valid DNS server.
This can be left blank if the ezeio should only use the Ethernet port for LAN communication (Modbus/TCP) and not for server communication.
**Gateway**
Only significant if the IP is set. This should be the IP address of the local gateway device.
This can be left blank if the ezeio should only use the Ethernet port for LAN communication (Modbus/TCP) and not for server communication.
**Network mask**
Only significant if the IP is set. IPv4 network mask for the local network.
For Modbus/TCP, only /24 or smaller networks are supported. The last octet is used in the driver section to address the Modbus/TCP servers.
=== Unregister ezeio ===
The Unregister ezeio button removes an ezeio from the account it is registered to. It can then be added to another account. Since an ezeio can be moved between groups within an account, by simply dragging and dropping, this feature is only needed when the new location desired is outside of the current account. Deleting the ezeio has no effect on its configuration or services. Links to dashboard Widgets and reports in the group will be broken.
Once deleted, you will need the serial number and registration code to add the ezeio to another account. These are located on the left side of the ezeio and also in the Identity section of the System information.
==== System information ====
This section occupies the left side of the System window. It is mainly informational, but there are some tools available to users with **Edit ezeio** privileges.
==== Identity ====
**Serial** - The serial of an ezeio is factory set and cannot be changed.
**Name** - The ezeio's name is user defined and can be changed by any user with **Edit ezeio** privileges'.
**Registration code** This code is factory set and cannot be changed. The reg code is used only when registering for a new account or adding an ezeio to an existing group/account.
**Most resent comm** - The date and time (local web browser time) of the last communication with the serve is displayed. The time elapse since this contact is also displayed for an "at a glance" reference of comm status. The elapse time is displayed as the most relevant unit/s of time. Starting with seconds (s) and progressing to months and days (mo, d).
**Uptime** - This is the elapse time since last reset/reboot.
__Reboot__ - Clicking "__Reboot__" will bring up a dialog box to confirm your intention and explain the result. The result is similar to power cycling the ezeio. It will immediately reboot. After rebooting the ezeio will begin the process of reconnecting, through the onboard cellular modem or through the local network via Ethernet port.
**Supply voltage** This displays 3 voltage readings. First is the DC in (barrel jack at the top right of the ezeio). Next is the Batt connection (far right on the green screw terminals). Last is the 5 volt supply (center of the green screw terminals). If the barrel jack is not used, disregard the first reading.
**Firmware version** - The firmware version represented by a date code ending with a 2 digit code. The format is __YYMMDD__xx.
__Update__ - Clicking on the __Update__ link, brings up a dialog box for selecting a firmware version. Selecting a firmware version to see the Release notes. The release notes will detail the added features included in this version. If you wish to proceed with the update, click the Update firmware button, otherwise, click Cancel. Updating firmware is optional in most cases and eze System does not force mass firmware updates into customers deployed ezeios. You may be instructed by eze System support or your reseller to update firmware to take advantage of new features.
==== Cellular information ====
All data shown in this section is informational.
**Signal (RSSI)** - Icons here indicate the connection type and signal strength. Two connected links with a letter R, indicates for connected and roaming (normal state for an ezeio). An X icon indicateThe familiar increasing, green 5 bar graph indicates optimal signal strength.
|| | Icon | Indication | Discription |
|Link|{{ezeio2:userinterface:configuration:roaming.png?direct|}} | Connected & Roaming | This is the normal connection and service type for an ezeio |
|Link|{{ezeio2:userinterface:configuration:link.png?direct|}} | Connected | Connection active in local service area |
|Link|{{ezeio2:userinterface:configuration:searching.png?direct|}} | Searching | The ezeio is searching for cellular service |
|Link|{{ezeio2:userinterface:configuration:x.png?direct|}}| No connection | Failed to connect to cell tower |
|Received signal|{{ezeio2:userinterface:configuration:strike.png?direct|}} | No connection| No network found or signal too weak |
|Received signal|{{ezeio2:userinterface:configuration:1_bar.png?direct|}}| Weak signal | Connected, but signal strength is marginal |
|Received signal|{{ezeio2:userinterface:configuration:5_bars.png?direct|}} | Strong signal | Connected, excellent signal strength |
|Signal level|{{ezeio2:userinterface:configuration:dbm.png?direct|}} | Strength of received signal | Lower negative number is stronger signal. Range: -100 dBm = 0%, -30 dBm = 100% |
**SIM ICCID** - This 19 digit number is the SIM cards serial number.
**Hardware IMEI** - (International Mobile Equipment Identity) The Model information following the IMEI identifies the modem type and version.
**Subscriber IMSI** - (International Mobile Subscriber Identity) The Network number following the IMSI, is the combined MCC (Mobile Country Code) & MNC (Mobile Network Code) which identify the country and carrier. Depending on the country, there may be agreements with multiple carriers. This means the MNC may change whether the unit is stationary or mobile.
**PIN status** -
**IP address** -
**Data used** -
==== Ethernet information ====
**IP address** -
**Data used** -
==== Logic status ====
**Input setting** -
__Reset logic__ - Clicking "__Reset logic__" will bring up a dialog box to confirm your intention and explain the result. Registers, Fields, counters, will be cleared. The restarting sequence allows data to populate registers and fields before logic and automation, dependent on those values, restart. Alarms that were in alarm state and who's conditions are still true will retrigger.
**Button status** - The button on the top of the ezeio can be pressed during start up for different effects.
==== Script status ====
**User script** -
**Modbus** -
**SDI-12** -
**CAN** -
**Core** -
==== System log ====
The system log tracks changes in connectivity between the ezeio and the eze.io servers. Time stamps are shown in UTC. Below is a list of system log details and their explainations.
| **Type** | **Details** | **Explanation** |
| Connection | CONNECT CELL | Connection established via cellular network |
| Connection | CONNECT ETH | Connection established via Ethernet |
| Connection | DISCONNECT CELL [reason] | The cellular connection was terminated. |
| Connection | DISCONNECT ETH [reason] | The Ethernet connection was terminated. |
| Connection | LINK-LOSS [reason] | The communication was lost / timed out |
| Boot | POR | Power-on reset |
| Boot | EXT,POR Down:1m 21s | External loss of power followed by elapse time |
| Boot | EXT,POR [SLEEP] Down:22s | followed by elapse time |
| Boot | SW | Software caused a reset |
| Boot | SW Down:1s | Rebooted, followed by elapse time |