<![CDATA[ES version bacnet module 3.6.0 issue compare ver. 3.5.2]]>As for testing, we have ES and also a PC installed with MANGO (non-commercial version).

With bacnet module version 3.5.2 on MANGO PC (Windows 10), we manage to scan ALL the controllers on old interface screen on bacnet/IP discovery.
0_1565143748066_es device manager.PNG

Upon we upgrade the bacnet module version 3.6.0 on MANGO PC, even the old interface or new interface we faced similiar issue that we did not manage to get all the DDC controller online in the list on bacnet/IP.

0_1565145546764_es device manager new.PNG
0_1565148102431_1.jpeg

Initially, we won't perform above test scan until we noticed MANGO ES bacnet discovery had very less of controllers it manage to scan on bacnet/IP on version 3.6.0.

Same issue we encounter too on bacnet/mstp on MANGO ES - manage to discover Alerton and Honeywell Spyder but not others brand of bacnet mstp ddc on same rs-485 comm. Is there any restriction on brands bacnet ms/tp ddc that MANGO ES allow to discover on bacnet ms/tp ?

Any firewall or settings we need to look into ?

regards,
Frank

]]>https://forum.mango-os.com/topic/4380/es-version-bacnet-module-3-6-0-issue-compare-ver-3-5-2RSS for NodeFri, 10 Apr 2026 22:48:58 GMTWed, 07 Aug 2019 03:24:15 GMT60<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 31 Oct 2019 09:08:06 GMT]]>@terrypacker Now the new version working fine. I'm able to detect all my BACnet devices. thank you for your support.

]]>https://forum.mango-os.com/post/23954https://forum.mango-os.com/post/23954Thu, 31 Oct 2019 09:08:06 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Wed, 16 Oct 2019 15:10:55 GMT]]>@techalton I've released a new module for 3.6.x that should fix your problem. Please report back if you have any issues. Thanks!

]]>https://forum.mango-os.com/post/23861https://forum.mango-os.com/post/23861Wed, 16 Oct 2019 15:10:55 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Tue, 15 Oct 2019 11:15:11 GMT]]>@techalton I have a working solution but like @phildunlap said I am not planning to release it until it is fully vetted. However if you are interested in using a beta version I can build you a replacement jar for you to test with. This would involve replacing a jar file in the web/modules/BACnet/web/lib folder of your Mango installation and restarting Mango.

]]>https://forum.mango-os.com/post/23853https://forum.mango-os.com/post/23853Tue, 15 Oct 2019 11:15:11 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Mon, 14 Oct 2019 13:50:12 GMT]]>Hi techalton,

This is the git issue it is being tracked in: https://github.com/infiniteautomation/BACnet4J/issues/43

Michel has responded and it looks like Terry has coded a prospective solution to this specific issue, but that it needs review / assistance to generalize the relaxing of the type checking in reading properties from other devices.

]]>https://forum.mango-os.com/post/23850https://forum.mango-os.com/post/23850Mon, 14 Oct 2019 13:50:12 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Mon, 14 Oct 2019 06:47:15 GMT]]>hello Phillip

@phildunlap said in ES version bacnet module 3.6.0 issue compare ver. 3.5.2:

Hi techalton,

Yes, we were able to replicate the issue and reached out to the developer who was working on the changes between BACnet4J 4 and 5, which is predominantly work toward getting a BACnet BTL Compliance certification.

The cause is that the device in question deviates from the BACnet specification with regards to the data type of its protocol version (section 12.11 specifies the protocol version to be an unsigned integer). The device in question provides a character string as its protocol version, The BTL specification stipulates how to respond to deviations from the specification, but I have not had access to the BTL compliance specification to ensure this is intended behavior, and the developer who did the work has not yet responded.

any update from your developer?

]]>https://forum.mango-os.com/post/23847https://forum.mango-os.com/post/23847Mon, 14 Oct 2019 06:47:15 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Tue, 17 Sep 2019 17:07:03 GMT]]>Hi techalton,

