Jump to content
SAU Community

Recommended Posts

G'day all,

I have been playing with my R32 GTR for a little over 12 months now, and am still relatively confused as to how the 4WD system works in the car. I have been competing in a wet skidpan motorkhana championship throughout the year, and during those events have been confused by how the system reacts versus how it is supposed to react.

It's simply a very wet skidpan scenario, lots of revs, lots of handbrake and clutch work. I have noticed though that if I throw the car around a cone in a 180 degree turn, when I step off the clutch the rear wheels hook up quite strongly and no power at all goes to the fronts. The car sort of hovers with the rear wheels screaming for probably a second to a second and a half, and then the fronts kick in, and I launch off across the concrete towards the next cone.

In a drift situation where I am feeding the power on, and sliding sideways around the obstacles, mostly the fronts engage and I get a nice smooth all-wheel drift. Sometimes though, the fronts will only kick in mid corner, or will cut-out mid corner. I don't get a warning light, or any error codes throughout the competition, and all the fluids / reservoirs seem good. If I grab the handbrake too quickly before the clutch is all the way in, I get a 4WD warning light on the dash, so I know that at least the light is working.

Is there any hard and fast rule or information about how the system should be working in those circumstances? I get a lot of people coming up to me and asking if I have disabled the system, or if I have a controller and have put most of the power to the rears. Granted, none of the people who ask me own Skylines, or know much about them, so they could just be assuming it's meant to be constant all wheel drive?

On a dry road, the system works great and I've never noticed it cutting in and out during normal or even "spirited" driving on dry surface.

Anyone got any similar experiences? Or can at least fill me in if this is how it should be working, or if it sounds like there's an issue?

Cheers.

Cliffs

Under load on wet skid pan during Motorkhana competition, front wheels engage randomly, and disengage randomly, causing me to spin out which makes me sad. Help.

Do you remember what the torque gauge is doing?

It could give you an indicator.

If the gauge is working instantaneously but you're not feeling the fronts grip, then the fault would be mechanical but if the torque gauge isn't reacting, I'd guess electrical.

As an aside I check mine in a wet grassy paddock, haven't done wet bitumen. (haven't had a wet paddock for a while either)

Does slides, straight line clutch drops etc and it hooks up as I'd expect, instantly, gauge and front wheels all happy together.

I found this article interesting:

http://www.autospeed.com/cms/article.html?&A=107753

The G sensor is pivotal to how the system reacts. Also it might be worth re-calibrating the G-sensor. You can see how I did it in my thread here: http://www.sau.com.au/forums/topic/356654-r32-gtr-g-sensor-fix/

Regards,

Jeff

I'd say that using a fairly crude AWD system in a scenario it wasn't set up for will likely cause unexpected results. The GTR was intended to be a tarmac race car. The ATESSA was pretty much there o make it power the front wheels on a straight line launch and to transfer drive to the front under certain lateral G conditions. If that Autospeed article linked above is the one where JE swapped or rotated his G sensors, you can get a good idea of how basic the program in the computer is.

Being the first incarnation of ATTESSA, the version in the R32 was quite crude, and relatively slow to react (compared with the versions in R33, R34). So it's quite likely that your manouvres on the skidpan are happening so quickly that ATTESSA can't keep up, and may lag behind or just give up in despair.

There's some pretty clever blokes working on the "G" sensor and their results are astounding.

Datsun_1600 would be one of those blokes and there are others on the GTROC forum.

Incredible that upgrading this sensor can have such a profound effect on a 25 year old chassis.

Sure the 32 was the first ATTESSA version but the 33 isn't too different, maintaining line pressure to the transfer case clutch packs in order to reduce their reaction time.

I do like the electronic upgrade.

Fixing a faulty G sensor and improving the performance of the ATTESA system as a whole are not quite the same thing.

There have been a number of aftermarket ATTESA controllers done by various people for various purposes. The early Jap ones were pretty much teh same sort of thing that JE came up with - effectively signal benders. But it's not really the G sensor that needs to be modded so much as making the ATTESA computer faster and more thoroughly programmed to be able to control the output side of the system more appropriately. Vis ATTESA Pro and so on.

IMO the biggest problem with R32 ATTESSA is its tune, not the response speed. The ATTESSA ECU takes fore/aft accelerometer and slip signals to push power to the front (which works fine, as we see in straight line response) but then uses the lateral accelerometer signal to reduce the amount of power that goes to the front (this function is way overdone). The signal benders reduce the lateral accelerometer signal, so the ATTESSA ECU doesnt cut power so much.

$60 ebay signal bender transformed my 32.

The more work you've done on your suspension setup to reduce understeer, the more power you'll be able to send to the front. Nissan included the lateral accelerometer/power cut function as a way to stop power induced understeer.

Do you remember what the torque gauge is doing?

It could give you an indicator.

If the gauge is working instantaneously but you're not feeling the fronts grip, then the fault would be mechanical but if the torque gauge isn't reacting, I'd guess electrical.

