ACE Network architecture
Figure 1. Expanded Ace Edge Network in the Nav Tree
The AceEdgeNetwork is the top-level parent component, and by default has typical component slots such as, Health and other status properties, Alarm Source Info, Ping Monitor, Tuning Policies, Heart Beat, and etc. The Property Sheet is the default view for the AceEdgeNetwork.
The Local (Ace Device) is the second-tier component in the network. It has typical device status properties, a Points Extension, and the ACE App. There can be only one child device in the AceEdgeNetwork, as such the AceDevice is included with the network component. The Property Sheet is the default view for the AceDevice.
The AceDevicePointsExt is the parent container for proxy points. The Ace Points Manager is the default view for the PointsExt.
The ACE App is a child of the Local AceDevice. The App folder is a
The ACE App has a number of configurable properties related to scan frequency, scan level, and order. When the ACE application is running it constantly scans components. Setting the scan “Level” is how you configure the frequency of component scanning, while “Order” controls the order of execution within a scan level. For more details see, “ace-AceApp” and “ace-AceCompManager” in the “Components and views" chapter of this guide.
The ACE driver has an extensive catalog of its own ACE components. You drag ACE components onto the Ace Wire Sheet view to build the Ace App.
Figure 2. ACE Catalog with expanded Ace Io folder
NOTE: The ACE Catalog functions like a palette, in that you access it via the
CAUTION: Protect against unauthorized access by restricting physical access to the computers and devices that manage your building model. Set up user authentication with strong passwords, and secure components by controlling permissions. Failure to observe these recommended precautions could expose your network systems to unauthorized access and tampering.