Jump to content

Reverse Lights Stay on - 2014 Silverado crew cab LTZ

jwhitesides

By jwhitesides
in Troubleshooting & Recalls

 Share

Recommended Posts

jwhitesides Enthusiast

jwhitesides

Posted
Posted

My reverse lights are staying on:

  • When in park
  • When in drive
  • When the ignition is off

 

I have removed fuse #33 in the engine compartment fuse box which kills power to the revers lights to keep from killing my battery. This also keeps my reverse camera from turning on when in reverse also.

 

I have unplugged the backup camera thinking this was causing a bad ground with no success.

 

I don't see where a relay might be that could be bad/stuck.

 

This is a interment problem which points to ground or relay issue somewhere but I don't know where to look.

jwhitesides Enthusiast

jwhitesides

Posted
  • Author
Posted

It looks like the relay KR61 "Trailer Backup Lamps Relay" is also the relay for the vehicle backup lamps. I will swap or replace this relay and see if this resolved the issue.

 

Thank you for the diagram! This was helpful. I will report back after I replace and drive for a few days to verify this was the problem.

 

  • Like 1
jwhitesides Enthusiast

jwhitesides

Posted
  • Author
Posted

In my continued research I am understanding this relay is integrated on a circuit board in the fuse block assembly. To fix this issue will require replacement of the entire fuse block under the hood.

 

Can anyone else agree with this?

  • 2 months later...
JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted
1 hour ago, Lsx04gt said:

Did you ever figure this out? Having the same exact thing happen

Welcome to the site.

 

This is what you need to do if it is the same problem as the above post:

 

this relay is integrated on a circuit board in the fuse block assembly. To fix this issue will require replacement of the entire fuse block under the hood.

  • Like 2
JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted
On 8/6/2021 at 7:40 AM, jwhitesides said:

In my continued research I am understanding this relay is integrated on a circuit board in the fuse block assembly. To fix this issue will require replacement of the entire fuse block under the hood.

 

Can anyone else agree with this?

Sounds correct, there are relays that are actually part of the UH FB, and can not be serviced or replaced.

  • Like 2
Lsx04gt New Member

Lsx04gt

Posted
Posted

Wow, great design. Read another story that was related where person replaced rear camera (stock) and cleared up all related backup light issues. This happened about a month ago, pulled fuse, did some bulb changing and light pulling and replaced fuse and stopped until a few days ago. I will have to clear up for good because PA insp/emm is coming up next month, and it’s nice to have truck work the way it should as well also! Thank you guys!

JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted
10 hours ago, Lsx04gt said:

Wow, great design. Read another story that was related where person replaced rear camera (stock) and cleared up all related backup light issues. This happened about a month ago, pulled fuse, did some bulb changing and light pulling and replaced fuse and stopped until a few days ago. I will have to clear up for good because PA insp/emm is coming up next month, and it’s nice to have truck work the way it should as well also! Thank you guys!

It has been that way for a while. Had to replace the whole fuse box in my 2008 to get the 3rd brake light to work.

$500.00 at dealer, never had a problem again though.

  • Like 1
jwhitesides Enthusiast

jwhitesides

Posted
  • Author
Posted

I haven't fixed it yet but after some troubleshooting I would have to agree that it's the fuse block. I can bang the fuse block to get the integrated relay to turn the reverse lights off. Also I have unplugged the reverse camera with no change to the reverse lights; so the bad ground in camera theory is not the issue in my situation.

Lsx04gt New Member

Lsx04gt

Posted
Posted
2 minutes ago, jwhitesides said:

I haven't fixed it yet but after some troubleshooting I would have to agree that it's the fuse block. I can bang the fuse block to get the integrated relay to turn the reverse lights off. Also I have unplugged the reverse camera with no change to the reverse lights; so the bad ground in camera theory is not the issue in my situation.

Thank you. Gonna try unplugging cam 1st since it’s easy but seems I will be buying a new under hood fuse block

  • 4 months later...
jwhitesides Enthusiast

jwhitesides

Posted
  • Author
Posted

I fixed the issue by replacing the under hood fuse block. You MUST get this from the dealer. Mine was $225 + tax. Be sure to have your VIN number to get the correct one. The replacement fuse block does have some different fuse arrangements that I verified with the dealer.

 

It it very easy to change out:

 

  1. Remove positive battery cable 10mm
  2. Remove power cable from batter to fuse block 10mm
  3. The two levers on the fuse block UN-clip and you rotate them all the way to the center; then rotate them back to the outside while slightly apply pressure to lift the fuse block up. Mine cam out VERY easy once I figured this out. No need to pry or use any tools. Take a look at the replacement fuse block levers and you will understand. No need to remove the cover on the fuse block either.
  4. Dropped the new one in in reverse from above.

Everything works great!

 

Some have mentioned of ground wire issues that may cause this. I am going to take a look at my ground wires from the battery to see if anything is visually wrong.

  • Like 1
  • 2 years later...
2014 GMC Sierra New Member

2014 GMC Sierra

Posted
Posted

I am trying to help my brother who has a 2014 GMC Sierra with the backup lights staying on.  I purchased a used fuse block at a salvage yard with the hope of saving him a few dollars but the problem persists. Maybe the problem was not the fuse box but something else, or maybe I have another faulty fuse box.  My brother said that someone at the dealership said there is a junction box near the rear wheel that should be checked for ground.  I am writing to inquire any any folks out there have experience with this problem and suggestions regarding what to check next. Many thanks

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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...