Rockwell Automation 1408-EMxx User Manual

User Manual
(Catalog Numbers
1408-TR1A-485, 1408-TR2A-485, 1408­EM1A-485, 1408-EM2A-485, 1408­EM3A-485, 1408-TR1A-ENT, 1408­TR2A-ENT, 1408-EM1A-ENT, 1408­EM2A-ENT, 1408-EM3A-ENT
)

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
) describes some important differences
WARNING
Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
IMPORTANT
ATTENTION
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence
SHOCK HAZARD
Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.
BURN HAZARD
Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.
Allen-Bradley, Rockwell Automation, Powermonitor, ControlLogix, PLC5, SLC, RSLinx and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.

Summary of Changes

Introduction

This release of this document contains new and updated information. The information below summarizes the changes to this manual since the last publication.
Revision bars in the margin identify updated information. Changes for this version of the document include:
Change Page
Added DH485 to the serial communication protocol table.
Added section with information about DH485.
Added that the Ethernet communication port supports 10 or 100 Mbps data rate, half-duplex, or full-duplex.
Added DH485 to the communication command summary.
Added information about explicit messaging instructions apply to Ethernet communication and serial communication.
Added instructions to configure RSLinx software driver configuration for DH485.
Added information for using the DH485 driver.
10
11
11
15
17
34
37
Added information for OPC tag browsing. 39 Added information about a user configured
data table. Added User Configured Table Results
Parameters table. Added User Configured Table Results table. 45 Added element 5 to Analog Input
Configuration table Updated elements 5 and 7 to Advanced
Configuration table. Updated Serial RS-485 Port Configuration
table. Updated Command table. 61 Added element 10 to the Log Request table. 64 Updated Wiring Diagnostics Results table. 68 Updated Unit Run Status Results table. 80
3Publication 1408-UM001B-EN-P - May 2008 3
40
45
46
48
51
Summary of Changes
Change Page
Added User Configurable Table Setup
92
Parameters table. Added User Configured Table Setup table. 92 Added Parameters for Configurable table. 93
4 Publication 1408-UM001B-EN-P - May 2008
Powermonitor 1000 Overview
Powermonitor 1000 Memory Organization
Communications Command Summary

Table of Contents

Preface
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . 7
Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Communication Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2
Data Table Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Table Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Table Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 3
Serial DF1 Full-duplex, DF1 Half-duplex Slave, DH485 . . . . 15
Optional EtherNet/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Modbus RTU Serial and Optional Modbus/TCP Ethernet . . . 16
Explicit Messaging
SCADA Applications
Powermonitor 1000 Data Tables
Chapter 4
Explicit Message Setup – Examples . . . . . . . . . . . . . . . . . . . 17
Reading Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 5
RSLinx Drivers Configuration . . . . . . . . . . . . . . . . . . . . . . . . 33
RSLinx Software OPC Server Setup. . . . . . . . . . . . . . . . . . . . 35
Appendix A
Summary of Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Index
5Publication 1408-UM001B-EN-P - May 2008 5
Table of Contents
6 Publication 1408-UM001B-EN-P - May 2008

Preface

Before You Begin

Who Should Use This Manual

Additional Resources

Use this document as a guide to set up communications with the 1408 Powermonitor 1000 unit using other applications and controllers. This document is intended for advanced users. You should already be familiar with data communications and programmable controller messaging.
For further information on installing, wiring, connecting, applying power, and configuring your 1408 power monitor, please refer to the Powermonitor 1000 Installation Instructions.
You should have a basic understanding of electrical circuitry and familiarity with relay logic. If you do not, obtain the proper training before using this product.
This table lists documents that contain additional information concerning Rockwell Automation Power and Energy Management Solutions products.
For additional information, refer to these publications, that you can download from http://literature.rockwellautomation.com
.
Resource Description
Powermonitor 1000 Unit Installation Instructions, publication 1408-IN001
If you would like a manual, you can:
download a free electronic version from the Internet at
http://literature.rockwellautomation.com
purchase a printed manual by contacting your local
Allen-Bradley distributor or Rockwell Automation sales office.
This publication gives product description and functionality.
7Publication 1408-UM001B-EN-P - May 2008 7
Preface Preface
8 Publication 1408-UM001B-EN-P - May 2008
Powermonitor 1000 Overview
Chapter
1

Safety

