Jump to content

2014-2018 K2XX Silverado Add Factory Front & Rear Park Assist

Brandonw62
 Share

Recommended Posts

pgamboa Senior Enthusiast

pgamboa

Posted
Posted
Yes, you are correct. There was no BCM programming required. Cluster and park assist module require programming. The Cluster requires the feature to be added and the park assist module needs to be associated with the vehicles vin.

Awesome! Great work and awesome details you’ve provided!


Sent from my iPhone using Tapatalk
Brandonw62 Enthusiast

Brandonw62

Posted
  • Author
Posted
1 hour ago, pgamboa said:


Awesome! Great work and awesome details you’ve provided!


Sent from my iPhone using Tapatalk

Phil, you had some fantastic content that helped jumpstart the idea, so thank you very much for the inspiration. These are fun projects that help people get the features they want out of their trucks. 

  • Like 1
  • 1 year later...
Viktorrocks15 Enthusiast

Viktorrocks15

Posted
Posted
Looks like I'll be helping two local members with this upgrade.  Fun times! [emoji4] [mention=170974]DBrach[/mention] and [mention=154140]Viktorrocks15[/mention]

I’m really excited about this retrofit. [emoji1303][emoji1320]


Sent from my iPhone using Tapatalk
DBrach Enthusiast

DBrach

Posted
Posted
24 minutes ago, pgamboa said:

Looks like I'll be helping two local members with this upgrade.  Fun times! :) @DBrach and @Viktorrocks15

Can't wait my man! Thank you...its long overdue on my truck since I installed the new bumpers with sensors a year ago lol. :)

  • 3 years later...
DBrach Enthusiast

DBrach

Posted
Posted
On 10/25/2020 at 9:05 AM, pgamboa said:

Looks like I'll be helping two local members with this upgrade.  Fun times! :) @DBrach and @Viktorrocks15

Geez, can't believe it's been 4 years @pgamboa! You ready to do this?! 

  • 11 months later...
Nodakrider New Member

Nodakrider

Posted
Posted

I’m in the process of researching this very same project for my 2022 GMC 2500HD. It was not ordered with park assist.  I’m starting to acquire the parts; have replaced the bumper and rear harness with a sensor-equipped wiring. It appears the frame harness has all the wiring going to the front end; have not looked at the front end termination yet (or even found it).

 

One of my biggest challenges is going is retrofitting the center stack dash switches to accommodate a park assist button. The nine switches are arranged in sets of three switch modules: left, center, and right. Park assist is always on the left third of the three modules. 

 

My truck now has a descent control button and two blanks in the left switch. I’ve acquired two other switch modules (one with park assist and the auto start/stop buttons; one with just the descent crtl ) and am hoping to make one switch from two that will contain the descent crtl and park assist buttons; the third will be blank. I will have to add pins to the switch module. 

 

I’ve not yet looked at the 371L plug behind the left module, but have the pin configuration. I’m hoping it is wired for all the possible buttons in the left switch, so I’ll just have to add pins to the module accordingly.  Again, this is going to be a challenge; I just picked up the switch modules yesterday and have not yet attempted to disassemble them. 

 

I’ve watched the referenced videos in this chat; great reference, as is this chat. Any help/suggestions are greatly appreciated. Thanks!

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...