Corrected from:
9400 HighLine V15.00.09
9400 Servo PLC V09.00.09
Response of the new version:
After a timeout, parameter read/write requests can be actuated again by a positive edge at the bExecute input.
What happens?
Parameter read/write requests are not executed as expected. The corresponding function block reports a timeout in dnState.
Even with a new positive edge at the bExecute input, the request cannot be executed successfully.
This behaviour may also occur when replacing a device with a new firmware version and the application remains the same.
When does this behaviour occur?
If a timeout error occurs while processing a parameter read/write request and the timeout is signalled immediately after actuating a new request by a positive edge at the bExecute input of the function block, processing "gets stuck" and, as a result, all subsequent requests will directly be confirmed with a timeout and will no longer be processed.
The above behaviour may always occur when a read/write request is confirmed with a timeout and automatic FB retriggering has been programmed
or when the function block is cyclically operated.
Which products are affected?
The following function blocks for writing and reading parameters from LenzeDevice9400 library version V02.11.01.00 or lower are affected:
L_DevParWriteFix, L_DevWriteParDInt, L_DevParReadFix, L_DevReadParDInt
There is no direct relationship with a firmware version in the 9400! The fact that the function restriction occurs with specific firmware versions and does not occur with other firmware versions is due to differences in the micro-timing.
Short-term measures:
Make sure that the timeout error won't occur
by selecting monitoring times that will not be exceeded, e.g. abort time C5924 = 2 s
or by completely deactivating the timeout check by selecting '0'.
Evaluation/recommendations:
As a result of the above function restriction, the device functions are not as expected when replacing devices with other firmware versions in an application.
So far the behaviour has only occurred once in a customer application and can be provoked with the above-described constellation in a test. Therefore, the probability of occurrence is low.
An applicative remedy is provided by changing the corresponding parameters.
