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.
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 request. Hence the need to change the broadcast address to 192.168.69.255.
I hope the above would help @techalton -
@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.
-
@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-resetpage, 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.
-
@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 @techaltonThanks for sharing @cwangv. when I change the broadcast address to 192.168.69.255.im unable to scan any device at all
-
@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.
-
Thanks for being persistent, techalton, we are examining the files and information you submitted.
-
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?
-
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.
-
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?
-
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.
-
@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.
-
@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!
-
@terrypacker Now the new version working fine. I'm able to detect all my BACnet devices. thank you for your support.
