ezeio2:userinterface:configuration:system

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
ezeio2:userinterface:configuration:system [2022-03-28 16:56] – andrehezeio2:userinterface:configuration:system [2025-05-07 22:07] (current) – [System log] andreh
Line 40: Line 40:
 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. 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.+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:+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. | | 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. | | 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 requestHibernate. If set to Controller Request, the servers will grant the request, and issue the hibernation command. |+| 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. |
  
 <WRAP center round alert 80%> <WRAP center round alert 80%>
Line 70: Line 70:
  
 **Server & Client ports** **Server & Client ports**
-Default setting is 502 on both server and client. This is the standard port number established by Modbus.org+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 === === Ethernet settings ===
  
 **IP** **IP**
 +The local IP of this ezeio device. Leave blank to use DHCP automatic assignment.
  
 **DNS** **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** **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** **Network mask**
 +Only significant if the IP is set. IPv4 network mask for the local network.
  
-**Ethernet ping interval**+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.
  
-=== Delete ezeio === +=== Unregister ezeio === 
-The delete 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. +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.   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.  
Line 119: Line 127:
 || | Icon | Indication | Discription | || | 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:roaming.png?direct|}} | Connected & Roaming | This is the normal connection and service type for an ezeio |
-|Link|{{ezeio2:userinterface:configuration:link.png?direct|}}||  | +|Link|{{ezeio2:userinterface:configuration:link.png?direct|}} | Connected | Connection active in local service area | 
-|Link|{{ezeio2:userinterface:configuration:searching.png?direct|}}||  |+|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 | |Link|{{ezeio2:userinterface:configuration:x.png?direct|}}| No connection | Failed to connect to cell tower |
-|Signal|{{ezeio2:userinterface:configuration:strike.png?direct|}} | No connection| No network found, signal to weak | +|Received signal|{{ezeio2:userinterface:configuration:strike.png?direct|}} | No connection| No network found or signal too weak | 
-|Signal|{{ezeio2:userinterface:configuration:1_bar.png?direct|}}| Weak signal | Connected, but signal strength is marginal | +|Received signal|{{ezeio2:userinterface:configuration:1_bar.png?direct|}}| Weak signal | Connected, but signal strength is marginal | 
-|Signal|{{ezeio2:userinterface:configuration:5_bars.png?direct|}} | Strong signal |  | +|Received signal|{{ezeio2:userinterface:configuration:5_bars.png?direct|}} | Strong signal | Connected, excellent signal strength | 
-|Sensitivity|{{ezeio2:userinterface:configuration:dbm.png?direct|}} | Strength of signal | Lower negative number is stronger signal. Range: -100 dBm = 0%,  -30 dBm = 100%  |+|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. **SIM ICCID** - This 19 digit number is the SIM cards serial number.
Line 166: Line 174:
  
 ==== System log ==== ==== 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.+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 explanations.
  
 | **Type** | **Details** | **Explanation** | | **Type** | **Details** | **Explanation** |
-| Connection | CONNECT CELL | Connection established via cellular network | 
 | Connection | CONNECT ETH | Connection established via Ethernet | | Connection | CONNECT ETH | Connection established via Ethernet |
-| Connection | DISCONNECT CELL [reason] | The cellular connection was terminated. |  +| Connection | CONNECT CELL | Connection established via cellular network | 
-| Connection | DISCONNECT ETH [reason] | The Ethernet connection was terminated. |  +| Connection | DISCONNECT ETH | The Ethernet connection was terminated. |  
-| Connection | LINK-LOSS [reason] | The communication was lost / timed out | +| Connection | DISCONNECT CELL ''[reason]'' | The cellular connection was terminated.| 
 +| | ''TMAIN'' - Modem stopped responding || 
 +| | ''TLINK'' - No heartbeat message from servers received in 10 minutes || 
 +| | ''TCONN'' - No acknowledgement received from the servers || 
 +| | ''ETH'' - The Ethernet connection was activated || 
 +| | ''ATT'' - The cell modem was disconnected from the cell network || 
 +| | ''SOCK'' - The TCP socket connection was closed from the remote side || 
 +| | ''CELLOFF'' - The cell modem was powered off || 
 +| Connection | LINK-LOSS ''[reason]'' | The communication was lost / timed out |  
 +| | ''VERSION'' - The firmware ID is invalid || 
 +| | ''SERIAL'' - The serial number is not recognized || 
 +| | ''FINGERPRINT'' - The security certificate is invalid || 
 +| | ''CLEAN'' - The link changed (Eth->Cell or Cell->Eth) and the old link status was erased || 
 +| | ''ERROR'' - Registration could not complete || 
 +| | ''BADDATA'' - Received data was corrupted/incomplete || 
 +| | ''BADKEY'' - A step was skipped during registration || 
 +| | ''MSGLEN'' - Received data had an invalid size || 
 +| | ''MONITOR'' - The server could not allocate necessary resources || 
 +| | ''TCPEOF'' - More data was expected, but did not arrive || 
 +| | ''TIMEOUT'' - No new data received in 10 minutes || 
 +| | ''SHUTDOWN'' - The server was shut down/restarted || 
 +| | ''USER'' - The user sent a disconnect request ||
 | Boot | POR | Power-on reset | | Boot | POR | Power-on reset |
 | Boot | EXT,POR Down:1m 21s | External loss of power followed by elapse time | | Boot | EXT,POR Down:1m 21s | External loss of power followed by elapse time |
Line 179: Line 207:
 | Boot | SW | Software caused a reset | | Boot | SW | Software caused a reset |
 | Boot | SW Down:1s | Rebooted, followed by elapse time |   | Boot | SW Down:1s | Rebooted, followed by elapse time |  
- + 
  • ezeio2/userinterface/configuration/system.1648486610.txt.gz
  • Last modified: 2022-03-28 16:56
  • by andreh