M84 / ECUManager disconnects with SDL

[BJ 991]

Hey all,

Just working through the nitty gritty on a new setup.

When I'm using ECU Manager with the M84 connected through UTC, if I flick the SDL on (separate switch), the M84 will intermittently disconnect and reconnect, while showing a low memory error.

Is this normal? I would assume that I cannot connect to both at the same time, however, am I not able to have the dash on while the ECU is connected?

Cheers

[BJ 991]

No dice?

[greenamex2]

You tried raising a support case with Motec?

[BJ 991]

You tried raising a support case with Motec?

Not yet, was thinking someone might have some quick cheat-sheet info.

Looking at an old post, it seems they cannot connect in-sync as each uses the same CAN (one at a time) however the dash also isn't seeing the ECU so leads me to believe I either have a resistor in the wrong spot, or need to add one.

[Stephen Dean]

Hi,

When you say that the Dash doesn't see the ECU, is this happening constantly or only when the UTC is connected?

Sometimes you can get both devices talking on the CAN Bus and to the managers at the same time, but normally it will not happen. I have found that connecting the UTC to the CAN Bus and then starting the ECU Manager, followed by the Dash Manager is the most consistent way of connecting to all devices concurrently, but not always.

The computer that you use makes a difference as well. My old laptop with Windows 7 was much more consistent in getting multiple device connections compared to my current Windows 10 laptop.

[BJ 991]

Hi,

When you say that the Dash doesn't see the ECU, is this happening constantly or only when the UTC is connected?

Sometimes you can get both devices talking on the CAN Bus and to the managers at the same time, but normally it will not happen. I have found that connecting the UTC to the CAN Bus and then starting the ECU Manager, followed by the Dash Manager is the most consistent way of connecting to all devices concurrently, but not always.

The computer that you use makes a difference as well. My old laptop with Windows 7 was much more consistent in getting multiple device connections compared to my current Windows 10 laptop.

Heya Stephen,

Definitely correct on the computer. I'm on a Windows 10 laptop and it will even dropout from ECU Manager sporadically with no other interruptions or devices connected. Pain in the butt when you're in the middle of running the engine.

No Dash Visibility: That's a constant. I've set the M84 template in the SDL to pull in all the channels. However under Connections, the only one it sees is the SDL USB connection when that is plugged in to the laptop.

Yet, I suspect the SDL ECU CAN connection is there, for the aforementioned reasoned: If I've only got ECU Manager opened and connected through UTC, as soon as I turn the dash on, the ECU connection drops out. So I have reason to believe it wants to hog the CAN somewhere along the line as soon as it is powered. Though I'm sure there's a rookie error in here somewhere, so take that reasoning for what it is worth

Cheers

[Stephen Dean]

Hi,

You will not see the M84 listed under connections, as that is showing the dashes connected through the Dash Manager software.

When you are connected to the Dash, if you go to Online | Monitor Channels... and scroll down to Comms CAN x Diag, where x signifies the CAN Section that you have the M84 Receive templates on, and look at the reported value.

It is most likely to be one of the following;

256 Bad Config
512 No Data - Wiring fault or incorrect setup
4096 BUS Warning - Usually crossed wiring or a lack of terminating resistors

[BJ 991]

Hi,

You will not see the M84 listed under connections, as that is showing the dashes connected through the Dash Manager software.

When you are connected to the Dash, if you go to Online | Monitor Channels... and scroll down to Comms CAN x Diag, where x signifies the CAN Section that you have the M84 Receive templates on, and look at the reported value.

It is most likely to be one of the following;

256 Bad Config
512 No Data - Wiring fault or incorrect setup
4096 BUS Warning - Usually crossed wiring or a lack of terminating resistors

Cool beans, I will give that a go when I hit the shed.

Out of curiosity: will the CAN bus detect (and default to) the ECU connection if the UTC is left plugged in to the Deltron, albeit not hooked up to the USB cable.

IE: ... Should the UTC box itself actually be removed from the Deltron plug when it is not in use?

Cheers

[Stephen Dean]

You can leave the UTC permanently connected to the bus if needed, some people do so as there is a terminating resistor in the UTC as it serves as one of the terminating resistors.

[BJ 991]

You can leave the UTC permanently connected to the bus if needed, some people do so as there is a terminating resistor in the UTC as it serves as one of the terminating resistors.

Thanks Stephen.

Yep, she be 512'ing alright. Disadvantage of using someone's existing SDL loom without pulling it apart! Hate to cut into the glued Raychem and double boots.

So... Existing CAN BUS plug I had coming off the SDL loom was a 3 pin female plug that had (according to pin continuity check)

PIN 1: CAN LO pin 35 continuity (beep)
PIN 2: CAN HI pin 36 continuity (beep)
PIN 3: CAN HI pin 36 continuity (no beep, just 100ohm reading)

I assumed PIN 3 had the resistor doubled over in the loom at that end of the BUS, so I took PIN 1 and PIN 2, plugged them into a pre-made twisted CAN BUS section, and plugged that in to the spare, 2-pin CAN plug on the ECU loom. Of which as you just mentioned, that is connected to the Deltron plug, where there is a resistor hooked to the UTC plugged in to that end of the bus.

Loom is super small. Easily less than 1 metre.
*ponders*