If Acceptable Missed Pings is set to
|
And Additional Missed Time (ms) is set to
|
Then
|
---|---|---|
0
|
0
|
Zero missed pings and zero additional missed time mean that you expect the device to never miss a ping. The ReportingAlgorithm considers the device as not reporting as soon as the device misses a ping.
|
0
|
7200000
|
Zero missed pings and two hours of additional missed time mean that you do not expect the device to miss a ping and that the ReportingAlgorithm should wait two hours before considering the device as not reporting.
|
5
|
0
|
Five missed pings and zero additional missed time mean that a device is still reporting until it misses more than five pings. The ReportingAlgorithm considers the device as not reporting as soon as the device misses the sixth ping.
|
4
|
3600000
|
Four missed pings and 60 minutes of additional missed time mean that a device is still reporting until it misses four pings plus an hour of additional time. The ReportingAlgorithm considers the device as not reporting as soon as it has missed four pings and an hour has passed since the last missed ping.
|
![]() |
If the acceptableMissedPings property is set to zero and a ping is received even milliseconds after it is expected, the ReportingAlgorithm may identify the device as not reporting. If you encounter this situation when using this property, consider adding some small amount of time to the additionalMissedTimeAllowed property to allow for some minor fluctuation in the execution of the evaluation. For example, setting the additionalMissedTimeAllowed property to one second (1000ms) and the acceptableMissedPings property to 2 will allow a ping to occur up to one second later than expected while still allowing the device to be identified as reporting. Similarly, if the number of missed pings is 5 and you expect network fluctuations, consider setting the additional missed time allowed to at least one second.
|
![]() |
The AxedaPollingTimer Thing runs as the eMessageConnector user that you set in the runAsUser property. To ensure that this property has the correct eMessage Connector user, you MUST run the GrantEMessageConnectorPermissions service of the eMessageServices Thing, whether the eMessage Connector user is a non-administrative user (recommended) or an Administrator (not recommended). For instructions on running the service, refer to Setting Up Permissions and Visibility for the eMessage Connector.
|