Just hooked up ScanGauge II & immediately got these error codes

those are CAN communication errors. it may be a fluke, they may stay gone. unfortunately, they may not.

if they come back, get that SG out of there and head to the dealer.

 

an interruption or an abnormal spike on the CAN lines can cause that.

one can plug in something to the DLC3 port at any time. if the SG simply can't communicate with the prius, oh well, the prius can still communicate with itself. when the prius can't communicate with itself, then you start to get codes.

is that making sense?

 

I just received my scan gauge (as a birthday gift no less) and had the same problem after hooking it up tonight, except that my second code was different. The two I got were:

U0100
U0293

I basically did the same thing described by the OP above. I was also able to clear the codes, but it took a few restarts to get the "red triangle of death" to disappear. Gave me quite the scare for a few tense minutes there. I assume this was a CAN communication error as described above caused by starting my Prius with the scan gauge attached rather than starting it first and then connecting the scan gauge to allow it to initialize properly.

Green Hokie, if you're still out there, did those codes ever come back for you?

 

If the SG is causing canbus transients that kick U codes, then
that sounds like a problem Ron needs to look at asap. Other scan
tools don't do that.
.
_H*

 

<div class='quotetop'>QUOTE(hobbit @ Nov 2 2007, 01:28 AM) [snapback]533732[/snapback]</div>

Is Ron with LinearLogic? Do you have contact information or just go through their website.

In fairness, the owner's manual does state to turn the vehicle on prior to connecting the SG the first time. In both my case and that of the OP, we hooked up the SG initially prior to turing our Prius on in accessory mode. The codes did clear, the car operated normally this morning, and the SG seems to be functioning properly.

I should have read and followed the owner's manual more carefully before connecting the SG. However, it would be nice if it explicitly stated that connecting the SG for the intitial time prior to starting the car can cause CAN communication errors. I don't know if this is a Prius-specific problem or not.

 

Yeah, I know I'm bumping an ancient thread, but +1 for me.

I hooked up my SG today before powering on (have done this a few times) and hit the exact problems at the OP. I also got the red triangle of death, the yellow check engine light and a red car w/a ! on the MFD. I believe my power up was w/my foot on the brake.

IIRC, the triangle of death, CEL and ! car on the MFD went after a few power cycles. ScanGauge showed codes U0100 and U0111 were stored.

Luckily, I was leaving from the Toyota dealer after getting LSC A0N (inverter pump change) done and my transmission fluid changed. Hope it was just a fluke from my user error and me not following SG directions.

 

+1 for me yesterday when leaving work.

Plugged in my SG2 after turning the car off, when I turned it back on the SG2 said "Connecting..." and just after putting it in reverse and putting my foot on the go pedal the red triangle of death, check engine, red "problem" icon on the MFD.

Turned the car off and on about 5 times and it went back to normal. The SG2 shows U0100 and P0000; P0000 means the SG2 didn't read the code properly right?

 

I got the symptoms same as OP however mine happened after 10 mins of driving ... I was accelerating and I heard a nasty bump that you feel when the engine turns off and I was running on ev only .

I stopped and I couldn't power off the car and I can hear the fans running near the radiator . At this time the car gave me codes U0100 And U0293 ... Clearing the codes did nothing and after waiting for the fan to die down I can finally power off the car ... Losing engine power was scary ... I wonder by clearing the codes and not using scangauge would prevent the problem?

Freaked me out though as it happened as I was traveling at 56km per hour ... And then having no engine power ... And two icons came up ... One was the car with (!) and the other was the letters in caps PS...

This sucks

 

The manual says to turn your car on BEFORE plugging in your ScanGauge. Plugging it in with the car off intermittently causes CAN communication errors. It is OK to leave it plugged in between trips.

JeffD

 

Glad you said that Jeff as I leave my scangauge plugged in at all times with no ill effect.

 

I have a 2004 Prius and I have a scanner to look for check engine light codes which says to plug it in and then turn on the ignition of the car without turning on the engine. Which of course means pressing the button twice without foot on the break. I made the mistake of pressing the button once which means the ignition was not on and so the scanner started looking for codes and I turned on the car and I got the master warning light and the same other lights that Green Hokie got came on including the check engine light ( which may have already been on) and then I pressed the button on my scanner and it gave me the codes U0100 and P0000 and U0293. Codes that had been previously on there which I hadn't cleared were gone. Is it possible that because I had plugged in the scanner and had only pressed the ignition switch once which only turns on the MFD and not the ignition and pressed the button on the scanner could have caused me to have the Master Warning light come on along with getting the codes I got when I did have the car turned on?

 

As mentioned earlier those are "lost communication" codes because the ECUs were not talking because they weren't powered up.

Reconnect the proper way and I expect those issues won't reoccur, unless your connection to the car is loose.

 

So I didn't cause any permanent problem with the car communicating with itself by improper use of the scanner? So those codes are not going to be trigged again just because I connected the scanner wrong which will cause the cars ECU's not to communicate properly on their own without having used the scanner again? In other words by clearing the codes they shouldn't come back on their own unless something is wrong with the car not caused by connecting the scanner wrong?

 

I wouldn't head to a dealer I would find a good mechanic like I found where I live who works on hybrids because the dealer will charge you a lot more to fix the problem. I had to get an extra key fob made for my car which my mechanic charged me $150.00 for at the dealer it would have cost more then $300.00 dollars. I need it in case I lose the one I already had because if you lose it then you are screwed if you don't have another one.

 

Why would those codes cause the master warning light and the light on the MFD warning of a problem with the hybrid batteries to come on? Is because the ECU's were not communicating so the car thinks the hybrid batteries are not working right?