Address Priorities

information about how to make an ECU (MoTeC or non MoTeC) work with a MoTeC dash or data logger

Address Priorities

Postby Trevan on Fri Mar 15, 2019 8:28 am

Hi,

I'm just starting out and doing some lessons on CAN so please excuse if this a silly question.

From what I have learnt about the arbitration process, my understanding is the lowest address will get priority on the bus. Looking at the default addressing in my M1 it appears that it uses address 0x7F0 while the other devices like LTC, PDM and C125 range from 0x400-0x600.

Is my understanding correct regarding the priorities? Without understanding the details I would have assumed you would want messages from the M1 to take priority.

Cheers,
Trevan
Trevan
 
Posts: 18
Joined: Sat Jan 21, 2017 7:31 am

Re: Address Priorities

Postby adrian on Fri Mar 15, 2019 9:10 am

Hi Trevan,

Although technically correct, it really doesn't matter in this case. If there is a message clash the one that loses arbitration is sent immediately after the message that wins (as long as it doesn't have another clash).

The maximum length of a CAN message is around 120-130 bits give or take some stuff bits. So if a message gets delayed by 1 message then it is a roughly 130uS delay (assuming a 1Mbit bus). The highest rate we transmit any messages out of the ECU is 100Hz (every 10ms) so the delay is nearly 2 orders of magnitude smaller than the transmit time.

So in this case it really doesn't matter what addresses are used, you'll never notice the delay even if there is a clash.

Adrian McGregor
MoTeC Australia
adrian
MoTeC
 
Posts: 589
Joined: Mon Apr 13, 2015 4:16 pm

Re: Address Priorities

Postby Trevan on Fri Mar 15, 2019 10:22 am

Hi Adrian,

Yes that makes a lot of sense. Classic example of textbook theory vs real world practice.

Thanks for the response mate.

Cheers,
Trevan
Trevan
 
Posts: 18
Joined: Sat Jan 21, 2017 7:31 am


Return to ECU to Dash Comms

Who is online

Users browsing this forum: No registered users and 1 guest