I’ve encountered error 0x65360 on an axis (Panasonic A6B) which cannot be cleared and is unable to resume, enable and operate to run again. As stated on the driver’s manual, it seems to be a PDO Watchdog Error Protection as shown below:
Everything else seems to be operating as usual as the network is still operational. This error seems to occur after prolonged period of operation (running for 20+ days). A network/controller restart, restarting INtime node or power-cycling the driver does not help with clearing the error. Only when power-cycling the PC can help with clearing away the error.
May I know what might be the root cause of this issue?
Initially thought it might be the PC affecting the PDO communication from master to the drivers as few axes returned error 0x65360 and few axes returned “No error”
And restarting the PC helped to clear away the error which might signify that the RMP/RMP network is starved from resources but I’m not sure if this is the case
PC Specs for reference
Processor: 12th Gen Intel(R) Core™ i7-12700, 2100Mhz, 7 Core(s)
RAM: 16GB
Graphics: Nvidia GTX 1660 Super
An interesting problem. I think we’ll want to collect some of the logs when it in the failing state to get to the root cause. Let me provide some though for now.
I’ve seen something similar to this once before when a different node on the network was taking an unusually long time to transition through its state machine. It wasn’t the faulting node, but a different drive’s delays which caused it once per power cycle of that other faulting drive. We can test this by reducing the network down to just the Panasonic to see what happens.
An issue with startup timing this is not fixed by a NodeA restart, but is fixed by the PC boot cycle makes me wonder if something on the Windows side has bloated to take up resources. You could look for anything out of the ordinary in TaskManager. The state machine should be transitioning within the RTOS. This doesn’t feel like a good explaination.
Steps for Data collection:
Before the issue arises, capture some Windows Task Manager details for later comparison.
Start RMPNetwork.rta on a good start to capture output for comparison with the later bad ones.
Shutdown the network and start normally.
Once the problem occurs, power cycle the Panasonic drive.
Start RMPNetwork.rta and capture the output for study.
If the Panasonic is still in error, power cycle it again.
Reduce the network down to just that 1 node.
Start RMPNetwork.rta and capture the output.