Follow these advisories when using this product.
ATTENTION
ATTENTION
Only qualified personnel, following accepted safety procedures, should install, wire, and service the power monitor and its associated components. Before beginning any work, disconnect all sources of power and verify that they are de-energized and locked out. Failure to follow these instructions may result in personal injury or death, property damage or economic loss.
Never open a current transformer (CT) secondary circuit with primary current applied. Wiring between the CT’s and the power monitor should include a shorting terminal block in the CT secondary circuit. Shorting the secondary with primary current present allows other connections to be removed if needed. An open CT secondary with primary current applied produces a hazardous voltage, which can lead to personal injury, death, property damage or economic loss.
IMPORTANT

Introduction

9Publication 1408-UM001B-EN-P - May 2008 9
This manual covers advanced techniques for configuring setup parameters and retrieving data from the power monitor using its available communications. Typical applications include SCADA applications using RSLinx Classic or OPC software to gather data from the power monitor and applications using explicit messaging from PLC controllers to retrieve data for control and information.
Please refer to the Powermonitor 1000 Installation Instructions, publication 1408-IN001
Product description and functionality
Basic meter and communications setup using the LCD display,
HyperTerminal or the web interface
The power monitor is neither designed for, nor intended for, use as a circuit protective device. Do not use this equipment in place of a motor overload relay or circuit protective relay.
for the following information:
Chapter 1 Powermonitor 1000 Overview
What Can I Do Using Communication Networks?
When you use communication networks with the power monitor you can do the following things.
Configure analog input parameters such as PT/CT ratios
Configure communications parameters such as IP address
Read real-time power and energy data
Read energy logs

Communication Overview

All Powermonitor 1000 units come standard with an RS-485 serial communication port. Models with catalog numbers ending in -ENT are equipped with an Ethernet 10BaseT communication port. This section covers serial and Ethernet communication, the available protocols, and what protocols to use for your application.
Serial Communication
The RS-485 serial communication port allows serial communication to your power monitor. This port can be configured to communicate using the protocols listed the Serial Communication Protocols table.
Serial Communication Protocols
Protocol Applications
DF1 Half-duplex Slave The DF1 Half-duplex Slave protocol may be used for point-to-point or multi-drop
communication using a DF1 Polling Master driver for RSLinx software, or when using explicit messages from Rockwell Automation controllers communicating via DF1 Half-duplex Master.
DF1 Full-duplex The DF1 Full-duplex protocol may be used only for point-to-point communication using a
RS-232 DF1 driver for RSLinx software, or when using explicit messages from Rockwell Automation controllers communicating via DF1 Full-duplex.
Modbus RTU Slave The Modbus RTU Slave protocol may be used for point-to-point or multi-drop
communication with a client using the Modbus RTU Master protocol for PLC controller communication.
Auto-sense With auto-sense selected, the RS-485 port switches among the available serial
protocols based on the format of the packets the port receives.
DH485 The DH485 protocol may be used for point-to-point or multi-drop communication using a
1747-PIC/AIC+ driver for RSLinx software, or when using explicit messages from Allen-Bradley controllers or HMI (PanelView) terminals communicating via DH485.
TIP
When configuring serial communication, users should verify that all serial devices wishing to communicate to the power monitor have the same communication rate, and the same data format.
10 Publication 1408-UM001B-EN-P - May 2008
Powermonitor 1000 Overview Chapter 1
DH485 Protocol
DH485 is a token-passing protocol that allows messaging by up to 32 nodes on a serial network. The master is the node that owns the token; only the master may transmit messages. When a node has completed transmitting messages, it passes the token to the next node.
The power monitor does not initiate DH485 data messages. When requested, it transmits reply messages to the initiator when it gets the token, and then passes the token to its successor.
TIP
The DH485 protocol uses the same data table addressing as DF1 protocols. Please refer to the CSP file number column of Powermonitor 1000 data tables.
The following configuration factors have a significant effect on network performance and should be considered when you plan a DH485 network.
Number of Nodes - unnecessary nodes will slow the data
transfer rate. The maximum number of nodes on the network is
32. Fewer nodes are better.
Node Addresses - best to start node addresses at 0 and assign in
sequential order. Controllers may not be node 0. Initiators such as personal computers should be assigned the lowest numbered addresses.
Communication Rate - Higher is better. All devices must be at
the same communication rate.
Maximum Node Address - should be set as low as possible to
reduce the time it takes to initialize the network.
Powermonitor 1000 units only support DH485 Local Link messages and do not support the Send and Receive Data (SRD) messages for DH485 non-token passing slave devices.
Ethernet Network Communication
The Ethernet network communication port allows communication with your power monitor using a local-area-network (LAN). The Ethernet port may also be used to view the power monitor’s internal webpage. This Ethernet port uses a static IP address only, and can simultaneously communicate using the protocols listed below. The Ethernet communication port supports 10 or 100 Mbps data rate, half-duplex, or full-duplex.
Publication 1408-UM001B-EN-P - May 2008 11
Chapter 1 Powermonitor 1000 Overview
EtherNet/IP Protocol
The power monitor supports the EtherNet/IP protocol for communicating via Ethernet or EtherNet/IP drivers in RSLinx Classic software, or when using explicit messages from Rockwell Automation controllers communicating via Ethernet or EtherNet/IP network.
Modbus TCP Protocol
Modbus TCP protocol is also supported for communicating via Modbus TCP for communication.
TIP
When configuring Ethernet communication, you should verify that IP addresses do not conflict with the existing infrastructure, and that subnet masks and gateways are properly set.
12 Publication 1408-UM001B-EN-P - May 2008
Chapter
2
Powermonitor 1000 Memory Organization
The power monitor memory is organized similarly to that of a PLC-5 or SLC 500 programmable controller. Data tables organize individual data items of similar function. For example, the analog input setup parameters are grouped in one data table, and voltage, current, and frequency metering results in another.