Yes, we were able to replicate the issue and reached out to the developer who was working on the changes between BACnet4J 4 and 5, which is predominantly work toward getting a BACnet BTL Compliance certification.

The cause is that the device in question deviates from the BACnet specification with regards to the data type of its protocol version (section 12.11 specifies the protocol version to be an unsigned integer). The device in question provides a character string as its protocol version, The BTL specification stipulates how to respond to deviations from the specification, but I have not had access to the BTL compliance specification to ensure this is intended behavior, and the developer who did the work has not yet responded.

]]>https://forum.mango-os.com/post/23655https://forum.mango-os.com/post/23655Tue, 17 Sep 2019 17:07:03 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Tue, 17 Sep 2019 04:13:00 GMT]]>hello Phillip

@phildunlap said in ES version bacnet module 3.6.0 issue compare ver. 3.5.2:

Thanks for being persistent, techalton, we are examining the files and information you submitted.

any update?

]]>https://forum.mango-os.com/post/23649https://forum.mango-os.com/post/23649Tue, 17 Sep 2019 04:13:00 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 12 Sep 2019 12:55:24 GMT]]>Thanks for being persistent, techalton, we are examining the files and information you submitted.

]]>https://forum.mango-os.com/post/23594https://forum.mango-os.com/post/23594Thu, 12 Sep 2019 12:55:24 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 12 Sep 2019 09:50:12 GMT]]>@techalton
You need to change the first three parts of the IP address to match you ip range.

I am having different BACnetIP issue. In your case, most likely it is down to mango since only thing that has been changed is the mango version of software. Your field controllers would have still be the same.

I have sent in my wireshark captures and am waiting for updates.

]]>https://forum.mango-os.com/post/23591https://forum.mango-os.com/post/23591Thu, 12 Sep 2019 09:50:12 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 12 Sep 2019 08:40:19 GMT]]>@cwangv said in ES version BACnet module 3.6.0 issue compare ver. 3.5.2:

Phil
some BACnet/IP devices won't respond to broadcast of 255.255.255.255. They only respond to local subnet broadcast requests. Hence the need to change the broadcast address to 192.168.69.255.
I hope the above would help @techalton

Thanks for sharing @cwangv. when I change the broadcast address to 192.168.69.255.im unable to scan any device at all

]]>https://forum.mango-os.com/post/23589https://forum.mango-os.com/post/23589Thu, 12 Sep 2019 08:40:19 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 12 Sep 2019 07:24:55 GMT]]>@phildunlap said in ES version bacnet module 3.6.0 issue compare ver. 3.5.2:

Were the wireshark captures provided from the same discovery attempts as the six images posted here?

Perhaps you can modify your Mango/classes/log4j2.xml file to log BACnet4J at trace level for the course of the test, and then send in the Mango/logs/ma.log file and wireshark from an attempted discovery in 3.6

Add near similar tags close to the bottom of log4j2.xml:
<AsyncLogger includeLocation="true" name="com.serotonin.bacnet4j" level="trace"/>

You can then either restart Mango or reload them on the /ui/administration/log4j-reset page, if the Log4J reset module is installed.

Until I have reason to suspect Mango as the cause of these discovery issues, we would assess an hourly support fee for any direct assistance.

hello Phillip

On Wireshark and ma.log I'm able to see device 1003 but on the mango UI I'm unable to see the device.i have emailed the ma.log and Wireshark file to you

thanks.

]]>https://forum.mango-os.com/post/23588https://forum.mango-os.com/post/23588Thu, 12 Sep 2019 07:24:55 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 12 Sep 2019 07:18:11 GMT]]>@phildunlap said in ES version bacnet module 3.6.0 issue compare ver. 3.5.2:

Also I notice we only see one bind address for any of these discoveries. While I wouldn't expect that to be the issue 1003 isn't in your images from 3.6 despite it being in the wireshark responding in exactly the same manner as it did in 3.5 . Can you confirm the local device configuration is the same in both versions? Can you try using a bind address of 0.0.0.0 ?

hello Phillip

sorry for the late reply I have tried bind address 0.0.0.0 and still I'm unable to scan device 1003

