Modbus Pass-Through To Modbus Rtu Devices - Eaton PXG600E User & Installation Manual

Power xpert gateway 600e

Table of Contents

CHAPTER 11 - PXG600E SYSTEM INTEGRATION

170

EATON PXG600E User Manual • IM02603003E Rev 5, 11-May-2012 • Firmware Version 5.03:3835

Addressing the Target Downstream Device

Each "downstream" device is assigned a unique Modbus TCP Unit ID. This

unit ID can be found on the Device Summary. Refer to the

Device Summary Web Page Details on page 155

unit ID is used as the Modbus TCP unit identifier by the Modbus TCP client.

To access data from a "downstream" device, the Modbus TCP client

generates a request to the IP address of the PXG600E with the unit identifier

set to access the targeted "downstream" device. Consult the user

information of your Modbus TCP client to determine how to set the unit

identifier on a message.

Downstream Device Register Map

Each "downstream" device supported by the PXG600E has a fixed register

map. This map contains all of the data that is identified in the EDS file for the

device. The register maps for all supported devices are included on the

PXG600E CD-ROM that is shipped with the PX600. This map shows the

Triggering INCOM Slave Actions from Modbus TCP

The PXG600E supports a selected set of slave actions on some of the INCOM

devices. The supported slave actions are listed in the register map of the

device. See the user's manual for the specific INCOM device for information

on the specific slave action command functionality.

The slave action command is sent to the target INCOM device every time

you perform a write to the corresponding Modbus TCP register. You only

have to perform the write once to trigger the command. Use the write value

of "1. "

NOTICE: Additional slave actions are available for select INCOM

devices. Refer to

www.eaton.com/pxg

Supported Function Codes

The PXG600E supports the following Modbus TCP function codes:

Code