• Recent
    • Tags
    • Popular
    • Register
    • Login
    1. Home
    2. luigi
    3. Topics

    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
    L
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 7
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by luigi

    • L

      License

      User help
      • • • luigi
      5
      0
      Votes
      5
      Posts
      1.8k
      Views

      Jared WiltshireJ

      Hi @luigi here's a report of the licenses for the Java libraries that are used by Mango -
      https://cdn.rawgit.com/infiniteautomation/misc-files/master/third-party-report.html

      The libraries that start with com.infiniteautomation are covered by the Mango license.
      https://raw.githubusercontent.com/infiniteautomation/ma-core-public/main/Core/LICENSE

    • L

      Event handler binary set point

      User help
      • • • luigi
      2
      0
      Votes
      2
      Posts
      1.1k
      Views

      phildunlapP

      Hi luigi,

      Thanks for putting so much detail in! The only thing that's missing is the setup for the high limit detector you have on DP_i1.

      Your output point looks like a virtual point, so there is no excuse for it not accepting a set (unlike a Modbus point for instance, which could have the set request timeout). It is very weird that you have that virtual point set to an 'Alternate' change type. This means every poll period of the virtual data source it will flip from true to false or the other way around. Have you disabled polling on the virtual data source that owns DP_Ai1?

      I would look at your events to try to figure out what is going on if it isn't a misunderstanding of the change type. I would expect a message about the SetPointWorkItem failing if you see all the events raised / returned that you expect to.

      If on the other hand you don't see all the high limit events that you were expecting on DP_i1, then I'll wonder what version of Mango you are using, and I'll want to see the settings on the high limit detector.

    • L

      Mango Portlet

      User help
      • • • luigi
      2
      0
      Votes
      2
      Posts
      782
      Views

      Jared WiltshireJ

      @luigi I've never heard of Liferay but looking into it I would say that no, Mango is not portlet compliant.

    • L

      Integration with other scada system

      User help
      • • • luigi
      6
      0
      Votes
      6
      Posts
      1.6k
      Views

      phildunlapP

      If Haystack is available in that Niagara version, you would create a Haystack data source in Mango which would behave as a client and poll the Niagara server. This solution would probably be easier, go ahead and try! All you need is the URL to your Haystack server and your authentication information to create the data source.

      If using a scripting data source, you would have the full flexibility of the REST API that was the subject of the post. If it's serving a REST API and that's what you're querying, then you're the client and its the server again.

      There are other options. Both the BACnet and Modbus publishers in Mango accept writes over those protocols. If you find it easier to output a CSV once a day, there is a Data File data source that can import something you copy to it or you can define an arbitrary poll class and have Mango copy the file from the remote server. So, either client-server relationship is possible, but both the scripting and Haystack options would definitely be clients to their respective APIs.