OBD Diagnostics Scanner Pro Issue
09-25-2018 | 04:50 PM
#12
Thread Starter
Registered
Joined: Jul 2015
Posts: 1,202
Likes: 89
From: Atlantic Southeast
Keith
10-02-2018 | 12:38 PM
#13
Thread Starter
Registered
Joined: Jul 2015
Posts: 1,202
Likes: 89
From: Atlantic Southeast
UPDATE
The only way to see one or the other with OBD's ScannerPro is with an coding change to the program itself each time you want to flip back and forth. In speaking with Rinda about the Diacom software they noted if both ECU's are internally programmed as slaves their software will do the same thing. I therefore, chose was to send both ECU's to MEFI Burn to have the master/slave architecture to be removed altogether. Currently waiting on the ECU's to be returned to me.
About a half hour after typing the above I found the below picture in my archive!!
Looks like the port side ECU master/slave connection wire. I probably tucked it away after taking the picture over a year ago and is why I didn't find upon my initial inspection. This may be the issue all along but will need to find out why its disconnected, what pin the red wire goes to and why, where the red wire connects on the other end and why. Fun times! Stand by...............
https://uniim1.shutterfly.com/ng/ser...537344/enhance
Keith
The only way to see one or the other with OBD's ScannerPro is with an coding change to the program itself each time you want to flip back and forth. In speaking with Rinda about the Diacom software they noted if both ECU's are internally programmed as slaves their software will do the same thing. I therefore, chose was to send both ECU's to MEFI Burn to have the master/slave architecture to be removed altogether. Currently waiting on the ECU's to be returned to me.
About a half hour after typing the above I found the below picture in my archive!!
Looks like the port side ECU master/slave connection wire. I probably tucked it away after taking the picture over a year ago and is why I didn't find upon my initial inspection. This may be the issue all along but will need to find out why its disconnected, what pin the red wire goes to and why, where the red wire connects on the other end and why. Fun times! Stand by...............
https://uniim1.shutterfly.com/ng/ser...537344/enhance
Keith
Last edited by Tractionless; 10-02-2018 at 01:23 PM.
10-25-2018 | 03:52 PM
#14
Thread Starter
Registered
Joined: Jul 2015
Posts: 1,202
Likes: 89
From: Atlantic Southeast
UPDATE
The issue of the thread is now solved and I can finally scan to find the original off idle surge problem.
MEFI Burn disabled the synchronization link between the ECU's but I still had to unplug each (engine) single yellow wire connector to 3 wire connector.
I confirmed data stream into the logger per engine when hooked to each engine DLC and each engine ignition on separately.
BUP,
Now I'd like to know why Merc would sync the engines via the harness.
Keith
The issue of the thread is now solved and I can finally scan to find the original off idle surge problem.
MEFI Burn disabled the synchronization link between the ECU's but I still had to unplug each (engine) single yellow wire connector to 3 wire connector.
I confirmed data stream into the logger per engine when hooked to each engine DLC and each engine ignition on separately.
BUP,
Now I'd like to know why Merc would sync the engines via the harness.
Keith
10-25-2018 | 09:19 PM
#15
Registered
Joined: Sep 2016
Posts: 50
Likes: 3
From: Minnesota
So who want to take stabs at why builders / riggers did this link EFI engines together with one multi engine data link harness for twin engine apps. What are the reasons for this ? Lets see who can come up with the correct answers. There is one more than one reason for this adaption.
With Volvo, it will also sync the water temp and oil pressure gauges when they are close to each other as well as providing engine RPM sync when both engines are close. But this is just on the newer engines. MEFI isn't smart enough to do that.
Last edited by muc; 10-25-2018 at 09:48 PM.
