• 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

    Point value may not be reliable

    User help
    3
    8
    1.9k
    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
      PSpivey
      last edited by

      Hi guys,

      I just upgraded to the newest version of the core (3.52) and i am getting the notification saying point value may not be reliable on nearly every single one of my data points.

      Meta datapoints which have been created internally on the server as well as mango internal data points are the only points without this issue. All the other data points are being published via mango persistant tcp and are updating as they should however they are all saying this same message.

      I have added a screenshot as an example below. Most of these data points shown are updating ever second but are still seen to be unreliable according to mango. Has anyone else come across this issue?

      0_1539935819905_2167cabe-dcd4-4c72-bc49-55245a466273-image.png

      1 Reply Last reply Reply Quote 0
      • CraigWebC
        CraigWeb
        last edited by

        Hi PSpivey

        Could you give some more information on what data source the points are coming from. Could you also go to your data source page and have a look what is displaying by current alarms and runtime status of the data sources that are giving a problem0_1539938439934_Screen Shot 2018-10-19 at 10.39.06.png

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

          Hi CraigWeb,

          Thanks for the reply. They are all Mango Persistent TCP data sources and current alarms and Runtime Status shows nothing for all of them.

          0_1539938968999_4cd3b9f0-efc5-49ce-8738-5de1318520b1-image.png

          1 Reply Last reply Reply Quote 0
          • CraigWebC
            CraigWeb
            last edited by

            Are the points reliable on the mango instance that is publishing them ?

            1 Reply Last reply Reply Quote 0
            • Jared WiltshireJ
              Jared Wiltshire
              last edited by

              @PSpivey You are encountering a bug that we recently discovered with new versions of Mango. We added the ability for Persistent TCP publishers to send the unreliable status, however if you don't have this turned on the Persistent TCP data source thinks all the points are unreliable. We are looking to fix this ASAP.

              In the meantime if you update your publishing side to the latest "Persistent TCP" module version and turn on "Publish point attribute changes" on your publisher you should see the issue go away.

              Developer at Radix IoT

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

                Thanks for the help Jared, I've had a go of following your advice for a couple of mangos so far, a V3 and a V2. The V3, sad to say didn't seem to work. I updated the persistent TCP module to 3.5.1 and turned on "Publish point attribute changes" however it has not changed the status of my notification. It is still saying Point value may not be reliable for all points coming from that publisher. Any thoughts?

                Also, clicking on Check for upgrades on the modules page of my V2 mango comes up with the notification saying that all modules are up to date. It is currently using persistent 1.7.2 and the core version on that specific mango is 2.8.8, will i be able to fix the issue on a V2 mango without upgrading to V3?

                Jared WiltshireJ 1 Reply Last reply Reply Quote 0
                • P
                  PSpivey
                  last edited by

                  Sorry Jared, I checked again just now and it did work for the V3, mistake on my part but help for the V2 would still be greatly appreciated.

                  1 Reply Last reply Reply Quote 0
                  • Jared WiltshireJ
                    Jared Wiltshire @PSpivey
                    last edited by

                    @pspivey said in Point value may not be reliable:

                    will i be able to fix the issue on a V2 mango without upgrading to V3?

                    I suggested a fix for backwards compatibility with v2 publishers to one of our developers who was working on it. I'll see what became of it.

                    Developer at Radix IoT

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