How do you switch from ODB to ADS for DIS and INPA?

[phamine]

I have ODB working for both DIS 44/55 and INPA 5.00.

Do I need to edit ediabas.ini to have it work with ADS?

I'm using the adapter below. Pressing the button does not help.




Spec:
Dell D630 laptop with serial port
ODB to ADS adapter using serial port

Here's my ediabas.ini file showing the interface

Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =STD:OBD

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

; Interface = STD:OBD
; 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 : Suchreihenfolge analog zu EDIABAS.ini
; 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/XL von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CAN32.INI
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja
; 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

[IcemanBHE]

Do I need to edit ediabas.ini to have it work with ADS?

Correct.

You also need to run the ADS setup in Ediabas/Hardware/ADS

And I hope your INPA 5.x was an upgrade from 3.x or youll be missing some files...

[phamine]

Correct.

You also need to run the ADS setup in Ediabas/Hardware/ADS

And I hope your INPA 5.x was an upgrade from 3.x or youll be missing some files...

...Upgrade eh. I don't remember.

So if I wanted to use ODB again, I would have to run another setup to get it back as well as rewrite the ediabas.ini files?

Thanks

[IcemanBHE]

Depends...

On my D630s and X60s, you only have to run the hardware setups once, the first time.

Then just edit the ini and flip the interface switch and all is well. (EDIT: Of course the Ediabas server has to be shutdown before you do this...)

But I have seen other peoples computers that require the setups each time they swap...

[phamine]

So basically I'm switching to ADS from STD:OBD where I have bolded below in the ediabas file?

Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =STD:OBD

[IcemanBHE]

Correct.

[phamine]

Ok. No go.

1. Ran ADS setup
2. Changed to Default = STD:ADS to ediabas.ini in ediabas/bin and windows folder
3. Restarted

Did I miss something?

[age109]

Ok. No go.

1. Ran ADS setup
2. Changed to Default = STD:ADS to ediabas.ini in ediabas/bin and windows folder
3. Restarted

Did I miss something?

Change Interface=STD:OBD
to
Interface=ADS

[phamine]

Nice. It worked. Thank you all.

I changed the wrong field at first. I changed the default by mistake.

Its

Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =STD:OBD //Change this to Interface=ADS

Now I have to read on how to switch to D-CAN for newer cars.

[IcemanBHE]

No...it should say ADS

NOT STD:ADS

See your first post...those are your interface options.

[phamine]

No...it should say ADS

NOT STD:ADS

See your first post...those are your interface options.

Ah. It worked with STD:ADS.
Let me try just ADS tomorrow morning

[IcemanBHE]

I doubt it. Ill bet it didnt read the L Line modules.

Do a module dump with special tests both ways and see if it found them all.

[phamine]

I doubt it. Ill bet it didnt read the L Line modules.

Do a module dump with special tests both ways and see if it found them all.

What modules should a E36 1999 S52 M3 have that should show up. I tried Interface= STD:ADS and Interface= ADS and they both show up the same screen below.

Is there a specific L line module I can test in either DIS or INPA to verify?

[enda320]

The ABS is the main L line ecu which you can use to spot if you have it set up correctly.
If it was contacted, it would show a black bar with the ! mark like the airbag.

[jamie123]

it still looks like your in obd mode to me,your ediabas settings should read, =ADS then go to your hardware folder and click on adssetup,make sure you reboot the pc/laptop after.

[phamine]

1. I ran adssetup below and confirmed the driver was added.



2. I updated both ediabas.ini file in
- ediabas/bin and in windows folders with the descrip below in bold

;-----------------------------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =ADS

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

; Interface = STD:OBD
; 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 : Suchreihenfolge analog zu EDIABAS.ini
; Unterstuetzung : WIN3.xx : Nein
; WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja

3. Restarted
4. Bootup IFHSRV32 and DIS 44
5. Still can't access "ABS/ASC Stability Control" in the image below



I am able to connect in DIS using ADS as the cable is able to identify the car automatically. So it has something to do with me accessing the L lines. (ABS)

Thoughts

[IcemanBHE]

No cluster or body module either....

Not a E36 guy. Good luck.

Edit...is that a real Do-It-Auto interface or a ebay special.....

Phantom edit....I mean ONE Stop Electronics....

[phamine]

You guessed it.

Bought it from here.
http://www.one-stop-electronics.com/...&product_id=17

I did confirm that this cars has pin 15 as well. I guess ABS/Cluster/ZKE are read off L Line.

[age109]

How is DIS setup? Are you using Fister or Softing.

Fister is for ADS, Softing is for OBD. Might be a long shot, but I'd check.

From David Mc's Read this First Doc:

In order to use DIS to diagnose your car, first hit the IFHSrv32 shortcut you created earlier so that the Network between DIS and EDIABAS is supported. The IFHSrv32 icon will appear on your toolbar. Make sure that there are no Antivirus programs or firewalls running, then start your DIS/GT1 Virtual Machine.

A few minor adjustments may need to be made, depending upon what diagnostic head you are using – for example I use an ADS interface, so I had to use the Utilities menu to change the translator to “FISTER” and ensure that vm was switched off as INPA had been set up to use ADS rather than an OBD interface.

Remember that if you do make changes, you will also need to restart EDIABAS from the Utilities menu to ensure that your settings are adopted and saved.

[IcemanBHE]

What? Where did that come from?

Mine are set to Fister and I toggle back and forth between interfaces all the time.

[phamine]

Alright. Figuring I try to update my ADS driver since I'm using a Dell 630 that David MC posted.

http://forums.bimmerforums.com/forum...28&postcount=4

No go on L Line.

How is DIS setup? Are you using Fister or Softing.

Fister is for ADS, Softing is for OBD. Might be a long shot, but I'd check.

From David Mc's Read this First Doc:

In order to use DIS to diagnose your car, first hit the IFHSrv32 shortcut you created earlier so that the Network between DIS and EDIABAS is supported. The IFHSrv32 icon will appear on your toolbar. Make sure that there are no Antivirus programs or firewalls running, then start your DIS/GT1 Virtual Machine.

A few minor adjustments may need to be made, depending upon what diagnostic head you are using – for example I use an ADS interface, so I had to use the Utilities menu to change the translator to “FISTER” and ensure that vm was switched off as INPA had been set up to use ADS rather than an OBD interface.

Remember that if you do make changes, you will also need to restart EDIABAS from the Utilities menu to ensure that your settings are adopted and saved.

OBD and ADS only works on FISTER for me

[purplecty]

Do you need this for dell d610?

[phamine]

Do you need this for dell d610?

Not sure. From what I read it varies. If you have ADS working, no need I would guess.

Alright, I'm going to see if it's a hardware issue and do a continuity test on my cables/adapter.

http://forums.bimmerforums.com/forum...88&postcount=4

Anyone else using this adapter for ADS have trouble accessing L line?

[enda320]

Yep, I never got it to work, so I got an ICOM instead. Check your serial cable, I think you could get versions with the wires crossed for printers.

[328iJunkie]

Figure it out? I still cant talk to E36 ABS/ASC. I can talk to EVERYTHING else though !