• Recent
    • Tags
    • Popular
    • Register
    • Login

    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.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Cannot execute point link because it is currently running

    User help
    2
    3
    1.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      Pedro
      last edited by

      I have a metadata point that updates once per minute. It is configured to write a Modbus register via a Point Link whenever the value changes. However, almost every minute, I receive an event like this:

      Event active notification
      ** Urgent **
      11:52:00 - Cannot execute point link because it is currently   running
      

      Note: This event will automatically return to normal when the event criteria are no longer satisfied

      I have other metadata points that exhibit the same behavior. Nothing is shown in ma.log when these events occur. What exactly is the cause of this error? How can it be avoided?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • terrypackerT
        terrypacker
        last edited by

        This alarm is triggered when the point link is activated while it is already currently running. For example if you are trying to set a value via Modbus and it takes 10 seconds to set the value you cannot run this point link again for at least 10 seconds or you will get the above alarm.

        I would re-check your setup, it seems that your point link is running more often than you think. In very busy systems you may be limited by network bandwidth or number of available threads.

        FYI: Point Link tasks run as high priority work items.

        1 Reply Last reply Reply Quote 0
        • P
          Pedro
          last edited by

          Terry, thanks for your answer. Even though the target point sets in a second or two, three weeks ago I reduced the number of context updates that can possibly trigger the metadata point, and since then I have not seen this error.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post