(Almost) free DIY ADS interface

[zuranic2]

Hello,

I Just made mkI CD4053 interface. I connected to '93 e36 320i through PCMCIA serial card with Jaroslav Klima ADS driver modification.

Program recognize batt and ignition signals so I assume that interface is made correctly.

When I start identification, program does not recognize any module. If I directly select script for e36 engine (which I know is MS 40.1) I get messages:

IFH-0010: Data transmission to control unit disturbed

Requested control unit: 'MS 40_1, MS401K20' not found. Control unit found:'. Program will be stopped!

Error 95 SYS-0005: Object file not found.

I went through INPA_FAQ document and I set receive and transmit buffers to 8. I also try to copy SGBD files in Ediabas\Ecu directory but still I get same errors.

If I pick some other modules e.g. instrument cluster I get error:

IFH-0009: ECU isn’t connected or doesn’t respond

So, any suggestions?

[benemorius]

IFH-0010: Data transmission to control unit disturbed

This error means that it has detected a problem with the interface transmitting data onto the vehicle's diagnostic bus. If you get this error, then there must be a problem with either the interface or the vehicle.

[zuranic2]

I think that car is ok because Carsoft is running fine. So I will check interface.

[PitrekT]

It seems it is a problem with INPA scripts.Try to use DIS instead.

[zuranic2]

My laptop is not appropriate for this. It has 60GB HDD and 512MB RAM. I think this is not enough. Or it is?

[benemorius]

My laptop is not appropriate for this. It has 60GB HDD and 512MB RAM. I think this is not enough. Or it is?

Sure, it is enough. It's hard to find anything much better than that with a real serial port.

[HansV]

A laptop with a PCMCIA adapter and the ADSport tool should work fine, that is what I'm using.
You can actually by a new laptop with a serial port as well. We have a couple of HP's at work for serial applications. Dell and Siemens fujitsu also have serial port laptops.

[mattydr67]

Mr. HansV
Please tell me what PCMCIA do you use, sir?
Becasue not all kind of PCMCIA's working with ADS tool
Thank you
Good luck

[benemorius]

Is it possilbe with this design to manually control L-line (high / low) by using DTR or other pin ? Older ecu's need init on L-line.

I'm not sure what you're asking. Or maybe I'm just not sure why.

If you want to assert the L line manually, you can do so using the DTR and TXD pins at the serial port. If you raise TXD while DTR is low, you'll assert (lower) the L line. If DTR is high, you'll assert the K line.

Is that what you wanted?

[HansV]

Easier to du this with the OBD interface, where the L-LINE kan be pulsed with the RTS signal. But then you can only send wake up signals on the L-LINE, not transmit TDX data.
The TXD signal can be hard to control this way because you can't talk directly with the hardware, like the ADS driver does. But there might be some other driver that gives you direct control og the TXD pin?

[KevinMullins]

I'm not sure what you're asking. Or maybe I'm just not sure why.

If you want to assert the L line manually, you can do so using the DTR and TXD pins at the serial port. If you raise TXD while DTR is low, you'll assert (lower) the L line. If DTR is high, you'll assert the K line.

Is that what you wanted?

Easier to du this with the OBD interface, where the L-LINE kan be pulsed with the RTS signal. But then you can only send wake up signals on the L-LINE, not transmit TDX data.
The TXD signal can be hard to control this way because you can't talk directly with the hardware, like the ADS driver does. But there might be some other driver that gives you direct control og the TXD pin?

He's developing software and wanting to communicate with older ECU's and such, which requires wake on the L-line. So basically he's needing to trigger that wake signal on demand.
http://forums.bimmerforums.com/forum...ighlight=Testo
I'm sure he'll chime in with better details of his work in progress.

[benemorius]

Thanks for the explanation. In summary: I need to be able to put L-line high or low for certain amount of time. I assume it is possible by setting DTR high or low. I have to test this. Controlling TX pin ( high/low ) is not possible in my program.

I see. I didn't realize you still wanted to control it from software.

