• 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

    "Data point save due to wrong point referenced"

    User help
    3
    10
    4.8k
    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.
    • jeremyhJ
      jeremyh
      last edited by

      I am trying to add data points to a new MangoES and keep getting this message:

      Screen Shot 2015-12-03 at 6.04.18 pm.png

      When I get the message I have to refresh the page and it's making the process of configuring points quite a hassle.
      I'm not working in any other tabs and get this message even when using a private chrome session.

      Is there any way to avoid or fix this?

      Cheers

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

        Jeremy,

        Those checks were put in there to handle the 'state saving' feature of Mango where your session retains the last point you were working with ie. on the Data Point Details page or the Data Point Edit view. If you do not have multiple tabs open it's possible there is a bug. I have found a fixed several of these that can arise from the 'Data Source Tools' that are included with various data sources.

        What data source are you working with and are you trying to add a point via one of the tools? If not what steps can you provide me with to reproduce this issue?

        Thanks,
        Terry

        1 Reply Last reply Reply Quote 0
        • jeremyhJ
          jeremyh
          last edited by

          Hey Terry,

          Using the Modbus IP data source.

          I just did two quick screen records in quick succession and got the popup both times.

          https://www.youtube.com/watch?v=Q_UgO2fQDwA

          https://www.youtube.com/watch?v=jRMpOS2YIxA

          Note that my datasource device was offline the whole time (though I did expect it to come back online at anytime).

          I know the video isn't exactly what you'd call reproducible steps but I just wanted to show that I wasn't really doing anything too odd.

          1 Reply Last reply Reply Quote 0
          • JoelHaggarJ
            JoelHaggar
            last edited by

            Hi Jeremy,

            I believe this is a known issue that we should revolve soon. In the meantime If you use the "add data point" button on the Data points tab you shouldn't have a problem adding new points.

            upload-0a8f69d2-6178-4b6d-9807-706489fc6121

            1 Reply Last reply Reply Quote 0
            • jeremyhJ
              jeremyh
              last edited by

              Hi Joel

              I can do that. Should I avoid using the point test tool entirely?
              Cheers

              1 Reply Last reply Reply Quote 0
              • JoelHaggarJ
                JoelHaggar
                last edited by

                All the other parts of the Modbus tools work fine, it's only when you try and use the "Add Point" button that the issues occurs.

                1 Reply Last reply Reply Quote 0
                • jeremyhJ
                  jeremyh
                  last edited by

                  OK, no worries, thanks!

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

                    Jeremy,

                    We are working on a fix. You can track it here: https://github.com/infiniteautomation/ma-core-public/issues/489

                    Thanks,
                    Terry

                    1 Reply Last reply Reply Quote 0
                    • jeremyhJ
                      jeremyh
                      last edited by

                      Thanks Terry

                      Is this a different issue? https://github.com/infiniteautomation/ma-core-public/issues/323

                      Cheers

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

                        Ah yes, same bug. I'll make a note of that and re-open it while closing #489.

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