Jump to content

Recommended Posts

Posted

I'm looking to see the rear of the GMC lights. I don't know if they are just like the Silverado bellow or not. I also don't know if people have to cut them when they put the 2.5" retro projectors in like we do on the Silverado.

 

2013-12-22130908_zps5763f731.jpg

Posted

Alright HID gurus I need some advice. I am going to order my HID kit and have been on the fence about retrofitting to FX-R. I thought of something today that worries me. If I retrofit my Silverado with FX-R that will leave me with D2S bulbs/sockets. I use my truck a lot to tow my travel trailer. We do several long trips per year (next summer its WI to Yellowstone) and I got to thinking what if my HID goes out while on the road. If I retrofit to FX-R I could not just throw my stock H11 bulbs in. If I use the Silverado specific HID kit with H11 and OEM projectors I could carry my stock bulbs just in case. Last thing I want is to be in SD or MT next summer with no headlights. Anyone have an idea for me. I admit I'm not that familar with all the HID adapters etc.

Posted

A good quality HID kit is more reliable than a halogen.

I get the reliability and would order a trs kit. Any work around my concern.
Posted

I get the reliability and would order a trs kit. Any work around my concern.

A quality HID is much more reliable. But if you are concerned about that "what if" still, then I would just order a spare lightbulb or 2. If something happens you just change out to a new one! Problem solved

  • Like 1
Posted (edited)

The thing about a HID kit is; the reliability is as much about the installation as the parts themselves.

 

For example: I put the TRS kit on quickly, with the idea it was temporary. I tiewrapped the double relays to another harness and they hung with the connector side up. Well, I started having relay problems and traced it to water intrusion in the relay. The one relay connector seal allowed water into the relay an toasted it, twice. I shouldn't have hung it upside down and the seal shouldn't leak and I should put some dielectric grease on the seal, etc..

Edited by spurshot
Posted (edited)

Just re ordered another HID kit. This time the morimoto kit from TRS.. hopefully I don't have near as many problems as I did with my DDM kit..

 

Edit: Nevermind, A couple pieces in the Sierra kit are backordered..

Edited by Btreyu09
Posted

I just got my morimoto sierra spec xb35 kit from TRS installed today. The lights work great at night. When the DRLs are on the lights work good no flickering just a terrible buzzing noise. I believe the capacitor was installed in the correct spot. This is my first HID kit and I can't figure it out for the life of me. Thank you

Posted

The buzzing with the DRLs on. I thought the capacitor was supposed to take care of that or maybe I just got my information wrong.

Posted

I tried that already too. I'll have to dig around tomorrow some more when then wind isn't blowing 500 miles an hour.

Posted

Well I figured out what happened. When they installed it the capacitor that was in there somehow turned into an extension without a capacitor. It makes sense now.

Posted

Ddm top, morimoto from theretrofitsource.com bottom. This may help some people trying to decide what to get.post-133073-0-19071700-1419470460_thumb.jpg

post-133073-0-19071700-1419470460_thumb.jpg

post-133073-0-19071700-1419470460_thumb.jpg

post-133073-0-19071700-1419470460_thumb.jpg

Posted

Ddm top, morimoto from theretrofitsource.com bottom. This may help some people trying to decide what to get.attachicon.gifimage.jpg

Same wattages and color temps?

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...