Follow along for an enriching discussion with our CEO, Peter Herweck, and industry leaders for a captivating Global Keynote at #InnovationSummit Paris 2024. Watch recording and join the #ImpactMaker movement!️
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New InviteClose
Announcements
Find the latest Product Announcesments on The Exchange here: PA-00941 - EcoStruxure Building Advisor - New Features Q2 2023
Incorrect BACnet Network IDs can contribute to BACnet Communication Loops and slow/no communications. The current solution is to setup and run a search for BACnet Network, expose columns and manually inspect and change. To manually inspect, one has to know BACnet communications strategies.
DISPLAY 1: Site IP network BACnet Network ID
NOTIFICATION 1: BACnet Network IDs must match on site IP network
LEVEL: Routine
EXPLANATION: BACnet routers connected to site network need to be assigned the same BACnet Network ID
NOTIFICATION 2: Routed Networks should all have site Unique Network IDs
LEVEL: Critical
EXPLANATION: Routing to identical Network IDs will cause routing loops if the same network or slow communications if different networks
NOTIFICATION 3: BACnet Network name does not include BACnet Network ID
LEVEL: Informational
EXPLANATION: Including BACnet Network ID in BACnet network name helps installers and maintains know what network they are working on.
NOTIFICATION 4: Secondary IP Network should always use site-wide unique Network ID
LEVEL: Informational
EXPLANATION: Secondary IP network should be configured with unique site-wide unique ID in case BACnet network is assigned to Primary IP.
NOTIFICATION 5: MSTP Network should always use site-wide unique Network ID, unless there is a reason for two or more Automation Servers to be on the same MSTP Network.
LEVEL: Informational
EXPLAINATION: Few configurations require multiple AS per MSTP. However, only 1 Automation Server can be router to Site IP Network via Primary IP Port.
RECOMMENDED VALUES: NA
REQUIRED:
All Site Servers' pubconfig.db
ES/AS Communications Server & IP List
LOGIC:
Create table of all site objects by find all Object Type = bacnet.NetworkProxy, bacnet.IPDataLink, bacnet.MSTPDataLink and create table of Property= NetworkId and IPaddress
For each ES/AS where bacnet.IPDataLink matches ES/AS Communications Server & IP List, Set as Primary IP Network
Search all Primary IP Networks and identify most common Primary IP Network NetworkId display as Display 1, and those not matching, Notification 1.
For each AS, where bacnet.IPDataLink does not match ES/AS Communications Server & IP List, Set as Secondary IP Network
Any Secondary IP Network, MSTPDataLink, NetworkProxy NetworkId should be unique site wide to all NetworkIds, if not:
verify no Primary IP on that AS,
if Secondary Network, Flag Notification 4
if MSTP network, Flag Notification 5
else Notification 2.
Of all NetworkProxy, IPDataLink, MSTPDataLink, if Name is not "IP Network" and does not include NetworkID, then Notification 3