Jump to content

I can not spin my tires. Makes me mad


Recommended Posts

Posted

Ok sure there's no need to spin tires. But after buying all the stuff on my truck... Long tubes bigger cam springs shaved head cold air cat delete throttle body spacer and a diablo sport hand tuner I should be able to spin 35s....

 

But I can't even spin 245s with no tread!!!!!

 

I was stuck on grass. Sunk 4 holes in the wet grass and had some weight in the back and the truck wouldn't spin the tires in 4'hi it would only rev around 2!grand give or take!!! What the poop.'im expecting a nice play/daily driver not a truck slug bug.

 

Any help would be nice.

  • Replies 59
  • Created
  • Last Reply
Posted

Those fuel hostages are about 40 - 45lbs each plus tire weight of those cooper 35's at about 65 - 70 lbs each. At the very minimum that set up is 110lbs at each corner. Not gonna happen with that 6.0l without some serious engine work or better gearing.

 

What are you geared at right now?

Posted

My 2006 will roast them any time I want. Dry pavement, concrete, even from a slow roll. With your gearing it should be easy. I should mention that's without the brakes, that's for children lol.

Posted

Wow with all those upgrades you'd think you could. And for what it's worth that TB spacer is just a high priced paper weight

 

Sent from my LG-D800 using Tapatalk

Posted

Wow with all those upgrades you'd think you could. And for what it's worth that TB spacer is just a high priced paper weight

Sent from my LG-D800 using Tapatalk

It was free so I figured what the hell why not. And yeah it's embarrassing that I can't even spin the 245s with all the money I have into the truck! Could torque management and drive by wire really be the reason why? My brothers got a dirty and spins 35s with ease... I'm jealous...

Posted

It's a good chance. I've heard similar stories regarding torque management. Idk enough about to offer any solutions to it tho. Sorry

 

Sent from my LG-D800 using Tapatalk

Posted

Your programmer probably has most torque management removed.

Do the "canned tunes" have that ability?

 

Sent from my LG-D800 using Tapatalk

Posted

Not sure. I'm sure their site could give specifics. To me it's puzzling that he can't light em up. Maybe a tranny issue? I dunno

Posted

Very well could be... Tyler have you noticed any mechanical problems?

 

Sent from my LG-D800 using Tapatalk

Posted

Very well could be... Tyler have you noticed any mechanical problems?

Sent from my LG-D800 using Tapatalk

No. I do not have 4 low tho. Won't engage.but new trans. Just rebuilt. I mean I give trucks a good run but off the line it's junk... Even with the 245s
Posted

I don't know then bud. Maybe someone a with a little more knowledge in this will chime in and help you. Good luck

 

Sent from my LG-D800 using Tapatalk

Posted

I don't know then bud. Maybe someone a with a little more knowledge in this will chime in and help you. Good luck

Sent from my LG-D800 using Tapatalk

I don't know then bud. Maybe someone a with a little more knowledge in this will chime in and help you. Good luck

Sent from my LG-D800 using Tapatalk

I really hope so my dads f150 lights up his 275s like nothing... Upsetting

Archived

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

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