Jump to content

Recommended Posts

Posted

Greetings!

 

I'm rebuilding a 2007 Chevy Express G2500, that had been wrecked in the front end. We've straightened the frame, replaced grill, bumper,& hood.  Prior to this work, the Dash Cluster operated properly, but,... After getting the above work done, the Dash Cluster Gauges would come on, & then the Voltage, Oil, Temperature gauges would rise & fall, & the "Security" & "Check Engine"& "Battery"  indicators would come on & then off. Putting a load on the Van, by turning on headlights, Flashers, & radio, has no effect, BUT,.... When the Gauges fall down,... The Radio quit working.  I stumbled in to learning that when the brake pedal was "Tapped", that everything would return to normal, but within 3 to 5 seconds, the "Possession of the Van" would start all over again. 

 

I then found that by putting slight pressure &/or pressing the brake pedal, that this issue disappears.

 

No Fuses have blown, & so far, I have not found any wire,directly making contact with the brake pedal assembly, neither under the dash, nor at the firewall near the Brake booster/reservoir assembly.

 

Do You have any ideas, any data, or any sources that you could direct me, so as to solve this problem? 

 

I am familiar with a Service Bulletin that had been issued via GM, that was addressing an issue similar to this, with part of the problem being in the wiring harness close to the "Brake Switch", but, have a problem in locating that Bulletin in the many files/Downloads/Videos that I have saved for my van. 

 

Regards,

David

Posted

Greetings Ya'll! 

 

This is my first post & more than likely there will be many more, as I rebuild my van

 

I bought a wrecked in the front end 2007 Chevy EXpress G2500, & after having straightened the frame, replaced the bumper & grill, lights, & hood, the Dash Cluster Gauges, & Indicator lights which had no problem before, then began to operate in an insane manner! The Temp., Oil, & Battery Gauges would rise & fall, & the "Security", "Check Engine", would go on & off.  I put a "load" on the system by tuning on the headlights, heater, & radio, but they had No Effect on what was happening, BUT,...... when the Gauges fell to 0, the radio also quit working every time, but the Heater Blower, Hazard lights, & Headlights continued to operate with no problems. 

 

I found by accident that by pressing on the brake pedal, & releasing it that everything would return to normal, including the radio for about 3-5 seconds, but then the "Van Possession" would then return. Again, nothing happens to the Hazards, Blower motor, nor Headlights.

 

Now here's Th' Kicker,... When I depress the Brake Pedal, the Dash Cluster works perfectly. When I release the brake pedal, then within 3-5 seconds the Dash Cluster & Radio then start the whole insane process over again.

 

Has anybody experienced this, & if so, how did you fix this nightmare? Is there a ground that may have become disconnected during Our Repairs, that is specific for the Dash & Radio?

 

And, can anyone tell me where to get the Dash wring diagram? 

 

 

Posted

Sounds to me like there's a ground with either a bad connection, or is not connected at all. With lack of ground, power will find other ways to get back to the battery, causing all kinds of strange issues. The good part is, you can concentrate on the front half of the vehicle to find it.

Posted

My first thought would be to check all the grounds in the dash and front end.  Also, if you replaced the cluster, did you have it programmed to the truck?  Best place to find a wiring diagram is in the factory shop manual, you might be able to find one reasonable on Ebay.

Posted

Greetings C/K,

 

Do you know of any GM Document, on Th' Net, that gives the location of the Frame, Body, Dash, & Motor Grounds? 

 

And, I've not replaced the Dash Cluster yet, and I'm thinking that it has more to do with a Ground,due to the Radio operating erratically, & that it everything goes back to normal when the brake pedal is depressed.

 

And, I'm going to hunt down that Factory Shop Manual that You mentioned.

 

Posted

The manual is best because it also has a component locater section which will show you exactly where the grounds (and other connectors and components) are located.  You might get lucky on the web but I don't know of any specific sites.

  • Thanks 1
Posted

Thank You C/KMan & diyer2!

 

I'll look in to the Manuals for sure.

 

What's been baffling me is how the radio quits working while all of this is ongoing, .... Other than possibly a Common Ground, do Ya'll know if whether the Dash Cluster also controls the radio?

 

And again Thank You!

  • 2 weeks later...
Posted

Greetings Jsdirt,

 

I have to apologize, I just saw your reply, & I never got a notification about any reply.

 

With My & My Son's work,& many other issues, we've made very little progress on working on my van.

 

Today, I learned about a ground location, via  a video from "Etrailer" about how to install a "trailer brake controller", as well as the ground wire & hot wire color that feeds the brake switch, & I'm hoping to get back over to work on the Van, & ck out these grounds & wires, work permitting, early next week.

 

And I appreciate your help Js!

  • Like 1
Posted

No problem. 🍻

 

There's usually a couple critical grounding points up front, such as one at the left body mount by the driver's door, and another on the back of one of the cylinder heads - I forget which one, but it's there. Also don't forget the basics like the battery connections and cables - check BOTH ends of the cables for a good connection. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...