Hi,

I am working on a project where we have CANopen communication between a safetyPLC (CANopen Manager / master)and an industrial PC (slave).
It's working pretty well, except for this one issue;

When the PC slave device shuts off, CANopen stops. But when the PC comes back up again, the CANopen communication does not resume until I do a PLC restart (power off and on), or code re-download.

In our application, we use the S_CANopen_PC_SIL2.S_xActive to monitor communication status.
I experimented by setting S_CANopen_PC_SIL2.xEnable to true and to acknowledge error once it goes down, and like this I am able to get the CANopen to resume after PC slave comes back alive. However this only works for 1 time.
I don't know why it only does the trick once.

This is the sequence currently:
PLC & PC up an running : S_CANopen_PC_SIL2.S_xActive = TRUE , no errors
PC stops communicating : S_CANopen_PC_SIL2.S_xActive = FALSE , still no errors
PC comes back alive : S_CANopen_PC_SIL2.S_xActive = TRUE , no errors - successfully re-established once.
PC stops again : S_CANopen_PC_SIL2.S_xActive = FALSE , now I get error : SCT_timout instantly .
PC comes back alive, (sends same NMT bootup message as before) : S_CANopen_PC_SIL2.S_xActive = FALSE

Note: The time of the PC being off doesn't seem to have an effect, first xEnable it always comes back up, second time it doesn't.

Ideally CANopen manager should be the one to control the xEnable of the slave device, and our application should only monitor the status. I will attach the current CANopen manager settings.

How could I get CANopen to re-establish the communication after it stops once for any reason?

Thanks in advance,
Djordje

did you try:
https://help.codesys.com/webapp/EJRR-G2buObcxgy7pR9gJbNzzcI%2FCANRemoteDeviceSafe;product=3S%20CANopenSafety;version=3.5.17.0
to set S_xErrorAck to quit this error?
and check - S_eError for the result.
SCT Timeout means: Telegrams did not arrive in time
Maybe a good option is to ask the plc manufacturer, this is what I would recommend