Gauge cluster goes blank.

[samgm2]

After connecting to my (2007 Cobalt), the console displays a lock and I cannot start the vehicle.

The car has an E-37 computer.

ideas?

[Duramax 6.6L]

Sounds like the security system is activated. Did you get any error codes?

[samgm2]

Sounds like the security system is activated. Did you get any error codes?

I didn't check. The car is a 2007 Chevy Cobalt, at least not with the EFILive scanner.

Earlier, I attempted to put in a 2010 Chevy HHR VCM and and BCM. Unfortunately, I didn't have the VTD from that HHR at the time. Things didn't work, so I went back to the Cobalt VCM and BCM. Everything appeared to function correctly once again. My EFILive tuner arrived the next day. That was my first attempt at a connection.

I do notice the lock icon come up on the gauge cluster when I attempt to connect the scanner. This is all in an attempt to get the flex fuel function working in a Cobalt...

How do I get around this? The car functions just fine otherwise and I can scan it and update the VCM with the HP Tuners hardware and everything works. Unfortunately, the HP Tuners hardware won't work with a 2.2 L HHR (what a pain). That is why I switched to EFILive. I would like to mate the EFILive Hardware with the HHR VCM, BCM, VTD. For now however, I am just trying to scan the Cobalt (stock).

Is this a security problem with the Cobalt, or is it a security problem with EFILive?

[GMPX]

Sam, there is no known issues with any E37 vehicles so whatever is happening to you is a first.
I can't quite figure out what you are saying though, are you suggesting that just plugging the V2 in and attempting to use the scantool is causing the car to not start?

[samgm2]

Yes, once the unit is plugged into either a 2007 Cobalt or HHR, the vehicle will not start. The lock icon on the vehicle's instrument cluster is illuminated and none of the gauges will work.

If the unit is plugged in AFTER the vehicle is already running, the engine continues to run but the gauges all go dead and the lock icon is again illuminated. The unit does get a data stream however and logging is possible.

This problem does not manifest itself on a 2007 Sky (redline) or a 2000 Blazer.

I sure could use some help here. I purchased this unit SPECIFICALLY to target the E-37 and E-38 computers. This is for Flex Fuel research.

A question:

Is a license required to scan a vehicle?



Sam, there is no known issues with any E37 vehicles so whatever is happening to you is a first.
I can't quite figure out what you are saying though, are you suggesting that just plugging the V2 in and attempting to use the scantool is causing the car to not start?

[joecar]

No, license is needed for flashing only.

I suspect something like either of these:
- scantool's module bus id is being used by another module,
- ECM is communicating exclusively with scantool and ignoring some other module.

Try disabling some of the other modules one-by-one (by pulling their fuses).

[MisterBill]

Hi, I'm Bill and am working with Sam on this FFV research with the Cobalt and HHR vehicles.

For starters I would like to point out that we are not hobbyists...this is a real project with real money and real schedules involved and spending time troubleshooting a $800-$1000 off the shelf product, while it might be fun for Sam and myself as we do enjoy tinkering, is not something the people we report to are going to be ok with. Sam also had a ticket open with the support department that was CLOSED based on the last post in this thread. This is also unacceptable as no solutions have been provided as of yet.

With that said...disabling any of the vehicle's modules is completely meaningless as the vehicle would be in a non-operating state at that point. I propose instead that we consider the fact that the firmware version of our V2 is dated 7/6/11 and our first attempt to scan was on 7/10/11 (forgive me I didn't make note of the version number just the date). If this problem is indeed a "first" then our suspicion is a recently introduced firmware bug. Is there a way we can revert back to a KNOWN good firmware version? (granted there may be other bugs, but all we want to know is if the dead instruments symptom goes away with a different firmware version...and this should be a very quick and easy test to do).

Is there a way to identify the most recent firmware version that is known to work with an E37 equipped vehicle?

Thanks,

Bill

[GMPX]

Hi Bill,

I'm going to send Sam an Email right now explaining how to get around your issue, we figured out what is wrong.

Cheers,
Ross

[MisterBill]

Hi Ross,

I just got off the phone with Sam...he did get your email and will try your suggestion to disconnect pin 1 of the data link connector tomorrow.

Thanks for the prompt reply.

Bill

[MisterBill]

Removing the pin 1 (low speed data) did indeed correct the instrument cluster problem. It brings up another rather interesting question though (to us anyway)...why did it fail ONLY on the E37 computer? Should it not have blown up on the other two cars we tried it on (or for that matter anything that uses the low speed data bus to drive the instrument cluster)?

Inquiring minds want to know!

Bill

[GMPX]

I don't think all GM's cars used the Low Speed CAN bus, most just share all the data over the high speed CAN bus.