Programmer’s manual RVT-D Modbus data table · 2018-05-10 · The Modbus protocol establishes the format for the master’s query by placing into it the device (or broadcast) address,

Programmer’s manual

RVT-D Modbus data table

1

Table of contents

1 INTRODUCTION............................................................................................................... 4 1.1 Intended audience .................................................................................................................................4 1.2 Before you start .....................................................................................................................................4 1.3 How to use this manual .........................................................................................................................4

2 MODBUS PROTOCOL OVERVIEW................................................................................. 4 2.1 Overview................................................................................................................................................4 2.2 Transactions on Modbus Networks .......................................................................................................4 2.3 Serial Transmission Mode .....................................................................................................................5 2.4 Modbus Message Framing ....................................................................................................................6

3 MODBUS FUNCTION CODES ......................................................................................... 7 3.1 Data Addresses in Modbus Messages..................................................................................................7 3.2 Supported function codes......................................................................................................................7 3.3 Master’s queries and Slave’s responses...............................................................................................8 3.4 Reads and writes to Modbus addresses (functions 1,2,3,4,5,6,15,16,22,23) .......................................8 3.5 Fetch comm event counter (function 11)...............................................................................................9 3.6 Fetch comm event log (function 12) ....................................................................................................10 3.7 Diagnostics function and subfunctions (function 8) .............................................................................11 3.8 Exception responses ...........................................................................................................................12

4 DATA ACCESS .............................................................................................................. 13 4.1 Formats................................................................................................................................................13 4.2 Access levels .......................................................................................................................................14 4.3 Minimum and maximum values ...........................................................................................................15 4.4 Modbus Data table...............................................................................................................................15

5 MEASUREMENTS.......................................................................................................... 16 5.1 Main measurements ............................................................................................................................16 5.2 Event logging .......................................................................................................................................18 5.3 Output relays operation .......................................................................................................................20 5.4 Alarm logging.......................................................................................................................................22 5.5 Nodes overview ...................................................................................................................................24 5.6 Outputs / Inputs ...................................................................................................................................25 5.7 Harmonic voltage spectrum.................................................................................................................27 5.8 Spectrum analysis of the current .........................................................................................................29 5.9 Clock reference....................................................................................................................................31

6 SETTINGS ...................................................................................................................... 32 6.1 Bank settings .......................................................................................................................................32 6.2 Protections...........................................................................................................................................36 6.3 Event logging settings .........................................................................................................................37 6.4 Installation settings ..............................................................................................................................38 6.5 User settings........................................................................................................................................41 6.6 I/O configuration ..................................................................................................................................41 6.7 Change Mode (AUTO-MAN-SET) .......................................................................................................43 6.8 CAN Configuration...............................................................................................................................45 6.9 User data storage ................................................................................................................................46 6.10 RVT-D manufacturer information.........................................................................................................47

7 OUTPUT & INPUT BITS ................................................................................................. 49 7.1 Output bits ...........................................................................................................................................49 7.2 Input bits ..............................................................................................................................................50

8 DEVICE SPECIFIC MODBUS FUNCTIONS................................................................... 51 8.1 Read Exception Status (function 7) .....................................................................................................51

2

8.2 Report Slave ID (function 17) ..............................................................................................................51

9 CRC GENERATION........................................................................................................ 53

10 APPENDIX ...................................................................................................................... 54 10.1 List of abbreviations.............................................................................................................................54 10.2 References ..........................................................................................................................................55

3

1 INTRODUCTION

1.1 Intended audience

This manual is intended for programmers, commissioning people, supervision people who need to start communication, access data, and to develop supervision software which will interact with the PowerIT LV Power Factor Controller RVT-D.

1.2 Before you start

This manual describes the RVT-D Modbus data table. All information available from the keyboard of the RVT-D will be available through the Modbus data table. Addresses, access levels and storage types information are of concerns. To be able to access data of the PowerIT Power Factor controller RVT-D consistently, a basic knowledge of it is needed. Functionality of the RVT-D, meaning of various measurements, logging of data are some particular aspects that should be familiar. Look in the RVT-D operating manual to know more about it.

1.3 How to use this manual

Chapter 2 gives details concerning the Modbus protocol. Chapter 3 describes Modbus functions and how Modbus is implemented in the controller. Chapter 4 contains the formats and access rights information to exchange data. Chapter 5 contains the table reference and formats to access measurement data. Chapter 6 contains the table reference and formats to access setting datas. Chapter 7 contains the table reference for bit reads & writes. Chapter 8 describes device specific Modbus functions. Chapter 9 give a way to calculate the Cyclical Redundancy Check (CRC) Chapter 10 is dedicated to annexes.

2 MODBUS PROTOCOL OVERVIEW

2.1 Overview

MODBUS RTU is a non-proprietary serial communications protocol that is widely used in the process control industry. The protocol was developed by Modicon for PLC communications and later released for public use. This protocol is available in all major Human Machine Interface (HMI) software packages and terminals. Many of the major controller and PLC manufacturers also offer MODBUS protocol as a standard or optional protocol in their instrumentation. The hardware over which MODBUS RTU communications are performed is not defined by the protocol. MODBUS RTU is supported on RS-232, RS-422, RS-485, Ethernet and other electrical standards. It should be noted that MODBUS RTU, MODBUS ASCII and MODBUS Plus are unique communication formats, and are not compatible with each other. This document will discuss MODBUS RTU only.

2.2 Transactions on Modbus Networks

Modbus protocol uses a master–slave technique, in which only one device (the master) can initiate transactions (called ‘queries’). The other devices (the slaves) respond by supplying the requested data to the master, or by taking the action requested in the query. Typical master devices include host processors and programming panels. Typical slaves include programmable controllers. The master can address individual slaves, or can initiate a broadcast message to all slaves. Slaves return a message (called a ‘response’) to queries that are addressed to them individually. Responses are not returned to broadcast queries from the master.

4

The Modbus protocol establishes the format for the master’s query by placing into it the device (or broadcast) address, a function code defining the requested action, any data to be sent, and an error–checking field. The slave’s response message is also constructed using Modbus protocol. It contains fields confirming the action taken, any data to be returned, and an error–checking field. If an error occurred in receipt of the message, or if the slave is unable to perform the requested action, the slave will construct an error message and send it as its response.

The Query: The function code in the query tells the addressed slave device what kind of action to perform. The data bytes contain any additional information that the slave will need to perform the function. The data field must contain the information telling the slave which register to start at and how many registers to read. The error check field provides a method for the slave to validate the integrity of the message contents. The Response: If the slave makes a normal response, the function code in the response is an echo of the function code in the query. The data bytes contain the data collected by the slave, such as register values or status. If an error occurs, the function code is modified to indicate that the response is an error response, and the data bytes contain a code that describes the error. The error check field allows the master to confirm that the message contents are valid.

2.3 Serial Transmission Mode

The transmission mode defines the bit contents of message fields transmitted serially on the networks. It determines how information will be packed into the message fields and decoded. Modbus defines two transmission modes: ASCII or RTU. Only RTU mode will be used here. The mode and serial parameters must be the same for all devices on a Modbus network. RTU Mode The main advantage of this mode is that its greater character density allows better data throughput than ASCII for the same baud rate. Each message must be transmitted in a continuous stream. The format for each byte in RTU mode is:

5

Bits per Byte: 1 start bit 8 data bits, least significant bit sent first 1 bit for even/odd parity; no bit for no parity 1 stop bit if parity is used; 2 bits if no parity Error Check Field: Cyclical Redundancy Check (CRC)

The messages are transmitted in the network from left to right, i.e. the Least Significant Bit (LSB) first and the Most Significant Bit (MSB) last.

2.4 Modbus Message Framing

A Modbus message is placed by the transmitting device into a frame that has a known beginning and ending point. This allows receiving devices to begin at the start of the message, read the address portion and determine which device is, and to know when the message is completed. Partial messages can be detected and errors can be set as a result. RTU Framing In RTU mode, messages start with a silent interval of at least 3.5 character times. This is most easily implemented as a multiple of character times at the baud rate that is being used on the network (shown as T1–T2–T3–T4 in the figure below). Another factor to consider is that each device has its own response time. This response time can be anywhere from a few milliseconds to a few hundred milliseconds. The Host must be configured to allow adequate time for the slowest device to respond.

The first field then transmitted is the device address. Networked devices monitor the network bus continuously, including during the ‘silent’ intervals. When the first field (the address field) is received, each device decodes it to find out if it is the addressed device. Following the last transmitted character, a similar interval of at least 3.5 character times marks the end of the message. A new message can begin after this interval. The entire message frame must be transmitted as a continuous stream. If a silent interval of more than 1.5 character times occurs before completion of the frame, the receiving device flushes the incomplete message and assumes that the next byte will be the address field of a new message. Similarly, if a new message begins earlier than 3.5 character times following a previous message, the receiving device will consider it a continuation of the previous message. This will set an error, as the value in the final CRC field will not be valid for the combined messages. A typical message frame is shown below.

6

For a complete description of the Modbus protocol, please look at the Modicon Modbus Protocol Reference Guide (PI–MBUS–300 Rev. J).

3 MODBUS FUNCTION CODES

3.1 Data Addresses in Modbus Messages

Modbus defines 4 address spaces: 2 address spaces for bit addressable data and 2 address spaces for 16 bits addressable data.

Address space Data Readable / writable Modbus name 0XXXX Output bit Read & write Coil Status 1XXXX Input bit Read Input Status 3XXXX Input word Read Input Register 4XXXX Output word Read & write Holding Register

Input register address space will be mainly used for measurements. Holding register address space will contain settings. All data addresses in Modbus messages are referenced to zero. For example: The coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in the data address field of a Modbus message. Coil 127 decimal is addressed as coil 007E hex (126 decimal). Holding register 40001 is addressed as register 0000 in the data address field of the message. The function code field already specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is implicit. Holding register 40108 is addressed as register 006B hex (107 decimal).

3.2 Supported function codes

The following table gives the Modbus functions which are implemented and supported. The code is the one used in function field of the Modbus message. The address space concerned and the purpose of the function are given below.

7

Code Function Address range / Remark

1 Read Coil Status 0XXXX Reads the on/off status of discrete outputs 2 Read Input Status 1XXXX Reads the on/off status of discrete inputs 3 Read Holding Registers 4XXXX Reads contents of output registers 4 Read Input Registers 3XXXX Reads contents of input registers 5 Force Single Coil 0XXXX Sets the status of a discrete output 6 Preset Single Register 4XXXX Sets the value of a holding register 7 Read Exception Status Device specific (see chapter 8) 8 Diagnostics Checks the communication system between the master

and the slave 11 Fetch Comm. Event Ctr. Returns the amount of successful read/write operations

on data points 12 Fetch Comm. Event Log Returns log registers of communication events 15 Force Multiple Coils 0XXXX Sets the status of multiple discrete outputs 16 Preset Multiple Registers 4XXXX Sets the value of multiple holding registers 17 Report Slave ID Device specific (see chapter 8) 22 Mask Write 4X registers 4XXXX And / Or write of a holding register 23 Read/Write 4X registers 4XXXX Reads a set of holding registers and writes a

set of holding registers in one query

Remark: please note that for security reasons broadcast is not supported by the RVT-D.

3.3 Master’s queries and Slave’s responses

When a master device sends a query to a slave device it expects a normal response. One of four possible events can occur from the master’s query: - If the slave device receives the query without a communication error, and can handle the query

normally, it returns a normal response. - If the slave does not receive the query due to a communication error, no response is returned. The

master program will eventually process a timeout condition for the query. - If the slave receives the query, but detects a communication error (parity or CRC), no response is

