Waiting for ScanGaugeIII - Don't

Cowcatcher · **Posted:** Tue Jul 31, 2007 12:46 am

Since someone pre-nounce the ScanGaugeIII here weeks ago I have been checking their site and waiting for an announcement. I was getting impatient so I dropped them a note today. Here is Ron DeLong's answer:

Quote:

Dave,

We are not planning a ScanGaugeIII at this time. We are adding capability to the current ScanGaugeII by program upgrades and accessories. These will be announced on our website when they become available.

Ron

So, watch their site for software updates.

nix · **Posted:** Tue Jul 31, 2007 9:52 am

I'll definately be sending mine in when the update is available. BTW, the original sgIII thread had this in the opening paragraph:

Quote:

This was all a candid conversation over the phone.. so don't hold me to any details. Just thought you all would like to hear the gossip.

o8k · **Posted:** Tue Jul 31, 2007 9:14 pm

So just pretend you could'nt predict i would ask =D Anyone know if it fixes the Problem w/ communication faliure between CRD computer and SG?

Bill.Barg · **Posted:** Tue Jul 31, 2007 11:32 pm

Here is what I got as a response from Ron at Scangauge.

"We are not making an SG3 or planning to. We are going to be adding new features through new programming for the ScanGaugeII. Information on how to update your ScanGaugeII to add the new features will be available on our website when it becomes available.

I have heard that running the ScanGaugeII RATE at NORMAL or SLOW solves the shutdown problem on the jeep diesel.

Ron"

nix · **Posted:** Wed Aug 01, 2007 9:47 am

Bill.Barg wrote:

I have heard that running the ScanGaugeII RATE at NORMAL or SLOW solves the shutdown problem on the jeep diesel.

Ron"

Doing this does not fix the problem on my 2005 CRD.

Cowcatcher · **Posted:** Wed Aug 01, 2007 10:28 am

Gosh, I hope folks weren't thinking I was taking a poke at the ScanGauge folks or the earlier poster. I was trying to let people know not to wait like I was planning on doing.

The problem with the ScanGauge shutting down on the Liberty I believe has been well attributed to D/C and not the ScanGauge. Don't expect them, ScanGauge, to fix it.

nix · **Posted:** Wed Aug 01, 2007 1:20 pm

There was an interesting point brought up by another member here on L.O.S.T. (I don't remember their name).. who asked the question.. why doesn't the factory trip computer (EVIC) crash like the ScanGauge does? If I remember correctly, when you splice in an EVIC unit you tap into the OBD2 wires so... the physical source is the same. Do other OBDII readers crash?

Cowcatcher · **Posted:** Wed Aug 01, 2007 1:27 pm

I think that since most OBDII readers are handheld diagnostic tools most people plug them in, use them for a specific purpose, then unplug and go on with life rather than leaving them connected. I think the problem, as stated before, has to do with the Liberty design with the data conflicts assiciated with multiple data sources on the same data buss.

msilbernagel · **Posted:** Wed Aug 01, 2007 2:19 pm

Nix,

I think you're spot on. Obviously, the EVIC doesn't have this problem, so it is accomodating whatever problem the CRD's computer(s) have (there is some funky sharing arrangement with regard to which computer 'masters' the bus). Perhaps if we sent an EVIC to ScanGauge, they could watch the interaction on the bus and see how to make it work smoothly?

Either that or we need to kit up some EVICs!

Mark

nix wrote:

There was an interesting point brought up by another member here on L.O.S.T. (I don't remember their name).. who asked the question.. why doesn't the factory trip computer (EVIC) crash like the ScanGauge does? If I remember correctly, when you splice in an EVIC unit you tap into the OBD2 wires so... the physical source is the same. Do other OBDII readers crash?

kb61751 · **Posted:** Wed Aug 01, 2007 3:14 pm

The EVIC uses a different data bus at the ODB2 connector. You can force the scangage to look at this feed and get some info, but not much. VPW is what the scangage looks at for all the info, that drops off after a while, ISO is what the EVIC uses. If my memory is correct.

Bill.Barg · **Posted:** Thu Aug 02, 2007 8:27 pm

running the ScanGaugeII RATE at NORMAL or SLOW does not fix problem for me either.

o8k · **Posted:** Thu Aug 02, 2007 9:31 pm

Wonder if D/C is in non-compliance of OBDII standards here?

I was never so sure my EVIC wasnt crashing too, since its only giving avg mpg, one would never know immidiately. My SGII continues to update avg MPG also.... but it still gets valid mileage change value against a frozen fuel flow rate at time of crash.... If the EVIC does the same thing... but corrects for this since it also knows how much is in the tank (SGII does not) it stays more acurate even through the crash event..... Just a wild arse theory......

EDIT: and i also concur, no rate change fixes the problem, ive tried every setting in there.

I dont want to BLAME SG for this, its a fantastic tool worked flawless on my tdi jetta. Big Bad DC on this one! wish there was a hack SG could come up w/ to keep the thing runnin tho.

bugnout · **Posted:** Thu Aug 02, 2007 10:00 pm

Did a little test yesterday, I put the mode to auto and forced connection when I started out, then went back in to see what it was set too, vpw protocol as mentioned earlier. When the scangauge stopped working again, I set mode to auto and forced reconnection and this time it came up iso. only a couple of items worked, like rpm and mph

So looks like the vpw protocol is no longer available for the scangauge to find.

Cowcatcher · **Posted:** Thu Aug 02, 2007 10:19 pm

I think the issue is that the data is there somewhere but not at the OBDII connection. If you could pull it directly from its origin before it gets pushed into the shared OBDII buss that might help some but the problem will remain that the data that is wanted is not all coming from a single source. If you could capture it earlier you might still need to capture it on two different OBDII readers.

o8K - I don't know for sure but I suspect that there is no OBDII standard that requires continous running of all readouts. Certainly the ScanGauge continues to work there is just nothing there to read that you want. I bet if the CRD throws a code the ScanGauge would see that just fine.

MACKJ · **Posted:** Fri Aug 03, 2007 8:09 am

When I first tried my SGII I had set a code (the old ORM!) to test the beast.
It fired up on VPW protocol but did not see any codes.
Forced it to ISO then it found and cleared the code. :shock:

Is this normal?

Joe Romas · **Posted:** Fri Aug 03, 2007 9:18 am

MACKJ wrote:

When I first tried my SGII I had set a code (the old ORM!) to test the beast.
It fired up on VPW protocol but did not see any codes.
Forced it to ISO then it found and cleared the code. :shock:

Is this normal?

The BOSCH ecm uses ISO/CAN and the rest of the car uses VPW :roll:

Engine codes would be in the BOSCH controler :lol:

I read DC hacked the engine controler to make it communicate with the VPW protocol :lol:

I have a VAG-COM setup (for VW's) and it works well with our engine controler but does not see any of the VPW controlers

Waiting for ScanGaugeIII - Don't

Who is online