Comunicaciones Modbus Guía de usuario Para los interruptores automáticos Powerpact marcos H, J y L con unidades de disparo Micrologic

Transcription

1 Modbus Communication User Guide For PowerPact H-, J- and L-Frame Circuit Breakers Comunicaciones Modbus Guía de usuario Para los interruptores automáticos Powerpact marcos H, J y L con unidades de disparo Micrologic Communication Modbus MC Guide de l utilisateur pour disjoncteurs PowerPact MC à châssis H, J et L avec déclencheurs Micologic MC Instruction Bulletin Boletín de instrucciones Directives d'utilisation Retain for Future Use. / Conservar para uso futuro. / À conserver pour usage ultérieur.

2

3 Modbus Communication User Guide For PowerPact H-, J- and L-Frame Circuit Breakers Instruction Bulletin Retain for future use.

4 ENGLISH

5 Modbus Communication User Guide 06/2011 Table of Contents SECTION 1: MODBUS COMMUNICATION... 5 Introduction... 5 Access to Functions... 5 General Description... 5 Mounting... 6 Connection to the Modbus Network... 6 Modbus Address Switches... 7 Modbus Traffic LED... 7 Modbus Locking Pad... 7 Test Button... 8 Test LED... 8 Schematics... 8 Configuration of the Modbus Interface Module Automatic Configuration Personalized Configuration ENGLISH SECTION 2: MODBUS PROTOCOL Modbus Master-Slave Principle Characteristics of the Master-Slave Principle Master-Slave Communication Mode Request-Reply Mode Broadcast Mode Response Time Data Exchange Registers and Addresses Frames Modbus Functions Read Functions Scattered Holding Register Read Function Write Functions Diagnostic Functions Diagnostic Counters Counters Reset Modbus Exception Codes Exception Responses Exception Frame Exception Codes Hardware Protection Software Protection Password Management Default Passwords Password Modification with RSU Password Reset with RSU Command Interface Command Data Structure Command Status Command Examples Open Circuit Breaker Reset Energy Measurements Read Date and Time Date Management Date Format External Synchronization Internal Synchronization Date Counter Date Conversion Principle Date Conversion Example History Mechanism Schneider Electric All Rights Reserved 3-EN

6 Modbus Communication User Guide Table of Contents 06/2011 ENGLISH History Mechanism History Reading Modbus Registers Tables Table Format Data Types SECTION 3: MICROLOGIC TRIP UNIT DATA Micrologic Trip Unit Registers Real-Time Measurements Minimum/Maximum Values of Real-Time Measurements Energy Measurements Demand Measurements Minimum/Maximum Measurements Reset Time Identification Status Alarm History Trip History Maintenance Operation History Pre-Alarms User-Defined Alarms Protection Parameters Configuration of the SDx Module Measurement Parameters Time-Stamped Information Maintenance Indicators Miscellaneous Micrologic Trip Unit Commands Protection Commands Acknowledge Event Commands Measurement Configuration Commands SECTION 4: BSCM DATA BSCM Registers Identification Status Maintenance Indicators Event History BSCM Commands Commands and Error Codes Circuit Breaker Control Commands Counter Commands SECTION 5: MODBUS INTERFACE MODULE DATA Modbus Interface Module Registers Identification Modbus Network Parameters Modbus Interface Module Commands List of Modbus Interface Module Commands Communication Profile Communication Profile Registers APPENDIX A: CROSS REFERENCES TO MODBUS REGISTERS EN 2011 Schneider Electric All Rights Reserved

7 Modbus Communication User Guide 06/2011 Section 1 Modbus Communication Section 1 Modbus Communication Introduction The Modbus communication option enables a PowerPact H-, J-, or L- frame circuit breaker to connect to a supervisor or to any other device with a master Modbus communication channel. ENGLISH The Modbus communication option is available for the following circuit breaker configurations: PowerPact H-, J-, or L-frame electronic trip circuit breakers with the BSCM (Breaker Status Control Module) and with the communicating motor operator PowerPact H-, J-, or L-frame circuit breaker with Micrologic 5/6 trip unit A PowerPact H-, J-, or L-frame circuit breaker connects to a Modbus communication network through a Modbus Interface Module (IFM). Access to Functions The Modbus communication option provides access to such functions as: reading of metering and diagnostic data reading of status conditions and remote operations transfer of time-stamped events displaying protection settings reading of the circuit breaker identification and configuration data time-setting and synchronization Functions available depend on the application, the circuit breaker with its Micrologic trip unit type, and on the BSCM. General Description The IFM enables an ULP (Universal Logic Plug) PowerPact J-frame circuit breaker to connect to a Modbus network. Each circuit breaker has its own IFM and a corresponding Modbus address. Figure 1: Modbus Interface Module (IFM) pin screw type connector (Modbus connection and power supply) 2. Modbus address switches 3. Modbus traffic LED 4. Modbus locking pad 5. Test LED 6. Test button 7. Mechanical lock 8. 2 RJ45 connectors 9. Stacking accessory connection Schneider Electric All Rights Reserved 5-EN

