Jump to content

Recommended Posts

Posted
Thanks Nate_0022. Im assuming you have experience with this kit? If so can you tell me how long you have been running it?
Only issue with those kits (only speaking from experience in selling tons of them) is that when something doesnt work it is a total pain in the ass to diagnose. Is it one of the relays? Maybe a ground.... or perhaps a bad ingiter. But wait could it be the ballast? Hmmm, or one of a bunch of different connection points in the system perhaps? Oh crap, maybe it is a bad bulb! Lol. Obviously I am exaggerating a tad, but when you are on the seller/customer support end of it you really start trying to find a system that performs well, is easy to install or diagnose if not working and doesnt break the bank.

Sent from my SM-N950U using Tapatalk

Posted
45 minutes ago, FastWS6TA said:

Only issue with those kits (only speaking from experience in selling tons of them) is that when something doesnt work it is a total pain in the ass to diagnose. Is it one of the relays? Maybe a ground.... or perhaps a bad ingiter. But wait could it be the ballast? Hmmm, or one of a bunch of different connection points in the system perhaps? Oh crap, maybe it is a bad bulb! Lol. Obviously I am exaggerating a tad, but when you are on the seller/customer support end of it you really start trying to find a system that performs well, is easy to install or diagnose if not working and doesnt break the bank.

Sent from my SM-N950U using Tapatalk
 

I hear you on that one. When I initially installed my hid kit, nothing would fire. Re checked grounds, used my power supply to test ballast, igniters and bulbs, all were working just fine. Had to take the pins out of the connection And install the pins by themselves to The OEM connection. So I finally figured out the pins weren’t fully inserting into The OEM connection so I had to do some trimming. 

Posted (edited)

FastWS6TA, The link you supplied was pretty thin on details. Doesnt really say what parts are included. Which Morimoto HID light is it if its not the Elite and which Hylux Ballast is included in the kit?

 

 

13 hours ago, FastWS6TA said:

https://www.fastheadlights.com/product-p/buy_hid_kit.htm

This kit is much better than the Morimoto Elite kit. The Morimot kit requires a relay harness and to be honest the 35 watt igniter/ballast from Morimoto have been very unreliable. I stopped selling the Morimoto Elite system because I was going crazy with troubleshooting and processing warranty claims. The Hylux ballast is much simpler and has been far more reliable. Its asplug n play as it gets.

You can also upgrade your fog lights to the Morimoto XBLED fog lights to improve output and beam distribution. Those are listed on the site above as well. They are also plug n play.

Sent from my SM-N950U using Tapatalk
 

 

Edited by Vulcan762
Posted
FastWS6TA, The link you supplied was pretty thin on details. Doesnt really say what parts are included. Which Morimoto HID light is it if its not the Elite and which Hylux Ballast is included in the kit?
 
 
 
Morimoto HID bulbs (35 watt) and a Hylux ballast (pair).

Sent from my SM-N950U using Tapatalk

Posted

Have been running the Morimoto Elite kit in my '15 Sierra with no issues for a few years. Added the XBLed fogs also. Now can actually see at night.

 

The kit from Fastheadlights looks to be more simple for an install and if it performs as well or better than the Morimoto kit I'd give it a try.

Posted
4 hours ago, FastWS6TA said:

Morimoto HID bulbs (35 watt) and a Hylux ballast (pair).

Sent from my SM-N950U using Tapatalk
 

Was it you guys that offered a discount to forum members on your products? If so, how do I order with it?

Posted
Was it you guys that offered a discount to forum members on your products? If so, how do I order with it?
gmforum_10%

Use that code at checkout.

Sent from my SM-N950U using Tapatalk

Posted (edited)

@fastws6ta, I bought the 3.0 fxr kit from you a few years ago. In an pretty sure the ballast or the ignitors have quit. I noticed that your selling a different style projector kit. do the new hid kits use the same plug as my old ones?

 

Answer:  yes it uses it.  Thanks Phil

 

Sent from my Pixel 2 XL using Tapatalk

 

 

 

 

Edited by bwilliams22685
got answer from Phil in email
Posted (edited)

Got my mini d2s projectors and kit from fastheadlights, thanks @FastWS6TA !

 

cant for the life of me figure out how to get at the bottom headlight bolt behind the splash guard in the wheel well without removing the white plastic trim piece above my bumper. Any tips? I did a search here and tried YouTube but can’t find specifics anywhere.

 

when looking at it from the wheel well it looks like a sheet metal bracket is blocking the majority of the 10mm bolt I need to remove.

 

thanks!

Edited by mr4wdLTZ
Posted
48 minutes ago, mr4wdLTZ said:

Got my mini d2s projectors and kit from fastheadlights, thanks @FastWS6TA !

 

cant for the life of me figure out how to get at the bottom headlight bolt behind the splash guard in the wheel well without removing the white plastic trim piece above my bumper. Any tips? I did a search here and tried YouTube but can’t find specifics anywhere.

 

when looking at it from the wheel well it looks like a sheet metal bracket is blocking the majority of the 10mm bolt I need to remove.

 

thanks!

Bumper trim has to come off first.  4 bolts and it pops right out.  Take off the plastic trim above the grill under the hood with all those plastic push pins.  6 10mm bolts for the grill, 3 on top and 3 on bottom.  It pops right out. 4 bolts on each headlight to remove them from the truck.  It sounds like a lot of work, but it took me about 30 mins to swap out my headlights.

  • Thanks 1
Posted
1 hour ago, cbrsilv15 said:

Bumper trim has to come off first.  4 bolts and it pops right out.  Take off the plastic trim above the grill under the hood with all those plastic push pins.  6 10mm bolts for the grill, 3 on top and 3 on bottom.  It pops right out. 4 bolts on each headlight to remove them from the truck.  It sounds like a lot of work, but it took me about 30 mins to swap out my headlights.

Ok that makes sense. Couldn’t see any way around removing that to get to the bolt.

 

thanks!

 

Posted (edited)

Projectors in and all put back together.

 

you weren’t kidding about that blue coating, holy cow!

 

install process was very easy compared to my old FXRs on my tundras. About 2.5 hrs start to finish.

 

waiting to get night shots tonight

8EFCDA4C-8457-4836-AD91-C0E81F1D913E.jpeg

Edited by mr4wdLTZ
  • Like 1
Posted (edited)

Here are some night shots.

 

mini D2S 5.0 kit with 35 watt hylux ballasts. 5500K D2S bulbs.

 

The D2S exceeded my expectations once I was able to line them up and take a drive tonight. The 5.0 is on or with my FXRs in my old trucks. With a fraction of the modification necessary to make it work.

 

the splitter that allows the bi-xenon high beam function in conjunction with the factory halogen high beams really enhances the brights. I did add some syllabi’s silverstar ultra 9005s while I had it all apart. Better than stock but not the same color temperature. That’s ok. The output is outstanding. 

 

i highly recommend @FastWS6TA kits.

07557AB3-5538-42F8-B7DF-5E74AA2F4CD6.jpeg

2579537C-D7C5-4B5F-98AC-6A470E0D3D1D.jpeg

Edited by mr4wdLTZ
  • Like 1

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