Data Table Addressing

Appendix
Data tables may be addressed in several ways.
A provides a detailed list of the power monitor data tables.
CSP addressing. This is also known as PLC-5 style or PCCC
addressing. Addresses are written in the form Axx:yy where A is a letter describing the function of the data table, xx is the table number, and yy is the element within, or offset into, the table. For example, F23:0 is the CSP address of the first element in the energy metering results table.
CIP addressing. This is also known as DeviceNet addressing.
Addresses are of the form Object:Instance:Attribute. CIP addressing allows addressing only a single element of an entire data table. In CIP addressing, the energy metering results table object 4 (Assembly object), instance 16 (energy results table) and attribute 3 (data).
Modbus RTU addressing. The data tables may be addressed by a
Modbus RTU master using Modbus register addressing. The Modbus protocol supports four types of data: Discrete Input, Coil, Input Register, and Holding Register. The power monitor supports Input Registers (read-only) with addresses in the 30000 range and Holding Registers (read-write or write only) with addresses in the 40000 range. Using the same example as above, the energy results table has a Modbus address range of 30401…30438

Data Table Access

13Publication 1408-UM001B-EN-P - May 2008 13
Controllers and client applications may read or write single element, multiple elements or complete tables as permitted by the addressing selected.
Each data table’s read/write access is listed in Appendix
A.
Chapter 2 Powermonitor 1000 Memory Organization
The power monitor requires a valid password before it accepts a write. There are two ways a password may be written.
An entire table including a valid password may be written.
A valid password may be written to the Single element password
write table which then enables single element writes until 30 minutes without a single element write elapses.

Data Table Data Format

The power monitor stores data in two basic formats.
Integer, in which the 16-bit word may be represented by a
signed integer value or a bit field
Floating-point, in the 32-bit IEEE 754 format
Modbus input registers and holding registers are 16 bits long. Floating point values in the data tables are represented as big-Endian two-register arrays in IEEE-754 floating point format. The Modbus client application must be able to reassemble the two-word array into a valid floating-point value.
An example Modbus address for a floating-point value is 40101-2. Register 40101 holds the most significant bytes of the number and 40102 holds the lowest significant bytes.
14 Publication 1408-UM001B-EN-P - May 2008
Chapter
Communications Command Summary
3

Serial DF1 Full-duplex, DF1 Half-duplex Slave, DH485

Optional EtherNet/IP

