Lenze i510 - Modbus Function Codes

Parameter Name / value range / [default seng] Info
0x232F:017
(PAR 585/017)
Modbus diagnoscs of last TX data
: Data byte 15
(TX data diagnoscs: Last TxD byte15)
•
Read only
8.5.7 Modbus funcon codes
The mode of access to inverter data (parameters) is controlled via funcon codes.
Details
The inverter supports the following funcon codes:
Funcon code Funcon name Descripon
3 0x03 Read Holding Registers Read one or more 16-bit data words.
6 0x06 Preset Single Register Write a 16-bit data word.
16 0x10 Preset Mulple Registers Write one or more 16-bit data words.
23 0x17 Read/Write 4X Registers Write one or more 16-bit data words and read them back.
Addressing
•
The funcon codes listed above exclusively refer to 4X registers in Modbus addressing.
•
All data in Lenz
e drives can only be accessed via 4X registers, i.e. via register addresses start-
ing from 40001.
•
The 4xxxx reference is implicit, i. e. given by the funcon code used. In the frame therefore
the leading 4 is omied in the addressing process.
•
The numbering of the registers starts with 1; addressing, however, starts with 0. Therefore,
for instance, the address 0 is used in the frame when register 40001 is read.
Telegram structure
Communicaon is established on the basis of the central medium access method. Communi-
caon is always started by a master request. The inverter (slave) then either gives a valid
response or outputs an error code (provided that the request has been received and evalu-
ated as a valid Modbus frame). Error causes can be invalid CRC checksums, funcon codes
that are not supported, or impermissible data access.
All Modbus frames have the following basic structure:
•
A "frame" consists of a PDU (Protocol Data Unit) and an ADU (Applicaon Data Unit).
•
The PDU contains the funcon code and the data belonging to the funcon code.
•
The ADU serves the purposes of addressing and error detecon.
•
The data are repr
esented in Big Endian format (most signicant byte rst).
ADU (Applicaon Data Unit)
Slav
e address Funcon code Data Checksum (CRC)
PDU (Protocol Data Unit)
Error codes
Error code Name Cause(s)
0x01 Invalid funcon code The funcon code is not supported by the inverter, or the inverter is in a
state in which the r
equest is not permissible or in which it cannot be
processed.
0x02 Invalid data address The combinaon of a start address and the length of the data to be
transmied is invalid.
Example: If you have a slave with 100 registers, the rst register has the
address 0 and the last register has the address 99. If there is a request of
four registers now, from the start address 96, the request can be pro-
cessed successfully (for registers 96, 97, 98, and 99). If, however, ve reg-
isters from the start address 96 are queried, this error code is returned,
since the slave has no register with the address 100.
0x03 Invalid data value
The cause, however, is not that a (parameter) value is wrien outside
the valid seng range. As a maer of principle, the Modbus protocol
has no informaon on valid seng ranges of individual registers or their
meaning.
0x04 Slave device failure A non-correctable error has occurred while the request was processed in
the inverter.
Conguring the network
Modbus
Modbus funcon codes
131
Phone: 800.894.0412 - Fax: 888.723.4773 - Web: www.actechdrives.com - Email: info@actechdrives.com