RUGGEDCOM DIRECTOR
User Guide
ii
Copyright © 2017 Siemens Canada Ltd
All rights reserved. Dissemination or reproduction of this document, or evaluation and communication of its contents, is not authorized
except where expressly permitted. Violations are liable for damages. All rights reserved, particularly for the purposes of patent application or
trademark registration.
This document contains proprietary information, which is protected by copyright. All rights are reserved. No part of this document may be
photocopied, reproduced or translated to another language without the prior written consent of Siemens Canada Ltd.
Disclaimer Of Liability
Siemens has verified the contents of this document against the hardware and/or software described. However, deviations between the product
and the documentation may exist.
Siemens shall not be liable for any errors or omissions contained herein or for consequential damages in connection with the furnishing,
performance, or use of this material.
The information given in this document is reviewed regularly and any necessary corrections will be included in subsequent editions. We
appreciate any suggested improvements. We reserve the right to make technical improvements without notice.
Registered Trademarks
RUGGEDCOM™ and ROS™ are trademarks of Siemens Canada Ltd.
Other designations in this manual might be trademarks whose use by third parties for their own purposes would infringe the rights of the
owner.
Open Source
RUGGEDCOM DIRECTOR contains Open Source Software. For license conditions, refer to the associated License Conditions document.
Security Information
Siemens provides products and solutions with industrial security functions that support the secure operation of plants, machines, equipment
and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens' products and solutions
undergo continuous development. Siemens recommends strongly that you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and
integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be
considered. For more information about industrial security, visit http://www.siemens.com/industrialsecurity.
To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visit http://
support.automation.siemens.com.
Warranty
Refer to the License Agreement for the applicable warranty terms and conditions, if any.
For warranty details, visit www.siemens.com/ruggedcom or contact a Siemens customer service representative.
Contacting Siemens
Address
Siemens Canada Ltd
Industry Sector
300 Applewood Crescent
Concord, Ontario
Canada, L4K 5C7
Telephone
Toll-free: 1 888 264 0006
Tel: +1 905 856 5288
Fax: +1 905 856 1995
E-mail
ruggedcom.info.i-ia@siemens.com
Web
www.siemens.com/ruggedcom
RUGGEDCOM DIRECTOR
User Guide
Table of Contents
iii
Table of Contents
Preface ............................................................................................................. v
Alerts .................................................................................................................................................. v
Accessing Documentation .................................................................................................................... vi
Training .............................................................................................................................................. vi
Customer Support ............................................................................................................................... vi
Chapter 1
Introduction ..................................................................................................... 1
1.1Features ....................................................................................................................................... 2
1.2Security Recommendations ............................................................................................................ 2
1.3Data Execution Prevention ............................................................................................................. 3
1.4Use Cases ..................................................................................................................................... 3
1.5Requirements ............................................................................................................................... 3
1.5.1System Requirements ......................................................................................................... 4
1.5.2Installation Notes ............................................................................................................... 4
1.5.3Enabling Telnet Client In Windows ...................................................................................... 4
1.5.4Microsoft Windows Firewall ................................................................................................ 5
Chapter 2
User Interface ................................................................................................... 7
2.1Main Window ............................................................................................................................... 7
2.1.1Connection Table ............................................................................................................... 8
2.1.2Main Window Display Columns ........................................................................................... 8
2.1.2.1Color-Coded Indicators ............................................................................................ 9
2.1.2.2Operations On Table Entries ................................................................................... 10
2.1.3Main Window Buttons ...................................................................................................... 11
2.1.4Main Window Menu Bar ................................................................................................... 11
2.2Dialog Boxes ............................................................................................................................... 13
2.2.1Add a Virtual Serial Port ................................................................................................... 13
2.2.2Configure a Serial Device .................................................................................................. 15
2.2.3Start ROS Trace ................................................................................................................ 16
Chapter 3
Using RUGGEDCOM DIRECTOR ......................................................................... 17
3.1Configuring a New Virtual Serial Port Connection .......................................................................... 17
Table of Contents
RUGGEDCOM DIRECTOR
User Guide
iv
3.2Multiple Connections to the Same Port ......................................................................................... 18
3.3Configuring Multiple Connections At Once ................................................................................... 18
3.4Configuration Auto-Saving ........................................................................................................... 19
3.5ROS Trace ................................................................................................................................... 19
3.5.1Starting and Stopping ROS Trace ....................................................................................... 19
3.5.2ROS Trace Files ................................................................................................................ 20
3.5.3Configuring ROS Trace ...................................................................................................... 21
3.5.4Sample Trace File ............................................................................................................. 21
Chapter 4
Theory of Operation ........................................................................................ 27
4.1Principles of Operation ................................................................................................................ 27
4.2Serial Control Signals .................................................................................................................. 28
RUGGEDCOM DIRECTOR
User Guide
Preface
Alerts v
Preface
This guide describes the RUGGEDCOM DIRECTOR serial redirection software utility which, in conjunction with
RUGGEDCOM server networking products, extends the reach of traditional serial communications across IP
networks. It contains instructions and guidelines on how to use the software, as well as some general theory.
It is intended for use by network technical support personnel who are familiar with the operation of networks. It is
also recommended for us by network and system planners, system programmers, and line technicians.
CONTENTS
•“Alerts”
•“Accessing Documentation”
•“Training”
•“Customer Support”
Alerts
The following types of alerts are used when necessary to highlight important information.
DANGER!
DANGER alerts describe imminently hazardous situations that, if not avoided, will result in death or
serious injury.
WARNING!
WARNING alerts describe hazardous situations that, if not avoided, may result in serious injury and/or
equipment damage.
CAUTION!
CAUTION alerts describe hazardous situations that, if not avoided, may result in equipment damage.
IMPORTANT!
IMPORTANT alerts provide important information that should be known before performing a procedure
or step, or using a feature.
NOTE
NOTE alerts provide additional information, such as facts, tips and details.
Preface
RUGGEDCOM DIRECTOR
User Guide
vi Accessing Documentation
Accessing Documentation
The latest user documentation for RUGGEDCOM DIRECTOR v1.4 is available online at
www.siemens.com/ruggedcom. To request or inquire about a user document, contact Siemens Customer Support.
Training
Siemens offers a wide range of educational services ranging from in-house training of standard courses on
networking, Ethernet switches and routers, to on-site customized courses tailored to the customer's needs,
experience and application.
Siemens' Educational Services team thrives on providing our customers with the essential practical skills to make
sure users have the right knowledge and expertise to understand the various technologies associated with critical
communications network infrastructure technologies.
Siemens' unique mix of IT/Telecommunications expertise combined with domain knowledge in the utility,
transportation and industrial markets, allows Siemens to provide training specific to the customer's application.
For more information about training services and course availability, visit www.siemens.com/ruggedcom or
contact a Siemens Sales representative.
Customer Support
Customer support is available 24 hours, 7 days a week for all Siemens customers. For technical support or general
information, contact Siemens Customer Support through any of the following methods:
Online
Visit http://www.siemens.com/automation/support-request to submit a Support Request (SR) or check
on the status of an existing SR.
Telephone
Call a local hotline center to submit a Support Request (SR). To locate a local hotline center, visit http://
www.automation.siemens.com/mcms/aspa-db/en/automation-technology/Pages/default.aspx.
Mobile App
Install the Industry Online Support app by Siemens AG on any Android, Apple iOS or Windows mobile
device and be able to:
• Access Siemens' extensive library of support documentation, including FAQs and manuals
• Submit SRs or check on the status of an existing SR
• Contact a local Siemens representative from Sales, Technical Support, Training, etc.
• Ask questions or share knowledge with fellow Siemens customers and the support community
RUGGEDCOM DIRECTOR
User Guide
Chapter 1
Introduction
1
Introduction
RUGGEDCOM DIRECTOR is a software utility that creates virtual COM port-style serial device interfaces on
computer systems running the following operating systems: Microsoft Windows 7 (32 and 64 bit), Windows
7 Embedded (32 bit, running on an APE card), Windows 8 (32 and 64 bit), Windows 10 (32 and 64 bit),
and Microsoft Windows Server 2012 (64 bit). Each virtual serial port is connected across an IP network to a
corresponding serial interface on a RUGGEDCOM server device.
Application software that ordinarily connects to a given device via local serial port hardware can thus be made to
connect, transparently, to the same device via a remote ROS-based serial server, located anywhere within reach of
an IP network.
RUGGEDCOM DIRECTOR is installed as a service in Windows. This means virtual serial port connections configured
using RUGGEDCOM DIRECTOR run in the background by default, even when RUGGEDCOM DIRECTOR is not
running.
Following a system reboot, previously configured connections will resume automatically. When RUGGEDCOM
DIRECTOR is restarted, active virtual connections are visible in the main window.
NOTE
Virtual serial port traffic (bytes) and IP traffic (packets) are only counted when the RUGGEDCOM
DIRECTOR user interface is running.
IMPORTANT!
RUGGEDCOM DIRECTOR is intended to control only legacy serial devices over IP, as all information
in serial communication traces is in plain text, including any possible login credentials required for
accessing remote devices. Legacy telecontrol protocols that need RUGGEDCOM DIRECTOR do not
normally require login information. Using RUGGEDCOM DIRECTOR to control ROS devices in such a
manner is not recommended.
RUGGEDCOM DIRECTOR has no access control and no security features to handle sensitive data.
Using the Windows login mechanism, make sure the use of RUGGEDCOM DIRECTOR and access to the
configuration data is only possible by authorized personnel.
CONTENTS
•Section1.1, “Features”
•Section1.2, “Security Recommendations”
•Section1.3, “Data Execution Prevention”
•Section1.4, “Use Cases”
•Section1.5, “Requirements”
Chapter 1
Introduction
RUGGEDCOM DIRECTOR
User Guide
2 Features
Section1.1
Features
• Transparent COM-port virtualization and redirection via IP.
• No application level support is necessary. RUGGEDCOM DIRECTOR provides an application interface identical to
that of hardware COM-ports.
• Compact, detailed main window displays a complete summary all configured connections.
• Supports up to 128 simultaneous connections.
• Detailed port status, logging and tracing.
• Built-in knowledge of all models of RUGGEDCOM server devices assists in the configuration of multiple
connections.
• Convenient Telnet connection to serial server management interface.
• Background mode operation in System Tray.
• Access throughout the program to context-sensitive help.
Section1.2
Security Recommendations
The computer system running RUGGEDCOM DIRECTOR and the RUGGEDCOM DIRECTOR software should be
appropriately secured.
Authentication
• Replace the default passwords for all user accounts and processes (where applicable).
• Use strong passwords. Avoid weak passwords such as password1, 123456789, abcdefgh, etc.
• Make sure passwords are protected and not shared with unauthorized personnel.
• Passwords should not be re-used across different user names and systems, or after they expire.
• Record passwords (including device passwords) in a safe, secure, off-line location for future retrieval should
they be misplaced.
• File transfer protocols – FTP, HTTP, NFS and Windows File sharing – should not allow unauthenticated access to
RUGGEDCOM DIRECTOR software, configuration or database directories.
Physical/Remote Access
• Make sure RUGGEDCOM DIRECTOR is deployed behind a corporate firewall.
• Be aware of any non-secure protocols enabled on the device. While some protocols, such as HTTPS, SSH
and SNMPv3, are secure, others, such as Telnet and RCDP, were not designed for this purpose. Appropriate
safeguards against non-secure protocols should be taken to prevent unauthorized access to RUGGEDCOM
DIRECTOR and the network.
• Use RUGGEDCOM DIRECTOR in a secured environment with controlled and monitored network access and local
machine access.
• SSH connections to RUGGEDCOM ROS devices via RUGGEDCOM DIRECTOR do not use strict host key checking.
Make sure to verify the identity of any RUGGEDCOM ROS devices before connecting to them.
RUGGEDCOM DIRECTOR
User Guide
Chapter 1
Introduction
Data Execution Prevention 3
Policy
• Periodically audit the use, installation and configuration of RUGGEDCOM DIRECTOR to make sure it complies
with these recommendations and/or any internal security policies.
• Review the user documentation for other Siemens products used in coordination with RUGGEDCOM DIRECTOR
for further security recommendations.
• For increased security, Siemens recommends enabling Data Execution Prevention (DEP) when using
RUGGEDCOM DIRECTOR. For more information about DEP, refer to Section1.3, “Data Execution Prevention”.
• For the latest information on security issues for Siemens products, visit the Industrial Security website
[http://www.industry.siemens.com/topics/global/en/industrial-security/news-alerts/Pages/alerts.aspx] or
the ProductCERT Security Advisories website [http://www.siemens.com/innovation/en/technology-focus/
siemens-cert/cert-security-advisories.htm]. Updates to Siemens Product Security Advisories can be obtained
by subscribing to the RSS feed on the Siemens ProductCERT Security Advisories website, or by following
@ProductCert on Twitter.
Section1.3
Data Execution Prevention
Data Execution Prevention (DEP) helps protect workstations by monitoring programs to make sure they use system
memory safely. If DEP notices a program using memory incorrectly, it automatically closes the program and sends
a notification.
For increased security, Siemens recommends enabling DEP when using RUGGEDCOM DIRECTOR. For more
information about DEP, including instructions on how to enable DEP, visit www.microsoft.com.
Section1.4
Use Cases
Some common uses of RUGGEDCOM DIRECTOR are:
•Remote Monitoring/Control: Serial devices may be controlled or monitored from computer systems at remote
sites.
•Consolidation/Centralization: Multiple software applications running on a single central computer system can
access serial devices at various remote sites across an IP network.
Section1.5
Requirements
This section sets out the hardware, software, and networking environment required in order to correctly install
and operate Siemens's RUGGEDCOM DIRECTOR serial redirector application.
CONTENTS
•Section1.5.1, “System Requirements”
•Section1.5.2, “Installation Notes”
•Section1.5.3, “Enabling Telnet Client In Windows”
Chapter 1
Introduction
RUGGEDCOM DIRECTOR
User Guide
4 System Requirements
•Section1.5.4, “Microsoft Windows Firewall”
Section1.5.1
System Requirements
RUGGEDCOM DIRECTOR must be installed and run with administrative privileges on a computer running Microsoft
Windows. It has been tested against and verified to operate correctly under Microsoft Windows 7 (32 and 64 bit),
Windows 7 Embedded (32 bit, running on an APE card), Windows 8 (32 and 64 bit), Windows 10 (32 and 64 bit),
and Microsoft Windows Server 2012 (64 bit).
RUGGEDCOM DIRECTOR must be run on a computer with a network card installed. The network card must be
configured to use TCP/IP and have a valid IPv4 address.
An Internet connection is not required to install and run RUGGEDCOM DIRECTOR but Microsoft Internet Explorer is
required to make use of the integrated online Help (accessed via Help links within the software).
Section1.5.2
Installation Notes
The installation program contains the RUGGEDCOM DIRECTOR application, integrated online help, PDF
documentation, and all supporting software libraries required by the application. The RUGGEDCOM DIRECTOR
installation program unpacks all files into a user-selectable directory.
NOTE
The online Help is displayed in a Web browser running with full administrator privileges. During
installation, you have the option to disable the online Help. Select No when asked if you want to install
the user guide, and this will disable the online Help.
Section1.5.3
Enabling Telnet Client In Windows
To take advantage of the RUGGEDCOM DIRECTOR Telnet connection feature, Telnet Client must be enabled in
Microsoft Windows. In some Windows versions, this option is disabled by default. For more information about
enabling the Telnet Client, visit www.microsoft.com.
The following steps outline the typical Telnet Client enable procedure in Windows:
1. Open the Control Panel.
2. Click on Programs and Features.
3. In Programs and Features, click on Turn Windows features on or off.
4. In the list of Windows features, check the box beside: "Telnet Client".
5. Click OK.
RUGGEDCOM DIRECTOR
User Guide
Chapter 1
Introduction
Microsoft Windows Firewall 5
Section1.5.4
Microsoft Windows Firewall
Depending on the settings of the network firewall built in to Microsoft Windows operating systems, a warning
similar to the following might be displayed when RUGGEDCOM DIRECTOR attempts to make a network connection
to a RUGGEDCOM server:
Figure1:Windows Firewall Warning
If this warning is displayed, it is recommended to allow access for RUGGEDCOM DIRECTOR to operate correctly.
Chapter 1
Introduction
RUGGEDCOM DIRECTOR
User Guide
6 Microsoft Windows Firewall
RUGGEDCOM DIRECTOR
User Guide
Chapter 2
User Interface
Main Window 7
User Interface
The RUGGEDCOM DIRECTOR user interface centers on a main window, which displays all configured virtual serial
port connections along with basic status and statistical information, along with commonly needed controls.
CONTENTS
•Section2.1, “Main Window”
•Section2.2, “Dialog Boxes”
Section2.1
Main Window
The RUGGEDCOM DIRECTOR main window is displayed after initialization:
Figure2:Main Window
The RUGGEDCOM DIRECTOR main window consists of four main components:
• A series of columns summarizing key information.
• A column of navigational buttons on the right side of the window.
• A menu bar across the top of the window with a series of drop-down menus.
• A status bar along the bottom of the window, which displays context-sensitive program status.
Chapter 2
User Interface
RUGGEDCOM DIRECTOR
User Guide
8 Connection Table
This section describes these components in more detail.
CONTENTS
•Section2.1.1, “Connection Table”
•Section2.1.2, “Main Window Display Columns”
•Section2.1.3, “Main Window Buttons”
•Section2.1.4, “Main Window Menu Bar”
Section2.1.1
Connection Table
The main window display lists all the remote serial connections configured in RUGGEDCOM DIRECTOR. The
connection list may be customized in the following ways:
•Sorting: The entire display may be sorted on the basis of any one of the columns (including the Server IP:Port
column). Clicking on a column title will sort the whole list in increasing order of the items in that column.
Clicking again will sort in decreasing order.
•Resizing: Each column may be resized by clicking and dragging the rightmost edge of a column title.
Section2.1.2
Main Window Display Columns
Figure3:Main Window Display Columns
RUGGEDCOM DIRECTOR's main window displays configuration, status, and connection statistics for each serial
redirector configuration entry. The columns displayed are:
Status Indicator The color of the indicator in the leftmost column represents the status of the corresponding
connection, and changes in real time in response to changes in status. For more information
on this feature, see the section on Section2.1.2.1, “Color-Coded Indicators”.
Server Name The serial server name, to identify a particular connection. The name may be entered
manually or generated automatically.
RUGGEDCOM DIRECTOR
User Guide
Chapter 2
User Interface
Color-Coded Indicators 9
Virtual Port Virtual serial port number (e.g. COM5, COM6, etc.).
Server IP: Port The IP address and port number of the serial server to which the corresponding virtual serial
port is redirected (e.g. 192.168.0.1:5555).
Connection Status The connection status represents the network connection between RUGGEDCOM DIRECTOR
and the corresponding serial server.
Rx Chars The number of bytes received via the virtual serial port.
Tx chars The number of bytes transmitted via the virtual serial port.
Rx Packets The number of packets received via the virtual serial port.
Tx Packets The number of packets transmitted via the virtual serial port.
CONTENTS
•Section2.1.2.1, “Color-Coded Indicators”
•Section2.1.2.2, “Operations On Table Entries”
Section2.1.2.1
Color-Coded Indicators
An icon in the leftmost column of each entry displays the status of RUGGEDCOM DIRECTOR's connection to the
corresponding serial server:
• Green indicates that the connection is established and is ready to use.
• Red indicates that an error has occurred on this connection.
• Gray indicates that the connection is stopped or has not yet been started.
If the indicator is red, the status bar at the bottom of the window will display a brief explanation when the list item
is clicked on.
The interpretation of the status indication varies slightly for TCP versus UDP connections.
TCP Connection Status Summary
Connected The corresponding virtual serial port connection has been started, RUGGEDCOM DIRECTOR
has successfully established a network connection with the RUGGEDCOM server and is ready
to pass data on the virtual serial port.
Error An attempt to start the corresponding virtual serial port connection has been made, but
RUGGEDCOM DIRECTOR cannot connect to the specified serial server.
Stopped The corresponding virtual serial port connection has been stopped by the user.
UDP Connection Status Summary
Since UDP is not a connection-oriented protocol, the status of UDP-based virtual serial port connections must be
reported differently.
Started The corresponding virtual serial port connection has been started, and RUGGEDCOM
DIRECTOR is able to reach the serial server via the network.
Chapter 2
User Interface
RUGGEDCOM DIRECTOR
User Guide
10 Operations On Table Entries
Error The corresponding virtual serial port connection has been started, and RUGGEDCOM
DIRECTOR is not able to reach the serial server via the network.
Stopped The corresponding virtual serial port connection has been stopped by the user.
Section2.1.2.2
Operations On Table Entries
Several operations and shortcuts are supported when clicking on individual list entries in the main window:
•Clicking or Double-clicking on an entry selects the entry.
•Right-clicking on an entry brings up the Right Mouse menu (note that all actions in the menu will apply to all
currently highlighted entries rather than to only the entry that is being right-clicked).
•Shift-clicking on an entry selects a range of information between a previously clicked entry and the one
currently being shift-clicked.
•Ctrl-clicking on an entry toggles the selection state of the corresponding item. This allows the detailed selection
of a group, or of a discontinuous range.
Right Mouse Menu
The Right Mouse Menu, illustrated below, is accessed by right-clicking anywhere in the main window. Actions in
this menu will apply to highlighted entries rather than only the entry that is being right-clicked.
Figure4:Right Mouse Menu
Add Add a virtual serial port configuration to the list via the Add Virtual Port dialog box. For more
information, refer to Section2.2.1, “Add a Virtual Serial Port”.
Remove Remove the selected virtual serial ports from the list.
Start Enable bidirectional communication on the selected virtual serial port connection(s).
Stop Disable bidirectional communication on the selected virtual serial port connection(s).
Configure Display the configuration editor for the selected COM port. For more information, refer to
Section2.2.2, “Configure a Serial Device”.
Telnet Open a Telnet session to the corresponding serial server's management interface.
RUGGEDCOM DIRECTOR
User Guide
Chapter 2
User Interface
Main Window Buttons 11
Section2.1.3
Main Window Buttons
Five buttons are located in a column to the right of the main display window. These provide rapid and convenient
access to the most commonly required functions of RUGGEDCOM DIRECTOR. The buttons are described below.
Add virtual serial ports.
Remove virtual serial ports from a list.
Show COM port details.
Show the configuration editor.
Open a Telnet session.
Section2.1.4
Main Window Menu Bar
Figure5:Main Menu Bar
The following sections describe the commands that are accessible from the main menu bar (pictured above) at the
top of the main window.
File Menu
Figure6:File Menu
Save session Save the current configuration to a specified file.
Load session Load a configuration from a specified file.
Exit Terminate RUGGEDCOM DIRECTOR.
Chapter 2
User Interface
RUGGEDCOM DIRECTOR
User Guide
12 Main Window Menu Bar
View Menu
Figure7:View Menu
Telnet Open a Telnet session to the selected serial server's management interface.
Device Menu
Figure8:Device Menu
Add Add virtual serial ports to the list (bring up an Add Virtual Port dialog box). For more
information, refer to Section2.2.1, “Add a Virtual Serial Port”.
Remove Remove the selected virtual serial ports from the list.
Start Enable bidirectional communication on the selected virtual serial port connection(s).
Stop Disable bidirectional communication on the selected virtual serial port connection(s).
Configure Show the configuration editor for the selected COM port. For more information, refer to
Section2.2.2, “Configure a Serial Device”.
ROS Trace Menu
Figure9:ROS Trace Menu
Start ROS Trace Open the Start ROS Trace dialog box, which will start a ROS Trace. For more information,
refer to Section2.2.3, “Start ROS Trace” and Section3.5, “ROS Trace”.
Stop ROS Trace Stop a ROS Trace.
Show in folder Display a Windows Explorer folder that contains ROS Trace files (output files).
RUGGEDCOM DIRECTOR
User Guide
Chapter 2
User Interface
Dialog Boxes 13
Help Menu
Figure10:Help Menu
User guide Open the user guide for RUGGEDCOM DIRECTOR.
About RUGGEDCOM DIRECTOR Show the version number and support information.
NOTE
Selecting No for the option to install the user guide during installation disables the online Help. If the
online Help is disabled, selecting User guide displays a dialog box that says "Help file not found."
Section2.2
Dialog Boxes
This section describes in detail the special-function dialog windows referred to from various places in the main
interface window.
CONTENTS
•Section2.2.1, “Add a Virtual Serial Port”
•Section2.2.2, “Configure a Serial Device”
•Section2.2.3, “Start ROS Trace”
Section2.2.1
Add a Virtual Serial Port
This dialog box is used to create a configuration set by specifying information for a remote RUGGEDCOM server,
which may serve several serial port connections at once.
Chapter 2
User Interface
RUGGEDCOM DIRECTOR
User Guide
14 Add a Virtual Serial Port
Figure11:Add Virtual Serial Port Dialog Box
Server Model The model of RUGGEDCOM server to connect to.
Number of ports The number of ports to configure. This parameter is filled in automatically by RUGGEDCOM
DIRECTOR based on the RUGGEDCOM server model, but may be overridden.
IP Address:Port The IP address and starting port number of the serial server. Note that the ending port
number is generated based on the starting port and the total number to configure.
Server Name A name that identifies a particular configuration. The name is generated automatically but
may be overridden.
Transport Method The IP protocol to use for connections in this configuration. Briefly, TCP guarantees delivery
at the potential cost of increased latency, and UDP does not guarantee delivery, but can offer
lower latency.
Local Port (UDP only) The starting UDP port number of local (to RUGGEDCOM DIRECTOR's system) connections
to the serial server. Note that the ending port number is generated based on the starting
port and the total number to configure. Note also that for TCP connections, this parameter is
neither displayed nor needed.
Virtual Serial Port The virtual system COM ports to create for this configuration. Note that the starting port is
specified, and the remainder are automatically created incrementally, skipping any ports that
may already have been allocated.
Add Add the virtual serial port configuration to RUGGEDCOM DIRECTOR.
Cancel Cancel the operation.
Help Display user guide information about the dialog box.
NOTE
The number of ports that may be configured at a time is between one and the maximum serial port
supported by the selected model of RUGGEDCOM server. The default IP port will be filled in after the
RUGGEDCOM DIRECTOR
User Guide
Chapter 2
User Interface
Configure a Serial Device 15
server model is chosen. A unique name will be generated each time based on the server model and any
existing configuration.
Section2.2.2
Configure a Serial Device
This dialog box is used to modify the settings of an existing single configured connection.
Figure12:Configure Device Dialog Box
IP Address:Port The IP address of the serial server and port number of the virtual serial port connection.
Server Name A name that identifies the connection.
Transport Method The IP protocol to use for connections in this configuration. Briefly, TCP guarantees delivery
at the potential cost of increased latency, and UDP does not guarantee delivery, but can
offer lower latency. Note that the transport method cannot be changed for an existing
connection.
Virtual Serial Port The virtual system COM ports to use for this connection.
OK Save the configuration.
Cancel Cancel the reconfiguration.
Help Display user guide information about the dialog box.
Chapter 2
User Interface
RUGGEDCOM DIRECTOR
User Guide
16 Start ROS Trace
Section2.2.3
Start ROS Trace
This dialog box is used to start a ROS Trace. For more information on this feature, see Section3.5, “ROS Trace”.
Figure13:Start ROS Trace Dialog Box
The buttons on the Start ROS Trace dialog box are:
Start Start a ROS Trace.
Cancel Cancel a ROS Trace.
RUGGEDCOM DIRECTOR
User Guide
Chapter 3
Using RUGGEDCOM DIRECTOR
Configuring a New Virtual Serial Port Connection 17
Using RUGGEDCOM DIRECTOR
This section describes how to configure RUGGEDCOM DIRECTOR.
CONTENTS
•Section3.1, “Configuring a New Virtual Serial Port Connection”
•Section3.2, “Multiple Connections to the Same Port”
•Section3.3, “Configuring Multiple Connections At Once”
•Section3.4, “Configuration Auto-Saving”
•Section3.5, “ROS Trace”
Section3.1
Configuring a New Virtual Serial Port Connection
To configure one or more virtual serial port connections between RUGGEDCOM DIRECTOR and a RUGGEDCOM
server device, one must first configure the server to provide as many RawSocket connections as required. Once
these are configured, RUGGEDCOM DIRECTOR can then be configured to connect to the server ports.
NOTE
For more information about how to configure RawSocket connections, refer to the ROS User Guide for
the RUGGEDCOM device available at www.siemens.com/ruggedcom.
The following information is needed at the server in order to configure a RawSocket connection that may be
connected to using RUGGEDCOM DIRECTOR:
• RUGGEDCOM server serial port number(s)
• Connection method (TCP or UDP)
• RUGGEDCOM DIRECTOR IP address
• TCP port number or UDP port numbers at both server and RUGGEDCOM DIRECTOR ends
The following information is needed at RUGGEDCOM DIRECTOR in order to configure a virtual serial port
connection to a RUGGEDCOM server:
• Starting COM port number
• Connection method (TCP or UDP)
• IP address/remote TCP port number or IP address/local and remote UDP port numbers
• RUGGEDCOM server model
For detail on configuring a new connection or series of connections, refer to Section2.2.1, “Add a Virtual Serial
Port”.
Chapter 3
Using RUGGEDCOM DIRECTOR
RUGGEDCOM DIRECTOR
User Guide
18 Multiple Connections to the Same Port
Section3.2
Multiple Connections to the Same Port
It is possible to connect several RUGGEDCOM DIRECTOR virtual serial ports to the same serial port on a
RUGGEDCOM server. It is important to set the MaxConns parameter for the RawSocket configuration to accept as
many connections as are required.
Section3.3
Configuring Multiple Connections At Once
RUGGEDCOM DIRECTOR will create virtual COM ports for as many serial ports as are supported by the model
of RUGGEDCOM server being connected to. Any of these automatically created configuration entries may be
modified afterwards. For example, RUGGEDCOM DIRECTOR will create a configuration RS400 consisting of four
serial ports. If only three connections are needed, the surplus one may be deleted.
NOTE
The main window displays only the counted packets for one TCP connection to the same port of a serial
server at a time. For more information about the main window display, refer to Section2.1.2, “Main
Window Display Columns”.
In order for RUGGEDCOM DIRECTOR's auto-configuration process to work, the following convention must be
followed for the server's own configuration. For all server serial ports that are to be used with RUGGEDCOM
DIRECTOR:
• All of a given server's serial ports must share the same IP address as the server itself.
• The connection protocol (TCP or UDP) must be common to all ports.
• The TCP or UDP port numbers of each port must be in sequence.
A typical RUGGEDCOM DIRECTOR/server configuration is illustrated below:
Figure14:Add Range Configuration
Only currently unassigned COM ports will be displayed in the selection drop box. The auto-configuration process
skips unavailable COM port numbers when creating a series of virtual ports. For example, if the user wants
to add three ports starting with COM5, but COM 7 and 8 are in use, then RUGGEDCOM DIRECTOR will create
configurations for COM5, COM6, and COM9. To remove an existing virtual port form the list, simply select the
relevant line in the main window and press the Remove button.
RUGGEDCOM DIRECTOR
User Guide
Chapter 3
Using RUGGEDCOM DIRECTOR
Configuration Auto-Saving 19
Section3.4
Configuration Auto-Saving
Connections configured using RUGGEDCOM DIRECTOR are persistent: configuration information is saved
automatically at the time RUGGEDCOM DIRECTOR is terminated, and is reloaded each time RUGGEDCOM
DIRECTOR is started.
NOTE
Configuration is usually saved explicitly via the Save session option. For more information, refer to
“File Menu”.
NOTE
When multiple simultaneous connections have been saved, RUGGEDCOM DIRECTOR can take several
minutes to reload the connections at start up.
Section3.5
ROS Trace
RUGGEDCOM DIRECTOR has a tracing feature called ROS Trace. Using ROS Trace, you can set up a remote server
and enable tracing on a ROS device. ROS Trace then listens for any incoming data from a ROS device.
The status of ROS Trace is displayed in the bottom right corner of the page. Depending on the status, the status
message will say "ROS Trace Enabled(Port#)", "ROS Trace Disabled" or "ROS Trace Error". If an error occurs, ROS
Trace automatically turns off.
This section describes ROS Trace in more detail.
CONTENTS
•Section3.5.1, “Starting and Stopping ROS Trace”
•Section3.5.2, “ROS Trace Files”
•Section3.5.3, “Configuring ROS Trace”
•Section3.5.4, “Sample Trace File”
Section3.5.1
Starting and Stopping ROS Trace
To start ROS Trace, do the following:
1. To start ROS Trace, click on the ROS Trace menu on the main menu bar, and then click Start ROS Trace. The
Start ROS Trace dialog box appears.
Chapter 3
Using RUGGEDCOM DIRECTOR
RUGGEDCOM DIRECTOR
User Guide
20 ROS Trace Files
Figure15:Start ROS Trace dialog box
2. Enter a port number.
3. Click Start. ROS Trace starts.
4. In the main window, click on a port from the list.
5. Click to open a Telnet session.
6. Enter your ROS user name and press Enter.
7. Enter your ROS password and press Enter.
8. Configure ROS as required to run the ROS Trace. For information on how to configure ROS, see the ROS User
Guide.
Clicking Show in Folder on the ROS Trace menu opens a Windows Explorer folder that contains ROS Trace files
(output files).
To stop ROS Trace, click on the ROS Trace menu on the main menu bar, and then click Stop ROS Trace. Click yes
when prompted.
Section3.5.2
ROS Trace Files
ROS Trace files are stored in the folder named ROSTraceFiles, which is located inside the RUGGEDCOM
DIRECTOR folder. This folder is created during installation. If not, it is created when the ROS Trace server gets data
from ROS devices. A text file is created for each ROS device. The name of the ROS Trace file is the IP address of the
device.
Example:
C:\Program Files\RUGGEDCOM\RUGGEDCOM RUGGEDCOM DIRECTOR\ROSTraceFiles\{IP Address}(1).txt
{IP Address} is the IP address of the ROS device.
By default, ROS Trace keeps two files for each device (the default value of NumberOfROSTraceFiles is set to
2 in the configuration file). If the file name contains a (1), this means it contains the most recent incoming data.
A file name containing (2) is the archived file that has reached the maximum size (rolled over). If the file with (1)
reaches maximum size, it will become (2), and the existing (2), which is the oldest entry, is deleted.
In the ROS Trace file, the date stamp is created by the trace server and the time stamp is created by the ROS
device.
Example:
RUGGEDCOM DIRECTOR
User Guide
Chapter 3
Using RUGGEDCOM DIRECTOR
Configuring ROS Trace 21
[08/1/2012] 08/01 07:57:50.301 TRACE Connected to 1093741c, port 5330
[08/1/2012] 07:58:12.697 RawSocket Port 2, tx msg 1b
31
[08/1/2012] 07:58:12.738 RawSocket Port 2, tx msg 1b
32
[08/1/2012] 07:58:12.779 RawSocket Port 2, tx msg 1b
33
[08/1/2012] 07:58:56.744 RawSocket Port 3, tx msg 1b
34
[08/1/2012] 07:58:56.804 RawSocket Port 3, tx msg 1b
34
[08/1/2012] 07:58:57.001 RawSocket Port 3, tx msg 1b
34
[08/1/2012] 08/01 08:02:50.012 RawSocket Port 4, tx msg 1b
61
[08/1/2012] 08:02:50.462 RawSocket Port 4, tx msg 1b
73
Section3.5.3
Configuring ROS Trace
The ROS configuration file is called RCDIRECTOR.ini. It is located in the RUGGEDCOM DIRECTOR folder in your
workstation.
The number of ROS Trace files can be changed in the configuration file. The parameter to be modified is called
NumberOfROSTraceFiles. The maximum size of each text file can be configured by changing the value of the
ROSTraceFileSize in the configuration file. The unit is in megabytes (MB).
After changing the configuration file, restart ROS Trace and then the changes will take effect.
It is recommended not to change the value of the ROSTraceBufferSize parameter. If the incoming data is
larger than the buffer provided, ROS Trace generates an error.
The default values for the parameters described in this section are as follows:
• NumberOfROSTraceFiles = 2
• ROSTraceFileSize = 10
• ROSTraceBufferSize = 512
Section3.5.4
Sample Trace File
RUGGEDCOM Director(TM)
Serial Trace
---General Information---
Serial port: COM5
Server Name: RS910 #1
Model: RS910
IP: 172.30.85.2
Port: 50001
Transport method: TCP
---Traffic Count---
Serial (bytes)
RX: 2822
TX: 26
Chapter 3
Using RUGGEDCOM DIRECTOR
RUGGEDCOM DIRECTOR
User Guide
22 Sample Trace File
IP (packets)
RX: 15
TX: 18
---Data---
[2/4/2010 9:47:20] >> 1 bytes
0D .
[2/4/2010 9:47:21] << 432 bytes
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 30 6D 1B 5B 32 4A 1B 5B 31 3B 31 48 1B 5B .[0m.[2J.[1;1H.[
3F 32 35 68 0D 0A 20 20 20 20 20 20 20 20 20 20 ?25h..
20 20 20 20 20 20 20 52 75 67 67 65 64 20 4F 70 Rugged Op
65 72 61 74 69 6E 67 20 53 79 73 74 65 6D 20 76 erating System v
33 2E 37 2E 33 20 28 53 65 70 20 31 35 20 32 30 3.7.3 (Sep 15 20
30 39 20 31 37 3A 32 39 29 20 20 20 20 20 20 20 09 17:29)
20 20 20 20 20 20 0D 0A 20 20 20 20 20 20 20 20 ..
43 6F 70 79 72 69 67 68 74 20 28 63 29 20 52 75 Copyright (c) Ru
67 67 65 64 43 6F 6D 2C 20 32 30 30 38 20 2D 20 ggedCom, 2008 -
41 6C 6C 20 72 69 67 68 74 73 20 72 65 73 65 72 All rights reser
76 65 64 0D 0A 0D 0A 20 20 20 20 20 20 20 20 53 ved.... S
79 73 74 65 6D 20 4E 61 6D 65 3A 20 20 20 50 41 ystem Name: PA
53 53 30 31 0D 0A 20 20 20 20 20 20 20 20 4C 6F SS01.. Lo
63 61 74 69 6F 6E 3A 20 20 20 20 20 20 4C 6F 63 cation: Loc
61 74 69 6F 6E 0D 0A 20 20 20 20 20 20 20 20 43 ation.. C
6F 6E 74 61 63 74 3A 20 20 20 20 20 20 20 43 6F ontact: Co
6E 74 61 63 74 0D 0A 20 20 20 20 20 20 20 20 50 ntact.. P
72 6F 64 75 63 74 3A 20 20 20 20 20 20 20 52 53 roduct: RS
39 30 30 4C 2D 48 49 44 2D 54 58 54 58 56 31 0D 900L-HID-TXTXV1.
0A 20 20 20 20 20 20 20 20 4D 41 43 20 41 64 64 . MAC Add
72 65 73 73 3A 20 20 20 30 30 2D 30 41 2D 44 43 ress: 00-0A-DC
2D 30 30 2D 32 31 2D 37 33 0D 0A 20 20 20 20 20 -00-21-73..
20 20 20 53 65 72 69 61 6C 20 4E 75 6D 62 65 72 Serial Number
3A 20 52 53 39 30 30 4C 2D 30 35 30 37 2D 30 30 : RS900L-0507-00
31 39 0D 0A 0D 0A 20 20 20 20 20 20 20 20 45 6E 19.... En
74 65 72 20 55 73 65 72 20 4E 61 6D 65 3A 20 20 ter User Name:
[2/4/2010 9:47:30] >> 1 bytes
61 a
[2/4/2010 9:47:30] << 1 bytes
61 a
[2/4/2010 9:47:31] >> 2 bytes
64 6D dm
[2/4/2010 9:47:31] >> 1 bytes
69 i
[2/4/2010 9:47:31] >> 1 bytes
6E n
[2/4/2010 9:47:33] << 4 bytes
64 6D 69 6E dmin
[2/4/2010 9:47:34] >> 1 bytes
0D .
RUGGEDCOM DIRECTOR
User Guide
Chapter 3
Using RUGGEDCOM DIRECTOR
Sample Trace File 23
[2/4/2010 9:47:35] << 28 bytes
0D 0A 0D 0A 20 20 20 20 20 20 20 20 45 6E 74 65 .... Ente
72 20 50 61 73 73 77 6F 72 64 3A 20 r Password:
[2/4/2010 9:47:35] >> 1 bytes
61 a
[2/4/2010 9:47:35] << 1 bytes
78 x
[2/4/2010 9:47:35] >> 1 bytes
64 d
[2/4/2010 9:47:35] >> 1 bytes
6D m
[2/4/2010 9:47:35] << 1 bytes
78 x
[2/4/2010 9:47:35] << 1 bytes
78 x
[2/4/2010 9:47:36] >> 1 bytes
69 i
[2/4/2010 9:47:36] >> 1 bytes
6E n
[2/4/2010 9:47:36] << 1 bytes
78 x
[2/4/2010 9:47:36] << 1 bytes
78 x
[2/4/2010 9:47:36] >> 1 bytes
0D .
[2/4/2010 9:47:37] << 1132 bytes
1B 5B 30 6D 1B 5B 31 3B 30 48 1B 5B 32 4B 1B 5B .[0m.[1;0H.[2K.[
30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 0;22;27;25;24m.[
31 3B 31 48 1B 5B 3F 32 35 6C 50 41 53 53 30 31 1;1H.[?25lPASS01
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 31 3B 33 35 48 4D 61 69 6E 20 4D 65 6E 75 .[1;35HMain Menu
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 31 3B 36 35 48 20 20 20 61 64 6D 69 6E 20 .[1;65H admin
61 63 63 65 73 73 1B 5B 3F 32 35 6C 1B 5B 30 6D access.[?25l.[0m
1B 5B 32 3B 30 48 1B 5B 32 4B 1B 5B 33 3B 30 48 .[2;0H.[2K.[3;0H
1B 5B 32 4B 1B 5B 34 3B 30 48 1B 5B 32 4B 1B 5B .[2K.[4;0H.[2K.[
35 3B 30 48 1B 5B 32 4B 1B 5B 36 3B 30 48 1B 5B 5;0H.[2K.[6;0H.[
32 4B 1B 5B 37 3B 30 48 1B 5B 32 4B 1B 5B 38 3B 2K.[7;0H.[2K.[8;
30 48 1B 5B 32 4B 1B 5B 39 3B 30 48 1B 5B 32 4B 0H.[2K.[9;0H.[2K
1B 5B 31 30 3B 30 48 1B 5B 32 4B 1B 5B 31 31 3B .[10;0H.[2K.[11;
30 48 1B 5B 32 4B 1B 5B 31 32 3B 30 48 1B 5B 32 0H.[2K.[12;0H.[2
4B 1B 5B 31 33 3B 30 48 1B 5B 32 4B 1B 5B 31 34 K.[13;0H.[2K.[14
3B 30 48 1B 5B 32 4B 1B 5B 31 35 3B 30 48 1B 5B ;0H.[2K.[15;0H.[
Chapter 3
Using RUGGEDCOM DIRECTOR
RUGGEDCOM DIRECTOR
User Guide
24 Sample Trace File
32 4B 1B 5B 31 36 3B 30 48 1B 5B 32 4B 1B 5B 31 2K.[16;0H.[2K.[1
37 3B 30 48 1B 5B 32 4B 1B 5B 31 38 3B 30 48 1B 7;0H.[2K.[18;0H.
5B 32 4B 1B 5B 31 39 3B 30 48 1B 5B 32 4B 1B 5B [2K.[19;0H.[2K.[
32 30 3B 30 48 1B 5B 32 4B 1B 5B 32 31 3B 30 48 20;0H.[2K.[21;0H
1B 5B 32 4B 1B 5B 32 32 3B 30 48 1B 5B 32 4B 1B .[2K.[22;0H.[2K.
5B 32 33 3B 30 48 1B 5B 32 4B 1B 5B 32 34 3B 30 [23;0H.[2K.[24;0
48 1B 5B 32 4B 1B 5B 30 3B 32 32 3B 32 37 3B 32 H.[2K.[0;22;27;2
35 3B 32 34 6D 1B 5B 34 3B 33 30 48 41 64 6D 69 5;24m.[4;30HAdmi
6E 69 73 74 72 61 74 69 6F 6E 1B 5B 30 3B 32 32 nistration.[0;22
3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 35 3B 33 30 ;27;25;24m.[5;30
48 45 74 68 65 72 6E 65 74 20 50 6F 72 74 73 1B HEthernet Ports.
5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 1B [0;22;27;25;24m.
5B 36 3B 33 30 48 45 74 68 65 72 6E 65 74 20 53 [6;30HEthernet S
74 61 74 73 1B 5B 30 3B 32 32 3B 37 3B 32 35 3B tats.[0;22;7;25;
32 34 6D 1B 5B 37 3B 33 30 48 4C 69 6E 6B 20 41 24m.[7;30HLink A
67 67 72 65 67 61 74 69 6F 6E 1B 5B 30 3B 32 32 ggregation.[0;22
3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 38 3B 33 30 ;27;25;24m.[8;30
48 53 70 61 6E 6E 69 6E 67 20 54 72 65 65 1B 5B HSpanning Tree.[
30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 0;22;27;25;24m.[
39 3B 33 30 48 56 69 72 74 75 61 6C 20 4C 41 4E 9;30HVirtual LAN
73 1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 s.[0;22;27;25;24
6D 1B 5B 31 30 3B 33 30 48 50 6F 72 74 20 53 65 m.[10;30HPort Se
63 75 72 69 74 79 1B 5B 30 3B 32 32 3B 32 37 3B curity.[0;22;27;
32 35 3B 32 34 6D 1B 5B 31 31 3B 33 30 48 43 6C 25;24m.[11;30HCl
61 73 73 65 73 20 6F 66 20 53 65 72 76 69 63 65 asses of Service
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 31 32 3B 33 30 48 4D 75 6C 74 69 63 61 73 .[12;30HMulticas
74 20 46 69 6C 74 65 72 69 6E 67 1B 5B 30 3B 32 t Filtering.[0;2
32 3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 31 33 3B 2;27;25;24m.[13;
33 30 48 4D 41 43 20 41 64 64 72 65 73 73 20 54 30HMAC Address T
61 62 6C 65 73 1B 5B 30 3B 32 32 3B 32 37 3B 32 ables.[0;22;27;2
35 3B 32 34 6D 1B 5B 31 34 3B 33 30 48 4E 65 74 5;24m.[14;30HNet
77 6F 72 6B 20 44 69 73 63 6F 76 65 72 79 1B 5B work Discovery.[
30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 0;22;27;25;24m.[
31 35 3B 33 30 48 44 69 61 67 6E 6F 73 74 69 63 15;30HDiagnostic
73 1B 5B 30 3B 31 3B 32 37 3B 32 35 3B 34 6D 1B s.[0;1;27;25;4m.
5B 32 34 3B 31 48 3C 43 54 52 4C 3E 1B 5B 30 3B [24;1H<CTRL>.[0;
32 32 3B 32 37 3B 32 35 3B 32 34 6D 20 20 1B 5B 22;27;25;24m .[
30 3B 31 3B 32 37 3B 32 35 3B 34 6D 5A 2D 48 65 0;1;27;25;4mZ-He
6C 70 1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 lp.[0;22;27;25;2
34 6D 20 1B 5B 30 3B 31 3B 32 37 3B 32 35 3B 34 4m .[0;1;27;25;4
6D 53 2D 53 68 65 6C 6C 1B 5B 30 3B 32 32 3B 32 mS-Shell.[0;22;2
37 3B 32 35 3B 32 34 6D 20 1B 5B 30 3B 31 3B 32 7;25;24m .[0;1;2
37 3B 32 35 3B 34 6D 58 2D 4C 6F 67 6F 75 74 1B 7;25;4mX-Logout.
5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 20 [0;22;27;25;24m
1B 5B 30 6D 1B 5B 30 4B 1B 5B 30 6D 1B 5B 31 3B .[0m.[0K.[0m.[1;
30 48 1B 5B 32 4B 1B 5B 30 3B 32 32 3B 32 37 3B 0H.[2K.[0;22;27;
32 35 3B 32 34 6D 1B 5B 31 3B 31 48 1B 5B 3F 32 25;24m.[1;1H.[?2
35 6C 50 41 53 53 30 31 1B 5B 30 3B 32 32 3B 32 5lPASS01.[0;22;2
37 3B 32 35 3B 32 34 6D 1B 5B 31 3B 33 35 48 4D 7;25;24m.[1;35HM
61 69 6E 20 4D 65 6E 75 1B 5B 30 3B 32 32 3B 32 ain Menu.[0;22;2
37 3B 35 3B 32 34 6D 1B 5B 30 3B 32 32 3B 32 37 7;5;24m.[0;22;27
3B 35 3B 32 34 6D 1B 5B 31 3B 36 35 48 20 20 20 ;5;24m.[1;65H
20 20 20 34 20 41 4C 41 52 4D 53 21 4 ALARMS!
[2/4/2010 9:47:38] >> 3 bytes
1B 5B 41 .[A
[2/4/2010 9:47:38] >> 3 bytes
1B 5B 41 .[A
[2/4/2010 9:47:38] << 75 bytes
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 37 3B 33 30 48 4C 69 6E 6B 20 41 67 67 72 .[7;30HLink Aggr
RUGGEDCOM DIRECTOR
User Guide
Chapter 3
Using RUGGEDCOM DIRECTOR
Sample Trace File 25
65 67 61 74 69 6F 6E 1B 5B 30 3B 32 32 3B 37 3B egation.[0;22;7;
32 35 3B 32 34 6D 1B 5B 36 3B 33 30 48 45 74 68 25;24m.[6;30HEth
65 72 6E 65 74 20 53 74 61 74 73 ernet Stats
[2/4/2010 9:47:38] >> 3 bytes
1B 5B 41 .[A
[2/4/2010 9:47:38] << 73 bytes
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 36 3B 33 30 48 45 74 68 65 72 6E 65 74 20 .[6;30HEthernet
53 74 61 74 73 1B 5B 30 3B 32 32 3B 37 3B 32 35 Stats.[0;22;7;25
3B 32 34 6D 1B 5B 35 3B 33 30 48 45 74 68 65 72 ;24m.[5;30HEther
6E 65 74 20 50 6F 72 74 73 net Ports
[2/4/2010 9:47:38] >> 3 bytes
1B 5B 41 .[A
[2/4/2010 9:47:39] << 73 bytes
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 35 3B 33 30 48 45 74 68 65 72 6E 65 74 20 .[5;30HEthernet
50 6F 72 74 73 1B 5B 30 3B 32 32 3B 37 3B 32 35 Ports.[0;22;7;25
3B 32 34 6D 1B 5B 34 3B 33 30 48 41 64 6D 69 6E ;24m.[4;30HAdmin
69 73 74 72 61 74 69 6F 6E istration
[2/4/2010 9:47:39] << 71 bytes
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 34 3B 33 30 48 41 64 6D 69 6E 69 73 74 72 .[4;30HAdministr
61 74 69 6F 6E 1B 5B 30 3B 32 32 3B 37 3B 32 35 ation.[0;22;7;25
3B 32 34 6D 1B 5B 31 35 3B 33 30 48 44 69 61 67 ;24m.[15;30HDiag
6E 6F 73 74 69 63 73 nostics
[2/4/2010 9:47:39] >> 1 bytes
0D .
[2/4/2010 9:47:39] << 928 bytes
1B 5B 3F 32 35 6C 1B 5B 30 6D 1B 5B 32 3B 30 48 .[?25l.[0m.[2;0H
1B 5B 32 4B 1B 5B 33 3B 30 48 1B 5B 32 4B 1B 5B .[2K.[3;0H.[2K.[
34 3B 30 48 1B 5B 32 4B 1B 5B 35 3B 30 48 1B 5B 4;0H.[2K.[5;0H.[
32 4B 1B 5B 36 3B 30 48 1B 5B 32 4B 1B 5B 37 3B 2K.[6;0H.[2K.[7;
30 48 1B 5B 32 4B 1B 5B 38 3B 30 48 1B 5B 32 4B 0H.[2K.[8;0H.[2K
1B 5B 39 3B 30 48 1B 5B 32 4B 1B 5B 31 30 3B 30 .[9;0H.[2K.[10;0
48 1B 5B 32 4B 1B 5B 31 31 3B 30 48 1B 5B 32 4B H.[2K.[11;0H.[2K
1B 5B 31 32 3B 30 48 1B 5B 32 4B 1B 5B 31 33 3B .[12;0H.[2K.[13;
30 48 1B 5B 32 4B 1B 5B 31 34 3B 30 48 1B 5B 32 0H.[2K.[14;0H.[2
4B 1B 5B 31 35 3B 30 48 1B 5B 32 4B 1B 5B 31 36 K.[15;0H.[2K.[16
3B 30 48 1B 5B 32 4B 1B 5B 31 37 3B 30 48 1B 5B ;0H.[2K.[17;0H.[
32 4B 1B 5B 31 38 3B 30 48 1B 5B 32 4B 1B 5B 31 2K.[18;0H.[2K.[1
39 3B 30 48 1B 5B 32 4B 1B 5B 32 30 3B 30 48 1B 9;0H.[2K.[20;0H.
5B 32 4B 1B 5B 32 31 3B 30 48 1B 5B 32 4B 1B 5B [2K.[21;0H.[2K.[
32 32 3B 30 48 1B 5B 32 4B 1B 5B 32 33 3B 30 48 22;0H.[2K.[23;0H
1B 5B 32 4B 1B 5B 32 34 3B 30 48 1B 5B 32 4B 1B .[2K.[24;0H.[2K.
5B 30 3B 32 32 3B 37 3B 32 35 3B 32 34 6D 1B 5B [0;22;7;25;24m.[
34 3B 32 38 48 43 6F 6E 66 69 67 75 72 65 20 41 4;28HConfigure A
6C 61 72 6D 73 1B 5B 30 3B 32 32 3B 32 37 3B 32 larms.[0;22;27;2
35 3B 32 34 6D 1B 5B 35 3B 32 38 48 56 69 65 77 5;24m.[5;28HView
20 4C 61 74 63 68 65 64 20 41 6C 61 72 6D 73 1B Latched Alarms.
5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 1B [0;22;27;25;24m.
5B 36 3B 32 38 48 43 6C 65 61 72 20 4C 61 74 63 [6;28HClear Latc
68 65 64 20 41 6C 61 72 6D 73 1B 5B 30 3B 32 32 hed Alarms.[0;22
3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 37 3B 32 38 ;27;25;24m.[7;28
Chapter 3
Using RUGGEDCOM DIRECTOR
RUGGEDCOM DIRECTOR
User Guide
26 Sample Trace File
48 56 69 65 77 20 53 79 73 74 65 6D 20 4C 6F 67 HView System Log
1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D .[0;22;27;25;24m
1B 5B 38 3B 32 38 48 43 6C 65 61 72 20 53 79 73 .[8;28HClear Sys
74 65 6D 20 4C 6F 67 1B 5B 30 3B 32 32 3B 32 37 tem Log.[0;22;27
3B 32 35 3B 32 34 6D 1B 5B 39 3B 32 38 48 56 69 ;25;24m.[9;28HVi
65 77 20 43 50 55 20 44 69 61 67 6E 6F 73 74 69 ew CPU Diagnosti
63 73 1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 cs.[0;22;27;25;2
34 6D 1B 5B 31 30 3B 32 38 48 56 69 65 77 20 50 4m.[10;28HView P
72 6F 64 75 63 74 20 49 6E 66 6F 72 6D 61 74 69 roduct Informati
6F 6E 1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 on.[0;22;27;25;2
34 6D 1B 5B 31 31 3B 32 38 48 4C 6F 61 64 20 46 4m.[11;28HLoad F
61 63 74 6F 72 79 20 44 65 66 61 75 6C 74 73 1B actory Defaults.
5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 1B [0;22;27;25;24m.
5B 31 32 3B 32 38 48 52 65 73 65 74 20 44 65 76 [12;28HReset Dev
69 63 65 1B 5B 30 3B 31 3B 32 37 3B 32 35 3B 34 ice.[0;1;27;25;4
6D 1B 5B 32 34 3B 31 48 3C 43 54 52 4C 3E 1B 5B m.[24;1H<CTRL>.[
30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 6D 20 20 0;22;27;25;24m
1B 5B 30 3B 31 3B 32 37 3B 32 35 3B 34 6D 5A 2D .[0;1;27;25;4mZ-
48 65 6C 70 1B 5B 30 3B 32 32 3B 32 37 3B 32 35 Help.[0;22;27;25
3B 32 34 6D 20 1B 5B 30 3B 31 3B 32 37 3B 32 35 ;24m .[0;1;27;25
3B 34 6D 53 2D 53 68 65 6C 6C 1B 5B 30 3B 32 32 ;4mS-Shell.[0;22
3B 32 37 3B 32 35 3B 32 34 6D 20 1B 5B 30 3B 31 ;27;25;24m .[0;1
3B 32 37 3B 32 35 3B 34 6D 58 2D 4C 6F 67 6F 75 ;27;25;4mX-Logou
74 1B 5B 30 3B 32 32 3B 32 37 3B 32 35 3B 32 34 t.[0;22;27;25;24
6D 20 1B 5B 30 6D 1B 5B 30 4B 1B 5B 30 6D 1B 5B m .[0m.[0K.[0m.[
31 3B 30 48 1B 5B 32 4B 1B 5B 30 3B 32 32 3B 32 1;0H.[2K.[0;22;2
37 3B 32 35 3B 32 34 6D 1B 5B 31 3B 31 48 1B 5B 7;25;24m.[1;1H.[
3F 32 35 6C 50 41 53 53 30 31 1B 5B 30 3B 32 32 ?25lPASS01.[0;22
3B 32 37 3B 32 35 3B 32 34 6D 1B 5B 31 3B 33 34 ;27;25;24m.[1;34
48 44 69 61 67 6E 6F 73 74 69 63 73 1B 5B 30 3B HDiagnostics.[0;
32 32 3B 32 37 3B 35 3B 32 34 6D 1B 5B 30 3B 32 22;27;5;24m.[0;2
32 3B 32 37 3B 35 3B 32 34 6D 1B 5B 31 3B 36 35 2;27;5;24m.[1;65
48 20 20 20 20 20 20 34 20 41 4C 41 52 4D 53 21 H 4 ALARMS!
RUGGEDCOM DIRECTOR
User Guide
Chapter 4
Theory of Operation
Principles of Operation 27
Theory of Operation
This section describes the operation of RUGGEDCOM DIRECTOR from a network perspective.
CONTENTS
•Section4.1, “Principles of Operation”
•Section4.2, “Serial Control Signals”
Section4.1
Principles of Operation
RUGGEDCOM DIRECTOR is capable of creating up to 128 virtual serial ports connected to ports on RUGGEDCOM
server devices. Applications on the same system as RUGGEDCOM DIRECTOR can use these virtual ports as though
they were physical serial ports. No special configuration or modification is necessary to existing applications.
For each virtual serial port connection, RUGGEDCOM DIRECTOR monitors data transmitted via the port by
connected applications, and either encapsulates them in either UDP datagrams, or transmits them in a TCP
stream, depending on the connection method specified at configuration time. The encapsulated data is received
by the RUGGEDCOM server at the other end of the TCP/IP or UDP/IP network connection, and transmitted via
its configured physical serial port. The connection is bidirectional. Serial traffic originating at a serial device is
received by the RUGGEDCOM server, transmitted via TCP or UDP to RUGGEDCOM DIRECTOR, and forwarded to the
serial application.
Figure16:Principles Of Operation
Chapter 4
Theory of Operation
RUGGEDCOM DIRECTOR
User Guide
28 Serial Control Signals
Section4.2
Serial Control Signals
RUGGEDCOM DIRECTOR will only support control signals locally (i.e. between RUGGEDCOM DIRECTOR and
connected applications). Only serial data is forwarded across the network. The full set of signals that RUGGEDCOM
DIRECTOR presents to an application connecting to one of its virtual serial ports is listed below:
Parameter Description
Transmitted Data (TxD) Binary data sent from the PC to the serial device.
Received Data (RxD) Binary data received by the PC from the serial device.
Request To Send (RTS) The serial application asserts the RTS signal in order to signal that it wishes to transmit data.
Clear To Send (CTS) When a serial device (in this case, RUGGEDCOM DIRECTOR) receives an RTS signal, it in turn
asserts CTS back to the application, indicating that data can be transmitted. RUGGEDCOM
DIRECTOR does this unconditionally.
Data Terminal Ready (DTR) Asserted by the PC to indicate that it is ready to be connected.
Data Set Ready (DSR) Asserted by a serial device (in this case, RUGGEDCOM DIRECTOR) to indicate that it is
powered on and is ready to receive data from the PC.
RTS, CTS, DTR, DSR signals are only simulated locally between serial applications and RUGGEDCOM DIRECTOR.
These control signals will not be transmitted in either direction over the network. The figure below illustrates the
serial signals.
Figure17:Serial Signals