8 Modbus Communication User Guide Section 1 Modbus Communication 06/2011 ENGLISH Mounting Connection to the Modbus Network The Modbus Interface Module is a DIN rail mounted device. A stacking accessory enables the user to interconnect several interface modules without additional wiring. The 5-pin screw-type connector enables the Modbus Interface Module to connect to the Modbus network (2 wires) and to the 24 Vdc power supply. Each pin is labeled for easier wiring. Table 1: Modbus Interface Module Pins Connector Marking Color Description Unshielded Length Stripped Length D1 D1 Blue Communication pair D1: RS 485 B/B signal or Rx+/Tx+ D0 White D0: RS 485 A/A signal or Rx-/Tx- 2 in. (5 cm) max 0.28 in. (7 mm) Shield 0.8 in. (2 cm) max in. (7 mm) V Black 0 V of the power supply 24 V Red 24 Vdc power supply 2 in. (5 cm) max 0.28 in. (7 mm) 0.28 in. (7 mm) in. (50 mm) 0.79 in. (20 mm) 24 0 D0 D1 1 To prevent electromagnetic disturbance, minimize the unshielded length of the Modbus cable. NOTE: No more than two wires can connect inside the same pin of the Modbus Interface Module connector. 6-EN 2011 Schneider Electric All Rights Reserved

9 Modbus Communication User Guide 06/2011 Section 1 Modbus Communication Modbus Address Switches The Modbus Interface Module bears the Modbus address of the IMU (Intelligent Modular Unit) to which it connects. See the ULP System User Guide for more information about the intelligent modular unit. The user defines the Modbus address using the two address switches on the front panel of the Modbus on interface module. The address range is Value 0 is reserved for broadcasting commands. The Modbus Interface Module is initially configured with address 99. ENGLISH Figure 2: Example of Rotary Switch Address Address configuration for Address 21 2x10 + 1x1 = 21 Modbus Traffic LED Modbus Locking Pad The Modbus traffic yellow LED indicates the circuit breaker is transmitting or receiving data over the Modbus network. When the Modbus address switches are on value 0, the LED is steady ON. When the Modbus address switches are from 1 to 99, the LED is ON during the transmission and reception of messages, OFF otherwise. The Modbus locking pad on the front panel of the Modbus Interface Module enables or disables sending remote control commands over the Modbus network to the Modbus Interface Module or other modules (BSCM or Micrologic trip unit). Figure 3: Modbus Locking Remote control commands enabled Remote control commands disabled If the arrow points to the open padlock, remote control commands are enabled. If the arrow points to the closed padlock, remote control commands are disabled. The only remote control commands that are enabled when the arrow points to the closed padlock are the set absolute time and get current time commands. See Set Absolute Time on page 80. For the other cases, the only way to modify parameters such as the protection settings is through the Micrologic trip unit front panel or with the RSU software using the UTA tester connected to the Micrologic trip unit test plug Schneider Electric All Rights Reserved 7-EN

10 Modbus Communication User Guide Section 1 Modbus Communication 06/2011 ENGLISH Test Button The test button tests the connection between all the modules connected to the Modbus Interface Module: Micrologic trip unit, front display module FDM121, and the UTA tester. Pressing the test button launches the connection test for 15 seconds. During the test, all the modules keep working normally. Test LED The yellow test LED indicates the connection between the modules that connect to the Modbus Interface Module. Table 2: Test LED Status Test LED Status ON: 50 ms / OFF: 950 ms ON: 250 ms / OFF: 250 ms ON: 500 ms / OFF: 500 ms ON: 1000 ms / OFF: 1000 ms Always ON Always OFF Signification Nominal mode (no test running) ULP module address conflict: two identical ULP modules are in the same intelligent modular unit. Degraded mode (EEPROM is out of service) Test mode Always ON ULP connection is out of service Always OFF No power supply ULP connection is out of service No power supply Schematics Depending on the configuration of the PowerPact H-, J- or L-frame circuit breaker, connect the Modbus Interface Module to the circuit breaker using one of the following configurations: connection of the Modbus Interface Module to the Micrologic trip unit connection of the Modbus Interface Module to the BSCM (Breaker Status Control Module) connection of the Modbus Interface Module to both the BSCM and the Micrologic trip unit All connection configurations require the NSX Cord. See the PowerPact H-, J-, or L-Frame Circuit Breaker User Guide for more information regarding the description and mounting of circuit breaker products (Micrologic trip unit, BSCM, and NSX Cord). 8-EN 2011 Schneider Electric All Rights Reserved

