Correct Dick,In another thread someone quoted the LinearLogic troubleshooting information.
Primarily it was "manually set the communication protocol" instead of leaving it to snoop it out on its own.
No one reported "results" of that hint ... so use the buttons to get to the appropriate SETUP screen, and try the different protocols.
And then please report back.
--dick
Hi everyone, i did email linear logic and there response was to try another scangauge, which i did and the result was the same (stays connecting), at that point they suggested that i take it to someone that has more sophisticated obd reading hardware and see if we manage to make a connection with obd system. Now when i was buying the sprinter the dealership hooked the xentry computer and worked perfectly. So im beginning to believe that mercedes has devised a way to keep us out of the system.Correct Dick,
It was me replying to Damien following on from his comment on post 15 of this thread...
https://sprinter-source.com/forum/showthread.php?t=65480&page=2
His last comment then was that he was going to email Linear Logic but never posted a follow up.
Keith.
Yes it does, the other scangauge that i tried works all day long on my transit.Does it connect to a different vehicle's OBDII? Can you try another (gas powered) vehicle to see if it's the SGII, or the Sprinter's OBDII ?
Also, mine works with my Sprinter cab chassis, but I sent it to Linear Logic to get the firmware/software upgraded/flashed to 4.22+ level so it would work with the custom X-Gauges created by G. Chappell and James DeLong (of LL).
How do i force the communications protocol?Damien: did you *try* forcing the communications protocol?
(if you have a 2nd pre-2016 NCV3 available, you can snoop the ScanGauge to see what protocol IT chose)
--dick
So, you have 2 X Scangauges? You say "the other scangauge" works on another vehicle. Your Transit.Yes it does, the other scangauge that i tried works all day long on my transit.
One more quick question. Is the key in the "RUN" position, or the engine running, when you get the never ending "Connecting" message?How do i force the communications protocol?
The one off my transit didn't work on my sprinterBut will this ScanGauge work on your Transit or the one off your Transit work on your Sprinter?
I'll try that, thanks!So, you have 2 X Scangauges? You say "the other scangauge" works on another vehicle. Your Transit.
I meant you should try the same SGII that won't connect to your Sprinter, on a different vehicle, preferably gas, but not critical.
Unless I'm misreading your comments.
Dammit Cheyenne, you asked my question.
Yeah i tried all that even with the engine running, stays in the connecting screen then shuts down.One more quick question. Is the key in the "RUN" position, or the engine running, when you get the never ending "Connecting" message?
FORCE/SELECT THE PROTOCOL:
You'd have to connect to a different vehicle with it, or it could be powered by the OBDII that it won't connect to. (I think? never tried it)
Then press "MORE" then "MORE" then "MODE".
Using the left and right arrow buttons, you can scroll through the available list of protocols that the SGII supports.
From the SGII manual troubleshooting section:
Never stops saying
“Connecting...”
Vehicle ECU not on Turn key to RUN or start engine <<<<
ECU not responding properly
Use MORE>MORE>MODE and try
Forcing the following modes:
FORD Products: PWM or CANSF
GM Products: VPW , ISO or CANSF
Chrysler Products: ISO, VPW or CANSF
Volvo Products: ISO, CANSF or CANLF
Others: ISO, KWPS, KWPF, CANSF,
CANLF, CANSS or CANLS
Where to Get Support
Online: www.ScanGauge.com/support
www.facebook.com/ScanGauge
Toll Free: 1-888-433-5664
E-mail: support@linear-logic.com
Ok.... then what i'd do (on a day i was willing to trudge through "tedious, unrewarding") is plug it into the Transit ... where it will connect.Yeah i tried all that even with the engine running, stays in the connecting screen then shuts down.
Thanks!! Will have a go again at it tonight.OK.... my 2005 T1N uses the "KWPF" protocol.
Here's the scangauge manual for finding/forcing the protocol ("mode"):
View attachment 105970
... so it involves tapping the More button *twice* in rapid succession to get there,
then tapping the MODE button on the upper left.
(according to my manual, the Mode button is accessible when it's saying "Connecting...", but i couldn't test that)
...but you do need the key to be in the Run position.
If you do choose to manually select a Mode, run through the choices by tapping either button to the side of the displayed Mode.
When you reach one you want to try, press the FORCE button ... that locks it into the ScanGauge's memory.
That way it will be remembered as you trot the ScanGauge back from the Transit to the Sprinter.
good luck
--dick