Functionality overview of Evocon devices

Networking capabilities

Available connectivity	Ethernet (RJ45), WiFi
Supported speed Ethernet	10/100 Mbps
Supported WiFi standards	2.4GHz 802.11b/g/n
DHCP support	WPA/WPA2, Open network
Static IP support	✅
https://en.wikipedia.org/wiki/HTTP_tunnel	✅
Custom DNS support	✅
Custom NTP support	✅
Custom hostname support	✅
https://en.wikipedia.org/wiki/Command-line_interface over USB support	✅
Over-the-air updates	✅
Connection to Evocon	HTTPS, MQTT (TCP 443, 8883)

Evocon solution Architecture overview

Interactions between Evocon devices and the servers

Evocon device 3 connects to the cloud servers using MQTT protocol secured by TLSv1.2. Each device authenticates with its unique X.509 client certificate. This connection is used for updating configuration and sending signal data.

Real time clock of the device is synchronised using HTTPS (via devices.evocon.com). If HTTPS connection fails, HTTP connection is used as a backup. NTP is used as backup if HTTPS and HTTP connections fail.

Firmware updates are downloaded by the device over HTTPS connection (from devices.evocon.com). Update process is initiated by the Evocon support.

Interactions between Evocon devices and the AWS IoT platform.

Collected signal data is sent from Evocon device contains the following information:

Device ID - Specified by Evocon to every device
Input number - Identifies the inputs 1,2 and 3
Quantity of signals - How many signals were counted during the time interval configured (usually it is 1, but can be more than 1 in case of faster signals)
Timestamp - Timestamp of the data packet (either once per minute or when the signal (high to low edge) was detected.

As visible from above, no customer or production identifiable data is sent to the cloud by the Evocon device.

What does this mean for IT?