Jump to content

Recommended Posts

Posted

I was able to find only one socket so I replaced the one I thought most likely to be the culprit. Now the brake light with the new socket works and the other one doesn't when the headlights are turned on. In fact it is dimmer than before when the brakes are on with the headlights off. Does this make sense? I have another socket on order, be here Monday.

 

Interesting findings when shopping for a tail light socket. GM only services the tailight harness, $111.82 for each side. NAPA had the socket only with wire pigtails for $24.85. They also have the harness assy for $18.52 per side. So the harness assy which has 3 sockets, wire harness and connector to plug into the main harness is LESS than the socket only and over $93 LESS than GM. ??????

 

 

You may find you have the socket connected backwards. The bulb has two filaments, one brighter than the other. Parking light is the dim filament.

Posted

With park or headlights ON: both bulbs light the dimmer filament. When brake is pushed the bulb with the new socket lights the bright filament and the dim filament, the other light goes out.

 

With park or headlight OFF and brake pushed: The bulb with new socket lights the bright filament, the other one lights the dim filament.

Posted

With park or headlights ON: both bulbs light the dimmer filament. When brake is pushed the bulb with the new socket lights the bright filament and the dim filament, the other light goes out.

 

With park or headlight OFF and brake pushed: The bulb with new socket lights the bright filament, the other one lights the dim filament.

 

 

I think you have found the bad socket then. Has this truck had any modifications to the wiring that you know of? Like maybe someone installed the U-Haul trailer light kit?

Posted

No trailer light kit. It is a van conversion so it has lots of interior lighting, rear stereo & spkrs, TV, elec couch/bed etc. This was all professionally done well before I bought it. The brake light problem is recent as there is a yearly safety inspection where it was discovered. Not found last year.

  • 2 weeks later...
Posted

As a follow up, I changed the other rear socket and the problem is gone! Thanks to Doug and oldscsc for all the help.

 

what do you guys mean when you say rear socket ?
Posted

As a follow up, I changed the other rear socket and the problem is gone! Thanks to Doug and oldscsc for all the help.

 

what do you guys mean when you say rear socket ?

 

 

The light socket that holds the bulb. Duh! :D

  • Like 1
  • 1 year later...
Posted

As a follow up, I changed the other rear socket and the problem is gone! Thanks to Doug and oldscsc for all the help.

This same issue is happening to my 1994 Chevy truck. I replaced the circuit board for both sides, and still doing the same. You said you replaced the rear socket. Can you upload a picture of how it should look?

Posted

This same issue is happening to my 1994 Chevy truck. I replaced the circuit board for both sides, and still doing the same. You said you replaced the rear socket. Can you upload a picture of how it should look?

please refer to post #23 for your answer

  • 4 months later...
Posted

Identical symptoms on my 2000 Chevy Express 2500 van, although only on one side. Upon inspection, the back up lamp and socket were very corroded, and although the lamp was still functional, I decided to replace the tail light harness and lamp for less than $30 at the local auto parts store. This solved the brake light problem as well. I thoroughly appreciate the generous expert contributions on this thread which helped me save a trip to the mechanic.

  • 5 years later...
Posted

YESSSSSSS!!!!!!    :D :D :D :D :D :D  I know this thread is several years old but........

 

Same exact problems on 1998 GMC Savana 1500. Brake lights work with headlights off; brake lights turn off with headlights on.

 

I bought one socket for the right side and changed it out today. IT WORKED! Just ordered the socket for the left side and I'll install it tomorrow. 

 

Thank you guys!

  • 1 year later...
Posted

Not to take over this discussion, but i am having the same issue, however, when i disconnect the front parking lamp fuse, i have brake lights and tail lights. Im not horribly experienced with wiring but i am learning. Could you refer me where to look?

 

Thanks in advance!

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...