returned. The master program will eventually process a timeout condition for the query. - If the slave receives the query without a communication error, but cannot handle it (for example, if the

request is to read a non–existent coil or register), the slave will return an exception response informing the master of the nature of the error.

3.4 Reads and writes to Modbus addresses (functions 1,2,3,4,5,6,15,16,22,23)

The format of a read function (read coil status (01), read input status (02), read input registers (04), read holding registers (03)) is as follows:

QUERY Slave address 1 byte Function 1 byte Starting data address 2 bytes Quantity of points 2 bytes Error check field CRC 2 bytes

RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Byte count 1 byte Data values N bytes Error check field CRC 2 bytes

8

The format of a force single coil (05) or a preset single register (06) function is as follows:

The format of a force multiple coil (15) or a preset multiple registers (16) function is as follows:

The format of a read/write multiple registers (23) function is as follows:

The format of a Mask/write register (22) function is as follows:

QUERY Slave address 1 byte Function 1 byte Data address 2 bytes Data value 2 bytes Error check field CRC 2 bytes

RESPONSE Slave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Data address 2 bytes Data value 2 bytes Error check field CRC 2 bytes

QUERY Slave address 1 byte Function 1 byte Data address 2 bytes Quantity of points 2 bytes Byte count 1 byte Data values N bytes Error check field CRC 2 bytes

RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Data address 2 bytes Quantity of points 2 bytes Error check field CRC 2 bytes

QUERY Slave address 1 byte Function 1 byte Read data address 2 bytes Read quantity of points 2 bytes Write data address 2 bytes Write quantity of points 2 bytes Byte count 1 byte Write data values N bytes Error check field CRC 2 bytes

RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Byte count 1 byte Data values N bytes Error check field CRC 2 bytes

QUERY Slave address 1 byte Function 1 byte Data address 2 bytes And mask 2 bytes Or mask 2 bytes Error check field CRC 2 bytes

RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Data address 2 bytes And mask 2 bytes Or mask 2 bytes Error check field CRC 2 bytes

3.5 Fetch comm event counter (function 11)

The controller’s event counter is incremented once for each successful message completion. It is not incremented for exception responses, poll commands, or fetch event counter commands. It returns amount of successful read/write operations on data points. The format of a Fetch comm event counter (11) function query is as follows:

QUERY Slave address 1 byte Function 1 byte Error check field CRC 2 bytes

RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Status word 2 bytes (0) Event counter 2 bytes Error check field CRC 2 bytes

9

3.6 Fetch comm event log (function 12)

Returns a status word, the comm event counter (see function 11) , the bus message counter (see function 08 subfunction 11), and a field of event bytes from the slave.

The format of a Fetch comm event log (12) function query is as follows:


RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Byte count 1 byte Status word 2 bytes (0) Event counter 2 bytes Bus message counter 2 bytes Event log buffer N bytes Error check field CRC 2 bytes

The 64 bytes wide Event log buffer is filled with communication events. The most recent communications event is shown in the Event 0 byte. Event bytes are stored in the Even log buffer for 4 different reasons. The bit will be set to a logic ‘1’ if the corresponding condition is TRUE. Slave Modbus Receive Event This type of event byte is stored by the slave when a query message is received. It is stored before the slave processes the message. Bit Contents 0 Not Used 1 Communications Error 2 Not Used 3 Not Used 4 Character Overrun 5 Currently in Listen Only Mode 6 Broadcast Received 7 1 Slave Modbus Send Event This type of event byte is stored by the slave when it finishes processing a query message. It is stored if the slave returned a normal or exception response, or no response. Bit Contents 0 Read Exception Sent (Exception Codes 1-3) 1 Slave Abort Exception Sent (Exception Code 4) 2 Not used 3 Not used 4 Write Timeout Error Occurred 5 Currently in Listen Only Mode 6 1 7 0

Slave Entered Listen Only Mode This type of event byte is stored by the slave when it enters the Listen Only Mode. The event is defined by a content of ‘04’ hex.

10

Slave Initiated Communication Restart This type of event byte is stored by the slave when its communications port. Is restarted. The slave can be restarted by the Diagnostics function (code 08), with subfunction Restart Communications Option (code 01). The event is defined by a contents of ‘00’ hex.

3.7 Diagnostics function and subfunctions (function 8)

The format of a diagnostics (08) function query is as follows:

QUERY Slave address 1 byte Function 1 byte Subfunction 2 bytes Data field 2 bytes Error check field CRC 2 bytes

The format of a response to a diagnostics function query is an echo of the query itself. If the request is directed to a counter, however, the slave returns the counter’s value in the data field. 00 Return Query Data The data in the query data field is to be returned (looped back) in the response. The entire response should be identical to the query. 01 Restart Communication Option The slave’s peripheral port is to be initialized and restarted, and all of its communication event counters are to be cleared. If the port is currently in the Listen Only Mode, no response will be sent. If the port is not currently in the Listen Only Mode, a normal response will be sent. This occurs before the restart is executed. 02 Return Diagnostic Register (Not supported) 03 (Not supported) 04 Force Listen Only Mode Forces the addressed slave to enter the Listen Only Mode for Modbus communications. 10 Clear Counters and Diagnostic Register Clears all counters and the diagnostic register. 11 Return Bus Message Count The response data field returns the total quantity of messages that the slave has detected in the communications system since its last restart, clear counters operation, or power-up. 12 Return Bus Communication Error Count The response data field returns the quantity of CRC errors encountered by the slave since its last restart, clear counters operation, or power-up. 13 Return Bus Exception Error Count The response data field returns the quantity of Modbus exception responses returned by the slave since its last restart, clear counters operation, or power-up. 14 Return Slave Message Count The response data field returns the quantity of messages addressed to the slave, or broadcast that the slave has processed since its last restart, clear counters operation, or power-up.

11

15 Return Slave No Response Count The response data field returns the quantity of messages addressed to the slave for which it sent no response (neither a normal response nor an exception response) since its last restart, clear counters operation, or power-up. 16 Return Slave NACK Response Count (Not supported) 17 Return Slave Busy Response Count (Not supported) 18 Return Bus Character Overrun Count The response data field returns the quantity of messages addressed to the slave that it could not handle due to a character overrun condition since its last restart, clear counters operation, or power-up 19 (Not supported) 20 (Not supported) 21 (Not supported) Diagnostic counters

Bus Message Counter The total number of messages that the slave device has detected in

the communications system since its last restart, clear counters operation, or power-up.

Bus Communication Error Counter The number of CRC or LRC errors encountered by the slave device since its last restart, clear counters operation, or power-up.

Bus Exception Error Counter The number of Modbus exception responses sent by the slave device since its last restart, clear counters operation, or power-up.

Slave Message Counter The number of messages addressed to the slave device or broadcast that the slave device has processed since its last restart, clear counters operation, or power-up.

Slave No Response Counter The number of messages addressed to the slave device for which it sent no response (neither a normal response nor an exception response) since its last restart, clear counters operation, or power-up.

Bus Character Overrun Counter The number of messages addressed to the slave device that it could not handle due to a character overrun condition since its last restart, clear counters operation, or power-up .

3.8 Exception responses

Exception responses are sent when the slave device cannot handle the query. The format of an exception response to a master's query is as follows: 01 ILLEGAL FUNCTION The function code received in the query is not an allowable action for

the slave device (see paragraph 3.2). 02 ILLEGAL DATA ADDRESS The data address or number of items received in the query is not

allowable or correct for the slave device. The slave device will send this exception response if an attempt to read or write part of a multiple register database object is detected. Possible objects are time, strings and counters

03 ILLEGAL DATA VALUE A value contained in the query data field is out of range. The contents of the register or the status of the coil has not changed (see paragraph 4.3).

04 SLAVE DEVICE ABORT An unrecoverable error occurred while the slave was attempting to perform the requested action. This may happen when the access level for changing a parameter is not reached (see paragraph 4.2) .

05 ACKNOWLEDGE Not supported 06 SLAVE DEVICE BUSY Not supported 07 NEGATIVE ACKNOWLEDGE Not supported 08 MEMORY PARITY ERROR Not supported

12

An application program in the master is responsible for handling exception responses. Typical processes include successive attempts to send a query, sending diagnostic messages to the slave, and notifying the operators.

4 DATA ACCESS

4.1 Formats

Various formats are used depending on the type of data and the number bits used. BITS 0 or 1. Used in the address range 0XXXX to 1XXXX. SIGNED CHAR Signed chars are 8 bit values. These values vary in the range -128 to +127 although some registers have a limited range of acceptable values. The most significant bit defines the sign, zero indicating positives. Signed chars are converted to signed integers and transmitted as two 8 bit bytes for protocol compatibility. The variable is expressed as “cName”. Non volatile write accessible variable are expressed as “cNVName”. UNSIGNED CHAR Unsigned chars are 8 bit values. These values vary in the range 0 to 255 although some registers have a limited range of acceptable values. Unsigned chars are converted to unsigned integers and transmitted as two 8 bit bytes for protocol compatibility. The variable is expressed as “bName”. Non volatile write accessible variable are expressed as “bNVName”. SIGNED INTEGER Signed Integers are 16 bit values transmitted as two 8-bit bytes. The most significant byte is always transmitted first. These values vary in the range -32768 to +32767 although some registers have a limited range of acceptable values. The most significant bit defines the sign, zero indicating positives. The variable is expressed as “iName”. Non volatile write accessible variable are expressed as “iNVName”.

UNSIGNED INTEGER Unsigned Integers are 16 bit values transmitted as two 8-bit bytes. The most significant byte is always transmitted first. These values vary in the range 0 to 65535 although some registers have a limited range of acceptable values. The variable is expressed as “wName”. Non volatile write accessible variable are expressed as “wNVName”. SIGNED LONG INTEGERS (Signed Long) Signed long integers are 32 bit values transmitted as four 8-bit bytes. These values vary in the range -2147483648 to 2147483647 although some registers have a limited range. The most significant bit defines the sign, zero indicating positives. The variable is expressed as “IName”. Non volatile write accessible variable are expressed as “INVName”. UNSIGNED LONG INTEGERS (Unsigned Long) Unsigned long integers are 32 bit values transmitted as four 8-bit bytes. These values vary in the range 0 to 4294967295 although some registers have a limited range. The variable is expressed as “dwName”. Non volatile write accessible variable are expressed as “dwNVName”. SINGLE-PRECISION IEEE FLOAT NUMBERS These numbers implement the IEEE-754 standard for binary floating point arithmetic (32 bits). The format is described below:

13

|-------WORD 2-------|-------WORD1-------| 31.30....23.22.....16|15.................0 |s | 8 bits 23 bits mantissa |s | e7---e0 m22---------------------m0 ---------mantissa--------- |-Exponent |--| Sign bit

s : 1 sign bit; explains the sign (0 = positive, 1 = negative) e : 8 bits two’s complement exponent. The true value is the exponent minus 127. m : 23 bits . The “most significant bit” of the normalized mantissa before the decimal point is

implicitly 1, but is not stored. The value range is also between 1.0 (included) and 2.0 (excluded).

