SocketServer is integrated in the firmware that comes installed on your DM-2000 Series, DeviceMaster LT, DeviceMaster PRO, DeviceMaster RTS, DeviceMaster Serial Hub, and some DeviceMaster UP models.
![[Note]](images/note.gif) |
|
To use a DeviceMaster UP for a specific industrial protocol, use PortVision DX to load the appropriate firmware, which replaces SocketServer.
DeviceMaster ports can be configured for TCP/IP socket access from other hosts or for serial tunneling using SocketServer. The default operation of the DeviceMaster SocketServer is to buffer network-bound data and transmit the buffered data to the network once every 50ms. This is intended to provide a reasonable trade-off between latency and network utilization. If more control is desired when the serial port receive data is transmitted to the network, there are two user configurable features that can be used: Detect End of Line and Serial Rx Buffer Timeout on the Port Configuration page.
When you open SocketServer, you can review information about the DeviceMaster on the Home page and then you can access these menus and pages:
If you want to use any of the ports as COM or tty ports, you should install a NS-Link (DeviceMaster) driver and then follow the procedures in this help system to configure the ports that you want to use as TCP/IP sockets.
|
|
If you install and enable an NS-Link (DeviceMaster) device driver on your PC, an NS-Link version of SocketServer loads on the DeviceMaster. The versions can be distinguished by what is displayed in the Firmware field on the Home - Server Info page (NS-Link or SocketServer).
SocketServer provides three configuration modes:
TCP/IP socket mode operation is used to connect serial devices with an application that supports TCP/IP socket communications addressing.
Serial tunneling mode is used to establish a socket connection between two DeviceMasters through an ethernet network.
UDP mode is designed for applications that need faster data transmission, or that make use of UDP’s broadcast capabilities. UDP differs from TCP in that a UDP transmission does not first require a connection to be opened before sending data and the receiving device does not issue acknowledgements to the sender.
SocketServer provides a telnet command line interface that provides the following commands:
The Home (Server Info) page provide general information about this DeviceMaster, such as:
Firmware version
Host Name, which can be configured using the Network Configuration page
The serial number or MAC address
System uptime
IP configuration information
The Port Overview page displays when you click the Port menu. This page provides an overview of the settings for each port and provides NS-Link and Socket connection information for the DeviceMaster ports. There is also an example of what the connection information means.
To access the Port Configuration page, click the Port number that you want to configure under the Port menu.
See the SocketServer Configuration Methods discussion for port configuration procedures.
|
|
The Port Configuration page provides the following configuration options:
The following table explains the Serial configuration portion of the Port page. You can also refer to procedures on configuring the DeviceMaster for socket mode, serial tunneling, or UDP mode.
The following table provides information about the Advanced portion of the Port Configuration page.
| Advanced Serial Configuration | Description (Default in Bold) | ||||
|---|---|---|---|---|---|
| Terminating Resistor (Only displays on applicable models) | To ensure the best signal integrity on a long distance high-speed RS-422 or RS-485 network, sometimes it is required to place a 120Ω termination resistor between each of the transmit differential pair or receive differential pair. Signal reflection is reduced and a reliable communication is ensured by placing the 120Ω termination resistor. The DeviceMaster LT provides a software (SocketServer and NS-Link) controllable 120Ω termination resistor for each differential pair on every port in RS-422 and RS-485 mode. Using the software, you can place 120Ω termination resistors between the signals shown below:
| ||||
| DTR Mode | Available choices are: ON all the time, OFF all the time, or on when a connection is established on this port (Socketon). Use Socketon if you want DTR turned on when a connection is established on this port. | ||||
| RTS Mode | Available choices are: RTS ON all the time, OFF all the time,
on when a connection is established on this port (Socketon), or on when data is being transmitted (Toggle).
Use the Socketon option
if you want RTS turned on when a connection is established on this port.
Use Toggle if you want RTS turned on when data is
being transmitted and turned off upon completion of data transmission.
| ||||
| Pre/Post RTS Hold Time | If the RTS Toggle feature is enabled, SocketServer will turn RTS on and wait for the Pre RTS Hold Time before starting data transmission. RTS will remain turned on for the Post RTS Hold Time after data transmission completes. The Pre/Post RTS Hold Time can be configured to values from 0 ms to 4,294,967,295 ms (approximately 49 days). The default is 0 ms. | ||||
| Detect End of Line† | If Detect End of Line is enabled (1-byte or 2-bytes), the DeviceMaster buffers receive serial data until the configured 1- or 2-byte EOL sequence is received. When that sequence has been received, the buffered data (including the EOL sequence) is written to the network. The default is Disabled. | ||||
| End of Line Characters | If Detect End of Line is enabled, enter the decimal equivalent of the end of line character. | ||||
| Serial Rx Buffer Timeout† | If the Serial Rx Buffer Timeout feature is enabled, the DeviceMaster buffers receive serial data until a gap in the serial receive data stream has been detected. This gap can be configured to values from 1 ms to 4,294,967,295 ms (approximately 49 days). The default is 0ms. | ||||
| Reset UART After Timeout | This option only displays on applicable models. If a receive timeout is enabled, selecting this option causes the UART's internal state to be cleared whenever a receive timeout occurs. | ||||
| Rx FIFO Disable | This option allows a parity conflict on a DeviceMaster RTS 1-port. It may be necessary to use this option after you have determined that the cabling is correct and you are able to transmit data but not receive proper data. | ||||
| Send Buffered Data After Close | When unchecked, any buffered data is discarded when the TCP connection is closed. When checked SocketServer finishes sending any buffered data after the TCP connection is closed. | ||||
| Clone settings to all serial ports | If you enable this option, the saved port settings for this port are saved to all of the ports on the DeviceMaster. | ||||
| † If desired, the Detect End of Line and Serial Rx Buffer Timeout fields can be enabled at the same time: receive data is buffered until either an EOL character or a timeout is detected. In any case, the maximum amount of receive data that is buffered is 8KB. If the 8KB receive buffer is filled, the buffered data is written to the network even though an EOL character or timeout has not been detected. | |||||
The following table explains the TCP Connection Configuration portion of the Port Configuration page. You can also refer to procedures on configuring the DeviceMaster for socket mode, serial tunneling, or UDP mode.
| TCP Connection Configuration | Description | ||||
|---|---|---|---|---|---|
| Enabled | Not checked by default. Enable must be checked if you want to use this port as a socket or to enable security for the secure COM port redirector. | ||||
Listen Port | Click the Listen check box (default) so that the DeviceMaster listens for incoming TCP/IP socket connections on the port number specified in the Port box. You can change the default TCP port number on which the DeviceMaster listens for connections in the Port box. This is the actual socket value used for this physical serial port. This number must not be duplicated under this IP address. | ||||
Connect to IP Address | This option is generally used in serial tunneling. Enter an IP address and port number to which the DeviceMaster should initiate a TCP connection in the Target Port and Source Port fields. | ||||
Target Port | Enter the IP address of the DeviceMaster that should initiate a TCP connection. | ||||
Source Port | This is the port number of the Source Port. | ||||
| Connect | You must select the Connect conditions under which the DeviceMaster
should initiate a TCP connection (it only initiates a connection when a connection is not already established):
| ||||
| Disconnect | Click the Disconnect conditions under which the DeviceMaster should close the TCP connection:
| ||||
| Idle Timeout | The default value is 300. The Idle Timeout is the number of seconds in the Idle Timeout box before a disconnect occurs if you selected a Disconnect On value. | ||||
| Telnet Protocol Enable (RFC 2217) | Click this option to enable RFC 2217 extensions to Telnet for full serial communication over a TCP connection. The ports are configured in the client by specifying the IP address of the DeviceMaster and the port number (for example, 8000-80xx). |
The following table explains the UDP Connection Configuration portion of the Edit Port Configuration page. You can refer to the procedures in configuring the DeviceMaster in UDP mode.
| UDP Connection Configuration | Description |
|---|---|
| Enable serial to Ethernet | This enables data, from a serial port, to be sent to the list of IP addresses and/or port numbers. When Enable serial to Ethernet is selected, it allows data from the serial side to be forwarded on to the Ethernet side of the DeviceMaster. When Enable serial to Ethernet is NOT selected, this option prevents the data from the serial side being forwarded on to the Ethernet side of the DeviceMaster. |
| Enable Ethernet to serial | This options allows data from the IP addresses, specified in the list, or any IP address. When Enable Ethernet to serial is selected, it allows data from the Ethernet side to be forwarded to the serial side of the DeviceMaster. When Enable Ethernet to serial is NOT selected, it prevents data from the Ethernet side being forwarded on to the serial side of the DeviceMaster. |
| Allow Ethernet data from any IP Address | This options permits data reception from any IP address rather than limiting it to the list of IP addresses. This option is used in conjunction with the Target IP Address Port fields. When Allow Ethernet data from any IP address is selected, it requires you to enter the IP address of the sending unit, the IP address of the DeviceMaster that the data is expected from, in the following examples. The IP address is now serving double-duty. It is indicating that both the device the data is to be set to and received from when both Enable serial to Ethernet and Enable Ethernet to serial are enabled. The only time the IP address needs to be entered in this case is if the data needs to be responded to so that the DeviceMaster knows where to send the replies back to. If the receive from any is checked, it accepts it form any address. If just can't reply to that address automatically. So the first line should not say it requires an IP address of the sending unit. In the event that some incoming data from specific units may not need an acknowledgement (while other sending units do need acknowledgement) where the IP address of that sending unit is not included in the list, but the incoming data is needed, then this would be the time to enable this option. Remember that to send data back to the originating unit, that the Port number must also be used in addition to the IP address. |
|
Target IP Address Port Target Port Source Port | Enter the Target IP Address Port (serial -> eth) for each port, which is a list of destination IP addresses and port numbers to which you are going to send the serial data received as UDP packets. When there has been no IP address indicated, there is no data sent. This address can also indicate that data is allowed to be received from the network when it has originated at the IP address specified in this list. |
| UDP Listen Port | Enter the value of the UDP Listen Port, which is the specified port number to be used to listen for UDP data coming in on the Ethernet line. This is the port number assigned to this particular port. This is used in the same manner as the TCP Port number assignments. |
You can verify operation of your connection by reviewing the Port Overview page. The following table explains the sample connection status shown below.
| Port | Configuration Settings | Notes | ||||
|---|---|---|---|---|---|---|
| 1 | Enabled = No | No This port has had no configuration changes applied. All values shown are default values. This port is not available for socket mode or serial tunneling at this time. | ||||
| 2 |
| This port is configured for Serial Tunneling mode and has a remotely connected PC as indicated by the address of 192.168.2.11:1042. The Remote IP address is displayed indicating that there is a current connection from the IP address of 192.168.2.11. The value shown of 1042 is from the Ethernet layer and is a variable value and is not user controllable. The Remote DeviceMaster is initiating the connection since the Connect To value is 0.0.0.0. In this case, the Connect On = Always would be incorrect. The initiating DeviceMaster would have the Connect On function. If the remote DeviceMaster does have the Connect On value set, then this Always option is ignored. | ||||
| 3 | Incomplete | This port has been partially configured for Serial Tunneling. It is not connected to another DeviceMaster. The Port Enabled is set to No, so this port is unable to initiate or receive a socket connection. A Remote IP address and port value has been entered into Connect To: configuration showing 192.168.2.11 to the default physical Port 1 as indicated by the value of 8000. It will not connect or be available until the Enabled is set to Yes and a Connect On option is selected. | ||||
| 4 | Enabled = Yes | Socket Mode has been enabled. It confirms the local port of 8003 for the physical Port 4 on the DeviceMaster. A Remote IP address is displayed indicating that there is a current connect from the IP address of 192.168.2.41. The value shown of 1024 is from the Ethernet layer and is a variable value and is not user controllable. Since the Connection Configuration values are at the default, the remote system has initiated this connection. |
You can use the Network Configuration page to configure the DeviceMaster network configuration after you have initially changed the default network information from the default values to appropriate values for your IPv4 or IPv6 network.
In addition, you can change the TCP Keepalive timeout, Rx Polling Period, or Boot Timeout values to fit your environment.
Click the Network menu to access the Network Configuration page.
You can use the Changing Network Configuration procedure for additional information.
Network Configuration page provides configuration parameters for:
| General Options | Description |
|---|---|
| Host Name | You can enter a 16-character Host Name to identify this DeviceMaster on the Home page. |
Rx Polling Default = 50 | This option controls the frequency with which the DeviceMaster transmits serial port data across the TCP connection. The default value is 50ms. |
TCP Keepalive Default = 60 | This option allows you to set the amount of time in seconds that the DeviceMaster waits until it closes this connection and frees all the ports associated with it. The TCP protocol has an optional keepalive feature where the two network stacks periodically ping each other to make sure the connection is still up. In the UNIX world, this feature is usually known as the SOKEEPALIVE socket option. By default, this keepalive feature is not enabled, and the only time you know a connection is down is when you try to write something and the other end does not acknowledge you. The potential issue with the DeviceMaster occurs when data flow was mostly one-way, and the receiver of the data was configured to initiate the TCP connection. If the sender of the data was rebooted, it would wait for the initiation a connection, discarding data. The receiver would wait forever for data and never realize that the other end wasn't connected any more and that the TCP connection needed to be re-established. Enabling the TCP keepalive feature for a connection solves this problem: the TCP stack periodically pings the other end. If the connection has gone away, the DeviceMaster is notified, so that it can attempt to re-establish the TCP connection. |
Boot Timeout Default = 15 | Allows you to change the bootloader time-out value before the default application, typically, SocketServer loads. You may need to increase this time-out value to 45 for compatibility with spanning tree devices (normally switches). If you change the time-out value to 0, this prevents SocketServer from loading. |
Telnet Timeout Default = 300 | Allows you to change the telnet time-out value before telnet times out. You may need to increase this time-out value to 45 for compatibility with spanning tree devices (normally switches). If you change the time-out value to 0, this prevents SocketServer from loading. |
This table provides information about configuring IPv4 addresses.
| IPv4 Options | Description |
|---|---|
| Use DHCP | Configures the DeviceMaster to use DHCPv4 mode. If you select Use DHCP, the IPv4 Address field below is disabled and set to 0.0.0.0. See your System Administrator to acquire a unique reserved IPv4 address if you are using DHCP. They will need the MAC address of the unit to provide you with an IPv4 address. |
| Disable IPv4 networking | Configures the DeviceMaster to use DHCPv4 mode. Configures the DeviceMaster to run in MAC mode with an NS-Link (DeviceMaster) driver. The MAC addressing method has the following advantages:
If you select Disable IPv4 networking, the IPv4 Address field below is disabled and set to 255.255.255.255. The netmask and default gateway are also disabled with their existing values. |
| Use Static Config Below | Configures the DeviceMaster to use DHCPv4 mode. Configures the DeviceMaster with the static IPv4 address information that you provide in the IPv4 Address, IPv4 Netmask, and IPv4 Gateway fields below. The DeviceMaster is shipped from the factory with the following default IPv4 network settings:
|
This table provides information about configuring IPv6 addresses.
| IPv6 Options | Description |
|---|---|
| Use DHCPv6 | Configures the DeviceMaster to use DHCPv6 mode. If you select Use DHCP, the IPv6 Address field below is disabled. See your System Administrator to acquire a unique reserved IPv6 address if you are using DHCPv6. They will need the MAC address of the unit to provide you with an IPv6 address. |
| Disable IPv6 networking (Default) | If you select Disable IPv6 networking, the IPv6 Address field below is disabled. The IPv6 gateway is also disabled with its existing values. |
| Use Static configuration below | Configures the DeviceMaster with the static IPv6 address information that you provide in the IPv6 Address, IPv6 Prefix Length, and IPv6 Gateway fields below. The IPv6 Prefix Length is the network prefix bits for the IPv6 address. |
Use the following steps to change network settings in the DeviceMaster after initially configuring the network values. For initial configuration, you must use PortVision DX, an NS-Link (DeviceMaster) device driver, or a RedBoot method discussed in the DeviceMaster Installation and Configuration Guide that supports the DeviceMaster PRO, DeviceMaster RTS, and DeviceMaster Serial Hub or DeviceMaster LT User Guide, which supports the DeviceMaster LT.
PortVision DX is the easiest and recommended IP configuration method.
You can use the following procedure to change an IP address using the Network Configuration page after initial network configuration.
Click the Network menu, which defaults to the Network Configuration page.
If desired, enter a Host Name to identify this DeviceMaster.
If necessary, change the Rx Polling Period.
If necessary, change the TCP Keepalive Timeout value.
If necessary, change the Bootloader Timeout value.
If necessary, change the Telnet Timeout value.
Enter values appropriate for your network environment. You can refer to IP Configuration Fields for information.
If you selected Use static configuration, enter a valid IP address and support values for the selected IP type or types.
After making any changes, click Save.
Note After completing this step, the browser may no longer be able to open the web page depending on the addresses in the DeviceMaster and the network segment to which it is connected.
You can easily set up a password to secure the DeviceMaster.
There is no password set from the factory.
Use the following information to configure a password for this DeviceMaster.
If necessary, click Network | Password.
If changing an existing password, enter that password in the Old Password field.
Enter a new password.
Enter the password in the Confirm New Password field.
Click the Save button.
To log into the DeviceMaster, you must enter the following:
admin for the username
The configured password for the password.
This table discusses Security Settings options.
| Security Settings Options | Description |
|---|---|
| Enable Secure Data Mode | If Secure Data mode is enabled TCP connections which carry data to/from the serial ports will be encrypted using SSL or TLS security protocols. This includes the following:
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. See the Client Authentication section for details. |
| Enable Secure Config Mode | If Secure Config mode is enabled, unencrypted access to administrative and diagnostic functions is disabled. Secure Config mode changes DeviceMaster behavior as follows:
|
| Enable Telnet/ssh | This option enables or disables the telnet security feature after you click Save and the DeviceMaster has been rebooted. This option is enabled by default. |
| Enable Monitoring Secure Data via Telnet/SSH | When checked, this allows the monitor command to be used while Secure Data Mode is enabled. When unchecked, the monitor command can only be used if Secure Data Mode is not enabled. You must click Save and reboot the DeviceMaster for the change to affect. This option is disabled by default. |
| Enable SNMP | This option enables or disables the SNMP security feature after you click Save and the DeviceMaster has been rebooted. This option is enabled by default. |
| Minimum Allowed SSL/TLS Version | You can select the appropriate version for your environment.
|
| Allow TCP connections only from the address blocks below | When you select this option, you must enter the Block Address and width of the TCP connections that you want to communicate with this DeviceMaster. |
Use the following steps to change security settings in the DeviceMaster.
Click the appropriate check boxes in the Security Settings page to enable or disable security accordingly. Refer to the Security Configuration Area subsection for detailed information.
After making changes to the Security Configuration area, you must click Save.
You may need to configure security keys or certificates depending on your choices.
For secure operation, the DeviceMaster uses a set of four keys and certificates. These keys and certificates may be configured by the user.
| Key and Certificate Management | Description | ||||
|---|---|---|---|---|---|
| RSA Key pair used by SSL and SSH servers |
This is a private/public key pair that is used for two purposes:
| ||||
| 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. If a DeviceMaster serial port configuration is set up to open (as a client) a TCP connection to another server device, the DeviceMaster also uses this certificate to identify itself as an SSL client if requested by the server. In order to function properly, this certificate must be signed using the Server RSA Key. This means that the server RSA certificate and server RSA key must be replaced as a pair. | ||||
| DH Key pair used by SSL servers |
This is a private/public key pair that is used by some cipher suites to encrypt the SSL/TLS handshaking messages.
| ||||
| Client Authentication Certificate used by SSL servers |
If configured with a CA certificate, the DeviceMaster requires all SSL/TLS clients to present an RSA identity certificate that has been signed by the configured CA certificate. As shipped, the DeviceMaster is not configured with a CA certificate and all SSL/TLS clients are allowed. See Client Authorization for more detailed information. |
|
|
If desired, controlled access to SSL/TLS protected features can be configured by uploading a client authentication certificate to the DeviceMaster. By default, the DeviceMaster is shipped without a CA (Certificate Authority) and therefore allows connections from any SSL/TLS client.
If a CA certificate is uploaded, the DeviceMaster only allows SSL/TLS connections from client applications that provide to the DeviceMaster an identity certificate that has been signed by the CA certificate that was uploaded to the DeviceMaster.
This uploaded CA certificate that is used to validate a client's identity is sometimes referred to as a "trusted root certificate", a "trusted authority certificate", or a "trusted CA certificate". This CA certificate might be that of a trusted commercial certificate authority or it may be a privately generated certificate that an organization creates internally to provide a mechanism to control access to resources that are protected by the SSL/TLS protocols.
To control access to the DeviceMaster's SSL/TLS protected resources you should create your own custom CA certificate and then configure authorized client applications with identity certificates signed by the custom CA certificate.
Use the following steps to update security keys and certificates in the DeviceMaster.
Click Browse to locate the key or certificate file, highlight the file, and click Open.
Refer to the Key and Certificate Management subsection for detailed information.
Click Upload when you return to the Key and Certificate Management area.
The key or certificate notation changes from factory or none to User when the DeviceMaster is secure.
|
|
Use the following tables for field definitions. The first table illustrates the Server Configuration fields and the second table provides information about the Message Enable Configuration fields.
| Server Configuration Options | Description |
|---|---|
| SMTP Server IP Address | The IP address of the SMTP server. |
| Sender Host Name | The host name of the SMTP sender. A common format for host names is mail.domainname.com. (For example, mail.Comtrol.com.) |
| Recipient Email Address | The address of the administrator of the network or DeviceMaster. The DeviceMaster will send notifications to this address. Multiple email recipients are not supported. Use the normal email address format, for example, Support@Comtrol.com. |
| Sender Email Address | A name that you can assign to the DeviceMaster. For example, DeviceMaster1@Comtrol.com. This is only what is displayed in the senders address and cannot be replied to. |
This table provides information about the Message Enable Configuration fields.
| Message Enable Configuration Options | Description |
|---|---|
| DeviceMaster Boot Up | The unit boots up. This includes when the unit resets or when the power is cycled. |
| NS-Link TCP Connect | When someone makes a TCP connection to the unit, for example when the NS-Link (DeviceMaster) driver connects using IP mode. |
| NS-Link TCP Timeout | When the TCP Time-out activates during an idle time-out or when the unit disconnects. |
| NS-Link TCP Disconnect | When the server causes a disconnect, for example when the NS-Link (DeviceMaster) device driver stops. |
| NS-Link MAC Connect | When someone makes a MAC connection to the unit, for example when the NS-Link (DeviceMaster) device driver starts up. |
| NS-Link MAC Timeout | When the MAC Time-out activates during an idle time-out or when the unit disconnects. |
| NS-Link Port Open | When someone opens a serial port using an NS-Link device driver. The message states which port is being used. NS-Link is a port connection. |
| NS-Link Port Close | When the port is closed. The message states which port is being used. NS-Link is a port connection. |
| TCP Socket Port Open | When someone opens a port through a TCP/IP connection to the DeviceMaster. The message states which port is being used. |
| TCP Socket Port Close | When the port is closed. The message states which port is being used. |
| Web Login | This triggers when the password access is successful. |
| Web Login Error | When someone tries to enter the DeviceMaster Web server unsuccessfully. |
| Telnet/ssh Login | Triggers when someone successfully logs into a DeviceMaster Telnet/ssh session. The password is the same as the Web server password. |
| Telnet/ssh Error | When someone tries to enter a DeviceMaster Telnet/ssh session unsuccessfully. |
| Telnet/ssh Close | When someone closes the port. This provides a time stamp if desired. |
| Save | Saves the changes that you have made on this page and the DeviceMaster is updated. |
Use the following procedure to setup the parameters for email message delivery.
Enter the Host Name of the SMTP server. The common format for host names is mail.domainname.com. (For example, mail.Comtrol.com.)
Enter a valid Email Recipient. This is the address of the administrator of the network or DeviceMaster. The DeviceMaster will send notifications to this address. Multiple email recipients are not supported.
Use the normal email address format, for example, Example@Comtrol.com.
Enter a valid Email sender. This is a name that you can assign to the DeviceMaster. For example, DM1@Comtrol.com.
This is only what is displayed in the sender's address and cannot be replied to.
Click the desired check boxes to have the DeviceMaster send a message when the appropriate events occur.
The RFC1006 protocol provides an additional transport layer on top of TCP/IP. RFC1006 connections to the DeviceMaster are made to a single TCP/IP port (default is 102). If the port number configured is negative, no incoming RFC1006 connections are allowed.
To determine the desired destination for incoming connections, the RFC1006 protocol contains an endpoint name (TSAP) field in the connection request frame. Each serial port on the DeviceMaster has a TSAP endpoint name (defaults are PORT01 through PORT32). If a port’s TSAP name is configured as blank, connections to that port are not allowed. Incoming connections are also refused for serial ports that are busy (in use by either SocketServer or NS-Link).
RFC1006 is a datagram service and to get useful results you may have to configure the DeviceMaster so that it can determine where the RxSerial data stream is to be divided into datagrams. The buffering description determines how to do this.
Connections initiated by the DeviceMaster are RFC1006 connections if the Connect To TSAP field on the RFC1006 Configuration page is not blank. If that field is blank, then outbound connections are raw TCP/IP connections.
You can refer to the Configuring RFC1006 (ISO Over TCP) discussion for more information.
| RFC1006 Settings | Description |
|---|---|
| Listen on TCP Port | RFC1006 connections to the DeviceMaster are made to a single TCP/IP port (default is 102). If the port number configured is negative, no incoming RFC1006 connections are allowed. |
| Port # | The physical port on the device. |
| Local TSAP | Each serial port on the DeviceMaster has a local TSAP endpoint name (defaults are PORT01 through PORT32). |
| Connect To IP | The IP address to which connections are initiated when the Connect On conditions are true for the serial port in the Connect To IP field. This is the same as the Connect To address field on the Port Configuration page. |
| Connect To Port | The TCP port number to which connections are initiated when the Connect On conditions are true for the serial port in the Port field. This is the same as the Connect To Port field on the Port Configuration page. |
| Connect To TSAP | The local endpoint name for the serial port. To determine the desired destination for incoming connections, the RFC1006 protocol contains an endpoint name (TSAP) field in the connection request frame. If a port’s TSAP name is configured as blank, connections to that port are not allowed and then outbound connections are raw TCP/IP connections. Incoming connections are also refused for serial ports that are busy (in use by either SocketServer or NS-Link). |
| Save | Saves the changes that you have made on this page and the DeviceMaster is updated. |
To configure DeviceMaster ports for the RFC1006 protocol, use the following procedure.
Make sure that you have configured the network information into the DeviceMaster and it is connected to the network.
If necessary, change the Listen on TCP Port to the TCP/IP port number upon which the DeviceMaster accepts incoming RFC1006 connections. The default value is 102. Any negative value disables all incoming RFC1006 connections.
Enter the local endpoint name for the serial port in the Local TSAP field. A blank value disables incoming RFC1006 connections for that port.
Enter the IP address to which connections are initiated when the Connect On conditions are true for the serial port in the Connect To IP field. This is the same as the Connect To address field on the Port Configuration page.
Enter the TCP port number to which connections are initiated when the Connect On conditions are true for the serial port in the Connect To Port field. This is the same as the Connect To port field on the Port Configuration page.
Enter the RFC1006 endpoint name (at the above IP/port) to which connections are initiated when the Connect On conditions are true for the serial port in the Connect To TSAP field. If this field is blank, a raw TCP/IP connection are initiated. If the field contains a value the RFC1006 protocol is used to connect to the TSAP name given.
Click Save when you have completed the RFC1006 (ISO over TCP) Configuration page.
You can use the System Log and Port Monitor pages to troubleshoot DeviceMaster issues.
The System Log page provides system level information, which is updated every 10 seconds.
Click the Refresh button to view the latest system log information.
Click the Clear button to restart a new system log file.
Click the Save Logfile button to save the system log file, if requested by Technical Support.
You can use the Port Monitor page to moniter transmit and receive data on a selected serial port. You can gather up to 1,000,000 records at a time by changing the value in the Log History records box.
You can refer to the following procedures to use this page.
Click Diagnostics | Port Monitor.
Enter the port number that you want to monitor.
If desired, change the value of the Log History records.
Click the Start button.
If desired, save the contents by clicking the Download button.
You can upload firmware (SocketServer or Bootloader) using the System | Update Firmware page.
Use the following procedure to upload the latest firmware onto the DeviceMaster.
If necessary, download the firmware from the Comtrol download site.
Click the Browse button, navigate to the file and select it.
Click the Update button.
SocketServer provides a status screen.
You can use the Save Configuration option to save a DeviceMaster configuration file for recovery purposes or to quickly configure other DeviceMasters that require the same configuration using the Load Configuration option.
You can use this procedure to save a DeviceMaster configuration file.
Click System | Configuration File.
Click the Save Configuration button.
Save the configuration file.
Use the System | System Snapshot page to download a snapshot of the DM status, log and DeviceMaster configuration. This information may be requested by Technical Support to provide configuration and status data for troubleshooting an issue.
You can use the System | Restore Defaults page to restore all settings or a combination of the following:
Port settings, including RFC1006
Server settings, including email configuration, and general network settings
Security settings, password, keys, and certificates
IP address settings
To restore the defaults, click the settings that you want to reset and click the Restore button.
Use the following procedure to set up DeviceMaster ports for use through TCP/IP socket connections.
Make sure that you have configured the network information into the DeviceMaster and it is connected to the network.
Note The default IP address is 192.168.250.250 for the DeviceMaster.
Click Port menu and then click the port number that you want to configure. The Port Configuration page appears.
Configure the serial characteristics for this port.
Note See Serial Configuration Fields if you need field descriptions.
Configure the TCP connection characteristics for this port.
Click Enabled so that SocketServer uses this port.
Click the Listen check box so that the DeviceMaster listens for incoming TCP/IP socket connections on the port number specified in the On Port box for this port.
Optionally, change the default TCP port number on which the DeviceMaster listens for connections in the On Port box. This is the actual socket value used for this physical serial port. This number must not be duplicated under this IP address.
You must select the Connect conditions under which the DeviceMaster should initiate a TCP connection (it only initiates a connection when a connection is not already established).
Optionally, select the Disconnect conditions under which the DeviceMaster should close the TCP connection.
Optionally, enter the number of seconds in the Idle Timeout box before a disconnect occurs if you selected a Disconnect value.
After verifying that the value for each item for the selected port is suitable, select Save.
Repeat Steps 2 through 5 for each port that you want to configure on the DeviceMaster or clone the port.
If you select Clone settings to al serial ports, only the Serial Configuration parameters are cloned, not the Connection Configuration values.
Click Network | Security if you want to set up DeviceMaster security.
To configure any ports for RFC1006, go to Configuring RFC1006 (ISO Over TCP) to complete configuration.
You can verify the operation of your application and connections by checking for a change in the receive and transmit bytes on the Port Overview page.
Use the following procedure to set up two DeviceMasters for serial tunneling.
Make sure that you have configured the network information into the DeviceMaster and it is connected to the network.
Note The default IP address is 192.168.250.250 for the DeviceMaster.
Click the Port menu and then click the port number on DM#1 that you want to configure. The Port Configuration page appears.
Configure the serial characteristics for this port.
Select the port mode of the device (RS-232, RS-422, or RS-485) that you plan on connecting to this port.
Note The DeviceMaster Serial Hub only supports RS-232.
Select the baud rate of the device.
Select the parity, number of data bits, flow control, and stop bits for this port.
Select whether you want DTR Mode on all of the time, or off all the time, or on when a connection is established on this port (socketon). Use socketon if you want DTR Mode turned on when a connection is established to this port.
If Detect End of line detect is enabled (1-byte or 2-bytes), the DeviceMaster buffers received serial data until the configured 1 or 2 byte EOL sequence is received. When that sequence has been received, the buffered data (including the EOL sequence) is written to the network.
If the Serial Rx Buffer Timeout feature is enabled, the DeviceMaster buffers receive serial data until a gap in the serial receive data stream has been detected. This gap can be configured to values from 1 ms to 4,294,967,295 ms (approximately 49 days).
Note If desired, the Detect end of line and Serial Rx Buffer Timeout fields can be enabled at the same time: receive data are buffered until either an EOL or a timeout is detected. In any case, the maximum amount of receive data that is buffered is 8KB. If the 8KB receive buffer is filled, the buffered data is written to the network even though an EOL or timeout has not been detected.
Configure the TCP connection characteristics for this port.
Click Enabled for SocketServer to use this port.
Click the Listen check box so that the DeviceMaster listens for incoming TCP/IP socket connections on the port number specified in the On Port box for this port.
Optionally, change the default TCP port number on which the DeviceMaster listens for connections in the On Port box.
Enter the IP address and port number to which the DeviceMaster should initiate a TCP connection in the Connect to IP Address and Target | Source Port boxes.
You must select the Connect conditions under which the DeviceMaster should initiate a TCP connection (it only initiates a connection when a connection is not already established):
Always: Initiate a connection always and maintain a persistent connection.
Data: Initiate a connection when data is received.
DSR: Initiate a connection when DSR is active.
CD: Initiate a connection when CD is active
Optionally, select the Disconnect conditions under which the DeviceMaster should close the TCP connection:
Idle: Close the connection if no data has been transmitted or received for the number of seconds specified by Idle Timeout.
No DSR: Close the connection when DSR goes inactive.
No CD: Close the connection when CD goes inactive.
Note If you selected Always as the Connect value, a Disconnect value is not required.
Optionally, enter the number of seconds in the Idle Timer box before a disconnect occurs if you selected a Disconnect value.
After verifying that the value for each item for the selected port is suitable, select Save.
Repeat Steps 3 through 6 for each port you want to configure on DM#1 or clone the port. If you select Clone settings to all serial ports, only the Serial parameters are cloned, not the TCP or UDP Connection configuration values.
Enter the IP address of DM#2 in the Address box of the web browser, and press the Enter key.
Configure the serial characteristics for this port on DM#2, if necessary, use Step 4.
Configure the TCP connection characteristics.
Click Enabled so that SocketServer uses this port.
Click the Listen check box so that the DeviceMaster listens for incoming TCP/IP socket connections on the port number specified in the Enable on Port box for this port.
Optionally, change the default TCP port number on which the DeviceMaster listens for connections in the On Port box. This must match the value entered in Step 5d.
It is not necessary to enter an IP address for this unit to connect to as the first unit programmed is initiating the connection.
After verifying that the value for each item is correct, select Save.
Repeat Steps 9 through 12 for each port you want to configure on DM#2.
Click Network | Security if you want to set up DeviceMaster security.
To configure any ports for RFC1006, go to Configuring RFC1006 (ISO Over TCP) to complete configuration.
Connect your serial devices to the DeviceMasters.
You can verify operation of your connection by reviewing the Port Overview page.
UDP mode is designed for applications that need faster data transmission, or that make use of UDP’s broadcast capabilities. UDP differs from TCP in that a UDP transmission does not first require a connection to be opened before sending data and the receiving device does not issue acknowledgements to the sender.
This section provides procedures for the following UDP configuration procedures:
The following procedure is a general procedure that provides basic descriptions and definitions. See the UDP Configuration Overview for detailed examples about each type of UDP configuration.
Make sure that you have configured the network information into the DeviceMaster and it is connected to the network.
Note The default IP address is 192.168.250.250 for the DeviceMaster.
Click the Port menu and click the port number on the DeviceMaster that you want to configure.
Configure the serial characteristics for this port.
Select the port mode of the device (RS-232, RS-422, or RS-485) that you plan on connecting to this port.
Note The DeviceMaster Serial Hub only supports RS-232.
Select the baud rate of the device.
Select the parity, number of data bits, flow control, and stop bits for this port.
Select whether you want DTR Mode ON all the time, OFF all the time, or socketon(on when a connection is established on this port). Use socketon if you want DTR turned on when a connection is established to this port.
If Detect End of Line detect is enabled (1-byte or 2-bytes), the DeviceMaster buffers receive serial data until the configured 1 or 2 byte EOL sequence is received. When that sequence has been received, the buffered data (including the EOL sequence) is written to the network.
If the Serial Rx Buffer Timeout feature is enabled, the DeviceMaster buffers receive serial data until a gap in the serial receive data stream has been detected. This gap can be configured to values from 1 ms to 4,294,967,295 ms (approximately 49 days).
Note If desired, the Detect End of Line and Serial Rx Buffer Timeout fields can be enabled at the same time: receive data is buffered until either an EOL or a timeout is detected. In any case, the maximum amount of receive data that is buffered is 8KB. If the 8KB receive buffer is filled, the buffered data is written to the network even though an EOL or timeout has not been detected.
Configure the UDP connection characteristics. See the UDP Configuration Examples section, if you are unsure how to configure UDP for your environment.
Click Enable Serial to Ethernet to enable data, from a serial port, to be sent to the list of IP addresses and/or port numbers.
When Enable Serial to Ethernet is NOT selected, it allows data from the serial side to be forwarded on to the Ethernet side of the DeviceMaster.
When Enable Serial to Ethernet is NOT selected, this option prevents the data from the serial side being forwarded on to the Ethernet side of the DeviceMaster.
Click Enable Ethernet to Serial to allow data from the IP addresses, specified in the list, or any IP address. See Step c if you want the data to be sent out as serial data.
When Enable Ethernet to Serial is selected, it allows data from the Ethernet side to be forwarded to the serial side of the DeviceMaster.
When Enable Ethernet to Serial is NOT selected, it prevents data from the Ethernet side being forwarded on to the serial side of the DeviceMaster.
Click Allow Ethernet Data from Any IP Address to permit data reception from any IP address rather than limiting it to the list of IP addresses.
This option is used in conjunction with the Target IP Address Port (serial- >eth) fields.
When Allow Ethernet Data from Any IP Address is selected, it accepts incoming data from a sending unit where the sending unit has entered the IP address of this unit. There still must be an IP address installed in the list for data to be returned to the originating point.
For example, if using these ports in a One-Way mode, and this is the unit receiving the data, instead of entering in the IP addresses of all of the sending units, select this option.
When Allow Ethernet Data from Any IP Address is selected, it requires us to enter the IP address of the sending unit, the IP of the DeviceMaster that the data is expected from, in the following examples. The IP address is now serving double duty. It is indicating both the device that data is to be set to and received from when both Enable Serial to Ethernet and Enable Ethernet to Serial are enabled.
In the event that some incoming data from specific units may not need an acknowledgement (while other sending units do need acknowledgement) where the IP address of that sending unit is not included in the list, but the incoming data is needed, then this would be the time to enable this option. Remember that to send data back to the originating unit, that the Port number must also be used in addition to the IP address.
Enter the Target IP Address (serial- >eth) for each port, which is a list of destination IP addresses and port numbers for sending the serial data received as UDP packets.
When there has been no IP address indicated, there is no data sent. This address can also indicate that data is allowed to be received from the network when it has originated at the IP address specified in this list.
Enter the value of the UDP Listen Port, which is the specified port number to be used to listen for UDP data coming in on the Ethernet line.
This is the port number assigned to this particular port. This is used in the same manner as the TCP Port number assignments.
After verifying that the value for each item for the selected port is suitable, click Save.
Repeat Steps 3 through 6 for each port that you want to configure on the DeviceMaster.
Click Network | Security if you want to set up DeviceMaster security.
To configure any ports for RFC1006, go to Configuring RFC1006 (ISO Over TCP) to complete configuration.
You can verify the operation of your application and connections by checking for a change in the receive and transmit bytes on the Port Overview page.
The UDP Configuration Overview section provides you with detailed information about how to use the different types of UDP configuration methods.
The following examples use a DeviceMaster 1-port (DM1) and a DeviceMaster 4-port. The following information is static in all of the examples.
DM1 is configured to these network settings:
IP Address = 192.168.11.11 Mask = 255.255.255.0 Gateway = 192.168.11.1 DM4 is configured to these network settings:
IP Address = 192.168.11.41 Mask = 255.255.255.0 Gateway = 192.168.11.1.
In the examples, you can use this procedure to configure the serial portion of the DM1 and DM4.
Make sure that you have configured the network information into the DeviceMaster unit and it is connected to the network.
Note The default IP address is 192.168.250.250 for the DeviceMaster.
Enter the IP address of the DeviceMaster in the Address field of your web browser and press the Enter key.
Click the Port menu and then the appropriate port and configure it accordingly.
Serial Configuration:
Port Mode: RS-232
Baud Rate: 115200
Parity: None
Data bits: 8
Stop bits: 1
Flow Control: None
DTR Mode: off
Detect End of Line: Disabled
Serial Rx Buffer Timeout: 0
TCP Connection Configuration:
Make sure that Enabled is NOT checked and all other options at default.
In this example an DeviceMaster 1-port (DM1) forwards its incoming serial data out Ethernet to an DeviceMaster 4-port (DM4) to all four serial ports. Those four serial ports may connect to four different PCs, etc.
There are several steps in the procedure:
Example Application: A scale connected to an DM1 that sends its data to multiple monitoring PCs. Each PC receives the data at the same time and has no need to acknowledge the receipt of the data from the scale.
Use this procedure to configure one-to-many, one-way UDP data transfer. This example represents one serial port out to four serial ports.
Configure the DM1 serial characteristics as shown in the Overview in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Do not Enable Ethernet to Serial. This prevents data from the Ethernet side to be forwarded on to the serial side of the DM.
Do not Allow Ethernet Data From Any IP Address. This prevents any data from being accepted from any undesired UDP origination point.
Enter in Target IP Addresses and the Port numbers of the DM4 destination ports.
192.168.11.41 7000
192.168.11.41 7001
192.168.11.41 7002
192.168.11.41 7003
Click Save.
Configure Port 1 of the DM4 serial characteristics as shown in Step 3
Configure the UDP Connection Configuration as follows:
Do not Enable Serial to Ethernet. This prevents data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Do not Enable Ethernet Receive From Any IP Address. Leaving this disabled requires us to enter the IP address of the Sending unit, in this case, the IP of the DM1 in the Target IP Address field.
Enter the DM1 IP address of 192.168.11.11 in the Target IP Address field.
Note It is not necessary to enter the port value, but it may be a handy reminder of the sending port when a multiport units are used for troubleshooting and tracking purposes.
Click Save.
Configure Port 2 of the DM4 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Do not Enable Serial to Ethernet. This prevents data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Click Allow Ethernet Data From Any IP Address. With this enabled, it prevents the requirement for us to enter the IP address of the sending unit, in this case the IP of the DM1 in the Target IP Address field. If this option is enabled, any UDP packets are accepted regardless of the origination point, as long as the origination point includes this address as a destination. This does create possible security issues and is not recommended as a general course. Since the previous option is selected, it is NOT necessary to enter the IP of the DM in the Target IP field.
Note Keep in mind the security issues associated with this option.
Click Save.
Repeat the options from either Port 1 or Port 2 as desired for remaining ports
Use this procedure to test this configuration. This procedure uses Test Terminal, which is included in PortVision DX.
|
|
Attach a null-modem cable from COM2 on PC#1 to DM1 RS-232 port.
Use one of the methods below.
Install a multiport serial adapter into PC and connect each port of the DM4 to a port on the multiport serial adapter. This test has used a DeviceMaster 8-port (DM8) to create additional ports in the same PC that COM2 is being used in.
Attach a null-modem cable from COM2 on each PC to each DM4 RS-232 serial port.
Attach a null-modem cable from COM2 on PC#2 to DM4 Port#1
Attach a null-modem cable from COM2 on PC#3 to DM4 Port#2.
Attach a null-modem cable from COM2 on PC#4 to DM4 Port#3.
Attach a null-modem cable from COM2 on PC#5 to DM4 Port#4.
Open Test Terminal and Open COM2, setting the port parameters to match the DM1.
Open a second copy of Test Terminal and open four ports (in this example COMs3, 4, 5, and 6) set the port parameters to match the DM4.
Attach a null-modem cable from Port 1 of the DM4 to Port 1 of the DM8 (COM3).
Attach a null-modem cable from Port 2 of the DM4 to Port 2 of the DM8 (COM4).
Attach a null-modem cable from Port 3 of the DM4 to Port 3 of the DM8 (COM4).
Attach a null-modem cable from Port 4 of the DM4 to Port 4 of the DM8 (COM5).
In the COM2 window, type any character. This character should appear in COMs3, 4, 5, and 6 in the second copy of Test Terminal.
Note There is NO DATA RETURN to COM2 in this example.
In this example a DM 1-port (DM1) forwards its incoming serial data out Ethernet to an all four serial ports of a DM 4-port (DM4). The DM4 serial ports may connect to four different PCs, etc. Data is returned from the four ports to the DM1.
There are several steps in the procedure:
Example Application: A milling machine connected to an DM1 sends its data to multiple monitoring PCs. Each PC receives the data at the same time. One PC needs to acknowledge the receipt of the data and all PCs need the capability to send new instruction sets to the milling machine. In the situation of all PCs responding at the same time, all of the data is intermingled. There is NO means to differentiate the data to indicate the sending party. It is imperative that only one PC at a time send data.
Use this procedure to configure one-to-many, bi-directional UDP data transfer. This example represents one serial port out to four serial ports with a data reply.
Configure the DM1 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Do NOT Allow Ethernet Data From Any IP Address. Leaving this disabled requires us to enter the IP address of the sending unit, in this case the IP of the DM4 that the reply is expected from. The IP address is now serving double duty. It is indicating both the device that data is to be set to and received from.
Enter the Target IP Addresses and port numbers of the DM4 destination ports.
192.168.11.41 7000
192.168.11.41 7001
192.168.11.41 7002
192.168.11.41 7003
Here we are setting the IP addresses and individual port addresses to enable the data to be sent to all four ports. The port value is required only for outbound data. Since this is two-way data transferring, the port value is required. Inbound data only would require that the IP address be added once.
Click Save.
Configure Port 1 of the DM4 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Do NOT Allow Ethernet Data From Any IP Address. Leaving this disabled requires us to enter the IP address of the Sending unit, in this case the IP of the DM1 in the Target IP Address field.
Enter the IP address of 192.168.11.11 and Port 7000 for the DM1 in the Target IP Address field.
Note For bi-directional communications, it IS required to enter the port value of the DM1. In this case, 7000.
Click Save.
Configure Port 2 of the DM4 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Click Allow Ethernet Data From Any IP Address. When enabled, this prevents the requirement for us to enter the IP address of the sending unit, in this case the IP of the DM1 in the Target IP Address field. If this option is enabled any UDP packets are accepted, regardless of the origination point. This does create possible security issues and is not recommend as a general course.
Since the previous option is selected, it is NOT necessary to enter the IP of the DM in the Target IP field.
Note Now that bi-directional communication is desired, it is required that the IP address and port value of the DM1 be entered in the Target IP Address options so that the returning data know its destination.
Click Save.
Repeat the options from either Port 1 or Port 2 as desired for remaining ports.
This test procedure is slightly different from the test procedure illustrated in the previous subsection.
Follow Steps 1 through 5 in the Testing this Configuration discussion to start the test procedure.
In the COM3 (or COM4, 5, 6) type any character. This character should appear in COM2 in the first copy of Test Terminal.
To test that the data is not differentiated, place loopback plugs on the DM4.
Open COM2 and enter a character. This character should be repeated four times (once for each port) with no indication of which port sent which character.
Note There is DATA RETURN to COM2 in this example.
In this example an DM 4-port (DM4), using all four serial ports, forwards its incoming serial data from all four ports out through Ethernet to an DM1 connected to the PC COM2 by means of a null-modem cable. The four serial ports may connect to four different PCs, scales, etc.
There are several steps in the procedure:
Example Application: A scale is connected to each of the DM4 ports and sends its data to a single monitoring PC (COM2). Each scale sends its data in sequence and no two scales send data at the same time. This is critical as there is no means by which data can be identified as to the sending port, and the data is intermingled. For example: Port 1 sends ABCD and Port 2 sends 1234, both at the same time. The data seen in COM2 may be A1B2CD34.
Use this procedure to configure many-to-one, one-way UDP data transfer. This example represents four serial ports out to one serial port.
Configure the DM1 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Do NOT Enable Serial to Ethernet. This prevents data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Do NOT Allow Ethernet Data From Any IP Address. Leaving this disabled requires us to enter the IP address of the sending unit, in this case the IP of the DM4 in the Target IP Address field.
Enter the IP address of 192.168.11.41 as the DM4 in the Target IP Address field. Since all four ports are in the same DM, all on the same IP address, it is not necessary to enter the IP address more than once. The receiving side does not know the sending port nor does it need to know the sending port value (7000, 7001, etc.).
Note It is not necessary to enter the port value, but it may be a handy reminder of the sending port when several multiport units are used, for trouble shooting and tracking purposes.
Click Save.
Configure Port 1 of the DM4 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Do NOT Enable Ethernet to Serial. This prevents data from the Ethernet side to be forwarded on to the serial side of the DM.
Do not Allow Ethernet Data From Any IP Address. This prevents any data from being accepted from any UDP origination point. We are not setting this unit up to accept any data.
Enter the IP address of 192.168.11.11 and Port 7000 for the DM1 in the Target IP Address field.
Note This is the destination of the data.
Click Save.
Repeat the port configuration options for the remaining ports.
This test procedure is slightly different from the test procedure illustrated in the previous subsection.
Follow Steps 1 through 5 in the Testing this Configuration discussion (One-to-Many, One-Way UDP Data Transfer Configuration) to start the test procedure.
In the COM3, 4, 5, and 6 windows, type any character. This character should appear in COM2 in Test Terminal. If two or more, of COMs3, 4, 5, or 6 sends data at the same time, the data is merged in COM2 with no way to tell which device sent which information. COMs3, 4, 5, and 6 must use a round-robin approach so that the data may be properly evaluated.
Note There is NO DATA RETURN to COMs3, 4, 5, or 6 in this example. Entering of any data into COM2 is not transmitted back to COM3, 4, 5, or 6.
In this example an DM 4-port (DM4), using all four serial ports, forwards its incoming serial data from all four ports out through Ethernet to an DM1 connected to the PC COM2 by means of a null-modem cable. The four serial ports may connect to four different PCs, scales, etc. Data is returned from the DM1 to the four ports.
There are several steps in the procedure:
Example Application: A scale is connected to each of the DM4 ports and it sends data to a single monitoring PC (COM2). Each scale sends its data in sequence and no two scales send data at the same time. This is critical as there is no means by which data can be identified as to the sending port, and the data is intermingled. For example: Port 1 sends ABCD and Port 2 sends 1234, both at the same time. The data seen in COM2 may be A1B2CD34. Once data has been received from all four ports, the application needs to send an acknowledgment so that the scale can reset in preparation for the next measurement.
Use this procedure to configure many-to-one, one-way UDP data transfer. This example represents four serial ports out to out serial port with data reply.
Configure the DM1 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Do NOT Allow Ethernet Data From Any IP Address. Leaving this disabled requires us to enter the IP address of the sending unit, in this case the IP of the DM4 in the Target IP Address field.
Enter the IP address of 192.168.11.41 as the DM4 in the Target IP Address field. Since we want replies to be sent to each of the four ports on the DM4 unit, we must enter the IP addresses and port values of each port.
192.168.11.41 7000
192.168.11.41 7001
192.168.11.41 7002
192.168.11.41 7003
Configure Port 1 of the DM4 serial characteristics as shown in Step 3.
Configure the UDP Connection Configuration as follows:
Click Enable Serial to Ethernet. This allows data from the serial side, to be forwarded on to the Ethernet side, of the DM.
Click Enable Ethernet to Serial. This allows data from the Ethernet side to be forwarded on to the serial side of the DM.
Do NOT Allow Ethernet Data From Any IP Address. This prevents any data from being accepted from any UDP origination point.
Enter the IP address of 192.168.11.11 and Port 7000 for the DM1 in the Target IP Address field.
Note This is the destination of the data and with it entered in the field and both Enable Serial to Ethernet and Enable Ethernet to Serial, data flows both directions.
Repeat the Port Configuration options for the remaining ports.
Follow Steps 1 through 5 in the Testing this Configuration discussion (One-to-Many, One-Way UDP Data Transfer Configuration) to start the test procedure.
In the COM3, 4, 5, and 6 windows, type any character. This character should appear in COM2 in Test Terminal. If two or more of COM3, 4, 5, or 6 sends data at the same time, the data is merged in COM2 with no way to tell which device sent which information. COMs3, 4, 5, and 6 must use a round-robin approach so that the data may be properly evaluated.
Note There is DATA RETURN to COM3,4,5 or 6 in this example. Entering of any data into COM2 is transmitted back to COM3,4,5 or 6 simultaneously.
