USB ADS Interface Working!

[2JZ E36]

The motivation to use USB is that I can use a modern 64-Bit OS and still access old ECUs. The difference between ADS and OBD is that it also uses L-Line, instead of only K-Line. On my free-ads interface I just wired the L-Line into the correct spot on the OBD2 plug, so I dont need the 20-pin adapter on the bench. For the car I just use an OBD to 20 pin adapter.

[MParallel]

The reasons are crystal clear. Just wondering about what exactly you use for a cable. Pic of the setup?

[2JZ E36]

Sorry for the late reply. This is what my setup looks like:




FkS4JZr.jpg

There is the original free-ads interface board inside there with a sub-9 to USB converter and an OBD2 to OBD1 adapter.

[Fireball1991]

Nice!
What kind of converter do you have? And one more thing, what programs do you use? I mean inpa 3.01 & ediabas 6.4.3 or else?

[Raku]

This solution do work but when replacing api32.dll it changes the ediabas version to 7.3.0 and making egs and dme not able to read. With real usb port everything working with ediabas version 6.4.7. Maybe this will work if the modified ediabas library in old version. Anyone has any solutions to get ads and dis to work with usb serial port device?

[2JZ E36]

Nice!
What kind of converter do you have? And one more thing, what programs do you use? I mean inpa 3.01 & ediabas 6.4.3 or else?

I have an FTDI Serial to USB adapter with EDIABAS 7.3.0 and INPA 5.06. But that doesnt mean that other versions dont work, I just havent tried others

This solution do work but when replacing api32.dll it changes the ediabas version to 7.3.0 and making egs and dme not able to read. With real usb port everything working with ediabas version 6.4.7. Maybe this will work if the modified ediabas library in old version. Anyone has any solutions to get ads and dis to work with usb serial port device?

You could try to use the old version with the github library and see if that works. I get a version mismatch on my setup for E36 clusters for example, but it works just fine. Might be different in your case...

[Raku]

Tried older versions too but all based off ediabas 7.3.0. i can read ihka on my e34 and every module on my e39 with that but i mostly wanted to get dis working so i can scan ecus on the m50 and m60 engines

[2JZ E36]

Tried older versions too but all based off ediabas 7.3.0. i can read ihka on my e34 and every module on my e39 with that but i mostly wanted to get dis working so i can scan ecus on the m50 and m60 engines

Can you connect to the gauge cluster in your E34 via USB ADS? I have a E34 High cluster on my bench, but I cannot connect to it. Not sure if its something with my setup or USB ADS does not work here.

[KyronXLK]

Hey guys, Interested in trying this out but I can't even seem to find any ADS interfaces! Maybe it's because I'm in the UK. Any Idea where to buy them these days?

[facom39]

HI. I've tried this dll without success at the moment with DDE2 (M51).
Looking on K/L line with a protocol analyser initialisation is ok at 5 baud. I can see the answer on Line K (0x55 ...) at 250baud/4ms per bit (?) but no ack ack from diag tool.
I'm usind a prolific USB/Serial and think the problem can be there.
Is a FTDI chip mandatory ?

[Fireball1991]

I have an FTDI Serial to USB adapter with EDIABAS 7.3.0 and INPA 5.06. But that doesnt mean that other versions dont work, I just havent tried others



You could try to use the old version with the github library and see if that works. I get a version mismatch on my setup for E36 clusters for example, but it works just fine. Might be different in your case...

Nice! glad to hear that. here's another question, how did you install the ediabas and inpa? I mean, in the installer wizard what did you choose? Ads or std:obd?
thanks a lot!

[2JZ E36]

I have updated my post with a new solution for 64-Bit machines! This actually works on E34 cluster I have on my bench which did not work with the USB solution.

[roundhouse]

Hello there! Thanks for such a great update for our oldies!

Now, I have a problem running DIS in x64 environment. I installed an x64 patched ADS driver, and ifhsrv32 now runs ok, without warning on DirectNT.sys But when I start the DIS, and trying to connect to my car, ifhsrv32 stops working and closes without any messages. In the system journal I found a message, that ifhsrv32 was closed because of faulty component, Ads32.dll.

So is there a workaround for the problem? Or maybe there's another server for DIS?

[hooutoo]

Looking for a bit of an assist here. I'm running a Dell d630 with a native rs232 port so I tried to implement solution #2 on post #1. I've copied DirectNT.sys (x64 version which is 12bytes in size) and ran bcdedit command. Rebooted, but when my Win7x64 pro tries to load it i get blue screened by DirectNT.sys (see pic). Of course, I have to go into safe mode and remove the it and all is well but no INPA.
20230116_092601.jpg

Any suggestions would be greatly appreciated!

[MParallel]

There was a specific problem witg certain Dell computers, but not sure if this applies to you. If you have RS232 port, you may go just native ADS (with a 32bit OS).

[Rusty 2800 E3]

On the GitHub download I can´t find a DirectNT.sys file
What am I missing?

[Nemtor]

hi does this work with bmw e36 m3 ? 1995?
where can i get BMW ADS Interface

in the UK?

[Fireball1991]

Hi there!
I have a quick question about inpa.
So i CAN diag my e36 cars but what about e34s? I have a 525tds and I can’t diag it, I can’t find M51D25 in the list. And also I have a 164E2 e36 1.6 touring, it is the same. Can’t find the right engine code in the list. Could anyone help me? Thanks a lot!