Repeat DM1 to another CAN network

No, there is no way of repeating a multi-packeted message in a good way. We are considering adding something like this as a gateway function.

CAN routing now available in IQANdesign 5 on the MC4 modules.

Does the CAN routing forward DM1 messages? Because I don't get it to work.

I have a MC41 connected with CAN A - CAN A (The diagnostics bus) on a MC43.
The MC43 is connected to a MD4 via CAN B.

DM1 messages directly from the MC43 is displayed on the MD4 but I don't get any DM1 messages from the MC41.

In the CAN routing rules on the MC43, I have set from CAN A to CAN B and the "Default action" to "Allow" without any exceptions. 

The CAN frames for DM1 can be routed, but only if you do not use DM1 in channel in the application. 

We are looking at making this work in parallel. 

Hi Gustav.

I am using MC43FS and 7.02 IQAN design FW.

Has this DM01 routing function been updated recently? I have noticed, as per this conversation, that the DM01 wont rout if its being used by the application somewhere else (which I need it to do).

Also, to make things quite complicated. I have two (maybe three soon) sources of the DM01 messages (1x engine and 1x transmission CANC and 1x Engine CAND).  Engines are on separate CAN channels. but they all produce a DM01 message.

I want to route the DM01's (yes all three) to another single CAN channel (CANB).  But even if this eventually works, then how can I distinguish between them? Is there a means to re-config the source address through the routing, or some other means to allow the end processing device to collect these messages individually?

From 7.03, CAN routing of DM1 will work also when it is used by the application. 

The other question is more difficult, routed message will have the same CAN ID as the original message. You probably have the default SA 0 on all three. That will create a mess if route all to the same bus. 

Thanks.

If there was some means to re-tag the routed DM01 message (like modify the routed source address) then this would be close to a solution.  I have used this type of work around with another type of system.  Could you add this feature to your development?

Cheers!

I had missed that the DM1 message uses not only PGN 65226 but also 60160 and 60416.

Also, the "DM1 in channel" was assigned to the master responsible for the routing, rather than the master initially sending the DM1 message.