Instruction Leaflet IL0131127EN Effective October 2018 Contents Description Page 1 Introduction 2 11 Reference documents 2 12 Definitions 2 2 Modbus communications 2 21 Modbus TCP 2 22 Modbus RTU via USB 2 23 Modbus function codes 2 24 Modbus slave/device address 2 ECAM Ethernet communications adapter module Modbus reference manual PXR-ECAM – MTCP: ethernet communication adapter module with Modbus TCP/IP Description Page 25 Register number vs register address 2 26 Exception codes 2 3 Modbus register map 3 31 Real-time data object registers 3 32 Input status (discrete inputs) 8 33 Setpoint registers 8 34 Event registers 26 Figure 1. Left = front view, right = side view CAM-PXR Link 24 VDC Mounting foot CAM expansion port USB conf port CAM-PXR link status LED Power Ok status Ethernet E1 w link/speed LEDs Ethernet E2 w link/speed LEDs DIN Relay CAM-Link Status Mounting foot Spring clip 99 mm (39”) 18 mm (71”) 35 mm (14”) DIN rail mount
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Instruction Leaflet IL0131127EN Effective October 2018
1 IntroductionThe PXR-ECAM is designed to connect with an electronic trip unit’s CAM link and expand the communication capabilities into ethernet Modbus TCP/IP and an HTML5 web interface . The ECAM is intended for use with PXR 20/25 molded case circuit breakers (MCCB), PXR 20/25 air circuit breakers (ACB) and NRX series circuit breakers . The module also provides discrete Inputs, relay outputs, and trip unit event data storage . In addition to Modbus TCP over ethernet, the ECAM also provides Modbus RTU capability on the USB port .
This document details the data and functions available for the PXR and NRX trip units via the ECAM Modbus register map . Depending upon trip unit features, a large number of features are accessible through the Modbus registers such as:• Real time data objects (voltage, current, power, energy, status
etc .);• Trip unit event logging (trips, alarms etc .);• Trip unit setpoints read/write;• ECAM network status (IP/MAC address); and• ECAM digital inputs and relay outputs .
1.1 Reference documents
IL0131132EN PXR ECAM Instruction Leaflet IL013005EN PXR ECAM User Manual
For further porudct information and upgrades access: www .eaton .com/cam
1.2 Definitions
ECAM ethernet communications adapter module .
ETU electronic trip unit .
Modbus RTU Modbus remote terminal unit . Modbus messaging over serial protocol such as RS-485 .
Modbus TCP Modbus messaging over ethernet TCP/IP protocol .
2 Modbus communicationsThe ECAM supports Modbus TCP using the ethernet ports and Modbus RTU using the USB port . In general, each port type provides access to the same register set except the USB port also provides some additional network configuration .
2.1 Modbus TCP
A Modbus TCP message is essentially a Modbus RTU message embedded in a TCP/IP wrapper . The Modbus master that initiates a message is considered a client of the Modbus slave which is consid-ered the server . The slave/server does not need a Modbus slave ID since it uses an IP address . Hence, any slave address can be used with a Modbus TCP message to the ECAM as it is not used .
2.2 Modbus RTU via USB
When the USB port is connected to a Windows® PC it is treated as a virtual serial port and appears in device manager ports as a USB serial device (COMx) port . You will need to install an .inf driver in order for the PC to recognize the serial port . The cable connection between the PC and the ECAM is an “A male to micro B” .
Driver install: Retrieve “LTK_USB_CDC .inf” from Eaton website ECAM downloads . Plug the unit into PC USB port . In Device Manager->Other Devices, right-click on LTK-USB and select Update Driver and Browse My Computer . Enter the path of the .inf file .
Select ‘Install this driver software’ . “LTK USB Serial” will show as completed .
Browse the Windows device manager and use the specified COMx (where x is a number such as 5 or 6 etc .) port as the serial port in the Modbus RTU master application .
2.3 Modbus function codes
ECAM Modbus communications supports the following Modbus function codes .
The ECAM is a Modbus slave device . For Modbus RTU over USB, the ECAM slave address is 1 and is not configurable . For Modbus TCP, the ECAM will respond to any slave address from 1-247 since the IP address is what actually identifies the particular device on the network .
2.5 Register number vs. register address
Modbus register maps often identify registers by number, address, or both . Register number is simply 1 greater than the address . In actual Modbus messages, the register address is used . In this document, register identification is usually by register number unless the address is specified .
2.6 Exception codes
When there is an error in a request or response, the ECAM will respond an exception code .• If the function code in the query is not supported, exception code
01 is returned in the response; also used for the unsupported sub-function code in Modbus diagnostics .
• If the requested data register/bit address is illegal, exception code 02 is returned .
• If the data in the query is illegal, exception code 03 is returned .• If the ECAM does not support the query function, exception code
04 is returned .
3
Instruction Booklet IL0131127ENEffective October 2018
3 Modbus register map3.1 Real-time data object registers
Real-time objects such as current, voltage, power, energy and so on are shown in Table 2 below . Most real-time data can be obtained either in IEEE floating point or in fixed-point format . Energy objects can be only obtained in fixed-point format . For data shown in fixed-point format, each result would be the real-time data multiplied by the scale factor shown in that column .
3.1.1 Energy objects
Energy objects can be obtained in two-register fixed-point data format and four-register encoded format but not in floating point format . The two-register format is presented in units of kilowatt-hours .
The four registers encoded energy object occupies register 3 through register 0 . Register 3 is the high order register and register 0 is the low order register . Register 3 high byte contains value corresponding to engineering units (power of 10 signed exponent) . Register 3 low byte contains a mantissa multiplier value (power of 2 exponent) . Register 3 through register 0 contains a 48-bit energy mantissa in units of watthours . The data format of four registers is shown as follows .
Since these objects have the capability to change in real time, a complete data object must be obtained in a single transaction to avoid data tearing .
4
Instruction Booklet IL0131127ENEffective October 2018
Input status bits 1001 through 1032 may be available using function code 02 . The status definitions are defined in the following table . The first 16 bits are the actual status state while the last 16 bits indicate whether the corresponding status state is valid(1) or not(0) . If invalid the bit should be ignored .
Table 6. Input status bits.
Input Definition Input Definition
1001 Breaker is in the closed position
1017 Breaker is in the closed position is validity
1002 Un-acknowledged trip condition
1018 Unacknowledged trip condition is validity
1003 Active or un-acknowledged alarm
1019 Active or un-acknowledged alarm validity
1004 0 1020 01005 Maintenance mode
is active1021 Maintenance mode is active
validity1006 Test mode is active 1022 Test mode is active validity1007 0 1023 01008 0 1024 01009 Phase rotation is
ABC11025 Phase rotation is ABC validity
1010 Long delay pickup is active
1026 Long delay pickup is active validity
1011 Zone interlock is active
1027 Zone interlock is active validity
1012 0 1028 01013 “Ground” is source
ground1029 “Ground” is source ground
validity1014 Breaker is in the
“connected” position11030 Breaker is in the “connected”
position validity1015 Spring is the charged
state11031 Spring is the charged state
validity1016 0 1032 01 NRX1150 only.
Note when accessing these (via function code 02), the status bits you request are packed in bytes in the return message . For example, if you request four status bits starting at 1001, you will get one byte of status bits back with those four bits in the lower nibble . If you request 16 status bits, they return packed into two bytes and so on .
3.3 Setpoint registers
The trip unit’s setpoints are organized into groups . Each group can be considered as a binary array of information which can be obtained through Modbus register access .
Register 3001 is a R/W register used to select the particular group . The high byte contains the requested group number; while the low byte must contain 255(0xFF16) . The setpoints register can be read using function code 03 or 04 . Register 3001 can be written using function code 06 or 16 .
Depending upon the group selected, a specific number of registers in the range 3002 through 3122 contain the binary array of setpoint information . These may be read by using function code 03 or 04 .
To modify setpoints, the following process is followed:
A . Write selected group to register 3001;
B . Write password to register 3000;
C . Write modified group witch function code 16; and
D . Execute “Save Setpoints Change” slave action command within 10 seconds .
In Step C ., a complete setpoint group of registers must be written in one Modbus transaction using function code 16 .
Note that the changes and save action must be completed within ten seconds of writing the correct password . The password format is 16-bit unsigned decimal number . This password is the password as entered at the trip unit display and is not related to the password needed to log into the web interface of the ECAM . Some trip unit’s (such as NRX1150) do not support or require a password . In this case the password can still be written but is ignored .
After completing the setpoint group write, the new setpoint values may be either saved or aborted by sending the control function “Save Setpoints Change” or “Abort Setpoints Change”, respectively (see the Section 3 .4 .3 entitled “Control Actions”) . The ECAM will automatically abort the write setpoint group transfer in approximately 15 minutes if no further writes are initiated with the currently written setpoint group .
The setpoint group definitions for the NRX520M, NRX1150, PXR ACB, and PXR MCCB are presented in the following tables/sections .
3.3.1 PXR MCCB setpoints
The following PXR MCCB setpoint groups are accessible via the ECAM:
0 – System group
1 – Protection group
2 – Modbus settings group (trip unit local Modbus port)
4 – I/O module group
9
Instruction Booklet IL0131127ENEffective October 2018
Table 7. PXR MCCB - setpoints group 0: system group.Register Setpoint name R/W Format Value definition Unit
3000 Password W “0000” (factory default). See Section 3.3.3001 Group 0 = system R/W 0x00FF3002 Rating information R Encoded 25 --> 25 A
40 --> 40 A 60 --> 60 A 63 --> 63 A 90 --> 90 A 100 --> 100 A 125 --> 125 A 140 --> 140 A 150 --> 150 A 160 --> 160 A 200 --> 200 A 220 --> 220 A 225 --> 225 A 250 --> 250 A 300 --> 300 A 350 --> 350 A 400 --> 400 A 450 --> 450 A 550 --> 550 A 600 --> 600 A 630 --> 630 A800 --> 800 A 875 --> 875 A 1000 --> 1000 A 1200 --> 1200 A 1250 --> 1250 A 1400 --> 1400 A 1600 --> 1600 A 2000 --> 2000 A 2500 --> 2500 A
b0 --> LdSel: with long delay protection b1 --> SdSel: with short delay protection b2 --> InstSel: with Inst protection b3 --> GfSel: with ground fault protection b4 --> ARMSel: with maintenance mode b5 --> OvrideSel: with override protection b6 --> RCDSel: with ground fault RCD b7 --> MotorSel: with motor protection b8 --> NeuSenorSel: with neutral sensor b9 --> ThermalSel: with thermal memory b12 --> VoltSel: with voltage sampling feature b13 --> ExtADCSel: with external AD7779
3005 Style2 R Encoded 0 = false 1 = true
b0 --> ModbusSel: with integrated Modbus b1 --> CAMSel: with CAM RS422 port b2 --> IOModuleSel: with IO module port b3 --> RelaySel: with relay b4 --> ZSISel: with ZSI b5 --> LCDSel: with LCD display feature = 1
10
Instruction Booklet IL0131127ENEffective October 2018
Register Setpoint name R/W Format Value definition Unit
3006 Maintenance mode: state R/W Encoded b8 - ARMs mode status, read-only bit. 0 --> MM disabled in trip unit 1 --> MM enabled in trip unit b7 - “Local ON” shows the position MM switch, read-only bit. 0 <--> switch on OFF/REMOTE position 1 <--> switch on ON position b6 - “Local MM Switch” position valid or invalid, read-only bit. 0 <--> rotary switch position is valid 1 <--> rotary switch position is invalid b1 - “MM pin” shows the status of MM signal sent from secondary terminal, read-only bit. 0 <--> MM pin on secondary terminal inactive 1 <--> MM pin on secondary terminal active b0 - “Remote Control” of MM, configurable bit. 0 <--> remote communication channel disables MM mode 1 <--> remote communication channel enables MM mode
3007 ARMs level R/W Encoded 1 = 2.5 * In 2 = 4 * In 3 = 6 * In 4 = 8 * In 5 = 10 * In
3003 Break frame R Encoded 00 --> NRX NF01 --> NRX RF02 --> Magnum std.03 --> Magnum narrow04 --> Magnum double wide05 --> Magnum double narrow06 --> MCCB11 --> NZM212 --> NZM313 --> NZM421 --> PD222 --> PD3-A23 --> PD3-B24 --> PD425 --> PD526 --> PD6
3004 Style 1 R Encoded0 = false1 = true
b0 --> LdSel: with long delay protectionb1 --> SdSel: with short delay protection b2 --> InstSel: with Inst protectionb3 --> GfSel: with ground fault protection b4 --> ARMSel: with maintenance mode b5 --> OvrideSel: with override protection b6 --> RCDSel: with ground fault RCD b7 --> MotorSel: with motor protectionb8 --> NeuSenorSel: with neutral sensor b9 --> ThermalSel: with thermal memory b12 --> VoltSel: with voltage sampling feature b13 --> ExtADCSel: with external AD7779
3005 Style 2 R Encoded0 = false1 = true
b0 --> ModbusSel: with integrated Modbusb1 --> CAMSel: with CAM RS422 portb2 --> IOModuleSel: with IO module portb3 --> RelaySel: with relayb4 --> ZSISel: with ZSIb5 - -> LCDSel: with LCD display feature = 1
3007 ZSI R/W Encoded ZSI, zone interlock*When enabled, for trip unit with G, ZSI is implemented for short delay and ground fault.*When enabled, for trip unit without G, ZSI is implemented for short delay.Trip unit side:0 <--> disable1 <--> enable
Table 10. PXR MCCB - setpoints group 4: I/O module group.Register Setpoints name R/W Format Value definition
3000 Password W Encoded Default “0000”3001 I/O module Cfg R/W Encoded 0x04FF3002 Validity flags 0….15 R/W Encoded For each bit:
0: corresponding parameter inactive1: corresponding parameter activee.g. Bit 8 = 1 ==> parameter 8 = active
3003 Validity flags 16….31 R/W Encoded For each bit: 0: corresponding parameter inactive1: corresponding parameter activee.g. Bit 8 = 1 ==> parameter 8 = active
3004 0: digital output 0 R/W Encoded3005 1: digital output 1 R/W Encoded3006 2: digital output 2 R/W Encoded3007 3: digital output 3 R/W Encoded3008 4: S0 channel 0 type R/W 0: ouput disabled
1: sends pulses based on active energy2: sends pulses based on reactive energy3: sends pulses based on apparent energy
3009 5: S0 channel 0 scale R/W 0: sends a pulse every 1 W1: sends a pulse every 10 W2: sends a pulse every 100 W3: sends a pulse every 1000 W
3010 6: S0 channel 0 pulse R/W pulse duration x *10 msrange: 1…50 ==> 10…500 ms
3011 7: S0 channel 1 type R/W 0: output disabled1: sends pulses based on active energy2: sends pulses based on reactive energy3: sends pulses based on apparent energy
3012 8: S0 channel 1 scale R/W 0: sends a pulse every 1 W1: sends a pulse every 10 W2: sends a pulse every 100 W3: sends a pulse every 1000 W
3013 9: S0 channel 1 pulse R/W Pulse duration x *10 mRange: 1…50 ==> 10…500 ms s
The triggering of an event in a trip unit can provide historical data object values at the instance in time the event occurred . The ECAM groups the events into particular types as shown below .
Table 27. Event types & capacities.Event type Max stored Type Format ID Note ETU
A single triggering can place information into multiple event types . For example, the occurrence of an event triggered by a circuit breaker trip may provide historical summary, historical trip informa-tion, and trip waveforms .
Access to event information is based on the selection of event type and event ID . Register 8193 is a R/W register used to select the event type, using function code 06 or 16 to write . The event infor-mation may be read by using function code 03 or 04 .
When the event type selection is written in register 8193, the earli-est and latest event ID can be obtained respectively in register 8194 and 8196 to determine the range of events saved for the selected type . Register 8198 is a R/W register used to select the requested event ID and is written with function code 16 . If the requested event exists, register 8200 and 8202 provide the Previous event ID and Next event ID . If the requested event does not exist in trip unit, an exception code is returned .
The date and time when request event happened is read in registers 8204 through 8211 using the same date and time description as shown in Table 38 . This corresponds to the time of occurrence of the historical event .
Register 8212 provides a format ID to indicate the selected event type’s data content . Validity bit 0 set to 1 indicates that the first data object contains valid information, bit 1 indicates the second data object contains valid information, etc . The number of additional validity registers is thus equal to the (number of data objects -1) / 16 . The data object registers follow the last validity register . An invalid register access exception code 02 will be returned for any attempted read past the last data object register .
Note that some trip units do not support all data features . For example the PXR20 does not provide voltage inputs and hence voltage and power data and related waveforms will be invalid or not present .
Oscillographic waveform data (Table 34) provides a delta time between points variable at register pair 8213 . The data points follow time delta time variable at register 8215 up to the number of regis-ters required to contain the all the data points . An invalid register access exception code 02 will be returned for any attempted read past the last data point register .
27
Instruction Booklet IL0131127ENEffective October 2018
Table 28. Historical summary event.Register Format R/W Historical summary event
8193 Encoded R/W Event type = 8EFF16
8194 Unsigned32 R Earliest event ID8196 Unsigned32 R Latest event ID8198 Unsigned32 R/W Requested event ID8200 Unsigned32 R Previous event ID8202 Unsigned32 R Next event ID8204 Date/Time R Date/time8212 Encoded R Format of data = 000016, 000116, 000416, 000516, 000616
8213 b0 R Object validity bit8214 Encoded R Event cause
00 = power up - time OK 01 = setpoints download 02 = time adjusted 03 = trip 04 = alarm 05 = enter test mode 06 = exit test mode 07 = plug changed 08 = power up - no time 09 = test completed 10 = maintenance mode active 11 = maintenance mode inactive 12 = opened by communications 13 = closed by communications:
Table 29. Historical time adjustment event.Register Format R/W Historical time adjustment event
8193 Encoded R/W Event type = 85FF16
8194 Unsigned32 R Earliest event ID8196 Unsigned32 R Latest event ID8198 Unsigned32 R/W Requested event ID8200 Unsigned32 R Previous event ID8202 Unsigned32 R Next event ID8204 Date/time R Date/time8212 Encoded R Format of data = 000116
8213 b0 R Object validity bit8214 Date/time R New date/time
28
Instruction Booklet IL0131127ENEffective October 2018
Table 30. Historical capture event - NRX1150 only.Register Format R/W Historical capture event Units
8193 Encoded R/W Event type = 88FF16
8194 Unsigned32 R Earliest event ID8196 Unsigned32 R Latest event ID8198 Unsigned32 R/W Requested event ID8200 Unsigned32 R Previous event ID8202 Unsigned32 R Next event ID8204 Date/time R Date/time8212 Encoded R Format of data = 000216
8213 b10 – b0 R Object validity bits8214 Encoded R Cause of capture: 00 = network, 01 = display8215 Unsigned16[31] R IA harmonic content: fundamental through 31st harmonic %8246 Unsigned16[31] R IB harmonic content: fundamental through 31st harmonic %8277 Unsigned16[31] R IC harmonic content: fundamental through 31st harmonic %8308 Unsigned16[31] R IN harmonic content: fundamental through 31st harmonic %8339 Unsigned16[31] R VAN harmonic content: fundamental through 31st harmonic %8370 Unsigned16[31] R VBN harmonic content: fundamental through 31st harmonic %8401 Unsigned16[31] R VCN harmonic content: fundamental through 31st harmonic %8432 Unsigned16[31] R VAB harmonic content: fundamental through 31st harmonic %8263 Unsigned16[31] R VBC harmonic content: fundamental through 31st harmonic %8294 Unsigned16[31] R VCA harmonic content: fundamental through 31st harmonic %
Table 31. Historical trip/major alarm event.Register Format R/W Historical trip & major alarm event Units
8194 Unsigned32 R Earliest event ID8196 Unsigned32 R Latest event ID8198 Unsigned32 R/W Requested event ID8200 Unsigned32 R Previous event ID8202 Unsigned32 R Next event ID8204 Date/time R Date/time8212 Encoded R Format of data: trip = 000416 major alarm = 000516
8213 b15 - b00 R Object validity bits8214 b31 - b16 R Object validity bits8215 Encoded R Status cause (primary, secondary, cause)8217 Unsigned32 R IA A8219 Unsigned32 R IB A8221 Unsigned32 R IC A8223 Unsigned32 R IN A8225 Unsigned32 R IG source A8227 Unsigned32 R IG residual A8229 Unsigned32 R VAB V8231 Unsigned32 R VBC V8233 Unsigned32 R VCA V8235 Unsigned32 R VAN V8237 Unsigned32 R VBN V8239 Unsigned32 R VCN V8241 Signed32 R Real 3 phase power W8243 Signed32 R Real 3 Phase Power Demand W8245 Unsigned32 R Apparent 3 phase power VA8247 Signed16 R Device temperature 1/10 oC8248 Unsigned16 R Frequency 1/10 Hz8249 Signed32 R Reactive 3 phase power vars8251 Signed16 R Apparent power factor 1/100 pf8252 Unsigned16 R IA % THD 1/10 %8253 Unsigned16 R IB % THD 1/10 %
29
Instruction Booklet IL0131127ENEffective October 2018
Register Format R/W Historical trip & major alarm event Units
8254 Unsigned16 R IC % THD 1/10 %8255 Unsigned16 R IN % THD 1/10 %8256 Unsigned16 R Operations count8257 Signed32 R Reactive power demand vars8259 Unsigned32 R Apparent power demand VA8261 Unsigned32 R IA demand A8263 Unsigned32 R IB demand A8265 Unsigned32 R IC demand A8267 Unsigned32 R IN demand A8269 b31 - b00 R Binary status with validity bits (see Table
<NRX Discrete Input Status Definitions>
Table 32. Historical minor alarm event.Register Format R/W Historical minor alarm event Units
8193 Encoded R/W Event\type: alarm = 81FF16
8194 Unsigned32 R Earliest event ID8196 Unsigned32 R Latest event ID8198 Unsigned32 R/W Requested event ID8200 Unsigned32 R Previous event ID8202 Unsigned32 R Next event ID8204 Date/time R Date/time8212 Encoded R Format of data: minor alarm = 000616
8213 b0 R Object validity bit8214 Encoded R Status cause (primary, secondary, cause)
Table 33. Historical trend event.
Register Format R/W Historical trend event Units
8193 Encoded R/W Event type = 8AFF16
8194 Unsigned32 R Earliest entry tag8196 Unsigned32 R Latest entry tag8198 Unsigned32 R/W Requested entry tag8200 Unsigned32 R Event ID associated with this entry tag8202 Unsigned32 R Number of entry tags associated with this event ID8204 Date/time R Date/time8212 Encoded R Format of data = 000316
8213 b2 - b0 R Object validity bits8214 Unsigned64 R Forward active energy kWh8218 Unsigned64 R Reverse active energy kWh8222 Unsigned64 R Apparent energy kVAh
ote:N Addresses 8225 and 8227 are both ground current . According to the setpoint “ground sensing” setting in “Setpoints group 1: protection group”, the actual ground current would be displayed in related register and the value in the other register would be zero . For example, if the “ground sensing” setting is 0, the ground current sensing type is residual ground current . IG residual in address 8227 would be the actual value and IG source in address 8225 would be zero .
8194 Unsigned32 R Earliest event ID8196 Unsigned32 R Latest event ID8198 Unsigned32 R/W Requested event ID8200 Unsigned32 R Previous event ID8202 Unsigned32 R Next event ID8204 Date/time R Date/time8212 Encoded R Format of data (= event type)8213 IEEE float R Delta time between points sec8215 Data format [xx] R Data points
Note: Voltage waveforms are not available on PXR20 models.
3.4.1 Block of registers
A block of registers can be established to remap the data object registers to different register addresses . The block of registers is stored in non-volatile memory and is retained between power cycles .
Function code 16 is used to load the object assignments for the block of registers . The block assignments are stored beginning at 1001/20481 . Only the first data object register address is assigned within the block of registers . For example, although data object IA occupies register 4611 and 4612, only register 4611 is loaded into the block of assignment registers . Verification of this block of assignment registers can be read from trip unit with a function code 03 or 04 from these 1001/20481 registers .
Data pertaining to the objects configured in the block of assign-ment registers is mapped into registers starting at 1201/20737 and continuing in successive order for each object assigned . The number of objects and their placement order in this data block of registers is dependent on the configuration of the block of assignment registers . The total number of data block of registers is limited to 100 .
The data can be obtained from the data block of registers by a read function code 03 or 04 . The address of the starting object must be aligned with a starting address of an object within the data block of registers . The number of registers to obtain must align with an ending address of an object within the data block of registers .
31
Instruction Booklet IL0131127ENEffective October 2018
Modbus register number Modbus register addressNumber of registersLow High Low High
Mapped block of registers configuration R/W 1001 20481 1000 20480 100Mapped block of registers data R 1201 20737 1200 20736 200Invalid object access configuration R/W 2001 25345 2000 25344 1Floating point data word order configuration R/W 2002 25346 2001 25345 1Fixed point data word order configuration R/W 2003 25347 2002 25346 1Control actions R/W 2901 25089 2900 25088 3Date and time register R/W 2921 2920 8
3.4.2 Configuration Registers
Non-volatile register 2001/25345 is used to configure the ECAM to respond to a group of data objects, of which some objects are invalid within that group . When non-zero (factory default value), any attempt to access a group of data objects that contain an invalid object will result in an illegal data object code 02 .
When register 2001/25345 is set to zero, the ECAM will respond to a group of objects with data contained in the valid objects of the group . Since data is not available for the invalid objects, the informa-tion in the register is undefined . These registers may contain 000016 or a value of (0xFFFFFFFF16) may be used to represent an invalid unsigned fixed point object . (0x8000000016) may be used to repre-sent an invalid signed fixed point object and (NAN = 0x7FF2000016) may be used to represent an invalid floating point value . This allows access to a block of registers using a single read command, of which some are not implemented in that block, rather than multiple read commands which contain only implemented registers . The applica-tion is thus responsible for selecting the implemented registers . The starting register number must be valid object . If the starting register number accesses an invalid object, the illegal data object exception code 02 will be issued, regardless of this configuration setting .
Non-volatile register 2002/25346 is used to configure the data transmission order of 32-bit floating point data . If non-zero (factory default value), the floating point low order word is first in the Modbus register space . When the register is set to be 0, the float-ing point high order word is first in the Modbus register space .
Non-volatile register 2003/25347 is used to configure the data trans-mission order of 32-bit fixed point data . If non-zero (factory default value), the fixed point low order word is first in the Modbus register space . When the register is set to be 0, the fixed point high order word is first in the Modbus register space .
Configuring any or all registers 2001/25345 through 2003/25347 is accomplished using a write function code “06” or “16” .
3.4.3 Control actions
A set of registers is reserved for trip unit remote control and ECAM specific controls, starting from 2901/25089 through 2903/25091 . These three registers should be written together with a “slave action number” and its 1’s complement using function code 16 . The “slave action number” and its function are listed in remote control data formats, their support being product dependent . The 1’s complement encoding is utilized to make it more difficult to send an accidental control action such as open/close breaker that was not intended .
If the “slave action number” and its first complement command is valid, trip unit will execute the action . Once the command is successfully acknowledged by the trip unit, it returns a normal function code 16 response to Modbus master . Since it may take some time for the trip unit to take action, the Modbus master may further determine if the product completed the slave action function successfully after the normal response by interrogating the trip unit, for example, by reading its status . If the “slave action number” and its first complement command is invalid, trip unit returns exception code 03 .
32
Instruction Booklet IL0131127ENEffective October 2018
System Control Capture waveform 3 0 1Reset interface statistics 3 0 2Save setpoints change 3 0 7Abort setpoints change 3 0 10Reset setpoints change flag 3 1 1
ECAM relay outputs Relay breaker mode on 110 163 0Relay breaker mode off 110 163 1Relay 1 on (RLY1) 110 1 0Relay 1 off (RLY1) 110 1 1Relay 2 on (RLY2) 110 2 0Relay 2 off (RLY2) 110 2 1
ECAM non-volatile memory control
Erase event and system logs 14 14 14Erase ECAM configuration 14 14 15
3.4.4 ECAM relay control
The ECAM relay outputs RLY1, RLY2 are located on the ECAM itself at connector TD as shown in the diagram below . The can operate either in breaker mode or general mode . Since these physically exist on the ECAM and are not on the trip unit, they can be operated without an ETU connected .
In breaker mode, the relays work as a unit where a “Close” command closes relay 1 for ~ .5 seconds while relay 2 is held open . An “Open” command closes relay 2 for ~ .5 seconds while relay 1 is held open .
In General mode, the two relays can be individually latched closed or open .
mWARNINGDO NOT CONNECT THE RELAY OUTPUTS TO THE CIRCUIT BREAKER “OPEN” AND “CLOSE” CIRCUITS UNLESS REMOTE CONTROL IS SPECIFI-CALLY INTENDED AND THE PROCESS FOR ISSUING THE REMOTE OPEN/CLOSE IS RESTRICTED, CONTROLLED, AND HAS BEEN SAFETY EVALUATED/APPROVED.
mWARNINGNEVER CONNECT THE RELAY OUTPUTS TO THE CIRCUIT BREAKER “OPEN” AND “CLOSE” CIRCUITS WHEN THE RELAY OUTPUTS ARE INTENDED FOR GENERAL PURPOSE OPERATION.
33
Instruction Booklet IL0131127ENEffective October 2018
The “Erase Event and System Logs” command will erase all event and system Log data stored within the ECAM . This can be used for maintenance purposes to reset the storage after testing etc . Note that system log data is only accessible through the ECAM web interface .
The “Erase ECAM configuration” command will reset all ECAM internal configuration to default factory settings . This includes reset-ting the following:• Ethernet IP allocation method and any user fixed IP address;• Customer defined network User accounts; and• Admin user password restored to default .
3.4.6 Date and time
The ECAM supports Modbus master read real-time clock informa-tion . Eight registers, starting from register number 2921, are reserved for this information, as defined in 0 . Detailed information is listed in 0 . User could set system time through function code 16 .
The ECAM supports internal diagnostics to monitor internal Modbus port communication with function code 08 . For different sub-function codes, diagnostics information is listed below .
Identification registers are read only data read using function code 03 or 04 . ASCII format means the data is available as a null termi-nated string of ASCII characters . The size of the string can be less than the range indicated below .
Table 39. ETU ID registers.Register number
Modbus address Description Format Range Registers Comments
4497 4496 Device name ASCII 16 char 84505 4504 Model name ASCII 16 char 84513 4512 N/A4529 4528 Style # ASCII 32 char 16 Numeric
… Reserved4494 4493 Reserved4495 4494 Product ID Bit map 32-bit 2 Division code = 0X0F
Product code = 0x01Comm ver = 0000|0010|0000|1111b = 0x020F
3.4.10 ECAM specific registers
The following is a list of registers and related functions that are specific to the ECAM and not related to the trip unit that may be connected to the ECAM . For register reads use function codes 03 or 04 . For register writes use function code 016 . Registers with an ASCII format return two characters per register and multiple regis-ters are read to obtain the entire string .
Table 41. ECAM specific registers.
Description R/W Register addressRegister count Data parameters Format Note
FW version R 25628 3 0xrrrr (rev) 0xmmmm (minor) 0xMMMM (major)
16-bit unsigned Three words returned. Rev is first word.
RTC time R/W 25700 2 0xMMSS0x00HH
BCD Each nibble contains a binary coded decimal number.
UART framing errors R 25639 1 16-bit unsigned UART connection to trip unitUART noise errors R 25640 1 16-bit unsigned UART connection to trip unitUART overrun errors R 25641 1 16-bit unsigned UART connection to trip unitRTC date R/W 25704 2 0xMMDD
0x00YYBCD
Active IP address R 25665 2 0xCCDD0xAABB
16-bit unsigned IP address = AA.BB.CC.DD
IP allocation method R/W 25771 1 0xNNNN 16-bit unsigned NNNN=0 - Fixed 192.168.1.11 - DHCP2 - Address from NV memory
Static IP address R/W 25776 2 0xLLLL0xHHHH
16-bit unsigned IP address to use when 25771=2
MAC address R 25673 3 0xNNNN0xAF0A 0x00D0
16-bit unsigned 1st word 0xNNNN has unique address, 2nd & 3rd are fixed
Digital inputs R 25727 2 0x0X0Y0x000Z
16-bit unsigned X = Dig Input IN1 stateY = Dig Input IN2 stateZ = Dig Input IN3 stateStates are 0 or 1
ECAM PCB temperature R 25774 1 16-bit signed Units in degrees CCAM unit serial # R 43110 6 YYMMDDLPXXXX ASCII 12 characters in 6 registersHW rev R 43120 3 XXXYYY ASCII 6 characters in 3 registersPCB serial number R 43180 6 XXXXXXXXXXXX ASCII 12 characters in 6 registersCatalog number R 43140 10 PXR-ECAM-MTCP ASCII Up to 20 characters in 10 registersStyle number R 43160 10 66D2352G01 ASCII Up to 20 characters in 10 registers
35
Instruction Booklet IL0131127ENEffective October 2018
The active IP address can be read from two registers starting at address 25665 . This is helpful if the IP address cannot be read from the trip unit display .
For example:
If 0x0ED8 is read from 25665 and 0x0A82 is read from 25666 this represents IP address 10 .130 .14 .216
Table 42. ECAM IP address example decodeRegister 25665 (low word= 3rd & 4th octets)
Register 25666 (high word = 1st & 2nd octets)
Hex 0E D8 0A 82Decimal 14 216 10 130
3.4.12 IP address allocation (USB port only)
The IP address allocation method is set by writing to register 25771 and selecting either fixed IP address or dynamic (DHCP):
0 - Fixed default 192 .168 .1 .1;
1 - DHCP - network assigned;
2 - Address from NV memory .
For example, to set a fixed IP address:
1 . Write desired IP address to 25776 as two words (low word/octets first) .
2 . Write a 2 to register address 25771 ( take address from NV memory) .
3 . Reboot ECAM (power cycle) .
To set for dynamic/DHCP IP:
1 . Write a 1 to register address 25771 (dynamic allocation) .
2 . Reboot ECAM (power cycle) .
3.4.13 Dig inputs description
The ECAM 24 V digital inputs IN1, IN2, and IN3 are available at connector at TD pins 4, 3, 2 respectively (see Figure 2 . ECAM I/O connections) . They physically exist on the ECAM and are not related to the ETU . To activate an input, 24 Vdc is applied between the input pin and the common return at TD .1 . The table below indicates the read register values expected for the possible states of the 3 inputs .
Instruction Booklet IL0131127ENEffective October 2018
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY
The information, recommendations, descriptions and safety nota-tions in this document are based on Eaton Corporation’s (“Eaton”) experience and judgment and may not cover all contingencies . If further information is required, an Eaton sales office should be consulted . Sale of the product shown in this literature is subject to the terms and conditions outlined in appropriate Eaton selling policies or other contractual agreement between Eaton and the purchaser .
THERE ARE NO UNDERSTANDINGS, AGREEMENTS, WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE OR MERCHANTABILITY, OTHER THAN THOSE SPECIFICALLY SET OUT IN ANY EXISTING CONTRACT BETWEEN THE PARTIES . ANY SUCH CONTRACT STATES THE ENTIRE OBLIGATION OF EATON . THE CONTENTS OF THIS DOCUMENT SHALL NOT BECOME PART OF OR MODIFY ANY CONTRACT BETWEEN THE PARTIES .
In no event will Eaton be responsible to the purchaser or user in contract, in tort (including negligence), strict liability or other-wise for any special, indirect, incidental or consequential damage or loss whatsoever, including but not limited to damage or loss of use of equipment, plant or power system, cost of capital, loss of power, additional expenses in the use of existing power facilities, or claims against the purchaser or user by its customers resulting from the use of the information, recommendations and descriptions contained herein . The information contained in this manual is subject to change without notice .