Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
I'm using Codesys V3.5.16.40 with Windows 64 Bit RTE V3.5.16.40
When the node is configured to be reset (flag in general setting of Canopen node), the Master doesn't wait until the node send its bootup message. The master starts with SDO request for device type (OD 1000h) after 1st node sends its bootup message and this leads to SDO timeout errors. Sometimes it also happens for other SDOs configuring PDOs.
If disabling this general reset flag for the node, node configuration succeeds.
How can CANopen manager configured to wait for each node before configuring it or is this a bug?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm using Codesys V3.5.16.40 with Windows 64 Bit RTE V3.5.16.40
When the node is configured to be reset (flag in general setting of Canopen node), the Master doesn't wait until the node send its bootup message. The master starts with SDO request for device type (OD 1000h) after 1st node sends its bootup message and this leads to SDO timeout errors. Sometimes it also happens for other SDOs configuring PDOs.
If disabling this general reset flag for the node, node configuration succeeds.
How can CANopen manager configured to wait for each node before configuring it or is this a bug?