Jump to content
SAU Community

Recommended Posts

You are correct r32 Gtr manual states front right sensor....try cleaning it, it’s very easy to take off. Just curious are your abs and 4wd light on? I just went through all this shit I’m sure we can solve it quick. 

54BE5EAA-5FDE-48D5-ADF0-7BFFC529531F.jpeg

Edited by MoMnDadGTR

ok so you currently are in 2wd.  so lets get this beat. 1. make sure you have a good positive and negative connection to your battery. 2. check the main ground from battery to frame to engine mount. now that the grounds are good make sure the connection for the wheel sensor is actually plugged in. its near the drivers side strut tower in the engine bay ill take a picture for you. as far as cleaning it goes, im sure you could even just wipe it if you remove it, I used brake cleaner.

No I’m pretty old school mate no Facebook, could be a good thread for others if we fix it as well. I know when I was fixing my error codes I found lots of threads with unsolved mystery ha. Here’s a picture of abs connector for right sensor.

63D0AAA9-50DC-48CE-8ADA-EA1D912B2F36.jpeg

Okay i can confirm my one is connected. But maybe it's not a solid connection whete there may be crap contact. 

 

I'll pull out my sensor and give it a clean after work today. 

My battery was relocated to the  boot after my engine build. My awd was working perfectly before 

 

I'll relocate the battery ground cable as it is now connected to the boot latch nut there. I might try the strut tower? 

I also chased wires like you until I replaced my atessa computer in the trunk of car(atessa control unit). mine had water damage from my rear windshield sprayer leaking and was telling me codes that weren't real. check for power and continuity at that clip as well that I just posted if all else fails. hoping that connector is loose as your issue.

if it was working before I wouldn't think move the ground. be patient. my car is setup very simple(no battery relocation or anything) so it was very easy to diagnose and fix. there are some super rebutable guys on here im sure they will step in if cleaning it doesn't work. just a question what ecu are you running? ive heard and seen guys having awd problems with apexi jetro systems...if you still have a stock ecu try a different one if you can get your hands on one

https://www.gtrusablog.com/2017/05/r32-nissan-skyline-gt-r-attesa-code-1.html

this is a link for trouble shooting your error code, im 99 percent sure this will lead you to your issue...the manual has worked every time for me in solving these attesa codes. I would print it off(about 800 pages so use your works printer full r32 gtr manual) if I was you is a gtr bible!

I highly suggest trouble shooting it with the link I sent you. (It’s straight from r32 gtr manual brotha) This will rule out things quick if you know how to use a multi meter. Way better than guessing but hope it works out.....all you have to do is pull the plugs from the atessa control unit and get to work. 

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

    • Thank you, 100% the intent. New coils were due and the 17" sixers look/feel loads better than the stock wheels. The aero options are so spot on.   Thanks for the warm welcome, all!
    • 98 r34 gtt Been rocking my latest setup and car running like never before. Have put a good 200 miles on it since all the latest changes and additions. everything is dialed in and have been driving it a bunch.   However, all a sudden last weekend as soon as I pushed throttle passed 4k and the engine stumbles, (slow or fast acceleration) hesitates and doesn’t go above 4100 or so, like a misfire. Everything else seems fine. I had a “good” set of coil packs that I removed from car when I first got it when I changed them over to new coils. I swapped out current ones for those, but no change. I also changed the plugs, no change. Seems to rev over 4 when out of gear with no load just fine no “misfire”, but as soon as its in gear with a load of any kind, it “misfires” as soon as rpm drop back below 4 k it runs perfectly, smooth, starts, restarts and drives fine as long as I keep it below 4 k while in gear. All readings look fine, no CEL   Any idea as to what could all a sudden cause an issue when pushing rpms passed 4 k?
    • When you say your cams are 272/262 is that 272in and 262ex?
    • We're arguing semantics. I am saying 45 accel and a 55 deccel ramp are "2 ways". Even a 45 degree ramp and an 89 degree ramp is "2 ways", because it is literally... two ways. The cusco 55/30 ramp is a 2 way. It's two ways. I get it though - in normal nomenclature a "2 way" would be 45/45 or 55/55 or 60/60 i.e the same locking in both directions. And something like 45/65 would be considered "1.5 way". I would then say if we're getting into the nitty gritty then every locking diff is a "2 way" diff and we should not speak in 1.5, or 2 ways but ramp angles instead. Which ofc if one of those ramp angles is 90deg, that side is not doing any locking. :p So Nismo don't obviously sell 3 things. The fact of the matter that they only sell two items really goes to show that there's a 2 way and a "1,5 way" which is really a 1 way. I believe the actual lockup for the 'adjustability' of the GT pro is really just setting preload for when the ramps actually start locking up. It's not changing how much 'wayness' there is. It is (somehow) horribly explained. People just buy whatever diff and go "locks up good bruh" and that's what ends up on socials forever.  
×
×
  • Create New...