In that case, you're basically running up against the very same problem which (I assume) provoked BMW to use the ghetto direct hardware control ADS drivers that we've all come to hate so much due to their requiring a "real" serial port. I expect we can find a better solution in our time than they found in theirs (that was decades ago) but I'm afraid it won't be as simple as toggling the DTR pin on an existing ADS interface. Toggling DTR only switches the output driver between the K and L lines. The only way to actually then pull K or L low is with TXD.

Of course, the most obvious solution is to simply invent a new interface which does allow this direct control of the L line with DTR as you're hoping for, but I think no one would disagree that the last thing the world needs is a new interface which is incompatible with everything else. Some brainstorming may be in order. If I read through your Test-O thread, will that bring me up to speed on what you're doing?

Yes, well I'm actually working on another project more actively but this is something that also needs to be solved.

Curiosity compels me to ask if you wouldn't mind elaborating.

[epj3]

Valuable thread -- I appreciate all the posts which helped me successfully install EDIABAS/INPA and easyDIS. I was able to pair my alarm unit to my car, reset my random airbag light, and bleed my brakes the proper way. I purchased the ADS interface from benemorius and it works great.

Two things -- I was receiving the IFH-0009 error while initially trying to run the ABS bleeding procedure. The ABS unit had a fault code stored (I removed the ASC throttle body years ago). I temporarily fixed that and I no longer received the error.

Other, it's very easy and cheap to purchase an old PC or laptop on craigslist specifically for this use. My total out of pocket expense for the PC, keyboard/mouse, serial cable and interface was less than a Peake reader.

[benemorius]

Did some experiment and it turns out setting TX line low is as easy as calling SetCommBreak- method. Then with DTR you can control which one, K or L.

I've been doing some research and I'm being led to the same conclusion, but I've been delayed in getting a compiler set up on my INPA laptop by the lack of a wifi adapter so I haven't played around with it yet. How is it actually working out for you? Have you successfully woken up and communicated with a 5 baud wakeup module using standard windows APIs?

It's almost too good to be true. It could mean that we're only one windows hacker away from having a rewritten ADS driver and freeing everyone from real serial ports. Of course, I could be way off the mark here, but I really can't imagine any other reason for that damn driver to exist if not for the 5 baud wakeup.

[archonx]

Hello there from good old germany. Today i had my second test with the interface in hansV´s MkII version. Second because the first time i gave up too fast.
My technical setup:
Dell D830 laptop with real serial connector
Win XP Ultimate 32bit
HansV MKII interface.
Inpa 4.4.7 Ediabas 6.4.3
E36 325 ECE Convertible M50B25TÜ
The first try i had was not succesful at all, i got no connection to any module. Then i tried it with inpa 5.0.1 later i read that this is only an update and i need an older version for the module data.

So the Point is with my current setup (inpa 4.4.7 and MKII interface) today i was succesful in connecting to airbag module, read and delete fs. But still i can´t access any other module i get IFH-0009. I checked the Com1 settings and the ediabas and obd .inis. I think the module should be ok and settings should also be ok. If not i wouldn´t be able to acces airbag module.
https://www.dropbox.com/s/8wsqqynsri...-D%203.2.T3000
this is my layout it can be opened with this program:
....................................
these days i will try to setup dis and check with that up till then i hope somone has an idea what´s wrong

Thanks in advance and sorry for my english ;-)

[KevinMullins]

Shouldn't have to mess with the OBD.ini .... everything should be in ADS mode, not OBD.
Did you run the ADSsetup from the Hardware folder of EDIABAS?
Is the EDIABAS.ini set to run in ADS mode?
Did you adjust all the COM port settings as usual for INPA? (latency rates and such)
Have you tried running the "Quick Identification Test" in INPA to see what all modules it recognizes?
And you should be running INPA version 3.01 (4.4.7 is the loader version, not INPA itself)

[archonx]

Hello again.
I ran the adssetup when i installed inpa. Today i ran it again, same issue.
i don´t really know where in the ediabas.ini to seth the interface, i just see explanation on which interfaces are possible so here´s my ediabas.ini as found in ediabas folder and copied to windows folder

;================================================= ============================
;EDIABAS 6.4.3 Configuration
[Configuration]
;================================================= ============================


;-----------------------------------------------------------------------------
; EcuPath
; Description : ECU file path
; Default = .
EcuPath = C:\EDIABAS\ECU


