BACnet Devices uninitialized


BACnet Devices uninitialized

Welcome, you have tagged this as Ignition81, however your screenshot is not from Ignition. Please explain what you need to discuss.

This forum is for discussion of Ignition SCADA topics, and whilst they have a BACnet driver, it doesn't appear from your screenshot that you are using it... please clarify.

1 Like

Bacnet uninitiated

@Kevin.Herron are simulators supported?

yes its supported

Please link me, because I've read the manual and I see no mention of it.

Just because BACnet hardware is supported doesn't mean BACnet simulators are.

I've used that same BACnet simulator for testing, so that shouldn't be an issue. Could you share your logs and your local and remote device configurations?

1 Like

CoreCertificationTest_Ignition_logs_20230511-1938.idb (2.0 MB)

The Bacnet device constantly switches between Initializing and Uninitialized

I have enclosed the simulator settings

Both Ignition and the simulator appear to be on the same machine, so could you change the bind port for your local device to something other than 47808 since the simulator also defaults to the same port. I typically just use 47809. Then I would suggest restarting the gateway.

After looking at the logs, it looks like the local device did not get initialized because that port is in use already. The suggestion above should clear that up.

Error initializing LocalDevice "BACNet_Test". bindAddress=, bindPort=47808, networkNumber=1, deviceNumber=1000 Address already in use: Cannot bind at java.base/ Method) at java.base/ Source) at java.base/ Source) at java.base/ Source) at com.serotonin.bacnet4j.npdu.ip.IpNetwork.initialize( at com.serotonin.bacnet4j.transport.DefaultTransport.initialize( at com.serotonin.bacnet4j.LocalDevice.initialize( at com.serotonin.bacnet4j.LocalDevice.initialize( at com.inductiveautomation.ignition.drivers.bacnet.LocalDeviceManager.addLocalDevice(LocalDeviceManager.kt:172) at com.inductiveautomation.ignition.drivers.bacnet.LocalDeviceManager.onStartup(LocalDeviceManager.kt:65) at com.inductiveautomation.ignition.common.lifecycle.AbstractLifecycle.startup( at com.inductiveautomation.ignition.drivers.bacnet.BacnetModuleHook.startup(BacnetModuleHook.kt:77) at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl$LoadedModule.startup( at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.startup( at com.inductiveautomation.ignition.gateway.IgnitionGateway.startupInternal( at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.startup( at com.inductiveautomation.ignition.gateway.IgnitionGateway.initRedundancy( at com.inductiveautomation.ignition.gateway.IgnitionGateway.lambda$initInternal$0( at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ at java.base/java.util.concurrent.Executors$ Source) at java.base/ Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$ Source) at java.base/ Source)

Thanks, It 's worked. I was changing the port on both simulator and local device. But NOW I just changed the port no in local device but NOT in Simulator. That made the BACnet device connection to go to INTIALIZED state. It is the final state or it will change from "Initialized" to "Running" as well. If it is, when it will change to RUNNING state.

Since BACnet uses UDP which is "connectionless", Initialized is the final state.

Here's a good BACnet KBA put out by our support department that may be worth a read.


Thank You