ezeio2:introduction:start

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
Next revisionBoth sides next revision
ezeio2:introduction:start [2021-09-17 17:47] andrehezeio2:introduction:start [2021-09-24 22:01] – ↷ Links adapted because of a move operation andreh
Line 121: Line 121:
 There are eight (8) discrete inputs on the ezeio. Each input can be individually configured to monitor voltage, current, resistance or pulses. The configuration is done via the web interface at https://eze.io. There are eight (8) discrete inputs on the ezeio. Each input can be individually configured to monitor voltage, current, resistance or pulses. The configuration is done via the web interface at https://eze.io.
  
-More information about connecting to the inputs is available [[ezeio2:installation:inputs|here]].+More information about connecting to the inputs is available [[ezeio2:connections:inputs|here]].
  
 === Discrete outputs === === Discrete outputs ===
Line 151: Line 151:
 Several devices can be connected at the same time on the same Modbus/RTU cable. The protocol is very robust, uses low cost bulk wires and can be used in noisy environments and over long distances. Several devices can be connected at the same time on the same Modbus/RTU cable. The protocol is very robust, uses low cost bulk wires and can be used in noisy environments and over long distances.
  
-More information about Modbus/RTU is available [[ezeio2:installation:modbusrtu|here]].+More information about Modbus/RTU is available [[ezeio2:connections:modbusrtu|here]].
  
 === Modbus/TCP === === Modbus/TCP ===
Line 159: Line 159:
 The ezeio supports standard Modbus/TCP as both a 'server' and a 'client'. There are multiple drivers available for various devices. The ezeio supports standard Modbus/TCP as both a 'server' and a 'client'. There are multiple drivers available for various devices.
  
-More information about Modbus/TCP is available [[ezeio2:installation:modbustcp|here]].+More information about Modbus/TCP is available [[ezeio2:connections:modbustcp|here]].
  
 === CAN === === CAN ===
Line 199: Line 199:
 ^ | 32MB flash buffer for log data | ^ | 32MB flash buffer for log data |
 ^ Interfaces | Ethernet, CAN, Modbus RS485, SDI-12, Discrete I/O | ^ Interfaces | Ethernet, CAN, Modbus RS485, SDI-12, Discrete I/O |
-^ Cellular | LTE CAT-M1 global (optional GSM 2G/3G) +^ Cellular | LTE CAT-M1 global | 
-^ RTC | Automatically synchronized with servers. Supercap backup (>24h) | +^ RTC | Automatically synchronized with servers. Supercap backup (~24h) | 
-^ Power | 11-30VDC supply (switching ((Power consumption independent of input votage))), <1W self-draw average |+^ Power | 12-24VDC supply (switching ((Power consumption mostly independent of input voltage))), <1W self-draw average |
  
 There are no provisions for directly connecting to the hardware for configuration. All configuration is managed through the servers https://eze.io. There are no provisions for directly connecting to the hardware for configuration. All configuration is managed through the servers https://eze.io.
Line 207: Line 207:
 === Embedded software === === Embedded software ===
  
-The ezeio runs a proprietary software stack, designed bottom-up by eze System. The software is embedded in the microcontroller and runs immediately when power is applied. The configuration, drivers and user designed logic is synchronized automatically from the cloud servers, and runs locally on the ezeio.+The ezeio runs a proprietary software stack, designed from scratch by eze System. The software is embedded in the microcontroller and runs immediately when power is applied. The configuration, drivers and user designed logic is synchronized automatically from the cloud servers, and runs locally on the ezeio.
  
 Each ezeio unit has unique keys for validating with the ezeio cloud system and will refuse any other attempts to communicate than with the ezeio servers. The system is inherently secure, designed for direct use on the public Internet with no need for additional VPN, firewalls or other third-party security measures. Each ezeio unit has unique keys for validating with the ezeio cloud system and will refuse any other attempts to communicate than with the ezeio servers. The system is inherently secure, designed for direct use on the public Internet with no need for additional VPN, firewalls or other third-party security measures.
  • ezeio2/introduction/start.txt
  • Last modified: 2022-07-07 16:59
  • by andreh