thanks.

]]>https://forum.mango-os.com/post/23587https://forum.mango-os.com/post/23587Thu, 12 Sep 2019 07:18:11 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Sat, 31 Aug 2019 01:30:05 GMT]]>Phil
some bacnet/ip devices won't respond to broadcast of 255.255.255.255. They only respond to local subnet broadcast request. Hence the need to change the broadcast address to 192.168.69.255.
I hope the above would help @techalton

]]>https://forum.mango-os.com/post/23468https://forum.mango-os.com/post/23468Sat, 31 Aug 2019 01:30:05 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Fri, 30 Aug 2019 16:24:19 GMT]]>Thanks for sharing what you saw on your network cwangv!

I would encourage @techalton to try the bind address is 0.0.0.0 . From the wiresharks emailed in, I believe they're broadcasting on 255.255.255.255 already, but we can see in one screenshot the local device's bind address is the IPv4 address.

]]>https://forum.mango-os.com/post/23464https://forum.mango-os.com/post/23464Fri, 30 Aug 2019 16:24:19 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Fri, 30 Aug 2019 14:26:17 GMT]]>Hi, Guys
I figured it out the issue (at least for me).
It is to do with the broadcast address. For me, I needed to change it from 255.255.255.255 to 192.168.69.255 (which is my subnet host ip range).
after doing that, all is well.
0_1567175967998_Screen Shot 2019-08-31 at 12.37.32 am.png

@techalton - give it try.

thanks.

]]>https://forum.mango-os.com/post/23459https://forum.mango-os.com/post/23459Fri, 30 Aug 2019 14:26:17 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Fri, 30 Aug 2019 13:51:34 GMT]]>Hi,
I am having similar issue running Bacnet Module 3.6.1. I can only discover some of the bacnet/ip devices, however other bacnet/ip devices can see Mango points (via bacnet/ip).
Other bacnet/ip devices on the network can see each other with no issues.
Using the legacy UI yields the same problem.
Let me know If I need to check anything to help out.

thanks.

]]>https://forum.mango-os.com/post/23457https://forum.mango-os.com/post/23457Fri, 30 Aug 2019 13:51:34 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 29 Aug 2019 19:35:52 GMT]]>Were the wireshark captures provided from the same discovery attempts as the six images posted here?

Perhaps you can modify your Mango/classes/log4j2.xml file to log BACnet4J at trace level for the course of the test, and then send in the Mango/logs/ma.log file and wireshark from an attempted discovery in 3.6

Add near similar tags close to the bottom of log4j2.xml:
<AsyncLogger includeLocation="true" name="com.serotonin.bacnet4j" level="trace"/>

You can then either restart Mango or reload them on the /ui/administration/log4j-reset page, if the Log4J reset module is installed.

Until I have reason to suspect Mango as the cause of these discovery issues, we would assess an hourly support fee for any direct assistance.

]]>https://forum.mango-os.com/post/23447https://forum.mango-os.com/post/23447Thu, 29 Aug 2019 19:35:52 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Thu, 29 Aug 2019 06:14:06 GMT]]>@phildunlap said in ES version BACnet module 3.6.0 issue compare ver. 3.5.2:

Also I notice we only see one bind address for any of these discoveries. While I wouldn't expect that to be the issue 1003 isn't in your images from 3.6 despite it being in the wireshark responding in exactly the same manner as it did in 3.5 . Can you confirm the local device configuration is the same in both versions? Can you try using a bind address of 0.0.0.0 ?

can we arrange a remote view session via Teamviewer to our pc...please let us know the time and date? when u are free. thank you

]]>https://forum.mango-os.com/post/23422https://forum.mango-os.com/post/23422Thu, 29 Aug 2019 06:14:06 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Wed, 28 Aug 2019 16:58:37 GMT]]>Also I notice we only see one bind address for any of these discoveries. While I wouldn't expect that to be the issue 1003 isn't in your images from 3.6 despite it being in the wireshark responding in exactly the same manner as it did in 3.5 . Can you confirm the local device configuration is the same in both versions? Can you try using a bind address of 0.0.0.0 ?

]]>https://forum.mango-os.com/post/23411https://forum.mango-os.com/post/23411Wed, 28 Aug 2019 16:58:37 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Wed, 28 Aug 2019 16:50:02 GMT]]>Yes, I did. They all show the same devices reporting IAms this time, but I do see that the 3.5 version is making solicitations in your captures for WhoIs specific device numbers, but there is no response in the captures where these devices are discovered so it's hard to say the significance of that. Perhaps different sets of points are enabled on the two Mango instances?

