Jump to content
SAU Community

Recommended Posts

On 25/03/2022 at 12:21 PM, bcozican said:

assuming not by the details in the discussion bit does Haltech upgraded software allow traction control through DBW?

Sure can :) 

Here's another mock up I've done for you (you can add more dimensions to it, such as a rotary trim switch position OR canbus keypad selection)

Note I do not work for Haltech, I just like their products as it's affordable and user friendly for the enthusiast tuner such as myself.

image.thumb.png.389581a2820040d9b43157b884aada63.png

  • Like 1

Thanks a lot for your answers!

So basically it will be for a setup around 800bhp, street use and some track days.

It's not meant for racing so I don't think I will have a lot of traction control scenarios as I want to keep it as simple as possible. Less effort for max performance.

So basically if the aftermarket ECU can deal with the quite high speed ABS wheel sensors (and maybe some circuitry in between to feed ECU with square wave) then it's just a matter of creating/tuning a map. This doesn't look too complicated or am I missing something ?

Then finally I'm considering keeping the ATTESA system as it's taking into account much more parameter that I thought.

I'm just concerned on how these 2 systems would work together :
exemple, low friction on straight line full power, the rear wheels start to spin then the ATTESA will send some power to the front until the rear stop.
But the aftermarket control see it too so it will reduce power ? or should it reduce power only when the front spin ? or should the aftermarket trigger only when the attesa system can't manage anymore: ie when the rear/front wheels are still spinning when the F/R torque ratio is 50/50 ?

https://www.gtr.co.uk/cdn-cgi/image/format=auto,onerror=redirect,width=1920,height=1920,fit=scale-down/https://www.gtr.co.uk/attachments/1648330759137-png.272474/

/cdn-cgi/image/format=auto,onerror=redirect,width=1920,height=1920,fit=scale-down/https://www.gtr.co.uk/attachments/1648330759137-png.272474/ It looks like there is a front torque meter, can someone point me out what is it and where it's located ?Also is 30kg.m maximum measurable value ?
Thanks again for your advice
On 3/26/2022 at 3:27 PM, bigboss59400 said:

Thanks a lot for your answers!

So basically it will be for a setup around 800bhp, street use and some track days.

It's not meant for racing so I don't think I will have a lot of traction control scenarios as I want to keep it as simple as possible. Less effort for max performance.

So basically if the aftermarket ECU can deal with the quite high speed ABS wheel sensors (and maybe some circuitry in between to feed ECU with square wave) then it's just a matter of creating/tuning a map. This doesn't look too complicated or am I missing something ?

Then finally I'm considering keeping the ATTESA system as it's taking into account much more parameter that I thought.

I'm just concerned on how these 2 systems would work together :
exemple, low friction on straight line full power, the rear wheels start to spin then the ATTESA will send some power to the front until the rear stop.
But the aftermarket control see it too so it will reduce power ? or should it reduce power only when the front spin ? or should the aftermarket trigger only when the attesa system can't manage anymore: ie when the rear/front wheels are still spinning when the F/R torque ratio is 50/50 ?

https://www.gtr.co.uk/cdn-cgi/image/format=auto,onerror=redirect,width=1920,height=1920,fit=scale-down/https://www.gtr.co.uk/attachments/1648330759137-png.272474/

/cdn-cgi/image/format=auto,onerror=redirect,width=1920,height=1920,fit=scale-down/https://www.gtr.co.uk/attachments/1648330759137-png.272474/ It looks like there is a front torque meter, can someone point me out what is it and where it's located ?Also is 30kg.m maximum measurable value ?
Thanks again for your advice

It's not too complicated but you will need to test it in the real world with ECU logs to refine it. As you have correctly identified you have to be careful about how you implement your strategy because reducing throttle input can cause the ATTESA system to reduce transfer case pressure, which is probably the opposite of what you want to happen when the car is losing traction. Also, if you're going to be building this thing to output 800 hp consider the impact of both soft fuel cut and ignition timing retard on the engine. Soft fuel cut will need some work to make sure AFRs don't go too wonky and some work to make sure the harmonics generated by running only 4 or 5 cylinders doesn't cause problems, ignition timing retard make cause EGTs to skyrocket past safe levels. The "front torque meter" in an R34 GTR is in the MFD. It is a number that exists, but is not particularly useful. It is not measuring anything. It is basically just an internal conversion table that takes the duty cycle target from the main torque split routine and converts it to a "kg-m front torque" value based upon whatever conversion they had from testing a prototype. The actual state of your transfer case clutch pack including the age and order/orientation of the clutch plates, the fluid used, the state of the fluid, the state of the pump's ability to produce pressure, the actual grip of the front tires, the actual torque output by your engine, etc all impacts how much torque actually gets sent to the front wheels especially because the factory front diff is open.