11 Modbus Communication User Guide 06/2011 Section 1 Modbus Communication Figure 4: Connection of the Modbus Interface Module to the Micrologic Trip Unit or BSCM Connection of the Modbus Interface Module to the Micrologic Trip Unit using the NSX Cord: Modbus 24 V Connection of the Modbus Interface Module to the BSCM using the NSX Cord Modbus 24 V ENGLISH NSX Cord NSX Cord 2011 Schneider Electric All Rights Reserved 9-EN

12 Modbus Communication User Guide Section 1 Modbus Communication 06/2011 Figure 5: Connection of Modbus Interface Module to BSCM and Micrologic Trip Unit ENGLISH Connection of the Modbus Interface Module to the BSCM and the Micrologic Trip Unit using the NSX Cord Modbus Connection of the Modbus Interface Module to the BSCM and the Micrologic Trip Unit using the NSX Cord > 480 Vac (with Isolation Module) Modbus 24 V NSX Cord 24 V Isolation Module NSX Cord > 480 Vac 10-EN 2011 Schneider Electric All Rights Reserved

13 Modbus Communication User Guide 06/2011 Section 1 Modbus Communication Configuration of the Modbus Interface Module Two configurations of the Modbus Interface Module are available: automatic configuration (Auto-Speed sensing ON); when connected to the Modbus network, the Modbus Interface Module automatically detects the network parameters (default configuration). personalized configuration (Auto-Speed sensing OFF); the user can personalize the network parameters using the RSU (Remote Setting Utility) software. ENGLISH Automatic Configuration Personalized Configuration The user defines the Modbus slave address using the two address switches on the front panel of the Modbus Interface Module. When connected to the Modbus network, the Modbus Interface Module automatically detects the network speed and parity. The Auto-Speed sensing algorithm tests the available baudrates and parities and automatically detects the network parameters. The Modbus master must send at least 15 frames on the Modbus network so that the auto-speed sensing algorithm works. The transmission format is: binary with one start bit eight data bits one stop bit in case of even or odd parity two stop bits in case of no parity. NOTE: If there are problems with the Auto-Speed sensing algorithm: 1. Set up the Modbus Interface Module to Modbus address 1 (see Modbus Address Switches on page 7), 2. Send a Read Multiple Register (FC03) request to slave 1, at any address and for any number of registers, 3. Send this request at least 15 times. The user defines the Modbus slave address using the two address switches on the front panel of the Modbus Interface Module. The user personalizes the network parameters with the RSU software. The following figure shows the Modbus Interface Module configuration tab with RSU: 2011 Schneider Electric All Rights Reserved 11-EN

14 Modbus Communication User Guide Section 1 Modbus Communication 06/2011 ENGLISH When the Auto-Speed sensing option is disabled, the user selects the network baud rate and parity: The supported baud rates are: 4800, 9600, 19200, and bauds. The supported parities are: even, odd, and none. NOTE: It is not possible to change the Modbus address or the status of the locking pad with RSU. The RSU software is available at See the RSU Online Help for more information about the Modbus Interface Module with RSU. 12-EN 2011 Schneider Electric All Rights Reserved

