Trying to bridge????

Justin · #1 Sat, April 4th, 2009, 09:45 PM

Every time i plug my programmer into my truck it says its trying to bridge, please wait??? The truck is programmed to level two and i plugged it in and let it try to bridge for atleast ten minutes with no results. Also I noticed the clip on my cable is broken...I just got this two days ago...little frustrating...

***88Racing*** · #2 Sun, April 5th, 2009, 12:27 AM

Are you putting the plug in right?
Is the obd port plug inserted correctly?
Is the key in the on position and motor not running?
What's the temp?
What's the voltage?
If you are doing everything right you may have to let Bill, Corey, or Jack handle this.

Lars

***Jackpine*** · #3 Sun, April 5th, 2009, 01:29 AM

I'm not going to be much help either. The only time I've heard of the "trying to bridge" notification is when the Gryphon is plugged into a PC and has just finished updating the firmware. Bill has said the "bridge" is the communications circuit built into the OBD-II cable for the older vehicles (up to 2003).

Is yours a pre-2004 truck? And, to repeat Lars, did you have the ignition ON before plugging the Gryphon in?

If you answered YES to the first three questions Lars asked, I suspect the problem will have to be handled by Bill or Corey.

- Jack

Justin · #4 Sun, April 5th, 2009, 08:03 AM

Can you put the plugs in incorrectly? Dont really see how that could happen. The key is on with out the truck running. It was working fine when i pulled into the driveway last night, then when I started the truck this morning thats all I got, even after I let the truck get good and warm. It is pretty cold outside, but I wasnt trying to program it or anything just turned the truck on and thats all I could get. And yes the truck is a 2000.

***Jackpine*** · #5 Mon, April 6th, 2009, 01:21 AM

Ugh - OK, this is an "in use problem". Have you disconnected the Gryphon, turned the ignition ON, and then tried plugging it back in? (And maybe, looking at your original post, you HAVE tried that! - Sorry, I've had a busy day).

At this point, I haven't a clue unless it's possibly a low voltage problem (which I doubt). Wish I knew more about your MY programmer! I think the Mad Doctor is going to have to jump in here. Sorry, Bill - Help!

- Jack

Justin · #6 Mon, April 6th, 2009, 03:22 PM

Well, thanks for trying to help. Ive tried everything i could think of including pulling it all out and checking the cable and the ends to make sure they didnt get pinched or anything.