Jump to content

2019 Chassis Swap with 2015

Jeff1978

By Jeff1978
in Engines & Drivetrain

 Share

Recommended Posts

Jeff1978 Enthusiast

Jeff1978

Posted
Posted

I'm new to this site but couldn't yet find the information I'm looking for. Hopefully someone can confirm or point me to a previous post.

 

I have a 71 Chevy C20 that's sitting on a 2019 Silverado LD 1500 4WD Z71 Chassis/Suspension/Drivetrain.  There is an issue with the frame so I need to replace it.  I found a 2015 Silverado 1500 4WD Z71 that I can use for parts.  Can anyone tell me if the chassis is the same?  Will all of the 2019 drive train bolt to the 2015?

 

 

Also, do you know if the rack and pinion and front differential from the 2015 will work with the 2019 components/ computer?

 

Thanks!

IMG_9339.jpg

newdude Senior Enthusiast

newdude

Posted
Posted (edited)
1 hour ago, Jeff1978 said:

I'm new to this site but couldn't yet find the information I'm looking for. Hopefully someone can confirm or point me to a previous post.

 

I have a 71 Chevy C20 that's sitting on a 2019 Silverado LD 1500 4WD Z71 Chassis/Suspension/Drivetrain.  There is an issue with the frame so I need to replace it.  I found a 2015 Silverado 1500 4WD Z71 that I can use for parts.  Can anyone tell me if the chassis is the same?  Will all of the 2019 drive train bolt to the 2015?

 

 

Also, do you know if the rack and pinion and front differential from the 2015 will work with the 2019 components/ computer?

 

Thanks!

IMG_9339.jpg

 

 

LD yes, if it was a new style 2019 those are an all new frame.  

 

The steering rack, there are racks that show 2014-2016, and then 2017-2019 LD.  Not sure what is different but they do show different p/ns between those two year windows.  

Edited by newdude
  • Thanks 1
Buckwild27 Enthusiast

Buckwild27

Posted
Posted
1 hour ago, Jeff1978 said:

I'm new to this site but couldn't yet find the information I'm looking for. Hopefully someone can confirm or point me to a previous post.

 

I have a 71 Chevy C20 that's sitting on a 2019 Silverado LD 1500 4WD Z71 Chassis/Suspension/Drivetrain.  There is an issue with the frame so I need to replace it.  I found a 2015 Silverado 1500 4WD Z71 that I can use for parts.  Can anyone tell me if the chassis is the same?  Will all of the 2019 drive train bolt to the 2015?

 

 

Also, do you know if the rack and pinion and front differential from the 2015 will work with the 2019 components/ computer?

 

Thanks!

IMG_9339.jpg

Do you have any build pictures of this project? I'm wanting to do the same thing with my 71 gmc. 

Jeff1978 Enthusiast

Jeff1978

Posted
  • Author
Posted

Newdude, thanks for the information, Much appreciated!  Now I understand why I've been seeing conflicting information.  Any idea if the front differential is the same?  

newdude Senior Enthusiast

newdude

Posted
Posted
13 minutes ago, Jeff1978 said:

Newdude, thanks for the information, Much appreciated!  Now I understand why I've been seeing conflicting information.  Any idea if the front differential is the same?  

 

 

Diff appears to be the same.  

 

The p/ns for the frames appear to all be the same too 2014-2019 so every hard point should match up.  

Jeff1978 Enthusiast

Jeff1978

Posted
  • Author
Posted

Perfect, Thanks for all the help!

 

Just thinking...I need to change the ECM since it was damaged due to the donor truck that everything came from was wrecked.  I wonder if i use an earlier model ECM if that would eliminate any concerns with the earlier model rack and pinion not working.  I'm sure the 2014-2016 rack will bolt up but there must be something different with the associated wiring.  Kind of just thinking out loud here...

Jeff1978 Enthusiast

Jeff1978

Posted
  • Author
Posted
23 hours ago, Homewrecker007 said:

Do you have any build pictures of this project? I'm wanting to do the same thing with my 71 gmc. 

I just got the truck from a friend so as of now I don't have any build pics ,but I'm currently backing up a bit and taking it apart. I'm redoing some of the work that was previously done cause i think the frame has damage. 

Buckwild27 Enthusiast

Buckwild27

Posted
Posted
18 minutes ago, Jeff1978 said:

I just got the truck from a friend so as of now I don't have any build pics ,but I'm currently backing up a bit and taking it apart. I'm redoing some of the work that was previously done cause i think the frame has damage. 

Ok, please take pictures. 

Jeff1978 Enthusiast

Jeff1978

Posted
  • Author
Posted (edited)
29 minutes ago, Homewrecker007 said:

Ok, please take pictures. 

I'll take some pics.  If you go on youtube go to RustoMod Garage. Those guys did a awd C10. Has some pretty good info and I believe they used a 2007 esclade drive train. 

 

Edited by Jeff1978
  • Like 1
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

If you do replace the PCM, you will need to have it programmed by a dealer or someone with a dealer level scan tool and a GM subscription to the correct files. The PCM and TCM have to be flashed together for they run the same matching operating systems, otherwise the transmission will not shift and you'll be stuck in limp mode.

  • 2 months later...
Jeff1978 Enthusiast

Jeff1978

Posted
  • Author
Posted (edited)

Ok so the front differential from my 2019 1500 LD is cracked (left).  I picked up a front differential from a 2015  1500 (right).  Can anyone tell me if the 2016 differential will work?  See attached pics.  

 

I also attached a pic of how the chassis looks now.  Just trying to get everything bolted up, brake and fuel lines ran before putting the body back on.  Thanks for the help!

 

Jeff

IMG_0407.jpg

IMG_0589.jpg

Edited by Jeff1978
Jeff1978 Enthusiast

Jeff1978

Posted
  • Author
Posted (edited)

Well, looking back it looks like the question was already answered by Newdude.  Sorry, I guess its been a minute and I've slept a lot since then. .. But can anyone confirm is the gear ratio on the 2019 is the same as the 2015 1500 z71?

 

Thanks,

Edited by Jeff1978
mikeyk101 Senior Enthusiast

mikeyk101

Posted
Posted

I could be wrong but I thought there were different gear ratios available. I don't think there was just a single "standard" gear ratio used. You would just have to know which gears are in the differential you picked up and make sure it matches the rear gearing. I am fairly certain that 3.42 and 3.73 were two of the possibilities but cantt remember the third. Maybe 3.04???

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...