legacycentral bbs

We're not on the same page. This thread isn't about that scan tool. Maybe you should ask your question in the thread about that scan tool.

I'm having similar problems as IronMonkeyL255. My notebook is an IBM T23 1.13GHz. I was using a Dell Latitude from work with version 0.5 successfully, but moved and had to give the notebook back. I bought this T23 expecting it to work, but was surprised to find neither version 0.5 or 0.6 works. I have successfully shorted the send/receive leads on my cable (using a paperclip) to get 00:ff:ff. When hooked up to the ECU it seems to sit and wait polling for the ECU ROM ID. I wasn't even getting the shorted 00:ff:ff until I switched the BIOS ports/IRQ as IronMonkeyL255 mentioned....

Any leads on these issues?

Cheers
-Jeff

I could not get version 0.6 to talk to my 1990 EJ22 but after reading this thread I saw the comments about trying version 0.5.

So I did and it works fine. Version 0.6 hangs at the read ECU revision screen (as if it wasn't hooked up).

Using an old Toshiba 4100 laptop and Paralled cable.

Just thought you would like to know.

Paul C.

Paralled ? Oops, sorry, typo.

"Parallel port cable"

+1 for new version no worky on a 90 L but v.05 works fine. I tested with both serial and parallel and just hung on the reading ROM ID.

finally got it working, sweet. will report data

Alright, finally got my connector made. Unfortunately since I'm using a old ass laptop, the battery is dead so I can't drive around and monitor values. I did drive around town to get the car warmed up, then sat in the driveway idling.

Tried the 0.06 version but it would hang on reading my ROM (72.36.22). The 0.05 one worked fine though. Since I'm unfamiliar with the various ranges of the parameters, would someone look them over and give some feedback?

Idling:
RPM 625-700
Coolant 192-203F
Ignition Timing 15
Airflow 1.04-0.98v
Load 39-42
Throttle PS 4.68
Injector PW 2.4-2.6ms
IAC duty 0.365
O2 0.04-0.8v
Fuel trim -1.56-2.56%
Timing correction 0
Boost control 1.56%
Bar pressure 663.75 torr
Boost/Vac -18 inHg


Reving: & holding to around 3-3.5K
RPM
Coolant
Ignition Timing 47
Airflow 1.9v
Load
Throttle PS 4.2
Injector PW 2.1-2.3ms
IAC duty 32.50%
O2
Fuel trim 3.12%
Timing correction
Boost control 93%
Bar pressure
Boost/Vac


1) Is the O2 sensor ok? Seems kind of low, or would that change more while driving?

2) The barometric pressure was reading at 663.75 torr, which is 12.82 PSI. I'm at ~4300 ft. Since I'm don't have a FCD installed, that basically means I'm not going to be getting any boost up here?

3) How are the other values?

Hi all,
Great program you've put together, I have a MY97 Forester ST B with the Jecs Unisia 22610 AD410 ECU. Trying the turbo series ROMIDs but no luck reading data from ECU as yet. Anyone got the ROMID and parameters that could get me reading?
Thanks again.

Subaru's part catalog says 22610 AD410 is not a valid part #.....

Sorry, typo here meant 22611 AD410

still nothing...here's what I'm using to check

https://www.subarugenuineparts.com/oe_parts_cat.html

Any workarounds to use with a laptop with no serial or parallel ports, like a USB-to-serial converter?

So I went through the process of wiring my car to use this tool. I didnt really make an adapter, although I did goto to radioshack and bought a 25pin connector. I just ran some wire to the diagnostic port, and used some crimp on connectors and placed them into pin 2,3 & 9... then ran the wiring behind my stereo console and installed the 25pin connector in my glovebox. I have a printer extension cable I then connect to the glovebox and run to my laptop, everything looks slick and out of the way...

So that was the hard part (so i thought). I copied the .com file to my laptop, setup a boot menu where I can bypass Win98 and have to load B10Scan in DOS Mode, and fired away. Nothing, it hung at the "reading ROM ID" screen. As agrivated as I was, i checked my LPT settings in the bios, and played with everything. I couldnt get anything to work.

So i called Ryan and asked if I could come over and use his adapter he made (which we have used in the past and has been verified to work). I get to his house, plug his adapter into my laptop and still nothing. So I deem the laptop to be defective and shrug it off. 10min later his adapter fell apart and we were unsure if it was even working properly when we tried. So i came home today and used my multimeter as a continuity tester. I verified I had continuity from the diagnostic cable to the end of the printer extension (the very end that plugs directly into the laptop) and everything tested okay. No reason the wiring should be faulty.

I read every page of this thread, and found others were having problems with version 0.06 and sucess with 0.05. So I downloaded v.0.05 and ran it and BINGO IT WORKED!

So, im not sure whatsup... but 0.06 doesnt seem to communicate with my ECU. I read the release notes and i dont think there is anything in 0.06 that i really need that 0.05 doesnt have. Im trying to use this tool to help diagnose my poor fuel mileage.

Just thought I'd let it be known.
-Brian

Hi!
I got mine legacy turbo european. Tried to connect this tool in both 05 and 06 versions. It sees the ECU, but there's the message

Rom ID 72.34.a2. (unrecognized)

ECu is
G8

22611 AB010
A18-000 RFI

japan electronic counting systems co ltd

Can you vikash please assign mine ecu at your program?

vikash hasn't been on here in a long time

Anybody can enlighten me what to do?
I realy need to monitor my ecu but cant find anything usable. obdII is easyer in that thing.

Is that riht that i got another type of ECu than USA legacys do?

Yes you have a different ECU then the USA Legacies.

Wheres the difference in harasteristics? Not in that its JECS or hitachi. Have us legaciec more power? Mine was 200 when young

The overseas models had completely different engines, so the air fuel ratio curves, timing, etc are going to be different.

Yes the overseas models have more power. The stock power level on the USA turbo legacies was 165 hp.

Anyone have an idea why some laptops don't completely work with the b10scan?

For example, I borrowed a Gateway Solo 5300 and it could most often read my rom id, but thats it. Very rarely would it be able to read any other parameters. Didn't matter if I changed the BIOS between ECP, EPP, or bi-directional. Same results between 0.5 and 0.6. I tried two Solo 5300's.

When I tried a Gateway Solo 2500, it worked just fine. Used the same bootdisk and cable for both tests. Unfortunately the 2500's battery is dead so I can't drive around with it, while the 5300's battery is great .

can you read CELs with this?

Nope, just ecu info. Have to use the blink codes for CELs.

I just tried to get this going with ver 5. It finds a romid but then tells me its unrecognized. I have a 93 leg turbo. Anyone have any idea what could be wrong?

What ROM ID does it say you have?