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
The trace.log, uploaded to Building Advisor Portal, may contain warnings about nsp.pin.BACnet duplicate device identifiers. This should be surfaced to the user to correct since there should be only one device per instance ID in the range of 0 to 4194302. Also, any hex IPV4 addresses should be presented as decimal and include port number. If they have the same ID and are at different addresses, they are two devices with the same instance ID. If they are at the same address, a routing loop exposes the same device via two paths (one will see two I-AMs for the same device from different sources in a packet capture).
An example is instance 111 is used by ArticCool_01 at c00f0a9fbaco (192.15.10.159:47808) and Device_111 at c00f0a9fbaco (192.15.10.159:47808) since they are at the same address, there is a routing loop, which can cause a packet storm.
2020-05-13 12:53:48.552 [1815851904] nsp.pin.BACnet Device Device_111 (ID=111) is online, but a different device (ID=111) is broadcasting (BACnetMain) 2020-05-13 12:53:48.554 [1815851904] nsp.pin.BACnet Device Device_111_«2»_c00f0a9fbac0 (ID=111) is not configured: duplicate device identifier (BACnetMain) 2020-05-13 12:53:48.590 [1813754752] nsp.pin.BACnet Device ArcticCool_01_«2»_c00f0a9fbac0 (ID=111) is not configured: duplicate device identifier (Property Value Delivery)