;-----------------------------------------------------------------------------
; SimulationPath
; Description : Simulation file path
; Default = .
SimulationPath = C:\EDIABAS\SIM


;-----------------------------------------------------------------------------
; TracePath
; Description : Trace file path
; Default = .
TracePath = C:\EDIABAS\TRACE


;-----------------------------------------------------------------------------
; CodeMapping
; Description : Character mapping file path
; Default = .
;CodeMapping = C:\EDIABAS\BIN\ansi2oem.tab


;-----------------------------------------------------------------------------
; TraceSize
; Description : Maximum size of each trace file [KB]
; Value : 0..32767
; Default = 1024
;TraceSize = 1024


;-----------------------------------------------------------------------------
; ApiTrace
; Description : Enable/Disable API/User trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + time stamp
; 3 = User trace + time stamp + process id (Win32)
; 4 = Function trace
; 5 = Function trace + time stamp
; 6 = Function trace + time stamp + timing
; 7 = Function trace + time stamp + timing + process id (Win32)
; Default = 0
ApiTrace = 0


;-----------------------------------------------------------------------------
; IfhTrace
; Description : Enable/Disable IFH trace
; Value : 0 = Trace disabled
; 1 = Trace enabled
; 2 = Trace enabled
; 3 = Trace enabled
; Default = 0
IfhTrace = 0


;-----------------------------------------------------------------------------
; SystemTraceSys
; Description : Enable/Disable system trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceSys = 0


;-----------------------------------------------------------------------------
; SystemTraceBip
; Description : Enable/Disable BIP trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceBip = 0


;-----------------------------------------------------------------------------
; SystemTraceIfh
; Description : Enable/Disable IFH system trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceIfh = 0


;-----------------------------------------------------------------------------
; SystemTraceNet
; Description : Enable/Disable network trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceNet = 0


;-----------------------------------------------------------------------------
; BipDebugLevel
; Description : BIP debug level of ECU files
; Value : 0..32767
; Default = 0
BipDebugLevel = 0


;-----------------------------------------------------------------------------
; UbattHandling
; Description : Ubatt ON/OFF handling
; Value : 0 = Ubatt ON/OFF: No EDIABAS error
; 1 = Ubatt ON/OFF: EDIABAS error
; Default = 1
UbattHandling = 0


;-----------------------------------------------------------------------------
; IgnitionHandling
; Description : Ignition ON/OFF handling
; Value : 0 = Ignition ON/OFF: No EDIABAS error
; 1 = Ignition ON/OFF: EDIABAS error
; Default = 1
IgnitionHandling = 0


;-----------------------------------------------------------------------------
; TaskPriority
; Description : EDIABAS process/thread priority (only Win32/16)
; Value : 0 = Optimal EDIABAS performance = 8
; 1 = Minimal EDIABAS performance
; ..
; 10 = Maximal EDIABAS performance
; Default = 0
TaskPriority = 0


;-----------------------------------------------------------------------------
; LoadWin32
; Description : Map EDIABAS Win16 calls to EDIABAS Win32
; Value : 0 = Win16/32 Mapping disabled (Win16-->Win16)
; 1 = Win16/32 Mapping enabled (Win16-->Win32)
; Default = 0 for Windows 9x/Me
; Default = 1 for Windows NT4/2000/XP
;LoadWin32 = 0


;-----------------------------------------------------------------------------
; SystemResults
; Description : Enable/Disable system results (ubatt/ignition/jobstatus)
; Value : 0 = Disable system results
; 1 = Enable system results
; Default = 1
SystemResults = 1


;-----------------------------------------------------------------------------
; RetryComm
; Description : Repeat failed communication automatically (1x)
; Value : 0 = Retry disabled
; 1 = Retry enabled (1x)
; Default = 1
RetryComm = 1


;-----------------------------------------------------------------------------
; Simulation
; Description : Enable/Disable ECU simulation
; Value : 0 = Simulation disabled
; 1 = Simulation enabled
; Default = 0
Simulation = 0


;-----------------------------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = EDIC
Interface =STD:ADS


; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!


