After programming the IP address into the DeviceMaster (DeviceMaster PRO, DeviceMaster RTS, or DeviceMaster Serial Hub), you are ready to verify that the DeviceMaster contains the latest firmware or appropriate firmware for your environment.

You may need to update the existing firmware or upload firmware to meet the requirements for your site.

Bootloader is the RedBoot operating system that runs the device during the power on phase, which then starts the default application on the DeviceMaster. You can check the Bootloader version on the DeviceMaster against the latest Bootloader version and if necessary, update Bootloader.

Note
Typically, you should not update Bootloader unless advised to do so by Technical Support or a requirement stated in the Firmware Downloads table.

SocketServer is loaded from the factory by default and is used with the NS-Link device drivers and applications that support Winsock connections, for telnet type connections, and for Serial Tunneling. You can check the SocketServer version on the DeviceMaster against the latest version and if necessary, update SocketServer.

Note

Technical Support recommends that you update to the latest version of SocketServer before installing an NS-Link device driver or configuring socket ports.

This step is not required if you planning on uploading Modbus Server.

Upload Modbus Server firmware for applications that require remote Modbus/RTU communications such as OPC servers. You can download the latest version and upload Modbus Server on the DeviceMaster.

Checking the SocketServer or Modbus Server Version

Use this procedure to check the SocketServer or Modbus Server version with PortVision DX that resides on the DeviceMaster. SocketServer is the default firmware loaded on the DeviceMaster.

Optionally, you can use RedBoot to check the firmware version. See the RedBoot Procedures section in the DeviceMaster Installation and Configuration Guide.

If necessary, start PortVision DX and if the DeviceMaster is not displayed in the Device List pane, scan the network.
Check the SocketServer or Modbus Server version number of the Software Version for the DeviceMaster.
Check to see if a later version is available.

If the downloadable version is newer than the version shown in the DeviceMaster, download the file and then go to Updating SocketServer or Uploading or Updating Modbus Server.

Updating SocketServer

Use this procedure to upload the latest version of SocketServer into the DeviceMaster using PortVision DX.

Optionally, you can use RedBoot to upload SocketServer. See the RedBoot Procedures section in the DeviceMaster Installation and Configuration Guide.

Note
Technical support does not recommend updating firmware across a WAN. For best results, connect the DeviceMaster directly to a PC or laptop to upload SocketServer.

Make sure that you have located the latest SocketServer version.
If necessary, start PortVision DX, and if the DeviceMaster is not displayed in the Device List pane, scan the network.
Right-click the DeviceMaster in the Device List pane (lower) for which you want to update, click Advanced > Upload Firmware, browse to the SocketServer .bin file, and then click Open.
Click Yes to the Upload Firmware message that warns you that this is a sensitive process. It may take a few moments for SocketServer to upload onto the DeviceMaster. The DeviceMaster will reboot itself during the upload process.
Click Ok to the advisory message about waiting to use the DeviceMaster until the status reads ON-LINE. In the next polling cycle, PortVision DX updates the Device List pane and displays the new SocketServer version.

Uploading or Updating Modbus Server

Use this procedure to upload the latest version of Modbus Server into the DeviceMaster using PortVision DX.

Note
Technical support does not recommend updating firmware across a WAN. For best results, connect the DeviceMaster directly to a PC or laptop to upload Modbus Server.

Make sure that you have located the latest Modbus Server version.
Execute the Modbus Server .msi file.
1. Click Run to start the file installation procedure or Save to save the file to your site, and then execute the .msi file and click Start to begin the file installation procedure.
2. If necessary, click Run to any Internet Security warnings.
3. Click Next at the Modbus Server Setup Wizard.
4. Read and click I accept the terms in the License Agreement and then Next.
5. Click Next to install Modbus Server in the default directory (C:\Comtrol\Modbus_Server\) or browse to another location. Make sure that you remember the path where you place the files because you will need to access the .bin file during the installation procedure.
6. Click Install and the click Finish.
If necessary, start PortVision DX, and if the DeviceMaster is not displayed in the Device List pane, scan the network.
Right-click the DeviceMaster in the Device LIst pane (lower) for which you want to update, click Advanced > Upload Firmware, browse to the Modbus Server .bin file, and then click Open.
Click Yes to the Upload Firmware message that warns you that this is a sensitive process. It may take a few moments for Modbus Server to upload onto the DeviceMaster. The DeviceMaster will reboot itself during the upload process.
Click Ok to the advisory message about waiting to use the DeviceMaster until the status reads ON-LINE. In the next polling cycle, PortVision DX updates the Device List pane and displays the Modbus Server version.
Configure the port characteristics for your devices.

Checking the Bootloader Version

Use this procedure to check the Bootloader version on the DeviceMaster using PortVision DX.

Optionally, you can use RedBoot to check the bootloader version. See the RedBoot Procedures section in the DeviceMaster Installation and Configuration Guide.

If necessary, start PortVision DX and if the DeviceMaster is not displayed in the Device List pane, scan the network.
Right-click the DeviceMaster and click Advanced > Reboot Device.
Click Yes to the Confirm Reboot query.
Right-click the DeviceMaster, click Refresh Device as many times as necessary to catch the reboot cycle in the Device List pane. The Bootloader version is briefly displayed during the reboot cycle before SocketServer loads.
Check to see if a later version is available and if necessary, upload a new version of Bootloader.

Updating Bootloader

Note

Technical Support does not recommend updating Bootloader across a WAN. For best results, connect the DeviceMaster directly to a PC or laptop to upload Bootloader.

Make sure that power is not interrupted while uploading Bootloader. Power interruption while uploading Bootloader will require that the DeviceMaster must be sent into Comtrol so that it can be reflashed.

If you are not successful uploading SocketServer into the DeviceMaster, do not upload Bootloader. If the NS-Link driver for Windows has been installed, make sure that the driver is disabled through the Device Manager before uploading Bootloader.

Use this procedure to upload the latest version of Bootloader into the DeviceMaster using PortVision DX.

Optionally, you can use RedBoot to upload Bootloader. See the RedBoot Procedures section in the DeviceMaster Installation and Configuration Guide.

Make sure that you have located the latest Bootloader version.
If necessary, start PortVision DX and if the DeviceMaster is not displayed in the Device List pane, scan the network.
Right-click the DeviceMaster in the Device List pane (lower) for which you want to update, click Advanced > Upload Firmware, browse to the Bootloader .bin file, and then click Open.
Click Yes to the Upload Firmware message that warns you that this is a sensitive process.
Click Ok to the second Upload Firmware message and then click Refresh until the Bootloader version displays in the Device List pane, which should show the new version.

	06/11/14	Home \| Comtrol Support
	Copyright © 2014 Comtrol Corporation.