Eliminated from:
9400 HighLine SW V7.0
Behaviour of the new version?
Even where applications have a high bus load on the CAN on board, telegrams transmitted from the drive to the PC are not misinterpreted during SDO block data transfer (e.g. monitoring activities in the FB Editor of the
L-force Engineer). The SDO block data telegrams are sent in the correct order.
Description of the problem
When block data is read via CAN on board, the relevant SDO telegrams are sporadically sent in the wrong order. Evaluation at the receiver end leads to corresponding error messages (e.g. fields highlighted in red for monitoring activity in the FB Editor of the
L-force Engineer).
When does the problem occur?
The problem occurs when CAN on board is used, when a high bus load is already present and when SDO block data is also being transferred from the controller.
This kind of scenario will often arise when electrical shafts (=> high bus load) are being used via CAN on board and the
L-force Engineer is being used to work online via CAN at the same time, since the
L-force Engineer makes intensive use of SDO block data transfer.
Which products are affected?
9400 HighLine SW ≤ V5.1
Diagnostics options?
Instead of displaying the expected monitoring signals, the corresponding fields in the FB-Editor of the
L-force Engineer are highlighted in red (interrupted communication).
Short-term measures/recommendations?
- Carry out lower-priority data exchange, such as monitoring activities, using the L-force Engineer via an alternative interface (diagnostic adapter, Ethernet).
- Reduce the bus load on the CAN bus (e.g. implement the electrical shaft via digital frequency, powerlink, CAN slot module).
Evaluation:
The behaviour described here only occurs if there is a high bus load on the CAN on board and if SDO block data transfer is taking place at the same time. This will then result in communication faults during block data transfer.
This behaviour does not have any impact whatsoever on drive behaviour and it primarily arises during commissioning and maintenance work if the
L-force Engineer is used for online communication with the drive axis via CAN. In normal operation, block data transfer is only rarely implemented via CAN, so the behaviour is not usually seen.
Published with Service Message No. 38/2009
