more quick actions
minimize quick actions
Topic starter
Hello Team,
How can we configure the attached BACnet communication in PcVue?
Thanks & Regards,
Nitesh Dongare
Posted : 19/12/2022 7:28 pm
hello,
With two network interfaces, two different device id and two different network id.
hope it helps.
Posted : 19/12/2022 7:32 pm
Topic starter
Hello,
We tried with two different networks interfaces, two different ID & network ID. Below are the observations :
1. In online scan can we can see only BACnet devices that are in IP series of first network interface.
2. If we add the device by giving static binding from the second IP series then connections getting broke.
Please go through attached screenshots for details on configuration and result.
Thanks & Regards,
Nitesh Dongare
Posted : 20/12/2022 11:39 am
Hello,
As Brice told, the network IDs have to be different and also not 0 (0 is not suitable for this case).
And if you use BACnet MSTP ou over Lontalk, don't use network ID defined by any of these BACnet networks.
In this case, device IDs can be the same because it's the same BACnet device object for both interfaces.
You need to restart the network or PcVue after apply the changes.
Static binding shouldn't be necessary for this case. The devices seem to be in the same sub-network that BACnet client.
Regards
Posted : 20/12/2022 7:43 pm
Hi,
Just for my information, the networkID we configure in PcVue network interface shall be the same than declared in the Device?
Nico
Posted : 20/12/2022 10:06 pm
Topic starter
Hello,
When we configured two network interfaces with ID 1 & 2 respectively then we were able to discover & connect with all the devices. Thank you Brice, Jérôme & Nico.
Thanks & Regards,
Nitesh Dongare
Posted : 21/12/2022 6:54 pm
Hello,
By convention, a network-number identifies one network. So all BACnet server devices on a same network should have a same network-number.
Specialy when BACnet router/gateway are present to distinguish the networks (required for messages routing).
Whatever, classic cases with only BACnet/IP devices, different network-number shouldn't disturb the communication.
Posted : 21/12/2022 11:28 pm
Thank you for the answers.
My understanding about the original problem: The main trick you gave us was that one "the network IDs have to be different and also not 0 (0 is not suitable for this case)".
Nitesh did already the test with 2 network IDs but he kept the first network with the number 0. That's why it didn't work.
So the question is: Why 0 is not suitable for this case?
Nico
Posted : 22/12/2022 12:14 am
According to the standard, 0 indicates that the Network_Number is not known or cannot be determined. It is also possible for the stack API to block routing with 0 and when used with multiple IP interfaces the stack API works as a BACnet router.
Posted : 22/12/2022 5:24 pm