Jump to content

Installation of grill lights

TXguy

By TXguy
in Modifications, Wheels & Tires

 Share

Recommended Posts

  • Replies 82
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

TXguy
TXguy

Completed installation. 

TXguy
TXguy

Here is a couple of photos. I bolted between the horizontal supports in the grill. The 1/4” bolts fit perfect with fender washers. 

Smoothbassman
Smoothbassman

You can use a fuse tap right on the parking light circuit in the fuse box in the front of the truck.       Fuse 34 is what you want to tap into.        Y

Posted Images

SilentSierra Enthusiast

SilentSierra

Posted
Posted
4 minutes ago, Eric Minsker said:

Awesome! How did you wire them up?

It was very easy.  I bought a micro fuse tap and connected the positive wire from the lighting harness to the right parking light fuse...the ground wire I simply pulled out a bolt (between the radiator and fuse box) and secured the ground wire with the reinserted screw.  The three lights are attached to the grill with 3m tape and are very secure.  I love the look they give to this  big grill! The lights are easily installed in 5 minutes and used the enclosed zip ties to help hide the wires...I soldered the positive wire to the micro wire tap and soldered the negative wire to the wire loop (not sure what you call the flat round washer with a wire crimp for mounting wires). 

38EB265A-138E-490D-9724-E736BD06FDC0.png

ken babick Enthusiast

ken babick

Posted
Posted

curious-I notice on Amazon there arent very many good reviews for the lights you used-as I am looking to do the same on my silverado-did you have any trouble with the wires being thin fragile etc on the lights??

 

SilentSierra Enthusiast

SilentSierra

Posted
Posted
5 hours ago, ken babick said:

curious-I notice on Amazon there arent very many good reviews for the lights you used-as I am looking to do the same on my silverado-did you have any trouble with the wires being thin fragile etc on the lights??

 

The little round lights I originally used had thinner wires than the F150LED lights.  Both lights had pretty small wires...that’s why I chose to solder them.   The small round lights had bad reviews of not working after being wet.  I’m pretty pleased with the F150LED lights as they seem to be a much better quality than the small round lights!   

  • Like 1
SilentSierra Enthusiast

SilentSierra

Posted
Posted (edited)

The F150LED lights are soldering 2 wires vs 8 on the small lights...and they are orange, not yellow 

Edited by SilentSierra
SilentSierra Enthusiast

SilentSierra

Posted
Posted (edited)
15 minutes ago, rikhek said:

A different approach:  

 

I thought about doing that also but I went with the bar route and then removed it within a week (and I spent a lot of time on it for a custom wrapped fit).  Here is the difference between my bar attempt and the F150LED lights

B8C61E6A-E37A-4B66-8F52-72D0F0BE2BC2.jpeg

Edited by SilentSierra
  • Thanks 1
rikhek Enthusiast

rikhek

Posted
Posted

Yeah,  I read and saw the various pictures that in you shared in detail in your various posts in this thread.  Are you sharing new/different info than what you've already detailed in this thread?  I'm confused on your repost and am curious if I'm just missing "new" information you're sharing?

SilentSierra Enthusiast

SilentSierra

Posted
Posted

Didn’t mean to confuse you or hurt your feelings.  I did two different methods and trying to save someone else some time by seeing a few options. Wish I had seen these lights prior to going through all the work with the bar.   When your lights break (I know the quality since that’s what I used first) give this method a shot.  There is no comparison in the quality of the light and wiring harness.  

rikhek Enthusiast

rikhek

Posted
Posted

Confused yes.  Hurt feelings?  I'm puzzled why you'd think my feelings were hurt.  It just seemed strange you'd repost exactly what you already posted in great detail in the thread.  Whatever....

 

I will say I like the Ford lights you used better than what I have and you used on your first go around.  If mine fail I have 6 spare ones to use and they only cost $13 for a box of ten lights.  The quality seems to be fine for the application but only time will tell.  If I have issues with mine I'll go the Ford route as you've done.  

rikhek Enthusiast

rikhek

Posted
Posted

Ooops, no I won't be going the Ford route as you have.  I just clicked on the link and saw the Ford lights you used cost $80 for three lights.  I'm too cheap to spend that much for 3 lights.  Especially since they are cosmetic items...

SilentSierra Enthusiast

SilentSierra

Posted
Posted

Totally understand that.   I debated and looked at this post a dozen times before I decided to do it...and still have issues trying to copy a raptor look.  Lol. I spent around $50 the first go with the bar (lights, bar, paint , primer, fuse tap...) then changed my mind.  Im probably a dumbass for spending a total of $130 but oh well, I waste a lot on money too.  lol 

ken babick Enthusiast

ken babick

Posted
Posted

Thanks for all the input-I attached a photo of how I did the lights on my 2018 Silverado-I think they look great. I noticed that the grill had nice round design in the grill and with the 3/4 inch amber lights from Amazon-of course they wouldn't fit-too small. So I used a 3/4 inch piece of PVC pipe and sliced off about 3/8 inch slab then inserted that into a same slice of 3/4 elbow or connector which gave me the right diameter.  I sprayed the PVC with black paint--I used black JB weld RV sealant to secure the pieces into the grill-You cannot see the JB unless you get your face right into the grill. Wiring was the tough part as the inside of that area is totally sealed except for a tiny corner up top. I love the way it looks. Now I gotta figure out the grill on my 2020 silverado

black out.jpg

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