Programmer’s manual
RVT Modbus data table
1
1
INTRODUCTION........................................................................................... 4 1.1 1.2 1.3
2
MODBUS PROTOCOL OVERVIEW............................................................. 4 2.1 2.2 2.3 2.4
3
BANK SETTINGS ............................................................................................................................................... 32 PROTECTIONS ................................................................................................................................................. 34 EVENT LOGGING SETTINGS ............................................................................................................................. 36 INSTALLATION SETTINGS ................................................................................................................................. 37 USER SETTINGS .............................................................................................................................................. 37 I/O CONFIGURATION ........................................................................................................................................ 38 CHANGE MODE (AUTO-MAN-SET).............................................................................................................. 40 HIGHER LEVEL SYSTEM SETTINGS .................................................................................................................. 41 USER DATA STORAGE ..................................................................................................................................... 44 RVT MANUFACTURER INFORMATION .............................................................................................................. 45
OUTPUT & INPUT BITS ............................................................................. 47 7.1 7.2
8
MAIN MEASUREMENTS .................................................................................................................................... 18 EVENT LOGGING .............................................................................................................................................. 20 OUTPUT RELAYS OPERATIONS ........................................................................................................................ 22 ALARM LOGGING ............................................................................................................................................. 23 OUTPUTS / INPUTS .......................................................................................................................................... 25 HARMONIC VOLTAGE SPECTRUM .................................................................................................................... 27 SPECTRUM ANALYSIS OF THE CURRENT ......................................................................................................... 29 CLOCK REFERENCE......................................................................................................................................... 31
SETTINGS .................................................................................................. 32 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10
7
FORMATS......................................................................................................................................................... 14 ACCESS LEVELS .............................................................................................................................................. 15 MINIMUM AND MAXIMUM VALUES .................................................................................................................... 16 MODBUS DATA TABLE ..................................................................................................................................... 16
MEASUREMENTS...................................................................................... 18 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8
6
DATA ADDRESSES IN MODBUS MESSAGES ...................................................................................................... 7 SUPPORTED FUNCTION CODES ......................................................................................................................... 8 MASTER’S QUERIES AND SLAVE’S RESPONSES ................................................................................................ 9 READS AND WRITES TO MODBUS ADDRESSES (FUNCTIONS 1,2,3,4,5,6,15,16,22,23) ................................. 9 FETCH COMM EVENT COUNTER (FUNCTION 11) ............................................................................................. 10 FETCH COMM EVENT LOG (FUNCTION 12) ...................................................................................................... 10 DIAGNOSTICS FUNCTION AND SUBFUNCTIONS (FUNCTION 8) ........................................................................ 12 EXCEPTION RESPONSES ................................................................................................................................. 13
DATA ACCESS .......................................................................................... 14 4.1 4.2 4.3 4.4
5
OVERVIEW ......................................................................................................................................................... 4 TRANSACTIONS ON MODBUS NETWORKS ........................................................................................................ 5 SERIAL TRANSMISSION MODE .......................................................................................................................... 6 MODBUS MESSAGE FRAMING ........................................................................................................................... 7
MODBUS FUNCTION CODES ..................................................................... 7 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8
4
INTENDED AUDIENCE ......................................................................................................................................... 4 BEFORE YOU START .......................................................................................................................................... 4 HOW TO USE THIS MANUAL ............................................................................................................................... 4
OUTPUT BITS ................................................................................................................................................... 47 INPUT BITS ....................................................................................................................................................... 48
DEVICE SPECIFIC MODBUS FUNCTIONS............................................... 49 8.1 8.2
READ EXCEPTION STATUS (FUNCTION 7) ...................................................................................................... 49 REPORT SLAVE ID (FUNCTION 17) ................................................................................................................. 50
2
9
CRC GENERATION.................................................................................... 53
10 APPENDIX .................................................................................................. 54 10.1 10.2
LIST OF ABBREVIATIONS .................................................................................................................................. 54 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 Power Factor Controller RVT.
1.2 Before you start This manual describes the RVT Modbus data table. All information available from the keyboard of the RVT 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 consistently, a basic knowledge of it is needed. Functionality of the RVT, meaning of various measurements, logging of data are some particular aspects that should be familiar. Look in the RVT 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.
4
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.
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.
5
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: 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.
6
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.
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.
7
Address space 0XXXX 1XXXX 3XXXX 4XXXX
data readable / writable read & write Output bit read Input bit read Input word Output word read & write
Modbus name Coil Status Input Status Input Register 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.
Code 1
Function Read Coil Status
2
Read Input Status
3 4 5 6 7 8
Read Holding Registers Read Input Registers Force Single Coil Preset Single Register Read Exception Status Diagnostics
11
Fetch Comm. Event Ctr.
12 15
Fetch Comm. Event Log Force Multiple Coils
16
Preset Multiple Registers
17 22 23
Report Slave ID Mask Write 4X registers Read/Write 4X registers
Address range / Remark 0XXXX Reads the on/off status of discrete outputs 1XXXX Reads the on/off status of discrete inputs 4XXXX Reads contents of output registers 3XXXX Reads contents of input registers 0XXXX Sets the status of a discrete output 4XXXX Sets the value of a holding register device specific ( see chapter 8) Checks the communication system between the master and the slave Returns the amount of successful read/write operations on data points Returns log registers of communication events 0XXXX Sets the status of multiple discrete outputs 4XXXX Sets the value of multiple holding registers device specific ( see chapter 8) 4XXXX And / Or write of a holding register 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.
8
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 Function Starting data address Quantity of points Error check field CRC
1 byte 1 byte 2 bytes 2 bytes 2 bytes
RESPONSE Slave 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
The format of a force single coil (05) or a preset single register (06) function is as follows: QUERY Slave address Function Data address Data value Error check field CRC
1 byte 1 byte 2 bytes 2 bytes 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
The format of a force multiple coil (15) or a preset multiple registers (16) function is as follows: QUERY Slave address Function Data address Quantity of points Byte count Data values Error check field CRC
1 byte 1 byte 2 bytes 2 bytes 1 byte N bytes 2 bytes
RESPONSE Slave 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 9
The format of a read/write multiple registers (23) function is as follows: QUERY Slave address Function Read data address Read quantity of points Write data address Write quantity of points Byte count Write data values Error check field CRC
1 byte 1 byte 2 bytes 2 bytes 2 bytes 2 bytes 1 byte N bytes 2 bytes
RESPONSE Slave 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
The format of a Mask/write register (22) function is as follows: QUERY Slave address Function Data address And mask Or mask Error check field CRC
1 byte 1 byte 2 bytes 2 bytes 2 bytes 2 bytes
RESPONSE Slave 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 Function Error check field CRC
1 byte 1 byte 2 bytes
RESPONSE Slave address Function Status word Event counter Error check field CRC
1 byte (echo of master's query) 1 byte (echo of master's query) 2 bytes (0) 2 bytes 2 bytes
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: QUERY Slave address Function Error check field CRC
1 byte 1 byte 2 bytes
RESPONSE Slave address Function Byte count Status word Event counter Bus message counter Event log buffer Error check field CRC
1 byte (echo of master's query) 1 byte (echo of master's query) 1 byte 2 bytes (0) 2 bytes 2 bytes N bytes 2 bytes 10
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 0 1 2 3 4 5 6 7
Contents Not Used Communications Error Not Used Not Used Character Overrun Currently in Listen Only Mode Broadcast Received 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 0 1 2 3 4 5 6 7
Contents Read Exception Sent (Exception Codes 1-3) Slave Abort Exception Sent (Exception Code 4) Not used Not used Write Timeout Error Occurred Currently in Listen Only Mode 1 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. 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.
11
3.7 Diagnostics function and subfunctions (function 8) The format of a diagnostics (08) function query is as follows: QUERY Slave address Function Subfunction Data field Error check field CRC
1 byte 1 byte 2 bytes 2 bytes 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.
12
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 02 ILLEGAL DATA ADDRESS
The function code received in the query is not an allowable action for the slave device (see paragraph 3.2). 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 13
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 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’. 14
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 ‘lName’. Non volatile write accessible variable are expressed as ‘lNVName’. 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:
|-------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 : e : m :
1 sign bit; explains the sign (0 = positive, 1 = negative) 8 bits two’s complement exponent. The true value is the exponent minus 127. 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).
s The value may be computed using
: (-1)
(1.m 22−0 )2
e - 127
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 of the RVT. SET MODE: the RVT must be in Set Mode to allow parameters settings modifications. LOCKING SWITCH: the locking switch have to be released BANK SETTINGS: the parameter bank settings must be set to Unlocked.
15
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 keyboard are forbidden. Parameters may meanwhile be modified by Modbus access only (provided all others access levels are fulfilled).
Variable bNVMode bKeyboard ( bit 7 ) bNVBanklocked bNVModbusLocking
locked 1 : AUTO 2 : MAN 0 : Lock switch pushed 1 : Bank settings are locked 1 : Keyboard locked
Unlocked 4 : SET 1 : Lock switch released 0 : Bank settings are unlocked 0 : Keyboard unlocked
Comment 1: The following access level could be modified through Modbus or through the RVT keyboard: • Mode • Bank settings • Modbus Lock but when the RVT is locked by the locking switch, the access can not be modified through Modbus or through RVT keyboard. It can only be modified physically by pressing the locking switch located at the RVT back side. Comment 2: The RVT returns automatically to AUTO mode when no key is pressed or no writing are done through Modbus for more than five minutes.
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.
16
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.
17
5 MEASUREMENTS 5.1 Main measurements This table contains measurements done by the RVT except harmonics spectra that can be found in paragraph 5.6 and 5.7. Most of these measurements are converted to IEEE float number for easy handling. General description Measurements
Description
Variable
General rms voltage Measurements THDU Frequency Fundamental voltage rms current THDI Fundamental current reactive current active current cos phi Power factor active power reactive power apparent power missing reactive power missing steps temperature input 1 temperature input 2 presence of T1 presence of T2
Variable name ndUrms ndUrms ndTHDU ndTHDU ndFrequency ndFrequency ndU1 ndU1 ndIrms ndIrms ndTHDI ndTHDI ndI1 ndI1 ndISinPhi ndISinPhi ndICosPhi ndICosPhi ndCosPhi ndCosPhi ndPF ndPF ndP ndP ndQ ndQ ndS ndS ndQMiss ndQMiss ndNMiss ndNMiss ndT[0] ndT[0] ndT[1] ndT[1] bTPresent[0] bTPresent[1]
Modbus Register 30001 30002 30003 30004 30005 30006 30007 30008 30009 30010 30011 30012 30013 30014 30015 30016 30017 30018 30019 30020 30021 30022 30023 30024 30025 30026 30027 30028 30029 30030 30031 30032 30033 30034 30035 30036 30037 30038
Table number 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
offset 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
Units
Datatype
VOLT VOLT PERCENT PERCENT HERTZ HERTZ VOLT VOLT AMPERE AMPERE PERCENT PERCENT AMPERE AMPERE AMPERE AMPERE AMPERE AMPERE see Note (1) see Note (1) see Note (1) see Note (1) WATT WATT Var Var VA VA Var Var STEPS STEPS °C °C °C °C see Note (2) see Note (2)
FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high FLOAT/ low FLOAT/ high BYTE BYTE
18
Note (1): Cos phi values are represented in a particular format shown in the following table:
cos phi 0.1 ind 0.7 ind 1 0.7 cap 0.1 cap disabled
value 0.1 0.7 1 1.3 1.9 0
Positive values are for passive loads. Negative values represent regenerative mode. Note (2): Temperature probe present: Temperature probe not connected:
0 1
19
5.2 Event logging This table contains recorded values by the RVT through the event logging function (for more information, please refer to the RVT Installation and Operating Instructions manual). Each duration is given in seconds. General description
Description
Variable
Event Logging
Peak / duration Urms peak Accumulated peak Urms duration Irms peak Accumulated peak Irms duration peak active power Accumulated peak active power duration peak reactive power Accumulated peak reactive power duration peak missing reactive power Accumulated peak missing reactive power duration peak apparent power Accumulated peak apparent power duration peak THDU Accumulated peak THDU duration peak THDI Accumulated peak THDI duration
Variable name ndNVUrmsPeak ndNVUrmsPeak dwNVUrmsDuration dwNVUrmsDuration ndNVIrmsPeak ndNVIrmsPeak dwNVIrmsDuration dwNVIrmsDuration ndNVPPeak ndNVPPeak dwNVPDuration dwNVPDuration ndNVQPeak ndNVQPeak dwNVQDuration dwNVQDuration ndNVQMissPeak ndNVQMissPeak dwNVQMissDuration dwNVQMissDuration ndNVSPeak ndNVSPeak dwNVSDuration dwNVSDuration ndNVTHDUPeak ndNVTHDUPeak dwNVTHDUDuration dwNVTHDUDuration ndNVTHDIPeak ndNVTHDIPeak dwNVTHDIDuration dwNVTHDIDuration
Modbus register
Table number
offset
30101 30102 30103 30104 30105 30106 30107 30108 30109 30110 30111 30112 30113 30114 30115 30116 30117 30118 30119 30120 30121 30122 30123 30124 30125 30126 30127 30128 30129 30130 30131 30132
01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Units
Datatype
VOLT VOLT SECOND SECOND AMPERE AMPERE SECOND SECOND WATT WATT SECOND SECOND VAR VAR SECOND SECOND VAR VAR SECOND SECOND VA VA SECOND SECOND PERCENT PERCENT SECOND SECOND PERCENT PERCENT SECOND SECOND
FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high
20
peak frequency max Accumulated peak frequency max duration peak frequency min Accumulated peak frequency min duration peak Temperature max input 1 Accumulated Temperature max input 1 duration peak Temperature min input 1 Accumulated Temperature min input 1 duration peak Temperature max input 2 Accumulated Temperature max input 2 duration peak Temperature min input 2 Accumulated Temperature min input 2 duration
ndNVFMax ndNVFMax dwNVFDurationMax dwNVFDurationMax ndNVFMin ndNVFMin dwNVFDurationMin dwNVFDurationMin ndNVTMax[0] ndNVTMax[0] dwNVTDurationMax[0] dwNVTDurationMax[0] ndNVTMin[0] ndNVTMin[0] dwNVTDurationMin[0] dwNVTDurationMin[0] ndNVTMax[1] ndNVTMax[1] dwNVTDurationMax[1] dwNVTDurationMax[1] ndNVTMin[1] ndNVTMin[1] dwNVTDurationMin[1] dwNVTDurationMin[1]
30133 30134 30135 30136 30137 30138 30139 30140 30141 30142 30143 30144 30145 30146 30147 30148 30149 30150 30151 30152 30153 30154 30155 30156
01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
HERTZ HERTZ SECOND SECOND HERTZ HERTZ SECOND SECOND °C °C SECOND SECOND °C °C SECOND SECOND °C °C SECOND SECOND °C °C SECOND SECOND
FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high FLOAT/ low FLOAT/ high unsigned LONG / low unsigned LONG / high
21
5.3 Output relays operations This table contains general monitoring data from the RVT. The number of operations of each output capacitor relay is recorded since the RVT was manufactured. General description
Description
Bank monitoring
Number of operations
Variable number of operation output 1 number of operation output 2 number of operation output 3 number of operation output 4 number of operation output 5 number of operation output 6 number of operation output 7 number of operation output 8 number of operation output 9 number of operation output 10 number of operation output 11 number of operation output 12
Variable name dwNVOperation[0] dwNVOperation[0] dwNVOperation[1] dwNVOperation[1] dwNVOperation[2] dwNVOperation[2] dwNVOperation[3] dwNVOperation[3] dwNVOperation[4] dwNVOperation[4] dwNVOperation[5] dwNVOperation[5] dwNVOperation[6] dwNVOperation[6] dwNVOperation[7] dwNVOperation[7] dwNVOperation[8] dwNVOperation[8] dwNVOperation[9] dwNVOperation[9] dwNVOperation[10] dwNVOperation[10] dwNVOperation[11] dwNVOperation[11]
Modbus register
Table number
offset
30201 30202 30203 30204 30205 30206 30207 30208 30209 30210 30211 30212 30213 30214 30215 30216 30217 30218 30219 30220 30221 30222 30223 30224
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Units
Datatype
NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT NO UNIT
unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high unsigned LONG / low unsigned LONG / high
22
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.
General description
Description
Bank monitoring
Alarm buffer
Variable
Variable name
Modbus register
Units Table number
Datatype
offset
buffer 0
bAlarmLogType[0]
30301
03
01
Note (3)
BYTE
buffer 1
bAlarmLogType[1]
30302
03
02
Note (3)
BYTE
buffer 2
bAlarmLogType[2]
30303
03
03
Note (3)
BYTE
buffer 3
bAlarmLogType[3]
30304
03
04
Note (3)
BYTE
buffer 4
bAlarmLogType[4]
30305
03
05
Note (3)
BYTE
elapsed time of alarm in buffer 0
dwAlarmLogTime[0]
30306
03
06
SECOND
unsigned LONG / low
dwAlarmLogTime[0]
30307
03
07
SECOND
unsigned LONG / high
elapsed time of alarm in buffer 1
dwAlarmLogTime[1]
30308
03
08
SECOND
unsigned LONG / low
dwAlarmLogTime[1]
30309
03
09
SECOND
unsigned LONG / high
dwAlarmLogTime[2]
30310
03
10
SECOND
unsigned LONG / low
dwAlarmLogTime[2]
30311
03
11
SECOND
unsigned LONG / high
dwAlarmLogTime[3]
30312
03
12
SECOND
unsigned LONG / low
dwAlarmLogTime[3]
30313
03
13
SECOND
unsigned LONG / high
dwAlarmLogTime[4]
30314
03
14
SECOND
unsigned LONG / low
dwAlarmLogTime[4]
30315
03
15
SECOND
unsigned LONG / high
bAlarmLogIdx
30316
03
16
Note (3)
BYTE
elapsed time of alarm in buffer 2 elapsed time of alarm in buffer 3 elapsed time of alarm in buffer 4 buffer index
23
Note (3): The kind of alarm is given by the following table:
type of alarm PROTECTION COS PHI (insufficient available reactive power) 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 EXTERNAL (external input protection activated) PROTECTION U MIN (undervoltage detection)
value 1 2 3 4 5 6 7 8 9
24
5.5 Outputs / Inputs This table contains inputs / outputs status. General description Outputs-Inputs
Description
Variable
Variable name
Modbus register
Table number
offset
Units
Datatype
Relays outputs
Outputs status
P2
30401
04
01
Note (4)
unsigned INT
Keyboard
keyboard status
bKeyboard
30402
04
02
Note (5)
BYTE
Note (4): Outputs include relay outputs as well as the fan and the alarm relays. - ‘1’ means that the relay is not activated (output opened, alarm relay closed, fan relay opened). - ‘0’ means that the relay is activated (output closed, alarm relay opened, fan relay closed).
Outputs P2 Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 Bit 9 Bit 10 Bit 11 Bit 12 Bit 13 Bit 14 Bit 15
1 2 3 4 5 6 7 8 9 10 11 12 Alarm Fan Not used Not used 25
Note (5): Inputs refer to the buttons status of the RVT keyboard. Meanings of bits are given in the following table.
Keyboard Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
ESC HELP OK MINUS PLUS Not used Not used LOCK
pushed
released
1 1 1 1 1
0 0 0 0 0
0
1
26
5.6 Harmonic voltage spectrum This table contains voltage harmonics from 2nd up to 49th and fundamental voltage. General description
Description
Spectrum
U spectrum
Variable
Variable name
Modbus register
Table number
offset
Units
Datatype
harmonic 1
wUSpectrum[1]
30501
05
01
Note (6)
unsigned INT
harmonic 2
wUSpectrum[2]
30502
05
02
Note (6)
unsigned INT
harmonic 3
wUSpectrum[3]
30503
05
03
Note (6)
unsigned INT
harmonic 4
wUSpectrum[4]
30504
05
04
Note (6)
unsigned INT
harmonic 5
wUSpectrum[5]
30505
05
05
Note (6)
unsigned INT
harmonic 6
wUSpectrum[6]
30506
05
06
Note (6)
unsigned INT
harmonic 7
wUSpectrum[7]
30507
05
07
Note (6)
unsigned INT
harmonic 8
wUSpectrum[8]
30508
05
08
Note (6)
unsigned INT
harmonic 9
wUSpectrum[9]
30509
05
09
Note (6)
unsigned INT
harmonic 10
wUSpectrum[10]
30510
05
10
Note (6)
unsigned INT
harmonic 11
wUSpectrum[11]
30511
05
11
Note (6)
unsigned INT
harmonic 12
wUSpectrum[12]
30512
05
12
Note (6)
unsigned INT
harmonic 13
wUSpectrum[13]
30513
05
13
Note (6)
unsigned INT
harmonic 14
wUSpectrum[14]
30514
05
14
Note (6)
unsigned INT
harmonic 15
wUSpectrum[15]
30515
05
15
Note (6)
unsigned INT
harmonic 16
wUSpectrum[16]
30516
05
16
Note (6)
unsigned INT
harmonic 17
wUSpectrum[17]
30517
05
17
Note (6)
unsigned INT
harmonic 18
wUSpectrum[18]
30518
05
18
Note (6)
unsigned INT
harmonic 19
wUSpectrum[19]
30519
05
19
Note (6)
unsigned INT
harmonic 20
wUSpectrum[20]
30520
05
20
Note (6)
unsigned INT
harmonic 21
wUSpectrum[21]
30521
05
21
Note (6)
unsigned INT
harmonic 22
wUSpectrum[22]
30522
05
22
Note (6)
unsigned INT
harmonic 23
wUSpectrum[23]
30523
05
23
Note (6)
unsigned INT
harmonic 24
wUSpectrum[24]
30524
05
24
Note (6)
unsigned INT
harmonic 25
wUSpectrum[25]
30525
05
25
Note (6)
unsigned INT
harmonic 26
wUSpectrum[26]
30526
05
26
Note (6)
unsigned INT
harmonic 27
wUSpectrum[27]
30527
05
27
Note (6)
unsigned INT
harmonic 28
wUSpectrum[28]
30528
05
28
Note (6)
unsigned INT
27
harmonic 29
wUSpectrum[29]
30529
05
29
Note (6)
unsigned INT
harmonic 30
wUSpectrum[30]
30530
05
30
Note (6)
unsigned INT
harmonic 31
wUSpectrum[31]
30531
05
31
Note (6)
unsigned INT
harmonic 32
wUSpectrum[32]
30532
05
32
Note (6)
unsigned INT
harmonic 33
wUSpectrum[33]
30533
05
33
Note (6)
unsigned INT
harmonic 34
wUSpectrum[34]
30534
05
34
Note (6)
unsigned INT
harmonic 35
wUSpectrum[35]
30535
05
35
Note (6)
unsigned INT
harmonic 36
wUSpectrum[36]
30536
05
36
Note (6)
unsigned INT
harmonic 37
wUSpectrum[37]
30537
05
37
Note (6)
unsigned INT
harmonic 38
wUSpectrum[38]
30538
05
38
Note (6)
unsigned INT
harmonic 39
wUSpectrum[39]
30539
05
39
Note (6)
unsigned INT
harmonic 40
wUSpectrum[40]
30540
05
40
Note (6)
unsigned INT
harmonic 41
wUSpectrum[41]
30541
05
41
Note (6)
unsigned INT
harmonic 42
wUSpectrum[42]
30542
05
42
Note (6)
unsigned INT
harmonic 43
wUSpectrum[43]
30543
05
43
Note (6)
unsigned INT
harmonic 44
wUSpectrum[44]
30544
05
44
Note (6)
unsigned INT
harmonic 45
wUSpectrum[45]
30545
05
45
Note (6)
unsigned INT
harmonic 46
wUSpectrum[46]
30546
05
46
Note (6)
unsigned INT
harmonic 47
wUSpectrum[47]
30547
05
47
Note (6)
unsigned INT
harmonic 48
wUSpectrum[48]
30548
05
48
Note (6)
unsigned INT
harmonic 49
wUSpectrum[49]
30549
05
49
Note (6)
unsigned INT
Note (6): The value given is a percentage of the fundamental multiplied by 10 (ex: 100%: 1000)
28
5.7 Spectrum analysis of the current This table contains current harmonics from 2nd up to 49th and fundamental current.
General description
Description
Spectrum
I spectrum
Variable
Variable name
Modbus register
Table number
offset
Units
Datatype
harmonic 1
wISpectrum[1]
30601
06
01
Note (7)
unsigned INT
harmonic 2
wISpectrum[2]
30602
06
02
Note (7)
unsigned INT
harmonic 3
wISpectrum[3]
30603
06
03
Note (7)
unsigned INT
harmonic 4
wISpectrum[4]
30604
06
04
Note (7)
unsigned INT
harmonic 5
wISpectrum[5]
30605
06
05
Note (7)
unsigned INT
harmonic 6
wISpectrum[6]
30606
06
06
Note (7)
unsigned INT
harmonic 7
wISpectrum[7]
30607
06
07
Note (7)
unsigned INT
harmonic 8
wISpectrum[8]
30608
06
08
Note (7)
unsigned INT
harmonic 9
wISpectrum[9]
30609
06
09
Note (7)
unsigned INT
harmonic 10
wISpectrum[10]
30610
06
10
Note (7)
unsigned INT
harmonic 11
wISpectrum[11]
30611
06
11
Note (7)
unsigned INT
harmonic 12
wISpectrum[12]
30612
06
12
Note (7)
unsigned INT
harmonic 13
wISpectrum[13]
30613
06
13
Note (7)
unsigned INT
harmonic 14
wISpectrum[14]
30614
06
14
Note (7)
unsigned INT
harmonic 15
wISpectrum[15]
30615
06
15
Note (7)
unsigned INT
harmonic 16
wISpectrum[16]
30616
06
16
Note (7)
unsigned INT
harmonic 17
wISpectrum[17]
30617
06
17
Note (7)
unsigned INT
harmonic 18
wISpectrum[18]
30618
06
18
Note (7)
unsigned INT
harmonic 19
wISpectrum[19]
30619
06
19
Note (7)
unsigned INT
harmonic 20
wISpectrum[20]
30620
06
20
Note (7)
unsigned INT
harmonic 21
wISpectrum[21]
30621
06
21
Note (7)
unsigned INT
harmonic 22
wISpectrum[22]
30622
06
22
Note (7)
unsigned INT
harmonic 23
wISpectrum[23]
30623
06
23
Note (7)
unsigned INT
harmonic 24
wISpectrum[24]
30624
06
24
Note (7)
unsigned INT
harmonic 25
wISpectrum[25]
30625
06
25
Note (7)
unsigned INT
harmonic 26
wISpectrum[26]
30626
06
26
Note (7)
unsigned INT
harmonic 27
wISpectrum[27]
30627
06
27
Note (7)
unsigned INT
harmonic 28
wISpectrum[28]
30628
06
28
Note (7)
unsigned INT
harmonic 29
wISpectrum[29]
30629
06
29
Note (7)
unsigned INT
29
harmonic 30
wISpectrum[30]
30630
06
30
Note (7)
unsigned INT
harmonic 31
wISpectrum[31]
30631
06
31
Note (7)
unsigned INT
harmonic 32
wISpectrum[32]
30632
06
32
Note (7)
unsigned INT
harmonic 33
wISpectrum[33]
30633
06
33
Note (7)
unsigned INT
harmonic 34
wISpectrum[34]
30634
06
34
Note (7)
unsigned INT
harmonic 35
wISpectrum[35]
30635
06
35
Note (7)
unsigned INT
harmonic 36
wISpectrum[36]
30636
06
36
Note (7)
unsigned INT
harmonic 37
wISpectrum[37]
30637
06
37
Note (7)
unsigned INT
harmonic 38
wISpectrum[38]
30638
06
38
Note (7)
unsigned INT
harmonic 39
wISpectrum[39]
30639
06
39
Note (7)
unsigned INT
harmonic 40
wISpectrum[40]
30640
06
40
Note (7)
unsigned INT
harmonic 41
wISpectrum[41]
30641
06
41
Note (7)
unsigned INT
harmonic 42
wISpectrum[42]
30642
06
42
Note (7)
unsigned INT
harmonic 43
wISpectrum[43]
30643
06
43
Note (7)
unsigned INT
harmonic 44
wISpectrum[44]
30644
06
44
Note (7)
unsigned INT
harmonic 45
wISpectrum[45]
30645
06
45
Note (7)
unsigned INT
harmonic 46
wISpectrum[46]
30646
06
46
Note (7)
unsigned INT
harmonic 47
wISpectrum[47]
30647
06
47
Note (7)
unsigned INT
harmonic 48
wISpectrum[48]
30648
06
48
Note (7)
unsigned INT
harmonic 49
wISpectrum[49]
30649
06
49
Note (7)
unsigned INT
Note (7): The value given is a percentage of the fundamental multiplied by 10 (ex 100%: 1000)
30
5.8 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. Comment: please note that this clock reference is not a real time clock but counters incremented with the clock of the RVT. Counters are reset to zero when the RVT is reset. After one complete day, counters are reset to 0.
General description
Description
Timings
clock reference
Variable
Variable name
Modbus register
Table number
offset
Units
Datatype
seconds since last reset
bSecond
39801
98
01
SECONDS
BYTE
minutes since last reset
bMinute
39802
98
02
MINUTES
BYTE
hours since last reset
bHour
39803
98
03
HOURS
BYTE
31
6 SETTINGS 6.1 Bank settings This table contains bank settings except protection settings which can be found in paragraph 6.2. General Description
Description
Settings
Bank settings
Variable V nominal
Variable name
Modbus register
Table number
offset
Access Set LS BL
Units R
NV
Datatype
C
ndNVUNominal
40001
00
01
X
X
X
X
VOLT
FLOAT/ low
ndNVUNominal
40002
00
02
X
X
X
X
VOLT
FLOAT/ high
V scale
ndNVUScale
40003
00
03
X
X
X
X
No Unit
FLOAT/ low
ndNVUScale
40004
00
04
X
X
X
X
No Unit
FLOAT/ high
1Ph/3Ph
bNVNumberPhase
40005
00
05
X
X
X
X
Note (8)
BYTE
Q step
ndNVQStep
40006
00
06
X
X
X
X
VAR
FLOAT/ low
ndNVQStep
40007
00
07
X
X
X
X
VAR
FLOAT/ high
size output 1
NVRelayOut[0].bSize
40008
00
08
X
X
X
X
STEPS
BYTE
status output 1
NVRelayOut[0].bStatus
40009
00
09
X
X
X
X
Note (9)
BYTE
size output 2
NVRelayOut[1].bSize
40010
00
10
X
X
X
X
STEPS
BYTE
status output 2
NVRelayOut[1].bStatus
40011
00
11
X
X
X
X
Note (9)
BYTE
size output 3
NVRelayOut[2].bSize
40012
00
12
X
X
X
X
STEPS
BYTE
status output 3
NVRelayOut[2].bStatus
40013
00
13
X
X
X
X
Note (9)
BYTE
size output 4
NVRelayOut[3].bSize
40014
00
14
X
X
X
X
STEPS
BYTE
status output 4
NVRelayOut[3].bStatus
40015
00
15
X
X
X
X
Note (9)
BYTE
size output 5
NVRelayOut[4].bSize
40016
00
16
X
X
X
X
STEPS
BYTE
status output 5
NVRelayOut[4].bStatus
40017
00
17
X
X
X
X
Note (9)
BYTE
size output 6
NVRelayOut[5].bSize
40018
00
18
X
X
X
X
STEPS
BYTE
status output 6
NVRelayOut[5].bStatus
40019
00
19
X
X
X
X
Note (9)
BYTE
size output 7
NVRelayOut[6].bSize
40020
00
20
X
X
X
X
STEPS
BYTE
status output 7
NVRelayOut[6].bStatus
40021
00
21
X
X
X
X
Note (9)
BYTE
size output 8
NVRelayOut[7].bSize
40022
00
22
X
X
X
X
STEPS
BYTE
status output 8
NVRelayOut[7].bStatus
40023
00
23
X
X
X
X
Note (9)
BYTE
size output 9
NVRelayOut[8].bSize
40024
00
24
X
X
X
X
STEPS
BYTE
status output 9
NVRelayOut[8].bStatus
40025
00
25
X
X
X
X
Note (9)
BYTE
size output 10
NVRelayOut[9].bSize
40026
00
26
X
X
X
X
STEPS
BYTE
status output 10
NVRelayOut[9].bStatus
40027
00
27
X
X
X
X
Note (9)
BYTE
32
size output 11
NVRelayOut[10].bSize
40028
00
28
X
X
X
X
STEPS
status output 11
NVRelayOut[10].bStatus
40029
00
29
X
X
X
X
Note (9)
BYTE
size output 12
NVRelayOut[11].bSize
40030
00
30
X
X
X
X
STEPS
BYTE
status output 12
NVRelayOut[11].bStatus
40031
00
31
X
X
X
X
Note (9)
BYTE
Lin / Circ
bNVLinearCircular
40032
00
32
X
X
X
X
Note (10)
BYTE
Prog/direct
bNVProgDirect
40033
00
33
X
X
X
X
Note (11)
BYTE
Normal / Integral
bNVNormalIntegral
40034
00
34
X
X
X
X
Note (12)
BYTE
delay ON
dwNVDelayON
40035
00
35
X
X
X
X
SECOND
unsigned LONG / low
dwNVDelayON
40036
00
36
X
X
X
X
SECOND
unsigned LONG / high
delay OFF
dwNVDelayOFF
40037
00
37
X
X
X
X
SECOND
unsigned LONG / low
dwNVDelayOFF
40038
00
38
X
X
X
X
SECOND
unsigned LONG / high
dwNVDelayReset
40039
00
39
X
X
X
X
SECOND
unsigned LONG / low
dwNVDelayReset
40040
00
40
X
X
X
X
SECOND
unsigned LONG / high
dwNVDelayPrint
40041
00
41
X
X
X
X
SECOND
unsigned LONG / low
dwNVDelayPrint
40042
00
42
X
X
X
X
SECOND
unsigned LONG / high
Delay reset Delay print
BYTE
Note (8): Number of phases of the bank and voltage measurement connection: BNVNumberPhase 0 1 2
Signification 1 Phase 3 Phase / phase to phase 3 Phase / phase to neutral
Note (9): Outputs status: NVRelayOut[ ].bStatus 0 1 2
Signification Fixed OFF Enabled (for automatic compensation) Fixed ON
33
Note (10): bNVLinearCircular 0 1 Note (11): bNVProgDirect 0 1
Signification Linear Circular
Signification Progressive Direct
Note (12): bNVNormalIntegral 0 1
Signification Normal Integral
6.2 Protections This table contains protection levels against undervoltage, overvoltage, prohibitive harmonics, overtemperature and to enable an external protection: Once a protection level is reached, the following actions occur: • All the capacitor steps are switched OFF. • An alarm message appears on the display and is recorded. • The alarm relay closes. • The fan relay closes (valid for temperature protection only). The alarm message is recorded (for more information, please refer to paragraph 5.4)
34
General description
Description
Settings
Protections
Variable
Variable name
Modbus register
Table number
offset
40101
01
01
V min prot.
ndNVUMinProtect ndNVUMinProtect
40102
01
V max prot.
ndNVUMaxProtect
40103
01
ndNVUMaxProtect
40104
01
T1 start fan
ndNVTStartFan[0]
40105
01
ndNVTStartFan[0]
40106
01
T1 max prot.
ndNVTMaxProtect[0]
40107
01
ndNVTMaxProtect[0]
40108
01
ndNVTStartFan[1]
40109
ndNVTStartFan[1]
40110
ndNVTMaxProtect[1] ndNVTMaxProtect[1]
T2 start fan T2 max prot. THDV max prot. Ext. prot.
Access Set LS BL
R
NV
Units
Datatype
C
X
X
X
X
VOLT
FLOAT/ low
02
X
X
X
X
VOLT
FLOAT/ high
03
X
X
X
X
VOLT
FLOAT/ low
04
X
X
X
X
VOLT
FLOAT/ high
05
X
X
X
X
°C
FLOAT/ low
06
X
X
X
X
°C
FLOAT/ high
07
X
X
X
X
°C
FLOAT/ low
08
X
X
X
X
°C
FLOAT/ high
01
09
X
X
X
X
°C
FLOAT/ low
01
10
X
X
X
X
°C
FLOAT/ high
40111
01
11
X
X
X
X
°C
FLOAT/ low
40112
01
12
X
X
X
X
°C
FLOAT/ high
ndNVTHDUMaxProtect
40113
01
13
X
X
X
X
PERCENT
FLOAT/ low
ndNVTHDUMaxProtect
40114
01
14
X
X
X
X
PERCENT
FLOAT/ high
bNVExternalAlarm
40115
01
15
X
X
X
X
Note (13)
BYTE
Note (13): Each protection can be set as disabled (default value) by adjusting its value equal to 0.
35
6.3 Event logging settings This table contains the level related to the event logging function (please refer to paragraph 5.2.). General description
Description
Variable
Settings
Event Logging Vrms Threshold Settings
Modbus register
Table number
offset
ndNVUrmsThreshold
40201
02
01
X
X
VOLT
FLOAT/ low
ndNVUrmsThreshold
40202
02
02
X
X
VOLT
FLOAT/ high
ndNVIrmsThreshold
40203
02
03
X
X
AMPERE FLOAT/ low
ndNVIrmsThreshold
40204
02
04
X
X
AMPERE FLOAT/ high
ndNVPThreshold
40205
02
05
X
X
WATT
FLOAT/ low
ndNVPThreshold
40206
02
06
X
X
WATT
FLOAT/ high
reactive power threshold
ndNVQThreshold
40207
02
07
X
X
Var
FLOAT/ low
ndNVQThreshold
40208
02
08
X
X
Var
FLOAT/ high
missing reactive power threshold
ndNVQMissThreshold
40209
02
09
X
X
Var
FLOAT/ low
ndNVQMissThreshold
40210
02
10
X
X
Var
FLOAT/ high
apparent power threshold
ndNVSThreshold
40211
02
11
X
X
VA
FLOAT/ low
ndNVSThreshold
40212
02
12
X
X
VA
FLOAT/ high
temperature T1 threshold max
ndNVTThresholdMax[0]
40213
02
13
X
X
°C
FLOAT/ low
ndNVTThresholdMax[0]
40214
02
14
X
X
°C
FLOAT/ high
temperature T1 threshold min
ndNVTThresholdMin[0]
40215
02
15
X
X
°C
FLOAT/ low
ndNVTThresholdMin[0]
40216
02
16
X
X
°C
FLOAT/ high
temperature T2 threshold max
ndNVTThresholdMax[1]
40217
02
17
X
X
°C
FLOAT/ low
ndNVTThresholdMax[1]
40218
02
18
X
X
°C
FLOAT/ high
ndNVTThresholdMin[1]
40219
02
19
X
X
°C
FLOAT/ low
ndNVTThresholdMin[1]
40220
02
20
X
X
°C
FLOAT/ high
ndNVFThresholdMax
40221
02
21
X
X
HERTZ
FLOAT/ low
ndNVFThresholdMax
40222
02
22
X
X
HERTZ
FLOAT/ high
ndNVFThresholdMin
40223
02
23
X
X
HERTZ
FLOAT/ low
ndNVFThresholdMin
40224
02
24
X
X
HERTZ
FLOAT/ high
THDV threshold
ndNVTHDUThreshold
40225
02
25
X
X
PERCENT FLOAT/ low
ndNVTHDUThreshold
40226
02
26
X
X
PERCENT FLOAT/ high
THDI threshold
ndNVTHDIThreshold
40227
02
27
X
X
PERCENT FLOAT/ low
ndNVTHDIThreshold
40228
02
28
X
X
PERCENT FLOAT/ high
Irms Threshold active power threshold
temperature T2 threshold min frequency max threshold frequency min threshold
Variable name
Access Set LS BL
Units R
NV
Datatype
C
36
6.4 Installation settings This table contains installation parameters. General description
Description
Variable
Settings
Installation settings
CT scaling C/k Phase Shift
Variable name
Modbus register
Table number
offset
Access Set LS BL R NV
Units
Datatype
ndNVIScale
40301
03
01
X
X
X
No unit
FLOAT/ low
ndNVIScale
40302
03
02
X
X
X
No unit
FLOAT/ high
ndNVC_k
40303
03
03
X
X
X
AMPERE
FLOAT/ low
ndNVC_k
40304
03
04
X
X
X
AMPERE
FLOAT/ high
ndNVPhaseDelay
40305
03
05
X
X
X
DEGREE
FLOAT/ low
ndNVPhaseDelay
40306
03
06
X
X
X
DEGREE
FLOAT/ high
C
6.5 User settings This table contains additional installation parameters which are dedicated to the installer and/or the user.
General description
Description
Settings
User settings
Variable
Variable name
Modbus register
Table number
offset
Access Set LS BL
R
NV
Units
Datatype
C
Target cos phi
ndNVTargetCosPhi
40401
04
01
X
X
X
Note (1)
FLOAT/ low
ndNVTargetCosPhi
40402
04
02
X
X
X
Note (1)
FLOAT/ high
Night cos phi
ndNVNightCosPhi
40403
04
03
X
X
X
Note (1)
FLOAT/ low
ndNVNightCosPhi
40404
04
04
X
X
X
Note (1)
FLOAT/ high
Reg cos phi
ndNVRegCosPhi
40405
04
05
X
X
X
Note (1)
FLOAT/ low
ndNVRegCosPhi
40406
04
06
X
X
X
Note (1)
FLOAT/ high
alarm delay
dwNVDelayAlarm
40407
04
07
X
X
X
SECOND unsigned LONG / low
dwNVDelayAlarm
40408
04
08
X
X
X
SECOND unsigned LONG / high
dwNVDelayAlarmReset
40409
04
09
X
X
X
SECOND unsigned LONG / low
dwNVDelayAlarmReset
40410
04
10
X
X
X
SECOND unsigned LONG / high
ndNVCosPhiAlarm
40411
04
11
X
X
X
Note (1)
FLOAT/ low
ndNVCosPhiAlarm
40412
04
12
X
X
X
Note (1)
FLOAT/ high
alarm reset delay alarm cos phi
37
6.6 I/O configuration This table contains parameters related to external communication and graphic display. General description
Description
Settings
I/O configuration
Variable
Variable name
Modbus register
Table number Offset
Language
bNVLanguage
40501
05
01
Temperature unit
bNVFahrenheit
40502
05
LCD contrast
cNVLcdContrastOffset
40503
05
printer type
bNVPrinterType
40504
Modbus address
wNVModbusAddress
protocol
bNVModbusEnable
Modbus lock
Access Set LS BL X
R
NV
Units
Datatype BYTE
C
X
X
Note (14)
02
X
X
Note (15)
BYTE
03
X
X
No unit
signed CHAR
05
04
X
X
No unit
BYTE
40505
05
05
X
X
X
X
No unit
unsigned INT
40506
05
06
X
X
X
X
Note (16)
BYTE
bNVModbusLocking
40507
05
07
X
X
X
X
Note (17)
BYTE
Modbus baud rate
bNVUartBaudRate
40508
05
08
X
X
X
X
Note (18)
BYTE
parity
bNVParity
40509
05
09
X
X
X
X
Note (19)
BYTE
stop bits
bNVStopBit
40510
05
10
X
X
X
X
Note (20)
BYTE
Note (14): language bNVLanguage 0 1 2 3
Signification English French Deutsch Spanish
Note (15): temperature unit. (This parameter only affects the units of the measurements displayed on the LCD screen of the RVT.) bNVFahrenheit 0 1
Signification Celsius Fahrenheit
38
Note (16): protocol bNVModbusEnable 0 1
Signification Printer Modbus/RTU
Note (17): Modbus lock bNVModbusLocking 0 1
Signification Unlocked Locked
Note (18): baud rate bNVUartBaudRate 0 1 2 3 4 5 6 7 8 9
Signification 110 bauds 300 bauds 600 bauds 1200 bauds 2400 bauds 4800 bauds 9600 bauds 19200 bauds 38400 bauds 57600 bauds
Note (19): Parity bit bNVParity 0 1 2
Signification No parity Even Odd
39
Note (20): Stop bit bNVStopBit 0 1
Signification 1 stop bit 2 stop bit
6.7 Change Mode (AUTO-MAN-SET) This table contains the RVT operating mode. Switching ON and OFF steps (MAN mode) functionality is included in this table. General description
Description
Functional parameters
Functional parameters
Variable
Variable name
Modbus register
Table number
offset
Access Set LS BL
Units R
NV
Datatype
C
Mode
bNVMode
40601
06
01
Bank settings lock
bNVBankLocked
40602
06
02
Add 1 step
bAddOneStep
40603
06
03
X
X
Note (21) BYTE
Remove 1 step
bRemoveOneStep
40604
06
04
X
X
Note (21) BYTE
Step size in MAN mode
wNVManualSize
40605
06
05
X
X
X
X
Note (21) BYTE
X
X
Note (22) BYTE
X
STEPS
unsigned INT
Note (21): The mode may be changed with the following parameter: bNVMode
value
AUTO MAN SET
1 2 4
The default mode is AUTO.
40
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. RVT must be in SET mode to modify most of the parameter settings (for more information, please refer to RVT 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 (22): bNVBankLocked activates the ‘Bank settings ’ 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 0 1
Signification Unlocked Locked
6.8 Higher level system settings This table contains 2 string fields which contain: - the type of higher level system incorporating the controller ( capacitor bank ,…) and some technical data corresponding to this system . - the ABB Id number of this higher level system .
41
General Description
Description Variable
Variable name
Higher Level Syst
Settings
wNVHiLvlSystType[0]
49501
95
01
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[1]
49502
95
02
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[2]
49503
95
03
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[3]
49504
95
04
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[4]
49505
95
05
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[5]
49506
95
06
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[6]
49507
95
07
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[7]
49508
95
08
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[8]
49509
95
09
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[9]
49510
95
10
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[10]
49511
95
11
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[11]
49512
95
12
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[12]
49513
95
13
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[13]
49514
95
14
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[14]
49515
95
15
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[15]
49516
95
16
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[16]
49517
95
17
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[17]
49518
95
18
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[18]
49519
95
19
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystType[19]
49520
95
20
0
0
0
0
0
0
1
0
64
Note (23)
STRING
wNVHiLvlSystId[0]
49521
95
21
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[1]
49522
95
22
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[2]
49523
95
23
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[3]
49524
95
24
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[4]
49525
95
25
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[5]
49526
95
26
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[6]
49527
95
27
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[7]
49528
95
28
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[8]
49529
95
29
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[9]
49530
95
30
0
0
0
0
0
0
1
0
64
Note (24)
STRING
wNVHiLvlSystId[10]
49531
95
31
0
0
0
0
0
0
1
0
64
Note (24)
STRING
Higher level system Type
Higher level system Id
Modbus Access register Table number Offset Set LS BL ML Tbl R NV C
Access
Units
Datatype
Note (23): This string field is a succession of data related to the type of product in which the RVT is included. This field is fully dedicated to information and doesn’t influence the behaviour of the controller. The name and format of these data is defined for the RVT as follows: 42
RVT higher level system data Higher level system Description
format STRING STRING STRING STRING STRING WORD WORD BYTE
BYTE
BYTE
BYTE
BYTE BYTE
WORD BYTE STRING
STRING
name Type : APCM1 , APCR , … … … … RatedVoltage ( 0 – 65535 ) (V) ReactivePower * 10 ( 0 – 65535 ) Ex : 875 = 87.5 kvar Frequency 0 = 50 1 = 60 2 = 50/60 Circuit Breaker ‘0’ = No ‘J’ = circuit breaker ‘G’ = Switch ‘H’ = Switch with fuses Power Factor Controller 0 = No 1 = RVC 2 = RVT … Entry 0 = Bottom or Top 1 = Bottom 2 = Top Number of steps ( 0 – 255 ) Tri / Mono 1 = Mono 3 = Tri Reactors % * 100 ( 0 – 65535 ) Ex : 567 = 5.67 % IP ( 0 – 255 ) Ex 54 = IP54 Color ‘S’ = Standard ‘G’ = green ‘R’ = red Execution ‘SP’ = Special ‘RD’ = reinforced dielectric
Low / High wNVHiLvlSystType[0] wNVHiLvlSystType[1] wNVHiLvlSystType[2] wNVHiLvlSystType[3] wNVHiLvlSystType[4] wNVHiLvlSystType[5] wNVHiLvlSystType[6] wNVHiLvlSystType[7]
Low
High
wNVHiLvlSystType[8]
Low
High
wNVHiLvlSystType[9]
wNVHiLvlSystType[10] wNVHiLvlSystType[11]
Low High
Low High
wNVHiLvlSystType[12]
wNVHiLvlSystType[13] wNVHiLvlSystType[14] wNVHiLvlSystType[15] wNVHiLvlSystType[16] wNVHiLvlSystType[17] wNVHiLvlSystType[18] wNVHiLvlSystType[19]
43
Note (24): This string field is arranged as a succession ASCII characters: WordHI[0]_WordLO[0]_ WordHI[1]_WordLO[1]_… 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).
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 behaviour of the RVT.
General description
Description
User data storage
User data storage
Variable General purpose user data storage
Variable name
Modbus register
Table number
offset
Access Set LS BL R NV
Units Datatype
bNVUser[0]
49701
97
01
X
BYTE
bNVUser[1]
49702
97
02
X
BYTE
bNVUser[2]
49703
97
03
X
BYTE
bNVUser[3]
49704
97
04
X
BYTE
bNVUser[4]
49705
97
05
X
BYTE
bNVUser[5]
49706
97
06
X
BYTE
BNVUser[6]
49707
97
07
X
BYTE
BNVUser[7]
49708
97
08
X
BYTE
C
44
6.10 RVT manufacturer information This table contains general RVT information. General Description
Description
Manufacturer settings
Manufacturer settings
Variable
Variable name
Modbus register
Table number
offset
Access Set LS BL
Units R
NV
Datatype
C
Number of outputs
bNVNumberRelay
49801
98
01
X Note (25) BYTE
serial number
dwNVSerialNumber
49802
98
02
X Note (25) unsigned LONG / low
dwNVSerialNumber
49803
98
03
X Note (25) unsigned LONG / high
ABB ID 1
bNVABBIdNr1
49804
98
04
X Note (25) BYTE
ABB ID 2
wNVABBIdNr2
49805
98
05
X Note (25) unsigned INT
ABB ID 3
dwNVABBIdNr3
49806
98
06
X Note (25) unsigned LONG / low
dwNVABBIdNr3
49807
98
07
X Note (25) unsigned LONG / high
soft version
wSoftVersion
49808
98
08
X Note (25) unsigned INT
Product ID
wNVProductId[0]
49809
98
09
X
Note (26) unsigned INT
wNVProductId[1]
49810
98
10
X
Note (26) unsigned INT
wNVProductId[2]
49811
98
11
X
Note (26) unsigned INT
wNVProductId[3]
49812
98
12
X
Note (26) unsigned INT
wNVProductId[4]
49813
98
13
X
Note (26) unsigned INT
wNVProductId[5]
49814
98
14
X
Note (26) unsigned INT
wNVProductId[6]
49815
98
15
X
Note (26) unsigned INT
wNVProductId[7]
49816
98
16
X
Note (26) unsigned INT
wNVProductId[8]
49817
98
17
X
Note (26) unsigned INT
wNVProductId[9]
49818
98
18
X
Note (26) unsigned INT
wNVProductId[10]
49819
98
19
X
Note (26) unsigned INT
wProductType[0]
49820
98
20
X Note (26) unsigned INT
wProductType[1]
49821
98
21
X Note (26) unsigned INT
wProductType[2]
49822
98
22
X Note (26) unsigned INT
Product Type
45
Note (25): This part of the Modbus table contains ‘read only’ RVT manufacturer information: • • • •
Number of relays give the type of RVT ( 6 or 12 ) Serial number ID number Soft version (x.y : high byte = x, low byte = y)
Note (26): Another part contains non volatile ‘read / write’ manufacturer settings used to store data concerning the identification of the product. This non volatile memory has no effect on the behaviour of the RVT. 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]_…
46
7 OUTPUT & INPUT BITS 7.1 Output bits This table contains free bytes for bit change testing. This has no effect on the RVT behaviour. General description
Description
Variable
Variable name
Modbus register
Table number
offset
Access Set LS BL R NV
Units Datatype
OUTPUTBIT_0
00001
00
01
X
BIT
OUTPUTBIT_0
00002
00
02
X
BIT
OUTPUTBIT_0
00003
00
03
X
BIT
OUTPUTBIT_0
00004
00
04
X
BIT
OUTPUTBIT_0
00005
00
05
X
BIT
OUTPUTBIT_0
00006
00
06
X
BIT
OUTPUTBIT_0
00007
00
07
X
BIT
OUTPUTBIT_0
00008
00
08
X
BIT
OUTPUTBIT_1
00101
01
01
X
BIT
OUTPUTBIT_1
00102
01
02
X
BIT
OUTPUTBIT_1
00103
01
03
X
BIT
OUTPUTBIT_1
00104
01
04
X
BIT
OUTPUTBIT_1
00105
01
05
X
BIT
OUTPUTBIT_1
00106
01
06
X
BIT
OUTPUTBIT_1
00107
01
07
X
BIT
OUTPUTBIT_1
00108
01
08
X
BIT
OUTPUTBIT_2
00201
02
01
X
BIT
OUTPUTBIT_2
00202
02
02
X
BIT
OUTPUTBIT_2
00203
02
03
X
BIT
OUTPUTBIT_2
00204
02
04
X
BIT
OUTPUTBIT_2
00205
02
05
X
BIT
OUTPUTBIT_2
00206
02
06
X
BIT
OUTPUTBIT_2
00207
02
07
X
BIT
OUTPUTBIT_2
00208
02
08
X
BIT
C
47
7.2 Input bits This table contains free bytes for bit read testing. This has no effect on the RVT behaviour. Note (30): INPUTBIT_0 contains HEX value 0x55 Note (31): INPUTBIT_1 contains HEX value 0xAA Note (32): INPUTBIT_2 contains HEX value 0xFF General description
Description
Variable
Variable name
Modbus register
Table number
offset
INPUTBIT_0
10001
00
INPUTBIT_0
10002
00
INPUTBIT_0
10003
INPUTBIT_0
10004
INPUTBIT_0
Access Set LS BL
Units
Datatype
01
Note (30)
BIT
02
Note (30)
BIT
00
03
Note (30)
BIT
00
04
Note (30)
BIT
10005
00
05
Note (30)
BIT
INPUTBIT_0
10006
00
06
Note (30)
BIT
INPUTBIT_0
10007
00
07
Note (30)
BIT
INPUTBIT_0
10008
00
08
Note (30)
BIT
INPUTBIT_1
10101
01
01
Note (31)
BIT
INPUTBIT_1
10102
01
02
Note (31)
BIT
INPUTBIT_1
10103
01
03
Note (31)
BIT
INPUTBIT_1
10104
01
04
Note (31)
BIT
INPUTBIT_1
10105
01
05
Note (31)
BIT
INPUTBIT_1
10106
01
06
Note (31)
BIT
INPUTBIT_1
10107
01
07
Note (31)
BIT
INPUTBIT_1
10108
01
08
Note (31)
BIT
INPUTBIT_2
10201
02
01
Note (32)
BIT
INPUTBIT_2
10202
02
02
Note (32)
BIT
INPUTBIT_2
10203
02
03
Note (32)
BIT
INPUTBIT_2
10204
02
04
Note (32)
BIT
INPUTBIT_2
10205
02
05
Note (32)
BIT
INPUTBIT_2
10206
02
06
Note (32)
BIT
INPUTBIT_2
10207
02
07
Note (32)
BIT
INPUTBIT_2
10208
02
08
Note (32)
BIT
R
NV
C
48
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:
QUERY Slave address Function Error check field CRC
1 byte 1 byte 2 bytes
RESPONSE Slave 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
The format of the exception status for the RVT is given hereafter:
RVT exception status signification bit signification 0 1 2 3 4 5 6 7
alarm buffer index ( bit 0 ) alarm buffer index ( bit 1 ) alarm buffer index ( bit 2 ) Not used Not used alarm relay status (normally closed) fan relay status (normally open) presence of an alarm logged in the alarm buffer
0
1
open open no alarm
closed closed alarm logged
A quick monitoring of bits 5, 6, 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).
49
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:
QUERY Slave address Function Error check field CRC
1 byte 1 byte 2 bytes
RESPONSE Slave 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
The format of the Report Slave ID for the RVT is given hereafter:
RVT byte count slave ID Run indicator status Type
Additional data
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
0 = RVT 00 = MAN or SET ; FF = AUTO
96 0 00/FF R' V' T'
number of outputs soft version HI soft version LO serial number HH serial number HL serial number LH serial number LL ABB ID nr 1 ABB ID nr 2 HI ABB ID nr 2 LO ABB ID nr 3 HH ABB ID nr 3 HL ABB ID nr 3 LH ABB ID nr 3 LL
6 or 12 ex : 1 ex : 4 xx xx xx xx 20 0 50 xx xx xx xx
50
level 1 information for higher level systems (APC, PQF…)
level 1 information for Product
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
wNVHiLvlSystId[0] HI LO wNVHiLvlSystId[1] HI LO wNVHiLvlSystId[2] HI LO wNVHiLvlSystId[3] HI LO wNVHiLvlSystId[4] HI LO wNVHiLvlSystId[5] HI LO wNVHiLvlSystId[6] HI LO wNVHiLvlSystId[7] HI LO wNVHiLvlSystId[8] HI LO wNVHiLvlSystId[9] HI LO wNVHiLvlSystId[10] HI LO
wNVProductId[0] HI LO wNVProductId[1] HI LO wNVProductId[2] HI LO wNVProductId[3] HI LO wNVProductId[4] HI LO
51
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96
wNVProductId[5] HI LO wNVProductId[6] HI LO wNVProductId[7] HI LO wNVProductId[8] HI LO wNVProductId[9] HI LO wNVProductId[10] HI LO
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 1; if (flag) temp=temp ^ 0xA001; } } /* Reverse byte order. */ temp2=temp >> 8; temp=(temp