PCCC Protected Logical Read w/ 2 Address Fields (CMD = 0x0F,
FUNC = 0xA1)
PCCC Protected Logical Write w/ 2 Address Fields (CMD = 0x0F,
FUNC = 0xA9)
PCCC Protected Logical Read w/ 3 Address Fields (CMD = 0x0F,
FUNC = 0xA2)
PCCC Protected Logical Write w/ 3 Address Fields (CMD = 0x0F,
FUNC = 0xAA)
PCCC Protected Logical Write w/ 4 Address Fields (CMD = 0x0F,
FUNC = 0xAB)
PCCC Status Diagnostics (CMD = 0x06, FUNC = 0x03)
CIP Generic Assembly Object (Class 04), Get & Set Attribute
Single for Attribute 3 (data)
CIP Generic Assembly Object (Class 04), Get Attribute Single for
Attribute 4 (size)
PCCC PLC5 Word Range Write Function (CMD = 0x0F, FUNC =
0x00)
PCCC PLC5 Word Range Read Function (CMD = 0x0F, FUNC =
0x01)
PCCC PLC5 Typed Write Function (CMD = 0x0F, FUNC = 0x67)
PCCC PLC5 Typed Read Function (CMD = 0x0F, FUNC = 0x68)
PCCC Protected Logical Read Function w/2 Address Fields (CMD
= 0x0F, FUNC = 0xA1)
PCCC Protected Logical Write Function w/2 Address Fields
(CMD = 0x0F, FUNC = 0xA9)
PCCC Protected Logical Read Function w/3 Address Fields (CMD
= 0x0F, FUNC = 0xA2)
PCCC Protected Logical Write Function w/3 Address Fields
(CMD = 0x0F, FUNC = 0xAA)
PCCC Status Diagnostics (CMD = 0x06, FUNC = 0x03)
15Publication 1408-UM001B-EN-P - May 2008 15
Chapter 3 Communications Command Summary

Modbus RTU Serial and Optional Modbus/TCP Ethernet

