Ecu Error Codes

[nicr4wks]

Wow, which software is that? Sounds like it must be CONSULT2 compatible to hook into the ancillary ECUs - unless its just OBD2?

Nissan Data Scan will enter the airbag in to diagnostic mode and read/clear error codes, at launch you can select between AT/SHICAS/AC/SRS etc then scan the bus for the device and connect, on my 33 I can bring up main and air bag. SHICAS will connect but the sensors between hicas and shicas must be different as I can't get readings.

conZult lists plain old HICAS support but I've only got the trial version and it isn't enabled

Also thres one for mac, ConSultan that will let you download fuel maps from your ECU and graphs them out, looks pretty fancy except my usb>serial wont work in osx!.

[Dohmar]

Nissan Data Scan will enter the airbag in to diagnostic mode and read/clear error codes, at launch you can select between AT/SHICAS/AC/SRS etc then scan the bus for the device and connect, on my 33 I can bring up main and air bag. SHICAS will connect but the sensors between hicas and shicas must be different as I can't get readings.

conZult lists plain old HICAS support but I've only got the trial version and it isn't enabled

DataScan doesnt connect to my SHICAS in the 32 GTR. Apparently the registers for initialization are changed. I was able to manually send commands to the ecu via a hex terminal, aka EF FF F0 and then gotten the OK from it....

Would love to try Conzult Z32 out - the author has confirmed it does work on R32 GTR Hicas but I'm not game to pay $500 just on a whim

-D

[jrm]

I've got a copy of test software (from the developer) of just the HICAS part of the Conzult software so I could test it on my R34 GTT, but it wouldn't work to my dismay... (wouldn't even initialise the SHICAS ECU)

[Dohmar]

I've got a copy of test software (from the developer) of just the HICAS part of the Conzult software so I could test it on my R34 GTT, but it wouldn't work to my dismay... (wouldn't even initialise the SHICAS ECU)

Any chance you can chuck that HICAS part to me? Would like to try it on the r32, esp since he said it'd work

-D

[nicr4wks]

And I'd like to try it on a 33 plz ^-^

So no one has ever been able to make the HICAS speak? Wonder if chucking some commands to it over a terminal might get something from it instead of relying on other peoples software, need to find and initialize it first tho....

[jrm]

I've written some custom code to try and talk to it, but I don't know what codes I should be sending. The S-HICAS codes that I've found on-line don't seem to work, and because it seems to be on the CONSULT2 vs CONSULT1 protocol, it almost 'feels' (from my testing) that you need to get the timing between commands a little more precise (CONSULT1 stuff on the EF ECU seem a lot more 'loose' in its acceptance of commands).

I'd love to get in touch with people messing about with trying to talk to the ECUs via CONSULT (I'm a sysadmin, netadmin and programmer), but trying to find people is a complete pain - and the people who have put in the effort don't seem to want to share their knowledge about (understandable really - i've spent hours and hours on playing with stuff already - it can be arduous work).

[nicr4wks]

systems and network admin here too

Was searching around today and found a couple docs of interest:

http://vacated.net/carstuff/Generic_Nissan...table_Ver_2.pdf

http://www.plmsdevelopments.com/images_ms/...nds_Issue_6.pdf

Could get fairly annoying needing the car on to test all this out..

Perhaps we should take this to a global forum for more input? I believe the creator of Nissan Data Scan hangs around the ACT forums. Problem being a lot of these guys sell their own software and don't want to give away the secrets!

[Luke_ENR34]

Just got back from Dohmars place and a quick search of the ecu, no error codes came up. Whos next?

Nick i sent u a pm

[nicr4wks]

What software was used and what was tried?

Make sure I'm not gonna go ahead and try the same thing dohmar did

[Dohmar]

I've written some custom code to try and talk to it, but I don't know what codes I should be sending. The S-HICAS codes that I've found on-line don't seem to work, and because it seems to be on the CONSULT2 vs CONSULT1 protocol, it almost 'feels' (from my testing) that you need to get the timing between commands a little more precise (CONSULT1 stuff on the EF ECU seem a lot more 'loose' in its acceptance of commands).

I'd love to get in touch with people messing about with trying to talk to the ECUs via CONSULT (I'm a sysadmin, netadmin and programmer), but trying to find people is a complete pain - and the people who have put in the effort don't seem to want to share their knowledge about (understandable really - i've spent hours and hours on playing with stuff already - it can be arduous work).

Linux Sysadmin/engineer here, but not a coder

I used a hexterm to send the hex init codes, the only problem is the registers for my particular hicas don't match the ones published on the PLMS site - and thats the hicas codes the dude who made datascan used...

hex codes enabled me to manually initialize the hicas control unit and then initiate data streaming, but I couldn't decipher any of it.

for lukes issue, I used ECUTalk. For some reason, Nissan Datascan wouldnt work and my main laptop with obd scantech and datascan is currently out of action (pending reinstall of os)

His ecu reported no error codes, and I connected to the main ECU (hex EF) so either the airbag light isnt controlled by a control unit, or its been ofloaded into the abs or hicas computers or some other function - no airbag in the r32 gtr so I'm not quite familiar about where this would be

-D

[nicr4wks]

Airbag errors wont show up in the main ECU I've found, I'll give datascan a go as it's successfully been able to read bag codes on my 33 hopefully the 34 isn't too different.

Did you happen to give any of the reset procedures a go? There's a few guides floating around the forums where you turn your key and push the door switch several times which works for some people.

