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 manual 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
ROX™, Rugged Operating System On Linux™, CrossBow™ and ELAN™ are trademarks of Siemens Canada Ltd. . ROS® is a registered
trademark 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.
Third Party Copyrights
Siemens recognizes the following third party copyrights:
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.
Preface ................................................................................................................ xi
Conventions ....................................................................................................................................... xi
Alerts ......................................................................................................................................... xi
CLI Command Syntax ................................................................................................................ xii
Related Documents ............................................................................................................................ xii
System Requirements ........................................................................................................................ xii
Accessing Documentation .................................................................................................................. xiii
Training ............................................................................................................................................ xiii
Customer Support ............................................................................................................................. xiii
This guide describes v4.1 of ROS (Rugged Operating System) running on the RUGGEDCOM RSG2200. 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.
IMPORTANT!
Some of the parameters and options described may not be available depending on variations in the
device hardware. While every attempt is made to accurately describe the specific parameters and
options available, this Guide should be used as a companion to the Help text included in the software.
Conventions
This User Guide uses the following conventions to present information clearly and effectively.
Preface
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.
Conventionsxi
Preface
CLI Command Syntax
The syntax of commands used in a Command Line Interface (CLI) is described according to the following
conventions:
ExampleDescription
RUGGEDCOM ROS
User Guide
command
command parameter
command parameter1 parameter2
command parameter1 parameter2
command [parameter1 | parameter2]
command {parameter3 | parameter4}
command parameter1 parameter2 {parameter3 |
parameter4}
Related Documents
Other documents that may be of interest include:
• RUGGEDCOM RSG2200 Installation Guide
• RUGGEDCOM M2200 Installation Guide
• RUGGEDCOM RSG2200 Data Sheet
• RUGGEDCOM M2200 Data Sheet
• RUGGEDCOM Fiber Guide
• RUGGEDCOM Wireless Guide
• White Paper: Rapid Spanning Tree in Industrial Networks
Commands are in bold.
Parameters are in plain text.
Parameters are listed in the order they must be entered.
Parameters in italics must be replaced with a user-defined value.
Alternative parameters are separated by a vertical bar (|).
Square brackets indicate a required choice between two or more
parameters.
Curly brackets indicate an optional parameter(s).
All commands and parameters are presented in the order they must
be entered.
System Requirements
Each workstation used to connect to the ROS interface must meet the following system requirements:
• Must have one of the following Web browsers installed:
▪ Microsoft Internet Explorer 8.0 or higher
▪ Mozilla Firefox
▪ Google Chrome
▪ Iceweasel/IceCat (Linux Only)
• Must have a working Ethernet interface compatible with at least one of the port types on the RUGGEDCOM
device
• The ability to configure an IP address and netmask on the computer’s Ethernet interface
xiiCLI Command Syntax
RUGGEDCOM ROS
User Guide
Accessing Documentation
The latest Hardware Installation Guides and Software User Guides for most RUGGEDCOM products are
available online at www.siemens.com/ruggedcom.
For any questions about the documentation or for assistance finding a specific document, contact a Siemens
sales representative.
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.
Preface
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://
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, manuals, and much more
▪ Submit SRs or check on the status of an existing SR
▪ Find and contact a local contact person
▪ Ask questions or share knowledge with fellow Siemens customers and the support community
▪ And much more...
Accessing Documentationxiii
RUGGEDCOM ROS
User Guide
Preface
Customer Supportxiv
RUGGEDCOM ROS
User Guide
Introduction
This chapter provides a basic overview of the ROS software. It describes the following topics:
• Section 1.1, “Overview”
• Section 1.2, “Security Recommendations and Considerations”
• Section 1.3, “Port Numbering Scheme”
• Section 1.4, “Available Services by Port”
• Section 1.5, “SNMP Management Interface Base (MIB) Support”
• Section 1.6, “SNMP Traps”
• Section 1.7, “ModBus Management Support”
• Section 1.8, “Certificate and Key Requirements”
Chapter 1
Introduction
Section 1.1
Overview
Welcome to the ROS Software User Guide for the RSG2200. This Guide describes the wide array of carrier
grade features made available by ROS (Rugged Operating System). These features include:
IMPORTANT!
The RSG2200/M2200 is not intended for use or resale as online control equipment in hazardous, highrisk environments that require fail-safe performance, such as nuclear facilities, aircraft navigation or
communication systems, air traffic control, direct life support machines or weapons systems, in which
the failure of the software could result in death, personal injury, or severe physical or environmental
damage.
Rugged Operating System (ROS) Features
• Simple plug and play operation - automatic learning,
negotiation and crossover detection
• MSTP 802.1Q-2005 (formerly 802.1s)
• RSTP (802.1w) and Enhanced Rapid Spanning Tree
(eRSTP™) network fault recovery (<5ms)
• Quality of Service (802.1p) for real-time traffic
• VLAN (802.1Q) with double tagging and GVRP
support
• Link aggregation (802.3ad)
• IGMP Snooping for multicast filtering
• Port rate limiting and broadcast storm limiting
• Port configuration, status, statistics, mirroring,
security
• SNTP time synchronization (client and server)
Cyber Security Features
• Muti-level user passwords
• SSH/SSL (128-bit encryption)
• Enable/disable ports, MAC based port security
• Port-based network access control (802.1X)
• VLAN (802.1Q) to segregate and secure network
traffic
• RADIUS centralized password management
• SNMPv3 authentication and 56-bit encryption
Management Features
• Web-based, Telnet, CLI management interfaces
• SNMP v1/v2/v3 (56-bit encryption)
• Remote Monitoring (RMON)
• Rich set of diagnostics with logging and alarms
Overview1
Chapter 1
Introduction
• Industrial automation features (eg. Modbus)
Section 1.2
RUGGEDCOM ROS
User Guide
Security Recommendations and Considerations
The following describes important security-related recommendations and suggestions that should be considered
before implementing the RSG2200 on any network:
• Section 1.2.1, “Security Recommendations”
• Section 1.2.2, “Key Files”
Section 1.2.1
Security Recommendations
To prevent unauthorized access to the device, note the following security recommendations:
• Do not connect the device to the Internet. Deploy the device only within a secure network perimeter.
• Replace the default passwords for all user accounts and processes (where applicable) before the device is
deployed.
• Use strong passwords. Avoid weak passwords such as password1, 123456789, abcdefgh, etc. For more
information about creating strong passwords, refer to the password requirements in Section 4.3, “Configuring
Passwords”.
• Make sure passwords are protected and not shared with unauthorized personnel.
• Passwords should not be re-used across different usernames and systems, or after they expire.
• When RADIUS authentication is done remotely, make sure all communications are within the security perimeter
or on a secure channel.
• SSL and SSH keys are accessible to users who connect to the device via the serial console. Make sure to take
appropriate precautions when shipping the device beyond the boundaries of the trusted environment:
▪ Replace the SSH and SSL keys with throwaway keys prior to shipping.
▪ Take the existing SSH and SSL keys out of service. When the device returns, create and program new keys
for the device.
• Restrict physical access to the device to only trusted personnel. A person with malicious intent could extract
critical information, such as certificates, keys, etc. (user passwords are protected by hash codes), or reprogram
the device.
• Control access to the serial console to the same degree as any physical access to the device. Access to the
serial console allows for potential access to the ROS boot loader, which includes tools that may be used to gain
complete access to the device.
• Only enable services that will be used on the device, including physical ports. Unused physical ports could
potentially be used to gain access to the network behind the device.
• If SNMP is enabled, limit the number of IP addresses that can connect to the device and change the
community names. Also configure SNMP to raise a trap upon authentication failures. For more information,
refer to Section 5.7, “Managing SNMP”.
• Avoid using insecure services such as Telnet and TFTP, or disable them completely if possible. These services
are available for historical reasons and are disabled by default.
2Security Recommendations and Considerations
RUGGEDCOM ROS
User Guide
• Limit the number of simultaneous Web Server, Telnet and SSH sessions allowed.
• Configure remote system logging to forward all logs to a central location. For more information, refer to
Section 3.5, “Managing Logs”.
• Configuration files are provided in the CSV (comma separated values) format for ease of use. Make sure
configuration files are properly protected when they exist outside of the device. For instance, encrypt the files,
store them in a secure place, and do not transfer them via insecure communication channels.
• Management of the configuration file, certificates and keys is the responsibility of the device owner. Before
returning the device to Siemens for repair, make sure encryption is disabled (to create a cleartext version of the
configuration file) and replace the current certificates and keys with temporary throwaway certificates and keys
that can be destroyed upon the device's return.
• Be aware of any non-secure protocols enabled on the device. While some protocols, such as HTTPS and
SSH, are secure, others, such as Telnet and RSH, were not designed for this purpose. Appropriate safeguards
against non-secure protocols should be taken to prevent unauthorized access to the device/network.
• Configure port security features on access ports to prevent a third-party from launching various attacks that can
harm the network or device. For more information, refer to Section 5.10, “Managing Port Security”.
• Periodically audit the device to make sure it complies with these recommendations and/or any internal security
policies.
Chapter 1
Introduction
Section 1.2.2
Key Files
ROS uses security keys to establish secure remote logins (SSH) and Web access (SSL).
It is strongly recommended that a unique SSL certificate and SSH keys be created and provisioned. New ROS based units from Siemens will be shipped with a unique certificate and keys preconfigured in the ssl.crt and
ssh.keys flash files.
The default and auto-generated SSL certificates are self-signed. It is recommended to use an SSL certificate that
is either signed by a trusted third-party Certificate Authority (CA) or by an organization's own CA. This technique
is described in the Siemens application note: Creating/Uploading SSH Keys and SSL Certificates to ROS UsingWindows, available from www.siemens.com/ruggedcom.
The sequence of events related to Key Management during an upgrade to ROS v4.1 or later is as follows:
NOTE
The auto-generation of SSH keys is not available for Non-Controlled (NC) versions of ROS.
• On first boot, ROS will start the SSH and SSL services using the default keys.
• Immediately after boot, ROS will start to generate a unique SSL certificate and SSH key pair, and save each
one to its corresponding flash file. This process may take several minutes to complete. As each one is created,
the corresponding service is immediately restarted with the new keys.
• At any time during the key generation process, custom keys can be uploaded. The custom keys will take
precedence over both the default and auto-generated keys.
• On subsequent boot, if there is a valid ssl.crt file, the default certificate will not be used for SSL. If there is a
valid ssh.keys file, the default SSH key will not be used.
• At any time, new keys may be uploaded or generated by ROS using the sslkeygen or sshkeygen CLI
commands.
The following sections describe SSL certificates and SSH key pairs in more detail:
Key Files3
Chapter 1
Introduction
RUGGEDCOM ROS
• Section 1.2.2.1, “SSL Certificates”
• Section 1.2.2.2, “SSH Key Pairs”
Section 1.2.2.1
SSL Certificates
ROS supports SSL certificates that conform to the following specifications:
• X.509 v3 digital certificate format
• PEM format
• RSA key pair, 512 to 2048 bits
The RSA key pair used in the default certificate and in those generated by ROS uses a public key of 1024 bits in
length.
NOTE
RSA keys smaller than 1024 bits in length are not recommended. Support is only included here for
compatibility with legacy equipment.
User Guide
NOTE
The default certificate and keys are common to all ROS versions without a certificate or key files. That
is why it is important to either allow the key auto-generation to complete or to provision custom keys. In
this way, one has at least unique, and at best, traceable and verifiable keys installed when establishing
secure communication with the unit.
NOTE
RSA key generation times increase depending on the key length. 1024 bit RSA keys may take several
minutes to generate, whereas 2048 bit keys may take significantly longer. A typical modern PC system,
however, can generate these keys in seconds.
The following (bash) shell script fragment uses the openssl command line utility to generate a self-signed
X.509 v3 SSL certificate with a 1024 bit RSA key suitable for use in ROS . Note that two standard PEM files are
required: the SSL certificate and the RSA private key file. These are concatenated into the resulting ssl.crt file,
which may then be uploaded to ROS:
# RSA key size:
BITS=1024
# 20 years validity:
DAYS=7305
# Values that will be stored in the Distinguished Name fields:
COUNTRY_NAME=CA # Two-letter country code
STATE_OR_PROVINCE_NAME=Ontario # State or Province
LOCALITY_NAME=Concord # City
ORGANIZATION=Ruggedcom.com # Your organization's name
ORGANIZATION_CA=${ORGANIZATION}_CA # Your Certificate Authority
COMMON_NAME=RC # The DNS or IP address of the ROS unit
ORGANIZATIONAL_UNIT=ROS # Organizational unit name
# Variables used in the construction of the certificate
REQ_SUBJ="/C=${COUNTRY_NAME}/ST=${STATE_OR_PROVINCE_NAME}/L=${LOCALITY_NAME}/O=${ORGANIZATION}/OU=
${ORGANIZATIONAL_UNIT}/CN=${COMMON_NAME}/"
REQ_SUBJ_CA="/C=${COUNTRY_NAME}/ST=${STATE_OR_PROVINCE_NAME}/L=${LOCALITY_NAME}/O=${ORGANIZATION_CA}/
OU=${ORGANIZATIONAL_UNIT}/"
4SSL Certificates
RUGGEDCOM ROS
User Guide
########################################################################
# Make the self-signed SSL certificate and RSA key pair:
openssl req -x509 -newkey rsa:${BITS} -nodes \
-days ${DAYS} -subj ${REQ_SUBJ} \
-keyout ros_ssl.key \
-out ros_ssl.crt
# Concatenate Cert and Key into a single file suitable for upload to ROS:
# Note that cert must precede the RSA key:
cat ros_ssl.crt ros_ssl.key > ssl.crt
For information on creating SSL certificates for use with ROS in a Microsoft Windows environment, refer to the
following Siemens application note: Creating/Uploading SSH Keys and SSL Certificates to ROS Using Windows.
The following is an example of a self-signed SSL certificate generated by ROS:
Controlled versions of ROS support SSH public/private key pairs that conform to the following specifications:
• PEM format
• DSA key pair, 512 to 2048 bits in length
The DSA key pair used in the default key pair and in those generated by ROS uses a public key of 1024 bits in
length.
NOTE
DSA keys smaller than 1024 bits in length are not recommended, and support is only included here for
compatibility with legacy equipment.
NOTE
DSA key generation times increase depending on the key length. 1024 bit RSA keys may take several
minutes to generate, whereas 2048 bit keys may take significantly longer. A typical modern PC system,
however, can generate these keys in seconds.
The following (bash) shell script fragment uses the ssh-keygen command line utility to generate a 1024 bit DSA
key suitable for use in ROS . The resulting ssh.keys file, which may then be uploaded to ROS:
User Guide
# DSA key size:
BITS=1024
# Make an SSH key pair:
ssh-keygen -t dsa -b 1024 -N '' -f ssh.keys
The following is an example of an SSH key generated by ROS:
The device generates the following standard traps:
Table: Standard Traps
TrapMIB
linkDown
linkUp
IF-MIB
authenticationFailure
coldStart
newRoot
topologyChage
risingAlarmRMON-MIB
SNMPv2-MIB
BRIDGE-MIB
SNMP Traps11
Chapter 1
Introduction
TrapMIB
fallingAlarm
lldpRemoteTablesChangeLLDP-MIB
The device also generates the following proprietary traps:
Table: Proprietary Traps
TrapMIB
RUGGEDCOM ROS
User Guide
genericTrap
powerSupplyTrap
swUpgradeTrap
cfgChangeTrap
weakPasswordTrap
defaultKeysTrap
RUGGEDCOM-TRAPS-MIB
Generic traps carry information about events in their severity and description objects. They are sent at the same
time an alarm is generated for the device. The following are examples of RUGGEDCOM generic traps:
NOTE
Information about generic traps can be retrieved using the CLI command alarms. For more
information about the alarms command, refer to Section 2.6.1, “Available CLI Commands”.
Table: Generic Traps
TrapSeverity
heap errorAlert
NTP server failurenotification
real time clock failureError
failed passwordWarning
MAC address not learned by switch fabricWarning
BootP client: TFTP transfer failureError
received looped back BPDUError
received two consecutive confusing BPDUs on port, forcing downError
GVRP failed to learn – too many VLANsWarning
The device generates the following traps when specific events occur:
Table: Event-Based Traps
TrapMIBEvent
rcRstpNewTopologyRUGGEDCOM-STP-MIBThis trap is generated when the device
12SNMP Traps
topology becomes stable after a topology
change occurs on a switch port.
RUGGEDCOM ROS
User Guide
Section 1.7
ModBus Management Support
Modbus management support in RUGGEDCOM devices provides a simple interface for retrieving basic status
information. ModBus support simplifies the job of SCADA (Supervisory Control and Data Acquisition) system
integrators by providing familiar protocols for retrieving RUGGEDCOM device information. ModBus provides
mostly read-only status information, but there are some writable registers for operator commands.
The ModBus protocol PDU (Protocol Data Unit) format is as follows:
Function CodeData
The following sections describe the support for ModBus management:
• Section 1.7.1, “ModBus Function Codes”
• Section 1.7.2, “ModBus Memory Map”
• Section 1.7.3, “ModBus Memory Formats”
Section 1.7.1
Chapter 1
Introduction
ModBus Function Codes
RUGGEDCOM devices support the following ModBus function codes for device management through ModBus:
NOTE
While RUGGEDCOM devices have a variable number of ports, not all registers and bits apply to all
products.
Registers that are not applicable to a particular device return a zero (0) value. For example, registers
referring to serial ports are not applicable to RUGGEDCOM switch devices.
Read Input Registers or Read Holding Registers — 0x04 or 0x03
Example PDU Request
Function Code1 Byte0x04(0x03)
Starting Address2 Bytes0x0000 to 0xFFFF (Hexadecimal)
128 to 65535 (Decimal)
Number of Input Registers2 BytesBytes 0x0001 to 0x007D
Example PDU Response
Function Code1 Byte0x04(0x03)
Byte Count1 Byte2 x N
Number of Input RegistersNa x 2 Bytes
a
The number of input registers
a
Write Multiple Registers — 0x10
Example PDU Request
Function Code1 Byte0x10
Starting Address2 Bytes0x0000 to 0xFFFF
ModBus Management Support13
Chapter 1
Introduction
Number of Input Registers2 BytesBytes 0x0001 to 0x0079
Byte Count1 Byte2 x N
Registers ValueNb x 2 BytesValue of the register
b
The number of input registers
b
Example PDU Response
Function Code1 Byte0x10
Starting Address2 Bytes0x0000 to 0xFFFF
Number of Registers2 Bytes1 to 121 (0x79)
Section 1.7.2
ModBus Memory Map
The following details how ModBus process variable data is mapped.
Product Info
The following data is mapped to the Productinfo table:
RUGGEDCOM ROS
User Guide
Address#RegistersDescription (Reference Table in UI)R/WFormat
000016Product IdentificationRText
001032Firmware IdentificationRText
00401Number of Ethernet PortsRUint16
00411Number of Serial PortsRUint16
00421Number of AlarmsRUint16
00431Power Supply StatusRPSStatusCmd
00441FailSafe Relay StatusRTruthValue
00451ErrorAlarm StatusRTruthValue
Product Write Register
The following data is mapped to various tables:
Address#RegistersDescription (Reference Table in UI)R/WFormat
00801Clear AlarmsWCmd
00812Reset Ethernet PortsWPortCmd
00832Clear Ethernet StatisticsWPortCmd
00852Reset Serial PortsWPortCmd
00872Clear Serial Port StatisticsWPortCmd
Alarms
The following data is mapped to the alarms table:
14ModBus Memory Map
RUGGEDCOM ROS
User Guide
Address#RegistersDescription (Reference Table in UI)R/WFormat
010064Alarm 1RAlarm
014064Alarm 2RAlarm
018064Alarm 3RAlarm
01C064Alarm 4RAlarm
020064Alarm 5RAlarm
024064Alarm 6RAlarm
028064Alarm 7RAlarm
02C064Alarm 8RAlarm
Ethernet Port Status
The following data is mapped to the ethPortStats table:
Address#RegistersDescription (Reference Table in UI)R/WFormat
03FE2Port Link StatusRPortCmd
Chapter 1
Introduction
Ethernet Statistics
The following data is mapped to the rmonStats table:
Address#RegistersDescription (Reference Table in UI)R/WFormat
04002Port s1/p1 Statistics - Ethernet In PacketsRUinst32
04022Port s1/p2 Statistics - Ethernet In PacketsRUinst32
04042Port s1/p3 Statistics - Ethernet In PacketsRUinst32
04062Port s1/p4 Statistics - Ethernet In PacketsRUinst32
04082Port s2/p1 Statistics - Ethernet In PacketsRUinst32
040A2Port s2/p2 Statistics - Ethernet In PacketsRUinst32
040C2Port s2/p3 Statistics - Ethernet In PacketsRUinst32
040E2Port s2/p4 Statistics - Ethernet In PacketsRUinst32
04102Port s3/p1 Statistics - Ethernet In PacketsRUinst32
04122Port s3/p2 Statistics - Ethernet In PacketsRUinst32
04142Port s3/p3 Statistics - Ethernet In PacketsRUinst32
04162Port s3/p4 Statistics - Ethernet In PacketsRUinst32
04182Port s4/p1 Statistics - Ethernet In PacketsRUinst32
041A2Port s4/p2 Statistics - Ethernet In PacketsRUinst32
041C2Port s4/p3 Statistics - Ethernet In PacketsRUinst32
041E2Port s4/p4 Statistics - Ethernet In PacketsRUinst32
04202Port s5/p1 Statistics - Ethernet In PacketsRUinst32
04222Port s5/p2 Statistics - Ethernet In PacketsRUinst32
04242Port s5/p3 Statistics - Ethernet In PacketsRUinst32
ModBus Memory Map15
Chapter 1
Introduction
RUGGEDCOM ROS
User Guide
Address#RegistersDescription (Reference Table in UI)R/WFormat
04262Port s5/p4 Statistics - Ethernet In PacketsRUinst32
04282Port s6/p1 Statistics - Ethernet In PacketsRUinst32
042A2Port s6/p2 Statistics - Ethernet In PacketsRUinst32
042C2Port s6/p3 Statistics - Ethernet In PacketsRUinst32
042E2Port s6/p4 Statistics - Ethernet In PacketsRUinst32
04302Port s7/p1 Statistics - Ethernet In PacketsRUinst32
04322Port s7/p2 Statistics - Ethernet In PacketsRUinst32
04342Port s8/p1 Statistics - Ethernet In PacketsRUinst32
04362Port s8/p2 Statistics - Ethernet In PacketsRUinst32
04402Port s1/p1 Statistics - Ethernet Out PacketsRUinst32
04422Port s1/p2 Statistics - Ethernet Out PacketsRUinst32
04442Port s1/p3 Statistics - Ethernet Out PacketsRUinst32
04462Port s1/p4 Statistics - Ethernet Out PacketsRUinst32
04482Port s2/p1 Statistics - Ethernet Out PacketsRUinst32
044A2Port s2/p2 Statistics - Ethernet Out PacketsRUinst32
044C2Port s2/p3 Statistics - Ethernet Out PacketsRUinst32
044E2Port s2/p4 Statistics - Ethernet Out PacketsRUinst32
04502Port s3/p1 Statistics - Ethernet Out PacketsRUinst32
04522Port s3/p2 Statistics - Ethernet Out PacketsRUinst32
04542Port s3/p3 Statistics - Ethernet Out PacketsRUinst32
04562Port s3/p4 Statistics - Ethernet Out PacketsRUinst32
04582Port s4/p1 Statistics - Ethernet Out PacketsRUinst32
045A2Port s4/p2 Statistics - Ethernet Out PacketsRUinst32
045C2Port s4/p3 Statistics - Ethernet Out PacketsRUinst32
045E2Port s4/p4 Statistics - Ethernet Out PacketsRUinst32
04602Port s5/p1 Statistics - Ethernet Out PacketsRUinst32
04622Port s5/p2 Statistics - Ethernet Out PacketsRUinst32
04642Port s5/p3 Statistics - Ethernet Out PacketsRUinst32
04662Port s5/p4 Statistics - Ethernet Out PacketsRUinst32
04682Port s6/p1 Statistics - Ethernet Out PacketsRUinst32
046A2Port s6/p2 Statistics - Ethernet Out PacketsRUinst32
046C2Port s6/p3 Statistics - Ethernet Out PacketsRUinst32
046E2Port s6/p4 Statistics - Ethernet Out PacketsRUinst32
04702Port s7/p1 Statistics - Ethernet Out PacketsRUinst32
16ModBus Memory Map
Loading...
+ 216 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.