• 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

    BACnet aquisition Data Source splitting

    How-To
    2
    2
    1.5k
    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.
    • mondayVisionM
      mondayVision
      last edited by

      Hi there,

      I am about to setup mango to retrieve BACnet data from six JCI DCCs, approximately 200 data points each.

      What will be the best approach considering data sources. Should I use one data source for all controllers or better use one data source for each controller?

      Especially regarding CPU performance and best Threading behaviour.

      Best regards
      Alex

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by phildunlap

        Hi Alex,

        The intention is to move toward those two possibilities being a complete wash, so that it can be about segmenting it for management purposes.

        Currently, though, I have observed issues when your number of BACnet sources gets considerably higher. In one such instance, the user had 100 individual BACnet devices and their thread consumption was enough Mango had trouble booting. After moving all the data points onto a single data source, this issue was resolved and Mango started quite quickly. Using one data source is considered the more computationally efficient route right now.

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