BACnet Static Route

[maherhodali]

Hello Everyone,

I am facing a problem in communicating with BACnet devices over MSTP static routing connection.

I am communicating with MSTP loop throw BACnet router which have (2001) network ID. under the router BACnet gateway connected to the same MSTP loop which have different BACnet network ID (103). My problem here is that devices that are connected under the gateway have a MAC address in Hex format such as 00:00:00:0C:1F:34.

How possible is WinCC can discover such devices as its only accepts MAC addresses with integer format with 6 digits only ?.
Note that maximum digits we can use in port field is 5 Digits.

If its not possible what is the alternative solution to discover devices using static routing?

please check the attached pictures for more clarifications.

[alug]

Hello Mr. Hodali,

I am not sure if I understand you configuration correctly, but can you try to enter in the static binding configuration of the device
in the panel an IP address 0.0.0.12 (corresponds to 0x0C) and a port 7988 (corresponds to 0x1F34).

If it does not work, can you please send us the config file and a screen short of the device configuration and maybe a short overview about you network configuration

best regards

Andreas

[maherhodali]

Hello Andreas,

Please find attached Network Topology and device config, in quick terms (Master Engine (Controller) With MS/TP ID "2001", the MS/TP Devices with MAC Addresses from (1-XX) as Integer Numbers and CRAC Units Gateway. (Under this Gateway MS/TP ID "103" and MAC Address format "00:00:00:12:131:63". Please find snapshot attached for it.

Also this is our trail Config File entry under BACnet Catagory:

[bacnet]

staticRouterBinding = "1002:10.241.12.11:47808"
staticRouterBinding = "1009:10.241.12.11:47808"
staticRouterBinding = "1012:10.241.12.11:47808"


staticRouterBinding = "2001:10.230.142.72:47808" #Engine
staticRouterBinding = "103:10.230.142.72:47808" #CRAC Gateway, the IP here same as Engine


staticRouterBinding = "2002:10.230.140.14:47808"
staticRouterBinding = "2003:10.230.140.12:47808"
staticRouterBinding = "2004:10.230.140.81:47808"
staticRouterBinding = "2005:10.230.140.82:47808"
staticRouterBinding = "2006:10.230.142.139:47808"
staticRouterBinding = "2007:10.230.142.7:47808"
staticRouterBinding = "2008:10.230.140.72:47808"


In Document attached you can find a detailed result from broadcasting IP scanning, How can we discover "device 80031" under MSTP 103.

Thanks

[maherhodali]

Hello Andreas,

Any updates regarding the above case ?

Thanks

[alug]

Hi Maher,

can you please send us also a screen shot how you configured the corresponding device in WinCC OA BACnet device panel

best regards

Andreas

[maherhodali]

Hi Andreas,

Sure, please find attached document.

As MS/TP network id we considered 103 as MSTP for device gateway; and also we tried to convert the port number "at the end of the MAC address" but it seems to be a very high number which is not allowed to be inserted in BACnet Driver Port/Mac address field.

Please give us the correct inputs to fulfill the requirements.

Regards

[alug]

Hi Maher,

can you try the setting in the screenhot enclosed.
If the BACnet address is not a MSTP address the keyword _MSTP does not apply.
Your address is decimal 00:00:00:12:131:63.
You have to enter this in the IP Address and Port field as
IP: 0.0.0.12 Port 33599
The 33599 is 0x833F. The 0x83 -> 131 and 0x3F -> 63

This should work. If not than we need a wireshark trace of the communication to the corresponding gateway

best regards

Andreas

[maherhodali]

Hello Andreas,

Thank you for your support.
Unfortunately; the configurations in picture above didn't work with the device mentioned.
we have tried to connect the device from different network sub-net but the device still offline (Check the attached Wireshark and WinCCOA configurations implemented).

Third party software using only (Router IP (10.230.142.72) / Device instance (820031) / Network ID (103)) was able to communicate with the device unlikely with WinCC-OA.

Regards

[leoknipp]

If you want to get futher assistance please get in contact with your common WinCC OA support or the WinCC OA consulting team if you have a valid consulting pool.

Please take into account that the WinCC OA Portal is no replacement for the common WinCC OA support. The analysis of the provided wireshark trace will take some time and therefore you have to get in contact with the common WinCC OA support.

Best Regards
Leopold Knipp
Senior Support Specialist

[maherhodali]

Hello Leo,

Thanks for the clarifications.

We need only your confirmation that such "BACnet communication" is supported by WinCC OA BACnet Manager, will start our trouble-shooting after your confirmation.

in case that WinCC OA doesn't have a clear procedure will try to go with a different communication approach to solve this.

Regards

Maher Hodali