IMO iDrive2 XKL Instruction Manual page 81

iDrive2 inverters
If Modbus communication is used to control the hibernation restore delay time as 5.0s. Firstly, 5.0 can be
magnified by 10 times to integer 50 (32H) and then this data can be sent.
After the inverter receives the command, it will change 50 into 5 according to the fieldbus ratio value and then set
the hibernation restore delay time as 5s.
Another example, after the upper monitor sends the command of reading the parameter of hibernation restore
delay time ,if the response message of the inverter is as following:
Because the parameter data is 0032H (50) and 50 divided by 10 is 5, then the hibernation restore delay time is 5s.
7.3.6 Fault message response
There may be fault in the communication control. For example, some parameter can only be read. If a writing
message is sent, the inverter will return a fault response message.
The fault message is from the inverter to the master, its code and meaning is as below:
Code Name
01H Illegal command
Illegal data
02H
address.
Illegal value
03H
04H Operation failed
05H Password error
06H Data frame error
Written not
07H
allowed.
The parameter
can not be
08H
changed during
running
The command from master can not be executed. The reason maybe:
1. This command is only for new version and this version can not realize.
2. Slave is in fault state and can not execute it.
Some of the operation addresses are invalid or not allowed to access.
Especially the combination of the register and the transmitting bytes are
invalid.
When there are invalid data in the message framed received by slave.
Note: This error code does not indicate the data value to write exceed the
range, but indicate the message frame is an illegal frame.
The parameter setting in parameter writing is invalid. For example, the
function input terminal can not be set repeatedly.
The password written to the password check address is not same as the
password set by P7.00.
In the frame message sent by the upper monitor, the length of the digital frame
is incorrect or the counting of CRC check bit in RTU is different from the lower
monitor.
It only happen in write command, the reason maybe:
1. The written data exceeds the parameter range.
2. The parameter should not be modified now.
3. The terminal has already been used.
The modified parameter in the writing of the upper monitor can not be
modified during running.
81
Communication protocol
Meaning