User guide

Chapter 1

Introduction

RUGGEDCOM ROS

User Guide

20 Uint16

0x10 0x00 0x80 0x00 0x01 2 0xFF 0x00

• FF 00 for register 00 80 clears the system alarms

• 00 00 does not clear any alarms

The response may look like:

0x10 0x00 0x80 0x00 0x01

Section 1.7.3.3

Uint16

The Uint16 format describes a Standard ModBus 16 bit register.

Section 1.7.3.4

Uint32

The Uint32 format describes Standard 2 ModBus 16 bit registers. The first register holds the most significant 16

bits of a 32 bit value. The second register holds the least significant 16 bits of a 32 bit value.

Section 1.7.3.5

PortCmd

The PortCmd format describes a bit layout per port, where 1 indicates the requested action is true, and 0

indicates the requested action is false.

PortCmd provides a bit layout of a maximum of 32 ports. Therefore, it uses two ModBus regsiters:

• The first ModBus register corresponds to ports 1 – 16

• The second ModBus register corresponds to ports 17 – 32 for a particular action

Bits that do not apply to a particular product are always set to zero (0).

A bit value of 1 indicates that the requested action is true. For example, the port is up.

A bit value of 0 indicates that the requested action is false. For example, the port is down.

Reading Data Using PortCmd

To understand how to read data using PortCmd, consider a ModBus Request to read multiple registers from

locatoin 0x03FE.

0x04 0x03 0xFE 0x00 0x02

The response depends on how many parts are available on the device. For example, if the maximum number of

ports on a connected RUGGEDCOM device is 20, the response would be similar to the following:

0x04 0x04 0xF2 0x76 0x00 0x05

In this example, bytes 3 and 4 refer to register 1 at location 0x03FE, and represent the status of ports 1 – 16.

Bytes 5 and 6 refer to register 2 at location 0x03FF, and represent the status of ports 17 – 32. The device only

has 20 ports, so byte 6 contains the status for ports 17 – 20 starting from right to left. The rest of the bites in