Hi,

as the title says which scan tool would you recommend or what's your experience with x or y model, pros ans cons, etc...

The car wiring is OBDIIb(USDM) and using a conversion harness going to a OBDIIa JDM ECU... and I'm looking to read JOBD codes off a p73-013 JDM ECU.

functions I'm interested in are: read all types of codes(CEL,OBD,ABS,SRS,Immo,etc...), erase codes, definitions, live monitoring.

thanks in advance!

 

The JDM ecus ending with 0xx are not US OBDII compliant meaning an OBDII code reader will not connect with it. To read codes you will have to jump the SCS connector and count the CEL flashes.

 

^ this no matter what high end scanner sold in us you buy will Not read that ecu. i own 3 high end snap on scanners/labscope or combo and i never had one connect and read jdm ecu

 

you're right, that I knew already.

What I'm mainly interested in is not just pulling the codes with the paperclip trick but rather being able to monitor data in realtime, take snapshots, erase codes without having to disconnect anything and being able to read pending or soft codes.

 

tell me about it, I went to see my friend at the Acura dealer to try to read the ECU and their Honda Diagnostic Tablet wasn't even able to communicate with the ECU.
IIRC I read about someone down in OH who had done it before with the system at the Honda dealer but I can't seem to find that tread anymore.

Maybe they had a different tool or update installed that enabled them to do it, I don't know.

Since I have no experience operating their new system and he was doing me a favour, I didn't say anything, maybe he had to select a particular option I didn't know about? anybody know?

Someone I spoke with suggested I give it a try with the old GNA600 but they still are pretty expensive just for the sake of trying if it doesn't work in the end...

 

I searched and I searched, maybe not in the right places IDK, but lately I did spend quite alot of time reading and trying to gather as much info as possible myself on the subject not only here but on several sites and msg boards (not only for Honda's) and there has to be a way as there is about nothing that can't be done or un-hackeable these days.

I can't understand so many posts coming to the same results...other than the vast majority of them are dated and mainstream scanners availability have come a long way since then and prices have dropped ridiculously too...and I know that just recently some had (partial)succes with smartphone apps and bluetooth OBDII connectors with other car makes so that tell me that it's not impossible.


wtf do they read ECU's with in Japan??? saw some JDM ITR front cuts that have an OBDII connector today...must be for a reason.

has anybody tried a JOBD reader/scan tool yet?

 

you would most likely have to find a HIGH end import shop that deals with direct import cars. they might have invested in a tool from japan or asia that can read their stuff.

 

also depending on what and how your trying to view live data, you could always try a labscope (oscilloscope). the 2 i have is a 4 channel and a 2 channel. so basically with a 4 channel i can hook up to all 4 inj, or all for ing cable, or anything i want and lay over top one another, i can also do freeze data, change time frame to get better look at fire line of ign, also do the same with inj and see if i have any oddities with 1 inj vs the rest. they can also check cam/crank sensors, and a VAST aray of other sensors.

 

I will definitely try to find one if I can't find any other solution...but the key word here is ''HIGH end'' as you mentionned or I might try to buy one from asia off ebay or whatever as a last resource and keep my fingers crossed...

 

Why not get a USDM PCM?

 

I do have one already but I need to be able to read the jdm ecu that's currently connected to the car.

 

Why? The USDM ecu will tell you much more info then you need, only problem is connecting it to a JDM engine which is lacking a few sensors. CKF, VTEC press, secondary o2 to name a few.

 

maybe I'm misinterpreting your comment, but well correct me if I'm wrong, but I always thought that trouble codes were stored in the ECU, not anywhere else like on a separate chip or module...is it not the case?

Unless I'm wrong with the above statement, I don't see how I would be able dig out some soft codes(with the USDM ECU) kept on record and related to some intermittent problems that happened while the JDM ECU was plugged on the car. I need to pull these codes, assuming that there may be some in order to hopefully better diagnose the issue.

Even, if I plug back the USDM ECU, you never know when or if the problem will show up again. I don't want to risk damaging anything by letting it go for too long and if the problem is caused by the said JDM ECU, I need to know too for sure so I can take appropriate action.