Jump to content

Recommended Posts

Posted

New 2020 Silverado High Country 3500 - glove box sticker says 'should not be used to carry a slide in camper' - dealer cannot tell me why....  does anyone know why?

Posted

The pickup camper calculation says you will exceed FGAWR.  I assume you have a crew cab diesel and there is not much room under FGAWR when you have curb plus five passengers.  Some of the camper weight goes to front axle and this puts you over FGAWR.  GM recommends ordering VYU snow plow prep or F60 Heavy Front Suspension.  These two packages increase your front spring rate and FGAWR and you would get a camper sticker.

 

#iworkforGM 

Posted

Thanks #IworkforGM.  Another question if you can please.  We made a mistake and bought a High Country from the dealer not knowing it was NOT rated for a Slide in Camper.  Now we're working w/ dealer to add either the VYU or F60 to our 2020 3500 HD crew cab long box Duramax High Country.  This is so we can add a slide in camper.  I read you say that we still won't get a glove box sticker from GM.  But what we would need after the mod, is the new Cargo Weight Rating and Dimensions A and B.  Would the dealer be able to provide those?  Or how would we figure those out??  Thanks again.

Posted

I do not know how GM comes up with these calculations for slide in camper rating.

How do they know how much the slide in weighs.

Some slide in campers weigh as little as 1,500 lbs, others can weigh 5,000 lbs+.

With a 3500 truck you should be fine as long as the camper does not go way over the truck payload rating.     

Even if you are under the payload rating, an aftermarket rear sway bar and rear air bags make for a much better ride with the camper on the truck..

Posted (edited)
5 hours ago, SnoGirl said:

Thanks #IworkforGM.  Another question if you can please.  We made a mistake and bought a High Country from the dealer not knowing it was NOT rated for a Slide in Camper.  Now we're working w/ dealer to add either the VYU or F60 to our 2020 3500 HD crew cab long box Duramax High Country.  This is so we can add a slide in camper.  I read you say that we still won't get a glove box sticker from GM.  But what we would need after the mod, is the new Cargo Weight Rating and Dimensions A and B.  Would the dealer be able to provide those?  Or how would we figure those out??  Thanks again.

You just need to upgrade to the F60 torsion bars and realign the truck.  This will give you equal equipment to 6000 FGAWR.  If you have a single rear wheel truck, your front tire pressure can stay at 60 psi. If you have a dually, raise your front tire pressure to 80 psi with your camper.

 

Your dealer would need to call the TAC line to see if they can get the dimensions.  There is a computer program that calculates the dimensions and camper weight based on VIN.  If you have problems send me a pm.

 

#iworkforGM 

Edited by MTU Alum
Posted

Thank you SO very much MTU Alum!  I'm feeling comfortable now keeping the vehicle - the dealer is adding the torsion bars on Tuesday!  You are a great source of information - thank you for responding so quickly too!

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   6 Members, 1 Anonymous, 1,706 Guests (See full list)

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