DeviceMaster 500 Firmware

This page contains the following topics:

Latest Files

[Note]
Note

You will need PortVision DX (v3.03 or higher) to upload the DeviceMaster LT firmware (.cmtl) files. Optionally, you can use the Firmware Uploader Utility for Linux (v1.06 or higher).

NameFilesDescription
Bootloader

4.25

Bootloader is the RedBoot operating system that runs the device during the power on phase, which then starts the default application on the DeviceMaster 500.

You can check the Bootloader version.

You should update to Bootloader v3.23 or higher, if you install the NS-Link driver v10.10 or higher for Windows or NS-Link' driver 5.04 or higher for Linux.

You can review the firmware History file for the latest updates and enhancements.

SocketServer

11.11

SocketServer is the default application that runs on the DeviceMaster 500 and is for use with the NS-Link device drivers and applications that support Winsock connections, for telnet type connections, and for Serial Tunneling. You can use SocketServer to configure DeviceMaster 500 ports for TCP/IP socket access from the other hosts or for serial tunneling.

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

You can use PortVision DX to check the SocketServer version and if necessary, update SocketServer. If you do not want to use PortVision DX to update SocketServer, you can use RedBoot. Refer to Uploading Firmware in the RedBoot Procedures section of the DeviceMaster 500 Installation and Configuration Guide.

You can download and unzip the SocketServer help file and open the ssvr_help.htm. This is the help system embedded in SocketServer.

You can review the firmware History file for the latest updates and enhancements.

Software Dependencies

After programming the IP address into the DeviceMaster 500, you are ready to verify that the DeviceMaster 500 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 500. You can check the Bootloader version on the DeviceMaster 500 against the latest Bootloader version and if necessary, update Bootloader.

    [Note]
    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 500 against the latest version and if necessary, update SocketServer.

    [Note]
    Note

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

Checking the SocketServer Version

Use this procedure to check the SocketServer version that resides on the DeviceMaster 500 using PortVision DX.

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

  1. If necessary, start PortVision DX and if the DeviceMaster 500 is not displayed in the Device List pane, scan the network.

  2. Check the SocketServer version number of the Software Version for the DeviceMaster 500.

  3. Check the Pepperl+Fuchs Comtrol, Inc. web site to see if a later version is available.

    If the downloadable version is newer than the version shown in the DeviceMaster 500, download the file and then go to Updating SocketServer

  4. If the SocketServer version on the DeviceMaster 500 is current, you are ready to install an NS-Link device driver for tty or COM ports, or you are ready to configure the sockets.

Updating SocketServer

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

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

[Note]
Note

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

  1. Make sure that you have located the latest SocketServer version.

  2. If necessary, start PortVision DX, and if the DeviceMaster 500 is not displayed in the Device List pane, scan the network.

  3. Right-click the DeviceMaster 500 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.

  4. 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 500. The DeviceMaster 500 will reboot itself during the upload process.

  5. Click OK to the advisory message about waiting to use the DeviceMaster 500 until the status reads ON-LINE. In the next polling cycle, PortVision DX updates the Device List pane and displays the new SocketServer version.

Checking the Bootloader Version

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

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

  1. If necessary, start PortVision DX and if the DeviceMaster 500 is not displayed in the Device List pane, scan the network.

  2. Right-click the DeviceMaster 500 and click Advanced > Reboot Device.

  3. Click Yes to the Confirm Reboot query.

  4. Right-click the DeviceMaster 500, 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.

  5. Check to see if a later version is available and if necessary, upload a new version of Bootloader.

Updating Bootloader

[Note]
Note

Technical Support does not recommend updating Bootloader across a WAN. For best results, connect the DeviceMaster 500 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 500 must be sent into Pepperl+Fuchs Comtrol, Inc. so that it can be re-flashed.

If you are not successful uploading SocketServer into the DeviceMaster 500, 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 500 using PortVision DX.

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

  1. Make sure that you have located the latest Bootloader version.

  2. If necessary, start PortVision DX and if the DeviceMaster 500 is not displayed in the Device List pane, scan the network.

  3. Right-click the DeviceMaster 500 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.

  4. Click Yes to the Upload Firmware message that warns you that this is a sensitive process.

  5. 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.


nice color