02-03-2009 03:14 AM
02-03-2009
09:18 AM
- last edited on
12-13-2024
02:12 PM
by
Content Cleaner
It seems like you somehow messed up the references for your SDO's. At least the error indicates that.
The error indicates that a SDO process is still pending and you started another one for the same SDO reference. That could indicate bus problems or starved message IDs because of priority or just a device that is not answering. The spy log file shows the notification waiting for 17 seconds, because the driver becomes unresponsive and reports the internal error.
Could you post a small example that shows the same behavior and your way of storing the references?
And could you try going back to NI-CAN 2.5.2 ? We had some changes to the way we report notification errors in 2.6 and perhaps the older version brings some more error information earlier in the game.
DirkW