Jump to content

Recommended Posts

Posted

I looked through this the other day. I was hoping someone did an install video on the Silverados. It doesn't seem that you have to remove the headlights like the Sierra.

 

Are the the relays run straight to the battery and then plugged into the ballast?

 

+1 on the TRS spec kit.

 

You don't have to remove the headlights on the sierra's to do the install. Check out Fondupot's Sierra install on Youtube (should be basically the same process for the silverado):

Posted

Sounds good guys. Cant wait to get this done.

I would suggest having a multi-meter close by in case you have any issues with the install. Makes narrowing things down much easier and will save you a lot of time...

 

Sent from my SM-N910V using Tapatalk

Posted

Confirmed.

 

Ultra HID w/ CAN-bus from DDM work without a harness. Super easyon the 2014 Silverado LTZ too!

Posted

I would suggest having a multi-meter close by in case you have any issues with the install. Makes narrowing things down much easier and will save you a lot of time...

 

Sent from my SM-N910V using Tapatalk

Absolutely. Just don't multi meter the output on the ballast;)-. Lol. Lol.

 

Sent from my SM-N920V using Tapatalk

Posted

For those of you with the stock Sierra projectors, do you seem to have dark spots in your beam pattern. I can make out the curves of light (kind of like arcs) and just wondering if this is normal with the stock projectors?

 

Sent from my SM-N910V using Tapatalk

Posted (edited)

For those of you with the stock Sierra projectors, do you seem to have dark spots in your beam pattern. I can make out the curves of light (kind of like arcs) and just wondering if this is normal with the stock projectors?

 

Sent from my SM-N910V using Tapatalk

Yup the stock projectors are meant for Halogens which do not have the electrode that runs parallel to the arc tube. What you are seeing is the shadow from the electrode. Well that's what I assume it to be anyway

Edited by abominable z71
Posted

Yup the stock projectors are meant for Halogens which do not have the electrode that runs parallel to the arc tube. What you are seeing is the shadow from the electrode. Well that's what I assume it to be anyway

Thanks man, that makes a lot of sense. I'd love to do a full retrofit with the rx350's but just can't bring myself to open up the headlights on a brand new 50k truck...

 

I am thinking about switching to 4500k bulbs though. I got the 35w 5500k and just not 100% happy with the color.

 

Sent from my SM-N910V using Tapatalk

Posted

Thanks man, that makes a lot of sense. I'd love to do a full retrofit with the rx350's but just can't bring myself to open up the headlights on a brand new 50k truck...

 

I am thinking about switching to 4500k bulbs though. I got the 35w 5500k and just not 100% happy with the color.

 

Sent from my SM-N910V using Tapatalk

I'm running the 4500k morimotos in the stock projectors with Denso ballasts, I'm very happy with the light output from the 4500k. It offers the most usable light without being too yellow and produces more foot candles than the higher K. Everyone looks at lumen output but foot candles is what determines how much light you have per square foot at a measured distance from the source which is really what matters when you're trying to illuminate something. This is where the temperature/color/K rating comes into play which is actually the frequency of the light wavelength the human eyes sees. We see red at 620nm or 400Thz and all colors in between up to violet at 380nm or 780 Thz, infrared and ultraviolet are the wavelengths on either side of the spectrum that we cannot see. Given the same power output from the ballast, the lower frequency waves travel further than higher frequency with identical power. This means the lower K value will have more foot candles the further you move away from the source because the lower frequency light is attenuated less as it passes through the air molecules. This is why infrared works through walls, the low frequency even though unseen by the human eye passes through a wall that visible light waves cannot pass. This is also why lights in the 8k and 10k range are blue and purple and have terrible lumen and foot candle ratings even though they're powered by the same 35 watt ballast. Obviously the better the optics in a projector and higher quality bulbs can help focus more light to where it needs to be.

 

I'm going to open up the head lights and put in the rx projectors and run them with the Osram night breakers which I think are 4200K this should get the most foot candles where they need to be. I want the most light on the road not lights the look cool, function over form if you will.

Posted

Thanks man, that makes a lot of sense. I'd love to do a full retrofit with the rx350's but just can't bring myself to open up the headlights on a brand new 50k truck...

 

I am thinking about switching to 4500k bulbs though. I got the 35w 5500k and just not 100% happy with the color.

 

Sent from my SM-N910V using Tapatalk

 

I did the same as abominable on my 2014 Sierra. Just TRS's Sierra Spec kit worked wonders. I drove my wife's 2009 Acadia this weekend and hated the headlights on it. It's dual projectors with halogens and they SUCK now compared to my truck. I thought they were way better before the upgrade. I might upgrade her Acadia, except that it's relatively old and has plenty of interior rattles to make me want to drive it off a cliff.

Posted

Can anyone with the 14/15 sierra tell me if i can safely run the 50W morimoto kit? Im about to pull the trigger on some HIDs but cant decide which kit to buy. Is the 50W that much better or should I stick with the 35W? I just really dont want to melt anything.

Thanks!

Posted

Can anyone with the 14/15 sierra tell me if i can safely run the 50W morimoto kit? Im about to pull the trigger on some HIDs but cant decide which kit to buy. Is the 50W that much better or should I stick with the 35W? I just really dont want to melt anything.

Thanks!

I've had 50/55w ballasts the life of my truck and never had any problems with heat. I prefer the 50/55 because it gives more power to the lights and drowns out most of the blue. 6500k 50w ballasts is perfect in my opinion.

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

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