Modbus GB

3
01/2013 Modbus

1 GENERAL INFORMATION ON THE DOCUMENTATION....................................... 5
1.1 Instruction Manuals.................................................................................................... 5
1.2 Used Pictograms and Signal Words ............................................................................ 5
1.3 Information on Use..................................................................................................... 5
1.3.1 Using external products ................................................................................................ 6
1.4 Maintenance and Service............................................................................................ 6
2 RS485 INTERFACES.......................................................................................... 7
2.1 Set the Protocol for the Communication Module........................................................ 7
3 MODBUS ........................................................................................................... 8
4 PROTOCOL...................................................................................................... 10
4.1 Address Representation............................................................................................ 10
4.2 Message Structure .................................................................................................... 10
4.3 Supported Function Codes........................................................................................ 11
4.3.1 Function Code 3, Read 16-Bit or 32-Bit-Parameter .........................................................12
4.3.2 Function Code 6, Write 16-Bit-Parameter ......................................................................14
4.3.3 Function Code 16, Write 16-Bit-Parameter.....................................................................15
4.3.4 Function Code 16, Write 32-Bit-Parameter.....................................................................16
4.3.5 Function Code 100, Read 32-Bit-Parameter ...................................................................17
4.3.6 Function Code 101, Write 32-Bit-Parameter...................................................................19
4.3.7 Function Code 8, Diagnostics........................................................................................20
4.3.8 Exception Responses ...................................................................................................22
4.3.9 Exception Codes ..........................................................................................................22
4.3.10 Modbus Transmission Modes ........................................................................................23
4.4 Time Monitoring Function......................................................................................... 28
5 HANDLING OF DATA SETS / CYCLIC WRITING............................................... 29
6 MODBUS MESSAGE EXAMPLES ....................................................................... 31
6.1 Modbus RTU-Message Examples .............................................................................. 31
6.1.1 16 Bit Parameter access...............................................................................................31
6.1.2 32 Bit Zugriff ...............................................................................................................34
6.2 Modbus ASCII-Message Examples............................................................................ 39
6.2.1 16 Bit access ...............................................................................................................39
6.2.2 32 Bit access ...............................................................................................................42
6.3 ASCII-Table (0x00 0x7F)....................................................................................... 47
General Information on the Documentation

4
Modbus 01/2013

7 PARAMETER LIST............................................................................................ 48
7.1 Parameters ("Para" Menu) ....................................................................................... 48
8 BUS ERROR MESSAGES................................................................................... 49

5
01/2013 Modbus

1 General Information on the Documentation
This documentation describes the communication with solar inverters using the Modbus protocol. The
modular hardware and software structure allows the user-friendly customization of the inverters.
1.1 Instruction Manuals
For better clarity, the user documentation is structured according to the customer-specific demands
made on the inverter.
Operating Instructions
The Operating Instructions documents the complete functionality of the solar inverter. The installation
of the communication modules as well as the parameters necessary for specific applications for adap-
tation to the application and the extensive additional functions are described in detail. This informa-
tion is not part of this document, for general safety instructions and for information regarding the
mechanical and electrical installation refer to the operating instructions of the solar inverter.

This documentation has been produced with the greatest of care and extensively and repeatedly
checked. For reasons of clarity not all the detailed information on all types of the product and also not
every imaginable case of installation, operation or maintenance has been taken into account. If you
require further information or if specific problems which are not dealt with extensively enough in the
documentation exist, you can request the necessary information from the local BONFIGLIOLI repre-
sentative.
We would also point out that the contents of this documentation are not part of a previous or existing
agreement, assurance or legal relationship and are not intended to amend the same. All obligations of
the manufacturer result from the underlying purchase contract, which also contains the complete and
solely valid warranty regulation. These contractual warranty provisions are neither extended nor lim-
ited by the production of this documentation.
The manufacturer reserves the right to correct or amend the contents and the product information as
well as omissions without prior notification and assumes no kind of liability for damage, injuries or
expenditure to be put down to the aforementioned reasons.
1.2 Used Pictograms and Signal Words
The following pictograms and signal words are used in the documentation:
Danger!
Danger refers to an immediate threat. Non-compliance with the precaution described will
result in death, serious injury or material damage.

Warning!
Warning refers to a possible threat. Non-compliance with the warning may result in death,
serious injury or material damage.

Caution!
Caution refers to an immediate hazard. Non-compliance may result in personal or material
damage.

Attention!
Attention and the related text refer to a possible behavior or an undesired condition which can occur
during operation.

Note
Marks information that facilitates handling for you, and supplements the corresponding part of the
documentation.
1.3 Information on Use
Warning!
Before commissioning and the start of the operation, make sure to fix all covers and check
General Information on the Documentation

6
Modbus 01/2013

the terminals. Check the additional monitoring and protective devices according to EN
60204 and applicable the safety directives (e.g. Working Machines Act, Accident Prevention
Directives etc.).
No connection work may be performed, while the system is in operation.
1.3.1 Using external products
Please note, that Bonfiglioli Vectron does not take any responsibility for the compatibility of external
products.
Using the device in combination with external products is carried out at your own risk.
1.4 Maintenance and Service
Warning!
Unauthorized opening and improper interventions can lead to personal injury or material
damage. Repairs on the inverters may only be carried out by the manu-facturer or persons
authorized by the manufacturer.
Check protective equipment regularly.
Any repair work must be carried out by qualified electricians.

7
01/2013 Modbus

2 RS485 Interfaces
The inverter can be controlled from a PLC or another master device via a serial interface using the
Modbus or VABus protocol. The VABus protocol is required for the parameterization with the VPlus PC-
Software.
The connection can be established via the Communication Module.
The following protocols can be selected:
Modbus RTU
Modbus ASCII
VABus

Warning!
Via the Modbus-Communication, a control unit can access all of the inverter parameters.
The changing of parameters, whose meaning is not known to the user, can lead to the
malfunctioning of the inverter and to dangerous situations in the plant.

Caution!
If values are to be written regularly with a high repetition rate, then no entry may be
made to the EEPROM, as it only has a limited number of admissible write cycles (approx.
1 million cycles). If the number of allowed write cycles is exceeded then the EEPROM will
be damaged. See Chapter 5 "Handling of Data Sets / Cyclic Writing".

RS485-Connection
Inverters can be connected to a bus system, the bus structure is linear and implemented as a 2-wire
line. Up to 247 inverters can be addressed and polled from a bus master via Modbus.
The inverters can be parameterized and controlled via the bus system. During operation data can be
requested and set from a PC or PLC.
2.1 Set the Protocol for the Communication Module
395 Protocol
With Parameter Protocol 395, the communication protocol can be selected for an optional Communi-
cation Module (CM).

Protocol 395 Function
0 - VABus
The slot for the Communication Module is set to the VABus com-
munication protocol. Factory setting.
2 - Modbus-RTU
The slot for an optional Communication Module is set to the Mod-
bus-RTU communication protocol.
3 - Modbus-ASCII
The slot for an optional Communication Module is set to the Mod-
bus-ASCII communication protocol.

For Modbus communication only settings 2 and 3 are relevant. Further possible protocols are de-
scribed in other manuals.

Attention!
Changes are effective immediately and without a restart of the inverter.
Modbus

8
Modbus 01/2013

