|  | DeviceMaster 500 FirmwareThis page contains the following topics:
![[Note]](images/note.gif) | | 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). |
|
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 |
|---|
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 |
|---|
| 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 VersionUse 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.
If necessary, start PortVision DX and if the DeviceMaster 500 is not displayed in the Device List
pane, scan the network. Check the SocketServer version number of the Software Version for the DeviceMaster 500. 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 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.
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 |
|---|
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. |
|
Make sure that you have located the latest SocketServer version. If necessary, start PortVision DX, and if the DeviceMaster 500 is not displayed in the
Device List pane, scan the network. 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. 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. 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 VersionUse 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.
If necessary, start PortVision DX and if the DeviceMaster 500 is not displayed in the
Device List pane, scan the network. Right-click the DeviceMaster 500 and click Advanced > Reboot Device. Click Yes to the Confirm Reboot query.
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. Check to see if a later version is available
and if necessary, upload a new version of Bootloader.
| | 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.
Make sure that you have located
the latest Bootloader version. If necessary, start PortVision DX and if the DeviceMaster 500 is not displayed in the
Device List pane, scan the network. 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. 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.
| |
