Standard objects: are collections of objects that are stored and executed on the server, rather than the controller. You may find them useful in expanding the logical control application with supporting server objects that do not reside or execute in the controller. For example, you may add graphics and trend charts to help visualize the zone control application of a SmartX IP controller. They execute in the EcoStruxure BMS server and not in the controller.
BACnet Objects: are collections of objects that are stored and executed on the SmartX Controller. For example, BACnet values, IO points, Trends, Schedules and Programs.
Example:
You then create Script program B as an EcoStruxure Building Operation Script program that executes in the EcoStruxure BMS server.
Both Script program A and Script program B may look similar in WorkStation and visually, they also coexist in the SmartX IP controller Application folder. However, SmartX IP controllers are BACnet device objects, while EcoStruxure Building Operation objects are not.
To differentiate them, notice the differences in the accompanying icons in the sample MP Series controller. You can also view the Object category property in the List View to determine which is the standard object.
BACnet Objects: are collections of objects that are stored and executed on the SmartX Controller. For example, BACnet values, IO points, Trends, Schedules and Programs.
Example:
You then create Script program B as an EcoStruxure Building Operation Script program that executes in the EcoStruxure BMS server.
Both Script program A and Script program B may look similar in WorkStation and visually, they also coexist in the SmartX IP controller Application folder. However, SmartX IP controllers are BACnet device objects, while EcoStruxure Building Operation objects are not.
To differentiate them, notice the differences in the accompanying icons in the sample MP Series controller. You can also view the Object category property in the List View to determine which is the standard object.