Jump to content
SAU Community

Recommended Posts

  • Replies 114
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

quite possibly that would just be from an external accelerometer than something in the ecu? what other things are on the dash? if theyre largely mechanical type things (rather than typical sensor readings from consult) then id say thats what it is

does it say anything in the service/user manual (if there is one?)

Edited by NewKleer

The R34's show the G-sensors digitally on the dash for 2000 models up, and mechanically for 98-2000 models.

The R32 GTRs and GTS4's have a couple of G-sensors around the place, but you don't get to see what they're doing. I think they would go to the ECU though.

I'm pretty sure the g-sensor would need to report to the ECU for ATTESSA functionality, unless of course there's a sperate unit/controller for it...

Also, just to confirm... HICAS is also controlled from the ECU? Or does it just manage the steering angle sensor and the like somewhere else?

  cowie165 said:
Re: G-sensor ECU input for R32 GTR. The last few pages are the relevant section. It's the Autospeed article on the R32 from years back.

Thanks for the article, which for those that havn't read it, explains how to intercept the signal between the accelerometer (g-sensor) and the ECU. Which also allows for modification (i.e. piggyback system).

However, what I'd like to do, is read the sensor output voltage from the ECU (via the consult port)

Suppose we could try some reverse engineering.

trying to read g-sensor via consult port would mean reprogramming the ecu (and knowing how to do something like that). would take 5% of the time of that to just read the voltage directly from the sensor.

The documentation I have read implies that there *is* a consult port (that is, it had an id byte after a two byte initialisation)

it just doesn't seem to be wired up.

Of course, I could be wrong.

though it appears that all the computers get *all* their data as sensor voltages.... ahh, the possiblilties are endless

(when I make that attessa controller, I'll share it with confidence - as opposed to state my theory and get shot to pieces)

While I'm at it, I'll ask this question:

What are the inputs to the hicas computer, AND how does it control the pump (r32).

heck - the same with attessa. I have partial information on the input, none on how it controls the centre diff.

I suspect I'll need to get at it with a multimeter one day...

supposedly air con, hicas, and auto transmission can be queried via consult protocol, but ive never had success. i saw a table of whats supported in what vehicle, and i think the common cars only support ecu, whereas gtr and z32 (which ive never tried) support some of the others

Consult and Conzult work with AirCon, Hicas and Auto Trans in the Z32's. They each have their own seperate control unit but all read from the DDL.

quote=NewKleer,31 Jan 2006, 06:26 PM]

supposedly air con, hicas, and auto transmission can be queried via consult protocol, but ive never had success. i saw a table of whats supported in what vehicle, and i think the common cars only support ecu, whereas gtr and z32 (which ive never tried) support some of the others

  • 2 weeks later...

have released an alpha version of ecu talk while or work on the consult lcd

http://www.ecutalk.com

needs .net framework 1.1, links on the downloads page there

Edited by NewKleer
  NewKleer said:
supposedly air con, hicas, and auto transmission can be queried via consult protocol, but ive never had success. i saw a table of whats supported in what vehicle, and i think the common cars only support ecu, whereas gtr and z32 (which ive never tried) support some of the others

on my r32 gtr the hicas ecu wont respond to the initialisation unless there are delays between bytes but the engine ecu responds with no delays could be to do with the extra distance to the hicas ecu in the boot or even the different processor used by hicas, my ac ecu also remains silent with no delays but i have only just discovered

the need for delays and have not tested for the aircon delays yet.

i read that plms have to send initialisation more than once sometimes they are possibly not using delays.

my hicas responds to hex ff ff e4 with 10 then i send d1 f0 hicas then streams the error codes FF020000 ff start byte, 02 number of data bytes following, 0000 error code bytes ie no errors when ignition was last turned off

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



  • Latest Posts

    • My guesstimate, with no real numbers to back it up, is it won't effect it greatly at all.its not a huge change in position, and I can't see the air flow changing from in turbulence that much based on distance, and what's in front of it. Johnny and Brad may have some more numbers to share from experience though.
    • Which solenoid? Why was it changed? Again, why was this done? ...well, these wear..but ultimately, why was it changed? Did you reset the idle voltage level after fitment? I'm just a tad confused ~ the flash code doesn't allude to these items being faulty, so in my mind the only reason to change these things, would be some drive-ability issue....and if that's the case, what was the problem? Those questions aside, check if the dropping resistor is OK ...should be 11~14 ohms (TCU doesn't throw a flash code for this) ~ also, these TCU designs have full time power (to keep fault code RAM alive), and I think that'll throw a logic code (as opposed to the 10 hardware codes), if that power is missing (or the ram has gone bad in the TCU, which you can check..but that's another story here perhaps).
    • Question for people who "know stuff" I am looking at doing the new intake like the one in the picture (the pictured is designed for the OEM TB and intake plenum), this design has the filter behind the front bar, but, the filter sits where the OEM duct heads into the front bar, and the standard aperture when the OEM ducting is removed allows the filter to pulled back out of the front bar into the engine bay for servicing, a simple blanking plate is used to seal the aperture behind the filter This will require a 45° silicone hose from the TB, like the alloy pipe that is currently there, to another 45° silicone hose to get a straight run to the aperture in the front bar Question: how will it effect the tune if I move the MAF about 100-150mm forward, the red is around where my MAF is currently, and the green would be where it would end up Like this This is the hole the filter goes through  Ends up like this LOL..Cheers    
    • Despite the level up question, actually I do know what that is....it is a pressure sender wire.  So check out around the oil filter for an oil pressure sender, or maybe fuel pressure near the filter or on the engine. Possibly but less likely coolant pressure sensor because they tend to be combined temp/pressure senders if you have one. Could also be brake pressure (in a brake line somewhere pre ABS) but maybe I'm the only one that has that on a skyline.
    • Pull codes via the self-diagnosis procedure. As far as I can tell this is just a sign of transmission issues but not a code unto itself.
×
×
  • Create New...