@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.
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