• 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

    unable to discover a bacnet device on my network

    User help
    4
    18
    5.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.
    • M
      Mircea
      last edited by

      Hi Phil,
      I looked in ma.log file and found this "Module dashboards 3.6.0 is not compatible with core 3.2.2
      java". I don't know what to do from here.

      My controller IP is 192.168.1.127.
      Mango ES V3 IP is 192.168.1.135

      0_1512818621012_81c0c670-672f-45d2-8eda-51cf8f98d52a-image.png

      One extra question.
      When I look into Mango ES V3 Configuration I see this

      0_1512818713925_39f811ff-302d-4c15-9803-a2ad624647a4-image.png

      The Address highlighted with red don't look like 192.168.1.135.
      I remember i changed one time and after I wasn't able to log in . I need to use USB driver to restore the fix IP.
      Do you know why ? It is more easy to change here the IP then with USB.
      Thanks
      Mircea

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

        Hi Mircea,

        If you are updating, you can mark the dashboards module for deletion on the modules page and then restart Mango. This will delete the dashboards module. It was superseded by the MangoUI module.

        I'm not sure why the discovery wouldn't be happening, that looks like the local device IP you'd want to be using. Perhaps after you update you may see a better result. Past that, it would probably take a wireshark capture to say anything about what's occurring.

        I wonder if you've altered your /etc/network/interfaces file? it's probably a bug that it has the IPv6 in the IPv4 field. Can you share your /etc/network/interfaces file?

        1 Reply Last reply Reply Quote 0
        • M
          Mircea
          last edited by

          Hi Phil,
          Hi, I’ve marked the dashboard module for deletion and after that I’ve reinstalled the modules again and now all the modules are version 3.3.0-beta.1, also when I’m going in home page I’ve get a lot of features disabled.

          0_1515770637519_f8d58859-9051-40aa-851f-35657b6f2cee-image.png

          The problem with the BACnet it’s the same I cannot discover a BACnet device, it get me this error.

          0_1515770680054_90f0756e-0dd0-436b-8220-d7aac230a22e-image.png

          Now when I look into Mango ES Configuration everything looks ok, the address is ok.

          0_1515770713135_5dda45de-db72-4ecb-8e1c-33147523f791-image.png

          Also as you requested I can share interface file, here is a capture with the data from that file.

          0_1515770754460_34737629-f4e0-4eb6-99af-8a26970c306d-image.png

          Thanks
          Mircea

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

            Hi Mircea,

            The tiles on the home page are powered by an internal data source named "Mango Internal" with the xid "internal_mango_monitoring_ds". If this data source doesn't exist or is disabled (or some set of points on it are disabled or don't exist) you will see those tiles say they are disabled, instead of providing counts.

            There are updates to BACnet4J that we're evaluating updating into the BACnet module. It should be directly compatible with the module, still. You can test the 4.1.2 version of BACnet4J if you wish, by,

            1. Download BACnet4J 4.1.2 from our Maven repository: https://maven.mangoautomation.net/#browse/search=keyword%3Dbacnet4j:d3510b7ad18d82cd88bc82707116e89f:9fdf7807167774766a180f65ffd8a6c1
            2. Stop Mango
            3. Move Mango/web/modules/BACnet/lib/bacnet4j-4.0.1.jar somewhere else for safe keeping.
            4. Move bacnet4j-4.1.2.jar into Mango/web/modules/BACnet/lib/
            5. Start Mango

            Let us know if you decide to try this and how it goes!

            1 Reply Last reply Reply Quote 0
            • M
              Mircea
              last edited by

              Hi Phil,
              I fixed the tile issue on the home page.
              I will try next week the new bacnet 4.1.2. however with the existing bacnet module that come with Mango ES V3 I should be able to discover / find my controller on the network. Am i right ?
              I can find my controller with Mango ES V 2.8.
              Thanks
              Mircea

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

                Yes, I would say the existing BACnet module should work. If it doesn't that implies there may be an issue in the module or your network that should be corrected. A wireshark of 2.8 vs. 3.2 for a data source enabled + discovery would be the most informative way to probe why it isn't working. But, somethings were changed and improved between 4.0.1 and 4.1.2 of BACnet4J, so perhaps updating is all that is actually required.

                1 Reply Last reply Reply Quote 0
                • M
                  Mircea
                  last edited by

                  Hi Phil,
                  I try to connect to webmin( port 10000).
                  What is the factory default password ?
                  Thanks
                  Mircea

                  1 Reply Last reply Reply Quote 0
                  • M
                    Mircea
                    last edited by

                    I found it ....

                    1 Reply Last reply Reply Quote 0
                    • M
                      Mircea
                      last edited by

                      Hi Phil,
                      I update the Bacnet as you suggested but no luck . Same issue, I can't discover the controller.
                      I am not familiar with wireshark but I will try.
                      This is what I get after restarting mango with bacnet 4.1.2
                      0_1515800927257_9f57afab-b52b-4a4e-b4df-caa5231bff64-image.png

                      I am able to see the other Mango ES as a bacnet device.
                      0_1515800983057_f4bb6712-d83e-4857-bedd-1339260b1cd2-image.png

                      Thanks
                      Mircea

                      1 Reply Last reply Reply Quote 0
                      • M
                        Mircea
                        last edited by

                        Hi Phil,
                        I found that if I change the controller device Id while Mango is in process of sending object list request then Mango catch the controller id and display the list of objects that are on controller.
                        Hope this help for further investigation.
                        Thanks
                        Mircea

                        1 Reply Last reply Reply Quote 0
                        • M
                          mihairosu
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • M
                            Mircea
                            last edited by Mircea

                            Hi Phil,
                            Using the trick that I mention previous ( changing the ID of bacnet controller in the same time with the request from Mango to display the objects list) I was able to import the points. The problem is that the data base stop recording after a while.
                            0_1515961348763_71ee7b3d-02fe-48fe-b983-7f62b9b8bc09-image.png
                            0_1515961756773_74548fe9-4251-45b9-8618-6c12c5c92de6-image.png

                            The Jace2 data base record every minute ( the default settings).
                            If I stop and restart the data base the points start to record again for a while and stop after.
                            This is stranger to me. It is not the first time when I use Bacnet but is the first time when I used with Mango V3.
                            Any idea why . all thous issue ?
                            Thanks
                            Mircea

                            1 Reply Last reply Reply Quote 0
                            • M
                              Mircea
                              last edited by

                              Hi Phil,
                              Here are the requested wireshark.

                              [1_1516049331191_Bacnet MANGO v3.pcapng](Uploading 100%) [0_1516049331189_Bacnet MANGO v2_8.pcapng](Uploading 100%)

                              Please let me know what I need to do.
                              Thanks
                              Mircea

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

                                Mircea,

                                Can you email those into support@infiniteautomation.com ? Thanks

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

                                  Surprisingly, resolution was found in slightly different Local Device settings, specifically he had to use the broadcast address that was proper for the network and the sink address to bind. So, in this instance, bind address 0.0.0.0 and broadcast address 192.168.1.255

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