Hardware - Evocon IIoT device 3 - Networking configurations and capabilities

Networking capabilities

* 5GHz WiFi is not supported by the Evocon IIoT device 3

Interactions between Evocon devices and the servers

Evocon device 3 connects to the cloud servers using MQTT protocol secured by TLS. 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.

No customer or production identifiable data is sent to the cloud by the Evocon device.

What does this mean for company IT?

It is necessary to make sure that the firewall allows Evocon devices to communicate to the Internet. Ports DO NOT need to be opened from the internet towards the Evocon device.

Hostnames that need to be allowed in firewall for Evocon IIoT device 3 are

• IoT endpoint

  • IoT connection uses MQTT protocol over TLS and port 443.
  • The main endpoint for Evocon IIoT devices is:
    • iot.evocon.com (15.197.133.85)
  • Two fallback endpoints are:
    • iot1.evocon.com (35.71.154.210)
    • a3ed97ktfhc5dy-ats.iot.eu-west-1.amazonaws.com (dynamic IP addresses)

• Time and firmware update endpoint. These endpoints are used to update time (using cascading fallback from HTTPS to HTTP to NTP). And also update device firmware (HTTPS only).

• devices.evocon.com (13.248.201.79)

• devices1.evocon.com (76.223.88.250)

• No firewall rules are needed from the internet towards the devices.

Using Static IP or proxy configuration

If you would like to use Static IP address or proxy configuration, please provide the following information so that we can configure the device prior to shipping. It is also possible for customer IT to apply or change this configuration using a CLI-over-USB connection or WiFi interface.

• IP address
• Mask
• Gateway
• DNS server

If the connection must pass through a proxy server, the following is needed:

• Proxy server (name or ip address) and port

Using WiFi

Evocon device 3 only supports 2.4GHz WiFi connectivity.

Evocon device 3 only supports WPA-Personal, WPA2-Personal, WPA3-Personal security protocols or no password open networks.

If you would like Evocon to preconfigure WiFi network before shipping, please provide

• WiFi network name (SSID)
• WiFi network password

In this case, we will configure the WiFi and the device will connect when it is powered on at the site.

Up to 2 WiFi networks can be configured at once. The device will choose the one that has stronger signal.

Alternatively, customer can configure the WiFi and other parameters using the “WiFi interface” or “Command line interface” guides.

• Hardware - Evocon IIoT device 3 - Interface to configure IP and WiFi settings
• Hardware - Evocon IIoT device 3 - Command line interface (CLI)

Best practices

We suggest using a separate VLAN for Evocon (or other IoT) devices. This way, isolation from other business networks is achieved.