Jump to content

Recommended Posts

Posted

If both are out then you need to go back to the single points of failure. That would be
1.) Where the relay harness connects to the OEM input plug.
2.) Capacitor link c9nnection
3.) Connection at the battery

I would lean towards the 1st as those plugs can come lose.

Sent from my SM-N920V using Tapatalk

Posted
If both are out then you need to go back to the single points of failure. That would be
1.) Where the relay harness connects to the OEM input plug.
2.) Capacitor link c9nnection
3.) Connection at the battery

I would lean towards the 1st as those plugs can come lose.

Sent from my SM-N920V using Tapatalk



I will check the OEM input. I already checked connections at the battery. Is there any way to check the capacitor? Like with a multimeter?


Sent from my iPhone using Tapatalk
Posted

Should have the Morimoto M LED projectors and brackets available in a week. Easy install. No wire harness. No dust cap modification. All wiring fits inside the headlight so no grommets needed either. Smaller than FXR so it goes in easier. Fxr is still the better performer but requires more for the install.
This will be available for the Sierra and Silverado. Although I would still recommended the FXR for the Sierra. Since the Sierra requires to open the back of the headlight it doesn't matter that the MLed is smaller. My other concern with the Sierra retrofit is that if the MLed project has an issue it means the whole thing needs to be removed. That would require the back or the lense to be removed again. The FXR projector doesn't fail, but if a bulb or ballast did it is an easy swap.
Hope that all makes sense. Lol.6c4b5c20ce02d1604fe09938c26ad577.jpg58eaaab481492d8fc10c1f061b76fd9d.jpg

Sent from my SM-N920V using Tapatalk

Posted

Lots of info on different types of HID's but the overall consensus points to Morimoto. Is there a set and a place to purchase them from that is as close as plug-in-play as possible? I am going to do a rigid D2 fog and I am hoping for 5500k bulbs for low beam. Just want to make sure I can get a clean install along with water proofed items (dust caps). Any recommendations? 

Posted

Morimoto MLED Brackets for Silverado are all done. They fit great. No dust cap modification or anything needed. I'll get our website updated this week with them on it.84906ec0bd2a1df7515f648e3757ce37.jpgdaf1610e48991e693e99df0542e10290.jpg

Sent from my SM-N920V using Tapatalk

Posted
13 hours ago, FastWS6TA said:

Morimoto MLED Brackets for Silverado are all done. They fit great. No dust cap modification or anything needed. I'll get our website updated this week with them on it.84906ec0bd2a1df7515f648e3757ce37.jpgdaf1610e48991e693e99df0542e10290.jpg

Sent from my SM-N920V using Tapatalk
 

Look's good - Keep us updated 

Posted

Does anyone know how to connect the orange and black wires in the picture attached to the oem input? I have a 2015 silverado and this is the morimoto kit bulb wires. I believe they need to plug into the wires that originally went to the halogen bulb. Am I missing something? Any help would be greatly appreciated! Thanks

0330c8a7c0e5cbcd936ecbd8409b76db.jpg

Posted

Another bulb out issue with my
Morimoto HID kit for my Sierra. Same issue I had last year, took it apart and it magically worked again. Just noticed this tonight ... on the passenger side so hopefully I don’t have to remove the damn air box. Ugh.

This is why I hate worrying about aftermarket stuff for reliability reasons.


Sent from my iPhone using Tapatalk

  • Like 1
Posted
Another bulb out issue with my
Morimoto HID kit for my Sierra. Same issue I had last year, took it apart and it magically worked again. Just noticed this tonight ... on the passenger side so hopefully I don’t have to remove the damn air box. Ugh.

This is why I hate worrying about aftermarket stuff for reliability reasons.


Sent from my iPhone using Tapatalk
Did you check the connection on the ballast? Lose or corroded connections can cause bulb out issues. Or the ballast could just be bad. I would be surprised if it was the bulb. Start with ballast and igniter before ripping your hair out trying to get to the bulb.

Sent from my SM-N920V using Tapatalk

Posted
Is there any just straight up plug and play retrofit kits that are decent? I have looked through this thread but 195 plus pages is alot to read through.
What do you have for a truck?

Sent from my SM-N920V using Tapatalk

Posted
1 hour ago, FastWS6TA said:

What do you have for a truck?

Sent from my SM-N920V using Tapatalk
 

Sorry 2015 SIlverado LT. It does have OEM LTZ headlights though

 

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