3 Modbus
Note
In the case of the software reset, proceed as follows:
Stop inverter via control switch
Via the control Unit KP500, open parameter Program 34
Set parameter value 123
Confirm by pressing ENT
After the reset, the frequenxy inverter is initialized and is ready for operation after a few seconds.
010 Baud Rate
With Parameter Baud Rate 010 the transfer rate of the Modbus communication can be set. The set-
ting applies to the slot of the communication module.

Modbus Baud rate 1504 Function max. Line Length
1

1 2400 Baud Transfer rate 2400 Baud 30 m

Caution!
Changes are effective after a restart of the inverter.
All bus participants must be set to the same baud rate.
1375 Modbus Parity
With Parameter Modbus Parity 1375 the parity of the Modbus communication can be set.

Modbus Parity 1375 Function
0 Even Even parity is used in the data transfer.
1 Odd Odd parity is used in the data transfer.
2 None No parity is used in the data transfer.

Attention!
Changes are effective after a restart of the inverter.
1376 Modbus Address
The node address can be set with Parameter Modbus Address 1376. Up to 247 inverters can be op-
erated with Modbus. These are allocated a unique address in the range 1 to 247.

Parameter Setting
Nr. Description Min. Max. Factory Setting
1376 Modbus Address 1 247 1

1
The listed line lengths are recommended maximum values, which amongst other things, are dependent on the
properties of the cable.

9
01/2013 Modbus

Attention!
Changes are effective immediately and without a restart of the inverter.

An address must be allocated for each participant.
Double assignments are not permitted when allocating bus addresses.
For details on addressing, see Chapter 4.1 "Address Representation".
413 Modbus Watchdog Timer
The communication can be monitored. If the communication fails, then no data or incorrect data will
be transferred. This state will be detected by the Communication Watchdog.
The Watchdog-Function monitors the time, within which no correct communication occurs. This time
can be set with Parameter Modbus Watchdog Timer 413. The set value is the time in seconds within
which at least one correct data exchange must occur.
If the set monitoring time is reached the inverter generates an error.

Parameter Setting
Nr. Description Min. Max. Factory Setting
413 Modbus Watchdog Timer 0 s 10000 s 0 s

If the parameter is set to zero (factory setting), then monitoring is switched off.
Protocol

10
Modbus 01/2013

4 Protocol
The MODBUS serial communication protocol is a Master/Slave-Protocol. With the bus only one master
is connected (at a time). One or several (max. 247) slave-nodes are connected with each other on the
same bus. A MODBUS communication is always initiated by the master. The slave nodes do not com-
municate with each other. The master only initiates one MODBUS communication at a time.
The master sends a MODBUS request to the slave-nodes in two different operation modes::
In the Unicast operation mode the master addresses a single slave-node. After reception and
processing of the request, the slave-node sends a message (reply) to the master. In this operation
mode a MODBUS transfer consists of two messages: a request from the master and a reply from
the slave-node. Each slave-node must have a unique address (from 1 to 247), so that the slave-
nodes can receive requests independent of each other.
In the Broadcast operation mode the master can send a request to all slave-nodes. The slave-
nodes do not send a reply to the request.. The request consists of write commands. All slaves must
accept the write commands. Address 0 is reserved for the recognition of a broadcast request.
4.1 Address Representation
Up to 247 inverters can be operated on MODBUS. These are assigned addresses in the range
1 247. With address 0, all clients connected to the bus can be addressed simultaneously. Address 0
is also referred to as the Broadcast-Address.
4.2 Message Structure
A MODBUS message is made up of the following fields:

Address Function Code Data CRC (or LRC)

The Address field contains the slave-address in the Modbus message.
Valid slave node addresses are in the range of 0 247 (decimal). The individual slave devices are
assigned addresses in the range of 1 247. A master addresses a slave by placing the slave address
in the address field of the message. When the slave returns its response, it places its own address in
the response address field to let the master know which slave is responding.
The Function Code indicates to the inverter what kind of action to perform. The function code can
be followed by a Data field that contains request parameters (or, in the case of the inverter's re-
sponse, the response parameters).
If no error occurs related to a correctly received Modbus request then the data field contains the data
requested. If an error occurs then the field contains an Exception Code to indicate to the master that
the request was unsuccessful. Exception Responses and Codes are described in detail in chapter 4.3.9
"Exception Codes".
If a request is not received correctly (communication error, checksum error) then no response is sent.
The inverter waits for the next request.
The Error Checking Field is the result of a "Redundancy Checking" calculation that is performed on
the message contents. Two kinds of calculation methods are used depending on the transmission
mode that is being used (RTU or ASCII). See Chapter 4.3.10 "Modbus Transmission Modes".

11
01/2013 Modbus

4.3 Supported Function Codes
Modbus definitions for reading/writing data in a device do not fit directly to parameter access of in-
verters (independent of inverter manufacturer). Modbus is defined for reading/writing bits and regis-
ters in a different way. Furthermore, data access is limited to 16 bit wide data.
To fulfill the Modbus requirements the data access to parameters in the devices (inverters) will use
the following defined function codes:
16 bits values:
Function Code 3, Read ONE 16 bit wide data (Read Holding Register)
Function Code 6, Write ONE 16 bit wide data (Preset Single Register)
Function Code 16, Write ONE 16 bit wide data (Preset Multiple Register)

32 bits values:
For data access to 32 bit wide data two new inverter specific function codes are defined:
Function Code 3, Read two 16 bit (=32 Bit) wide data (Read Holding Register)
Function Code 16, Write two 16 bit (=32 Bit) wide data (Preset Multiple Register)
Function Code 100, Read ONE 32 bit wide data
Function Code 101, Write ONE 32 bit wide data
Note: The Modbus specification doesnt specify the handling of 32 bit values. The implemented han-
dlings and function codes to access 32 Bit values are however widely spread and commonly used.
These functions allow data access to 32-bit "long" variables/parameters in the inverter.

For diagnostic purposes the Modbus function code "8" (Diagnostics) is also supported.
These function codes and their corresponding data fields are described in detail in the following chap-
ters.

Note:
In all data fields with more than one byte, the highest order byte is transmitted first.

Message examples for all supported function codes in both RTU and ASCII transmission modes can be
found in Chapter 6 "Modbus Message Examples".
Protocol

12
Modbus 01/2013

4.3.1 Function Code 3, Read 16-Bit or 32-Bit-Parameter
This function code is used to read the value of 16 Bit or 32 Bit parameters in the inverter.
Request 16 Bit parameter read:
Start Frame (RTU or ASCII mode)

Address 1 Byte 1 0xF7 (=247)
Function Code 1 Byte 0x03
Start Address (Data Set / Para-No.) 2 Bytes 0x0000 0x963F
No. of Registers 2 Bytes 0x0001
CRC or LRC & Endframe
Response 16 Bit parameter read:

No. of Bytes 1 Byte 0x02
Register Value (Parameter Value) 2 Bytes 0 0xFFFF
Request 32 Bit parameter read:

Response 32 Bit parameter read:

Register Value (Parameter Value) 4 Bytes 0 0xFFFFFFFF
Exception Response:

Error Code 1 Byte 0x83
Exception Code 1 Byte 2, 3 or 4

Start Address
This field is used to store the parameter number and data set number. The parameter number ranges
from 0 - 1599 and is stored in the lower 12bits; the data set number ranges from 0 9 and is stored
in the upper 4 bits.
Example: Parameter 372 (hex. 0x174), data set 2 (hex. 0x2) is stored as hex. 0x2174.

