Jump to content

Recommended Posts

Posted

I want to add 2 small LED lights to my backrack on my 2015 Silverado LT. Got the lights, harness with relay and switch. I’ve installed them on late 90’s Chevys that had a AUX power supply at fuse box under hood. Do these style trucks have an AUX power hookup? Or do I need to run my power wire straight to the battery? Thanks for the help! 

Posted
9 hours ago, greenoliver1 said:

I want to add 2 small LED lights to my backrack on my 2015 Silverado LT. Got the lights, harness with relay and switch. I’ve installed them on late 90’s Chevys that had a AUX power supply at fuse box under hood. Do these style trucks have an AUX power hookup? Or do I need to run my power wire straight to the battery? Thanks for the help! 

It is easy to tap into the power at the 7 pin trailer connector at the rear bumper.  I used the that power for my led bed lights.  The only issue with this power source that it is constant on.

Posted
16 hours ago, UnlimitedMatt said:

It is easy to tap into the power at the 7 pin trailer connector at the rear bumper.  I used the that power for my led bed lights.  The only issue with this power source that it is constant on.

Sounds like you found the 12V wire, as opposed to the reverse wire. 

  • Like 1
Posted (edited)

Correct, Chris.

Edited by MikeBMW
  • Like 1
  • 4 weeks later...
Posted

I'm looking at hooking up Aux also, I want to control them from the Bed Lights, isn't there Block somewhere under the bed where I can tap in ?. I want to use the lights when needed, don't want them coming on when I lock the truck at night at the campground and disturbing fellow campers.

Posted (edited)
On 12/2/2021 at 11:48 AM, Beer Belly said:

I'm looking at hooking up Aux also, I want to control them from the Bed Lights, isn't there Block somewhere under the bed where I can tap in ?. I want to use the lights when needed, don't want them coming on when I lock the truck at night at the campground and disturbing fellow campers.

There could be a way to tie them into the actual bed light switch in the center console, @pgamboa might be able to help. Works best to shoot him an email at harnessdr.com. 

 

I wired in aux reverse lights but did not want them to always be on when the truck is in reverse, so I improvised and put a switch from otrattw in, and tapped into a constant 12v signal in the drivers side fuse panel via an add-a-fuse. Super simple install, below is the write up I made. Not sure if this is what you are going for just throwing out some options!

 

Edited by boettcher40
  • Like 1
Posted (edited)

 

I installed the Rigid flush mounts also.....but I ran #14AWG wire directly back to the battery, through a relay.    I didn't want to tap any existing 'reverse light' wiring at the rear bumper.  Didn't trust it to be big enough.

Edited by Dresari702
  • 1 month later...
Posted
On 11/6/2021 at 12:40 AM, MikeBMW said:

Correct, Chris.

I was working on a couple of our trailers here at work over the last few months.  One of our trailers was ALL F'D UP at the plug, only the RT turn and ground were correct.  🤬 Told them that like 2 years ago.  I had done some of my own troubleshooting, and told them which wires they had where.  "They fixed it," and still had a few on the wrong pins.  😡  Management will NOT let me fix it, "our AGE mechanics have to fix it."  This particular trailer is a "lift trailer," AKA "low boy," and the battery wire is on the tail lights pin and the tail lights wire is on the 12V pin.........STILL!!!  Day Shift turned in the trailer for maintenance, "dead battery," today.  Last time, all AGE did was replace the battery. 

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