; Interface = STD:ADS
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : \EDIABAS\HARDWARE\OBD\ODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
; INI-Datei : OBD.ini nur benutzt wenn im Windows-Verzeichnis
; Unterstuetzung : WIN3.xx : Nein
; WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja


; Interface = STD:FUNK
; Beschreibung : Funk-Diagnose Interface MDA von Fa. Siemens
; Installation : keine
; INI-Datei : FUNK.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja


; Interface = ADS
; Beschreibung : Serieller Pegelwandler (Anschluss an Diagnose-Dose)
; Installation : \EDIABAS\HARDWARE\ADS\ADS32\ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja


; Interface = KBUS
; Beschreibung : Serieller Pegelwandler (Anschluss direkt an K-Bus oder I-Bus)
; Installation : \EDIABAS\HARDWARE\ADS\ADS32\ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja


; Interface = EDIC
; Beschreibung : Serielles , PCMCIA , PC-Card Interface von Fa. Softing
; Installation : \EDIABAS\HARDWARE\EDIC\SETUP.EXE
; INI-Datei : EDICFW.INI, EDICHW.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja


; Interface = EDICC
; Beschreibung : EDIC-Card C oder EDIC-Card 2 CAN-Interface von Fa. Softing
; Installation : \EDIABAS\HARDWARE\EDIC\SETUP.EXE
; INI-Datei : XEDICC.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja


; Interface = STD:CAN
; Beschreibung : PCMCIA CAN-Interface CanCardX von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CANRTTP.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : ?
; Ansprechpartner: Hr. Jusko
; Telefon : +49-(0)89/382-35891 (Hotline)
; email : FLASH.SERVICE@BMW.DE (Hotline)


; Interface = STD:ADS4MOST
; Beschreibung : Most-Interfaces von Fa. Oasis
; Installation : keine (ausser Installation der Oasis-Karte)
; INI-Datei : ADS4MOST.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : Michael.Rowedder@bmw.de


; Interface = REMOTE
; Beschreibung : Anbindung eines EDIABAS-Interfaces über TCP/IP
; Installation : Anpassung der Einträge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : Michael.Rowedder@bmw.de


; Interface = REMOTE:name
; Beschreibung : Anbindung eines EDIABAS-Interfaces über TCP/IP
; Installation : Anpassung der Einträge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : REMOTE.INI (insbesondere für Parallelbetrieb notwendig)
; In REMOTE.INI stehen unter [name] spezif. Einstellungen(z.B.: RemoteHost, Port)
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : Michael.Rowedder@bmw.de


;-----------------------------------------------------------------------------
; NetworkProtocol
; Description : Network protocol
; Default =
NetworkProtocol = TCP


;================================================= ============================
;TCP/IP Configuration
[TCP]
;================================================= ============================


;-----------------------------------------------------------------------------
; RemoteHost
; Description : server address/name
; Default =
RemoteHost = WMUC102911


;-----------------------------------------------------------------------------
; Port
; Description : IP communication port
; Value : 1000 < port < 30000
; Default =
Port = 3000

;-----------------------------------------------------------------------------
;TimeoutConnect
; Description : Timeout for establishing the connection
; Default = 5000
TimeoutConnect = 2000


;-----------------------------------------------------------------------------
;TimeoutReceive
; Description : Timeout for receiving a message
; Default = 5000
TimeoutReceive = 2000


;-----------------------------------------------------------------------------
;TimeoutFunction
; Description : Timeout for a long function
; Default = 59000
TimeoutFunction = 10000


;-----------------------------------------------------------------------------
;DisconnectOnApiEnd
; Description : Enable/Disable Disconnection with function call ApiEnd
; Value : 0 = Disconnection disabled
; 1 = Disconnection enabled
; Default = 0
;DisconnectOnApiEnd = 1


;-----------------------------------------------------------------------------
;InitCmd<n>
; Description : Initialization command <n> (normally for OPPS)
; Default =
;InitCmd0 = FE,04,00,03,01
;InitCmd1 = FD,05,00,03,01


;================================================= ============================
; End Of File EDIABAS.ini
;================================================= ============================