Start Address
Data Set Parameter number
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
For the above example:
Hex. 0 0 1 0 0 0 0 1 0 1 1 1 0 1 0 0
Bin. 2 1 7 4

13
01/2013 Modbus

No. of Registers
This field is used to store the no. of parameters to be written. The value must always be 1 as it is only
possible to write one parameter at a time.
Byte Count
This field is set to
2 for 16 Bit parameters.
4 for 32 Bit parameters.
Register Value
This field is contains the 16-bit or 32-bit parameter value.
Note:
Parameter values with decimal places are transferred without the decimal point. Depending on the
number of decimal places, the values are multiplied by 10, 100 or 1000.
Example:
A current value of 10.3A is transmitted. The numerical value actually transmitted is 103, which corre-
sponds to 0x67 in HEX format.
Exception Code
The following exception codes can occur:
2 ILLEGAL DATA ADDRESS No. of Registers field not equal to 1.
Parameter unknown
3 ILLEGAL DATA VALUE No. of bytes in the data field too small or too large
4 SLAVE DEVICE FAILURE Error on reading the parameter
Exception Codes are described in detail in Chapter 4.3.9 "Exception Codes".
Examples:
16 Bit 32 Bit
Modbus RTU 6.1.1.1 6.1.2.1
Modbus ASCII 6.2.1.1 6.2.2.1

Protocol

14
Modbus 01/2013

4.3.2 Function Code 6, Write 16-Bit-Parameter
This function code is used to write the value of an integer or unsigned integer parameter in the in-
verter.
Request 16 Bit parameter write:

Response:

Exception Response:


Start Address
from 0 1599 and is stored in the lower 12 bits; the data set number ranges from 0 9 and is stored
e.g.: Parameter 372 (hex. 0x174), data set 2 (hex. 0x2) is stored as hex. 0x2174.

Start Address
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Hex. 0 0 1 0 0 0 0 1 0 1 1 1 0 1 0 0
Bin. 2 1 7 4

Register Value
This field is used to store the 16-bit parameter value.

Note:

Example:
A current value of 10.3A is to be transmitted. The numerical value actually transmitted is 103, which
corresponds to 0x67 in HEX format.

15
01/2013 Modbus

Exception Code
2 ILLEGAL DATA ADDRESS Parameter unknown
4 SLAVE DEVICE FAILURE Error on writing the parameter


Example of a Modbus ASCII telegram: see chapter 6.2.1.2.
Example of a Modbus RTU telegram: see chapter 6.1.1.2.

Function code 16 can be used to to write the value of 16 Bit parameter in the inverter.

Response:

Exception Response:


Start Address

Start Address
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Hex. 0 0 1 0 0 0 0 1 0 1 1 1 0 1 0 0
Bin. 2 1 7 4

Protocol

16
Modbus 01/2013

Register Value

Note:

Example:
A current value of 10.3A is to be transmitted. The numerical value actually transmitted is 103, which
corresponds to 0x67 in HEX format.

Exception Code


Example of a Modbus ASCII telegram: see chapter 6.2.1.3
Example of a Modbus RTU telegram: see chapter 6.1.1.3

Function code 16 can be used to to write the value of 16 Bit parameter in the inverter.


Register Value (Parameter Value) 2 Bytes 0 0xFFFF FFFF
Response:

Exception Response:


17
01/2013 Modbus

Start Address

Start Address
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Hex. 0 0 1 0 0 0 0 1 0 1 1 1 0 1 0 0
Bin. 2 1 7 4

Register Value

Note:

Example:
A frequency value of 123.45 Hz is to be transmitted. The numerical value actually transmitted is
12345, which corresponds to 0x3039 in HEX format.

Exception Code


4.3.5 Function Code 100, Read 32-Bit-Parameter
Request:

Response:

Protocol

18
Modbus 01/2013

Exception Response:

Error Code 1 Byte 0xE4

Start Address

Start Address
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Hex. 0 0 1 0 0 0 0 1 0 1 1 1 0 1 0 0
Bin. 2 1 7 4

No. of Registers
Note:
Parameter Values with decimal places are transferred without the decimal point. Depending on the

Example:

Exception Code

4 SLAVE DEVICE FAILURE Error on reading the parameter

Example of a Modbus ASCII telegram see chapter 6.2.2.2.
Example of a Modbus RTU telegram see chapter 6.1.2.3 6.1.2.3.

19
01/2013 Modbus

Request:

Start Address (Data Set/Para-No.) 2 Bytes 0x0000 0x963F
Response:

Start Address (Data Set/Para-No.) 2 Bytes 0x0000 0x963F
Exception Response:

Error Code 1 Byte 0xE5
Exception Response 1 Byte 2, 3 or 4

Start Address
Start Address
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Hex. 0 0 1 0 0 0 0 1 0 1 1 1 0 1 0 0
Bin. 2 1 7 4

Register Value

Note:

Example: Frequency Value
Protocol

20
Modbus 01/2013

Exception Code



4.3.7 Function Code 8, Diagnostics
This function code is used to access the Modbus diagnostic counters that are supported by the in-
verter. Each counter can be obtained by a sub-function code bound to the counter number. All of the
counters can be cleared using the hexadecimal sub-function code 0x0A.

The following sub-function codes are supported:

Sub
Function

Name

Description
0x0A Clear all counters Sets all counters to zero
0x0B Return Bus Message Count No. of valid messages received
(with all addresses)
0x0C Return Bus Communication Error Count No. of messages with CRC or
Parity/Framing/Overrun error
0x0D Return Bus Exception Error Count No. of Exception Responses sent
0x0E Return Slave Message Count No. of messages received
(with slave address)
0x0F Return Slave No Response Count No. of Broadcast messages received
0x10 Return Slave NAK Count not used, return value is always 0
0x11 Return Slave Busy Count not used, return value is always 0
0x12 Return Bus Character Overrun Count No. of messages with Overrun error

Request (Sub-function 0x0A, Clear all Counters):
Address
Sub-function 2 Bytes 0x000A
Data 2 Bytes 0x0000

Response:
Address
Sub-function 2 Bytes 0x000A
Data 2 Bytes 0x0000

21
01/2013 Modbus

Exception Response:
Address

Data
This field is always 0x0000.

Exception Code

1 ILLEGAL FUNCTION CODE Sub-function not supported
"data field" not equal to 0x0000
4 SLAVE DEVICE FAILURE Error on carrying out the function


Request (Sub-function 0x0B 0x12, Return Counter Value):
Address
Sub-function 2 Bytes 0x000B 0x0012
Data 2 Bytes 0x0000

Response:
Address
Sub-function 2 Bytes 0x000B 0x0012
Data 2 Bytes 0 0xFFFF

Exception Response:
Address

Data
This field is always set to 0x0000 in the request and contains the actual counter value in the response.

Exception Code

1 ILLEGAL FUNCTION CODE Sub-function not supported
3 ILLEGAL DATA VALUE
No. of bytes in the data field too small or too large
"data field" not equal to 0x0000
4 SLAVE DEVICE FAILURE Error on Reading the Diagnostic Counter

Protocol

22
Modbus 01/2013

