Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Aborted poll of bacnet source causes all subsequent points to be the same. *fixed*
-
Hi there,
I've having an interesting issue where if one of my bacnet devices (via bacnet ip) has an issue and the poll is aborted, all subsequent polls on all points under the data source are the same as the last recorded point value.
Occurred twice randomly, then tested it by physically disconnecting one bacnet device from the network and waiting for the device to be polled. It threw the poll aborted message as expected, then we connected the device back to the network. All subsequent points recorded the same respective value, whatever the value was before the aborted poll.
A forced refresh seems to fix the system, but I'm not 100% sure as I'm currently investigating it.
Nothing interesting comes up in the logs, only the poll aborted message.
Anyone have any ideas?
If not, is there a way to script a source refresh in response to the aborted poll?
update: fixed on mango update 3.1.1
Thanks!
Conor -
Glad to hear it's resolved!
