Jump to content

Recommended Posts

Posted

 

Potting? do you mean putting the whole thing in a water tight enclosure?

Yeah you basically fill the whole ballast with epoxy.
Posted

Has anyone seen the '15 Yukon ballasts? I was at the dealer today checking on other items and seeing a Yukon with HIDs peaked my interest. I'm curious about the wiring harness and ballasts. Perhaps it is something that could easier be converted to the Sierra? I'm guessing not, but it just made me wonder.

  • Like 1
Posted

Has anyone purchased HID's from Diode Dynamics? I spoke to a salesmen there and he assured me their HID kit was better than the TRS', shocker! Thoughts?

Posted

Has anyone seen the '15 Yukon ballasts? I was at the dealer today checking on other items and seeing a Yukon with HIDs peaked my interest. I'm curious about the wiring harness and ballasts. Perhaps it is something that could easier be converted to the Sierra? I'm guessing not, but it just made me wonder.

I did a quick search, not sure if I looked at everything you would need for the conversion or not. Ballasts were listed MSRP at $228.17 from GM or 177.97 online, HID bulbs are MSRP $240.00 from GM or $156 online. These were prices for a 2015 Yukon. It looked like those prices were per part, not for a pair of bulbs or ballasts. I didn't have time (or knowledge of what else would be needed) to look into any other parts (wiring harness etc.).

 

 

-Skeet

Posted

I did a quick search, not sure if I looked at everything you would need for the conversion or not. Ballasts were listed MSRP at $228.17 from GM or 177.97 online, HID bulbs are MSRP $240.00 from GM or $156 online. These were prices for a 2015 Yukon. It looked like those prices were per part, not for a pair of bulbs or ballasts. I didn't have time (or knowledge of what else would be needed) to look into any other parts (wiring harness etc.).

 

 

-Skeet

Do you have a part number you used to find the ballasts? I'm curious as to which one they are using.

Posted (edited)

Do you have a part number you used to find the ballasts? I'm curious as to which one they are using.

484632098a73a96cd8a7d77c67bffd00.jpg

I don't see anything that looks like part numbers I usually see, there is a code from each make and one for the ballast that look like RPO codes to me.

 

I just took that pic from my computer at work, it came from gmwholesaleparts.com. I picked a 2015 Yukon as my vehicle, they may not even be what I think they are lol.

 

Another site with a traditional part catalog layout may have more info, I just didn't see 2015 as an option to search for on most other sites yet when selecting your vehicle.

 

Edit* Since that pic is subpar, the codes it shows for the ballast when you click on it are: CK1(06) high intensity discharge headlamps(T4F), Chevrolet(X88), GMC(Z88).

 

It shows this ^^ same thing when you click on the bulbs too, don't think it will be much help.

 

-Skeet

Edited by SkeeterMcSkeet
Posted

It shows this ^^ same thing when you click on the bulbs too, don't think it will be much help.

 

-Skeet

Thanks. I sort of looks like it is using a D1S bulb type. If that's the case then I'm definitely going to ignore that setup all together. Thanks!

Posted

Finally installed the Sierra Spec HID kit from TRS and it exceeds everything I expected. I put in the 35w 5000k kit and although some people on this forum had me worried that they wouldn't be bright enough, it was the exact opposite. My wife has an Acura TL with HIDs and mine are much brighter. I'm sure that you can get even brighter if you change out the projectors and go for a custom 55w kit but the quality, simplicity and performance of this kit get the job done. For $200 and maybe an hours worth of work, I upgraded my headlights with the TRS HID kit and VLED 5000k fog lights and this trucks lights are now exactly what I would expect from a $50k truck!

 

Anyone looking for a simple upgrade that is reasonable priced, go with TRS!

 

I just got the same kit and installed it in my 2014 sierra all terrain. Sierra spec kit. But im having the same exact problem that i had with the cheaper kits that i had relays and error code eliminators on it. Well at night when i walk to the truck i unlock it and the lights turn. When u get in they cycle (turn off then back on) but thr passenger side does not refire. The driver side has always worked flawlessly in all 3 kits i have tried and set ups. The problem has always been the passenger side. Any ideas?

Posted

Did u purchase anything else with the install canbus harness, or did u just strickly use the sierra spec kit? Also what did u ground to on the passenger side? Thanks

Posted

 

I just got the same kit and installed it in my 2014 sierra all terrain. Sierra spec kit. But im having the same exact problem that i had with the cheaper kits that i had relays and error code eliminators on it. Well at night when i walk to the truck i unlock it and the lights turn. When u get in they cycle (turn off then back on) but thr passenger side does not refire. The driver side has always worked flawlessly in all 3 kits i have tried and set ups. The problem has always been the passenger side. Any ideas?

 

Sounds like a problem with a relay tripping when you turn the Truck on (AC power kicking in, since only DC power is available from the battery). My first guess is that you might just need a better ground location if your using the negative post on the battery or just better ground contact, meaning that you just need to scrape more paint off so the wire connection is better. Thats just a guess though since I'm not completely sure how you hooked your system up.

 

The guys from TRS are great too. Just give them a call. I had a ground issue on my first go around because I didn't scrape off enough paint. The guy on the phone walked me through the whole process.

Posted

Did u purchase anything else with the install canbus harness, or did u just strickly use the sierra spec kit? Also what did u ground to on the passenger side? Thanks

 

Nope, all I purchased was the Sierra Kit. I did purchase some extra bulbs but haven't needed them. I used the same ground on both sides. Its the small cross beam from the side panel to the grill. Just un-screwed the bolt, scraped off the paint and screwed the bolt back in with the wire in-between.

Posted

Ya thats what i used the cross suppport that goes to the front but i didnt srcape ill have to try that thanks

Posted

Ya thats what i used the cross suppport that goes to the front but i didnt srcape ill have to try that thanks

Make sure you scrape until it gets "shiny" the paint is pretty thing and has a grey primer that can fool you. Gotta have a good ground to make sure you don't short out the ballasts.

Posted

So i called TRS today and the guy said that my case was only the 2nd time he has heard of the problem. I tried some recommendations i scrapped the paint and tried it. I used what they use for a ground the radiator bolt. I made a jumper wire for the heck of it and tried the ground on the firewall. I swapped the ballasts around like he siggested. All that and it wont fire up the morimoto hid bulb at all, ans barely fires up the cheaper hid bulb. Thinking about tring to swap the harness around and get my power from the driverside and use that side as the source of the signal for the relays. At least if i have the same problem and its on the driver side i do t have to remover the entire air box to mess with it this sucks!

I am gonna call them back tomorrow with my finding i called them like 15 min before they closed so i didnt wanna hold him up.

Posted

Hey guys, I want to do a retrofit into my 2014 Silverado LTZ. I know I still need to pick some projectors, but is this the correct stuff I need otherwise?

 

Jq4Got5.png

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