Jump to content
SAU Community

R32 Attesa Not Working, No Relevant Codes

R32N00B
 Share

Recommended Posts

R32N00B Contributor

R32N00B

Posted
Posted

hey guys, need some help with this one.

ATTESA was working fine a year ago, but the car has been down getting new work done.

I have since deleted HICAS, Deleted ABS, and swapped from Power FC to AEM EMS.

There is no 4WD light coming on but my torque gauge is dead, it doesnt move.

(I had this problem when i first got the car and it was the g-sensor, i swapped it with a new one and have had 4wd since than)

When i flash codes from the attesa ECU i get code 8 and code 9 which are both for the ABS module and expected. From what I read this doesnt affect 4wd. no other codes. I know the Attesa ECU needs to see RPM, TPS Etc. But i would think it would throw a code if it weren't seeing these things. The aem has the proper circuit dedicated to TPS and RPM out, its not like i need to configure those outputs.

If anyone has been down this road before please help me out.

If it was giving me a code at least I'd know where to look.

thanks in advance

blind_elk Grand Master

blind_elk

Posted
Posted

ATTESA uses the ABS sensors for detecting wheel slip. If a lack of ABS didn't affect ATTESA, then why on earth would Nissan have built error codes into the system?

Any error causes ATTESA to not work. If you don't have a AWD light, then have you checked the bulb is working?

bozodos Grand Master

bozodos

Posted
Posted (edited)

had the same issue with my old R32 GTS-4 with RB25DET and Microtech - was never able to devise a way to make it work, and mine didn't throw a light either. I tried doing the wire crossing for the TPS signal, piggbacking a stock ECU onto the old loom, etc, no luck. The only possible lead I got told about was the existence of a signal box to make the ATTESSA ECU independent of needing TPS signal from the engine ECU?

If you ever manage to work it out please post up how you did it.

Edited by bozodos
R32N00B Contributor

R32N00B

Posted
  • Author
Posted (edited)

Yes I know attesa uses abs sensors but they Report directly to the attesa ecu (it's also the abs ecu hence why it blinks abs codes as well as attesa codes) so it's getting the signals it needs just fine

The codes 8 and 9 are relevant to the abs pump which has nothing to do with the 4wd

I've read about several (a lot) of people pulling abs pump out with no 4wd problems at all

Edited by R32N00B
blind_elk Grand Master

blind_elk

Posted
Posted

No help?

Not if you call people trying to help "bozo" :no:

ATTESA clearly relies on the ABS system working. If you've disabled ABS by removing the pump, then ATTESA is well within its rights to shut down as well.

Have you confirmed that the AWD warning light is working?

R32N00B Contributor

R32N00B

Posted
  • Author
Posted (edited)

Not if you call people trying to help "bozo" :no:

ATTESA clearly relies on the ABS system working. If you've disabled ABS by removing the pump, then ATTESA is well within its rights to shut down as well.

Have you confirmed that the AWD warning light is working?

Bozo is the guys screen name i was responding too.... -_-

As that's just not true I've searched and found over a dozen people removing the abs pump, getting codes 8/9 and have no Negative affects to the awd function

So I know that's not my problem

But for shits and giggles I'm going to pick up my abs pump at my old shop to plug it in and see but seeing how it's been done time and time again (and r32 n1 models come with no abs too) I doubt it will change anything.

ATTESA needs wheel speed sensors, yes I know this, I accidentally left one unplugged one time and got the code from the attesa ecu, when I plugged it back it it functioned perfect again, but it doesn't need the abs pump/solenoid assembly, that is strictly for ABS

Edited by R32N00B
bozodos Grand Master

bozodos

Posted
Posted

been seeing a lot of these R32 ATTESA threads coming up lately, can't remember if I ever looked for flashing LEDs on mine. Did not help that mine had a Stagea RB25 motor and gearbox as well, car was a headf**k from start to finish.

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
 Share
Go to topic listing


  • Similar Content

  • Latest Posts

    • GTSBoy
      Mistakes were made, my R34 Story

      By GTSBoy · Posted

      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. 
    • Kinkstaah
      Mistakes were made, my R34 Story

      By Kinkstaah · Posted

      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.
    • GTSBoy
      Mistakes were made, my R34 Story

      By GTSBoy · Posted

      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.
    • Kinkstaah
      Mistakes were made, my R34 Story

      By Kinkstaah · Posted

      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.
    • GTSBoy
      Mistakes were made, my R34 Story

      By GTSBoy · Posted

      Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...