Jump to content

Recommended Posts

Posted (edited)

I stumbled on this website. It has the RPO codes and descriptions. Also has lots of other useful info for those wanting to order their trucks.

 

http://www.gmfleetorderguide.com/NASApp/domestic/proddesc.jsp?year=2014&regionID=1&divisionID=2&type=0&vehicleID=14683&section=modelhome&page=&butID=1

 

Here is the reference sites for Chevy and GMC just select which one you need. Once you click Chevy or GMC in the box at the top right lets you pick the models you need.

 

http://www.gmfleetorderguide.com/NASApp/domestic/brandsel.jsp?year=2014&regionID=1

Edited by Blue Sierra Owner
  • Like 4
  • 3 months later...
  • 2 months later...
  • 3 weeks later...
  • 2 months later...
Posted

Interesting, the RPO codes for the L86 6.2 engine clearly read that, among other things, the engine is "E85 Max".

 

This coding is the same as what is referenced for the L83 5.3 and the 6 cyl engine. Those codes also state that, among other things, the engines are "E85 Max".

 

The inclusion of the "E85 Max" information for the 6.2 is at variance to everything else which is published about the 6.2. Anyone have insight as to why?

  • 4 months later...
  • 1 month later...
Posted

I'm new here and I'm not sure where to ask for help.

I have a 2004 GMC 1500 Sierra 2wd.

Extended cab, 5.3l v8, automatic.

The drivers bucket sags really bad. I feel like I'm going to have to look under the steering wheel to drive it.

My truck has not quite 56,000 miles on it.

It still has the original serpentine belt, spark plugs, disc pads, etc.

It has never had anything heavier than ice chest in the bed.

I need to get something to lift the rear of the bucket UP.

I had found a kit that installs between the floor and the bucket seat frame but I cant find it again.

Anyone have an inexpensive fix as I'm 63 and on disability.

Thank you for your time.

  • 6 months later...
Posted

Not all the codes in my glove box are on that list?

I sent a PM to GM Customer Service with my email and VIN and they sent me a build sheet for my truck. It included the RPO codes that matter. There is also a web site where you can look up individual codes...

http://www.rpocodes.com

  • Like 1
Posted

I sent a PM to GM Customer Service with my email and VIN and they sent me a build sheet for my truck. It included the RPO codes that matter. There is also a web site where you can look up individual codes...

http://www.rpocodes.com

Thanks!

  • 4 weeks later...
Posted

Visited the website that you posted, and still cannot locate a bunch of the codes for my truck. Is there a difference depending one when the truck was built in the model year? Just curious, not terribly worried, but just wondering why they would not have all the codes published.

  • 2 months later...
Posted

I sent a PM to GM Customer Service with my email and VIN and they sent me a build sheet for my truck. It included the RPO codes that matter. There is also a web site where you can look up individual codes...

http://www.rpocodes.com

 

Where did you send a PM to GM to get a build sheet? I just picked up a new 2015 Sierra SLT All Terrain 4X4 and it would be neat to have a build sheet. Is it a complete list?

 

Thanks,

Posted (edited)

Where did you send a PM to GM to get a build sheet? I just picked up a new 2015 Sierra SLT All Terrain 4X4 and it would be neat to have a build sheet. Is it a complete list?

 

Thanks,

Literally, send a PM to GM Customer Service...click on the link below and then "Send me a message". Yes, it is everything from my build sheet. Send them your name, email address and VIN...

http://www.gm-trucks.com/forums/user/92340-gm-customer-service/

Edited by chuckl1218
  • Like 1
  • 6 months later...
Posted

Not sure if I am in the right place but I was curious if anyone knew a sight where I could type in a vin code to find out what dealership a truck is at? I have a membership to Carfax, tried that... it just came back "NEW CAR, CLEAN"... But what I am really wanting to know is what dealership has the vehicle.

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...