Jump to content

2018 SIERRA 1800 SLT PLUS Z71 4x4 Wiring Help

JCeballos8

By JCeballos8
in Modifications & Accessories

Recommended Posts

JCeballos8 Enthusiast

JCeballos8

Posted
Posted

Hi guys,  hopefully someone out there in GM world can help me.  I'm installing an aftermarket running board lights which has courtesy lights and turn signal lights.  I looked every where to get some concrete answer where i can tap into the OEM parking lights wire, courtesy light wire, and turn signal wire.  Now, I realize i can run them into the hood and into each headlamp but I much rather keep the connections neat inside the cab.  I looked at the GMUPFitter manual and quite honestly it might as well be in chinese to me.  If any one has any info with pictures broken down Barney style I would appreciate it.  Also if you recommend not tapping into any wire coming from the BCM then where would be the best place to tap into?  Thanks in advance to everyone who is willing to help!   @pgamboa any suggestions?

1SLOW1500 Senior Enthusiast

1SLOW1500

Posted
Posted

Wires are at bcm and also in front door kick panels. If you are handy with a meter you can just meter in the door harness and find color in kick panel trim. Use floor grommets and you are all set.

Sent from my SM-N960U using Tapatalk

amxguy1970 Senior Enthusiast

amxguy1970

Posted
Posted

Is the wiring different on 4wd than 2wd for the parking lights and courtesy lights? Do they make a 2wd Z71 in 2018? Just curious because of the title, that seems like a bunch of Autozone information...

 

Tyler

JCeballos8 Enthusiast

JCeballos8

Posted
  • Author
Posted
19 minutes ago, amxguy1970 said:

Is the wiring different on 4wd than 2wd for the parking lights and courtesy lights? Do they make a 2wd Z71 in 2018? Just curious because of the title, that seems like a bunch of Autozone information...

 

Tyler

not sure, but mine is a 4x4

JCeballos8 Enthusiast

JCeballos8

Posted
  • Author
Posted

So just to update, pgamboa is the man.  He helped me out a lot.  No need to touch the BCM.  Pretty much remove the connection from the front door jambs by first removing the rubber boot from the outside.  

IMG_1237.jpg

JCeballos8 Enthusiast

JCeballos8

Posted
  • Author
Posted
On 9/25/2019 at 4:44 PM, paracutin said:

Get a hold of Phil (pgamboa).  If anyone knows, it will be Phil.  

Thanks a lot for this info, Phil helped me out a lot, he is the man!

  • 3 months later...

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • Grumpy Bear
      OCI, not when but why?

      By Grumpy Bear · Posted

      I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...