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

    • I had 3 counts over the last couple of weeks once where i got stranded at a jdm paint yard booking in some work. 2nd time was moving the car into the drive way for the inspection and the 3rd was during the inspection for the co2 leak test. Fix: 1st, car off for a hour and half disconnected battery 10mins 4th try car started 2nd, 5th try started 3rd, countless time starting disconnected battery dude was under the hood listening to the starting sequence fuel pump ect.   
    • This. As for your options - I suggest remote mounting the Nissan sensor further away on a length of steel tube. That tube to have a loop in it to handle vibration, etc etc. You will need to either put a tee and a bleed fitting near the sensor, or crack the fitting at the sensor to bleed it full of oil when you first set it up, otherwise you won't get the line filled. But this is a small problem. Just needs enough access to get it done.
    • The time is always correct. Only the date is wrong. It currently thinks it is January 19. Tomorrow it will say it is January 20. The date and time are ( should be ! ) retrieved from the GPS navigation system.
    • Buy yourself a set of easy outs. See if they will get a good bite in and unthread it.   Very very lucky the whole sender didn't let go while on the track and cost you a motor!
    • Well GTSBoy, prepare yourself further. I did a track day with 1/2 a day prep on Friday, inpromptu. The good news is that I got home, and didn't drive the car into a wall. Everything seemed mostly okay. The car was even a little faster than it was last time. I also got to get some good datalog data too. I also noticed a tiny bit of knock which was (luckily?) recorded. All I know is the knock sensors got recalibrated.... and are notorious for false knock. So I don't know if they are too sensitive, not sensitive enough... or some other third option. But I reduced timing anyway. It wasn't every pull through the session either. Think along the lines of -1 degree of timing for say, three instances while at the top of 4th in a 20 minute all-hot-lap session. Unfortunately at the end of session 2... I noticed a little oil. I borrowed some jack stands and a jack and took a look under there, but as is often the case, messing around with it kinda half cleaned it up, it was not conclusive where it was coming from. I decided to give it another go and see how it was. The amount of oil was maybe one/two small drops. I did another 20 minute session and car went well, and I was just starting to get into it and not be terrified of driving on track. I pulled over and checked in the pits and saw this: This is where I called it, packed up and went home as I live ~20 min from the track with a VERY VERY CLOSE EYE on Oil Pressure on the way home. The volume wasn't much but you never know. I checked it today when I had my own space/tools/time to find out what was going on, wanted to clean it up, run the car and see if any of the fittings from around the oil filter were causing it. I have like.. 5 fittings there, so I suspected one was (hopefully?) the culprit. It became immediately apparent as soon as I looked around more closely. 795d266d-a034-4b8c-89c9-d83860f5d00a.mp4       This is the R34 GTT oil sender connected via an adapter to an oil cooler block I have installed which runs AN lines to my cooler (and back). There's also an oil temp sensor on top.  Just after that video, I attempted to unthread the sensor to see if it's loose/worn and it disintegrated in my hand. So yes. I am glad I noticed that oil because it would appear that complete and utter catastrophic engine failure was about 1 second of engine runtime away. I did try to drill the fitting out, and only succeeded in drilling the middle hole much larger and now there's a... smooth hole in there with what looks like a damn sleeve still incredibly tight in there. Not really sure how to proceed from here. My options: 1) Find someone who can remove the stuck fitting, and use a steel adapter so it won't fatigue? (Female BSPT for the R34 sender to 1/8NPT male - HARD to find). IF it isn't possible to remove - Buy a new block ($320) and have someone tap a new 1/8NPT in the top of it ($????) and hope the steel adapter works better. 2) Buy a new block and give up on the OEM pressure sender for the dash entirely, and use the supplied 1/8 NPT for the oil temp sender. Having the oil pressure read 0 in the dash with the warning lamp will give me a lot of anxiety driving around. I do have the actual GM sensor/sender working, but it needs OBD2 as a gauge. If I'm datalogging I don't actually have a readout of what the gauge is currently displaying. 3) Other? Find a new location for the OEM sender? Though I don't know of anywhere that will work. I also don't know if a steel adapter is actually functionally smart here. It's clearly leveraged itself through vibration of the motor and snapped in half. This doesn't seem like a setup a smart person would replicate given the weight of the OEM sender. Still pretty happy being lucky for once and seeing this at the absolute last moment before bye bye motor in a big way, even if an adapter is apparently 6 weeks+ delivery and I have no way to free the current stuck/potentially destroyed threads in the current oil block.
×
×
  • Create New...