Installation and Configuration Guide
Trademark Notices Comtrol, NS‐Link, and DeviceMaster are trademarks of Comtrol Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. HyperTerminal is a registered trademark of Hilgraeve, Inc. Portions of SocketServer are copyrighted by GoAhead Software, Inc. Copyright © 2001. GoAhead Software, Inc. All Rights Reserved. Other product names mentioned herein may be trademarks and/or registered trademarks of their respective owners.
Table of Contents Introduction ............................................................................................................................9 Supported DeviceMaster Models ............................................................................................................... 9 DeviceMaster Port Usage ............................................................................................................................ 9 Installation Overview .....................................
Table of Contents Device Driver (NS-Link) Installation ..............................................................................51 Overview........................................................................................................................................................ 51 Before Installing the NS-Link Driver...................................................................................................... 51 Linux Installations .................................................
Table of Contents Connecting Serial Devices .................................................................................................91 DB9 Connectors ........................................................................................................................................... 91 DB9 Null-Modem Cables (RS-232) .......................................................................................................... 92 DB9 Null-Modem Cables (RS-422) .....................................
Table of Contents Restoring Serial Port Settings................................................................................................................ 119 NS-Link COM Port ................................................................................................................................. 120 Socket Port ..............................................................................................................................................
Table of Contents Troubleshooting and Technical Support......................................................................149 Troubleshooting Checklist ..................................................................................................................... 149 General Troubleshooting......................................................................................................................... 150 Testing Ports Using Port Monitor (PMon2) ............................................
Table of Contents viii - Table of Contents DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Introduction This section discusses the following topics: • Supported DeviceMaster Models on Page 9 • DeviceMaster Port Usage (below) • Installation Overview on Page 9 - NS-Link COM Port Driver Installation Overview on Page 11 - NS-Link tty Port Installation Overview on Page 11 - TCP/IP Socket Port Installation Overview on Page 11 • Locating Software and Documentation on Page 12 • Connectivity Requirements on Page 13 Supported DeviceMaster Models This Installation and Configuration Guide sup
Installation Overview Installation on Page 15. 2. Install PortVision DX. Note: PortVision DX replaces PortVision Plus. PortVision Plus does not support operating systems above Windows 7 and SocketServer versions above 9.00. Comtrol recommends connecting the DeviceMaster to a PC or laptop running Windows and that you install PortVision DX for easy IP address configuration and firmware updates.
NS-Link COM Port Driver Installation Overview NS-Link COM Port Driver Installation Overview Use the following overview, which are discussed in detail in the subsequent sections, to install and configure the DeviceMaster to run the NS-Link device driver for Windows operating systems.. 1. After connecting the DeviceMaster, programming the IP address with PortVision DX, and uploading the latest version of SocketServer, you are ready to install the driver. 2. Install the NS-Link device driver.
Locating Software and Documentation Locating Software and Documentation You can access the appropriate software assembly, PortVision DX, and DeviceMaster documentation from the Comtrol ftp site using any of these methods: • Comtrol Software and Documentation CD shipped with the DeviceMaster provides links to the latest files. • PortVision DX features a Documentation option that you can use to download and later, access documentation from within PortVision DX.
Connectivity Requirements Connectivity Requirements An Ethernet connection: either to an Ethernet hub, switch, or router; or to a Network Interface Card (NIC) in the host system using a standard Ethernet cable.
Connectivity Requirements 14 - Introduction DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Hardware Installation Installation Overview Use the links below to locate installation procedures for the following models: DeviceMaster PRO DB9 serial ports with dual 8† Ethernet†† ports 4-Port and 8-Port Installation on Page 26 RJ45 serial ports with dual 16 Ethernet†† ports 16-Port (DeviceMaster PRO) Installation on Page 30 Default Network Settings IP address: 192.168.250.250 Subnet mask: 255.255.0.0 Gateway address: 192.168.250.
Hardware Installation 1-Port - Enclosed Installation Use the following procedure to install the DeviceMaster 1-Port. 1. Place the 1-Port on a stable surface and skip to Step 2 or optionally mount the DeviceMaster using the mounting flanges or DIN rail adapters. a. Pick up the DeviceMaster so that the front of the device is facing you. b. Pick up a DIN rail clip. (The three tines should be on top and the M4 label should face you.) c.
Hardware Installation • Insert the DC positive wire into the positive screw terminal and the DC return wire into the return screw terminal.
Hardware Installation 1-Port - Embedded Installation Installing the DeviceMaster 1-Port Embedded system follows these basic steps: • Building the serial ribbon cable (below). • Mounting the Embedded on Page 19 and installing light pipes. • Attaching the Network and Serial Cables on Page 20. • Connecting the Power and Verifying Installation on Page 20. Observe proper ESD techniques when handling the DeviceMaster.
Hardware Installation Mounting the Embedded Use the following procedure to mount the DeviceMaster 1-Port Embedded with the 5-30VDC power supply. Observe proper ESD techniques when handling the DeviceMaster. Caution 1. Carefully remove the DeviceMaster from the anti-static bag, following standard electrostatic device handling procedures. Note: Write down the MAC address located on a label on the bottom (solder side) center of the DeviceMaster because you may need it during configuration. 2.
Hardware Installation 4. Optionally, attach the light pipes. The following light pipes have been tested and found to function; Bivar, Inc. (P/N:LP-230) and Ledtronics, Inc. (P/N:LTP003-0CW-001). After mounting the DeviceMaster, you are ready to connect the cables. Attaching the Network and Serial Cables Use the following procedure to attach the serial ribbon and Ethernet cables. For a larger illustration of the system, see 1-Port Embedded on Page 144. 1.
Hardware Installation 3. Use a small flat head screw to lock the wires into place. 4. Verify that each wire has been tightened securely. 5. Plug the screw terminal power connector into the DeviceMaster. 6. Connect the power supply to a power source. 7. Plug the screw terminal power connector into JP1 on the DeviceMaster by aligning the scalloped sides. Note: Align the plug properly.
Hardware Installation 2-Port (Serial Terminal) 1E/2E Installation Use the following procedure to install DeviceMaster 2-port models with serial terminal connectors. See 2-Port (DB9) 1E/2E Installation on Page 24 if the DeviceMaster has DB9 serial connectors. 1. Attach the DeviceMaster 2-Port to the DIN rail adapter. 2. Connect the power supply and apply power to the DeviceMaster using the power supply specifications on the product label and the following information.
Hardware Installation Do not connect RS-422/485 devices until the appropriate port interface type has been configured. The default port setting is RS-232. Caution 4. Verify that the Status LED has completed the boot cycle and network connection for the DeviceMaster is functioning properly using the following table. 2-Port Serial Terminal LED Descriptions The STATUS LED on the device is lit, indicating you have power and it has completed the boot cycle.
Hardware Installation 2-Port (DB9) 1E/2E Installation Use the following procedure to install DeviceMaster 2-port models with DB9 connectors. 1. Attach the DeviceMaster 2-Port to the DIN rail adapter. 2. Connect the power supply and apply power to the DeviceMaster using the power supply specifications on the product label and the following information. Observe proper ESD techniques when connecting and disconnecting the DeviceMaster. Caution a.
Hardware Installation 3. Use the appropriate method for network attachment of your DeviceMaster 2port: DeviceMaster 1E: Connect the 10/100 port to the same Ethernet network segment as the host PC using a standard network cable. DeviceMaster 2E: Connect the DeviceMaster 2E using one of these methods: • Ethernet hub, switch (10/100Base-T), Server NIC (10/100Base-T): Connect a 10/100 port to the same Ethernet network segment as the host PC using a standard Ethernet cable.
Hardware Installation 4-Port and 8-Port Installation Use the following procedure to install the DeviceMaster 4-port or 8-port. 1. Optionally, attach the mounting brackets using the screws provided in the kit (6-32 1/4” flathead machine) or place the DeviceMaster on a stable surface. DeviceMaster RTS - Larger Pictures, Page 146 DeviceMaster PRO and DeviceMaster Serial Hub Larger Picture, Page 146 Caution Failure to use the correct screws can damage the PCB and void the warranty.
Hardware Installation 4. Verify that the PWR LED has completed the boot cycle and network connection for the DeviceMaster is functioning properly using the table below. 4-Port and 8-Port LED Descriptions LED on the front panel of the DeviceMaster is lit, indicating you have power and it has completed the boot cycle. PWR Note: The PWR LED flashes while booting and it takes approximately 15 seconds for the Bootloader to complete the cycle.
Hardware Installation 16-Port (DeviceMaster RTS - External Power Supply) Installation Use the following procedure to install the DeviceMaster RTS 16-port with an external power supply. 1. Place the DeviceMaster RTS on a stable surface, or optionally mount the DeviceMaster in a rack. Rack Installation: a. Attach the L brackets to the interface using the screws supplied with the unit. b. You can mount the unit facing in either direction. Larger picture, Page 146 c. Attach the L bracket into your rack.
Hardware Installation 4. Verify that the PWR LED has completed the boot cycle and network connection for the DeviceMaster RTS is functioning properly using the table below. DeviceMaster RTS 16-Port (External Power Supply) LED Descriptions Red LED on the front panel of the DeviceMaster is lit, indicating you have power and it has completed the boot cycle. Red LED Note: The LED flashes while booting and it takes approximately 15 seconds for the Bootloader to complete the cycle.
Hardware Installation 16-Port (DeviceMaster PRO) Installation Use the following procedure to install the DeviceMaster PRO 16-port with an external power supply. 1. Place the DeviceMaster PRO on a stable surface, or optionally mount the DeviceMaster PRO in a rack. Rack Installation: a. Attach the L brackets to the DeviceMaster PRO using the screws supplied with the unit. b. You can mount the unit facing in either direction. c. Attach the L bracket into your rack.
Hardware Installation 5. Verify that the PWR LED has completed the boot cycle and network connection for the DeviceMaster is functioning properly using the table below. DeviceMaster PRO 16-Port LED Description Red LED (Front panel) Red LED on the front panel of the DeviceMaster PRO is lit, indicating you have power and it has completed the boot cycle. Note: The LED flashes while booting and it takes approximately 15 seconds for the Bootloader to complete the cycle.
Hardware Installation 16/32-Port Rack Mount Models (Internal Power Supply) Installation Use the following procedure to install the DeviceMaster 16-port or 32-port with an internal power supply. 1. Place the DeviceMaster on a stable surface, or optionally mount the DeviceMaster in a rack. Rack Installation: a. Attach the L brackets to the interface using the screws supplied with the unit. b. You can mount the unit facing in either direction. c. Attach the L bracket into your rack.
Hardware Installation 2. Connect the DeviceMaster port labeled 10/100 NETWORK to the same Ethernet network segment as the host PC using a standard network cable. DeviceMaster RTS - Larger pictures, Page 147 DeviceMaster Serial Hub - Larger picture, Page 146 Caution If you plan on using the NS-Link device driver, make sure that you do not connect RS-422/485 devices until the appropriate port interface type has been configured in the driver. The NS-Link default port setting is RS-232. 3.
Hardware Installation 34 - Hardware Installation DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Initial Configuration There are several ways to configure network information. Comtrol Technical Support recommends connecting the DeviceMaster to a PC or laptop running Windows and installing PortVision DX for initial configuration. Optionally, you can use RedBoot to configure the network address, see RedBoot Procedures on Page 129. This section shows how to use PortVision DX for initial DeviceMaster configuration.
PortVision DX Requirements RocketLinx switches are treated as non-intelligent devices and have limited feature support. For example, you cannot configure or update firmware on a thirdparty switch. PortVision DX Requirements Use PortVision DX to identify, configure, update, and manage the DeviceMaster on the following Windows operating systems: • Windows 8.
Installing PortVision DX Installing PortVision DX During initial configuration, PortVision DX automatically detects and identifies DeviceMaster units, if they are in the same network segment. Use the Software and Documentation CD that came with the DeviceMaster to check for the latest version of PortVision DX or use the link below to download the latest version. 1.
Installing PortVision DX 5. Click Next or optionally, browse to a different location and then click Next. 6. Click Next to configure the shortcuts. 7. Click Install. 38 - Initial Configuration DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Installing PortVision DX 8. Depending on the operating system, you may need to click Yes to the Do you want to allow the following program to install software on this computer? query. 9. Click Launch PortVision DX and Finish in the last installation screen. 10. Depending on the operating system, you may need to click Yes to the Do you want to allow the following program to make changes to this computer? query. 11. Select the Comtrol Ethernet attached products that you want to locate and then click Scan.
Configuring the Network Settings Configuring the Network Settings Use the following procedure to change the default network settings on the DeviceMaster for your network. Default Network Settings IP address: 192.168.250.250 Subnet mask: 255.255.0.0 Gateway address: 192.168.250.1 Note: Technical Support advises configuring one new DeviceMaster at a time to avoid device driver configuration problems.
Configuring the Network Settings 6. Highlight the DeviceMaster for which you want to program network information and open the Properties screen using one of these methods. • Double-click the DeviceMaster in the Device Tree or Device List pane. • Highlight the DeviceMaster in the Device Tree or Device List pane and click the Properties button.
Configuring the Network Settings 7. Optionally, rename the DeviceMaster in the Device Name field. Note: SocketServer versions previous to v9.00 did not support the Bootloader Timeout option in the PortVision DX Properties screen. Note: The MAC address and Device Status fields are automatically populated and you cannot change those values. 8. Optionally, enter the serial number, which is on a label on the DeviceMaster. 9. If necessary, you can change the Detection Type.
Checking the SocketServer Version 12. Click Apply Changes to update the network information on the DeviceMaster. Note: If you are deploying multiple DeviceMasters that share common values, you can save the configuration file and load that configuration onto other DeviceMasters. See Using SocketServer Configuration Files on Page 107 for more information. 13. Click Close to exit the Properties window. 14. Go to Checking the SocketServer Version on Page 43 to check the SocketServer version.
Checking the SocketServer Version 3. Check the Comtrol ftp site to see if a later version is available by accessing the ftp subdirectory that contains the latest version of SocketServer. • View an ftp subdirectory that contains the latest version of SocketServer: ftp://ftp.comtrol.com/dev_mstr/rts/software/socketserver.
Uploading SocketServer with PortVision DX Uploading SocketServer with PortVision DX Use this section to upload a newer version of SocketServer on the DeviceMaster using PortVision DX. Technical Support recommends updating SocketServer before any further configuration to avoid configuration problems. You can use this procedure if your DeviceMaster is connected to the host PC, laptop, or if the DeviceMaster resides on the local network segment. 1.
Uploading SocketServer with PortVision DX 4. Click Yes to the Upload Firmware message that warns you that this is a sensitive process. It may take a few moments for the firmware to upload onto the DeviceMaster. The DeviceMaster reboots itself during the upload process. 5. Click Ok to the advisory message about waiting to use the device until the status reads ON-LINE.
Customizing PortVision DX Customizing PortVision DX You can customize how PortVision DX displays the devices. You can even create sessions tailored for specific audiences. You can also add shortcuts to other applications using Tools > Applications > Customize feature. The following illustrates how you can customize your view. See the PortVision DX Help system for detailed information about modifying the view. For example, the above screen shot illustrates devices layered in folders.
Accessing DeviceMaster Documentation from PortVision DX Accessing DeviceMaster Documentation from PortVision DX You can use this procedure in PortVision DX to download and open the previously downloaded documents for the DeviceMaster. You can also check to see if you have the latest version of the documentation using PortVision DX. How to Download Documentation Use this procedure to initially download a document or documents. 1.
How to Open Previously Downloaded Documents How to Open Previously Downloaded Documents Use the following procedure to access previously downloaded documents in PortVision DX. Note: Optionally, you can browse to the Program Files (x86) > Comtrol > PortVision DX > Docs subdirectory and open the document. 1. If necessary, open PortVision DX > Start/Programs > Comtrol > PortVision DX > PortVision DX or use the desktop shortcut. 2. Click Help > Documentation. 3.
How to Open Previously Downloaded Documents 50 - Initial Configuration DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Device Driver (NS-Link) Installation This section discusses the following topics: • Linux Installations on Page 52 • Windows Installations on Page 53 Overview The following subsections discuss procedures that need to be done before installing and configuring the NS-Link device driver.
Linux Installations Linux Installations You can locate the latest device driver for Linux using one of these methods: • Download the latest device driver: ftp://ftp.comtrol.com/dev_mstr/rts/ drivers/linux. Note: Although the ftp link displays rts in the path, the driver supports the DeviceMaster models discussed in this User Guide. • Software and Documentation CD: You can use the CD to check the driver version on the CD against the latest released version. Open the /html/ default.
Windows Installations Windows Installations This subsection provides an installation overview for the NS-Link device driver for Windows. For detailed installation and configuration information, see the DeviceMaster Device Driver (NS-Link) User Guide for Windows, which is available on the Software and Documentation CD or you can download the latest. Supported Operating Systems The NS-Link device driver for Windows supports: • Windows 8/8.
NS-Link for Windows Installation 3. Click Next to install in the default location. 4. Click Install 5. Leave the Launch DeviceMaster Driver Installation box checked. If you do not check this box, you can use the shortcut under the Start button at: Programs > Comtrol > DeviceMaster > DeviceMaster Driver Installation Wizard. 6. Click Finish to complete the installation of the wizard. 54 - Device Driver (NS-Link) Installation DeviceMaster Installation and Configuration Guide: 2000594 Rev.
NS-Link for Windows Installation 7. Click Next to start the driver installation. 8. Click Install and Next. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
NS-Link for Windows Installation 9. Select the DeviceMaster model that you are installing from the list. 10. Enter the quantity of this DeviceMaster model that you want to install and click Ok. 11. Repeat Steps 9 and 10 for each DeviceMaster that you are installing and click Next. 12. Click Proceed. You may see the popup at the right for each port. 56 - Device Driver (NS-Link) Installation DeviceMaster Installation and Configuration Guide: 2000594 Rev.
NS-Link for Windows Installation 13. Return to the Installation Wizard and click Close. 14. Go to the next subsection for NS-Link driver configuration procedures. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Configuring the NS-Link Driver for Windows Configuring the NS-Link Driver for Windows This subsection provides a configuration overview for the NS-Link driver. For detailed information or if the DeviceMaster is on a different physical segment, refer to the help system or the DeviceMaster Device Driver (NS-Link) User Guide, which is available on the Software and Documentation CD or you can download the latest.
Configuring the NS-Link Driver for Windows 4. Click Apply to program the driver with the MAC address of the DeviceMaster or Ok to save the change and close the Comtrol Drivers Management Console. If you do not Apply the changes before leaving this screen, you will be prompted to Apply, Ignore, or Cancel the changes. 5.
Configuring the NS-Link Driver for Windows In addition to encrypting the data streams, it is possible to configure the DeviceMaster so that only authorized client applications can connect using SSL/TLS. For this option to function, you must also Enable Secure Data Mode in the NSLink web page. Note: See the help system or the DeviceMaster NS-Link User Guide for Windows if you need additional information on SSL and the corresponding options. 7.
Configuring COM Port Properties for Windows Configuring COM Port Properties for Windows The following is a COM port properties configuration overview. Use the DeviceMaster Device Driver (NS-Link) User Guide (also available on the CD) or the NS-Link Help system for detailed configuration information. 1. Highlight the first port you want to configure. 2. Complete the screen appropriately for the serial device that you plan on connecting to the port and click Ok. a.
Enabling Secure Data Mode 6. Click Apply to save these changes. Note: If you selected RS-422 mode, make sure that there is not a device attached to the port and click Ok. 7. Highlight the next port that you want to configure and perform Steps 1 through 6. 8. Refer to Connecting Serial Devices on Page 91 to attach your serial device. 9. Optionally, you may need to configure one or more ports for socket mode (Socket Port Configuration on Page 65).
Enabling Secure Data Mode 4. Configure your security key and certificate and click Set. Click the Help button if you need information about key and certificate management. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Enabling Secure Data Mode 64 - Device Driver (NS-Link) Installation DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Socket Port Configuration This section provides an overview of SocketServer and provides basic operating procedures. SocketServer and DeviceMaster security are discussed in detail in DeviceMaster Security on Page 69. Note: Technical Supports recommends that you update to the latest version of SocketServer before installing an NS-Link device driver or configuring socket ports.
SocketServer Architecture SocketServer Architecture TCP/IP socket mode operation is used to connect serial devices with an application that supports TCP/IP socket communications addressing. DeviceMaster PC or Mainframe IP socket application Ethernet Hub LAN/WAN Ethernet Hub Serial Device TCP/IP Socket Mode Serial tunneling mode is used to establish a socket connection between two DeviceMasters through an Ethernet network.
Accessing Socket Configuration Accessing Socket Configuration There are several ways to access the socket configuration pages. Use the method that fits your environment best. Web Browser • Web Browser • PortVision DX To access the socket configuration page for the DeviceMaster using a web browser, follow this procedure. 1. Start your web browser. 2. Enter the IP address of the DeviceMaster in the URL field. Note: If you do not know the IP address, you can view the IP address in PortVision DX. 3.
SocketServer Versions SocketServer Versions The SocketServer Overview discusses the that the default SocketServer web page is the same as the NS-Link web page. If the NS-Link driver is not running (not installed or disabled), SocketServer loads when you open a web browser session. Your SocketServer or NS-Link version may be different than these examples. These examples illustrate NS-Link and SocketServer v9.35 or higher.
DeviceMaster Security This subsection provides a basic understanding of the DeviceMaster security options, and the repercussions of setting these options. See Removing DeviceMaster Security Features on Page 171 if you need to reset DeviceMaster security options. See Returning the DeviceMaster to Factory Defaults on Page 173 if you want to return the DeviceMaster settings to their default values.
Understanding Security Methods and Terminology Term or Issue Digital Certificate Explanation A digital certificate is an electronic credit card that establishes your credentials when doing business or other transactions on the Web. It is issued by a certification authority (CA).
Understanding Security Methods and Terminology Term or Issue Explanation This is an algorithm for public-key cryptography. It is the first algorithm known to be suitable for signing as well as encryption. RSA is widely used in electronic commerce protocols, and is believed to be sufficiently secure given sufficiently long keys and the use of up-to-date implementations.
Understanding Security Methods and Terminology Term or Issue TLS (Transport Layer Security) Explanation Transport Layer Security (TLS) is a protocol that ensures privacy between communicating applications and their users on the Internet. When a server and client communicate, TLS ensures that no third party may eavesdrop or tamper with any message. TLS is the successor to the Secure Sockets Layer (SSL). TLS and SSL are not interoperable.
Understanding Security Methods and Terminology Term or Issue Explanation A number of products are offered that enable a company or group of companies to implement a PKI. The acceleration of e-commerce and business-to-business commerce over the Internet has increased the demand for PKI solutions. Related ideas are the virtual private network (VPN) and the IP Security (IPsec) standard. Among PKI leaders are: • RSA, which has developed the main algorithms used by PKI vendors.
TCP and UDP Socket Ports Used by the DeviceMaster TCP and UDP Socket Ports Used by the DeviceMaster Following list is all of the logical TCP and UDP socket ports implemented in DeviceMasters. Socket Port Number 22 SSH 23 Telnet 80 HTTP 443 SSL or HTTPS Description TCP Ports 22 (ssh) and 23 (telnet) are used for administrative and diagnostic purposes and aren't required for normal use and are enabled by default and Port 23 may be disabled.
DeviceMaster Security Features DeviceMaster Security Features The following subsections provide information about DeviceMaster security features. Security Modes The DeviceMaster supports two security modes. Security Mode Description SSL encryption for serial port data streams for both NS-Link and SocketServer. Secure Data mode: • Requires SSL encryption of TCP connections to SocketServer (Ports 8000, 8001, 8002, and so forth). • Disables UDP access to SocketServer.
Secure Data Mode and Secure Config Mode Comparison Secure Data Mode and Secure Config Mode Comparison This table provides information that compares Secure Data and Secure Config modes.
Security Comparison Security Comparison This table displays addition information about security feature comparisons.
SSL Overview SSL Overview DeviceMaster SSL provides the following features: • SSL Authentication Server Authentication Provides both encryption and authentication. - Encryption prevents a third-party eavesdropper from viewing data that is being transferred. - Authentication allows both the client (that is, web browser) and server (that is. DeviceMaster) to ensure that only desired parties are allowed to establish connections.
Client Authentication Client Authentication Certificates and Keys Client Authentication is the mechanism by which the DeviceMaster verifies the identity of clients (that is, web browsers and so forth). • Clients can generally be configured to accept a particular unknown server certificate so that the user is not subsequently warned.
SSL Performance - RSA Server Certificate used by SSL servers • This is the RSA identity certificate that the DeviceMaster uses during SSL/TLS handshaking to identify itself. It is used most frequently by SSL server code in the DeviceMaster when clients open connections to the DeviceMaster's secure web server or other secure TCP ports.
SSL Cipher Suites SSL Cipher Suites This subsection provides information about SSL cipher suites. • An SSL connection uses four different facilities, each of which can use one of several different ciphers or algorithms. A particular combination of four ciphers/algorithms is called a “cipher suite”. • A Cipher Suite consists of - Public Key Encryption Algorithm • Used to protect the initial handshaking and connection setup. • Typical options are RSA, DH, DHA, DHE, EDH, SRP, PSK.
SSL Resources SSL Resources You can refer to the following SSL resources for more information: • Standard reference book is SSL and TLS by Eric Rescorla • Wikipedia page on SSL/TLS provides a good overview: http://en.wikipedia.org/ wiki/TLS • openssl contains command-line tools to do the following. More information is available at: http://www.openssl.
Configure/Enable Security Features Overview Configure/Enable Security Features Overview You can enable DeviceMaster security features the web page (SocketServer or the NS-Link version). Key and Certificate Management must be done using the Security tab in the DeviceMaster web pages. If you want secure COM ports, you must also Enable SSL Mode and enter any applicable server or client certificates in the NS-Link device driver for Windows. See Device Driver (NS-Link) Installation on Page 51.
Configure/Enable Security Features Overview Security Option Description If Secure Config Mode is enabled, unencrypted access to administrative and diagnostic functions is disabled. Secure Config Mode changes DeviceMaster behavior as follows: Enable Secure Config Mode • Telnet access to administrative and diagnostic functions is disabled. SSH access is still allowed. • Unencrypted access to the web server via Port 80 (http:// URLs) is disabled.
Example 1 Security Option Description • (Continued from the previous page) Enable Monitoring Secure Data via Telnet securemon [enable|disable] By default, monitoring of TX/RX data when in Secure Data Mode is not allowed through telnet (an insecure protocol). This command allows you to override that default when securemon is enabled it will allow monitoring of secure data via an insecure protocol like telnet.
Example 3 Example 3 The -c option enables the use of color instead of < and > to indicate the data flow direction. Tx is green and Rx is red. dm> monitor -c 1 Serial monitoring started for port 1 -- press [Enter] to stop.
Key and Certificate Management Key and Certificate Management Options Description This is a private/public key pair that is used for two purposes: It is used by some cipher suites to encrypt the SSL/ TLS handshaking messages. Possession of the private portion of this key pair allows an eavesdropper to both decrypt traffic on SSL/TLS connections that use RSA encryption during handshaking.
Using a Web Browser to Set Security Features Using a Web Browser to Set Security Features The follow procedures are discussed below: Changing Security Configuration • Changing Security Configuration • Changing Keys and Certificates on Page 89 Use the following steps to change security settings in the DeviceMaster. 1. Enter the IP address of the DeviceMaster in the Address field of your web browser and press the Enter key.
Changing Keys and Certificates 5. Make the appropriate selection for your situation: Changing Keys and Certificates • Click Continue, if you addition configuration and then make sure that you reboot the DeviceMaster later so that the changes take affect. • Click Reboot so that changes take affect as soon as the DeviceMaster returns online. Use the following steps to update security keys and certificates in the DeviceMaster. 1.
Changing Keys and Certificates 6. You do not need to click Save, but changes will not take effect until the DeviceMaster is rebooted. You can reboot the DeviceMaster by returning to the Server Status tab (scroll to the bottom of the page) or using PortVision DX. 90 - DeviceMaster Security DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Connecting Serial Devices This section discusses connecting your serial devices to the DeviceMaster. It also provides you with information to build serial or test cables and loopback connectors to test the serial ports. • DB9 Connectors • RJ45 Connectors on Page 94 • Serial Terminals (4) - 1E on Page 97 • Serial Terminals (8) - 2E on Page 99 Note: Go to Building the Serial Ribbon Cable on Page 18 for connector information for the DeviceMaster 1-Port Embedded adapter.
Connecting Serial Devices Refer to the hardware manufacturer’s installation documentation if you need help with connector pinouts or cabling for the serial device. This illustrates the DB9 connector signals.
Connecting Serial Devices DB9 Loopback Plugs Loopback connectors are DB9 female serial port plugs with pins wired together that are used in conjunction with application software (Test Terminal or minicom) to test serial ports. The DeviceMaster is shipped with a a single loopback plug (RS232/422). Note: You can use Test Terminal (Windows) or minicom (Linux) to test the serial port. You can refer to Testing Ports Using Test Terminal on Page 156 for Windows systems.
Connecting Serial Devices RJ45 Connectors This subsection provides the following information: • Connector pin assignments (below) • RJ45 Null-Modem Cables (RS-232) • RJ45 Null-Modem Cables (RS-422) on Page 95 • RJ45 Straight-Through Cables (RS-232/485) on Page 95 • RJ45 Loopback Plugs on Page 95 • RJ45 RS-485 Test Cable on Page 96 • Connecting RJ45 Devices on Page 96 You can build your own null-modem or straight-through RJ45 serial cables if you are using the DB9 to RJ45 adapters using the fo
Connecting Serial Devices Use the following figure if you need to build an RS-422 null-modem RJ45 cable. A null-modem cable is required for connecting DTE devices. DeviceMaster Female RJ45 Null-Modem Cables (RS-422) Signal TxD+ TxDRxD+ RxDGND RJ45 Pins 1 4 8 5 3 Signal RxD+ RxDTxD+ TxDGND Note: RS-422 pinouts are not standardized. Each peripheral manufacturer uses different pinouts. Please refer to the documentation for the peripheral to determine the pinouts for the signals above.
Connecting Serial Devices RJ45 RS-485 Test Cable You can use a straight-through cable as illustrated previously, or build your own cable. RJ45 Signal Pins 4 TRxDTRxD+ 1 Signal TRxDTRxD+ Note: RS-422 pinouts are not standardized. Each peripheral manufacturer uses different pinouts. Please refer to the documentation for the peripheral to determine the pinouts for the signals above. Connecting RJ45 Devices You can use this information to connect serial devices to RJ45 connectors.
Connecting Serial Devices Serial Terminals (4) - 1E This subsection discusses the following topics for the DeviceMaster 2-port 1E with serial terminals (4). See Serial Terminals (8) - 2E on Page 99 if the DeviceMaster has eight serial terminals.
Connecting Serial Devices Serial Terminal (4) Null-Modem Cables (RS-232) Serial Terminal (4) Null-Modem Cables (RS-422) Serial Terminal (4) Straight-Through Cables (RS-232/485) An RS-232 null-modem cable is required for connecting DTE devices. RS-232 Null-Modem Cable TxD RTS RxD RxD CTS TxD RTS DB9 2 8 3 7 DB25 3 5 2 4 An RS-422 null-modem cable is required for connecting DTE devices. CTS RS-422 Null-Modem Cable Note: RS-422 pinouts are not standardized.
Connecting Serial Devices Serial Terminal (4) Loopback Signals Use this drawing to wire a loopback, which is used in conjunction with application software (Test Terminal for Windows or minicom for Linux) to test serial ports. Wire the terminals together to create a loopback. • TxD to RxD • RTS to CTS TxD RTS RxD CTS Note: You can use Test Terminal (Windows) or minicom (Linux) to test the serial port. You can refer to Testing Ports Using Test Terminal on Page 156 for Windows systems.
Connecting Serial Devices RS-232: Connecting the Ground Signal Ground Signal Ground† Chassis Ground† Not connected Return† Positive† † Wire gauge: AWG 12-22 5-30VDC RS-232 CD DSR RI RS-422/RS-485 N/A N/A Full-Duplex RS-485 Half- N/A N/A Duplex DTR TxD RTS RxD CTS N/A N/A TxD- TxD+ RxD- RxD+ N/A N/A TRxD- TRxD+ N/A N/A † RS-232 ground must be connected to the appropriate signal ground terminal.
Connecting Serial Devices Serial Terminal (8) Null-Modem Cables (RS-422) An RS-422 null-modem cable is required for connecting DTE devices. RS-422 Null-Modem Cable CD DSR RI DTR TxD RxD- RxD+ TxD- TxD+ 2 8 3 7 DB9 DB25 Serial Terminal (8) Straight-Through Cables (RS-232/485) RS-232 or RS-485 straightthrough cables are used to connect modems and other DCE devices.
Connecting Serial Devices Connecting Serial Devices Use the following information to connect the DeviceMaster 2-port 2E with serial terminals. 1. Connect your serial devices to the appropriate serial port on the DeviceMaster using the appropriate cable. Note: Refer to the hardware manufacturer’s installation documentation if you need help with connector pinouts or cabling for the serial device. 2. You can refer to Network and Device LEDs on Page 169 for information about the LEDs.
Managing the DeviceMaster This section discusses the following DeviceMaster maintenance procedures: • Rebooting the DeviceMaster • Uploading SocketServer to Multiple DeviceMasters on Page 104 • Configuring Multiple DeviceMasters Network Addresses on Page 105 Note: You can configure the network addresses for multiple DeviceMasters, configure common settings for the DeviceMasters, and save the settings to a configuration file that you can use to load settings up to all or selected DeviceMasters.
Managing the DeviceMaster Uploading SocketServer to Multiple DeviceMasters If an older version of the NS-Link driver for Windows (before v9.xx) has been installed, make sure that the driver is disabled through the Device Manager before uploading SocketServer. You can use this procedure if your DeviceMaster is connected to the host PC, laptop, or if the DeviceMaster resides on the local network segment. 1.
Managing the DeviceMaster Configuring Multiple DeviceMasters Network Addresses You can configure the network addresses for multiple DeviceMasters using the Assign IP to Multiple Devices option. In addition, you can also configure common settings for the DeviceMaster SocketServer or NS-Link web page and save the settings to a configuration file that you can load to all or selected DeviceMasters. See Using SocketServer Configuration Files on Page 107 for more information.
Managing the DeviceMaster 7. Enter the IP Address for the DeviceMaster. It is not necessary to enter the Subnet Mask and Default Gateway. 8. Click Ok to close the Add New Device window. It may take a few moments to save the DeviceMaster. 9. If necessary, click Refresh for the new DeviceMaster to display in the Device Tree or Device List panes. The DeviceMaster shows OFF-LINE if it is not attached to the network or if an incorrect IP address was entered.
Managing the DeviceMaster 6. Select LOCAL for the Detection Type. 7. Enter the MAC address or network information. Note: A MAC address label is attached to all DeviceMaster units. The first three pairs of digits start with 00 C0 4E. 8. Optionally, enter the serial number in the Serial Number list box. 9. Click Ok. 10. If necessary, click Refresh for the new DeviceMaster to display in the Device Tree or Device List panes.
Managing the DeviceMaster 4. Click the All check box or click only the properties that you want saved for each property page in the configuration file and click Done. 5. Click Ok to close the Save Configuration Completed message. Loading a SocketServer Configuration File Use the following procedure to load a previously saved a DeviceMaster configuration file.
Managing the DeviceMaster Using Driver Configuration Files This subsection discusses how to create (save) and load driver configuration files.
Managing the DeviceMaster 4. Click Save Configuration. 5. Optionally, change the default file name and click Save. 6. Repeat the previous steps for each DeviceMaster for which you want to save the driver configuration. Saving Port-Level Configuration Use the following procedure to create and save a port configuration file. Port configuration, must be saved on a port-by-port basis. 1.
Managing the DeviceMaster 3. Highlight the DeviceMaster for which you want to save the port-level configuration. 4. Highlight the port for which you want to save port configuration. 5. Click Save Configuration. 6. Repeat this process for each port for which you want to save the configuration settings. Loading Driver Configuration Files You must have previously saved a driver configuration file before you can load a configuration file.
Managing the DeviceMaster 3. In the left pane, highlight the DeviceMaster for which you want to load the device-level settings from the configuration file. 4. Click Load Configuration. 5. Browse to the location of the configuration file that you want to load. 6. Highlight the configuration file and click Open. The configuration file loads in a few moments. 7.
Managing the DeviceMaster 8. Click Apply so that the configuration is saved on the DeviceMaster. 9. Go to the next procedure if you want to restore port settings from a configuration file. Loading Port Configuration Use the following procedure to load the configuration file for port-level settings for your DeviceMaster. Note: Device driver configuration files must be for the same model with the same port density.
Managing the DeviceMaster 6. Highlight the configuration file and click Open. The configuration file loads in a few moments. 7. Make the appropriate choice for your situation: • Click No to the ComtrolApplet message, if you are using the file to set up multiple DeviceMasters with the same port-level settings. • Click Yes to the ComtrolApplet message, if you are using the file to restore a specific DeviceMaster. For example, you needed to remove and then reinstall the DeviceMaster NSLink device driver.
Managing the DeviceMaster Changing the Bootloader Timeout If SocketServer fails during the upload process, you should change the Bootloader timeout value to 45 seconds. Note: The DeviceMaster must be able to communicate using an IP address, which is compatible with this local network. If necessary, refer to Configuring the Network Settings on Page 40. You must meet these requirement to use this procedure. • NS-Link device driver assembly v10.xx or higher installed • SocketServer v9.
Managing the DeviceMaster Managing Bootloader Bootloader refers to the operating system that runs on the DeviceMaster hardware during the power on phase, which then loads SocketServer. Note: Typically, you should not update the Bootloader unless advised to do so by Comtrol Technical Support. There are several methods and tools that you can use to check the Bootloader version or update the Bootloader.
Managing the DeviceMaster 3. Right-click the DeviceMaster for which you want to update, click Advanced > Upload Firmware, browse to the Bootloader .cmtl 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. 6. Right-click the DeviceMaster and click Refresh until the Bootloader version displays in the Device List pane and verify that the new version loaded.
Managing the DeviceMaster Checking the NS-Link Version Use this procedure to check the NS-Link web page version. Remember, an NSLink version displays when the NS-Link device driver has been installed and configured, NS-Link is the same firmware as SocketServer. 1. Start PortVision DX. 2. If necessary, click Scan to locate the DeviceMaster. The Device List pane displays the NS-Link (SocketServer) version. 3. Check the Comtrol ftp site to see if a later version is available.
Managing the DeviceMaster 5. If a higher version of SocketServer is available and you want to update the DeviceMaster with the latest software: a. Update SocketServer using Uploading SocketServer with PortVision DX on Page 45. b. Download the latest driver from ftp://ftp.comtrol.com/dev_mstr/rts/drivers/ win7. c. Update to the latest driver using the DeviceMaster Device Driver (NSLink) User Guide, which can be downloaded using Page 12 or viewed on the Comtrol CD shipped with the DeviceMaster.
Managing the DeviceMaster NS-Link COM Port You can use this procedure to reset NS-Link serial port settings. 1. Open the Comtrol Drivers Management Console using Start > Programs > Comtrol > DeviceMaster or under Control Panel, Comtrol Drivers Management Console. 2. Highlight the first port that you want reset to default values. 3. Click the Defaults button (and if appropriate, Clone). 4. Click Apply or Ok.
Managing the DeviceMaster Accessing SocketServer Commands in Telnet/SSH Sessions (PortVision DX) You can open a Telnet or SSH session using PortVision DX. Use the appropriate procedure for your site: Telnet Session • Telnet Session (below) • SSH Session on Page 123 Use the following procedure to access a telnet session with PortVision DX. 1. In PortVision DX, PortVision DX, right-click the DeviceMaster in the Device List pane for which you want to open a telnet session, and click Telnet/SSH Session.
Managing the DeviceMaster 3. If necessary, enter the password and press Enter. If a password has not been set, press Enter. 4. You can type help to refer to available commands supported by SocketServer/ NS-Link. 122 - Managing the DeviceMaster DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Managing the DeviceMaster SSH Session Use the following procedure to access an SSH session with PortVision DX. 1. In PortVision DX, PortVision DX, right-click the DeviceMaster in the Device List pane for which you want to open an SSH session, and click Telnet/SSH Session. 2. Click SSH and leave the port number at the default. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Managing the DeviceMaster 3. If necessary (depending on the operating system), respond to the security notification. 4. Press Enter. Note: The DeviceMaster does not have a user name. 5. If necessary, enter the password and press Enter. If a password has not been set, press Enter. 6. You can type help to refer to available SocketServer/NS-Link commands. 124 - Managing the DeviceMaster DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Managing the DeviceMaster Accessing RedBoot Commands in Telnet/SSH Sessions (PortVision DX) You can open a Telnet or SSH session using PortVision DX to access RedBoot commands. Use the following procedure to access a telnet or SSH session with PortVision DX. 1. In PortVision DX, PortVision DX, right-click the DeviceMaster in the Device List pane for which you want to open a telnet session, and click Telnet/SSH Session. 2. Select Telnet or SSH, leave the Selected Port number, and click Ok.
Managing the DeviceMaster 3. If necessary, enter the password and press Enter. If a password has not been set, press Enter. If using an SSH session, press Enter to the login as prompt. Note: If the PuTTY screen flashes in the background and does not appear as shown above, make sure that Enable Telnet/ssh has not been disabled in SocketServer. To check this, return to PortVision DX, right-click the DeviceMaster in the Device List pane, and click Webpage.
Managing the DeviceMaster 5. Quickly re-open the telnet or SSH session using the previous steps. 6. Select Telnet or SSH, leave the Selected Port number, and click Ok. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Managing the DeviceMaster 7. Press Enter. You can type help to review the RedBoot commands. You can also refer to RedBoot Command Overview on Page 135. Note: The dm prompt should be replaced by a redboot prompt. If not, you can reset the Bootloader timeout for a longer time period and retry this procedure. 128 - Managing the DeviceMaster DeviceMaster Installation and Configuration Guide: 2000594 Rev.
RedBoot Procedures You can use this section as a reference if you want to perform tasks in RedBoot.
RedBoot Procedures Establishing a Serial Connection Use the following procedure to set up a serial connection with a terminal server program. You can use HyperTerminal (Windows) or Minicom (Linux) or optionally, Test Terminal (WCom2), which can be accessed from PortVision DX using Tools > Applications > Test Terminal (WCom2). 1. Connect a null-modem cable from an available COM port on your PC to Port 1 on the DeviceMaster.
RedBoot Procedures Establishing a Telnet Connection Use the following procedure to telnet to the DeviceMaster. 1. Open a telnet session, enter the DeviceMaster IP address. If using Windows, you can use PortVision DX, see Accessing RedBoot Commands in Telnet/SSH Sessions (PortVision DX) on Page 125. 2. Press the Enter key if you did not program a password or type the password and press Enter. ♥♦ Password: Comtrol DeviceMaster RTS Model ID: 5002111 SocketServer 9.
RedBoot Procedures Determining the Network Settings If you are not sure what the network information is on a DeviceMaster, you can perform the following procedure. 1. Establish communications with the DeviceMaster using the serial (Page 130) or telnet (Page 131) method. Default Network Settings IP address: 192.168.250.250 Subnet mask: 255.255.0.0 Gateway address: 192.168.250.1 2. At the RedBoot prompt, type ip. RedBoot>dis Loading disabled RedBoot> ip IP: 192.168.250.250 Mask: 255.255.0.0 Gateway: 192.
RedBoot Procedures Changing the Bootloader Timeout Use the following procedure to change the Bootloader timeout value. 1. Establish communications with the DeviceMaster using the serial (Page 130) or telnet (Page 131) method. 2. At the RedBoot prompt, type timeout. RedBoot> dis Loading disabled RedBoot> timeout Timeout 15 seconds RedBoot> timeout 45 timeout 45 seconds RedBoot>_ RedBoot responds with the current Bootloader timeout value. 3. Type timeout and a value to change the timeout value.
RedBoot Procedures Resetting the DeviceMaster When you have completed your tasks in RedBoot, you must enter a reset command at the RedBoot> prompt for the DeviceMaster to begin operation. Note: The LEDs on the DeviceMaster will go through the power up sequence. The DeviceMaster has completed its reset cycle when the PWR or Status LED is lit and it stops flashing.
RedBoot Procedures RedBoot Command Overview The following table is an overview of RedBoot commands available. After accessing RedBoot, you can review the list of commands online by entering help and pressing the Enter key. For more detailed information, see the eCos Reference Manual that is located on the Comtrol Software and Documentation CD or you can download it from: ftp:// ftp.comtrol.com/dev_mstr/rts/software/redboot/user_guide. RedBoot Commands Sets or displays web authentication.
RedBoot Procedures RedBoot Commands (Continued) mcopy -s -d -l [-1|-2|-4] Copies memory from one address to another. mfill -b -l -p [-1|-2|-4] Fills a block of memory with a pattern. model† Shows model number. password {password} Sets or deletes the password. ping [-v] [-n ] [-l ] [-t ] [-r ] [-i ] -h Network connectivity test. reset Resets the DeviceMaster.
Hardware Specifications Locating DeviceMaster Specifications Specifications can be found on the Comtrol web site at the following addresses.
Hardware Specifications External Power Supply Specifications This subsection discusses information that you may need if you wish to use your own external power supplies.
Hardware Specifications 2-Port (Serial Terminals) Power Supply This table provides the specifications to purchase a power supply for a DeviceMaster 2-port 1E/2E model with serial terminal connectors. External Power Supply: 2-Port (Serial Terminal Connectors) 5-30VDC Output voltage† Current† Power 5-30VDC 100 mA (Min) @ 24VDC 2.5 W † Any power supply that meets current consumption, voltage, power, and connector pinouts requirements can be used.
Hardware Specifications 4-Port Power Supply This table provides the specifications for the power supply shipped with the DeviceMaster 4port. +VDC V Return - GND Shield GND Comtrol Power Supply: 4-Port Input line frequency Input line voltage Output voltage Output current 47 - 63 Hz 90 - 260 VAC 24VDC 500 mA @ 24VDC Housing Molex P/N: 39-01-4030 Pins Molex P/N: 44485-1211 This table provides the specifications, if you intend on using your own power supply.
Hardware Specifications The following tables provide the specifications, if you intend on purchasing your own power supply for your DeviceMaster. External Power Supply: 16-Port DeviceMaster PRO Input line frequency Input line voltage Output voltage† Output current† 47 - 63 Hz 90 - 260VAC 9-30VDC 290 mA (Min) @ 24VDC † Any power supply that meets current consumption, voltage, power, and connector pinouts requirements can be used.
Hardware Specifications DeviceMaster Product Pictures This subsections provides you with detailed pictures of the different DeviceMaster models: 1-Port (DB9) 5VDC • 1-Port (DB9) 5VDC on Page 142 • 1-Port (DB9) 5-30VDC on Page 143 • 1-Port Embedded on Page 144 • 2-Port (Single Ethernet Port) with Serial Terminals on Page 144 • 2-Port (Dual Ethernet Ports) with Serial Terminals on Page 145 • 2-Port (Single Ethernet Port) DB9 on Page 145 • 2-Port (Dual Ethernet Ports) DB9 on Page 146 • 4-Port
Hardware Specifications 1-Port (DB9) 530VDC This illustrates the DeviceMaster 1-Port 5-30VDC. Note: The supported input voltage (5VDC or 5-30VDC) is printed on the top and bottom of the DeviceMaster. See DeviceMaster LEDs on Page 169 for information about the LEDs. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Hardware Specifications 1-Port Embedded This illustrates the DeviceMaster 1-port Embedded system that uses a 5-30VDC power supply. See 1-Port 5-30VDC Power Supply on Page 138 so that you can provide a power supply for the DeviceMaster. See DeviceMaster LEDs on Page 169 for information about the LEDs. 2-Port (Single Ethernet Port) with Serial Terminals The DeviceMaster 2-port 1E with serial terminals uses a 5-30VDC power supply.
Hardware Specifications 2-Port (Dual Ethernet Ports) with Serial Terminals The DeviceMaster 2-port 2E with serial terminals uses a 5-30VDC power supply. See 2-Port (Serial Terminals) Power Supply on Page 139 for information about the power supply. See DeviceMaster LEDs on Page 169 for information about the LEDs. 2-Port (Single Ethernet Port) DB9 The DeviceMaster 2-port 1E DB9 uses a 5-30VDC power supply. See 2-Port (DB9) Power Supply on Page 139 for information about the power supply.
Hardware Specifications 2-Port (Dual Ethernet Ports) DB9 The DeviceMaster 2-port 2E DB9 uses a 5-30VDC power supply. See 2-Port (DB9) Power Supply on Page 139 for information about the power supply. See DeviceMaster LEDs on Page 169 for information about the LEDs. 4-Port (DB9) The PWR LED for the DeviceMaster 4 with DB9 ports is on the other side of the unit. See DeviceMaster LEDs on Page 169 for information about the LEDs.
Hardware Specifications 16-Port (RJ45) Internal Power Supply The power switch for this model is on the other side of the unit. See DeviceMaster LEDs on Page 169 for information about the LEDs. DeviceMaster PRO 16-Port (RJ45) The power connector for this model is on the other side of the unit. See DeviceMaster LEDs on Page 169 for information about the LEDs. NEW GRAPHIC NEEDED DeviceMaster Serial Hub 16-Port (DB9) The power switch for this model is on the other side of the unit.
Hardware Specifications Notices Radio Frequency Interference (RFI) (FCC 15.105) Labeling Requirements (FCC 15.19) This equipment has been tested and found to comply with the limits for Class A digital devices pursuant to Part 15 of the FCC Rules. This equipment generates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
Troubleshooting and Technical Support This section contains troubleshooting information for your DeviceMaster. You may want to review the following subsections before calling Technical Support because they will request that you perform many of the procedures or verifications before they will be able to help you diagnose a problem.
Troubleshooting and Technical Support • Verify that the network IP address, subnet mask, and gateway is correct and appropriate for the network. Make sure that the IP address programmed into the DeviceMaster matches the unique reserved IP configured address assigned by the system administrator. - If IP addressing is being used, the system should be able to ping the DeviceMaster. - If using DHCP, the host system needs to provide the subnet mask and gateway.
Troubleshooting and Technical Support 149. General Condition Explanation/Action Indicates that the bootloader has not downloaded to the DeviceMaster. 1. If applicable, remove the NS-Link driver. PWR or Status LED flashing 2. Make sure that you have downloaded the most current driver: ftp://ftp.comtrol.com/dev_mstr/rts/ drivers/. 3. Install the latest driver and configure the DeviceMaster using the MAC address. Make sure that you reboot the system.
Troubleshooting and Technical Support General Condition Explanation/Action The problem is caused by a L2 bridging feature called Spanning Tree Algorithm (STA) in the switch. This feature is enabled by default in some switches. This features causes time-out problems on certain L2 protocols, such as our MAC mode. Resolution: There will be no firmware fix for this problem. Only one of the following fixes is required for resolution. 1. Disable STA in the switch. 2. Enable STA fast forwarding on the port. 3.
Troubleshooting and Technical Support Testing Ports Using Port Monitor (PMon2) You can use this subsection to test the DeviceMaster driver installation. If you need to install the device driver, locate the latest driver and driver installation documentation.
Troubleshooting and Technical Support 4. Click Driver, click RPSHSI/NSLINK. 5. If the DeviceMaster is communicating with the device driver for Windows, Port Monitor should display CLOSED status. If a port is open for an application, it displays as OPEN, and displays Actual Throughput, TxTotal and RxTotal statistics. Normally, there should be no data errors recorded or they should be very small. To find out what the actual errors are, scroll to the right.
Troubleshooting and Technical Support 6. You can view additional statistics to Port Monitor by adding columns. Click Tools and Add Columns. 7. Highlight or shift-click to add multiple statistics and click Ok. Note: See the Port Monitor help system if you need an explanation of a column. 8. Scroll to the right to view the new columns. 9. If you want to capture this session, you can save a current session as a report.
Troubleshooting and Technical Support Reports can be opened, viewed and re-used when needed. To open and view a report: a. Select File > Open or the Open Existing Session Session dialog appears. button. The Open b. Locate the session (table), you want to open and click the Open button. Optionally, if you want to continue monitoring for an existing session, you need to activate the Polling Interval.
Troubleshooting and Technical Support Opening Ports The following procedure shows how to use Test Terminal to send and receive test data to the serial ports. If necessary, use Installing PortVision DX on Page 37, which contains Test Terminal. 1. Stop all applications that may be accessing the ports such as RRAS or any faxing, or production software. See the appropriate help systems or manuals for instructions on stopping these services or applications.
Troubleshooting and Technical Support Sending and Receiving Test Data (RS-232/422/485: 4Wire) You can use this procedure to send and receive test data through the RS-232/422/ 485 (4-wire, full-duplex) port or ports that you want to test. 1. If you have not done so, perform Steps 1 through 2 on Page 157. 2. Install the loopback plug onto the port (or ports) that you want to test. See Connecting Serial Devices on Page 91, if you need to build loopback plugs. 3. Select Port > Send and Receive Test Data.
Troubleshooting and Technical Support Sending and Receiving Data (RS485: 2-Wire) This procedure shows how to use Test Terminal (WCom2) to test two RS-485 (2Wire, Half-Duplex) ports. 1. In PortVision DX, click Tools >Applications >Test Terminal (WCom2) to start Test Terminal. 2. Open two ports RS-485 ports. This example uses COM40 and COM41. Test Terminal will open two windows, note that both ports show Receiving on the status bar. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Troubleshooting and Technical Support 3. Right-click in both COM windows and remove the check mark for Receive. Both COM ports show Ready on the status bar. 4. Right-click in ONE window and select the Receive option from the pop up. 160 - Troubleshooting and Technical Support DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Troubleshooting and Technical Support 5. Right-click the OPPOSITE window and click Send. The Status line shows Sending or Receiving. In this case, COM40 is sending data and COM41 is receiving the data which is visually confirmed by the data scrolling across the COM41 window. Note: If you do not see the data being received it MAY be necessary to also disable the RTS and DTR options from the right-click pop-up menu in each COM port. 6. Right-click and remove the check mark on the Sending COM port. 7.
Troubleshooting and Technical Support Socket Mode Serial Port Testing This procedure illustrates using Putty, which is available in PortVision DX. Optionally, you can use any other Winsock compatible application. Note: The following procedure starts with resetting DeviceMaster to factory default values. You may want to save the DeviceMaster socket configuration using Saving a SocketServer Configuration File on Page 107. 1.
Troubleshooting and Technical Support 5. If necessary, re-open the web pages and click on the port that you want to test. The following example tests Port 1. 6. Scroll down TCP Connection Configuration options, click the Enable option, and leave all other settings on this page at their default values. Note the Port number as it is needed later in this procedure. In this example, the port number is 8000. 7. Scroll to the bottom of the page and click the Save button. 8.
Troubleshooting and Technical Support 9. Verify that the port has been enabled. 10. Leave the web page open. 11. Attach the loopback plug that was shipped with the DeviceMaster to the serial port of the DeviceMaster. See Connecting Serial Devices on Page 91 if you need to build a loopback plug. 12. Right-click the DeviceMaster in the Device List pane and click Telnet / SSH Session. 13. Enter the socket number of the port that you are testing (Step 6) and click Ok.
Troubleshooting and Technical Support PuTTY loads. 14. Type 123. If 112233 displays, you need to disable local echo. Use the following steps to disable local echo. a. Go to c: \Program Files (x86)\Comtrol\PortVision DX. b. Execute PUTTY.EXE to open the application. DeviceMaster Installation and Configuration Guide: 2000594 Rev.
Troubleshooting and Technical Support c. Click Terminal and click Force off for the Local echo option. d. Return to the Session menu, highlight Default Settings and then click Save. e. Click Cancel to close PuTTY. f. Close the telnet (PuTTY) session that you opened from PortVision DX. g. Re-open the telnet session by right-clicking the DeviceMaster, and select the Telnet / SSH Session option. h. Enter the Socket Port number and then click Ok. i. Enter 123, single digits should appear.
Troubleshooting and Technical Support 15. Remove the loopback plug and type abc. No characters should display because the return path is open. 16. Re-attach the loopback plug, type abc, and the characters should appear. 17. If you want to test additional ports, simply repeat this procedure on that port or ports. 18. Remove the loopback plug from the serial port and attach your serial device. You may need to set the serial parameters as necessary to match your attached equipment.
Troubleshooting and Technical Support Daisy-Chaining DeviceMaster 2E/4/8/16-Port Units The DeviceMaster 2E/4/8/16-port models with external power supplies follow the IEEE specifications for standard Ethernet 10/100BASE-TX topologies. When using the UP and DOWN ports, the DeviceMaster 2E/4/8/16 is classified as a switch. When using the UP port only, it is a simple end node device.
Troubleshooting and Technical Support DeviceMaster LEDs The DeviceMaster has network and port LEDs to indicate status. This subsection discusses: TX/RX LEDs • TX/RX LEDs • Network and Device LEDs on Page 169 This subsection discusses RX and TX LEDs on the following products: • DB9: DeviceMaster 4-port and 8-port models and the DeviceMaster Serial Hub 16-port. • RJ45: DeviceMaster RTS 16-port and 32-port models and the DeviceMaster PRO 16-port.
Troubleshooting and Technical Support Ports Model Network LEDs The LEDs are located between the RJ45 connector and the power terminal block. • 1 Note: The Status LED flashes while booting and it takes approximately 15 seconds for the bootloader to complete the cycle. When the Bootloader completes the cycle, the LED has a solid, steady light that blinks approximately every 10 seconds. DeviceMaster RTS Embedded 2 4 8 • The red Link Act LED (D2) is lit, which indicates a working Ethernet connection.
Troubleshooting and Technical Support Removing DeviceMaster Security Features When presented with a DeviceMaster that has had all security options set and the user is unaware of what the settings are, the restoring of a DeviceMaster can be very difficult.
Troubleshooting and Technical Support 5. At the RedBoot> prompt, type dis, and press Enter. Note: If you do not disable the loading feature of the Bootloader within the time-out period (default is fifteen seconds), an application will be loaded from flash and started. If this happens, repeat Steps 3 through 5. The #!DM command is the only case-sensitive command and must be in uppercase. 6. Enter password and press Enter, which clears the existing password. 7.
Troubleshooting and Technical Support 14. Click Telnet, leave Port 23 as the Selected Port and click Ok 15. Press Enter at the Password prompt. 16. Enter secureconf disable and press Enter. 17. Enter securedata disable and press Enter. Returning the DeviceMaster to Factory Defaults The DeviceMaster uses two types of memory, volatile and non-volatile. The volatile memory is in the form of DRAM and SRAM. They are used for program execution and buffers.
Troubleshooting and Technical Support The EEPROM memory is programmed with a number of default values. The values that you can modified are shown in the following table. Parameter Name Default Value Authentication None User Web or Console Port Configurable Telnet Port Yes No No Yes IP Address 192.168.250.250 Yes Yes Yes Yes IP Mask 255.255.0.0 Yes Yes Yes Yes IP Gateway 192.168.250.
Troubleshooting and Technical Support 5. To reset the bootloader timeout value, type timeout 15 and press Enter. 6. To enable SNMP, type snmp enable and press Enter. 7. To disable SSL, type ssl disable and press Enter. The SSL command is only available on DeviceMaster products running SocketServer 7.0 and later. Serial Port Access To use the serial method to access the DeviceMaster configuration, use Establishing a Serial Connection on Page 130.
Troubleshooting and Technical Support 6. Click Yes: Reboot. 7. Click the Network tab and make the following changes: a. Click the Use static configuration below check box and enter the following values: • Set the IP Address to 192.168.250.250. • Set the Netmask to 255.255.0.0. • Set the Gateway to 192.168.250.1. • Set the Bootloader Timeout to 15. b. Click Save. c. Click OK when reminded it is necessary to reboot to take effect. The DeviceMaster reboots.
Troubleshooting and Technical Support Technical Support If you are using an NS-Link driver for a Windows system, you should review the troubleshooting section in the DeviceMaster Device Driver (NS-Link) User Guide for Windows (Page 12) before contacting Technical Support. It contains troubleshooting procedures that you should perform before contacting Technical Support since they will request that you perform, some or all of the procedures before they will be able to help you diagnose your problem.
Troubleshooting and Technical Support 178 - Troubleshooting and Technical Support DeviceMaster Installation and Configuration Guide: 2000594 Rev.
