I/A Series G3 BACnet Server (Export) Operation

Issue

I/A Series G3 BACnet Server (Export) Operation

Product Line

TAC I/A Series

Environment

I/A Series G3

Cause

Integration to I/A Series G3 from a 3rd party BACnet system

Resolution

If the I/A Series host (ENS or ENC) is licensed as a BACnet server, you can export any number of selected types of objects in the station (regardless of location) to appear as BACnet objects. As such, these objects can service client requests from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects. 

The following I/A Series G3 objects can be exported as BACnet objects (extracted from the Niagara Ax BACnet Guide). 

 

You use the Bacnet Export Manager to export Niagara objects for BACnet. To access the Bacnet Export Manager, go to 'BacnetNetwork' > 'Local Device' and double click on the 'Export Table' under the Local Device. 

You can find details on using the Bacnet Export Manager on pages 4-57 to 4-71 of the Niagara Ax BACnet Guide. The Niagara Ax BACnet Guide is installed with G3 and can be found in \niagara\niagara-3.x.xx\docs.

 

can be exported also, where they appear externally as BACnet Trend Log objects.
from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories
can be exported also, where they appear externally as BACnet Trend Log objects.
(regardless of location) to appear as BACnet objects. As such, these objects can service client requests
from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories
can be exported also, where they appear externally as BACnet Trend Log objects.