4.3.8 Exception Responses
When the master device sends a request to the inverter it expects a normal response. One of four
possible events can occur from the masters query:
If the inverter receives the request without a communication error and can handle the query nor-
mally, it returns a normal response.
If the inverter does not receive the request due to a communication error, no response is returned.
The master will eventually process a timeout condition for the request.
If the inverter receives the request, but detects a communication error (parity, LRC, CRC, ...), no
response is returned. The master will eventually process a timeout condition for the request.
If the inverter receives the request without a communication error, but cannot handle it (for exam-
ple, if the request is to read an unknown parameter), the inverter will return an exception re-
sponse informing the client of the nature of the error.

The exception response message has two fields that differentiate it from a normal response:
Function Code Field:
In a normal response, the inverter echoes the function code of the original request in the function
code field of the response. All function codes have a mostsignificant bit (MSB) of 0 (their values are
all below 0x80 hexadecimal). In an exception response, the inverter sets the MSB of the function code
to 1. This makes the function code value in an exception response exactly 0x80 hexadecimal higher
than the value would be for a normal response. With the function codes MSB set, the master can
recognize the exception response and can examine the data field for the exception code.

Data Field:
In a normal response, the inverter may return data or statistics in the data field (any information that
was requested in the request). In an exception response, the inverter returns an exception code in the
data field. This defines the server condition that caused the exception.

The Exception Codes generated by the inverter are listed in Chapter 4.3.9 "Exception Codes".
4.3.9 Exception Codes
The following exception codes are generated by the inverter:

Code Modbus Name Cases when generated by the Inverter
1 ILLEGAL FUNCTION
Function Code unknown
Subfunction Code unknown (Diagnostics Function)
2 ILLEGAL DATA
ADDRESS
No. of Registers field incorrect (must always be 0x01)
Unknown Parameter or Parameter Data Type mismatch
3 ILLEGAL DATA VALUE
Error in dataset of frame
No. of bytes too small or too large
Certain fields not set to specific values
4 SLAVE DEVICE FAILURE
Read or Write Parameter failed
The reason for the error can be obtained by reading out Parameter
VABusSST Error Register 11.

23
01/2013 Modbus

VABusSST Error Register 11
Error number Meaning
0 no error
1 inadmissible parameter value
2 inadmissible data set
3 parameter not readable (write-only)
4 parameter not writable (read-only)
5 read error EEPROM
6 write error EEPROM
7 checksum error EEPROM
8 parameter cannot be written while the drive is running
9 values of the data sets differ from one another
10 wrong parameter type
11 unknown parameter
12 checksum error in received message
13 syntax error in received message
14 data type of parameter does not correspond to the number of bytes in the mes-
sage
15 unknown error

When the error register VABus SST Error Register 11 is read out, it is automatically cleared at the
same time.
4.3.10 Modbus Transmission Modes
Two different serial transmission modes are defined: the RTU mode and the ASCII mode. They
define the bit contents of message fields transmitted serially on the line. They determine how infor-
mation is packed into the message fields and decoded.
The transmission mode (and serial port parameters) must be the same for all devices on a MODBUS
Serial Line.
The transmission mode for the Modbus-Communication can be selected via Parameter Protocol 395.
See Chapter 3 "Modbus".
4.3.10.1 RTU Transmission
When devices communicate on a MODBUS serial line using the RTU (Remote Terminal Unit) mode,
each 8bit byte in a message contains two 4bit hexadecimal characters.
The main advantage of this mode is that its greater character density allows better data throughput
than ASCII mode for the same baud rate. Each message must be transmitted in a continuous stream
of characters.
4.3.10.1.1 Character Format
One character consists of 11 bits.
1 start bit
8 data bits, least significant bit sent first
1 parity bit
1 stop bit

Note:
If no parity is used then an extra stop bit is added.

Character format with parity checking:

Start B1 B2 B3 B4 B5 B6 B7 B8 Parity Stop

Character format without parity checking:

Start B1 B2 B3 B4 B5 B6 B7 B8 Stop Stop
Protocol

24
Modbus 01/2013

4.3.10.1.2 Frame Description

Slave
Address
Function
Code
Data CRC
1 Byte 1 Byte 0 to 252 Bytes
2 Bytes
(CRC-Lo, CRC-Hi)

The maximum size of a MODBUS RTU frame is 256 bytes.

4.3.10.1.3 Modbus Message RTU Framing
A MODBUS message is placed by the transmitting device into a frame that has a known beginning and
ending point. This allows devices that receive a new frame to begin at the start of the message, and
to know when the message is completed. Partial messages must be detected and errors must be set
as a result. In RTU mode, message frames are separated by a silent interval of at least 3.5 character
times.
MODBUS Message

Start Address Function Data CRC End
>= 3,5
Char

8 Bits 8 Bits N x 8 Bits 16 Bits
>= 3,5
Char

The entire message frame must be transmitted as a contiguous stream of characters.
If a silent interval of more than 1.5 character times occurs between two characters, the message
frame is declared incomplete and is discarded by the inverter.
4.3.10.1.4 CRC Checking
The RTU mode includes an errorchecking field that is based on a Cyclical Redundancy Checking
(CRC) method performed on the message contents.
The CRC field checks the contents of the entire message. It is applied regardless of any parity check-
ing method used for the individual characters of the message.
The CRC field contains a 16bit value implemented as two 8bit bytes.
The CRC field is appended to the message as the last field in the message. It is appended in the se-
quence "low-order byte", "high-order byte". The CRC highorder byte is the last byte to be sent in the
message.
The CRC value is calculated by the sending device, which appends the CRC to the message. The re-
ceiving 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.
The CRC calculation is started by first pre-loading a 16bit register to all 1s (0xFFFF). Then a process
begins of applying successive bytes of the message to the current contents of the register.
During generation of the CRC, each 8bit character is ExOR with the register contents. Then the result
is shifted in the direction of the least significant bit (LSB), with a zero filled into the most significant bit
(MSB) position. The LSB is extracted and examined. If the LSB was a 1, the register is then ExOR with
the fixed value 0xA001. If the LSB was a 0, no ExOR takes place.
This process is repeated until eight shifts have been performed. After the last (eight) shift, the next
8bit char is ExOR with the registers current value, and the process repeats for eight more shifts as
described above. The final content of the register, after all the bytes of the message have been ap-
plied, is the CRC value.
When the CRC is appended to the message, the low-order byte is appended first, followed by the
high-order byte.

25
01/2013 Modbus

Example for CRC calculating for the frame: "0x02 0x07"
MSB LSB
Start CRC 1111 1111 1111 1111 0xFFFF
1.char 0000 0000 0000 0010 0x02

ExOR

CRC 1111 1111 1111 1101
1.shift right 0111 1111 1111 1110 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1101 1111 1111 1111
2.shift right 0110 1111 1111 1111
0xA001 1010 0000 0000 0001

ExOR

CRC 1100 1111 1111 1110
3.shift right 0110 0111 1111 1111 0 = no ExOR
4.shift right 0011 0011 1111 1111 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1001 0011 1111 1110
6.shift right 0010 0100 1111 1111 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1000 0100 1111 1110
8.shift right 0010 0001 0011 1111 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1000 0001 0011 1110

2.char 0000 0000 0000 0111 0x07

ExOR

