This article provides an overview of the different options within GI.bench for writing a new or updating an existing configuration on a controller.
Write
Using the standard write function (located in the menu bar without a dropdown), only the modified configurations are saved to both the controller and modules. The write action is performed on the controller with the corresponding unique identifier (UID) as identified in the GI.bench configuration within the network. Configurations for modules that remain unchanged are not overwritten during this process.
Write controller (Force all)
The feature operates similarly to the standard write function, with the difference that it forcibly writes the entire configuration from GI.bench to both the controller and modules. This action occurs irrespective of whether the configuration has been modified. The write action is performed on the controller with the corresponding unique identifier (UID) as identified in the GI.bench configuration within the network.
Pre-configure controller
The configuration from GI.bench is applied to the controller, while the module configuration is not immediately written to the modules. This feature is useful for pre-configuring a controller, especially in scenarios where, for instance, the controller is set up in an office without currently connected modules. Subsequently, when the modules are physically connected, they will automatically receive the stored configuration in the controller.
Write to another controller
Similar to the standard write function, this feature enables writing the configuration to another controller with a different unique identifier (UID). You need to determine which UID should be modified. If you wish to retain the UID from the project configuration in GI.bench or the current controller, a prompt will appear for your decision.