Jump to content
SAU Community

Recommended Posts

Change in torque produces wheel spin... Not peak torque :)

I'm with rolls on this one - why would change in torque produce wheelspin? Think about how torque becomes force at the road surface.

I'm with rolls on this one - why would change in torque produce wheelspin? Think about how torque becomes force at the road surface.

Because its not linear. A sharp rise in torque will cause wheelspin.

I race RC, when you flip the RC car mid corner on a swept furface the reason was a loss of and then re gain of traction. Similar principal.

100% agree on the change in torque causing wheelspin.

You can have a huge peak torque figure but if the torque builds gradually you have a good chance of no wheelspin. If there is no torque then a sudden 500Nm jump over 500rpm it will be very hard to not get a lot of wheelspin.

Normally in a turbocharged car the biggest change in torque will also be as the turbo hits boost and reaches its peak torque, but that is just a coincidence.

See below example, yes it would be the strangest dyno curve ever but you get the idea.

post-29432-0-55490100-1311040548_thumb.jpg

That would be from boost controller, I found this boost creep and drop behavior happens to customers with return flow coolers. check hary's result pre and after cooler tests:

http://www.skylinesaustralia.com/forums/topic/261613-hypergear-hiflow-service-continued/page__st__1640__p__5772487#entry5772487

Been doing more research on this and it seems there are plenty of guys running return flow intercoolers making a lot more power:

http://www.skylinesaustralia.com/forums/topic/359972-most-power-with-a-return-flow-intercooler-and-std-piping/page__p__5747667__fromsearch__1#entry5747667

Change in torque produces wheel spin... Not peak torque :)

Can someone give a scientific reason why this is so? I'm not convinced.

There is a limit of grip the tyre can provide, the only force acting on the tyre is the torque turning it, I don't see why a fast increase in torque would cause this?

I can see why fastly increasing torque might be conducive to wheel spin, but it in itself won't cause it. Eg you break traction with x torque, the wheel spins increasing rpm which also increases torque hence it spins faster. If you have flat torque it will not continue to spin like this, however if the torque value is enough to cause the wheel spin in the first place it will still cotinue to spin, it just won't smash the limiter like a steep torque curve would..

If the torque curve is dropping off and x torque causes it to spin, the increase in rpm would cause the torque to drop and hence stop the tyre spinning, but if it doesn't drop below the value required to spin it in the first place, it will continue to spin.

edit: That was confusing to write lol.

Edited by Rolls

Can someone give a scientific reason why this is so? I'm not convinced either way now, going to have to think about it some more.

Without going into the physics of it, as I CBF to look up the formulas.

Torque is force, traction is force. The 1400kg car car only accelerate at a certain rate FROM a certain speed with its given variables (tyres suspension etc etc etc).

At a given point the rotating effort from the tyres (torque) will overcome the traction to the road. A sharp rise while it is already spinning will cause it to try and accelerate faster and with the additonal force it will overcome the available traction.

Think of traction as KG per square CM from tyre to road, how much force to you need to break the traction? Like the handbrake, yeah it will hold the car from rolling away, but the motor can overcome the force on the little handbrake shoes if you try hard enough cant it? Is it the increase in engine RPM that will make you break free of the handbrakes hold or is it more specifically the torque (ala FORCE) of the motor that will force the wheels to move?

Think about it dude...... Its physics.

Think about it dude...... Its physics.

I did and it isn't correct, it is the actual torque value that causes wheel spin, not whether it is increasing or not. If it increases steeply it is more likely to maintain wheel spin and not a single chirp though which is what I think you are getting at.

read my edited post.

I did and it isn't correct, it is the actual torque value that causes wheel spin, not whether it is increasing or not. If it increases steeply it is more likely to maintain wheel spin and not a single chirp though which is what I think you are getting at.

read my edited post.

If you are accelerating at X rate with your torque building at Y rate then why would you not impact the variable of traction if your Y rate increase significantly from your X rate that it previously was?

Think about it logically. You can accelerate as fast as the force you apply vs the amount of traction you have, your traction is constant, a sharp rise in torque (AKA FORCE) is NOT constant and will require more traction that your not getting any more of.

Traction, torque, force are all instaneous things, a sharp rate of torque increasing is something that happens over time.

