Dynamic Node ID - Is this possible?

[Mr.Jacobee]

Hello,

I would like to ask whether it is possible, from PLUS+1 GUIDE code or from an already compiled application, to reset or restart a CAN interface without performing a full power cycle.

The reason is that I need to change the Node ID of a specific CAN interface during operation. The application involves connecting two machines which normally operate independently, but in this case they need to be linked together and behave as one machine in a Master-Slave configuration.

Ideally, I would like to change the Node ID and then restart or reinitialize only the CAN interface, so the new configuration becomes active without switching the whole controller off and on again.

Is this possible in PLUS+1 GUIDE, or is a full power cycle required for the CAN interface to apply the new Node ID?

Thank you for any advice or experience.

[Lukey]

It might be possible on a DM7/10/12 Display, as there is a reset/reboot/power cycle wire signal command.

On a controller/expansion module I don't think the above command is available.

[samuelhj]

Hello,

I would like to ask whether it is possible, from PLUS+1 GUIDE code or from an already compiled application, to reset or restart a CAN interface without performing a full power cycle.

The reason is that I need to change the Node ID of a specific CAN interface during operation. The application involves connecting two machines which normally operate independently, but in this case they need to be linked together and behave as one machine in a Master-Slave configuration.

Ideally, I would like to change the Node ID and then restart or reinitialize only the CAN interface, so the new configuration becomes active without switching the whole controller off and on again.

Is this possible in PLUS+1 GUIDE, or is a full power cycle required for the CAN interface to apply the new Node ID?

Thank you for any advice or experience.

This is a terrible idea. For multiple reasons I'm not going to even discuss here. The better solution would to keep the two things seperated by a controller that acts as a gateway between whatever 3rd party is listening and the two nodes. The design of the gateway would be heavily influenced  by what type of application you're applying this to and how the 3way communication should look like.