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

    • I did end up getting it sorted, as GTSBoy said, there was a corroded connection and wire that needed to be replaced. I ended up taking out the light assembly, giving everything a good clean and re-soldered the old joints, and it came out good.
    • Wow, thanks for your help guys 🙏. I really appreciate it. Thanks @Rezz, if i fail finding any new or used, full or partial set of original Stage carpets i will come back to you for sure 😉 Explenation is right there, i just missed it 🤦‍♂️. Thanks for pointing out. @soviet_merlin in the meantime, I received a reply from nengun, and i quote: "Thanks for your message and interest in Nengun. KG4900 is for the full set of floor mats, while KG4911 is only the Driver's Floor Mat. FR, RH means Front Right Hand Side. All the Full Set options are now discontinued. However, the Driver's Floor Mat options are still available according to the latest information available to us. We do not know what the differences would be, but if you only want the one mat, we can certainly see what we can find out for you". Interesting. It seems they still have some "new old stock" that Duncan mentioned 🤔. I wonder if they can provide any photos......And i also just realized that amayama have G4900 sets. I'm tempted too. 
    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
×
×
  • Create New...