Issue
Attempting to map a 3rd party bacnet alarm and there is no way to navigate down to the object
Click here to see the following snapshots illustrating the issue
Environment
SmartStruxure
Windows XP SP3
Windows 7
Cause
We currently do not support external alarming (that is a BACnet alarm in the AS or ES monitoring a property in some other device.) This is being considered for a future revision.
Resolution
If the 3rd party device does not support alarming they would have to create an SmartStruxure alarm to monitor it.
An alternative work around if the 3rd party device supports alarms (Ex. Veeder Root in this case) is to create a BACnet Value in the AS (or ES) and then binding it from the Veeder Root object to the local value, and configure alarming from there.
