Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes

Reference · for Engineers

Connection Health

A dashboard item that lists every device connection with its reads, failed reads, read time and last read, the connections not reading first.

The Connection Health item shows how every device connection reads now. Each device is a row with its Edge Gateway, protocol and tag count, its read time against the slowest device, the share of reads that succeeded and how long ago it last read.

  • Header. How many devices are reading, the share of all reads that succeeded, the median read time and the reads counted, then how many devices are not reading, have failed reads, are slow or are reading.
  • Row. A device is not reading when its last read is older than the limit or it has none, has failed reads when under 99% of its reads succeeded, and is slow when its read time reaches the slow limit.

Devices that are not reading come first, then those with failed reads, then the slowest. Select a device to filter the other items of the dashboard by it.

Data fields

FieldKind
DeviceDimension
SiteDimension
GatewayDimension
ProtocolDimension
Device profileDimension
TagsMeasure
ReadsMeasure
Failed readsMeasure
Connection errorsMeasure
Read time (ms)Measure
Seconds since last readMeasure

Device is required: one row per device. Reads counts every read cycle, the failed ones included, so the share that succeeded is reads less failed reads over reads. Bind Seconds since last read with the Min summary.

Settings

SettingValuesDefault
Not reading after (s)A number from 5 to 86400120
Slow from (ms)A number from 1 to 60000500
  • Not reading after (s) is how old the last read may be before a device counts as not reading.
  • Slow from (ms) is the read time from which a device counts as slow.

Where to see it

The Meridian demo plant uses it on Meridian · Connectivity Command Center, with the read counters each Edge Gateway keeps per device.

Was this page helpful?

Evaluating Proxus? See it on your own machines in a 30-minute technical session.