USB ADS Interface Working!

[2JZ E36]

Hi,
I figured out two ways to make ADS interfaces work on modern machines:

1. USB Solution with EdiabasLib
EdiabasLib (Link (https://github.com/uholeschak/ediabaslib)) is a from scratch reimplementation for EDIABAS. I has a wrapper for the api32.dll, so it can simply be replaced. I have tested this with the a free-ADS interface, an RS232 to USB FTDI Serial adapter with INPA on an E36 cluster and it works as it should. It does not work on an E34 cluster however, use Solution #2 if your ecu does not work with this method either.

How to install:

Click on the link and go to releases on the top, download the binaries zip
Go into C:/EDIABAS/bin and create a backup of the api32.dll
Go into the EdiabasLibConfigTool and copy the contents of the API32 folder into the bin folder
Open the EdiasbasLib.config file
Uncomment (Remove <!-- and -->) the first block
Change the interface to <add key="Interface" value="ADS"/>
Change <add key="AdsComPort" value="yourCOMPort"/> to whatever port your adapter uses
Done!

The new dll does not use any of the default EDIABAS config files. To go back, simply rename the new api32.dll and use the old backup dll.

I have tested this with Tool32 and INPA successfully. I have tried to code it with NCSExpert 4.0.1 but it throws an error that the VIN is incorrect. I have found that for E36 clusters, I have to remove the CAN cluster from E36SGFAM.DAT to make it work. No idea why this is necessary, but I can recode the cluster successfully.

The disadvantage with this method is that while E36 clusters are accessible (which arent with OBD) I cannot connect to an E34 cluster with this method. I think this has to do with timing problems, the ADS driver is driving the pins directly (like an Arduino), which is why the DirectNT driver is necessary to allow this. So while some ecus dont seem to care, some others do.

Software Installation: EDIABAS 7.3.0 and INPA 5.06 on Win 10 64-Bit.

2. 64-Bit Solution
This solution still requires a real RS232 port, but it allows to use an ADS interface on a 64-Bit machine! I have recompiled the driver for 64-Bit to make this work, the original driver source was actually created in 1997 by the german computer magazine ct. The source code can still be found on the internet. I used a 64-Bit alternative called GiveIO to recompile a working 64-Bit kernel driver.
The original ads code is fixed to COM1 and a specific hardware address. Jarda has published a utility in a blog post (Link (http://blog.jaroslavklima.com/2011/04/make-ads-interface-work-with-pcmcia.html)) to change them, which is often required on modern systems. The source and binaries (Release tab) for the 64 Bit driver are on GitHub: Link (https://github.com/GTO2013/DirectNT64). I also included Jarda's utility in the download.
There is still a problem however: EDIABAS 7.3.0 does not support ADS. Older Ediabas versions like 6.4.3 do, but the included INPA version 3.01 does not run on 64-Bit systems. So you need to mix EDIABAS 6.4.3 with INPA 5.06. Another hurdle is that windows requires drivers to be signed, which you need certificates for. Since I dont have these, you will have to tell Windows to ignore it.

How to install:


Install the old BMW toolset with EDIABAS 6.4.3 first. Make a copy (rename) of the EDIABAS installation folder and then delete the rest.
Install the new BMW toolset with EDIABAS 7.3.0
Delete the new EDIABAS folder and use the old EDIABAS version
Click on the link and go to releases on the top, download the binaries zip
Paste the DirectNT.sys driver in Windows/System32/drivers
Open your RS232 port in the device manager and look under resouces. Note down the E/A region start, mine was EFC8 for example.
Open Jarda's utility (included in the github download) and patch the ADS driver with the new E/A region (and COM port if you like)
Tell Windows to ignore unsigned drivers: Open a cmd with admin privileges and enter bcdedit.exe /set nointegritychecks on
Reboot. It should work now! You can open a cmd and type sc query directnt to see if its running. You should see the two black dots and be able to connect.


If somebody knows how to sign the driver please let me know. I dont have much experience with kernel driver programming, use at your own risk! The only known issue I have found is that INPA sometimes freezes when you tab out and in again, but I can live with it.

[FAL]

...even though I select only one ECU to code, it tries to get the ZCS from all ecus.NCS doesn't try and read the ZCS from every ECU, just a select few. If you open the file E36ZST.000 with Notepad++ (or something similar), you'll see a list of the ECUs and either a 0 or a 1 next to them. Anything marked with a 1, holds the ZCS in its memory.

[2JZ E36]

NCS doesn't try and read the ZCS from every ECU, just a select few. If you open the file E36ZST.000 with Notepad++ (or something similar), you'll see a list of the ECUs and either a 0 or a 1 next to them. Anything marked with a 1, holds the ZCS in its memory.

You are correct, what I meant is that it tries to get the ZCS from every ECU on that list, even though you only chose one. I have experimented more with this and it doesnt seem to be related to the replaced dll at all. I have tried the new dll on an old XP installation with NCS 3.x and it works perfectly fine. So the error is only related to NCS 4.1, not the new dll. After I typed in the ZCS by hand in NCS 4.1 it works just like it should. This is only a problem on older C25 clusters (and probably older ECUs in general), on newer Can Bus clusters it works on 4.1. On the older cluster NCS 4.1 complains that the VIN is incorrect, so there seems to be some differences in how NCS 4.1 validates the VIN compared to NCS 3.x ...?

You can see how it tried to pull the ZCS from the EWS and CAN KMB unit, even though I selected the standard KMB only:
https://i.imgur.com/Ch2JLO2.png

[2JZ E36]

Okay, I found a workaround: I removed the CAN Cluster from E36SGFAM.DAT and now the older clusters work too! The only small error that comes up now is that NCS throws an error after coding when the ecu resets that it cant connect (duh). But the coding works and sticks. So everything works now! USB ADS on Win10 64-Bit :)

[MParallel]

That is pretty amazing.

For years I have tried different things, now I finally have an ultraportable MicroPC with serial port, and now there is a USB solution. Lol.

[MParallel]

Haven't tried on the car yet, but starting INPA, does not start Ediabas anymore. Is hat corretc?

And would this work with a usb-to-obd-to-20pin cabe?

[2JZ E36]

Haven't tried on the car yet, but starting INPA, does not start Ediabas anymore. Is hat corretc?

Yes, thats correct. The VBATT and IGN dots dont work anymore, but you should be able to connect.



And would this work with a usb-to-obd-to-20pin cabe?


I dont think such a cable will work for ADS, but you can try :D

[MParallel]

So what cable do you use if it’s not a serial ads cable?

[2JZ E36]

I use an FTDI USB to RS232 cable to the free ADS Interface. With obd cable you mean the k line cables with an obd port right? I have tried a chinese one without success...

[pumpkin eater]

I use an FTDI USB to RS232 cable to the free ADS Interface. With obd cable you mean the k line cables with an obd port right? I have tried a chinese one without success...

Are you talking about the Chinese one from InnovOBD Technology (their online shop is called one-stop or something)?

[MParallel]

I use an FTDI USB to RS232 cable to the free ADS Interface. With obd cable you mean the k line cables with an obd port right? I have tried a chinese one without success...

Ah got it.

Waiting for my TinyADS interface as we speak.

Still hoping to get the serial working, as the whole point is no extra adapter cables.

I must be close as some ads only modules do communicate.

[2JZ E36]

Are you talking about the Chinese one from InnovOBD Technology (their online shop is called one-stop or something)?

I dont know the brand sorry. Got it off eBay years ago, but its not the one you mentioned.


Ah got it.

Waiting for my TinyADS interface as we speak.

Still hoping to get the serial working, as the whole point is no extra adapter cables.

I must be close as some ads only modules do communicate.

What cable are you using? Some modules or all modules?

[MParallel]

Using Gert’s ADS cable, switchable to OBD and service reset. Loaned from a friend.

Should read all modules in ADS mode, which it does on the native installed 32 bit OS, but running it in VM WinXP SP3 (because my other laptop is uefi64 and can’t install a native 32bit OS (or I don’t know, bios has a Legacy boot option, but doesn’t see my bootable usb/sd cars).

So on both, running Win XP in VM, ADS, two black dots in Inpa. Can read remote controle module, can read gauge cluster (both ads only) but on the DME or ZKE it can’t communicate.

So something with the serial port connection to the VM is acting funny.

[2JZ E36]

Using Gert’s ADS cable, switchable to OBD and service reset. Loaned from a friend.

Should read all modules in ADS mode, which it does on the native installed 32 bit OS, but running it in VM WinXP SP3 (because my other laptop is uefi64 and can’t install a native 32bit OS (or I don’t know, bios has a Legacy boot option, but doesn’t see my bootable usb/sd cars).

So on both, running Win XP in VM, ADS, two black dots in Inpa. Can read remote controle module, can read gauge cluster (both ads only) but on the DME or ZKE it can’t communicate.

So something with the serial port connection to the VM is acting funny.

Does this cable work with the new library I linked?

[MParallel]

Haven’t had the time/opportunity to test it yet.

Still hope to get the original setup working though.

[2JZ E36]

If somebody else has gotten this working it might be useful to start a list with proven to be working setups/cables

[MParallel]

Not tested yet. But still confused why you think my usb to obd to 20-pin wouldn’t work, but your usb to rs232 to 20-pin would. And then in config file you use ads not usb, which is the connector you start with?

I’m also wondering, I once bought a usb-to-20 pin Do It Auto, which they no longer sell. Advertized as ads compatible, which I doubted, but had to test. Also came with a modified ads32.dll. Well long story short: didn’t work, worse yet, not communicating with any module.

Would be funny if it would with this ediabaslib variant.

[2JZ E36]

Not tested yet. But still confused why you think my usb to obd to 20-pin wouldn’t work, but your usb to rs232 to 20-pin would. And then in config file you use ads not usb, which is the connector you start with?

I’m also wondering, I once bought a usb-to-20 pin Do It Auto, which they no longer sell. Advertized as ads compatible, which I doubted, but had to test. Also came with a modified ads32.dll. Well long story short: didn’t work, worse yet, not communicating with any module.

Would be funny if it would with this ediabaslib variant.

The reason is works is because the RS232 USB cable has a driver that makes it seem like a normal serial port. To the program there is no difference if you use an RS232 cable or an actual serial port (for the most part). The reason why this doesnt work with the original .dll is because BMW adresses the serial chip directly (around the driver pretty much), which doesnt work because its actually USB. I suspect it wont work with an obd cable because it expects an RS232 interface, but you never know until you try it :)

If the creator of the tinyADS interface wanted to, he could put an RS232 to USB converter chip on his board. Then it would be a true USB interface without an adapter cable...

Edit: I have heard about the Do-it-Auto Interface, but it seems like you werent the only one having troubles with it...

[MParallel]

You mean the FTDI chip?

My usb to obd uses that chipset and drivers. So usb to obd (to 20 pin) should be no different than usb to rs232 to obd/20 pin.

But yes, just need to test all variations, including the USB lines of the config file.

Unless my tinyads will work with the true setup. Still a mystery why through a VM data seems to get lost or interrupted through the serial port.

[MParallel]

...The reason why this doesnt work with the original .dll is because BMW adresses the serial chip directly (around the driver pretty much), which doesnt work because its actually USB. I suspect it wont work with an obd cable because it expects an RS232 interface, but you never know until you try it :)...

Still trying to understand this. I thought this new method was to make it work without an RS232 interface, as that is the main problem with ADS. But you say it still expects an RS232 interface. Unless I am misunderstanding you.

I finally received my ADS interface (OpenLab). So if I copy your ssetup, I will need a USB-to-RS232 adapter. Too funny as there is an RS232 port on the pc I am using (but can't connect to most modules, as I need a VM 32-bit OS. Can connect to some ADS only modules, but not for example, the DME, which is really weird). I have VM setup to directly access the host's serial port.

There are many different USB-to-serial interfaces. Not sure if they all come wit the FTDI chipset.


I did some quick testing with my USB-OBD-20pin interface. Editting the config files did give different reesults. With ADS set as the interface and com-port set to the one of the USB port, I did get two black dots in INPA, but could not connect with any module.

Maybe it doesn't work with all version of EDIABAS. I was testing with 6.4.7.

[2JZ E36]

Still trying to understand this. I thought this new method was to make it work without an RS232 interface, as that is the main problem with ADS. But you say it still expects an RS232 interface. Unless I am misunderstanding you.

It thinks it is talking to a real RS232 interface, when in reality it is talking to an adapter. I dont know if that explanation is actually accurate, but thats how I explain it to myself :D A real RS232 interface is NOT needed.


There are many different USB-to-serial interfaces. Not sure if they all come wit the FTDI chipset.

It doesnt mean that other chipsets dont work, I just used an FTDI chip and it works correctly.




I did some quick testing with my USB-OBD-20pin interface. Editting the config files did give different reesults. With ADS set as the interface and com-port set to the one of the USB port, I did get two black dots in INPA, but could not connect with any module.

Maybe it doesn't work with all version of EDIABAS. I was testing with 6.4.7.

Did you try the OpenLab ADS Interface? Or are you still missing the RS232 adapter?

Personally I dont really care if an adapter is needed as long as it works. My main problem was that I had to carry a superold heavy laptop around just for the serial port on it. Now I can just use my daily ultrabook for the ADS stuff.

[Fireball1991]

hi there!

I've some quick questions for this setup...

so i built my own ADS interface about a 1.5 year ago, and it's working fine. i wondering, i'll like to convert this to USB because my laptop doesn't have a real serial port, just USB.

so what now? which cable do i need to convert serial to usb for my laptop?

i built this interface:

https://www.bimmerforums.com/forum/showthread.php?1650885-(Almost)-free-DIY-ADS-interface/page21

Post #508.

Thanks a lot!

[maxwatt]

@2JZ E36, Thanks for sharing this. Are you able to also share EDIABAS/INPA installer you used. My current installation files, doesn't seem to be working following your instruction. Also using Win10 64bit. Regards.

[2JZ E36]

@2JZ E36, Thanks for sharing this. Are you able to also share EDIABAS/INPA installer you used. My current installation files, doesn't seem to be working following your instruction. Also using Win10 64bit. Regards.

I use EDIABAS 7.3.0 und INPA 5.06, which should work if you follow the instructions closely. If it doesnt work you also have to make sure you have NET Framework installed.

[MParallel]

I have to get back to this project as I haven't had the time nor need for working ADS. But still would be cool.

I did put lots of time in getting my ADS working with an ADS interface AND native RS232 port, which works fine on my old big heavy laptop, but not on my Win10 64-bit host computer, with Win XP/Win7 32-bit guest OS. Serial port is configured correctly and I am able to acces two ADS-only module, but none of the others. I tried every baud speed and the other 10 million config settings, but none seem to work. I did notice in my EFI (bios) checking the port settings, it reverts back to Baud 11500 whereas normally 9600 is used. I wonder if under water it uses 11500 while 9600 is needed and this cause timing problems in the data transfering, that only two modules don't have a problem with.
Just sucks. Normally I would have simply ditched the 64-bit OS and just install a 32-bit OS, but the fact that the bios is of the (U)EFI variant, this prevents installing anything but 64-bit OS's. Even though it has a setting for legacy Bios in its config screens, setting it to this doesn't make it recognise any bootable 32-bit OS's.


Also after triple reading everything above, the whole USB interface doesn't make any sense. So it works with USB as tested by you (2JZ E36) but are still using an ADS interface, but with a USB-ADS adapter in between. That seems like it still needs the ADS hardware on the ADS side of the adapter.
If this Github setup works with USB, a direct USB-to-20 pin connector or USB-ODB -> OBD->20-pin connector cable should work too. You would think.

Now it sounds like a hybrid solution. You still need an actual ADS cable, but instead of using it directly on an RS232 port, it uses an USB port, with adapter cable in between.

[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:

https://i.imgur.com/OGH3o4L.jpg
https://i.imgur.com/OGH3o4L.jpg
https://i.imgur.com/OGH3o4L.jpg
698873

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

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 Interfacein 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!

[jsncarrier]

Did this ever come to a conclusion? Its getting hard to find a laptop with an actual serial port and there are videos of windows XP computers getting malware within minutes of being connected to the internet (https://www.youtube.com/watch?v=6uSVVCmOH5w)

I was able to get connection to ECU over a cheap K+D can cable but I'm trying to access the other modules (mostly the abs module) on my 1999 Z3 2.8L. It seems to use the L line from what I have been able to read online. I'd like an affordable way to diagnose my ABS issue, and possibly code the trip computer.

To my knowledge I can use ICOM, which seems expensive, or ADS which uses actual serial and old windows. Neither seem ideal. So, does anyone have a reproducable way to do this on a modern computer in 2024?

[328 Power 04]

If malware is your fear, then you can get newer laptops and Windows that work just fine. I'm not sure why XP is still suggested.

INPA for ADS works on windows 10 x86 (32-bit), and laptops that have the available dock with a true serial port will work. Dell E5430 with Serial Dock, x86 Windows, the Dell specific ADS driver, etc. is just one example.

ICOM works with any new / modern laptop and latest versions of the software.

[Rektosaurus]

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

https://i.imgur.com/OGH3o4L.jpg
https://i.imgur.com/OGH3o4L.jpg
https://i.imgur.com/OGH3o4L.jpg
698873

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

Hey, I was wondering of i could order that setup somewhere? The ads thing looks awesome in the bmw cover style😁

[oljay]

I tried this with numerous connectors and INPA versions but none worked. At the end, I had to get a dell latitude D630 with serial port and ADS cable from aliexpress, a true ADS connection just worked fine.

Still I'm curious if anyone else could do this, it would be nice to try and make it work with modern laptops...

[328 Power 04]

ICOM interface and you can run any new laptop and any new version of INPA and EDIABAS. ICOM talks all the different modes and protocols. Well not the junk Chinese ones.

[ZGator]

I tried this with numerous connectors and INPA versions but none worked. At the end, I had to get a dell latitude D630 with serial port and ADS cable from aliexpress, a true ADS connection just worked fine.

Still I'm curious if anyone else could do this, it would be nice to try and make it work with modern laptops...

at least for my DME 2k z3 ms4.2? I use a ADS round adapter with DCAN USB - which I also use sans the 64 bit ADS to USB2 adapter for my E90.

I use Windows 11 now but have been using it on windows for years. the Dcan usb will appear as COM interface in windows which you must setup as been described in detail.

[328 Power 04]

Facelift Z3 work with K+DCAN cable as they have no necessary ADS modules. It's all K-line. No L-line.

[RJ's325ITS]

2024 Dec. Update.

I've tried his solution #2 with no luck. I have an old Dell620 with native RS-232 Win10-64bit and I couldn't make it work. I've tried many cables with no luck. but I have one serial to OBD2 adapter that has 2 butons, one for obd and one for ADS. That one worked for me 10/15yrs ago when the Dell 620 was runing XP 32bit with INPA 3 and old Adiabas. But that original hard drive when out and took out the motherboard with it. So I ended up with loosing that working set up.

When I tried to launch INPA it gives me the error - No DirectNT.sys found -

Is there anyone in here that got this working with option #2 that can help me out?

I'm out of options. I've tried a bunch of scanners that were advertised to be able to communicate with the ABS module, no luck with any of them. I am trying to fix my fiancé's 1993 E36 ABS.

Thank you

[Niederbayer]

Hi,

i also tried solution #2 but unfortunately without success till now.
I followed the complete procedure. Setting nointegritychecks to on was not that easy, i had to disable secure boot in bios first.
"sc query directnt" shows me now that the driver is in running state. So far so good.
When i start inpa now, unfortunately i end up in a blue screen while inpa is loading.

System:
HP Probook 650 G4 with native RS-232
Win 11 64-bit

Has anyone observed the same problem and been able to solve it or has some hints for me?

Thanks

[2JZ E36]

This is the website of GiveIO, which I used to make this work (its german): https://www-user.tu-chemnitz.de/~heha/viewzip.php/hsn/giveio64.zip/readme.txt?as=TXT
He says that using a hypervisor produces a bluescreen, so you could check if that is enabled. He also says that on a W10 64 Bit machine he has a bluescreen, but on another he doesnt. He didnt know what causes it however.
I am using this setup in a tower pc with a cheap PCIE card (SIENOC PCI-Express PCI-E Dual RS-232).

[Dimy95]

i also don't find directnt.sys in the #2 solution
does anyone know ho to find it since i've had directnt.sys problem when i open inpa?
thank you

[adr0]

Hi,
relatively new to the forum and I have been having weeks upon weeks of issues trying to get INPA working with my vehicle.
I have followed all of your setup exactly and appear to be one step away from getting this mess working with my car.
Some background:
Running Windows 10 x64
FTDI usb to obd2 connector
ADS to OBD2 connector
I have used this ads connector with INPA out of the box to read the DME and the Airbag module, but I am unable to connect to the body control module, dashboard, and other important body electronics.
I have been attempting solution 1 of the original post, with the up to date downloaded github for ediabaslib binaries.
Where I currently sit, is after changing the lib config to ADS instead of std:obd, I am getting errors every time I try to connect to modules I was previously able to connect to.
Error: SYS-0002: ECU OBJECT FILE NOT FOUND.
I have already gone down the troubleshooting route from the original INPA documentation, and I have all of the files downloaded and in the correct location as all of the writeups suggest. I fear that I need a more specific solution in connecting the downloaded github software with INPA and NCS.
Has anyone else seen this error before or have any ideas towards a solution? Any help whatsoever would be greatly appreciated