Jump to content

Well Toyota finally did it!!

doverarjim

By doverarjim
in The Off-Topic Bar

Recommended Posts

doverarjim Senior Enthusiast

doverarjim

Posted
Posted

Just saw an ad on tv where Toyota bragged and showed pictures of their truck pulling the space shuttle!! Makes me think back to a time long long ago where a guy pulled a train with his teeth!! :jester:

  • Replies 60
  • Created
  • Last Reply
Chris Senior Enthusiast

Chris

Posted
Posted

I paused the TV when I saw that commercial and read the small disclaimer.

 

Do not attempt. The Tundra is towing more than it is rated. This was done for a short distance and serious damage can occur

 

Something like that

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

Chris Senior Enthusiast

Chris

Posted
Posted

Almost 300,000 pounds or 136,363.6 kg's

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

Chris Senior Enthusiast

Chris

Posted
Posted

A guy I play poker with has a Tundra CrewMax with the 5.7 and he doesn't like the commercial. He thinks its stupid and almost encourages people to overload their truck.

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

00Silverado4x4 Senior Enthusiast

00Silverado4x4

Posted
Posted

As I tell my wife, the commercial people play on the ignorance (normally use alternate term but I'll be nice) of the common man. Sure they will make some sales happen but the first time someone wants warranty repairs for doing something stupid with their truck....they'll be out on their butts.

Chris Senior Enthusiast

Chris

Posted
Posted

I've had my truck overloaded going up and down steep 8% grades on a winding road with an 11,000 pound toy hauler because the dodge 2500 grenaded the transfer case 2 weeks before the trip. I had no trans cooler and it was 105 outside. I knew my weight rating for the truck but I knew all the risks and no one to blame but myself

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

00Silverado4x4 Senior Enthusiast

00Silverado4x4

Posted
Posted

That's the difference you knew going into the haul you were overloaded. Met soooo many people that bought a truck "thinking" they could do all this great stuff because the salesman "said I could" and then wonders why their vehicle comes up broke. I've also overloaded my truck, including on the trip that go me to Georgia from Alaska. However if something were to break I knew who to blame. Idiotic commercials, advertisements, programming, needs to stop. Just my opinion. I'd love to haul the shuttle but I'm not going use my 1/2 ton just to "prove a point" or whatever Toyota was thinking.

Chris Senior Enthusiast

Chris

Posted
Posted

And my drive was a 4 hour tow. I don't have a electronic brake controller either which made the tow that much harder. I towed one way. I had to leave the campsite to go to class so when I got back to town I dropped my uncle off to get his Dodge from the shop and he drove back to camp for the night and brought his trailer home the next day with it.

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

StinkyCheese Senior Enthusiast

StinkyCheese

Posted
Posted

Didn't they have an advertisement where they gave an older gentleman a truck and he flat out said he overloaded it numerous times and it kept going? Why would you brag about overloading numerous times?

Chris Senior Enthusiast

Chris

Posted
Posted
Didn't they have an advertisement where they gave an older gentleman a truck and he flat out said he overloaded it numerous times and it kept going? Why would you brag about overloading numerous times?

 

If that was towards me, I overloaded by a lot once because I was in a pinch.

 

To the OP: What is it Toyota finally did?

 

My guess is over the top advertising/bragging

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

chev1guy Enthusiast

chev1guy

Posted
Posted

I agree that Toyota should not advertise the usage of their vehicles in an irresponsible manner because consumers will more than likely imitate it. Then that person will wonder why their truck is either limping home or just can’t make it. However, Toyota is not the auto manufacturer who does this.

Chris Senior Enthusiast

Chris

Posted
Posted

Oh I know they aren't the only one. But I have a good sized flat screen in my living room and I had to pause it and concentrate to read the disclaimer. Its that small. And they are the ones at the moment showing off and going to make people think

 

"A stock Tundra towed the space shuttle so since I have a CAI, cat-back, and a tune, I could pull this 30 ft 5th wheel up a mountain road to a campsite"

 

Sent from my DROID RAZR using Xparent Red Tapatalk 2

Archived

This topic is now archived and is closed to further replies.

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