Jump to content
SAU Community

Recommended Posts

Hey yall,

Been a thought iv had for years, thought it would be worth to throw it out there.

Say im looking for something more from a BNR32, what would be required to get my ATESSA up to scratch. Using a G-force sensor bender is a bit old hat, and doesn’t change the fact the system is clocking 10 times a second.

What do you think is required to get a R34 / 33 system into a BNR32?

Would the diff chassis lengths (hence torque application software) make it not work? Would i need to change transfer cases, or could simple ECU and sensor changes suffice?

Thoughts, opinions flames???? :yes:

M

an alternative could be to get a GRID dancer controller or hks ETS controller and upgrade the 4wd clutch packs to make it stronger

you could also look at locking the pump on via a relay interceptor if you have the vspec system (i did this in my gtst)

an alternative could be to get a GRID dancer controller or hks ETS controller and upgrade the 4wd clutch packs to make it stronger

you could also look at locking the pump on via a relay interceptor if you have the vspec system (i did this in my gtst)

Yah, unfortunately,

Using a G-force sensor bender is a bit old hat, and doesn’t change the fact the system is clocking 10 times a second.

The ATTESA system as a concept is one that’s used now by most of HiPo manufactures like Porches etc. I don’t want to lock it solid, front to back, nor simply strengthen the clutch packs, Iv never driven a R34 GTR, but am told the system is a lot more progressive and adaptive to wheel spin, and how tight it push’s the packs together. You can watch from footage of quick examples how it effects the attitude of the car (understand the E-diff has a role here, but lets leave that out of the equation for now)

Any other thoughts

Is the R23 V-Spec II a 1000/sec ecu, or was it just a retuned 100/sec ecu? The probelm I see with a R33/R34 ecu is that they have 10% always going to the front wheels, and if you put one of those ecu's in a R32, it would expext 10% to always be there.

Our Targa car has a HKS Kansai controller, no idea how good it is cause we've never turned it on (came with the car), if anyone has any english instructions i'd appresiate it.

Unless the controller replaces the attessa computer completly it can't refresh quicker. I've never seen the Bee-R ones but the grid and all the locally made ones like ours leave the standard computer in place

Is the R23 V-Spec II a 1000/sec ecu, or was it just a retuned 100/sec ecu? The probelm I see with a R33/R34 ecu is that they have 10% always going to the front wheels, and if you put one of those ecu's in a R32, it would expext 10% to always be there.

Stupid question..

but..

Why?

This does answere MANY MANY questions! I went staggy RB25 + ECU in my GTS4 and.. GUESS WHAT!?!.. 10% all the time..

..ghay..

Any way you cans stop/change it?

I think the trasferbox is designed diferently. As you have to remove the front shaft to dyno R33+, and not just the ecu fuse. well 10% is sfa in the grand sceme of things, i assume it balenced the car a little better, and it would make the attessa feel more responsive. The R32 one can feel a little slow at times.

Did you do the gearbox/trasfur case with the engine and ECU?

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

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...