As an aside I check mine in a wet grassy paddock, haven't done wet bitumen. (haven't had a wet paddock for a while either)

Does slides, straight line clutch drops etc and it hooks up as I'd expect, instantly, gauge and front wheels all happy together.

The gauge is working when the wheels engage. If I complete a hook turn and step off the clutch, as the rear wheels spin up, the gauge does nothing, but then as the fronts kick in, the gauge then bounces up to the level it is seemingly providing. So I think the relationship between the wheels and the gauge is ok.

I found this article interesting:

http://www.autospeed.com/cms/article.html?&A=107753

The G sensor is pivotal to how the system reacts. Also it might be worth re-calibrating the G-sensor. You can see how I did it in my thread here: http://www.sau.com.au/forums/topic/356654-r32-gtr-g-sensor-fix/

Regards,

Jeff

Cheers Jeff, I'll have a read through the article and your thread. A re-cal might be worth doing, even if it doesn't 100% fix the issue.

I'd say that using a fairly crude AWD system in a scenario it wasn't set up for will likely cause unexpected results. The GTR was intended to be a tarmac race car. The ATESSA was pretty much there o make it power the front wheels on a straight line launch and to transfer drive to the front under certain lateral G conditions. If that Autospeed article linked above is the one where JE swapped or rotated his G sensors, you can get a good idea of how basic the program in the computer is.

Of course - Never have I expected the system to work flawlessly while chucking it around a wet skidpan, and I am under no illusion that it was designed for that purpose. But Tarmac race-cars sometimes raced in the rain, so surely the system would have had *some* of it's design characteristics aimed towards putting the power down on a wet surface.

Being the first incarnation of ATTESSA, the version in the R32 was quite crude, and relatively slow to react (compared with the versions in R33, R34). So it's quite likely that your manouvres on the skidpan are happening so quickly that ATTESSA can't keep up, and may lag behind or just give up in despair.

Hmm... I think the lag is definitely there, but was hoping that it was for a reason other than that it just simply can't keep up.

There's some pretty clever blokes working on the "G" sensor and their results are astounding.

Datsun_1600 would be one of those blokes and there are others on the GTROC forum.

Incredible that upgrading this sensor can have such a profound effect on a 25 year old chassis.

Sure the 32 was the first ATTESSA version but the 33 isn't too different, maintaining line pressure to the transfer case clutch packs in order to reduce their reaction time.

I do like the electronic upgrade.

I'll have a look over on GTROC and see what I can dig up. Cheers.

IMO the biggest problem with R32 ATTESSA is its tune, not the response speed. The ATTESSA ECU takes fore/aft accelerometer and slip signals to push power to the front (which works fine, as we see in straight line response) but then uses the lateral accelerometer signal to reduce the amount of power that goes to the front (this function is way overdone). The signal benders reduce the lateral accelerometer signal, so the ATTESSA ECU doesnt cut power so much.

$60 ebay signal bender transformed my 32.

The more work you've done on your suspension setup to reduce understeer, the more power you'll be able to send to the front. Nissan included the lateral accelerometer/power cut function as a way to stop power induced understeer.

Thanks mate, the signal bender sounds like something I should look into. If I do a G sensor re-call, and test it, and then if still no luck, have a look at one of these jobbies, hopefully I can get a solution. Do you remember which one you used? Brand? Description? I'll scan eBay and see what I can dig up.

Thanks for the responses - It was a relief to log in here and not just see a bunch of replies of "Your system is f**ked" etc... There's still hope! Lol.

I will have a bit of a read of the G-sensor stuff and the benders and see what the go is.

Cheers.

Assuming ATTESSA is working fine - Get the transfer case modded by a place that knows what they're doing. Power transfer comes on sooner and harder. Difference is night and day. Best $ mod for handling i've ever done.

  • Like 1

