Jump to content

Recommended Posts

Posted (edited)

Recently loaded mine and the wifes bikes in a uhaul trailer and drove from Edmonton, AB to Halifax and back, dropping into the northern US. A total of 10,539kms and not a single issue other then my own stupidity of not getting my alignment done. I lowered my AT4 2” awhile back, got it aligned and then recently lowered it another 2” and knew i needed an alignment but last minute went on this trip. Which killed my 2 front tires. Other then that the truck did great. The uhaul trailer was causing more drag then i expected so the 10 speed was dropping to 9th or 8th gear alot when we were going 70-75mph. Used our truck bed tent and air mattress each night at truck stops. it was nice to visit the family and ride our bikes around Nova Scotia. If i can afford it, ill be doing the trip again this summer. 

40499F8C-46DB-46E6-A2C4-D6D05F4F6E5D.jpeg

79DFC87E-2440-4DAC-A5A3-82977F68ADAE.jpeg

459352DA-B416-4B9A-90B2-7A11E5CDC4D3.jpeg

D1CAFBA5-B3F6-4572-9DBC-173D6168878A.jpeg

Edited by Snakes709
  • Like 1
Posted
41 minutes ago, seamus2154 said:

^^^^^ What he said...but get it aligned first.

 

1 hour ago, JimCost2014 said:

Put the front tires on the back until you see snow, lots of tread left, except in that one area🤔😬👍


done and done. Rotated the tires the day after i got home and got an alignment done. Had to to back for a second alignment because once everything was within spec, the tires were rubbing. So i asked them to adjust the caster to 4.3L and 4.8R which is out of spec but no rubbing and wont effect tire wear. Ill pick up 2 new tires in the spring. Another month or two until my winter tires go on. 

  • Like 1
Posted

Just out of curiosity, did you have it in tow mode? I pull a 20' enclosed with my 2019 Sierra loaded with two Spyders (Can Am). I tried with and without tow mode and found that tow mode is the best way to go. Had tow mode on my 2017 Silverado and it was crap. 

Posted
1 hour ago, Phantom 4D said:

Just out of curiosity, did you have it in tow mode? I pull a 20' enclosed with my 2019 Sierra loaded with two Spyders (Can Am). I tried with and without tow mode and found that tow mode is the best way to go. Had tow mode on my 2017 Silverado and it was crap. 

I had it in tow mode on fhe way there but not on the way back. Fuel mileage was the exact same but i found with it in tow mode it would drop more gears to accelerate/hold speed and drop more gears for engine braking going down hill. Total weight was 2900lbs, so not that heavy. 
 

if i do this trip again, ill probably rent a trailer from another company. There is a local one that has a single axle, nosed shaped and fiber glass so its only 900lbs. Vs. The 1800lb square shaped tandem axle uhaul trailer. 

Posted
On 9/19/2022 at 10:23 AM, Snakes709 said:

I had it in tow mode on fhe way there but not on the way back. Fuel mileage was the exact same but i found with it in tow mode it would drop more gears to accelerate/hold speed and drop more gears for engine braking going down hill. Total weight was 2900lbs, so not that heavy. 
 

if i do this trip again, ill probably rent a trailer from another company. There is a local one that has a single axle, nosed shaped and fiber glass so its only 900lbs. Vs. The 1800lb square shaped tandem axle uhaul trailer. 

2900 isn't much weight. The only time I had multiple shifting was going up mountains. I learned to take it out of tow mode before the climb. Worked better. 

Posted
2 hours ago, Phantom 4D said:

2900 isn't much weight. The only time I had multiple shifting was going up mountains. I learned to take it out of tow mode before the climb. Worked better. 

I think it was much weight either. I think it was more the drag the trailer was creating. I was actually shocked how it mainly wanted to be in 9th gear most of the time. What i also found is if it was accelerating either to get up to speed or to hold speed up a incline, it would go to 9th or 8th, once it gets there it would just stay in that gear when using cruise control. I would have to drop 1mph, let it upshift and then increase by 1mph. 

  • 2 years later...
  • 2 weeks later...
Posted
On 2/21/2025 at 11:16 PM, cautious optimist said:

I'm curious how you knew what gear the transmission was in? My dad's Ford has it on the dash, but my truck doesn't seem to tell me anything about this. 

 

 

The truck won't tell you this.

One of the aftermarket monitors is required.

  • Thanks 1

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   5 Members, 1 Anonymous, 1,741 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...