# Revision history [back]

The schunk_lwa4d reflects the (special?) configuration that was use with Care-O-bot 4. As the init service error implies node 3 could not be reached.

This might have several reasons: * There is no node 3. Module IDs can be set freely. The Care-O-bot convention for LWA4d is 3-9. * Your bitrate is not correct. (Not sure if 500k or 1M is the default) * Your modules are not in CANopen mode.

You can check/set these things with the software tools provided by Schunk.

The node IDs can also read with candump: Just start candump can0 before powering on. While boot-up the devices should send messages with IDs 0x700 + node ID (hex!)

The schunk_lwa4d schunk_lwa4d package reflects the (special?) configuration that was use used with Care-O-bot 4. As the init service error implies node 3 could not be reached.

This might have several reasons: * reasons:

• There is no node 3. Module IDs can be set freely. The Care-O-bot convention for LWA4d is 3-9. * 3-9.
• Your bitrate is not correct. (Not sure if 500k or 1M is the default) * default)
• Your modules are not in CANopen mode.

mode.

You can check/set these things with the software tools provided by Schunk.

The node IDs can also read with candump: Just start candump can0 before powering on. While boot-up the devices should send messages with IDs 0x700 + node ID (hex!)

The schunk_lwa4d package reflects the (special?) configuration that was used with Care-O-bot 4. As the init service error implies node 3 could not be reached.

This might have several reasons:

• There is no node 3. Module IDs can be set freely. The Care-O-bot convention for LWA4d is 3-9.
• Your bitrate is not correct. (Not sure if 500k or 1M is the default)
• Your modules are not in CANopen 402 mode.

You can check/set these things with the software tools provided by Schunk.

The node IDs can also read with candump: Just start candump can0 before powering on. While boot-up the devices should send messages with IDs 0x700 + node ID (hex!)