15 > 3 0 > > 3 0 A % Ir Ir (x Io ) I s d(x Ir) Modbus Communication User Guide 06/2011 Section 2 Modbus Protocol Section 2 Modbus Protocol Modbus Master-Slave Principle The Modbus protocol exchanges information using a request-reply mechanism between a master (client) and a slave (server). The masterslave principle is a communication protocol in which one device (the master) controls one or more other devices (the slaves). In a standard Modbus network, there is one master and up to 31 slaves. ENGLISH A detailed description of the Modbus protocol is available at Characteristics of the Master-Slave Principle Master-Slave Communication Mode In a master-slave setup: Only one master can connect to the network at a time. Only the master can initiate communication and send requests to the slaves. The master can address each slave individually using its specific address or all slaves simultaneously using address 0. The slaves can only send replies to the master. The slaves cannot initiate communication, either to the master or to other slaves. The Modbus protocol can exchange information using two communication modes: request-reply mode broadcast mode Request-Reply Mode In request-reply mode, the master addresses a slave using the specific address of the slave. The slave processes the request then replies to the master. Figure 6: Request-Reply Mode o E M ic r c M o c E lo ic r g lo i g i.2 5 > 3 0 > > 3 0 A % Ir Ir (x Io ) I s d(x Ir) 6 8 o E M ic r c lo g i.2 5 > 3 0 > > 3 0 A % Ir Ir (x Io ) I s d(x Ir) 6 8 o E M ic r c lo g i > 3 0 > > 3 0 A % Ir Ir (x Io ) I s d(x Ir) Request 2. Process 3. Reply Master Slave 1 Slave 2 Slave 3 Slave Schneider Electric All Rights Reserved 13-EN

16 > 3 0 A 3 0 % Ir > Ir (x Io ) I s d(x Ir) 8 6 Modbus Communication User Guide Section 2 Modbus Protocol 06/2011 ENGLISH Broadcast Mode The master can address all slaves using address 0. This type of exchange is called broadcasting. The slaves do not reply to broadcasting messages. Figure 7: Broadcast Mode M ic o r c E lo g i.2 5 > 3 0 A 3 0 % Ir > Ir (x Io ) I s d(x Ir) 8 6 > 0 M ic o r c E lo g i.2 5 > 3 0 A 3 0 % Ir > Ir (x Io ) I s d(x Ir) 8 6 > 0 M ic o r c E lo g i.2 5 > 3 0 A 3 0 % Ir > Ir (x Io ) I s d(x Ir) 8 6 > 0 M ic o r c E lo g i.2 5 Master > 0 Slave 1 Slave 2 Slave 3 Slave 4 Response Time The response time Tr is the time needed by a slave to respond to a request sent by the master: request broadcasting request Tr reply Tr Values with the Modbus protocol: typical value < 10 ms for 90% of the exchanges maximum value ~700 ms A one second timeout after receiving a Modbus request is recommended. Data Exchange The Modbus protocol uses two types of data: bits 16-bit words called registers Each register has a register number. Each type of data (bit or register) has a 16-bit address. The messages exchanged with the Modbus protocol contain the address of the data to be processed. Registers and Addresses The address of register number n is n-1. For example, the address of register number is To avoid confusion, the tables in this manual give both register numbers and corresponding addresses. 14-EN 2011 Schneider Electric All Rights Reserved

17 Modbus Communication User Guide 06/2011 Section 2 Modbus Protocol Frames All the frames exchanged with the Modbus protocol have a maximum size of 256 bytes and are composed of four fields. Table 3: Frames Field Definition Size Description Destination of the request 1 Slave number 1 byte 0: broadcasting (all slaves concerned) 1 247: unique destination 2 Function code 1 byte See next paragraph Request or reply data 3 Data or subfunction code n bytes Subfunction code 4 Check 2 bytes CRC16 (to check transmission errors) ENGLISH Modbus Functions The Modbus protocol offers a number of functions to read or write data over the Modbus network. The Modbus protocol also offers diagnostic and network-management functions. Only the Modbus functions handled by the PowerPact H-, J-, or L-frame circuit breaker are described here. Read Functions Table 4: Available Read Functions Function Code Subfunction Code Name Description 3 Read holding registers Read n output or internal words. 4 Read input registers Read n input words Read device identification Read slave identification data. Read register example Table 5 shows how to read the rms current on phase A (I A ) in register The address of register 1016 is = 1015 =0x03F7. The Modbus address of the Modbus slave is 47 = 0x2F. Table 5: Reading the RMS Current Master Request Slave Reply Field Name Example (hexadecimal) Field Name Modbus slave address 0x2F Modbus slave address 0x2F Function code 0x03 Function code 0x03 Address of the word to read (MSB) 0x03 Data length in bytes 0x02 Address of the word to read (LSB) 0xF7 Register value (MSB) 0x02 Number of registers (MSB) 0x00 Register value (LSB) 0x2B Number of registers (LSB) 0x01 CRC MSB 0xXX CRC MSB 0xXX CRC LSB 0xXX CRC LSB 0xXX Example (hexadecimal) The content of register 1016 (address 1015) is 0x022B = 555. Therefore the rms current on phase A (I A ) is 555 A Schneider Electric All Rights Reserved 15-EN

