Timeout on all BACnet devices after upgrade from ma-core 2.8.8 to 3.3.1

Pedro

BACnet datasource is reporting timeouts for, it seems, all BACnet sources. e.g.:

15:33:03: 'BACnet': Error reading value for point MSB-B - MSB-B Frequency L2 (AC1) (1s): errorClass=device, errorCode=timeout

I don't think any of the BACnet eGauge devices are working after the Mango upgrade.

The following errors are filling up ma.log once per second:

ERROR 2018-02-28T15:33:27,171 (com.serotonin.bacnet4j.util.PropertyUtils.requestPropertiesFromDevice:211) - Timeout while finding device 222 
com.serotonin.bacnet4j.exception.BACnetTimeoutException: No response from instanceId 222
    at com.serotonin.bacnet4j.LocalDevice$2.get(LocalDevice.java:710) ~[bacnet4j-4.1.3.jar:?]
    at com.serotonin.bacnet4j.util.PropertyUtils.requestPropertiesFromDevice(PropertyUtils.java:207) ~[bacnet4j-4.1.3.jar:?]
    at com.serotonin.bacnet4j.util.PropertyUtils.lambda$readProperties$0(PropertyUtils.java:168) ~[bacnet4j-4.1.3.jar:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
ERROR 2018-02-28T15:33:27,171 (com.serotonin.bacnet4j.util.PropertyUtils.requestPropertiesFromDevice:211) - Timeout while finding device 223 
com.serotonin.bacnet4j.exception.BACnetTimeoutException: No response from instanceId 223
    at com.serotonin.bacnet4j.LocalDevice$2.get(LocalDevice.java:710) ~[bacnet4j-4.1.3.jar:?]
    at com.serotonin.bacnet4j.util.PropertyUtils.requestPropertiesFromDevice(PropertyUtils.java:207) ~[bacnet4j-4.1.3.jar:?]
    at com.serotonin.bacnet4j.util.PropertyUtils.lambda$readProperties$0(PropertyUtils.java:168) ~[bacnet4j-4.1.3.jar:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]

etc for each IP device.

Note that my BACnet datasource was created back in the day when there was only one BACnet datasource communicating with multiple IP addresses. Joel confirmed that in spite of this, it should still work after the upgrade.

The point timestamps are frozen at the time before the upgrade.

JoelHaggar

try running a whois on one of the BACnet Data Sources and see if it discovers the eGauges. You might also share your local device settings and other settings as something might need to be changed. I have an eGauge and the latest Mango works fine with it.

Pedro

@joelhaggar Was the datasource that is "working fine" created with the old Mango BACnet datasource that groups all IPs under a single datasource?

Pedro

@joelhaggar Send WhoIs reports "Listening for messages..." and does not show any responses.

The object list is also not responding.

Remote device object list
Device instance number 	211
No response from instanceId 211

JoelHaggar

@pedro I'm not sure what version it was created in. Are the eGauges on the same subnet as the Mango server? Please share your local device settings as well.

Pedro

@joelhaggar Yes, they're all on the same subnet. I emailed a JSON export of my BACnet datasource to the support email. I assume that's what you were asking for. The JSON is somewhat terse.

Pedro

BACnet is working now:

I upgraded the eGauge firmware and set each eGauge broadcast mask back to what I had before the V3 upgrade (192.200.255.255) per eGauge recommendations. I did not change the netmask. eGauge does not think the firmware upgrade would affect the BACnet discovery. Nonetheless, Mango subsequently found the eGauges via BACnet WhoIs, but the old BACnet points were still not updating. Mango allowed me to add new BACnet points from the eGauges, and the new (redundant) BACnet point updated, but none of the old points updated.

Disabling/enabling points, or disabling/enabling the BACnet datasoure, also did not cause the old BACnet points to update. The old BACnet points finally started updating after I saved the BACnet datasource, even though I had not made any changes to it. The only LAN switch/router configuration settings changed for troubleshooting were "IGMP snooping" and "Flood unknown multicast traffic," but they were subsequently re-enabled, and BACnet WhoIs still works. Neither LAN setting had any effect on BACnet.

Thanks for your help.