Corrected from:
Controller 3200 C V3.3.2
Controller p500 V3.3.2
Behaviour of the new version?
Irrespective of whether a connection to the CAN slaves at the CAN interface has been established via the Ethernet interface of the controller, the controller switches the CAN slaves to operational.
What happens?
- The CAN master of the CAN card does not switch the CAN slaves to operational.
- By means of an external HMI or an Engineering tool such as EASY Starter or L-force Engineer, or an HMI connected to the Ethernet interface, no connection to the CAN slaves can be established.
When does the problem occur?
The responses described above occur if a connection via the Ethernet interface of the controller to the CAN slaves at the CAN interface of the controller has already been established when the controller is switched on. In this case, the CAN slaves are accessed via the OPC server of the controller.
Example:
When the controller is started, there is an 'Ethernet – CAN via the Lenze controller' connection to the CAN slaves from the EASY Starter.
Which products are affected?
Controller 3200 C from V3.0
Controller p500 from V3.3
MC-CAN2 CAN card
Diagnostics options?
No telegrams are sent anymore.
Short-term measures/recommendations?
Disconnect the connection between the external HMI or Engineering tool and the CAN slaves and switch the mains of the controller.
Evaluation:
The functional restriction occurs if CAN nodes that are connected to the CAN interface of the controller are already accessed via the Ethernet interface of the controller when the controller is switched on.