18 Modbus Communication User Guide Section 2 Modbus Protocol 06/2011 Read device identification example ENGLISH The Read Device Identification function provides standardized access to the information required to identify a device. The description consists of a set of objects (ASCII character strings). A complete description of the Read Device Identification function is available at The coding for the identification of the Modbus Interface Module is the following: Table 6: Read Device Identification Name Type Description Vendor name STRING Schneider Electric (18 characters) Product code STRING TRV00210 Firmware version STRING VX.Y.Z (at least six characters) Vendor URL STRING (26 characters) Product name STRING ULP/Modbus Interface Module Scattered Holding Register Read Function The scattered holding register read function allows the user to: avoid reading a large block of contiguous words when only few words are needed avoid multiple use of functions 3 and 4 to read noncontiguous words Table 7: Scattered Holding Register Function Code Subfunction Code Name Description Read scattered holding register Read n noncontiguous words The maximum value for n is 100. Example Table 8 shows how to read addresses 101 = 0x65 and 103 = 0x67 of a Modbus slave. The Modbus address of the Modbus slave is 47 = 0x2F. Table 8: Reading Address of a Modbus Slave Master Request Slave Reply Field Name Example (hexadecimal) Field Name Example (hexadecimal) Modbus slave address 0x2F Modbus slave address 0x2F Function code 0x64 Function code 0x64 Data length in bytes 0x06 Data length in bytes 0x06 Subfunction code 0x04 Subfunction code 0x04 Transmission number 1 0xXX Transmission number 1 0xXX Address of first word to read (MSB) 0x00 First word read (MSB) 0x12 Address of first word to read (LSB) 0x65 First word read (LSB) 0x0A Address of second word to read (MSB) 0x00 Second word read (MSB) 0x74 Address of second word to read (LSB) 0x67 Second word read (LSB) 0x0C CRC MSB 0xXX CRC MSB 0xXX CRC LSB 0xXX CRC LSB 0xXX 1 The master gives the transmission number in the request. The slave returns the same number in the reply. 16-EN 2011 Schneider Electric All Rights Reserved

19 Modbus Communication User Guide 06/2011 Section 2 Modbus Protocol Write Functions Table 9: Available Write Functions Function Code Subfunction Code Name Description 6 Preset single register Write one word 16 Preset multiple registers Write n words ENGLISH Diagnostic Functions Table 10: Available Diagnostic Functions Function Code Subfunction Code Name Description 8 Diagnostic Manage diagnostic counters Clear counters and diagnostic register Return bus message counter Return bus communication error counter Return bus exception error counter Return slave message counter Return slave no response counter Return slave negative acknowledge counter 8 17 Return slave busy counter 8 18 Return bus overrun counter 11 Get communication event counter Reset all diagnostic counters Read the counter of correct bus messages managed by the slave Read the counter of incorrect bus messages managed by the slave Read the counter of exception responses managed by the slave Read the counter of messages sent to the slave Read the counter of broadcast messages Read the counter of messages sent to the slave but not answered because of a Negative Acknowledge exception code 07 Read the counter of messages sent to the slave but not answered because of a Slave Device Busy exception code 06 Read the counter of incorrect bus messages due to overrun errors Read Modbus event counter 2011 Schneider Electric All Rights Reserved 17-EN

20 Modbus Communication User Guide Section 2 Modbus Protocol 06/2011 ENGLISH Diagnostic Counters Modbus uses diagnostic counters for performance and error management. The counters are accessible using the Modbus diagnostic functions (function codes 8 and 11). See Table 11 for descriptions of the Modbus diagnostic counters and the Modbus event counter: Table 11: Counter Number Available Diagnostic Counters Counter Name 1 Bus message counter 2 3 Bus communication error counter Slave exception error counter Description Counter of correct bus messages managed by the slave Counter of incorrect bus messages managed by the slave Counter of exception responses managed by the slave and incorrect broadcast messages 4 Slave message counter Counter of messages sent to the slave 5 Slave no response counter Counter of broadcast messages 6 Slave negative acknowledge counter 7 Slave busy count 8 Bus character overrun counter 9 Comm. event counter Counter of messages sent to the slave but not answered because of a Negative Acknowledge exception code 07 Counter of messages sent to the slave but not answered because of a Slave Device Busy exception code 06 Counter of incorrect bus messages due to overrun errors Modbus event counter (this counter is read with function code 11) Counters Reset The counters are reset to 0 when they reach the maximum value 65535, when they are reset by a Modbus command (function code 8, subfunction code 10), when power supply is lost, or when communication parameters are modified. Modbus Exception Codes Exception Responses Exception responses from either the master (client) or a slave (server) can result from data processing errors. One of the following events can occur after a request from the master (client): If the slave (server) receives the request from the master (client) without a communication error and can handle the request correctly, it returns a normal response. If the slave (server) does not receive the request from the master (client) due to a communication error, it does not return a response. The master program eventually processes a timeout condition for the request. If the slave (server) receives the request from the master (client) but detects a communication error, it does not return a response. The master program eventually processes a timeout condition for the request. If the slave (server) receives the request from the master (client) without a communication error, but cannot handle it (for example, the request is to read a register that does not exist), the server returns an exception response to inform the master of the nature of the error. 18-EN 2011 Schneider Electric All Rights Reserved

