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.
Cannot execute point link because it is currently running
-
Hi,
I have an instance that has a function to turn on THREE Modbus outputs, when ONE data point goes high, and then subsequently turning them all back off when the point goes back low.
This all works fine using "Point Links", with no scripts.Recently I had an event appear :
9/5/2018 06:33:30 Cannot execute point link because it is currently running 9/5/2018 06:37:30 - Returned to normal 4 minutesThe status of the output changed to active in Mango, but didn't actually change the output to high.
I checked the point link, and it's settings are the same as the other two. Each point is on a different data source, but I did not get any data source events.
I cannot find any more info in the logs.
Does anyone know why this would of occurred, or exactly where to look in the logs?
-
Hmm. Do you know if you saved the point link when the event was active, and that's when it returned to normal?
I do think it's possible for a point link to get stuck thinking it's running. I think it would have to be an exception in the PointLinkRT's execute method. I'm not sure where one could produce such an error, but I will do some checking. I would have expected an error in your log like, "Uncaught exception in work item" and that the PointLinkRT's execute method will appear in the stack trace.
Otherwise, it could be that two point events for the source series were running at the same moment and the error about not being able to run the point link again is incidental to not having set the value to the device. If the modbus connection was simply down AND two events got queued at the same time, we could expect what you're describing. There would have been a data source event for the set point failure.
