# Bacnet Local Device **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [July 30, 2024, 2:37pm UTC](https://forum.inductiveautomation.com/t/bacnet-local-device/93913 "2024-07-30T14:37:05Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 30, 2024, 2:47pm UTC](https://forum.inductiveautomation.com/t/bacnet-local-device/93913/2 "2024-07-30T14:47:36Z")
The **binding** address is the Ignition side of the connection. The address Ignition listens to on **its** end of whatever protocol is involved. (0.0.0.0 is the internet wildcard address.) So, never the right setting to use for some **other** system's IP address. This is your third topic in a few days asking the same question. See here: > [@Ignition communication to BacNet MS/TP using BASrouterLX](https://forum.inductiveautomation.com/t/ignition-communication-to-bacnet-ms-tp-using-basrouterlx/93634): > > I wonder if anyone has set up a Contemporary Control's BASrouterLX-B device on Ignition to connect to a device that only communicates through BacNet MS/TP. I currently have a project that needs to use the points on the MS/TP device on a Vision application to test the functionality of the unit it is being used as the controller. Any help configuring the router's configuration setting and the Ignition device connection both local and remote would be appreciated. and here: > [@Bacnet/MS/TP to Bacnet/IP (when initialized, the object\_list is empty)](https://forum.inductiveautomation.com/t/bacnet-ms-tp-to-bacnet-ip-when-initialized-the-object-list-is-empty/93811): > > I’m having trouble discovering a BACnet MS/TP device (LS-1628) using Ignition through a BasRouter LX. Setup: • BasRouter LX: • IP: 192.168.92.68 • Ignition: • Points to BasRouter at 192.168.92.68, Port 47808 Issue: The LS-1628 is detected but its object list is empty in Ignition. Steps Taken: 1. Verified MS/TP and IP settings. 2. Ensured unique network numbers. 3. Increased discovery timeouts/retries. 4. Monitored BACnet traffic for who-is/i-am messages. 5. Tested direct MS/TP communicatio… That is against [this forum's rules](https://forum.inductiveautomation.com/faq). Your other posts probably didn't get an answer because the volunteers who hang out on this forum don't **have** an answer. Bacnet MS/TP has few users in this niche of the SCADA world, so we **just don't know**. If you don't get answers to a topic in several days, it is reasonable to add a comment to "bump" the topic, in case some volunteer here missed it the first time. After that, you should contact support. (This forum is **not** support.) Or otherwise pay someone to help you. --- _[View the full topic](https://forum.inductiveautomation.com/t/bacnet-local-device/93913)._