My first thought would be DBW to let the ECU be able to close the throttle and in the ECU output to ATTESA instead of sending it something related to TPS voltage I would instead take accelerator pedal position. Do some experiments to figure out how the factory TPS voltage is related to accelerator pedal position so you can get close to stock behavior at first. Also you should know that the TPS voltage is not sent exactly as-is to the ATTESA controller, instead it's some percentage of the TPS voltage.

Thanks for your detailed answer !

By soft fuel cut you meant lower injector duty cycle ?

My question might be stupid : why not stop the ignition for all cylinders but still opening a bit the injector to not rise the temperature too much ?

I never noticed such front torque caracteristic on the MFD, I will have a look next time

:O your thought looks very good ! thank you for the strategy !

On 3/29/2022 at 9:53 AM, bigboss59400 said:

Thanks for your detailed answer !

By soft fuel cut you meant lower injector duty cycle ?

My question might be stupid : why not stop the ignition for all cylinders but still opening a bit the injector to not rise the temperature too much ?

I never noticed such front torque caracteristic on the MFD, I will have a look next time

:O your thought looks very good ! thank you for the strategy !

By soft fuel cut I mean what was discussed before, cutting fuel to cylinders in a random fashion. So maybe every engine cycle (720 crank degrees) you are cutting fuel to one of the six cylinders. Or maybe two of the six cylinders. You cannot reduce injector duty cycle because that will just cause a lean-out that blows up your engine. Stopping ignition to all cylinders while still injecting fuel is a hard ignition cut limiter. Continuing to inject fuel like this without ignition is a very dangerous game to play, the air and fuel will be mixed properly and any spark or sufficient heat will cause it to ignite, possibly in the exhaust which can damage the cylinder head and turbine. As a general rule if you need to hard cut rev limit you should cut all fuel injection to all cylinders. OEMs do this not just for emissions reasons but also because it's a lot safer. Just the air pumping through the engine with no fuel will cool things down. The only danger as I mentioned is if your transient fuel control is not good, then constantly cutting fuel injection and resuming may cause lean-out. DBW is easier for this reason, just force the throttle to close to reduce torque instead.

  • Thanks 1
  • 2 weeks later...
On 09/04/2022 at 12:48 AM, bigboss59400 said:

Just a confirmation, since my front and rear are LSDs

I can connect only one rear and one front wheel speed sensor ?

Yes you can, however your traction control won't work where you are spinning all 4 wheels.

You need a GPS sensor to make the traction strategy work with a 4WD car work properly.

  • Like 1

If the 4 wheels are spinning,

Do you mean the traction control will not work if I connect only 2 over the 4 wheel speed sensor even if I have LSDs ?

Or do you mean I need a GPS to get the actual speed of the vehicule ? If so then yes I thought of adding a sensor like this but thanks for pointing this out again :)

 

Instead of a GPS which is quite slow, I'm looking in ground speed sensor type (radar at 24Ghz) but there are not a lot of brand and looks like it's not cheap too !

Edited by bigboss59400

If you want good quality traction control you need 4 wheels speed sensors. There is a mile of time (in traction control terms) between one wheel slipping, the slack being taken up, the diff locking, slack to the other wheel taken off and grip being delivered. No modern system is OK with that, single sensor ABS was obsolete about 30 years ago.

Also, I would never use just GPS for traction control. It is way to slow and inaccurate, particularly for rally use with large trees around. If it can be a 5th input to a system I would add it but you almost never have to deal with a situation with all 4 wheels slipping, at the same time, at the same speed unless you are doing it on purpose...

  • 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


  • Latest Posts

    • I’d love to find some where that can recover the dashes to look brand new and original. Mine has a very slight bubble, nothing compared to some I’ve seen though 
    • $170K. I asked one of the guys there as a joke if that price was just for the passenger seat as it was where the price sheet was... he tried really hard to crack a smile 😄 He also mentioned that every single part of the car was inspected and either restored or replaced with a new or as new part, or made from scratch. The interior was incredible, every inch like a new car.
    • Time for a modernisation, throw out the AFM, stock O2s, ECU into the e-waste bin. Rip out the cable throttle, IACV, pedal, etc. into the scrap metal bin. DBW, e-throttle, modern ECU, CANbus wideband, and the thing will drive better than when it left the factory.
    • I agree, don't go trusting those trims. As I said, first step is to put the logger away, and do the basics in diagnosis.   I spend plenty of time with data loggers. I also spend plenty of time teaching "technicians" why they need to stop using their data loggers, and learn real diagnostics.   The amount of data logs I play with would probably blow most people away. I don't just use it to diagnose. I log raw CAN data too, as a nice chunk of my job is reverse engineering what automotive manufacturers are doing.
    • I'm aware, but unless you're actually seeing the voltage the ECU is seeing and you're able to verify the sensors are actually working I find it hard to just trust STFT/LTFT. I will say, logging the ECU comes naturally to me because it's one of the lowest effort methods of diagnosis and I do similar things in my day job all the time. Staring at 20+ charts looking for something that isn't quite right isn't for everyone. NDS1 allows you to log almost everything so that's normally what I do and then sort out the data later. 
×
×
  • Create New...