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?

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
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

    • Yeah i have R34 with factory small box and now RB25DET NEO swapoed and iam planning to upgrade to big box.  So i would be good as long as i do not change diff? 
    • Based off what you’ve said here, I think I’ve figured out a good bit of what I’ve done wrong -  So on the line going from the PCV valve to carbon canister, there’s a T joint that is pretty much right next to that lower port - I hadn’t noticed that the hose in the diagram was curved to attach onto the carb, so I was putting that line for the lower port onto the PCV line / carbon canister line instead. I’m going to have a flick through the manual again tomorrow and should hopefully find a diagram that’ll show me where that T joint should be connected to. Timing also 100% needs to be sorted out as well, should be able to tackle that tomorrow as well. Definitely feel like I should be on the right track now though. 
    • The screw is for idle (pilot circuit) mixture adjustment. Else, I'm confused ~ the diagram shows 2 carby ports, and the intake manifold port, but you're suggesting the "2nd port on the back of the carb that isn’t mentioned in the diagrams" ...yet, both carby ports are shown...que?... ...in any event, that port should be connected, but if not (like it is now), it's unlikely to cause a backfire out the carby (it would introduce false air and give you a fast/lean idle) ...sounds more like timing issues/spark plug wire routing responsible for the backfiring.    
    • That's fair, I can see both points. I get enthusiastic when I see the FS section has a new post and want to see what interesting thing someone is selling. Then I get deflated it's a bump of a 10 year old post. Ha ha
×
×
  • Create New...