Jump to content
SAU Community

Recommended Posts

This tells you what BUT I dont know how to fix

1 Right front wheel speed sensor or circuit

2 Left front wheel speed sensor or circuit

3 Right rear wheel speed sensor or circuit

4 Left rear wheel speed sensor or circuit

5 ABS right front wheel actuator solenoid or circuit

6 ABS front front wheel actuator solenoid or circuit

7 ABS rear wheel actuator solenoid or circuit

8 ABS actuator motor, motor relay or circuit

9 ABS actuator relay or circuit

10 ETS control unit power supply or circuit

11 Fore-and-aft G sensor 1 or circuit

12 Fore-and-aft G sensor 2 or circuit

13 Fore-and-aft G sensor 1, fore-and-aft G sensor 2

14 G sensor power supply 1 or circuit

15 G sensor power supply 2 or circuit

16 Lateral G sensor or circuit

17 Air bleed connector or circuit

18 ETS pressure switch or circuit

19 ETS motor, motor relay or circuit

20 ETS solenoid or circuit

21 Throttle sensor or circuit

22 ETS oil level switch or circuit

The capacitors inside the G-sensor leak and cause the sensor to stuff up. This could save you some money

http://www.skylinesaustralia.com/forums/topic/356654-r32-gtr-g-sensor-fix/

Edited by central coast person
  • 1 year later...
  • 3 months later...

Eats solenoid is located on your attesa pump, which is a over your rear diff, if it's a r32 or next to the fuel tank if r33/34.

In the manual there is a trouble shooting guide that guides t you through fault finding the issue.

  • 1 month later...

Next time it comes on open the boot and count the number of flashes on the Attessa ECU. It will pause and then repeat the flashes.

Once you have the count look up the code earlier in this thread - that should identify the issue and the fix

Edited by Sinista32

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

    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
×
×
  • Create New...