In all six submitted captures devices 10000, 1001, 1002, 1003 and 1004 responded to the initial discovery request and no other devices did.

And once again all the actual BACnet/IP protocol WhoIS discovery request bytes and the TCP/IP addressing is exactly the same in all six captures, leading once again to suggest it is not a Mango issue.

]]>https://forum.mango-os.com/post/23410https://forum.mango-os.com/post/23410Wed, 28 Aug 2019 16:50:02 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Wed, 28 Aug 2019 00:40:27 GMT]]>@techalton said in ES version bacnet module 3.6.0 issue compare ver. 3.5.2:

@phildunlap Please check your email. thank you

Did u receive my email?

]]>https://forum.mango-os.com/post/23394https://forum.mango-os.com/post/23394Wed, 28 Aug 2019 00:40:27 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Mon, 26 Aug 2019 01:01:07 GMT]]>@phildunlap Please check your email. thank you

]]>https://forum.mango-os.com/post/23293https://forum.mango-os.com/post/23293Mon, 26 Aug 2019 01:01:07 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Fri, 23 Aug 2019 21:29:08 GMT]]>Please email the wireshark logs to support@infiniteautomation.com

]]>https://forum.mango-os.com/post/23288https://forum.mango-os.com/post/23288Fri, 23 Aug 2019 21:29:08 GMT<![CDATA[Reply to ES version bacnet module 3.6.0 issue compare ver. 3.5.2 on Fri, 23 Aug 2019 08:14:25 GMT]]>Dear Philips,
Hi, I'm Eswaran, we now we are having two issues that we unable to solve

  • First issue we unable to scan some brand controller in BACnet version 3.6.0 on pc version (windows 7)

    • First attempt with BACnet version 3.6.0 on pc version (windows 7)
      0_1566538793227_217b9fc9-dcaf-4f64-ac39-6b2d7259b955-image.png

    • Second attempt with BACnet version 3.6.0 on pc version (windows 7)
      0_1566539201512_988e3511-3089-4697-b70f-2a3361ae2f3d-image.png

    • Third attempt with BACnet version 3.6.0 on pc version (windows 7)
      0_1566539672723_73109f68-87be-4233-be76-f41b2b62b9b3-image.png

      0_1566539803371_50626ca0-a1b9-4b6b-a8dd-c66e5c4303a8-image.png

    • First attempt with BACnet version 3.5.2 on pc version (windows 7)

      0_1566540622452_1dc5c007-7e03-4812-b304-62faf643301a-image.png

    • Second attempt with BACnet version 3.5.2 on pc version (windows 7)

      0_1566542378304_82bb0b30-a383-46de-a398-674b77ff8612-image.png

    • Third attempt with BACnet version 3.5.2 on pc version (windows 7)
      0_1566542518457_67008356-b59c-420b-baa7-e6b517f18864-image.png

    As you can see ..... why Dev 1003 unable to scan in Bacnet version 3.6.0 (the latest version)

The Second issue was we unable to scan the DDC properly BACnet IP on mango ES

  • 0_1566544153605_aeccc0ec-3fd1-46f8-8bcd-7ad5fd2fd348-image.png

Pls refer to the link below for Wireshark file together with the mango host file :
https://files.mycloud.com/home.php?brand=webfiles&seuuid=ec51add0c5fe1adc5cc3e5a6d5627780&name=Mango_forum_Post_230819

]]>https://forum.mango-os.com/post/23271https://forum.mango-os.com/post/23271Fri, 23 Aug 2019 08:14:25 GMT