Jump to content

Recommended Posts

Posted (edited)

The first issue is the puddle/domelight's. I first noticed the issue when the puddle lights were flickering when the unlock button was pushed or the door was opened. Also, the interior dome lights would not come on when the door was opened. I've pushed the overhead switch to the on position and sometimes they would flash on quickly and shut off, but most of the time not come on at all. The dome lights come on when the individual buttons are pushed, but not at all with the overhead switch. Anyone know where the fuse is that controls the overhead switch?

 

 

My second issue is with the left turn signal. On the DIC I got a turn indicator failure for the left rear. The indications are with the blinker activation, the mirror/dash blinker lights will flash normal for about three seconds and then pulse quickly, followed by DIC message. *edit* Brake lights (left) also done activate.

My first action was replacing the bulbs, however that did not fix the problem. When I returned home, I troubleshot the bulbs by placing the lighting switch from auto to running lights and the lights came on, so I know the bulbs harness and wiring are working perfectly fine. I have checked the fuses in the engine compartment, number 14 I believe which is labeled trailer stop/left turn I believe. Any ideas on this issue?

 

I would like to troubleshoot the issues prior to taking it to the dealer under warranty 30 mins away.

Edited by Adam P.B.
Posted

Instrument panel fuse block (right) fuse 45 "body control module 6" removes power from dome light when I had them singularly turned on with their independent switch. Zero fuses are blown, maybe that issue is isolated to the switch.

Posted

I took the truck in today and got it diagnosed. The diode mod, performed exactly like the steps in this forum, somehow shorted out my BCM. I can't believe that would have done it, considering several other things that BCM controls work without issue. Well, new BCM and programming repair will cost one $675 dollars, all because I forgot to take out the damn diode before going to the dealership. Hard life lessons.

 

sidenote: I also performed the footwell lights modification and I'm certain this somehow factored into the equation.

 

I just removed the bcm and there are no chared areas or visible broken solders. If the bcm shorted out, wouldn't I be able to see something on the circuit board? Can any trained eyes spot any areas of interest where I can snap a closer photo to post.

 

With everyone who has had zero issues with the diode mod, I find it hard to believe this is the case. I think they saw the mod and blamed it all on that right away.

 

You think my fog light mod truely causes my issue?

Other side

post-142734-0-29597400-1465870140_thumb.jpeg

post-142734-0-40490000-1465870403_thumb.jpeg

post-142734-0-29597400-1465870140_thumb.jpeg

post-142734-0-40490000-1465870403_thumb.jpeg

post-142734-0-29597400-1465870140_thumb.jpeg

post-142734-0-40490000-1465870403_thumb.jpeg

post-142734-0-29597400-1465870140_thumb.jpeg

post-142734-0-40490000-1465870403_thumb.jpeg

  • 2 years later...
  • 1 year later...
Posted
On 1/20/2019 at 5:51 PM, Lazorith James Vaughn said:

My dome lights aren't working without manual operation of the buttons.. neither is the door chime when door is open/seatbelt/yadda yadda.. and.. neither if my.,.. Dun Dun Dunnn.. Left Rear Tail light!

What did you do to repair, please?

Did you ever find the resolution to your issue?  I'm having the same no left turn/brake and no dome lights/chime when door open as well, just had the BCM replaced at the dealership, the issue is still there...

  • 7 months later...

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...