The power monitor does not initiate Modbus commands but responds to commands sent by the Modbus master. These Modbus function codes are supported.
03 Read Holding Registers
04 Read Input Registers
16 Write Multiple Holding Registers
08 Diagnostics
00 Echo Command Data02 Return Diagnostic Counters10 Clear Diagnostic Counters
06 Write Single Holding Register
16 Publication 1408-UM001B-EN-P - May 2008
Chapter
4
Explicit Messaging
This section discusses data retrieval and parameter configuration using explicit messaging from Rockwell Automation controllers. Explicit messaging allows you to read and write from a controller to specific data tables within the power monitor. With explicit messages, users can read real-time power and energy values, configure analog input parameters, configure communications parameters, and also read energy logs.
In general, these instructions apply to Ethernet network communication (Ethernet/IP protocol) and Serial communication (DF1 half-duplex or full-duplex or DH485 protocols), provided that the protocol is supported by the controller. If using serial communication, the controller serial port must be correctly configured for protocol, communication rate, or parity. Refer to the appropriate controller user documentation for further details.
Explicit Message Setup – Examples
Please refer to Appendix descriptions of the power monitor data tables and their data access privileges, and data types.
The power monitor allows PLC-5 Typed, SLC Typed, and CIP Generic message requests.
This section gives examples on how to set-up explicit messaging.
A, Powermonitor 1000 Data Tables for
Read/Write Single or Multiple Elements
You can perform single or multiple element reads and writes to the power monitor. Below is a table documenting the message type to use for specific read/write type and communication scenarios.
17Publication 1408-UM001B-EN-P - May 2008 17
Chapter 4 Explicit Messaging
IMPORTANT
When performing a write to the power monitor, you must write the password value to the password element of that specific data table that you are writing to. This must be done in the same message; therefore you must perform a multiple element write. If you wish to perform only a single element write, you must write the password value to the Single Element Password Write table. This allows you to perform writes to any write access data table for the next 30 minutes.
Message Type
Read/Write Type Communication Read/Write Message Type
Single Element Serial SLC Typed Single Element Ethernet PLC5 Typed or SLC Typed Multiple Element Serial SLC Typed Multiple Element Ethernet
(1)
The CIP Generic message type is only available for RSLogix5000 software. All elements in the data table are written to or read back.
PLC5 Typed or SLC Typed or CIP Generic
(1)
RSLogix5000 – Message Configuration using PLC5 or SLC Typed Read/Write
This is an example of how to set up a message instruction to read or write single or multiple elements from a power monitor using PLC5 or SLC Typed messages. This setup applies to ControlLogix and CompactLogix programmable logic controllers.
18 Publication 1408-UM001B-EN-P - May 2008
Explicit Messaging Chapter 4
Follow these steps to configure a message.
1. Choose the appropriate parameters in the Message
Configuration window.
Parameter Choice
Message type Select the appropriate message type according to Message Type
page 18
.
Source Element Read: Refer to Appendix
address of the specific data table address you’re reading. If you are performing a multiple element read, this should be the first element in the array of elements you’re reading back.
Write: This is the controller tag in which to store the data being written to the power monitor.
Number of Elements
Destination Element
This is the number of elements being read or written to. If you are performing a single element read or write, then this value should be 1. If you are performing a multiple element read or write, then this should be the number of elements after the source element that you wish to read or write.
Read: This is the controller tag in which to store the data being read. Write: Refer to Appendix
address of the specific data table address you’re writing to.
A – Powermonitor 1000 Data Tables for the
A – Powermonitor 1000 Data Tables for the
on
2. Click the Communication tab to select the communication type,
either Ethernet or Serial.
Publication 1408-UM001B-EN-P - May 2008 19
Chapter 4 Explicit Messaging
3. Choose the communication type and then set the path and
communication method.
Communication Type Path Method
Ethernet <Backplane (always 1), Slot of Ethernet
Module, Port (always 2 for Ethernet), power monitor IP Address>
Serial Communications <Port, Power Monitor Serial Node Address> CIP
CIP
4. Click OK to complete the message setup.
RSLogix5000 Software – Message Setup Using CIP Generic
The following example shows how to set up your message instruction to read or write to a data table in the power monitor using a CIP Generic message type for RSLogix5000 software. This setup applies to ControlLogix and CompactLogix programmable logic controllers. The CIP Generic message type does not support single element reads or writes. In this example, we are reading the Voltage, Amps, and Frequency data table from the power monitor.
20 Publication 1408-UM001B-EN-P - May 2008
Explicit Messaging Chapter 4
Follow these steps to configure a message.
1. Choose the appropriate parameters in the Message
Configuration window.
Parameter Choice
Message Type Choose message type CIP Generic. Service Type Read: Select service type Get Attribute Single
Write: Select service type Set Attribute Single
Instance Refer to Appendix
requesting to read. In this example, the power monitor’s Voltage, Amp,
and Frequency data table is instance 14. Class 4 Attribute 3 Destination Get Attribute Single - This is the controller tag in which to store the
data being read. Source Element Set Attribute Single - Refer to Appendix
specific data table address you’re writing to. Source Length Set Attribute Single - This is the number of elements of the source
element, to be written to the power monitor.
A for the CIP Instance of the data table you are
A for the address of the
Publication 1408-UM001B-EN-P - May 2008 21
Chapter 4 Explicit Messaging
2. Click the Communication tab and enter the path and method.
Path Method
<Backplane (always 1), Slot of Ethernet Module, Port (always 2 for Ethernet), Power Monitor IP Address>
CIP
3. Click OK to complete message setup.
22 Publication 1408-UM001B-EN-P - May 2008
Explicit Messaging Chapter 4
RSLogix500 Software - Message Setup Using PLC5 or SLC Typed Read/Write
The following is an example of how to set up your message instruction to read or write single or multiple elements to a power monitor using Peer-To-Peer PLC5 or CPU 500 Typed messages in RSLogix500 software. This setup applies to SLC and MicroLogix programmable logic controllers.
Follow these steps to configure a message.
1. Set your MSG instruction.
Parameter Choice
Read/Write Select Read or Write Target Device Select the appropriate message type according to Message Type
page 18
. Local/Remote Select Local Control Block Select an available Integer word. In this example, we used N7:0.
2. Click Setup Screen at the bottom of the message instruction.
The message configuration window for either Ethernet network or Serial communication appears.
on
Publication 1408-UM001B-EN-P - May 2008 23
Chapter 4 Explicit Messaging
3. Choose the appropriate parameters in the Message
Configuration window.
Ethernet Network Communication
Serial Communication
Communication
Parameter Choice
Ty pe
Ethernet Data Table Address (This
Controller)
Size in Elements This is the number of elements being
Channel 1 Data Table Address
(Target Device)
MultiHop Yes
Read: This is the controller tag in which to store the data being read
Write: This is the controller tag that stores the value to be written to the power monitor.
read or written to. If you are performing a single element read or write, then this value should be 1. If you are performing a multiple element read or write, then this should be the number of elements after the source element that you wish to read or write.
Refer to Appendix
A for the address of
the specific data value you’re reading or writing to.
24 Publication 1408-UM001B-EN-P - May 2008
Explicit Messaging Chapter 4
Communication Ty pe
Serial Data Table Address (This
Parameter Choice
Controller)
Size in Elements This is the number of elements being
Channel 0 Data Table Address (Target
Device)
Local Node This is the serial node address of your
Read: This is the controller tag in which to store the data being read
Write: This is the controller tag that stores the value to be written to the power monitor.
read or written to. If you are performing a single element read or write, then this value should be 1. If you are performing a multiple element read or write, then this should be the number of elements after the source element that you wish to read or write.
Refer to Appendix the specific data value you’re reading or writing to.
power monitor.
A for the address of
Message setup is complete for Serial communication.
4. Click the MultiHop tab if configuring Ethernet communications.
5. Enter the IP Address of the power monitor in the To Address
box.
Message setup is complete.
Publication 1408-UM001B-EN-P - May 2008 25
Chapter 4 Explicit Messaging
RSLogix5 Software - Message Setup using PLC5 or SLC Typed Read/Write
The following is an example of how to set up your message instruction to read or write single or multiple elements to a power monitor using PLC5 or SLC Typed messages in RSLogix5. This setup applies to PLC5 programmable logic controllers.
Follow these steps to configure a message.
1. Choose an available message data block in your message
instruction.
In this example, we used MG9:0.
2. Click Setup Screen at the bottom of the message instruction.
The message configuration window for either Ethernet network or Serial communcation appears.
26 Publication 1408-UM001B-EN-P - May 2008
Explicit Messaging Chapter 4
3. Choose the appropriate parameters in the Message
Configuration window.
Ethernet Network Communication
Serial Communication
Communication Type Parameter Choice
Ethernet Communication Command Select the appropriate message type according to
Message Type
on page 18.
Data Table Address (This Controller) Read: This is the controller tag in which to store the data
being read. Write: This is the controller tag that stores the value to be
written to the power monitor.
Size in Elements This is the number of elements being read or written to. If
you are performing a single element read or write, then this value should be 1. If you are performing a multiple element read or write, then this should be the number of elements after the source element that you wish to read or
write. Port Number 2 Data Table Address (Target Device) Refer to Appendix
A for the address of the specific data
value you’re reading or writing to. MultiHop Yes
Publication 1408-UM001B-EN-P - May 2008 27
Chapter 4 Explicit Messaging
Communication Type Parameter Choice
Serial Communication Command Select the appropriate message type according to
Message Type
Data Table Address Read: This is the controller tag in which to store the data
being read.
Write: This is the controller tag that stores the value to be
written to the power monitor.
Size in Elements This is the number of elements being read or written to. If
you are performing a single element read or write, then
this value should be 1. If you are performing a multiple
element read or write, then this should be the number of
elements after the source element that you wish to read or
write.
Port Number 0 Data Table Address (Target Device) Refer to Appendix
value you’re reading or writing to.
Local Station Address This is the serial node address of your power monitor. Local / Remote Local
on page 18.
A for the address of the specific data
Message setup is complete for Serial communication.
4. Click the MultiHop tab if configuring Ethernet communication.
5. Enter the IP Address of the power monitor in the first row of the
To Address column.
Message setup is complete.
28 Publication 1408-UM001B-EN-P - May 2008
Explicit Messaging Chapter 4