i think com port should be ok, i tried max buffers and setting to 8 on transmit and receive buffers all other settings are default settings
when i run quick identification on inpaloader i see transmit diode flashing and trying to connect to the modules but it can´t acces any, except for the airbag module
https://www.dropbox.com/s/91w4ke29txbs6no/INPALOADER.exe%20funktioniert.bmp
https://www.dropbox.com/s/d1u056uy5xh2k6l/INPALOADER.exe%20funktioniert%20nicht.bmp
when i run inpa.exe itself i get only an error message "fehler beim übersetzen"
https://www.dropbox.com/s/fn8nmnk93juyhwu/INPA.exe%20Fehlermeldung.bmp
it´s the same when i disconnect my cable, so i think that it´s a software/laptop related problem

thanks for you help

- - - Updated - - -

Hello again.
I did a new test today. First i ran the adssetup.exe, again. No change. When i start inpaload.exe i can access airbag module, read and delete errors, all other modules don´t respond (pic 1 and 2).
https://www.dropbox.com/s/91w4ke29txbs6no/INPALOADER.exe%20funktioniert.bmp
https://www.dropbox.com/s/d1u056uy5xh2k6l/INPALOADER.exe%20funktioniert%20nicht.bmp
only difference in inpaloader is the attempt to access DME then this error messages appear:
https://www.dropbox.com/s/bvpk9x4nn3vakag/INPALOADER.exe%20DME1.bmp
https://www.dropbox.com/s/bb0sye0ut63wia7/INPALOADER.exe%20DME2.bmp
https://www.dropbox.com/s/iomhxjkiq9nq6ym/INPALOADER.exe%20DME3.bmp

When i start inpa.exe i get "fehler beim übersetzen".
https://www.dropbox.com/s/fn8nmnk93juyhwu/INPA.exe%20Fehlermeldung.bmp

I took a look into ediabas.ini again but i don´t see where to change the interface, only thing i see is the explanation which interfaces are possible so here´s my ediabas.ini:
https://www.dropbox.com/s/d5d8t8r0jjkureq/EDIABAS.INI
I think i even tried different settings for com port 1 now it´s set to maximum buffers for transmit and receive. This is my first try for inpa so i don´t know the usual settings i read in a faq file that buffers should be set to 8 i think i did this but after all i´m not sure at all cause i tried so much different settings ;-)
Quick identification test on inpa just delivers the error message on inpaloader only airbag module is responding
As i couldn´t access any module with inpa.exe i tried disconnecting the module and gave another try and inpa just gave me the same error "fehler beim übersetzen" (should be "error while translating" in english)

Thank you for your help

[archonx]

Shouldn't have to mess with the OBD.ini .... everything should be in ADS mode, not OBD.
Did you run the ADSsetup from the Hardware folder of EDIABAS?
Is the EDIABAS.ini set to run in ADS mode?
Did you adjust all the COM port settings as usual for INPA? (latency rates and such)
Have you tried running the "Quick Identification Test" in INPA to see what all modules it recognizes?
And you should be running INPA version 3.01 (4.4.7 is the loader version, not INPA itself)

Hello again.
I did a new test today. First i ran the adssetup.exe, again. No change. When i start inpaload.exe i can access airbag module, read and delete errors, all other modules don´t respond (pic 1 and 2).
https://www.dropbox.com/s/91w4ke29txbs6no/INPALOADER.exe%20funktioniert.bmp
https://www.dropbox.com/s/d1u056uy5xh2k6l/INPALOADER.exe%20funktioniert%20nicht.bmp
only difference in inpaloader is the attempt to access DME then this error messages appear:
https://www.dropbox.com/s/bvpk9x4nn3vakag/INPALOADER.exe%20DME1.bmp
https://www.dropbox.com/s/bb0sye0ut63wia7/INPALOADER.exe%20DME2.bmp
https://www.dropbox.com/s/iomhxjkiq9nq6ym/INPALOADER.exe%20DME3.bmp

When i start inpa.exe i get "fehler beim übersetzen".
https://www.dropbox.com/s/fn8nmnk93juyhwu/INPA.exe%20Fehlermeldung.bmp

