Jump to content
SAU Community

Recommended Posts

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

Would it be a factor of cable distance, or perhaps of the ecu relaying the information to the respective control units?

I presume that these all use the ecu consult port, right?

-->So apart from the fact that I want to intercept the G-sensors for the attesa, and intercept the BOSS sensor and directly control the solenoids for hicas, I can talk to the control units.... If only there was documentation on the 'active tests' and what they did...

cool.

  • Replies 114
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

there arent any active tests for hicas i dont think

you can get steering angle, direction, and a few other random things. no g-sensor i dont think

wouldnt be cable distance, electronic signals travel at speed of light. could be it needs to relay data and whatnot.

Edited by NewKleer
sounds good ugboot - have u tried scantech nissan (which supposedly supports the hicas/at/ac ecus) to see if they work on yours, or do they send it too fast also?

hi NewKleer

can u post the scantech nissan link if it is a demo or free

thanx

keith

http://techdiag.co.uk/obdscantech/ScanTechNissan.zip

should be good enough to test it with, however it has some horrible "give us money" screen that pops up every 5 seconds :P

not sure if they disabled the hicas/at/ac sections of it or not

Would it be a factor of cable distance, or perhaps of the ecu relaying the information to the respective control units?

I presume that these all use the ecu consult port, right?

-->So apart from the fact that I want to intercept the G-sensors for the attesa, and intercept the BOSS sensor and directly control the solenoids for hicas, I can talk to the control units.... If only there was documentation on the 'active tests' and what they did...

cool.

hi ebola

if u look at the varous wiring drawings needed to get the big picture all of the ecu's are connected in parrallel on the ddl bus this is why they respond to a different id byte ,engine hex ef, hicas e4, aircon hmm forgot that one but a4 i think, Also you can only address one at one time, they are all ecu's separately and linked by the ddl, I read that the eccu sends the rpm to the hicas ecu over the bus !

btw the attessa is not connected to the ddl so the attesa g sensors are not accessible

Keith

  • 2 weeks later...

planning to get a pocket pc version of ecu talk out by the end of the weekend, cause if i dont do it now then it might not be till the end of the year :domokun:

hopefully will have fault codes, gauges (and maybe bar graphs)

planning to get a pocket pc version of ecu talk out by the end of the weekend, cause if i dont do it now then it might not be till the end of the year :)

hopefully will have fault codes, gauges (and maybe bar graphs)

hi newkleer

hey it would be nice ifit was programmed in java so it would run on my old palmIIIe that has j2me support and a rs232 port that plugs into the plms cable.

hi newkleer

hey it would be nice ifit was programmed in java so it would run on my old palmIIIe that has j2me support and a rs232 port that plugs into the plms cable.

id fall asleep after 10 minutes if i did it in java. when you can get a second hand pocket pc for around $100, not much use trying to do it in java. a palm that old (with like 8mb ram/16mhz cpu) would struggle to run a hello world program :P

planning to get a pocket pc version of ecu talk out by the end of the weekend, cause if i dont do it now then it might not be till the end of the year :starwars:

hopefully will have fault codes, gauges (and maybe bar graphs)

and here it is (last post): http://www.skylinesaustralia.com/forums/in...howtopic=107201

now back to work on the consult lcd

id fall asleep after 10 minutes if i did it in java. when you can get a second hand pocket pc for around $100, not much use trying to do it in java. a palm that old (with like 8mb ram/16mhz cpu) would struggle to run a hello world program :(

yep the palmIII is a bit pov lol, wot pocket pc have u seen for around $100 that will run your sw. :)

cheers Keith

i picked up my jornada 568 for $150 second hand. theyre on ebay but theyre a bit more than that. having only used that, i cant recommend any others - but it runs fine on mine, and probably would on something with half the specs of it

eg these might be ok:

http://cgi.ebay.com.au/HP-Hewlett-Packard-...1QQcmdZViewItem

http://cgi.ebay.com.au/hp-jornada-540-ipaq...1QQcmdZViewItem

good thing about the older pda's is they would more often come with a serial sync cable than the newer ones - so then all you need is the male-male null modem adaptor (assuming it works like my 568 does)

as more people use it on their pda's hopefully i can get some feedback on which it works well with. you probably only need about <10mb ram and i think it takes less than 1mb of rom space (more if u use logging). all that will happen on a really slow cpu is that it just wont update as often.

i should check out mine again and see how many times the gauges update themselves per second, as thats probably a good gauge of speed

Edited by NewKleer
i picked up my jornada 568 for $150 second hand. theyre on ebay but theyre a bit more than that. having only used that, i cant recommend any others - but it runs fine on mine, and probably would on something with half the specs of it

Thanks newkleer. After searching through eBay, it seems the goin rate for 568's is in the range $100 to $170 with a mean around $130 nowdays. Are there any other models in the same price bracket worth looking at? I'm a PDA n00b and don't really know what would be suitable for what you have in mind.

Thanks

if i was looking for one, id check out these:

http://cgi.ebay.com.au/HP-Hewlett-Packard-...1QQcmdZViewItem

http://cgi.ebay.com.au/HP-Jornada-548-Hand...1QQcmdZViewItem

i found this site:

http://www.pocketgpsworld.com/markincar.php

appears that he's hooking up a serial gps receiver to his jornada 548 pda with null modem adaptor (http://www.expansys.com.au/product.asp?code=3011213). jornada 548 is pocket pc 2000, which actually supports .net compact framework (i thought it was only ppc 2002+). its possible there may be issues with it, i really cant say either way until someone with one says either way

its still a gamble, especially if your getting it for this sole purpose, you might be able to pick up one of those for say 60-80$.

btw, probably best to keep specific things/questions about my software in this thread: http://www.skylinesaustralia.com/forums/in...howtopic=107201 (and more general stuff here. made the seperate thread so this one didnt get inundated)

  • 2 weeks later...

Peter the PCB works a treat, thanks again! Now, I'm having trouble with calumsult as I can't seem to configure it for two of most sensors and can't find anywhere the AFM voltage is displayed (which is the main reason I bought the kit).

Is there any other software that might be better suited please? Perhaps some 300ZX software?

And I grabbed a hp pda via eBay, cheers.

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