Jump to content
SAU Community

Recommended Posts

Hey guys i bought a R32 GTS-4 last week and been having some troubles. The car came equipped with a TSC, Now if i have it in 4wd and any number on the dial i use after a couple minutes of driving the 4wd & ABS like comes on. Now if i switch it to 2wd the lights comes on automatically like they are expected to and the car drives fine but at low rpms till about 2000 rpm i can hear a whining noise almost like constant friction rub but the noise only comes while I'm accelerating. And for the couple minutes that 4wd works when i try it there is no noise at low rpm.

Now I have been reading that different size rims could cause the ATTESSA system to shut off 4wd, The rears are 17x9+24 on 225/50/17 and the fronts are not as wide (I'll get the size tomorrow) but also have 225/50/17 on them. So here is a list I have made to check tomorrow, let me know if I'm in the right direction.

1. Check battery and charge it (While driving it tonight for the first time in cold weather when i put the clutch in the revs would go from 1000 to 2000 and hold there for a couple of seconds and battery light flashed 3 times when i almost came to a complete stop then went back to normal.) The previous owner wired 3 gauges and a turbo timer to cd player 12v maybe this could be a problem.

2. Check pump fluid in the boot

3. Check front tire width

4. Drive it in 4wd till light comes on and read errors on ATTESSA

5. Disconnect TSC and try

6. Change fluid in diffs

7. The car is on cobb coilovers and i have rims cambered a bit, could ATTESSA turn awd of for this to?

If anyone has anything to add that i should try tomorrow or if any of these don't relate let me know please. The car is also running greddy emanage ultimate and has a hicas lock bar.

Link to comment
https://www.sau.com.au/forums/topic/409412-4wd-light-comes-on-while-driving/
Share on other sites

ATTESSA is controlled by a seperate ECU in the boot, the error code is a red light iirc that flashes, I've never actually done it myself but the error code should still be on there unless it gets wiped on engine shutdown. Since 4WD and ABS are linked to the same sensors, you could have a faulty wheel speed sensor but you won't know for sure till you get that code.

Erros codes are a pain to read and more then not i find not accurance, Get it hooekd up to a Nisaan consult and diagnose that way. Probly same reading but i hate craming hy head under there trying to read thoes dam flashes.

ATTESSA does need same rolling diamitor all around

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