Jump to content

Recommended Posts

Posted

Thanks for the pix......I just went out and looked at mine....not really any difference in the gap between the projector and the housing. I agree with the centering....that would bother me too.

How do you like your dmax otherwise?

Posted

I've not had a chance to check it out yet since I don't have a garage and its too cold to work outside, but how difficult is it to remove the headlights? Do you have to pull the grill or are there just bolts above and below the light?

 

I plan to tackle this job some weekend in my in-laws garage but I like to know what I am getting into before I start. I have to make sure I can get it done before the weekday since it is my wife's daily driver :)

Posted

1 remove the clips that hold the pastic trims under the hood

 

2 remove 4 bolts on top of the grill

 

3 there are 4 pastic tabs where the 4 bolts are that are holding the grill to the top. For this u need to lift the piece that the 4 bolts were holding down and back(lift up and bring the tabs back over the metal)

 

4 reach your hand behind the grill and start hitting the grille from the inside out popping the clips out from behind the grille. Make sure u get the few at the bottom then lift the grille up and out

 

5 remove the 3 screws you see holding the housing to the frame

 

6 remove the 2 bottom torx screws from the front of the wheel well plastic liner .... reach behind the bumber and remove the 4th headlight housing screw

 

7 one last tab holding the headlight the the truck .... take a flat head.. locate the upper most portion of the housing that connect to the truck should be the on that's next to the top fender..... press the meter in between the past with the flat head and pull the light out

 

8 unplug the connectors and there you have it

 

What I love about this truck is that the lights come straight out unlike my 2007.5 silverado 3500 hd where the light had to be slid out and some extra stuff needed to be taken apart this truck is so oooo much easier !!!!!

Posted

Thanks for the info. I've watched a video on how to replace the grill so these instructions make perfect sense.

Sounds like it will be much easier than the 20hours i spent installing my Webasto coolant heater :)

Posted

hello im new to this site and need some info on installing fx r 3.0 on 2015 Silverado with projectors heard about drilling the bottom to holes but any other info would be helpful such as what size and length screws how many washer s and were they were placed on projectors in front are on back also do I need splitters on highs on high beam

Posted

Yes you can, my 35w kit has a capacitor built in the ballasts, no relays to the battery at all. I am sure you suffer performance loss from this though...

 

I got my 55w working, found a local shop that sells 55w ballasts too.

 

I am using one capacitor inline to the signal of the driver side so it retains the relay connection. Working fine for 2 days now.

 

Coming from both kits, I would recommend the relay and capacitor, HIDs are not going off and on as much as it keeps it on for close to half a second when signal goes off

ive run a lot of HID's over the years, luckily my vehicles never needed the harnesses as my DRLs were always wired to a different bulb.

but every other kit ive put in that needed the relay harness has had issues.

ive used DDM, Doop, VVME, some ebay ones... and i dont even know what else.

 

i just bought VVME for my sierra, with the harness and im going to give it a go, but what i really want to do is figure out how to get the ecu/bcm changed to run 12v for DRL's. in a couple months im going to talk to the dealership shop foreman. there has got to be a way to do it.

Posted

That won't happen. It's guaranteed hard coded and the scan tool at the dealership will not have access to change voltage parameters.

Posted (edited)

Dream killer ^^^^

 

Lol jk

Edited by Mike1220
  • 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...