The datascan software states SHICAS which I'm guessing might have a different instruction set or initialisation string to HICAS, would be great to get some real time info displayed.

[Dohmar]

Airbag errors wont show up in the main ECU I've found, I'll give datascan a go as it's successfully been able to read bag codes on my 33 hopefully the 34 isn't too different.

Did you happen to give any of the reset procedures a go? There's a few guides floating around the forums where you turn your key and push the door switch several times which works for some people.

The datascan software states SHICAS which I'm guessing might have a different instruction set or initialisation string to HICAS, would be great to get some real time info displayed.

yeah but the shit thing is, nissan changed the hicas from hydraulic to electric from the r32 to r33, but they marketed both of them as being 'super hicas'.

'hicas' itself is the first edition found on JDM r31's

-D

[nicr4wks]

Heres my air bag init from NDS, not sure of the read or clear code commands as they're behind the gui.

Send FF FF DC (100ms pause between commands)

Receives 00 00 23

^ Works on my 33

And the SHICAS

SENDING: FF

DELAYING: 100 mS

SENDING: FF

DELAYING: 100 mS

SENDING: E4

DELAYING: 100 mS

RECEIVED: 00 00 1B

INITIALIZE OK ...

After that I believe it starts probing for sensors and fails:

SENDING: 5A

DELAYING: 25 mS

RECEIVED: A5

SENDING: 00

DELAYING: 25 mS

RECEIVED: FE

REGISTER 00 ... INVALID

SENDING: 30 (STOP)

RECEIVED: CF

This goes through 00 to 06.

So assuming E4 is the actual HICAS system we just need to find the correct sensor addresses?

Edit:: looking at the commands pdf linked earlier, "9F stream all sensors" might give an interesting output, ill give it a shot when its not so dark and cold >.>

And when looking for 01 on the hicas ecu it returns valid, this is only the speed sensor though.

Edited October 14, 2009 by nicr4wks

[Dohmar]

Heres my air bag init from NDS, not sure of the read or clear code commands as they're behind the gui.

So assuming E4 is the actual HICAS system we just need to find the correct sensor addresses?

Edit:: looking at the commands pdf linked earlier, "9F stream all sensors" might give an interesting output, ill give it a shot when its not so dark and cold >.>

And when looking for 01 on the hicas ecu it returns valid, this is only the speed sensor though.

OK since we're documenting this, I might have to dl a hexterm and give some stuff a go

Ben - R32 GTR 1989

Nick - R33 GTS-T S2 (year?)

Jenna- R34 GT-T (year?)

No doubt we'll get different values in some aspects, but its worth being thorough...

Once I got my laptop sorted I'll chuck OBD scantech on and fudge around with it

Cant recall what hexterm I used, it was suggested to me by the cat that makes the pda nisscan software

Anyone else got a consult cable and feel like doing some snooping?

-D

[NewKleer]

if the cat suggested it then it was probably lookrs232

[jrm]

OK since we're documenting this, I might have to dl a hexterm and give some stuff a go

Ben - R32 GTR 1989

Nick - R33 GTS-T S2 (year?)

Jenna- R34 GT-T (year?)

Mine is a 1998 R34 GT-T sedan in manual.

No doubt we'll get different values in some aspects, but its worth being thorough...

Once I got my laptop sorted I'll chuck OBD scantech on and fudge around with it

Cant recall what hexterm I used, it was suggested to me by the cat that makes the pda nisscan software

I did a tonne of testing recently with my car when I was playing around with writing some code to put on my CarPC, referencing various PLMS documents and trying to figure various timings out. I had no real issues talking to the primary ECU (EF) but subsidiary ECUs did seem to require more accurate timing (I could get results from a simple hexterm with EF, but with others it almost felt like it wanted it more accurate/timed out rather than a steady stream as from a program...). I did get the other ECUs to talk (sometimes I had more than one responding at once, that could get confusing - I guess it must be a central bus type arrangement for all of the ECUs via the CONSULT port). Anyways I gave up after a few hours of messing about because I'd pretty much killed my battery (I was using a notebook, and RDP'd into it via wireless) and I just didn't have the right hex codes to get anything meaningful (and nothing seemed to line up with the PLMS S-HICAS information).

I'd really like to get more into playing with this stuff, but I honestly don't know where to turn or who to talk to (or if they'd even talk to me!)

[NewKleer]

does anyone have a wiring diagram for the hicas unit consult lines? (or know where in the r32 engine manual it is?

[Dohmar]

does anyone have a wiring diagram for the hicas unit consult lines? (or know where in the r32 engine manual it is?

http://www.plmsdevelopments.com/diy_consult.htm

-D

[NewKleer]

sorry, i should have been more specific - does anyone have the pinout/wiring diagram specifying which pins on the hicas unit (say R32 GTR) are the consult lines

[nicr4wks]

Nick - R33 GTS-T S2 (year?)

Cant recall what hexterm I used, it was suggested to me by the cat that makes the pda nisscan software

1996

I had a go with a program called hexterm but it wasn't very fun to use.

does anyone have a wiring diagram for the hicas unit consult lines? (or know where in the r32 engine manual it is?

Wouldn't hold my breath on that but it would be nice

Luke managed to clear his error today via one of the processes on the forums, plugged in anyway and managed to connect to his airbag and read all ok.

Found another ECU on my bus tonight, init FF FF E7 not sure what it is, could be a/c :S

Does anyone have a decent term for manually sending commands? I've got 'Free Serial Port Monitor' which is useful for logging what other programs are talking over serial, still stumped getting anything out of HICAS.