21 Modbus Communication User Guide 06/2011 Section 2 Modbus Protocol Exception Frame The slave sends an exception frame to the master to report an exception response. An exception frame is composed of four fields. Table 12: Exception Frames Field Definition Size Description 1 Slave number 1 byte Destination of the request 0: broadcasting (all slaves concerned) 1 247: unique destination 2 Exception function code 1 byte Request function code (0x80) 3 Exception code n bytes see next paragraph 4 Check 2 bytes CRC16 (to check transmission errors) ENGLISH Exception Codes The exception response frame has two fields that differentiate it from a normal response frame: The exception function code of the exception response is equal to the function code of the original request plus 128 (0x80). The exception code depends on the communication error that the slave encounters. The following table describes the exception codes handled by the PowerPact H-, J-, or L-frame circuit breaker: Table 13: Exception Code Exception Codes Name Description 01 Illegal function 02 Illegal data address 03 Illegal data value 04 Slave device failure 05 Acknowledge 06 Slave device busy 07 Negative acknowledgment 08 Memory parity error Gateway path unavailable Gateway target device failed to respond The function code received in the request is not an authorized action for the slave. The slave may be in the wrong state to process a specific request. The data address received by the slave is not an authorized address for the slave. The value in the request data field is not an authorized value for the slave. The slave fails to perform a requested action because of an unrecoverable error. The slave accepts the request but needs a long time to process it. The slave is busy processing another command. The master must send the request once the slave is free. The slave cannot perform the programming request sent by the master. The slave detects a parity error in the memory when attending to read extended memory. The gateway is overloaded or not correctly configured. The slave is not present on the network Schneider Electric All Rights Reserved 19-EN

22 Modbus Communication User Guide Section 2 Modbus Protocol 06/2011 ENGLISH Write Protection CAUTION HAZARD OF NUISANCE TRIPPING OR FAILURE TO TRIP Adjusting protection settings must be done only by trained electrical personnel. Remote modifications of Modbus registers that alter protection settings can be hazardous to personnel near the circuit breaker or can cause equipment damage. Therefore, remote control commands are hardware and software protected. Failure to follow these instructions can result in injury or equipment damage. Hardware Protection The Modbus locking pad on the front panel of the Modbus Interface Module enables or disables remote control commands to be sent over the Modbus network to the Modbus Interface Module itself, and to the other modules (BSCM or Micrologic trip unit). Figure 8: Modbus Locking Remote control commands enabled Remote control commands disabled If the arrow points to the open padlock, remote control commands are enabled. If the arrow points to the closed padlock, remote control commands are disabled. The only remote control commands that are enabled even if the arrow points to the closed padlock are the set absolute time and get current time commands. See Set Absolute Time on page 80. For the other cases, the only way to modify parameters such as the protection settings is through the Micrologic trip unit front panel or with the RSU software using the UTA tester connected to the Micrologic trip unit test plug. Software Protection Password Management To prevent inadvertently changing the trip unit configuration, remote modifications of the Modbus registers are protected by: a robust data structure and a set of dedicated Modbus registers a multi-level password scheme This combination is called the command interface. Failure to conform to the command interface results in an error code and the operation is not performed. The hardware protection always has precedence over the software protection. Four passwords are defined, each corresponding to a level. A level is assigned to a role: Levels 1, 2, and 3 are used for general-purpose roles, such as an operator role. Level 4 is the administrator level. The administrator level is required to write the settings to the Micrologic trip units using RSU. 20-EN 2011 Schneider Electric All Rights Reserved