I took a look into ediabas.ini again but i don´t see where to change the interface, only thing i see is the explanation which interfaces are possible so here´s my ediabas.ini:
https://www.dropbox.com/s/d5d8t8r0jjkureq/EDIABAS.INI
I think i even tried different settings for com port 1 now it´s set to maximum buffers for transmit and receive. This is my first try for inpa so i don´t know the usual settings i read in a faq file that buffers should be set to 8 i think i did this but after all i´m not sure at all cause i tried so much different settings ;-)
Quick identification test on inpa just delivers the error message on inpaloader only airbag module is responding
As i couldn´t access any module with inpa.exe i tried disconnecting the module and gave another try and inpa just gave me the same error "fehler beim übersetzen" (should be "error while translating" in english)
Edit: When i connect the interface i get one diode complete and one diode a bit emitting light is this the normal behaviour of the interface or did i do wrong at assembly?

Thank you for your help

p.s. sorry for double posting, i thought post 1 was lost because after clicking on "reply" it vanished sorry for that

[KevinMullins]

Your EDIABAS.ini is fine.

;-----------------------------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = EDIC
Interface =STD:ADS

If you hadn't already, double or triple check your circuit build, make sure you don't have a transistor backwards or anything like that. I know I missed a few little things during my build and testing since we were making changes during circuit design phases.
It almost sounds like you are missing a communication line somewhere. Both K and L line LEDs should kinda go back and forth at times.

Edit: When i connect the interface i get one diode complete and one diode a bit emitting light is this the normal behaviour of the interface or did i do wrong at assembly?

Yeah, that sounds about right from what I recall. I no longer have LEDs on mine to check.

My little videos might be of some help to see how that circuit should be working. First video was before the final modification to the circuit, so there weren't as many modules recognized, but it has the LEDs to watch.
The second video is the MKII version, which should be the same modules you should get access to.
1. http://www.youtube.com/watch?v=cHxROZ3MN8I
2. http://www.youtube.com/watch?v=3jmLKVVrY9w

[IcemanBHE]

Your EDIABAS.ini is fine.

No.

It should say ADS. Not STD:ADS

[KevinMullins]

No.

It should say ADS. Not STD:ADS

Ah. Good catch..I just glanced and ignored the STD: part.
So yeah, it should look like this -

;-----------------------------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = EDIC
Interface =ADS

[archonx]

So, some days are gone, i did a new approach on a line matrix pcb... and what should i say, i got access to airbag, zke, cvm and instrumental cluster. so it seems that my old layout was badly assembled... :-( so now i´m doin a new layout which is easier to solder and to manufacture.
I´ll build a new one tomorrow or any day of this week. What makes me confused is that despite the success of reading many more modules, i can´t get access to my DME nor can i access my DWA or ABS or my BC. I was not able to get a scan of all my modules because my experimental interface didn´t recognize ignition. The error message when i try to access DME is: "SYS-00002: SG Variantenbeschreibungsdatei nicht gefunden" is there any special problem or is it likely that it´s still the interface?
I will build the new interface in each case but i want to exclude ohter errors as far as it´s possible.

Greetings

[KevinMullins]

Since other modules are responding I would assume your "environmental path" and all that is set correctly. Sounds more like it is not fonding the correct module files that it is expecting to find when trying to connect to those particular modules.

SYS-0002: ECU OBJECT FILE NOT FOUND EDIABAS_SYS_0002
Meaning: The ECU variant description file couldn't be found.
Causes: Either the description file does not exist in the EDIABS search path or the search path is wrong.
EDIABAS search path: The EDIABAS configuration element EcuPath describes the EDIABAS search path. When the configuration setting does not exist, the current directory is used by EDIABAS as the search path.
Error correction: Description file does not exist: Copy the requested description file in the EDIABAS search path.
Search path is wrong: Terminate the application program, and assign the correct path to configuration element EcuPath.

[archonx]

I did some extended researches and found this thread: http://www.bimmerforums.co.uk/forum/...hanks-t105302/ in short form it says that dme331.prg causes the problem on e36 325 without ews because this file is missing in c:/ediabas/ecu so how can i fix that/where can i find dme331 for download?

[KevinMullins]

Yeah, there are problematic versions of that one floating around...been awhile since I doinked with it, but I should have a working version around here, I'll look.

EDIT: Try this one. Just remove the ".pdf" from the name.DME331.PRG.pdf