Perform this action to download the logic to the ControlProgram of an online device. If there is no modification done to the logic from previous download to that controller apart from Setpoints value changes, Schedule block configuration changes, Wall module block configuration changes, Day Light Savings changes, tool performs a quick download of the configuration.
Perform this action to upload application in the controller to the ControlProgram. If the application in the online controller matches with application in Control Program, invoking this Action does only a quick upload. In the case of quick upload, tool only uploads Network Setpoint values, Schedule, Wall Module, Day Light Savings configurations. If the Control Program application is different than that in the device, tool perform a full upload.
Perform this action to change the device instance number in the online device through Niagara. Change the device Instance number in Device Object under Config object of a device and click Action to write the changed value to the controller.
The Generate Network Objects action on device level creates the object references from control program to create the binding between the objects. These Object references are listed and used in Add Bindings dialog to make the binding between the devices.
The Input points object references are displayed in the Target details of
Add Bindings dialog box.
The Output points object references are displayed on the Source details of
Add Bindings dialog box.
The Binary Output and Modulating Output points have 16 priority input object references and an output object reference on device level. The priority object references are displayed in Target details and output object reference are displayed in Source details of Add Binding dialog box.
On restarting the station the object references are removed from the device if it is not involved in binding.
The object references for binding are created using the Generate network
objects action on the device level (refer Generate network Objects action
description).
The Clear slots action is used to remove the object references that are not
involved in binding.
The Clear Bindings action on device level removes the binding information
from the controller.
The clear binding action changes the bound links to new Links. If the device is
having the obsolete Links then the obsolete links are removed from the
controller. These can be observed in Bacnet Link manager view (see Types of Link
Status section for more information).
The clear binding action can be performed only in the following conditions:
The Learn Links action on device level learns the bound links from the device.
When the bound link is deleted from the link manger view then the link are
displayed as obsolete link. If the user wants to restore the bound link then the
user can perform the learn links action on the device. After learn Links the
obsolete link are changed to bound link.
The Learn Links action can be performed only in the following conditions:
The Learn Links action first checks if the device from which the link is learnt is having the object reference at the device level, if its not present it will look for the object in the control program. But for the other device involved in binding it only checks for the object reference at the device level and if the reference is not found it would create default object references. In this case the Fetch Object Names action loads the control program and fetch the exact name of the object and rename the default name.