• 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

    'Discard extreme values' setting not sticking

    User help
    2
    5
    1.3k
    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 have a data point which sometimes returns wildly unwanted values, like -4296829.32.
      I must have enabled the 'discard extreme values' option a dozen times (and hit save!) but each time, it never seems to 'stick', and a few days later the nuisance values are still there.

      Any ideas? It is driving me nuts, not to mention screwing up all my graphs!

      {
      "dataPoints":[
      {
      "xid":"DP_952377",
      "name":"AC Active Power (All Phases)",
      "enabled":true,
      "loggingType":"ON_CHANGE",
      "intervalLoggingPeriodType":"MINUTES",
      "intervalLoggingType":"INSTANT",
      "purgeType":"YEARS",
      "pointLocator":{
      "range":"HOLDING_REGISTER",
      "modbusDataType":"FOUR_BYTE_INT_SIGNED",
      "writeType":"NOT_SETTABLE",
      "additive":0.0,
      "bit":0,
      "charset":"ASCII",
      "multiplier":0.001,
      "offset":30775,
      "registerCount":0,
      "slaveId":2,
      "slaveMonitor":false
      },
      "eventDetectors":[
      ],
      "plotType":"SPLINE",
      "unit":"kW",
      "chartColour":"",
      "chartRenderer":null,
      "dataSourceXid":"DS_897950",
      "defaultCacheSize":1,
      "deviceName":"na",
      "discardExtremeValues":false,
      "discardHighLimit":100000.0,
      "discardLowLimit":-1.0,
      "intervalLoggingPeriod":15,
      "purgeOverride":true,
      "purgePeriod":1,
      "textRenderer":{
      "type":"ANALOG",
      "useUnitAsSuffix":true,
      "unit":"kW",
      "renderedUnit":"kW",
      "format":"00.00"
      },
      "tolerance":0.0
      }
      ]
      }

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

        What version of Mango are you using. I'm pretty sure this issue has been resolved in the latests 2.4.X release.

        Joel.

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

          2.1.0 - sounds like it is time to upgrade!

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

            Yeah, upgrading will fix that. I would recommend upgrading to 2.4.2 and you'll find quite a few improvements and bug fixes.

            Here is the link to get all the files and at the bottom of the page are the upgrade instructions:
            http://infiniteautomation.com/index.php/download

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