CRC 1000 0001 0011 1001
1.shift right 0100 0000 1001 1100 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1110 0000 1001 1101
2. shift right 0111 0000 0100 1110 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1101 0000 0100 1111
3. shift right 0110 1000 0010 0111 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1100 1000 0010 0110
4. shift right 0110 0100 0001 0011 0 = no ExOR
5. shift right 0011 0010 0000 1001 1 = ExOR
0xA001 1010 0000 0000 0001

ExOR

CRC 1001 0010 0000 1000
result 1 2 4 1 CRC = 0x41 0x12
Protocol

26
Modbus 01/2013

Example: program sequence (C#)

Private int Modbus_CRC(string frame)
{
int poly = 0xA001; // polynom
int CRC = 0xFFFF; // start CRC

for (int i = 0; i < (int)(frame.Length); i++) // for each char
{
CRC ^= Convert.ToInt16(frame[i]); // ExOR

for (int j = 0; j < 8; j++) // eight times
{
if ((CRC& 0x01) == 0x01) // lsb == 1 ?
{
CRC>>= 1; // shift left
CRC ^= poly; // ExOR
}
else
{
CRC>>= 1; // shift left
}
}
}
Return CRC;
}

Call the function for the frame "0x02 0x07"

stringtemp_s = Convert.ToString((char)(0x2))+ Convert.ToString((char)(0x7));

Console.WriteLine(Modbus_CRC(temp_s));

Result: 4673 = 0x1241

CRC Low Byte = 0x41
CRC High Byte = 0x12

The Modbus CRC sequence is:

CRC Low Byte/High Byte 0x41 0x12

4.3.10.2 ASCII Transmission
When devices are setup to communicate on a MODBUS serial line using 7-bit ASCII (American Stan-
dard Code for Information Interchange) mode, each 8 bit character in a message is sent as two ASCII
characters. This mode is used when the physical communication link or the capabilities of the device
does not allow the conformance with RTU mode requirements regarding the management of timers.

Note:
This mode is less efficient than RTU since each byte needs two characters.
Example: The byte 0x5B is encoded as two characters: 0x35 and 0x42 ( 0x35 ="5", and 0x42 ="B" in
ASCII ).

27
01/2013 Modbus

4.3.10.2.1 Character Format
One character consists of 10 bits:
1 start bit
7 data bits, least significant bit sent first (value = 0x00 .. 0x7F)
1 parity bitj
1 stop bit

Note:
If no parity is used then an extra stop bit is added.

Character format with parity checking:
Start B1 B2 B3 B4 B5 B6 B7 Parity Stop

Character format without parity checking:
Start B1 B2 B3 B4 B5 B6 B7 Stop Stop

4.3.10.2.2 Modbus Message ASCII Framing
A MODBUS message is placed by the transmitting device into a frame that has a known beginning and
ending point. This allows devices that receive a new frame to begin at the start of the message, and
to know when the message is completed. Partial messages must be detected and errors must be set
as a result.
The address field of a message frame contains two characters.
In ASCII mode, a message is delimited by specific characters as Start-of-Frame and End-of-Frame. A
message must start with a trigger "colon"- character (":" = ASCII 0x3A) and ends with a "carriage
return/line feed" pair (ASCII 0x0D and 0x0A).
The allowable characters transmitted for all other fields are hexadecimal 09, AF (ASCII coded). The
devices monitor the bus continuously for the colon character. When0 this character is received, each
device decodes the next character until it detects the End-of-Frame (EoF)-character.
Intervals of up to one second may elapse between characters within the message. Unless the user has
configured a longer timeout, an interval greater than 1 second means an error has occurred.

A typical message frame is shown below:

SoF Address Function Data LRC EoF
1 char
:
2 chars 2 chars 0 up to 2* 252 chars 2 chars 2 chars
CR, LF

4.3.10.2.3 LRC Checking
In ASCII mode, messages include an errorchecking field that is based on a Longitudinal Redundancy
Checking (LRC) calculation that is performed on the message contents, exclusive of the beginning
colon and terminating CRLF pair characters. It is applied regardless of any parity checking method
used for the individual characters of the message.
The LRC field is one byte, containing an 8-bit binary value. The LRC value is calculated by the device
that emits, which appends the LRC to the message. The device that receives calculates an LRC during
receipt of the message, and compares the calculated value to the actual value it received in the LRC
field. If the two values are not equal, an error results.
The LRC field is one byte, containing an 8-bit binary value. The LRC value is calculated by the device
that emits, which appends the LRC to the message. The device that receives calculates an LRC during
receipt of the message, and compares the calculated value to the actual value it received in the LRC
field. If the two values are not equal, an error results.

Protocol

28
Modbus 01/2013

4.4 Time Monitoring Function
The Modbus protocol defines a pure Master/Slave operation. If a inverter is addressed by the bus
master, other inverters will only be addressed after the protocol with the first inverter has been com-
pleted or the timeout time has expired.
After a inverter has sent a message, a waiting time of 2 ms must be kept. This time is needed by the
inverter in order to switch off the RS485 transmitter. The bus master may not send a new message
until this time has elapsed.

Attention!
If the degree of utilization of the CPU is high (> 90%), the response time can be more than 500 ms.

Note:
The specified times are valid for operation with RS485 and RS232.

29
01/2013 Modbus

5 Handling of Data Sets / Cyclic Writing
Access to the parameter values is carried out on the basis of the parameter number and the required
data set.
There are parameters the values of which exist once (data set 0) as well as parameters the values of
which exist four times (data set 1...4). These are used for data set change-over.
If parameters which exist four times in the data sets are set to data set = 0, all four data sets are set
to the same value.
A read access with data set = 0 to such parameters is only successful if all four data sets are set to
the same value. If this is not the case, error 9 = "different values in data sets" is signaled via the error
register VABus SST Error Register 11. In this case, you must read out each data set separately for
the relevant parameter (see chapter 4.3.9 "Exception Codes").
New write requests will be blocked by the error register VABus SST Error Register 11. For this rea-
son, the error register must be read out, i.e. acknowledged, before a new write request can be sent.
Regardless of the signal status of the error register, reading access (read requests) is still possible.

The values are entered into the EEPROM automatically on the controller. If values are to be written
cyclically with a high repetition rate, there must be no entry into the EEPROM, as it only has a limited
number of admissible writing cycles (about 1 million cycles).

Caution!
If the number of admissible writing cycles is exceeded, the EEPROM is destroyed.

In order to avoid the destruction of the EEPROM, data which are to be written cyclically can be en-
tered in the RAM exclusively without a writing cycle on the EEPROM. In this case, the data are vola-
tile, i.e. they are lost when the supply voltage is switched off (Mains Off). They must be written into
the RAM again after the restart (Mains On).
The RAM writing operation is activated by increasing the number of the target data set by five.

Access to the Data Sets of the Inverter
Parameter EEPROM RAM
Data Set 0 0 5
Data Set 1 1 6
Data Set 2 2 7
Data Set 3 3 8
Data Set 4 4 9

Handling of Data Sets / Cyclic Writing

30
Modbus 01/2013

31
01/2013 Modbus

6 Modbus Message Examples
This chapter describes some examples for Modbus RTU and Modbus ASCII.
6.1 Modbus RTU-Message Examples
6.1.1 16 Bit Parameter access
6.1.1.1 Function Code 3, Read 16-Bit Parameter
Example 1:
Reading parameter Active Power 213 (0x00D5) in data set 0 from the inverter with address 1.

Request: Master Inverter

Field: Addr. Func. DSet/Par-No. No. of Regs CRC
Hex 01 03 00 D5 00 01 95 F2

Response: Inverter Master

Field: Addr. Func. No.Bytes Par-Value CRC
Hex 01 03 02 01 2C B8 09

The hexadecimal value sent is 0x001E = 300. Parameter Active Power 213 has one decimal places.
Therefore, the active Power is 30,0kW

Example 2:
Reading parameter Active Power 213 (0x00D5) in data set 0 from the inverter with address 1 and
No. of Regs field set to 2 (invalid value).


Hex 01 03 00 D5 00 02 D5 F3

Error Response: Inverter Master

Field: Addr. Func. Except. CRC
Hex 01 83 04 40 F3

The exception code sent is hexadecimal value 0x04 = SLAVE DEVICE FAILURE.

Modbus Message Examples

32
Modbus 01/2013

6.1.1.2 Function Code 6, Write 16-Bit Parameter
Example 1:
Writing parameter Power reduction reference value 1020 (0x03FC) in data set 5 (= RAM for data set
0) to the inverter with address 3.
The Power reduction is to be set to 50%. Parameter Power reduction reference value 1020 has no
decimal place.
Therefore the value to be sent is 50 = 0x0032.


Field: Addr. Funk. DSatz/Par-Nr. Par-Wert CRC
Hex 03 06 53 FC 00 32 D9 6B


Field: Addr. Func. DSet/Par-No. Par-Value CRC
Hex 03 06 53 FC 00 32 D9 6B

The response is an echo of the request message.

Example 2:
Writing out of range value 0 to parameter 1020 (0x03FC) in data set 5 (= RAM for data set 0) to the
inverter with address 3.


Hex 03 06 53 FC 00 6E D8 B0


Hex 03 86 04 E2 63


33
01/2013 Modbus

Example 1:
decimal place.


Field: Addr. Func. DSatz/Par-Nr. No. of registers
No. of
bytes
Par-value CRC
Hex 01 10 53 FC 00 01 02 00 32 50 BC


Field: Addr. Func. DSet/Par-No. No. of registers CRC
Hex 01 10 53 FC 00 01 D0 BD

The response contains the no. of registers written.

Example 2:
inverter with address 1


Field: Addr. Func. DSatz/Par-Nr. No. of registers
No. of
bytes
Par-value CRC
Hex 03 10 53 FC 00 01 02 00 6E 49 E5


Hex 03 90 04 EC 03



34
Modbus 01/2013

6.1.2 32 Bit Zugriff
Example 1:
Reading parameter Frequency 850 (0x0352) in data set 0 from the inverter with address 1.


Hex 01 03 03 52 00 02 65 9E


Field: Addr. Func. No.Bytes Par-Value CRC
Hex 01 03 04 00 09 27 C0 31 91

The hexadecimal value sent is 0x0000EA60 = 600000. Parameter Fixed Frequency 481 has four
decimal places.
Therefore, the frequency is 60.0000 Hz.

Example 2:
Reading parameter Frequency 850 (0x0352) in data set 0 from the inverter with address 1 and No.
of Regs field set to 1 (invalid value).


Hex 01 03 03 52 00 01 25 9F


Hex 01 83 04 40 F3


35
01/2013 Modbus

Example 1:
Writing parameter Fixed Frequency 3 482 (0x01E2) in data set 9 (= RAM for data set 4) to the in-
verter with address 1.
The frequency is to be set to 44.50 Hz. Parameter Fixed Frequency 3 482 has two decimal places.


Field
:
Addr. Funk. DSatz/Par-Nr. No. Registers
No.
Bytes
Par-Wert CRC
Hex 01 10 91 E2 00 02 04 00 00 11 62 50 11


Field: Addr. Func. DSet/Par-No. No. Registers CRC
Hex 01 10 91 E2 00 02 CD 02

The response contains the no. of registers written.

Example 2:
Writing parameter Fixed Frequency 3 482 (0x01E2) in data set 9 (= RAM for data set4) to the in-
The frequency is to be set to the invalid value 2000.00 Hz. Parameter Fixed Frequency 3 482 has two
decimal places.
Therefore the value to be sent is 20000 = 0x00030D40.


Field
:
Addr. Funk. DSatz/Par-Nr. No. Registers
No.
Bytes
Par-Wert CRC
Hex 01 10 91 E2 00 02 04 00 03 0D 40 28 C8


Hex 01 90 04 4D C3



36
Modbus 01/2013

Example 1:
Reading parameter Fixed Frequency 2 481 in data set 0 from the inverter with address 1.


Field: Addr. Funk. DSatz/Par-Nr. CRC
Hex 01 64 01 E1 81 DF


Field: Addr. Func. Par-Value CRC
Hex 01 64 00 00 03 E8 70 BC

The hexadecimal value sent is 0x000003E8 = 1000. Parameter Fixed Frequency 2 481 has two deci-
mal places.
Therefore, fixed frequency 2 = 10.00 Hz.

Example 2:
Reading unknown parameter 1600 (0x0640) in data set 2 from the inverter with address 1.


Field: Addr. Func. DSet/Par-No. CRC
Hex 01 64 26 40 5B 97


Hex 01 E4 04 6A C3


37
01/2013 Modbus

Example 1:
Writing parameter Rated Frequency 375 (0x0177) in data set 2 to the inverter with address 1.

The rated frequency is to be set to 10.00Hz. Parameter Rated Frequency 375 has two decimal places.
Therefore the value to be sent is 1000 = 0x03E8.


Hex 01 65 21 77 00 00 03 E8 46 C5


Hex 01 65 21 77 00 00 03 E8 46 C5


Example 2:
Writing out of range value 9.00 Hz to parameter 375 in data set 2 of the inverter with address 1.
Parameter Rated Frequency 375 has 2 decimal places. The value to be sent is 900 = 0x0384.


Hex 01 65 21 77 00 00 03 84 46 E8


Hex 01 E5 04 6B 53



38
Modbus 01/2013

Example 1a:
Clearing all Diagnostic Counters (Sub-function 0x0A) in the inverter with address 1.

Field: Addr. Func. Sub-function Data CRC
Hex 01 08 00 0A 00 00 C0 09

Hex 01 08 00 0A 00 00 C0 09

The response is an echo of the request. All counters are now set to zero.

Example 1b:
With all counters set to zero, read Diagnostic Counter 4, "Slave Message Count" (Sub-function 0x0E)
from the inverter with address 1.

Hex 01 08 00 0E 00 00 81 C8

Hex 01 08 00 0E 00 01 40 08

The counter value is 1(as this is the 1st message received after setting all counters to zero).

Example 2:
Reading unknown Diagnostic Counter 8 (Sub-function 0x13) from inverter with address 1.

Field: Addr. Funk. Sub-function Data CRC
Hex 01 08 00 13 00 00 11 CE

Hex 01 88 01 87 C0

The exception code sent is hexadecimal value 0x01 = ILLEGAL FUNCTION.

39
01/2013 Modbus

6.2 Modbus ASCII-Message Examples
6.2.1 16 Bit access
Example 1:
Reading parameter Active Power 213 (0x00D5) in data set 0 from the inverter with address 1.

Field: SoF Addr. Fct.Code DSet/Par-No. No. of Regs LRC EoF
ASC : 0 1 0 3 0 0 D 5 0 0 0 1 2 6 CR LF
Hex 3A 30 31 30 33 30 30 44 35 30 30 30 31 32 36 0D 0A

Field: SoF Addr. Fct.Code
No. of
Bytes
Par-Wert LRC EoF
ASC : 0 1 0 3 0 2 0 1 2 C C D CR LF
Hex 3A 30 31 30 33 30 32 30 31 32 43 43 44 0D 0A

The hexadecimal value sent is 0x001E = 300. Parameter Active Power 213 has one decimal places.
Therefore, the active Power is 30,0kW

Example 2:
Reading parameter Active Power 213 (0x00D5) in data set 0 from the inverter with address 1 and
No. of Regs field set to 2 (invalid value).

Field: SoF Addr. Fct.Code DSet/Par-No. No. of Regs LRC EoF
ASC : 0 1 0 3 0 0 D 5 0 0 0 2 2 5 CR LF
Hex 3A 30 31 30 33 30 30 44 35 30 30 30 32 32 35 0D 0A


Except.
Code
LRC EoF
ASC : 0 1 8 3 0 4 7 8 CR LF
Hex 3A 30 31 38 33 30 34 37 38 0D 0A

The sent exception code is hexadecimal value 0x04 = SLAVE DEVICE FAILURE.


40
Modbus 01/2013

Example 1:
decimal place.

Field: SoF Addr. Fct.Code DSet/Par-No. Para-Value LRC EoF
ASC : 0 3 0 6 5 3 F C 0 0 3 2 C 6 CR LF
Hex 3A 30 33 30 36 35 33 46 43 30 30 33 32 43 36 0D 0A

ASC : 0 3 0 6 5 3 F C 0 0 3 2 C 6 CR LF
Hex 3A 30 33 30 36 35 33 46 43 30 30 33 32 43 36 0D 0A


Example 2:
inverter with address 3.

ASC : 0 3 0 6 5 3 F C 0 0 6 E 5 E CR LF
Hex 3A 30 33 30 36 35 31 37 38 30 30 36 45 35 45 0D 0A


Field:
SoF Addr. Fct.Code
Except.
Code
LRC EoF
ASC : 0 3 8 6 0 4 7 3 CR LF
Hex 3A 30 33 38 36 30 34 37 33 0D 0A


41
01/2013 Modbus

Example 1:
decimal place.

Field SoF Addr.
Fct.Co
de
DSet/Par-No. No. Registers
No.
Byte
Para-Value LRC EoF
ASC : 0 1 1 0 5 3 F C 0 0 0 1 0 2 0 0 3 2 6 B CR LF
Hex 3A 30 31 31 30 35 33 46 43 30 30 30 31 30 32 30 30 33 32 36 42 0D 0A

Field SoF Addr.
Fct.Co
de
DSet/Par-No. No. Registers LRC EoF
ASC : 0 1 1 0 5 3 F C 0 0 0 1 9 F CR LF
Hex 3A 30 31 31 30 34 31 37 38 30 30 30 31 39 46 0D 0A

Example 2:
inverter with address 1

Field SoF Addr.
Fct.Co
de
No.
Byte
Para-Value LRC EoF
ASC : 0 3 1 0 5 3 F C 0 0 0 1 0 2 0 0 6 E 2 D CR LF
Hex 3A 30 33 31 30 35 33 46 43 30 30 30 31 30 32 30 30 36 45 32 44 0D 0A


Field:
SoF Addr. Fct.Code
Except.
Code
LRC EoF
ASC : 0 1 9 0 0 4 6 B CR LF
Hex 3A 30 31 39 30 30 34 36 42 0D 0A



42
Modbus 01/2013

6.2.2 32 Bit access
Example 1:
Reading parameter Frequency 850 (0x0352) in data set 0 from the inverter with address 1.


Feld: SoF Addr. Fct.Code DSet/Par-No. No. Registers LRC EoF
ASC : 0 1 0 3 0 3 2 2 0 0 0 2 D 5 CR LF
Hex 3A 30 31 30 33 30 33 32 32 30 30 30 32 44 35 0D 0A


Feld: SoF Addr. Fct.Code No. Byte Para-Value LRC EoF
ASC : 0 1 0 3 0 4 0 0 0 9 2 7 C 0 0 8 CR LF
Hex 3A 30 31 30 33 30 33 32 32 30 30 30 32 44 35 30 38 0D 0A

The hexadecimal value sent is 0x0000EA60 = 600000. Parameter Fixed Frequency 481 has four
decimal places.
Therefore, the frequency is 60.0000 Hz.

Example 2:
Reading parameter Frequency 850 (0x0352) in data set 0 from the inverter with address 1 and No.
of Regs field set to 1 (invalid value).


ASC : 0 1 0 3 0 3 5 2 0 0 0 1 A 6 CR LF
Hex 3A 30 31 30 33 30 31 45 30 30 30 30 31 41 36 0D 0A


Field:
SoF Addr. Fct.Code
Except.
Code
LRC EoF
ASC : 0 1 8 3 0 4 7 8 CR LF
Hex 3A 30 31 38 33 30 34 37 38 0D 0A


43
01/2013 Modbus

Example 1:
Writing parameter Fixed Frequency 3 482 (0x01E2) in data set 9 (= RAM for data set 4) to the in-
The frequency is to be set to 44.50 Hz. Parameter Fixed Frequency 3 482 has two decimal places.


Feld: SoF Addr. Fct.Code DSet/Par-No. No. Registers No. Byte Para-Value LRC EoF
ASC : 0 1 1 0 9 1 E 2 0 0 0 2 0 4 0 0 0 0 1 1 6 2 0 3 CR LF
Hex 3A 30 31 31 30 39 31 45 32 30 30 30 32 30 34 30 30 30 30 31 31 36 32 30 33 0D 0A

ASC : 0 1 1 0 9 1 E 2 0 0 0 2 7 A CR LF
Hex 3A 30 31 31 30 39 31 45 32 30 30 30 32 37 41 0D 0A

Example 2:
Writing parameter Fixed Frequency 3 482 (0x01E2) in data set 9 (= RAM for data set4) to the in-
The frequency is to be set to the invalid value 2000.00 Hz. Parameter Fixed Frequency 3 482 has two
decimal places.
Therefore the value to be sent is 20000 = 0x00030D40.

Field SoF Addr.
Fct.Co
de
No.
Byte
Para-Value LRC EoF
ASC : 0 1 1 0 4 1 7 8 0 0 0 1 0 2 0 0 0 0 3 3 CR LF
Hex 3A 30 33 30 36 32 31 37 38 30 30 30 31 30 32 30 30 30 30 33 33 0D 0A


Field:
SoF Addr. Fct.Code
Except.
Code
LRC EoF
ASC : 0 1 9 0 0 4 6 B CR LF
Hex 3A 30 31 39 30 30 34 36 42 0D 0A


44
Modbus 01/2013

Example 1:
Reading parameter Fixed Frequency 2 481 in data set 0 from the inverter with address 1.

Field: SoF Addr. Fct.Code DSet/Par-No. LRC EoF
ASC : 0 1 6 4 0 1 E 1 B 9 CR LF
Hex 3A 30 31 36 34 30 31 45 31 42 39 0D 0A

Field: SoF Addr. Fct.Code Para-Value LRC EoF
ASC : 0 1 6 4 0 0 0 0 0 3 E 8 B 0 CR LF
Hex 3A 30 31 36 34 30 30 30 30 30 33 45 38 42 30 0D 0A

The hexadecimal value sent is 0x000003E8 = 1000. Parameter Fixed Frequency 2 481 has 2 decimal
places.
Therefore, fixed frequency 2 = 10.00 Hz.

Example 2:

Field: SoF Addr. Fct.Code DSet/Par-No. LRC EoF
ASC : 0 1 6 4 2 6 4 0 3 5 CR LF
Hex 3A 30 31 36 34 32 36 34 30 33 35 0D 0A

Except.
Code
LRC EoF
ASC : 0 1 E 4 0 2 1 9 CR LF
Hex 3A 30 31 45 34 30 34 31 37 0D 0A


45
01/2013 Modbus

Example 1:
Writing parameter Rated Frequency 375 (0x0177) in data set 2 to inverter with address 1.

The rated frequency is to be set to 10.00 Hz. Parameter Rated Frequency 375 has two decimal plac-
es.
Therefore the value to be sent is 1000 = 0x03E8.

Field: SoF Addr. Fct.Cod DSet/Par-No. Para-Value LRC EoF
ASC : 0 1 6 5 2 1 7 7 0 0 0 0 0 3 E 8 1 7 CR LF
Hex 3A 30 31 36 35 32 31 37 37 30 30 30 30 30 33 45 38 31 37 0D 0A

ASC : 0 1 6 5 2 1 7 7 0 0 0 0 0 3 E 8 1 7 CR LF
Hex 3A 30 31 36 35 32 31 37 37 30 30 30 30 30 33 45 38 31 37 0D 0A


Example 2:
Writing out of range value to 9.00 Hz to parameter Rated Frequency 375 (0x0177) in data set 2 of
the inverter with address 1.

Parameter Rated Frequency 375 has 2 decimal places. The value to be sent is 900 = 0x0384

ASC : 0 1 6 5 2 1 7 7 0 0 0 0 0 3 8 4 7 B CR LF
Hex 3A 30 31 36 35 32 31 37 37 30 30 30 30 30 33 38 34 37 42 0D 0A

Except.
Code
LRC EoF
ASC : 0 1 E 5 0 4 1 6 CR LF
Hex 3A 30 31 45 35 30 34 31 36 0D 0A



46
Modbus 01/2013

Example 1a:
Clearing all Diagnostic Counters (Sub-function 0x0A) in the inverter with address 1.


Field: SoF Addr. Fct.Code Sub-function Data LRC EoF
ASC : 0 1 0 8 0 0 0 A 0 0 0 0 E D CR LF
Hex 3A 30 31 30 38 30 30 30 41 30 30 30 30 45 44 0D 0A


Field: SoF Addr. Fct.Code DSet/ Para-No. No. of Regs LRC EoF
ASC : 0 1 0 8 0 0 0 A 0 0 0 0 E D CR LF
Hex 3A 30 31 30 38 30 30 30 41 30 30 30 30 45 44 0D 0A

The response is an echo of the request. All counters are now set to zero.

Example 1b:
With all counters set to zero, read Diagnostic Counter 4, "Slave Message Count" (Sub-function 0x0E)
from the inverter with address 1.

ASC : 0 1 0 8 0 0 0 E 0 0 0 0 E 9 CR LF
Hex 3A 30 31 30 38 30 30 30 45 30 30 30 30 45 39 0D 0A

ASC : 0 1 0 8 0 0 0 E 0 0 0 1 E 8 CR LF
Hex 3A 30 31 30 38 30 30 30 45 30 30 30 31 45 38 0D 0A

Example 2:
Read unknown Diagnostic Counter 8 (Sub-function 0x13) from inverter with address 1.

Response: Master Inverter
ASC : 0 1 0 8 0 0 1 3 0 0 0 0 E 4 CR LF
Hex 3A 30 31 30 38 30 30 31 33 30 30 30 30 45 34 0D 0A

Except.
Code
LRC EoF
ASC : 0 1 8 8 0 1 7 6 CR LF
Hex 3A 30 31 38 38 30 31 37 36 0D 0A

The exception code sent is hexadecimal value 0x01 = ILLEGAL FUNCTION.

47
01/2013 Modbus

6.3 ASCII-Table (0x00 0x7F)
Dec. Hex. Char. Dec. Hex. Char. Dec. Hex. Char.
0 00 NUL 43 2B + 86 56 V
1 01 44 2C , 87 57 W
2 02 STX 45 2D - 88 58 X
3 03 ETX 46 2E . 89 59 Y
4 04 EOT 47 2F / 90 5A Z
5 05 ENQ 48 30 0 91 5B [
6 06 ACK 49 31 1 92 5C \
7 07 BEL 50 32 2 93 5D ]
8 08 BS 51 33 3 94 5E ^
9 09 TAB 52 34 4 95 5F _
10 0A LF 53 35 5 96 60 `
11 0B VT 54 36 6 97 61 a
12 0C FF 55 37 7 98 62 b
13 0D CR 56 38 8 99 63 c
14 0E 57 39 9 100 64 d
15 0F 58 3A : 101 65 e
16 10 59 3B ; 102 66 f
17 11 60 3C < 103 67 g
18 12 61 3D = 104 68 h
19 13 62 3E > 105 69 i
20 14 63 3F ? 106 6A j
21 15 NAK 64 40 @ 107 6B k
22 16 65 41 A 108 6C l
23 17 66 42 B 109 6D m
24 18 67 43 C 110 6E n
25 19 68 44 D 111 6F o
26 1A 69 45 E 112 70 p
27 1B ESC 70 46 F 113 71 q
28 1C 71 47 G 114 72 r
29 1D 72 48 H 115 73 s
30 1E 73 49 I 116 74 t
31 1F 74 4A J 117 75 u
32 20 SPACE 75 4B K 118 76 v
33 21 ! 76 4C L 119 77 w
34 22 77 4D M 120 78 x
35 23 # 78 4E N 121 79 y
36 24 $ 79 4F O 122 7A z
37 25 % 80 50 P 123 7B {
38 26 & 81 51 Q 124 7C |
39 27 ' 82 52 R 125 7D }
40 28 ( 83 53 S 126 7E ~
41 29 ) 84 54 T 127 7F DEL
42 2A * 85 55 U

Values used often are highlighted in grey.

Parameter List

48
Modbus 01/2013

7 Parameter List
7.1 Parameters ("Para" Menu)

Parameter
No. Description Units Value Range Chapter
RS485/RS232
395 Protocol - Selection 2.1
Modbus (RTU/ASCII)
010 Modbus Baud rate Baud Selection 3
413 Modbus Watchdog Timer s 0 1000 3
1375 Modbus Parity - Selection 3
1376 Modbus Address - 1 247 3

49
01/2013 Modbus

8 Bus Error Messages

VABus
10
Watchdog for X21-Connection. Communication error according to Parameter X21: VA-
Bus Watchdog Timer 1502.
F20
11
Watchdog for Communication Module. Communication error according to Parameter
CM: VABus Watchdog Timer 413.

The Actual error message can also be read out by parameter access via parameter Actual Fault 260.
Parameter Actual Error 259 shows the actual error in clear text on the operator panel and the PC
software tool VPlus.

Modbus GB

Uploaded by

Copyright:

Available Formats

Modbus GB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Modbus GB

Uploaded by

Copyright:

Available Formats

3

You might also like