Example 2: Image update for a CX9010 via the TwinCAT Management Server

Step 1: Project creation

First create a new project in the configurator. Enter a project name and a storage location for creating a .mscp (Management Server Config Project) file containing the individual project information.

Step 2: Update configuration

To enable data exchange between the central server and the various devices create the NetShare folder and enter it in the Configuration Project under Groups. Confirm with Apply.

Step 3: Adding devices

TwinCAT routes must be available for the devices with which you want to work. You can do this conventional via the TwinCAT System Manager or directly in the configurator by right-clicking on the selected device in the Network Environment. In the context menu that opens you can use the Add Route option and enter a route in the same way as in the System Manager. You can now copy the devices via drag and drop from the Network Environment into the window of the Devices subitem. Alternatively you can use the Add button in the Devices window. If the Cab file has been installed correctly on the target device, an "X" will appear in column Connected after a few seconds. Once this "X" appears the target device is able to process the scripts created in the configurator.

Further device information can be obtained by selecting a device in the Configuration Project.

Step 4: Adding actions

Under the Actions subitem of a group you can create script-based actions to be started on the devices.

For this example three actions will be created. The first action updates the files on the image of the previously selected CX9010 from HMI 2.26 to HPS 3.12. The second action is the real image update that is rewriting the boot.bin on the device. The last action is to copy a required additional file.

Actions can be added by right-clicking on the subitem New in the context menu of the Configuration Project or via Add in the Actions window.

For the first action you have to select the script Cx90xxImageUpdatePrep. Enter the folder for the new image in the SourceFolder field via the browser button. This is basically the folder containing the "www", "System" and "UPnP" Directory. Select "\Hard Disk" as the TargetFolder for an image update on the device. The preparations for the first action are now complete.

For the second Action the Cx90xxImageUpdate script should be selected. Enter the boot.bin of the new image in the Filename field. The targetfolder field should contain "\temp". The preparations for the second action are now complete.

[optional] For the third action please select the Copyfile script. The aim is to copy an important production file to the device. Under FileName you can navigate to the required file. Specify the target directory under TargetFolder and the copy option under CopyFlag. In this case copy option "Simple" is selected, which means a simple copy process.

Step 5: Start update

The update can now be started from various places in the configurator. One option is the Play button in the configurator toolbar. This option would start all activated actions for all available groups. Alternatively, you can select the respective device in the Configuration Project and start the configured actions for this device in the window that opens.

Under Device Status you can monitor the progress of the operations. Once Finished appears under Update State, highlighted in green, the operations for the respective device have been completed successfully. More detailed information about the device-specific update can be obtained by clicking on the respective device in the Configuration Project.

Step 6: Final steps

The script Cx90xxImageUpdate.script replaces all system files on the CX and resets all settings and registry entries (except the routes information). The device is restarted to complete the image update. The routes information is stored to ensure that the device is immediately available again. This means the route to your server PC continues to be available and does not have to be refreshed manually.