Edge Devices

“Edge device” is a reference to any data collector reading data from physical hardware at the shopfloor and sending that data to the cloud.

Most often, the role of the Edge Device fulfils our LogiXGate - robust reader, processor and publisher resilient to cloud unavailabilities, able to read from multiple OPC servers, Modbus connectors and SQL databases at the same time.

Frame 30 (1).png

Avoid a situation where multiple edge devices send data about the same line. This way the sequence of events is nondeterministic, so PackOS processing is not able to correctly understand a sequence of signals, and calculate root causes. Each line needs to have only a single Edge Device attached.

Frame 30 (2).png

Such edge devices are connected to IoT Hub, where they get it’s unique name - usually containing factory location and department/line identifier.

The process of registering Edge Device in IoT Hub and giving it a unique name is usually performed by an engineer responsible for the given IoT Hub

You can inspect and manage the list of Edge Devices feeding data to your factory by going to
Settings → Advanced → Edge Devices:

Here, you can also select which timestamp will be used for processing messages from this source

  • OPC time - the time reported by the OPC server when the value was read

  • Edge device time (default) - timestamp reported by the edge device when the value was read

  • IoT Hub time - timestamp when the message was received by the IoT Hub

  • Queue time - timestamp when the message was queued for processing

Additionally, a ‘Time correction’ can help you quickly adjust a skewed clock to match it with the cloud clock used for events such as order start.

‘Time correction’ setting should be used only as a last resort - if your clock is not synchronised with an NTP server the time difference may get worse over time