Reading Logs

You can perform explicit messages to read data from log records in the power monitor.
For information on setting up explicit messages to the power monitor, please refer to Explicit Message Setup – Examples
The following logs can be read into a controller depending on the logs supported by your power monitor.
Unit Status Log
Min/Max Log
Energy Log
Load Factor Log
Time of Use Log kWh
Time of Use Log kVAR
Time of Use Log kVA
Please refer to Appendix log you are requesting.
A for the data table address of the specific
on page 17.
Log Data Table Methodology
The log data tables only hold one record instance for a specific log. Successive reads of the data table return a successive record instance for that log. By writing to specific configuration elements in the Log Request Table data table, you can configure the log to return in a forward or reverse direction. You can also configure the log to return a specific record for all logs except the Unit Status Log, and Energy Log.
Refer to
Log Request Table on page 64 for more information.
Publication 1408-UM001B-EN-P - May 2008 29
Chapter 4 Explicit Messaging
Example 1: Read the 5th Log Record in the Load Factor Log
This example explains how to configure the Log Request Table to read the 5
1. Create a write message to write the following values to the Log
Element Item Name Value
0 Selected Log 4 1 Chronology of Auto Return Data 0 2 Mix/Max Record to be Returned 0 3 Number of Unit Status Records 0 4 Number of Energy Log Records 0 5 Number of Time of Use Log Records 0 6 Number of Load Factor Log Records 0 7 Load Factor or TOU Record to be Returned 5
th
log record in the Load Factor Log.
Request Table.
2. Create a read message to read the values in the Load Factor Log
table.
30 Publication 1408-UM001B-EN-P - May 2008
Loading...
+ 70 hidden pages