A sharp increase in torque is more likely to sustain wheel spin, but if the torque figure during that sharp rise never exceeds what your wheels can put to the ground, it won't cause any spin.

Its probably a crude example but say a clutch drop as opposed to a good launch at the same rpm. The peak torque is the same, the only difference is how sudden the torque changes.

Ok after some reading and thinking I agree, but not from the examples given haha. The stuff I read about was tyre deformation, eg if you spend 10 seconds applying a torque figure x that doesn't cause wheel spin, if you decrease the time from 10 and tend towards 0, there will always be a time factor that causes wheel spin, due to the tyre not having enough time to deform.

The clutch example is bad harey, a better one would be stabbing the throttle as theres no stored up energy and torque multiplcation from a slipping clutch.

Edited by Rolls

The clutch example is bad harey, a better one would be stabbing the throttle as theres no stored up energy and torque multiplcation from a slipping clutch.

yes but at least I am right :)

Ok after some reading and thinking I agree, but not from the examples given haha. The stuff I read about was tyre deformation, eg if you spend 10 seconds applying a torque figure x that doesn't cause wheel spin, if you decrease the time from 10 and tend towards 0, there will always be a time factor that causes wheel spin, due to the tyre not having enough time to deform.

The clutch example is bad harey, a better one would be stabbing the throttle as theres no stored up energy and torque multiplcation from a slipping clutch.

You fool, how is this not direct related to what I was saying LOL. Tyres are a freaking VARIABLE.

The thing you are missing is, we are bastardising the concept by saying an 'increase in torque' will create wheel spin. The set variable is the acceleration, the 'increase' we are harping on about is actually the rate of GAIN for torque. IE how steep the curve is on gaining torque.

And hey this is what perfect turbo selection is about in my eyes. If you can have a steep curve from a low RPM to a usable RPM aslong as the width is good enough you should be able to get some big time acceleration.

If I turned back time to pre JZ for me, I would have kept my crappy RB and put one of these SS turbos on. Problem was I did not have the patience to wait for the development of a successful unit like HG have now.

IMHO there arent enough SS1 and SS2 powered skylines out there, and I think those turbos cater almost perfectly for the 250 and 300kw crowd from what we are seeing.

i just bought an r32 gtst drifter, no engine etc etc, in the boot was an Air Research T04 with OP6 on the rear housing.

i Spoke to Stao this arvo about rebuilding it to remove the crazy amounts of shaftplay.

very curious to see what he can make of it for my RB25 i have for it.

Some very constructive ideas. any way, refer to the GenEses development, The belt supercharger probably won't do as by looking at the dynosheet of SS-2 All I need is some thing makes 2psi+ pre 2500rpms, which should increase down low torque and extend mid range. I'm looking at a 35V electric motor:

http://www.rcgroups.com/forums/showthread.php?t=1276604

Run that into a 3inches duction fan I think I have a pretty good chance getting that to boost. I'm hopping it doesn't self destruct when turbo is sucking at 24psi, or I will need an additional intake pipe which opens when intake pipe pressure becomes negative. If I can program some sort of relay that activate this device in a short block of 5 secs at certain throttle position and have its battery(s) charged all times then it should be pretty consistent.

How ever if I do get 300rwkws with the new prototype with stock response then there might be no need for it. Either way its going to be a interesting hobby turbo to work on in the weekends.

Torque and wheel spin, if the torque is a built up in a 45 degrees angle then that will be lot less likely to wheel spin then some thing shoot up in a 75 degrees angle. As the driver I personally would like to feel my car's pulling all the way to red from the second I step into throttle. So far the SS-1, SS-2 and G3 FNT have felt great on road.

I did have a customer whom I recently built a FNT G3 for, he's made 265rwkws at 17psi on a super safe tune, even thou it didn't max lots of power but he's got a very linear curve and peaked heaps of linear torque at 4000RPMs, then that torque held very straight towards 7000rpms. I will post up his sheet this weekend, that sort of curve would feel excellent on road and beating V8 with.

Hmmm I have a couple of hypotheticals that may support Rolls' peak torque argument here. Will post tomorrow when I have time, but should we continue in this thread or another one? It's an interesting topic.

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



  • Similar Content

  • Latest Posts

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...