Jump to content

Recommended Posts

Posted

I just went and unplugged the relay from the harness and plugged it back in. Everything works fine now. Weird? bad connection maybe?

Posted

While changing bulbs and redoing my headlight caps to a better seal I decided to increase the housings availability to breathe. I'm one of the guys who's completely stock lights had mild condensation GM said was normal. I noticed TRS sells and recommends Gore-Tex patches so I picked up some goretex and drilled the high beam caps with two large holes and covered them with the patches. No moisture gets in, but the housings breathe better now. I figured the high beam caps would be easily fixed if there is an issue. I also put another set of holes up high on the side of the housing.

 

 

 

 

post-204-0-15362800-1440798880_thumb.jpg

 

 

 

 

post-204-0-06368000-1440798882_thumb.jpg

post-204-0-15362800-1440798880_thumb.jpg

post-204-0-06368000-1440798882_thumb.jpg

post-204-0-15362800-1440798880_thumb.jpg

post-204-0-06368000-1440798882_thumb.jpg

post-204-0-15362800-1440798880_thumb.jpg

post-204-0-06368000-1440798882_thumb.jpg

Posted

I just went and unplugged the relay from the harness and plugged it back in. Everything works fine now. Weird? bad connection maybe?

 

Could be. I like these relays for critical items that need to be water resistant:

 

http://www.amazon.com/gp/product/B003TEO9GU?psc=1&redirect=true&ref_=oh_aui_search_detailpage

 

http://www.amazon.com/gp/product/B000VU9D0C?psc=1&redirect=true&ref_=oh_aui_search_detailpage

Posted

Just installed and tested out my new bulbs: Osram 66240 CBI's. They work great and are PURE white with my 35W morimoto ballasts. Pricey, but I think they were worth it. I did run into a ricer with a PNP HID kit and let's just say my FX-R's bi-xenons on high combined with Halogen high beams won. The light output in f'ing insane with all four linked together.

Posted

Im in the middle of the installing the morimoto silverado spec kit on a 2015 silverado and Im towards the end of this project and am confused as ever..

 

Does one of the OEM plugs not get used comming from the headlights? It all seems very straight forward and then i end up with this plug at the end with no where for it to go. Any help would be much appreciated. THanks.

Posted

Im in the middle of the installing the morimoto silverado spec kit on a 2015 silverado and Im towards the end of this project and am confused as ever..

 

Does one of the OEM plugs not get used comming from the headlights? It all seems very straight forward and then i end up with this plug at the end with no where for it to go. Any help would be much appreciated. THanks.

Correct, only one factory headlight plug is used to trigger the relay. The other you can tuck somewhere in the housing.

 

By the way, do you have projector and housings or reflector housings? Also, what have you done with the headlight covers? Did you somehow extend them out because when I attempted to put the cover on, there wasn't enough room with the HID bulb and plug for the cover to go back on.

Posted

I have the projectors for the low beams which are the ones I'm currently replacing. The directions say to drill a hole in the cover for the wires to pull through. Did you have to do that or are you saying that even after drilling in the covers the bulbs still poked through?

Posted (edited)

I have the projectors for the low beams which are the ones I'm currently replacing. The directions say to drill a hole in the cover for the wires to pull through. Did you have to do that or are you saying that even after drilling in the covers the bulbs still poked through?

That is correct. At least on my truck, I would have needed to extend out the covers. I scrapped the project until I can figure out what to do with the covers.

Edited by Lbsigman
Posted

Well I went on ahead with drilling out one of the covers anb you were absolutly correct. The light plug stuck trait out of the hole and you couldnt seal anything back up. I decided to drop back and punt as well. Im hopeing i can return the kit considering it was for a silverado and it doesnt fit like the instructions say. I really wanted the lights to work. I will be putting the silver stars in i guess like I probably should have anyways. Thank you for the help.

Posted

Well I went on ahead with drilling out one of the covers anb you were absolutly correct. The light plug stuck trait out of the hole and you couldnt seal anything back up. I decided to drop back and punt as well. Im hopeing i can return the kit considering it was for a silverado and it doesnt fit like the instructions say. I really wanted the lights to work. I will be putting the silver stars in i guess like I probably should have anyways. Thank you for the help.

Yup it's a total let down. I was super aggravated over it and luckily I only drilled one cover. I ended up keeping the kit but I need to figure out what to do with it. I do have 2 spare covers to play around with so maybe in the future I will try again.

Posted

I had a friend run into the same problem with his Chevy Volt projector light. He ended up buying some black abs tubing that was close to the same size as his projector cap and glueing it on as an extender after he drilled out the back. It didn't look bad after he was done with it.

Posted

Where did you find spare covers at? I patched mine with a plastic repair kit but It looks a little rigged up. I had rather have back to normal until I figure a better option out.

Posted

Where did you find spare covers at? I patched mine with a plastic repair kit but It looks a little rigged up. I had rather have back to normal until I figure a better option out.

I ordered 2 new covers from GM Parts Direct. Not cheap for what they are. After shipping, the total was like $56 for the pair. Part Number: 23215569

Posted

Having a bit of trouble with a TRS/Morimoto HID install.

Had a 2014 Sierra SLT that the following system was being used in:

9006: Morimoto Elite HID System

-2 x AMP: Morimoto 3Five DSP

-2 x 9006: 3Five 4300K $0.00

-2 x Canbus: 9006 $0.00

System was removed from the 2014 and placed in a 2015 Sierra SLT today. I can't for the life of me get the lights to work. Fuse looks good and after speaking with TRS I hit my ground contacts with sandpaper to remove some paint and ensure a good connection.

Any ideas? Did anything change from 2014 - 2015 that would prevent the system above from working?

Thanks in advance.

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