Jump to content
SAU Community

Recommended Posts

I'm not sure that's really true, there are 4 wires shown on the diagram and its very hard to read. 2 wires are for the g meter reading and the other 2 power and earth, but I'm not sure which of those would be useful as an AVI for an ECU.

I've been meaning to sort this out for mine too, so it would be good to hear from anyone who has it working

  • Like 1

If one is power, and one is earth, they would be readily findable with MM. Then the other 2 are the signal and its likely signal earth.

Notwithstanding that - this is the snip from the R32 wiring diagram.

image.thumb.png.336159d5dd74c774f7974f452fc4249f.png

The wire numbers are reasonably well identified and the call outs to 30 and 35 go to terminals 44 and 45 on the E-TS control unit. Seems simple enough. Should be quite similar on the 33.

  • Like 2

Just thinking even when finding the proper wiring, the problem then comes with the display value in the ICC software.  Im not sure of the proper value to choose from. the Haltech as it doesnt have a value for Kg/m^2 (torque). I think the Haltech would have to have a display unit option for Kg/m^2 or lbs.

Anyone have a Haltech connection? I'll slide them a $5 for R&D cost lol

 

For the calibration, I'd just log to get the highest voltage the signal delivers, then call that "50%". It's not like there is any real accuracy in the gauge, the value sent from the ATTESSA control unit is just an intended target, not an actual value delivered by a 30 year old, worn system.

  • Like 1

From Haltech:

Thank you for reaching out! 
 
"Now that we have a proper ATTESA control function, this will be added. 
What I have done in the past is use a generic to follow the ATTESA function output and generate a 0-100% channel in the iC-7, so you can see how much power is being sent to the front. 0 being RWD only, and 100% being as close to 50/50 as it can get."
3 hours ago, Duncan said:

Good on them for quick response. I don't suppose they confirmed the dash wire pin too?

They didnt provide a pinout or ETA for a firmware patch with this update.

I have tested the front torque gauge on the bench, the input from the ATTESA ecu is 0-5v.

There are four terminals. As  suggested above there is a fixed 12v across one pair of opposite screw terminals and the "sensor" 0-5v and sensor ground on the other two terminals. 

The copper track on the plastic "circuitboard" leading to the sensor 0-5v terminal is labelled "ETS" from memory (on the R32).

The calibration units for the display on the ic7 dont matter really but you could use 0-50% or 0-288psi on a r32. If its a r33 then it would be 10-50% or 25-288psi because of the minimum pressure they run (that i guess isnt shown on the gauge).

Based on my tests the front torque gauge meet doesnt totally accurately reflect the front wheel torque or centre clutch pressure in some conditions like the "fast start" behaviour when stationary, when the guage doesnt show that the centre clutch has been activated. But its close enough unless you are data logging for the track in which case drill/trap a pressure sensor on the back of the transfer case.

  • Like 5

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

    • Both windows operate normally while the engine is running but start to sag as soon as I switch off.  Does anyone know of reasonably priced replacements or other brands that will fit?
    • Actually PowerFC is probably the easiest to get basic data from, it comes with a hand controller and display so you don't need to remember to pack a laptop every time you drive. It also has a PC based viewing/logging option if required. Nissan used consult on these because back in the mid 80s, ODB was just a glint in a standard's body's eyes.  They switched to OBD shape around 2000 (my 2001 Cima had OBD shaped but not OBD compliant port) With the standard ECU there is a cable and software available to give basic data too, I think it is called Nissan Data Scan or s
    • Given by the sheer number of questions about offset, absolutely not. If you had the information formatted this way: Space from R34 GTT hub to outer arch = 100mm Space from R34 GTT inner hub to nearest suspension arm = 90mm. (making this up) Buying a wheel that was advertised as Enkei RPZ5 Diameter 18in Width 9 Distance to arch = 84mm Distance to suspension arm = 76mm 100% of people would know instantly if it fits. They would absolutely also know instantly how close it fits too, and no questions would need to be asked. You would know you would have 16mm from the guard and 14mm from the suspension arm.
    • Ah ok, for example for the apexi ecu I heard that it's pretty limited with the information it can give you. Also not sure why Nissan used the consult port over the obd2, what the idea there was.
    • Diagnosing with and without is mostly the same. You need to know, as Duncan asked, and what conditions. Car hot, cold, idling, driving, if while driving what rpms, is when you're varying, or is it when held constant.   From there it's understanding what can be causing it. Starting with pretending all of the sensors are correct. Which means if it's going rich, why would it be thinking more air is going in than it is, and under what conditions. So things like if only when under boost, it could be be a loose intake piping joint. It's just understanding the system, and understanding when/how the problem occurs, and then if it's only occuring in specific scenarios, what can be causing it.   ECU specifically, if it's aftermarket, it'll have software you can use, for the Skylines on factory ECU, there is Nissan Consult you can use. Most ECUs have a way to get data from them.
×
×
  • Create New...