Jump to content
SAU Community

Recommended Posts

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

  • Replies 42
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

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

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)

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

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

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

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!

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

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.

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

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

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

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.

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

    • Have a look at that (shitty) pic I posted. You can see AN -4 braided line coming to a -4 to 1/8 BSPT adapter, into a 1/8 BSPT T piece. The Haltech pressure sender is screwed into the long arm of the sender and factory sender (pre your pic) into the T side. You can also see the cable tie holding the whole contraption in place. Is it better than mounting the sender direct to your engine fitting......yes because it removes that vibration as the engine revs out 50 times every lap and that factory sender is pretty big. Is it necessary for you......well I've got no idea, I just don't like something important failing twice so over-engineer it to the moon!
    • Yup. You can get creative and make a sort of "bracket" with cable ties. Put 2 around the sender with a third passing underneath them strapped down against the sender. Then that third one is able to be passed through some hole at right angles to the orientation of the sender. Or some variation on the theme. Yes.... ummm, with caveats? I mean, the sender is BSP and you would likely have AN stuff on the hose, so yes, there would be the adapter you mention. But the block end will either be 1/8 NPT if that thread is still OK in there, or you can drill and tap it out to 1/4 BSP or NPT and use appropriate adapter there. As it stands, your mention of 1/8 BSPT male seems... wrong for the 1/8 NPT female it has to go into. The hose will be better, because even with the bush, the mass of the sender will be "hanging" off a hard threaded connection and will add some stress/strain to that. It might fail in the future. The hose eliminates almost all such risk - but adds in several more threaded connections to leak from! It really should be tapered, but it looks very long in that photo with no taper visible. If you have it in hand you should be able to see if it tapered or not. There technically is no possibility of a mechanical seal with a parallel male in a parallel female, so it is hard to believe that it is parallel male, but weirder things have happened. Maybe it's meant to seat on some surface when screwed in on the original installation? Anyway, at that thread size, parallel in parallel, with tape and goop, will seal just fine.
    • How do you propose I cable tie this: To something securely? Is it really just a case of finding a couple of holes and ziptying it there so it never goes flying or starts dangling around, more or less? Then run a 1/8 BSP Female to [hose adapter of choice?/AN?] and then the opposing fitting at the bush-into-oil-block end? being the hose-into-realistically likely a 1/8 BSPT male) Is this going to provide any real benefit over using a stainless/steel 1/4 to 1/8 BSPT reducing bush? I am making the assumption the OEM sender is BSPT not BSPP/BSP
    • I fashioned a ramp out of a couple of pieces of 140x35 lumber, to get the bumper up slightly, and then one of these is what I use
    • I wouldn't worry about dissimilar metal corrosion, should you just buy/make a steel replacement. There will be thread tape and sealant compound between the metals. The few little spots where they touch each other will be deep inside the joint, unable to get wet. And the alloy block is much much larger than a small steel fitting, so there is plenty of "sacrificial" capacity there. Any bush you put in there will be dissimilar anyway. Either steel or brass. Maybe stainless. All of them are different to the other parts in the chain. But what I said above still applies.
×
×
  • Create New...