The value may be computed using 12702122 2)....1()1( −− es mmm

IEEE float numbers (4-byte IEEE format) are transmitted in two subsequent 16-bit registers. Both registers must always transmit a 32-bit value in sequence to get the consistency of the display. When writing to an IEEE float number, both registers must be sent in sequence. The variable is expressed as “ndName” or fName”. Non volatile write accessible variable are expressed as “ndNVName” or “fNVName”. Rem: The floating point format used in the internal memory of the controller is not the IEEE format described above. The mantissa is coded internally on 16 bits in place of 23 loosing some non significant bits. Consequently, the 7 least significant bits are lost, which may give slightly different values.

4.2 Access levels

The access levels of the Modbus writings are identical to the access levels in the RVT-D. SET MODE: the RVT-D must be in Set Mode to allow parameters settings modifications. LOCKING SWITCH: the locking switch has to be released. BANK SETTINGS: the parameter bank settings must be set to Unlocked. The parameter MODBUS LOCK is used to add an access level to Modbus users. When locked, all parameter settings modifications (except the Modbus lock item setting) from the RVT-D keyboard are forbidden. Parameters may meanwhile be modified by Modbus access only (provided all others access levels are fulfilled).

Variable Locked Unlocked bNVMode 1: AUTO

2: MAN 4: SET

bKeyboard (bit 7) 0: Lock switch pushed 1: Lock switch released bNVBanklocked 1: Bank settings are locked 0: Bank settings are unlocked bNVModbusLocking 1: Keyboard locked 0: Keyboard unlocked Comment 1: The following access level could be modified through Modbus or through the RVT-D keyboard: • Mode • Bank settings • Modbus lock But when the RVT-D is locked by the locking switch, the access cannot be modified through Modbus or through RVT-D keyboard. It can only be modified physically by pressing the locking switch located at the RVT-D backside. Comment 2: The RVT-D returns automatically to AUTO mode when no key is pressed or no writing are done through Modbus for more than five minutes.

14

4.3 Minimum and maximum values

Parameters settings values have a limited range. If a written value exceeds the minimum and maximum allowable values, the written value will be overridden with this minimum or maximum value. An ILLEGAL DATA VALUE exception error will be sent back. Please refer to the Modbus data table for more details.

4.4 Modbus Data table

Data are sorted in several tables for more convenience. Some of these tables could include redundant information. Table data may be read only or read/write access. Data in each table is pointed to in a Modbus command by two consecutive data address bytes. The first byte defines the table number, and the second byte the offset of the data in the table. These two bytes are called either the ‘Modbus address’ or the ‘Modbus register’ A specific Modbus data table is dedicated to a specific product type. Access (read or write) to a non referenced Modbus address result in an ILLEGAL DATA ADDRESS exception error.

The table is structured as follows: 1/ Description - General description

- Specific description 2/ Variable - Variable description

- Variable name 3/ Modbus register - Modbus address

- Table number - Offset

4/ Access - Set Mode (SET column) (a cross in this column means that the RVT must be in Set mode to allow a modification of the parameter) - Locking Switch (LS column) (a cross in this column means that the RVT locking switch must be released to allow a modification of this parameter.) - Bank settings (BL column) (a cross in this column means that the Bank settings item must be set as ‘Unlocked’ to allow a modification of this parameter).

5/ Data storage - RAM: (R column) Value is stored into RAM and can be modified. - Non volatile: (NV column) Value is stored into Non volatile memory and can be modified but a maximum of 1000000 number of write cycle must not be exceeded. - Constant: (C column) Value is stored into ROM (can not be modified)

6/ Units - Type 7/ Data type - Format The Modbus Data table gives all information on the various data and how to access them.

15

5 MEASUREMENTS

5.1 Main measurements This table contains measurements done by the RVT-D except harmonics spectra that can be found in paragraph 5.7 and 5.8. Most of these measurements are converted to IEEE float number for easy handling

Description Variable Variable name Modbus Units Datatyperegister Table number offset

Measurements Vrms (rms voltage) ndUrms 30001 00 01 VOLT FLOAT/lowndUrms 30002 00 02 VOLT FLOAT/high

THDV (voltage total harmonic distorsion) ndTHDU 30003 00 03 PERCENT FLOAT/lowndTHDU 30004 00 04 PERCENT FLOAT/high

F (Frequency) ndFrequency 30005 00 05 HERTZ FLOAT/lowndFrequency 30006 00 06 HERTZ FLOAT/high

Fundamental voltage ndU1 30007 00 07 VOLT FLOAT/lowndU1 30008 00 08 VOLT FLOAT/high

Irms (rms current) ndIrms 30009 00 09 AMPERE FLOAT/lowndIrms 30010 00 10 AMPERE FLOAT/high

THDI (current total harmonic distorsion) ndTHDI 30011 00 11 PERCENT FLOAT/lowndTHDI 30012 00 12 PERCENT FLOAT/high

Fundamental current ndI1 30013 00 13 AMPERE FLOAT/lowndI1 30014 00 14 AMPERE FLOAT/high

I1-cap (fundamental capacitor current) ndISinPhi 30015 00 15 AMPERE FLOAT/lowndISinPhi 30016 00 16 AMPERE FLOAT/high

cos phi (displacement power factor) ndCosPhi 30017 00 17 see Note (1) FLOAT/lowndCosPhi 30018 00 18 see Note (1) FLOAT/high

PF (Power factor) ndPF 30019 00 19 see Note (1) FLOAT/lowndPF 30020 00 20 see Note (1) FLOAT/high

P (active power) ndP 30021 00 21 WATT FLOAT/lowndP 30022 00 22 WATT FLOAT/high

Q (reactive power) ndQ 30023 00 23 VAR FLOAT/lowndQ 30024 00 24 VAR FLOAT/high

S (apparent power) ndS 30025 00 25 VA FLOAT/lowndS 30026 00 26 VA FLOAT/high

ΔQ (missing reactive power) ndQMiss 30027 00 27 VAR FLOAT/lowndQMiss 30028 00 28 VAR FLOAT/high

ΔN (missing steps) ndNMiss 30029 00 29 STEPS FLOAT/lowndNMiss 30030 00 30 STEPS FLOAT/high

T1 (temperature input 1) ndT[0] 30031 00 31 °C FLOAT/low

General measurements

General description

16

ndT[0] 30032 00 32 °C FLOAT/highT2 (temperature input 2) ndT[1] 30033 00 33 °C FLOAT/low

ndT[1] 30034 00 34 °C FLOAT/highpresence of T1 bTPresent[0] 30035 00 35 see Note (2) BYTEpresence of T2 bTPresent[1] 30036 00 36 see Note (2) BYTE

Note (1): Cos phi values are represented in a particular format shown in the following table:

Cos phi Value 0.1 ind 0.1 0.7 ind 0.7

1 1 0.7 cap 1.3 0.1 cap 1.9

Disabled 0 Positive values are for passive loads. Negative values represent regenerative mode. Note (2):

Temperature probe Value Temperature probe present 0 Temperature probe not connected 1

17

5.2 Event logging

This table contains recorded values by the RVT-D through the event logging function (for more information, please refer to the RVT-D Installation and Operating Instructions manual). Each duration is given in seconds.


Event Logging Peak / duration Urms peak ndNVUrmsPeak 30101 01 01 VOLT FLOAT/lowndNVUrmsPeak 30102 01 02 VOLT FLOAT/high

Accumulated peak Urms duration dwNVUrmsDuration 30103 01 03 SECOND unsigned LONG/lowdwNVUrmsDuration 30104 01 04 SECOND unsigned LONG/high

Irms peak ndNVIrmsPeak 30105 01 05 AMPERE FLOAT/lowndNVIrmsPeak 30106 01 06 AMPERE FLOAT/high

Accumulated peak Irms duration dwNVIrmsDuration 30107 01 07 SECOND unsigned LONG/lowdwNVIrmsDuration 30108 01 08 SECOND unsigned LONG/high

peak active power ndNVPPeak 30109 01 09 WATT FLOAT/lowndNVPPeak 30110 01 10 WATT FLOAT/high

Accumulated peak active power duration dwNVPDuration 30111 01 11 SECOND unsigned LONG/lowdwNVPDuration 30112 01 12 SECOND unsigned LONG/high

peak reactive power ndNVQPeak 30113 01 13 VAR FLOAT/lowndNVQPeak 30114 01 14 VAR FLOAT/high

Accumulated peak reactive power duration dwNVQDuration 30115 01 15 SECOND unsigned LONG/lowdwNVQDuration 30116 01 16 SECOND unsigned LONG/high

peak missing reactive power ndNVQMissPeak 30117 01 17 VAR FLOAT/lowndNVQMissPeak 30118 01 18 VAR FLOAT/high

Accumulated peak missing reactive power duration dwNVQMissDuration 30119 01 19 SECOND unsigned LONG/lowdwNVQMissDuration 30120 01 20 SECOND unsigned LONG/high

peak apparent power ndNVSPeak 30121 01 21 VA FLOAT/lowndNVSPeak 30122 01 22 VA FLOAT/high

Accumulated peak apparent power duration dwNVSDuration 30123 01 23 SECOND unsigned LONG/lowdwNVSDuration 30124 01 24 SECOND unsigned LONG/high

peak THDV ndNVTHDUPeak 30125 01 25 PERCENT FLOAT/lowndNVTHDUPeak 30126 01 26 PERCENT FLOAT/high

Accumulated peak THDV duration dwNVTHDUDuration 30127 01 27 SECOND unsigned LONG/lowdwNVTHDUDuration 30128 01 28 SECOND unsigned LONG/high

peak THDI ndNVTHDIPeak 30129 01 29 PERCENT FLOAT/lowndNVTHDIPeak 30130 01 30 PERCENT FLOAT/high

General description

18

Accumulated peak THDI duration dwNVTHDIDuration 30131 01 31 SECOND unsigned LONG/lowdwNVTHDIDuration 30132 01 32 SECOND unsigned LONG/high

Description Variable Variable name Modbus Units Datatype

register Table number offsetpeak frequency max ndNVFMax 30133 01 33 HERTZ FLOAT/low

ndNVFMax 30134 01 34 HERTZ FLOAT/highAccumulated peak frequency max duration dwNVFDurationMax 30135 01 35 SECOND unsigned LONG/low

dwNVFDurationMax 30136 01 36 SECOND unsigned LONG/highpeak frequency min ndNVFMin 30137 01 37 HERTZ FLOAT/low

ndNVFMin 30138 01 38 HERTZ FLOAT/highAccumulated peak frequency min duration dwNVFDurationMin 30139 01 39 SECOND unsigned LONG/low

dwNVFDurationMin 30140 01 40 SECOND unsigned LONG/highpeak Temperature max input 1 ndNVTMax[0] 30141 01 41 °C FLOAT/low

ndNVTMax[0] 30142 01 42 °C FLOAT/highAccumulated Temperature max input 1 duration dwNVTDurationMax[0] 30143 01 43 SECOND unsigned LONG/low

dwNVTDurationMax[0] 30144 01 44 SECOND unsigned LONG/highpeak Temperature min input 1 ndNVTMin[0] 30145 01 45 °C FLOAT/low

ndNVTMin[0] 30146 01 46 °C FLOAT/highAccumulated Temperature min input 1 duration dwNVTDurationMin[0] 30147 01 47 SECOND unsigned LONG/low

dwNVTDurationMin[0] 30148 01 48 SECOND unsigned LONG/highpeak Temperature max input 2 ndNVTMax[1] 30149 01 49 °C FLOAT/low

ndNVTMax[1] 30150 01 50 °C FLOAT/highAccumulated Temperature max input 2 duration dwNVTDurationMax[1] 30151 01 51 SECOND unsigned LONG/low

dwNVTDurationMax[1] 30152 01 52 SECOND unsigned LONG/highpeak Temperature min input 2 ndNVTMin[1] 30153 01 53 °C FLOAT/low

ndNVTMin[1] 30154 01 54 °C FLOAT/highAccumulated Temperature min input 2 duration dwNVTDurationMin[1] 30155 01 55 SECOND unsigned LONG/low

dwNVTDurationMin[1] 30156 01 56 SECOND unsigned LONG/high

General description

19

5.3 Output relays operation

This table contains general monitoring data from the RVT-D. The number of operations of each output capacitor relay is recorded since the RVT-D was manufactured.


Bank monitoring Number of operations number of operation output 1 dwNVOperation[0] 30201 02 01 NO UNIT unsigned LONG/lowdwNVOperation[0] 30202 02 02 NO UNIT unsigned LONG/high

number of operation output 2 dwNVOperation[1] 30203 02 03 NO UNIT unsigned LONG/lowdwNVOperation[1] 30204 02 04 NO UNIT unsigned LONG/high















General description

20


Bank monitoring Number of operations number of operation output 17 dwNVOperation[16] 30233 02 33 NO UNIT unsigned LONG/lowdwNVOperation[16] 30234 02 34 NO UNIT unsigned LONG/high
















General description

21

5.4 Alarm logging

This table contains the alarm messages and the time elapsed since their occurrences. Time elapsed is not available after a power outage. There is a circular buffer where both information are stored - kind of alarm logged. - elapsed time since alarm occurred. This buffer may contain until 5 consecutive alarms. A buffer index points to the eldest alarm logged. When the buffer is full, the eldest alarm in the buffer is overwritten with the new one and the index is incremented.


Bank monitoring Alarm buffer buffer 0 bAlarmLogType[0] 30301 03 01 Note (3) BYTEbuffer 1 bAlarmLogType[1] 30302 03 02 Note (3) BYTEbuffer 2 bAlarmLogType[2] 30303 03 03 Note (3) BYTEbuffer 3 bAlarmLogType[3] 30304 03 04 Note (3) BYTEbuffer 4 bAlarmLogType[4] 30305 03 05 Note (3) BYTEelapsed time of alarm in buffer 0 dwAlarmLogTime[0] 30306 03 06 SECOND unsigned LONG/low

dwAlarmLogTime[0] 30307 03 07 SECOND unsigned LONG/highelapsed time of alarm in buffer 1 dwAlarmLogTime[1] 30308 03 08 SECOND unsigned LONG/low




dwAlarmLogTime[4] 30315 03 15 SECOND unsigned LONG/highbuffer index bAlarmLogIdx 30316 03 16 Note (3) BYTE

General description

22

Note (3): The kind of alarm is given by the following table: Type of alarm Value

PROTECTION COS PHI (insufficient available reactive power) PROTECTION DYNASWITCH STATUS (at least one dynaswitch reports an error on the Optocoupler Digital Input 2) PROTECTION DYNASWITCH STATUS CAN (at least one dynaswitch reports an error through the CAN communication) PROTECTION TEMP SENSOR (temperature sensor lost while monitoring) PROTECTION U MAX (overvoltage detection) PROTECTION T MAX (internal temperature threshold reached) PROTECTION T1 MAX (temperature sensor 1 threshold reached) PROTECTION T2 MAX (temperature sensor 2 threshold reached) PROTECTION THDU (THDU threshold reached) PROTECTION U MIN (undervoltage detection)

1 2 3 4 5 6 7 8 9 10

23

5.5 Nodes overview This table reports the status of each node through the CAN interface


Bank monitoring Nodes overview Node Id Nr0 bReadStateStep[0] 30317 03 17 Note (4) BYTENode Id Nr1 bReadStateStep[1] 30318 03 18 Note (4) BYTENode Id Nr2 bReadStateStep[2] 30319 03 19 Note (4) BYTENode Id Nr3 bReadStateStep[3] 30320 03 20 Note (4) BYTENode Id Nr4 bReadStateStep[4] 30321 03 21 Note (4) BYTENode Id Nr5 bReadStateStep[5] 30322 03 22 Note (4) BYTENode Id Nr6 bReadStateStep[6] 30323 03 23 Note (4) BYTENode Id Nr7 bReadStateStep[7] 30324 03 24 Note (4) BYTENode Id Nr8 bReadStateStep[8] 30325 03 25 Note (4) BYTENode Id Nr9 bReadStateStep[9] 30326 03 26 Note (4) BYTENode Id Nr10 bReadStateStep[10] 30327 03 27 Note (4) BYTENode Id Nr11 bReadStateStep[11] 30328 03 28 Note (4) BYTENode Id Nr12 bReadStateStep[12] 30329 03 29 Note (4) BYTENode Id Nr13 bReadStateStep[13] 30330 03 30 Note (4) BYTENode Id Nr14 bReadStateStep[14] 30331 03 31 Note (4) BYTENode Id Nr15 bReadStateStep[15] 30332 03 32 Note (4) BYTENode Id Nr16 bReadStateStep[16] 30333 03 33 Note (4) BYTENode Id Nr17 bReadStateStep[17] 30334 03 34 Note (4) BYTENode Id Nr18 bReadStateStep[18] 30335 03 35 Note (4) BYTENode Id Nr19 bReadStateStep[19] 30336 03 36 Note (4) BYTENode Id Nr20 bReadStateStep[20] 30337 03 37 Note (4) BYTENode Id Nr21 bReadStateStep[21] 30338 03 38 Note (4) BYTENode Id Nr22 bReadStateStep[22] 30339 03 39 Note (4) BYTENode Id Nr23 bReadStateStep[23] 30340 03 40 Note (4) BYTENode Id Nr24 bReadStateStep[24] 30341 03 41 Note (4) BYTENode Id Nr25 bReadStateStep[25] 30342 03 42 Note (4) BYTENode Id Nr26 bReadStateStep[26] 30343 03 43 Note (4) BYTENode Id Nr27 bReadStateStep[27] 30344 03 44 Note (4) BYTENode Id Nr28 bReadStateStep[28] 30345 03 45 Note (4) BYTENode Id Nr29 bReadStateStep[29] 30346 03 46 Note (4) BYTE

General description

24

Node Id Nr30 bReadStateStep[30] 30347 03 47 Note (4) BYTENode Id Nr31 bReadStateStep[31] 30348 03 48 Note (4) BYTE

Note (4) : bReadStateStep [i] Signification 0 No step detected 1 Step ready 2 Waiting reset delay 3 Connection error 4 Discharge error 5 Synchronization error 6 Fuse error 7 Discharge warning 8 Multiple nodes on output

5.6 Outputs / Inputs

This table contains inputs / outputs status.


Outputs-Inputs Optocoupler outputs Outputs status P2 30401 04 01 Note (5) unsigned INTKeyboard keyboard status bKeyboard 30402 04 02 Note (6) BYTE

General description

Note (5): Outputs include optocoupler outputs as well as the alarm relay. - ‘1’ means that the output is not activated (output opened, alarm relay closed). - ‘0’ means that the output is activated (output closed, alarm relay opened).

25

Outputs P2

Bit 0 1Bit 1 2Bit 2 3Bit 3 4Bit 4 5Bit 5 6Bit 6 7Bit 7 8Bit 8 9

Bit 9 10Bit 10 11Bit 11 12Bit 12 alarmBit 13 Not usedBit 14 Not usedBit 15 Not used

Note (6): Inputs refer to the buttons status of the RVT-D keyboard. Meanings of bits are given in the following table.

Keyboard

Bit 0 ESCBit 1 HELPBit 2 OKBit 3 MINUSBit 4 PLUSBit 5Bit 6Bit 7 LOCK

26

5.7 Harmonic voltage spectrum This table contains voltage harmonics from 2nd up to 49th and fundamental voltage.


Spectrum U spectrum harmonic 1 wUSpectrum[1] 30501 05 01 Note (7) unsigned INTharmonic 2 wUSpectrum[2] 30502 05 02 Note (7) unsigned INTharmonic 3 wUSpectrum[3] 30503 05 03 Note (7) unsigned INTharmonic 4 wUSpectrum[4] 30504 05 04 Note (7) unsigned INTharmonic 5 wUSpectrum[5] 30505 05 05 Note (7) unsigned INTharmonic 6 wUSpectrum[6] 30506 05 06 Note (7) unsigned INTharmonic 7 wUSpectrum[7] 30507 05 07 Note (7) unsigned INTharmonic 8 wUSpectrum[8] 30508 05 08 Note (7) unsigned INTharmonic 9 wUSpectrum[9] 30509 05 09 Note (7) unsigned INTharmonic 10 wUSpectrum[10] 30510 05 10 Note (7) unsigned INTharmonic 11 wUSpectrum[11] 30511 05 11 Note (7) unsigned INTharmonic 12 wUSpectrum[12] 30512 05 12 Note (7) unsigned INTharmonic 13 wUSpectrum[13] 30513 05 13 Note (7) unsigned INTharmonic 14 wUSpectrum[14] 30514 05 14 Note (7) unsigned INTharmonic 15 wUSpectrum[15] 30515 05 15 Note (7) unsigned INTharmonic 16 wUSpectrum[16] 30516 05 16 Note (7) unsigned INTharmonic 17 wUSpectrum[17] 30517 05 17 Note (7) unsigned INTharmonic 18 wUSpectrum[18] 30518 05 18 Note (7) unsigned INTharmonic 19 wUSpectrum[19] 30519 05 19 Note (7) unsigned INTharmonic 20 wUSpectrum[20] 30520 05 20 Note (7) unsigned INTharmonic 21 wUSpectrum[21] 30521 05 21 Note (7) unsigned INTharmonic 22 wUSpectrum[22] 30522 05 22 Note (7) unsigned INTharmonic 23 wUSpectrum[23] 30523 05 23 Note (7) unsigned INTharmonic 24 wUSpectrum[24] 30524 05 24 Note (7) unsigned INTharmonic 25 wUSpectrum[25] 30525 05 25 Note (7) unsigned INT

General description

27


Spectrum U spectrum harmonic 26 wUSpectrum[26] 30526 05 26 Note (7) unsigned INTharmonic 27 wUSpectrum[27] 30527 05 27 Note (7) unsigned INTharmonic 28 wUSpectrum[28] 30528 05 28 Note (7) unsigned INTharmonic 29 wUSpectrum[29] 30529 05 29 Note (7) unsigned INTharmonic 30 wUSpectrum[30] 30530 05 30 Note (7) unsigned INTharmonic 31 wUSpectrum[31] 30531 05 31 Note (7) unsigned INTharmonic 32 wUSpectrum[32] 30532 05 32 Note (7) unsigned INTharmonic 33 wUSpectrum[33] 30533 05 33 Note (7) unsigned INTharmonic 34 wUSpectrum[34] 30534 05 34 Note (7) unsigned INTharmonic 35 wUSpectrum[35] 30535 05 35 Note (7) unsigned INTharmonic 36 wUSpectrum[36] 30536 05 36 Note (7) unsigned INTharmonic 37 wUSpectrum[37] 30537 05 37 Note (7) unsigned INTharmonic 38 wUSpectrum[38] 30538 05 38 Note (7) unsigned INTharmonic 39 wUSpectrum[39] 30539 05 39 Note (7) unsigned INTharmonic 40 wUSpectrum[40] 30540 05 40 Note (7) unsigned INTharmonic 41 wUSpectrum[41] 30541 05 41 Note (7) unsigned INTharmonic 42 wUSpectrum[42] 30542 05 42 Note (7) unsigned INTharmonic 43 wUSpectrum[43] 30543 05 43 Note (7) unsigned INTharmonic 44 wUSpectrum[44] 30544 05 44 Note (7) unsigned INTharmonic 45 wUSpectrum[45] 30545 05 45 Note (7) unsigned INTharmonic 46 wUSpectrum[46] 30546 05 46 Note (7) unsigned INTharmonic 47 wUSpectrum[47] 30547 05 47 Note (7) unsigned INTharmonic 48 wUSpectrum[48] 30548 05 48 Note (7) unsigned INTharmonic 49 wUSpectrum[49] 30549 05 49 Note (7) unsigned INT

General description

Note (7): The value given is a percentage of the fundamental multiplied by 10 (ex 100%: 1000)

28

5.8 Spectrum analysis of the current

This table contains current harmonics from 2nd up to 49th and fundamental current.


Spectrum I spectrum harmonic 1 wISpectrum[1] 30601 06 01 Note (8) unsigned INTharmonic 2 wISpectrum[2] 30602 06 02 Note (8) unsigned INTharmonic 3 wISpectrum[3] 30603 06 03 Note (8) unsigned INTharmonic 4 wISpectrum[4] 30604 06 04 Note (8) unsigned INTharmonic 5 wISpectrum[5] 30605 06 05 Note (8) unsigned INTharmonic 6 wISpectrum[6] 30606 06 06 Note (8) unsigned INTharmonic 7 wISpectrum[7] 30607 06 07 Note (8) unsigned INTharmonic 8 wISpectrum[8] 30608 06 08 Note (8) unsigned INTharmonic 9 wISpectrum[9] 30609 06 09 Note (8) unsigned INTharmonic 10 wISpectrum[10] 30610 06 10 Note (8) unsigned INTharmonic 11 wISpectrum[11] 30611 06 11 Note (8) unsigned INTharmonic 12 wISpectrum[12] 30612 06 12 Note (8) unsigned INTharmonic 13 wISpectrum[13] 30613 06 13 Note (8) unsigned INTharmonic 14 wISpectrum[14] 30614 06 14 Note (8) unsigned INTharmonic 15 wISpectrum[15] 30615 06 15 Note (8) unsigned INTharmonic 16 wISpectrum[16] 30616 06 16 Note (8) unsigned INTharmonic 17 wISpectrum[17] 30617 06 17 Note (8) unsigned INTharmonic 18 wISpectrum[18] 30618 06 18 Note (8) unsigned INTharmonic 19 wISpectrum[19] 30619 06 19 Note (8) unsigned INTharmonic 20 wISpectrum[20] 30620 06 20 Note (8) unsigned INTharmonic 21 wISpectrum[21] 30621 06 21 Note (8) unsigned INTharmonic 22 wISpectrum[22] 30622 06 22 Note (8) unsigned INTharmonic 23 wISpectrum[23] 30623 06 23 Note (8) unsigned INTharmonic 24 wISpectrum[24] 30624 06 24 Note (8) unsigned INTharmonic 25 wISpectrum[25] 30625 06 25 Note (8) unsigned INT

General description

29


Spectrum I spectrum harmonic 26 wISpectrum[26] 30626 06 26 Note (8) unsigned INTharmonic 27 wISpectrum[27] 30627 06 27 Note (8) unsigned INTharmonic 28 wISpectrum[28] 30628 06 28 Note (8) unsigned INTharmonic 29 wISpectrum[29] 30629 06 29 Note (8) unsigned INTharmonic 30 wISpectrum[30] 30630 06 30 Note (8) unsigned INTharmonic 31 wISpectrum[31] 30631 06 31 Note (8) unsigned INTharmonic 32 wISpectrum[32] 30632 06 32 Note (8) unsigned INTharmonic 33 wISpectrum[33] 30633 06 33 Note (8) unsigned INTharmonic 34 wISpectrum[34] 30634 06 34 Note (8) unsigned INTharmonic 35 wISpectrum[35] 30635 06 35 Note (8) unsigned INTharmonic 36 wISpectrum[36] 30636 06 36 Note (8) unsigned INTharmonic 37 wISpectrum[37] 30637 06 37 Note (8) unsigned INTharmonic 38 wISpectrum[38] 30638 06 38 Note (8) unsigned INTharmonic 39 wISpectrum[39] 30639 06 39 Note (8) unsigned INTharmonic 40 wISpectrum[40] 30640 06 40 Note (8) unsigned INTharmonic 41 wISpectrum[41] 30641 06 41 Note (8) unsigned INTharmonic 42 wISpectrum[42] 30642 06 42 Note (8) unsigned INTharmonic 43 wISpectrum[43] 30643 06 43 Note (8) unsigned INTharmonic 44 wISpectrum[44] 30644 06 44 Note (8) unsigned INTharmonic 45 wISpectrum[45] 30645 06 45 Note (8) unsigned INTharmonic 46 wISpectrum[46] 30646 06 46 Note (8) unsigned INTharmonic 47 wISpectrum[47] 30647 06 47 Note (8) unsigned INTharmonic 48 wISpectrum[48] 30648 06 48 Note (8) unsigned INTharmonic 49 wISpectrum[49] 30649 06 49 Note (8) unsigned INT

General description

Note (8): The value given is a percentage of the fundamental multiplied by 10 (ex 100%: 1000)

30

5.9 Clock reference

This table contains clock references data. Data provided are seconds (0 to 59), minutes (0 to 59), and hours (0 to 23) since the last reset of the RVT-D. Comment: please note that this clock reference is not a real time clock but counters incremented with the clock of the RVT-D. Counters are reset to zero when the RVT-D is reset. After one complete day, counters are reset to 0.


Timings clock reference seconds since last reset bSecond 39801 98 01 SECONDS BYTEminutes since last reset bMinute 39802 98 02 MINUTES BYTEhours since last reset bHour 39803 98 03 HOURS BYTE

General description

31

6 SETTINGS

6.1 Bank settings

This table contains bank settings except protection settings which can be found in paragraph 6.2.

Description Variable Variable name Modbus Access Units Datatyperegister Table number offset Set LS BL R NV C

Settings Bank settings V nominal ndNVUNominal 40001 00 01 1 1 1 0 1 0 VOLT FLOAT/lowndNVUNominal 40002 00 02 1 1 1 0 1 0 VOLT FLOAT/high

V scaling ndNVUScale 40003 00 03 1 1 1 0 1 0 No unit FLOAT/lowndNVUScale 40004 00 04 1 1 1 0 1 0 No unit FLOAT/high

1Ph/3Ph bNVNumberPhase 40005 00 05 1 1 1 0 1 0 Note (9) BYTEQ step ndNVQStep 40006 00 06 1 1 1 0 1 0 VAR FLOAT/low

ndNVQStep 40007 00 07 1 1 1 0 1 0 VAR FLOAT/highsize output 1 NVRelayOut[0].bSize 40008 00 08 1 1 1 0 1 0 STEPS BYTEstatus output 1 NVRelayOut[0].bStatus 40009 00 09 1 1 1 0 1 0 Note (10) BYTEsize output 2 NVRelayOut[1].bSize 40010 00 10 1 1 1 0 1 0 STEPS BYTEstatus output 2 NVRelayOut[1].bStatus 40011 00 11 1 1 1 0 1 0 Note (10) BYTEsize output 3 NVRelayOut[2].bSize 40012 00 12 1 1 1 0 1 0 STEPS BYTEstatus output 3 NVRelayOut[2].bStatus 40013 00 13 1 1 1 0 1 0 Note (10) BYTEsize output 4 NVRelayOut[3].bSize 40014 00 14 1 1 1 0 1 0 STEPS BYTEstatus output 4 NVRelayOut[3].bStatus 40015 00 15 1 1 1 0 1 0 Note (10) BYTEsize output 5 NVRelayOut[4].bSize 40016 00 16 1 1 1 0 1 0 STEPS BYTEstatus output 5 NVRelayOut[4].bStatus 40017 00 17 1 1 1 0 1 0 Note (10) BYTEsize output 6 NVRelayOut[5].bSize 40018 00 18 1 1 1 0 1 0 STEPS BYTEstatus output 6 NVRelayOut[5].bStatus 40019 00 19 1 1 1 0 1 0 Note (10) BYTEsize output 7 NVRelayOut[6].bSize 40020 00 20 1 1 1 0 1 0 STEPS BYTEstatus output 7 NVRelayOut[6].bStatus 40021 00 21 1 1 1 0 1 0 Note (10) BYTEsize output 8 NVRelayOut[7].bSize 40022 00 22 1 1 1 0 1 0 STEPS BYTEstatus output 8 NVRelayOut[7].bStatus 40023 00 23 1 1 1 0 1 0 Note (10) BYTEsize output 9 NVRelayOut[8].bSize 40024 00 24 1 1 1 0 1 0 STEPS BYTEstatus output 9 NVRelayOut[8].bStatus 40025 00 25 1 1 1 0 1 0 Note (10) BYTEsize output 10 NVRelayOut[9].bSize 40026 00 26 1 1 1 0 1 0 STEPS BYTEstatus output 10 NVRelayOut[9].bStatus 40027 00 27 1 1 1 0 1 0 Note (10) BYTE

General description

32


Settings Bank settings size output 11 NVRelayOut[10].bSize 40028 00 28 1 1 1 0 1 0 STEPS BYTEstatus output 11 NVRelayOut[10].bStatus 40029 00 29 1 1 1 0 1 0 Note (10) BYTEsize output 12 NVRelayOut[11].bSize 40030 00 30 1 1 1 0 1 0 STEPS BYTEstatus output 12 NVRelayOut[11].bStatus 40031 00 31 1 1 1 0 1 0 Note (10) BYTEsize output 13 NVRelayOut[12].bSize 40032 00 32 1 1 1 0 1 0 STEPS BYTEstatus output 13 NVRelayOut[12].bStatus 40033 00 33 1 1 1 0 1 0 Note (10) BYTEsize output 14 NVRelayOut[13].bSize 40034 00 34 1 1 1 0 1 0 STEPS BYTEstatus output 14 NVRelayOut[13].bStatus 40035 00 35 1 1 1 0 1 0 Note (10) BYTEsize output 15 NVRelayOut[14].bSize 40036 00 36 1 1 1 0 1 0 STEPS BYTEstatus output 15 NVRelayOut[14].bStatus 40037 00 37 1 1 1 0 1 0 Note (10) BYTEsize output 16 NVRelayOut[15].bSize 40038 00 38 1 1 1 0 1 0 STEPS BYTEstatus output 16 NVRelayOut[15].bStatus 40039 00 39 1 1 1 0 1 0 Note (10) BYTEsize output 17 NVRelayOut[16].bSize 40040 00 40 1 1 1 0 1 0 STEPS BYTEstatus output 17 NVRelayOut[16].bStatus 40041 00 41 1 1 1 0 1 0 Note (10) BYTEsize output 18 NVRelayOut[17].bSize 40042 00 42 1 1 1 0 1 0 STEPS BYTEstatus output 18 NVRelayOut[17].bStatus 40043 00 43 1 1 1 0 1 0 Note (10) BYTEsize output 19 NVRelayOut[18].bSize 40044 00 44 1 1 1 0 1 0 STEPS BYTEstatus output 19 NVRelayOut[18].bStatus 40045 00 45 1 1 1 0 1 0 Note (10) BYTEsize output 20 NVRelayOut[19].bSize 40046 00 46 1 1 1 0 1 0 STEPS BYTEstatus output 20 NVRelayOut[19].bStatus 40047 00 47 1 1 1 0 1 0 Note (10) BYTEsize output 21 NVRelayOut[20].bSize 40048 00 48 1 1 1 0 1 0 STEPS BYTEstatus output 21 NVRelayOut[20].bStatus 40049 00 49 1 1 1 0 1 0 Note (10) BYTEsize output 22 NVRelayOut[21].bSize 40050 00 50 1 1 1 0 1 0 STEPS BYTEstatus output 22 NVRelayOut[21].bStatus 40051 00 51 1 1 1 0 1 0 Note (10) BYTEsize output 23 NVRelayOut[22].bSize 40052 00 52 1 1 1 0 1 0 STEPS BYTEstatus output 23 NVRelayOut[22].bStatus 40053 00 53 1 1 1 0 1 0 Note (10) BYTEsize output 24 NVRelayOut[23].bSize 40054 00 54 1 1 1 0 1 0 STEPS BYTEstatus output 24 NVRelayOut[23].bStatus 40055 00 55 1 1 1 0 1 0 Note (10) BYTEsize output 25 NVRelayOut[24].bSize 40056 00 56 1 1 1 0 1 0 STEPS BYTEstatus output 25 NVRelayOut[24].bStatus 40057 00 57 1 1 1 0 1 0 Note (10) BYTEsize output 26 NVRelayOut[25].bSize 40058 00 58 1 1 1 0 1 0 STEPS BYTEstatus output 26 NVRelayOut[25].bStatus 40059 00 59 1 1 1 0 1 0 Note (10) BYTEsize output 27 NVRelayOut[26].bSize 40060 00 60 1 1 1 0 1 0 STEPS BYTEstatus output 27 NVRelayOut[26].bStatus 40061 00 61 1 1 1 0 1 0 Note (10) BYTE

General description

33

Description Variable Variable name Modbus Access Units Datatype

register Table number offset Set LS BL R NV CSettings Bank settings size output 28 NVRelayOut[27].bSize 40062 00 62 1 1 1 0 1 0 STEPS BYTE

status output 28 NVRelayOut[27].bStatus 40063 00 63 1 1 1 0 1 0 Note (10) BYTEsize output 29 NVRelayOut[28].bSize 40064 00 64 1 1 1 0 1 0 STEPS BYTEstatus output 29 NVRelayOut[28].bStatus 40065 00 65 1 1 1 0 1 0 Note (10) BYTEsize output 30 NVRelayOut[29].bSize 40066 00 66 1 1 1 0 1 0 STEPS BYTEstatus output 30 NVRelayOut[29].bStatus 40067 00 67 1 1 1 0 1 0 Note (10) BYTEsize output 31 NVRelayOut[30].bSize 40068 00 68 1 1 1 0 1 0 STEPS BYTEstatus output 31 NVRelayOut[30].bStatus 40069 00 69 1 1 1 0 1 0 Note (10) BYTEsize output 32 NVRelayOut[31].bSize 40070 00 70 1 1 1 0 1 0 STEPS BYTEstatus output 32 NVRelayOut[31].bStatus 40071 00 71 1 1 1 0 1 0 Note (10) BYTELin / Circ bNVLinearCircular 40072 00 72 1 1 1 0 1 0 Note (11) BYTEProg/direct bNVProgDirect 40073 00 73 1 1 1 0 1 0 Note (12) BYTESwitch Delay dwNVDelayON 40074 00 74 1 1 1 0 1 0 SECOND unsigned LONG/low

dwNVDelayON 40075 00 75 1 1 1 0 1 0 SECOND unsigned LONG/highReset Delay dwNVDelayReset 40076 00 76 1 1 1 0 1 0 SECOND unsigned LONG/low

dwNVDelayReset 40077 00 77 1 1 1 0 1 0 SECOND unsigned LONG/highPrint Delay dwNVDelayPrint 40078 00 78 1 1 1 0 1 0 SECOND unsigned LONG/low

dwNVDelayPrint 40079 00 79 1 1 1 0 1 0 SECOND unsigned LONG/highCT scale-cap ndNVIDynScale 40080 00 80 1 1 1 0 1 0 NO UNIT FLOAT/low

ndNVIDynScale 40081 00 81 1 1 1 0 1 0 NO UNIT FLOAT/highInvert Icap bNVInvertIDyn 40082 00 82 1 1 1 0 1 0 EN/DIS BYTE

General description

Note (9): Number of phases of the bank and voltage measurement connection: bNVNumberPhase Signification 0 1 Phase 1 3 Phase / phase to phase 2 3 Phase / phase to neutral

34

Note (10): Outputs status: NVRelayOut[ ].bStatus Signification 0 Fixed OFF 1 Enabled (for automatic compensation) 2 Fixed ON

Note (11): bNVLinearCircular Signification 0 Linear 1 Circular

Note (12): bNVProgDirect Signification 0 Progressive 1 Direct

35

6.2 Protections This table contains protection levels against undervoltage, overvoltage, prohibitive harmonics and overtemperature: Once a protection level is reached, the following actions occurs: • All the capacitor steps are switched OFF. • An alarm message appears on the display and is recorded. • The alarm relay closes. The alarm message is recorded (for more information, please refer to paragraph 5.4)


Settings Protections V min prot. ndNVUMinProtect 40101 01 01 1 1 1 0 1 0 VOLT FLOAT/lowndNVUMinProtect 40102 01 02 1 1 1 0 1 0 VOLT FLOAT/high

V max prot. ndNVUMaxProtect 40103 01 03 1 1 1 0 1 0 VOLT FLOAT/lowndNVUMaxProtect 40104 01 04 1 1 1 0 1 0 VOLT FLOAT/high

T1 max prot. ndNVTMaxProtect[0] 40105 01 05 1 1 1 0 1 0 °C FLOAT/lowndNVTMaxProtect[0] 40106 01 06 1 1 1 0 1 0 °C FLOAT/high

T2 max prot. ndNVTMaxProtect[1] 40107 01 07 1 1 1 0 1 0 °C FLOAT/lowndNVTMaxProtect[1] 40108 01 08 1 1 1 0 1 0 °C FLOAT/high

THDV max prot. ndNVTHDUMaxProtect 40109 01 09 1 1 1 0 1 0 PERCENT FLOAT/lowndNVTHDUMaxProtect 40110 01 10 1 1 1 0 1 0 PERCENT FLOAT/high

General description

36

6.3 Event logging settings This table contains the level related to the event logging function (please refer to paragraph 5.2.).


Settings Event Logging SVrms Threshold ndNVUrmsThreshold 40201 02 01 0 1 0 0 1 0 VOLT FLOAT/lowndNVUrmsThreshold 40202 02 02 0 1 0 0 1 0 VOLT FLOAT/high

Irms Threshold ndNVIrmsThreshold 40203 02 03 0 1 0 0 1 0 AMPERE FLOAT/lowndNVIrmsThreshold 40204 02 04 0 1 0 0 1 0 AMPERE FLOAT/high

active power threshold ndNVPThreshold 40205 02 05 0 1 0 0 1 0 WATT FLOAT/lowndNVPThreshold 40206 02 06 0 1 0 0 1 0 WATT FLOAT/high

reactive power threshold ndNVQThreshold 40207 02 07 0 1 0 0 1 0 VAR FLOAT/lowndNVQThreshold 40208 02 08 0 1 0 0 1 0 VAR FLOAT/high

missing reactive power threshold ndNVQMissThreshold 40209 02 09 0 1 0 0 1 0 VAR FLOAT/lowndNVQMissThreshold 40210 02 10 0 1 0 0 1 0 VAR FLOAT/high

apparent power threshold ndNVSThreshold 40211 02 11 0 1 0 0 1 0 VA FLOAT/lowndNVSThreshold 40212 02 12 0 1 0 0 1 0 VA FLOAT/high

temperature T1 threshold max ndNVTThresholdMax[0] 40213 02 13 0 1 0 0 1 0 °C FLOAT/lowndNVTThresholdMax[0] 40214 02 14 0 1 0 0 1 0 °C FLOAT/high

temperature T1 threshold min ndNVTThresholdMin[0] 40215 02 15 0 1 0 0 1 0 °C FLOAT/lowndNVTThresholdMin[0] 40216 02 16 0 1 0 0 1 0 °C FLOAT/high

temperature T2 threshold max ndNVTThresholdMax[1] 40217 02 17 0 1 0 0 1 0 °C FLOAT/lowndNVTThresholdMax[1] 40218 02 18 0 1 0 0 1 0 °C FLOAT/high

temperature T2 threshold min ndNVTThresholdMin[1] 40219 02 19 0 1 0 0 1 0 °C FLOAT/lowndNVTThresholdMin[1] 40220 02 20 0 1 0 0 1 0 °C FLOAT/high

frequency max threshold ndNVFThresholdMax 40221 02 21 0 1 0 0 1 0 HERTZ FLOAT/lowndNVFThresholdMax 40222 02 22 0 1 0 0 1 0 HERTZ FLOAT/high

frequency min threshold ndNVFThresholdMin 40223 02 23 0 1 0 0 1 0 HERTZ FLOAT/lowndNVFThresholdMin 40224 02 24 0 1 0 0 1 0 HERTZ FLOAT/high

THDV threshold ndNVTHDUThreshold 40225 02 25 0 1 0 0 1 0 PERCENT FLOAT/lowndNVTHDUThreshold 40226 02 26 0 1 0 0 1 0 PERCENT FLOAT/high

THDI threshold ndNVTHDIThreshold 40227 02 27 0 1 0 0 1 0 PERCENT FLOAT/lowndNVTHDIThreshold 40228 02 28 0 1 0 0 1 0 PERCENT FLOAT/high

General description

37

6.4 Installation settings This table contains installation parameters.


Settings Installation settings CT scale-net ndNVIScale 40301 03 01 1 1 1 0 1 0 No unit FLOAT/lowndNVIScale 40302 03 02 1 1 1 0 1 0 No unit FLOAT/high

Istep ndNVUnityStepSize 40303 03 03 1 1 1 0 1 0 AMPERE FLOAT/lowndNVUnityStepSize 40304 03 04 1 1 1 0 1 0 AMPERE FLOAT/high

ΔIstep ndNVDeltaI 40305 03 05 1 1 1 0 1 0 PERCENT FLOAT/lowndNVDeltaI 40306 03 06 1 1 1 0 1 0 PERCENT FLOAT/high

Hysteresis ndNVHysteresis 40307 03 07 1 1 1 0 1 0 PERCENT FLOAT/lowndNVHysteresis 40308 03 08 1 1 1 0 1 0 PERCENT FLOAT/high

Qspeed bNVFastQ 40309 03 09 1 1 1 0 1 0 Note (13) BYTESequence strategy bNVOverCompensation 40310 03 10 1 1 1 0 1 0 Note (14) BYTEPhase Shift ndNVPhaseDelay 40311 03 11 1 1 1 0 1 0 DEGREE FLOAT/low

ndNVPhaseDelay 40312 03 12 1 1 1 0 1 0 DEGREE FLOAT/highCT-net bNVDisplayLineValues 40313 03 13 1 1 1 0 1 0 Note (15) BYTEControl bNVRegulationType 40314 03 14 1 1 1 0 1 0 Note (16) BYTETriggerON bNVCommandON 40315 03 15 1 1 1 0 1 0 Note (17) BYTEStartCurrent ndNVExtTriggerSize 40316 03 16 1 1 1 0 1 0 PERCENT FLOAT/low

ndNVExtTriggerSize 40317 03 17 1 1 1 0 1 0 PERCENT FLOAT/highTime In wNVTimeInPe 40318 03 18 1 1 1 0 1 0 Note (18) Unsigned INTTriggerOFF bNVCommandOFF 40319 03 19 1 1 1 0 1 0 Note (19) BYTETime Out wNVTimeOutPe 40320 03 20 1 1 1 0 1 0 Note (18) Unsigned INTStepControl bNVUseCT 40321 03 21 1 1 1 0 1 0 Note (20) BYTETotalDuration wNVTotalCycleON 40322 03 22 1 1 1 0 1 0 Note (21) Unsigned INT

General description

Note (13): bNVFastQ Signification 0 SLOW Q Computation 1 FAST Q Computation

38

Note (14): bNVOverCompensation Signification 0 Undercompensation 1 Overcompensation Note (15): bNVDisplayLineValues Signification 0 Line Values 1 Load Values Note (16): bNVRegulationType Signification 0 Open Loop regulation 1 Closed Loop regulation 2 External Trigger activated Note (17): bNVCommandON Signification 0 No start 1 Input 1 – rising edge 2 Input 1 – falling edge 3 Input 2 – rising edge 4 Input 2 – falling edge 5 Iload Note (18): expressed in 1/32 of a network period Pe= P/32

39

Note (19): bNVCommandOFF Signification 0 Time out activation 1 Input 1 – rising edge 2 Input 1 – falling edge 3 Input 2 – rising edge 4 Input 2 – falling edge 5 Iload 6 (Time out +1) activation Note (20): bNVUseCT Signification 0 Disable 1 Enable Note (21): expressed in number of network periods P.

40

6.5 User settings This table contains additional installation parameters which are dedicated to the installer and/or the user.


Settings User settings Target cos phi ndNVTargetCosPhi 40401 04 01 1 1 1 0 1 0 Note (1) FLOAT/lowndNVTargetCosPhi 40402 04 02 1 1 1 0 1 0 Note (1) FLOAT/high

V drop R/X ndNVR_X 40403 04 03 1 1 1 0 1 0 NO UNIT FLOAT/lowndNVR_X 40404 04 04 1 1 1 0 1 0 NO UNIT FLOAT/high

Inrush Size bNVInrushSize 40405 04 05 1 1 1 0 1 0 STEPS BYTEInrush ΔT wNVInrushDurationPe 40406 04 06 1 1 1 0 1 0 Note (18) unsigned INTalarm delay dwNVDelayAlarm 40407 04 07 1 1 1 0 1 0 SECOND unsigned LONG/low

dwNVDelayAlarm 40408 04 08 1 1 1 0 1 0 SECOND unsigned LONG/highalarm reset delay dwNVDelayAlarmReset 40409 04 09 1 1 1 0 1 0 SECOND unsigned LONG/low

dwNVDelayAlarmReset 40410 04 10 1 1 1 0 1 0 SECOND unsigned LONG/highalarm cos phi ndNVCosPhiAlarm 40411 04 11 1 1 1 0 1 0 Note (1) FLOAT/low

ndNVCosPhiAlarm 40412 04 12 1 1 1 0 1 0 Note (1) FLOAT/high

General description

6.6 I/O configuration This table contains parameters related to external communication and graphic display.


Settings I/O configuration Language bNVLanguage 40501 05 01 1 1 0 0 1 0 Note (22) BYTETemperature unit bNVFahrenheit 40502 05 02 0 1 0 0 1 0 Note (23) BYTELCD contrast cNVLcdContrastOffset 40503 05 03 0 1 0 0 1 0 No unit signed CHARprinter type bNVPrinterType 40504 05 04 0 1 0 0 1 0 No unit BYTEModbus adress wNVModbusAdress 40505 05 05 1 1 1 0 1 0 No unit unsigned INTprotocol bNVModbusEnable 40506 05 06 1 1 1 0 1 0 Note (24) BYTEModbus lock bNVModbusLocking 40507 05 07 1 1 0 0 1 0 Note (25) BYTEModbus baud rate bNVUartBaudRate 40508 05 08 1 1 1 0 1 0 Note (26) BYTEparity bNVParity 40509 05 09 1 1 1 0 1 0 Note (27) BYTEstop bits bNVStopBit 40510 05 10 1 1 1 0 1 0 Note (28) BYTE

General description

41

Note (22): language bNVLanguage Signification 0 English 1 French 2 Deutsch 3 Spanish Note (23): temperature unit. (This parameter only affects the units of the measurements displayed on the LCD screen of the RVT-D.) bNVFahrenheit Signification 0 Celsius 1 Fahrenheit Note (24): protocol bNVModbusEnable Signification 0 Printer 1 Modbus/RTU Note (25): Modbus lock bNVModbusLocking Signification 0 Unlocked 1 Locked Note (26): baud rate bNVartBaudRate Signification 0 110 bauds 1 300 bauds 2 600 bauds 3 1200 bauds 4 2400 bauds 5 4800 bauds 6 9600 bauds 7 19200 bauds 8 38400 bauds 9 57600 bauds

42

Note (27): Parity bit bNVMParity Signification 0 No parity 1 Even 2 Odd Note (28): Stop bit bNVStopBit Signification 0 1 stop bit 1 2 stop bit

6.7 Change Mode (AUTO-MAN-SET) This table contains the RVT-D operating mode. Switching ON and OFF steps (MAN mode) functionality is included in this table.

Note (29): The mode may be changed with the following parameter:


Functional parameters Functional parameters Mode bNVMode 40601 06 01 0 1 0 0 1 0 Note (29) BYTEBank settings lock bNVBankLocked 40602 06 02 1 1 0 0 1 0 Note (30) BYTEAdd 1 step bAddOneStep 40603 06 03 0 1 0 1 0 0 Note (29) BYTERemove 1 step bRemoveOneStep 40604 06 04 0 1 0 1 0 0 Note (29) BYTEStep size in MAN mode wNVManualSize 40605 06 05 0 1 0 0 1 0 STEPS unsigned INT

General description

bNVMode Value AUTO 1 MAN 2 SET 4

The default mode is AUTO.

43

Manual mode (MAN) can be used to switch ON/OFF steps. In MAN mode: • Set the ‘bAddOneStep’ parameter to 1 to switch ON one step. • Set the ‘bRemoveOneStep’ parameter to 1 to switch OFF one step. • wNVManualSize sets directly the number of fixed steps which will be automatically reconnected each time a power outage occurs while in the

MAN mode. It is readable but cannot be changed directly. Use “bAddOneStep” or “bRemoveOneStep” to change the number of steps in manual mode. RVT-D must be in SET mode to modify most of the parameter settings (for more information, please refer to RVT-D Installation and Operating Instruction manual. An exception error will occur if an attempt to change settings is done while in another mode than SET. Note (30): bNVBankLocked activates the ‘Bank settings <locked>’ function when set to 1. When the bank settings item is set as locked (whatever the Mode used): • a padlock icon appears beside all the bank settings • no modification can be made to the bank settings An exception error will occur if an attempt to change settings is done while bank settings item is set as locked. bNVBankLocked Signification 0 Unlocked 1 Locked

44

6.8 CAN Configuration


Functional parameters CAN configuration CAN control bNVCanControlbNVNodeTypebNVPhaseAdvancendNVDeadTimendNVDeadTimebNVIgnoreNodeStatusbNVTwoNodesPerId

40701 07 01 1 1 1 0 1 0 Note (31) BYTENode Type 40702 07 02 1 1 1 0 1 0 Note (32) BYTESynchro advance 40703 07 03 1 1 1 0 1 0 Note (33) BYTEDead time 40704 07 04 1 1 1 0 1 0 DEGREE FLOAT/low

40705 07 05 1 1 1 0 1 0 DEGREE FLOAT/highNode status 40706 07 06 1 1 1 0 1 0 Note (34) BYTETwo nodes / Id 40707 07 07 1 1 1 0 1 0 Note (35) BYTE

General description

Note (31): bNVCanControl Signification 0 Disabled 1 Enabled Note (32): bNVNodeType Signification 0 3ph capacitor 1 1ph capacitor 2 3ph reactor 3 1ph reactor Note (33): expressed in number of Pe/4 = P/128 Note (34): bNVIgnoreNodeStatus Signification 0 Ignored 1 Used Note (35): bNVTwoNodesPerId Signification 0 Disabled 1 Enabled

45

6.9 User data storage

This table contains free 8 bytes wide buffer where the user can store its own data. This non volatile memory have no effect on the behavior of the RVT-D.


User parameters User parameters User data storage bNVUser[0] 49701 97 01 0 0 0 0 1 0 BYTEbNVUser[1] 49702 97 02 0 0 0 0 1 0 BYTEbNVUser[2] 49703 97 03 0 0 0 0 1 0 BYTEbNVUser[3] 49704 97 04 0 0 0 0 1 0 BYTEbNVUser[4] 49705 97 05 0 0 0 0 1 0 BYTEbNVUser[5] 49706 97 06 0 0 0 0 1 0 BYTEbNVUser[6] 49707 97 07 0 0 0 0 1 0 BYTEbNVUser[7] 49708 97 08 0 0 0 0 1 0 BYTE

General description

46

6.10 RVT-D manufacturer information

This table contains general RVT-D information.

Note (36): This part of the Modbus table contains ‘read only’ RVT-D manufacturer information:


Manufacturer settings Manufacturer settings Number of outputs bNVNumberRelay 49801 98 01 0 0 0 0 0 1 Note (36) BYTEserial number dwNVSerialNumber 49802 98 02 0 0 0 0 0 1 Note (36) unsigned LONG/low

dwNVSerialNumber 49803 98 03 0 0 0 0 0 1 Note (36) unsigned LONG/highABB ID 1 bNVABBIdNr1 49804 98 04 0 0 0 0 0 1 Note (36) BYTEABB ID 2 wNVABBIdNr2 49805 98 05 0 0 0 0 0 1 Note (36) unsigned INTABB ID 3 dwNVABBIdNr3 49806 98 06 0 0 0 0 0 1 Note (36) unsigned LONG/low

dwNVABBIdNr3 49807 98 07 0 0 0 0 0 1 Note (36) unsigned LONG/highsoft version wSoftVersion 49808 98 08 0 0 0 0 0 1 Note (36) unsigned INTProduct ID wNVProductId[0] 49809 98 09 0 0 0 0 1 0 Note (37) unsigned INT

wNVProductId[1] 49810 98 10 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[2] 49811 98 11 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[3] 49812 98 12 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[4] 49813 98 13 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[5] 49814 98 14 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[6] 49815 98 15 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[7] 49816 98 16 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[8] 49817 98 17 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[9] 49818 98 18 0 0 0 0 1 0 Note (37) unsigned INTwNVProductId[10] 49819 98 19 0 0 0 0 1 0 Note (37) unsigned INT

Product Type wProductType[0] 49820 98 20 0 0 0 0 0 1 Note (37) unsigned INTwProductType[1] 49821 98 21 0 0 0 0 0 1 Note (37) unsigned INTwProductType[2] 49822 98 22 0 0 0 0 0 1 Note (37) unsigned INT

General description

• Number of outputs • Serial number • ID number • Soft version (x.y : high byte = x, low byte = y)

47

Note (37): Another part contains non volatile ‘read / write’ manufacturer settings used to store data concerning the identification of the product . This non volatile memory have no effect on the behaviour of the RVT-D. Some data contained in this part of the Modbus table are the same data that can be retrieve with the Report Slave ID Modbus function (code 17). This is a string field containing the ABB Id number of the product and the product type . This string field is arranged as a succession of ASCII characters : WordHI[0]_WordLO[0]_ WordHI[1]_WordLO[1]_…

48

7 OUTPUT & INPUT BITS

7.1 Output bits This table contains free bytes for bit change testing. This has no effect on the RVT-D behaviour.


OUTPUTBIT_0 00001 00 01 0 0 0 1 0 0 BITOUTPUTBIT_0 00002 00 02 0 0 0 1 0 0 BITOUTPUTBIT_0 00003 00 03 0 0 0 1 0 0 BITOUTPUTBIT_0 00004 00 04 0 0 0 1 0 0 BITOUTPUTBIT_0 00005 00 05 0 0 0 1 0 0 BITOUTPUTBIT_0 00006 00 06 0 0 0 1 0 0 BITOUTPUTBIT_0 00007 00 07 0 0 0 1 0 0 BITOUTPUTBIT_0 00008 00 08 0 0 0 1 0 0 BITOUTPUTBIT_1 00101 01 01 0 0 0 0 1 0 BITOUTPUTBIT_1 00102 01 02 0 0 0 0 1 0 BITOUTPUTBIT_1 00103 01 03 0 0 0 0 1 0 BITOUTPUTBIT_1 00104 01 04 0 0 0 0 1 0 BITOUTPUTBIT_1 00105 01 05 0 0 0 0 1 0 BITOUTPUTBIT_1 00106 01 06 0 0 0 0 1 0 BITOUTPUTBIT_1 00107 01 07 0 0 0 0 1 0 BITOUTPUTBIT_1 00108 01 08 0 0 0 0 1 0 BITOUTPUTBIT_2 00201 02 01 0 0 0 0 0 1 BITOUTPUTBIT_2 00202 02 02 0 0 0 0 0 1 BITOUTPUTBIT_2 00203 02 03 0 0 0 0 0 1 BITOUTPUTBIT_2 00204 02 04 0 0 0 0 0 1 BITOUTPUTBIT_2 00205 02 05 0 0 0 0 0 1 BITOUTPUTBIT_2 00206 02 06 0 0 0 0 0 1 BITOUTPUTBIT_2 00207 02 07 0 0 0 0 0 1 BITOUTPUTBIT_2 00208 02 08 0 0 0 0 0 1 BIT

General description

49

7.2 Input bits

This table contains free bytes for bit read testing. This has no effect on the RVT-D behaviour. Note (38): INPUTBIT_0 contains HEX value 0x55 Note (39): INPUTBIT_1 contains HEX value 0xAA Note (40): INPUTBIT_2 contains HEX value 0xFF


INPUTBIT_0 10001 00 01 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10002 00 02 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10003 00 03 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10004 00 04 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10005 00 05 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10006 00 06 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10007 00 07 0 0 0 0 0 0 Note (38) BITINPUTBIT_0 10008 00 08 0 0 0 0 0 0 Note (38) BITINPUTBIT_1 10101 01 01 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10102 01 02 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10103 01 03 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10104 01 04 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10105 01 05 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10106 01 06 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10107 01 07 0 0 0 0 0 0 Note (39) BITINPUTBIT_1 10108 01 08 0 0 0 0 0 0 Note (39) BITINPUTBIT_2 10201 02 01 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10202 02 02 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10203 02 03 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10204 02 04 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10205 02 05 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10206 02 06 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10207 02 07 0 0 0 0 0 0 Note (40) BITINPUTBIT_2 10208 02 08 0 0 0 0 0 0 Note (40) BIT

General description

50

8 DEVICE SPECIFIC MODBUS FUNCTIONS

8.1 Read Exception Status (function 7)

The read exception status function provides a simple and quick method for accessing alarm status conditions. The format of a read exception status (07) function is as follows:

The format of the exception status for the RVT-D is given hereafter:

A quick monitoring of bits 5 and 7 give the information that an alarm is present or that the fan relay is activated. Bits 0, 1, 2 give directly the index of the eldest alarm. Any change in these 3 bits means that a new alarm just occurred (see paragraph 5.4).

8.2 Report Slave ID (function 17)

The Report Slave ID function gives all information on the type of controller, serial number, type number. A free memory space may be used to store data needed for level 1 certification for an ABB higher-level system (capacitor bank, …). The format of the Report Slave ID (17) function is as follows:


RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Data value 1 byte Error check field CRC 2 bytes

QUERY

RVT-D exception status significationbit signification 0 10 alarm buffer index ( bit 0 )1 alarm buffer index ( bit 1 )2 alarm buffer index ( bit 2 )345 alarm relay status (normally closed) open closed67 presence of an alarm logged in the alarm buffer no alarm alarm logged

Slave address 1 byte Function 1 byte Error check field CRC 2 bytes

RESPONSESlave address 1 byte (echo of master's query) Function 1 byte (echo of master's query) Byte count Device specific (see below) Slave ID Device specific (see below) Run indicator status 0x00 or 0xFF (see below) Additional data Device specific (see below) Error check field CRC 2 bytes

51

The format of the Report Slave ID for the RVT-D is given hereafter:

RVT-Dbyte count 96slave ID 1 0 = RVT Run indicator status 2 00 = MAN or SET ; FF = AUTO 00/FFType 3 R

4 V5 T6 D78

Additional data 9 number of outputs 1210 soft version HI ex : 111 soft version LO ex : 412 serial number HH xx13 serial number HL xx14 serial number LH xx15 serial number LL xx16 ABB ID nr 1 2017 ABB ID nr 2 HI 018 ABB ID nr 2 LO 6519 ABB ID nr 3 HH xx20 ABB ID nr 3 HL xx21 ABB ID nr 3 LH xx22 ABB ID nr 3 LL xx23242526272829303132

0

''''

52

9 CRC GENERATION The Cyclical Redundancy Check (CRC) field is two bytes, containing a 16–bit binary value. The CRC value is calculated by the transmitting device, which appends the CRC to the message. The receiving device recalculates a CRC during receipt of the message, and compares the calculated value to the actual value it received in the CRC field. If the two values are not equal, an error results. Placing the CRC into the Message: When the 16–bit CRC (two 8–bit bytes) is transmitted in the message, the low-order byte will be transmitted first, followed by the high-order byte. Example: here is an example of calculating directly the CRC. /*----------------------------------------------------------------- FUNCTION :This routine calculates the crc high and low byte of a message. ----------------------------------------------------------------- INPUT PARAMETERS: buf -> Array containing message to be sent to controller start -> Start of loop in crc counter, usually 0. cnt -> Amount of bytes in message being sent to controller ----------------------------------------------------------------- OUTPUT : temp -> Returns crc byte for message. ----------------------------------------------------------------- */ word crc(byte *buf,word start,word cnt) { word i,j; word temp,temp2,flag; temp=0xFFFF; for (i=start; i<cnt; i++) { temp=temp ^ buf[i]; for (j=1; j<=8; j++) { flag=temp & 0x0001; temp=temp >> 1; if (flag) temp=temp ^ 0xA001; } } /* Reverse byte order. */ temp2=temp >> 8; temp=(temp << 8) | temp2; temp &= 0xFFFF; return(temp); }

53

10 APPENDIX

10.1 List of abbreviations ASCII American Standard Code for Information Interchange Baud rate Unit for measuring transmission speed in bits/s; Bit A binary digit, representing a one or zero Bus An electrical circuit over which data is transmitted Byte A whole number value represented by eight bits (0 to 255) Chassis or A connection to an electrically conductive housing or frame of a device. It may or may Chassis Ground not be connected to Earth Ground. Coil The telegram structure for Modbus transmission is implemented in registers (WORD)

or coils (BOOL). A coil may be either 8 or 16 bits in length. Common The voltage reference point of a circuit. It may or may not be connected to earth

ground, though it is generally assumed to be at zero volts, unless otherwise indicated. In floating circuits, the common is sometimes at a relatively high potential. This term is sometimes used interchangeably with the term “Ground” or GND

CRC Cyclic Redundancy Check. Complex error checking on a message block. CTS ClearToSend hardware handshaking signal. Used with RequestToSend. Earth or Earth Ground Global zero voltage reference point. Physical connection is made to the earth through

a grounding rod, water pipe or other reliable connection. Ground Voltage It may or may not be connected to earth ground, though it is generally assumed to be reference point at zero volts. Sometimes used interchangeably with the term “Common”. of a circuit. Handshaking method of data flow control for serial communications Hexadecimal or HEX A number system using a decimal 16 as its base. A single digit number in HEX ranges

from 0 to 15, represented by 0 to 9 and A to F. HMI Human-Machine Interface (formerly MMI) IndustrialIT Umbrella concept for ABB’s vision for enterprise automation. IndustrialIT Architecture The architecture of the Industrial IT system. The architecture defines how the system

is built, in terms of basic concepts, underlying technologies, system topology, modularity, and mechanisms for interaction between different parts of the system. It also defines concepts, rules, and guidelines that a component must comply with in order to fit in the Industrial IT system. A central feature of the IIT architecture is that information and functions are centered on Aspect Objects.

IndustrialIT Enabled A product that is Industrial IT enabled has been verified according to the process of Industrial IT certification. It has the right to use the “Industrial IT enabled” symbol.

Loopback A test used for checking functionality of a serial port, utilizing a test plug that connects send, receive and handshaking signals

Long Integer Analog value consisting of two consecutive 16-bit registers LRC Longitudinal Redundancy Check Measurement A measurement is a value computed by the controller through its analog and digital

inputs. Measurements can be read from the PQF-Manager front plate, or through the Modbus protocol.

Modbus adapter It is an optional small interface module through which the PQF-Manager is connected to an external Modbus serial communication bus. It performs an optical to RS485 conversion. The communication with the Modbus adapter is activated with a PQF-Manager parameter.

OPC OLE™ for Process Control. OPC is Plug-n-Play in the field of Automation and HMI. OLE™ for Process Control (OPC™) is the most standard way for connecting hardware and data devices with HMI client applications. OPC is a concept agreed upon by a committee of members from the OPC foundation. Most automation companies in the market place including ABB are members of this foundation. OPC uses state-of-the art technologies like COM, DCOM, ActiveX of Microsoft and makes development and programming easier. In the OPC world, there are two major types of applications:OPC Servers and OPC Clients.

OPC Servers OPC Server applications are used to collect data from the data sources like hardware devices. At the bottom level, the servers are mainly for reading inputs and writing

54

outputs of the data sources. At the upper level, the servers make the data available in a standard way to the OPC client applications.

OPC Clients The OPC Client applications can communicate directly with the OPC servers and get the data. This way OPC enhances the interface between client and server applications by providing a standard mechanism to communicate data from a data source to any client application.

Parameter A parameter is an operating data for the controller. Parameters can be read and programmed with the PQF-Manager front plate, or through the Modbus protocol.

Parity Simple method of data error checking performed at the byte level. May be user-specified as Odd, Even or None with most equipment and software.

PC Personal Computer Receive Incoming communication signal. (Rx) RTS RequestToSend hardware handshaking signal. Used with ClearToSend. RVT-D see Power IT Power Factor Controller RVT-D Rx See Receive PLC Programmable Logic Controller RTS Request To Send RTU Remote Terminal Unit Time-out Parameter specifying the max. wait time in ms. waiting for a response in the range

0..10000 ms. Signed Integer Whole number value represented by 16 bits (-32768 to 32767) Transmit Outgoing communication signal. (Tx) Tri-State The ability of a communications transmitter to turn its circuitry off, reducing the load on

the network Tx see Transmit Unsigned Integer Positive whole number value represented by 16 bits (0 to 65535) Word A group of 16 bits Xon/Xoff Software implementation of data flow control

10.2 References

- RS485 Modbus adapter operating manual - RVT-D Installation and Operation Instructions manual - Modicon Modbus Protocol Reference Guide (PI-MBUS-300 Rev. J).

55

56

ABB n.v. Power Quality Products Avenue Centrale, 10 Zoning Industriel de Jumet B-6040 Charleroi, Belgium Phone: +32 71 250 811 Fax: +32 71 344 007

This product has been certified by ABB Group as IndustrialIT EnabledTM.All product information is supplied in interactive electronic format, basedon ABB Aspect ObjectTM technology. Plug and ProduceTM installation and integration with other IndustrialITcertified products is available through the ABB Aspect IntegratorTM

Platform. While all care has been taken to ensure that the information contained inthis publication is correct, no responsibility can be accepted for anyinaccuracy. We reserve the right to alter or modify the informationcontained herein at any time in the light of technical or otherdevelopments. Technical specifications are valid under normal operatingconditions only. We do not accept any responsibility for any misuse of theproduct and cannot be held liable for indirect or consequential damages. 2G

CS

2120

11A

0065

2

007-

01-1

5 Th

e In

dust

rialIT

wor

dmar

k an

d al

l abo

ve-m

entio

ned

prod

uct n

ames

in th

e fo

rm P

ower

IT a

re re

gist

ered

or p

endi

ng tr

adem

arks

of A

BB.

Documents

Programmer’s manual RVT-D Modbus data table · 2018-05-10 · The Modbus protocol establishes the format for the master’s query by placing into it the device (or broadcast) address,