It basically runs in 2wd most of the time I'm competing anyway, and that works well for certain maps/courses, but I'd love the AWD to work full-time just to see what difference it makes. It's a wet skid pan, so no major loading of the driveline, it would just be interesting to see how it changes things.

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

    • The car/ECU will have all the sensor that it needs and expect to have. I think i do not have to explain to you how the Link is way better specialy if you have swapped engine   I just do not want to deal with any "problems" cuz i have only Nistune which i learned is not that great and in my case cant even deal with that speed problem (Link can) And of course it will be way more easier to tune and diagnose and safe. And for the ECU/speed problem...i dont know.
    • Per Mark Roberts of Sonictune: Mark Robert Author At this time, no. No ETA either 2016-17 models. You will be able to purchase and install a 2018.5+ TCU though   TCU purchasing and pricing info! As we near the release of TCU tuning, I am going to answer some questions I get asked often.   What do I need for TCU tuning? At this time, you will need a 2018.5+ TCU to be able to tune. If you have a 2016-to early 2018, you will need to replace your TCU with the newer version. One good way to know if your TCU is good is if you have auto upshift in manual mode in 1st gear around 6500 rpms. If your manual 1st gear goes to 7k rpm and will hit the rev limiter unless you shift, you have the older TCU.   Why do I need to buy another ecu license/phone flash if I already have it on my ECU tune? The TCU is its own computer module. It is completely separate from the ECU. Because of this, you will be required to purchase a TCU license and, if your tuner has it, the phone flash license required to tune it via phone/bluetooth.   Do I need TCU tuning? TCU tuning is NOT required. However, the faster your setup, the more it will assist in track and dragy time consistency.   If I’m ECU tuned by (tuner A) can I get my TCU tuned by (Tuner ? Yes, since it’s a different module and a completely separate flash, you can have two different tuners. However, it is highly recommend that you have both tuned by the same tuner. For me, my TCU tuning will directly complement my ECU tuning style and features and running my ECU and another TCU or vice versa MIGHT cause some issues. At this time and for the foreseeable future, I will only be tuning my current ECU tuned customers TCUs.     I have a SYVECS AWD controller. Do I still need it? Yes! The AWD controllers main job is to control your AWD system. However, with TCU tuning, you will no longer need the auto-shift function as that will be done through the TCU. The AWD controller will still be very beneficial for racers looking to maximize traction on the launch.     Shift schedule changes: holding gears longer at lower pedal input as well as max shift rpm changes. Please note, the new ECU race rom coming out will address 90% of the shitty drivability issues these cars have through custom maps from myself and Racebox—as well as others I am sure.   Increase shift speeds: as seen in the videos I’ve been posting, the TCU shifts much faster once tuned.   Increased shift pressures: as also seen in the videos, much firmer full throttle shifts.      
    • Per Mark Roberts of Sonictune:     Mark Robert Author At this time, no. No ETA either 2016-17 models. You will be able to purchase and install a 2018.5+ TCU though   TCU purchasing and pricing info! As we near the release of TCU tuning, I am going to answer some questions I get asked often.   What do I need for TCU tuning? At this time, you will need a 2018.5+ TCU to be able to tune. If you have a 2016-to early 2018, you will need to replace your TCU with the newer version. One good way to know if your TCU is good is if you have auto upshift in manual mode in 1st gear around 6500 rpms. If your manual 1st gear goes to 7k rpm and will hit the rev limiter unless you shift, you have the older TCU.   Why do I need to buy another ecu license/phone flash if I already have it on my ECU tune? The TCU is its own computer module. It is completely separate from the ECU. Because of this, you will be required to purchase a TCU license and, if your tuner has it, the phone flash license required to tune it via phone/bluetooth.   Do I need TCU tuning? TCU tuning is NOT required. However, the faster your setup, the more it will assist in track and dragy time consistency.   If I’m ECU tuned by (tuner A) can I get my TCU tuned by (Tuner ? Yes, since it’s a different module and a completely separate flash, you can have two different tuners. However, it is highly recommend that you have both tuned by the same tuner. For me, my TCU tuning will directly complement my ECU tuning style and features and running my ECU and another TCU or vice versa MIGHT cause some issues. At this time and for the foreseeable future, I will only be tuning my current ECU tuned customers TCUs.     I have a SYVECS AWD controller. Do I still need it? Yes! The AWD controllers main job is to control your AWD system. However, with TCU tuning, you will no longer need the auto-shift function as that will be done through the TCU. The AWD controller will still be very beneficial for racers looking to maximize traction on the launch.     Shift schedule changes: holding gears longer at lower pedal input as well as max shift rpm changes. Please note, the new ECU race rom coming out will address 90% of the shitty drivability issues these cars have through custom maps from myself and Racebox—as well as others I am sure.   Increase shift speeds: as seen in the videos I’ve been posting, the TCU shifts much faster once tuned.   Increased shift pressures: as also seen in the videos, much firmer full throttle shifts.      
    • The fancy pants red shock tower brace is finally incoming from MX5 Mania, getting it shipped from 'Merica has been a long and problematic process, and GWR, the 'Merican supplier will not ship directly to consumers outside of the US, Mania basically had to order a heap of them, the colour choice was silver, or red, and we all know anything red adds 5 killerwasps of dynotorques..... Whilst it does fit over a 2.5, and I've seen a few photos and videos of it being installed and fitting, google also says it might get real close to the FAB9 intake front runner, people in the US says it does fit with the FAB9 intake, except for one person who said it slightly touched.......so there is that.....LOL..... As it seems that I am the first in AU to have this combination of parts there's no local knowledge about fitment, so I'm just a willing guinea pig in this endeavour, I'll cross my fingers and toes and hope for the best In other news, I ordered stuff from China  on the same day I ordered the 23° silicone bend from Victoria, the stuff from China arrived a day ago, the 23° silicone bend is still travelling around Australia thanks to Australia Post, and "may" be here next week
    • Very good news...I contacted Racebox about it last night. My car is a 2016 so remains to be seen if it is compatible, requires a TCU swap, or is impossible.
×
×
  • Create New...