BMW K+CAN INPA/SSS/DIS/CARSOFT/NAVCODER usb interface idiot proof

[manocao]

it funny but i have updated inpa to 5.0.2 and it has different behaviour when connecting interface to pc:
now it always shows both dots white, until i power pin 1 of obd2 connector in interface, moment in which it turns both dots into black
with inpa 4.4.7, battery dot was always black (with interface plugged in pc, of course) and ignition dot turned into black only when powering pin 1 of obd2 connector in interface

when updating, i have selected "com1" and "usb to serial adapter", maybe it got something to do with all this???????
i see new installation has copied ftdi drivers (very old, v1.00.2115) to C:\EDIABAS\Hardware\OBD
maybe it is the only function of selecting "usb to serial adapter"

[oep]

manocao, don't need any switch for 20pin.
cut from above obd connector where pin1 is and solder wire and to 20pin obd. Melt little plastic over it where you solder wire and cover it. Works here.
As for usb inf, you need to restart soft to get both dots, or enter in some model and return.
Both bl/rl can be made to detect real bat and ing as normal inf does, use same diagram for other pins.

[manocao]

As for usb inf, you need to restart soft to get both dots, or enter in some model and return.

it doesnt work for me
both dots always white, even with interface pin16 powered, they only come black when powering pin1 (ignition)

edit: i found out the problem:
when upgrading i chose "usb-serial adapter" which modified a line in obd.ini (it wrote USB instead of OBD):
Hardware=OBD
i have edited obd.ini like above and now i got always battery dot black, and ignition dot gets black only when powering pin1
this is normal behaviour like before
if i edit Hardware=ADS then both dots are always black (this is for other kind of interface)

i have realized that upgrading hasnt erased previous 4.4.7 instalation because it installs inpa 5.0.2 in different directory:
inpa 4.4.7 ---> C:\INPA\BIN\INPALOAD.EXE
inpa 5.0.2 ---> C:\EC-APPS\INPA\BIN\INPALOAD.EXE
so i can use both versions
although if i try some cars in both versions, i got errors, i think there are some .ifo files missing

here is my obd.ini (it is located at C:\EDIABAS\Bin):

[OBD]
Port=Com1
Hardware=OBD
RETRY=ON
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xF0000000
;Tracelevel=0x0000FFFF
; Bit 0 = Funktionsaufruf
; Bit 1 = io Ergebnis
; Bit 2 = nio Ergebnis
; Bit 3 = Detailinfos
; Nibble 0 = readchar_wait
; Nibble 1 = main
; Nibble 2 = cmd
; Nibble 3 = obd
; Nibble 4 = send_and_receive_...
; Nibble 5 = read_telegram_...
; Nibble 6 = send_telegram
; Nibble 7 = SendData

[UNIT_A]
Port=Com2
Hardware=OBD
[UNIT_B]
Port=Com3
Hardware=OBD
[UNIT_C]
Port=Com4
Hardware=OBD
[UNIT_D]
Port=Com5
Hardware=OBD
[UNIT_E]
Port=Com6
Hardware=OBD
[UNIT_F]
Port=Com7
Hardware=OBD
[UNIT_G]
Port=Com8
Hardware=OBD
[UNIT_H]
Port=Com9
Hardware=OBD
[UNIT_I]
Port=Com10
Hardware=OBD
[UNIT_J]
Port=Com11
Hardware=OBD
[UNIT_K]
Port=Com12
Hardware=OBD
[UNIT_L]
Port=Com13
Hardware=OBD
[UNIT_M]
Port=Com14
Hardware=OBD
[UNIT_N]
Port=Com15
Hardware=OBD
[UNIT_O]
Port=Com16
Hardware=OBD



***************


Example for OBD.ini :

[OBD]
Port = Com1
;Einstellen der seriellen Schnittstelle
;erlaubte Werte: COM1, .., COM99
TRACELEVEL = 0
;nur f?r interne Fehlersuche
;erlaubte Werte: 0=aus, ansonsten 0x00000000 .. 0xFFFFFFFF
RETRY = OFF
;Wiederholung im Fehlerfall, wird von EDIABAS bereits gemacht, sollte deshalb aus sein.
;erlaubte Werte: OFF, ON
MODE=NORMAL
;Bei KBUS werden DS2-Telegramme in K-Bus-Telegramme umgewandelt.
;Kommunikation nur am einzelnen DS2-Steuerger?t am K-Bus zul?ssig.
;erlaubte Werte: NORMAL, KBUS
HARDWARE=OBD
;OBD-Stecker OBD
;OBD-Stecker am USB->Seriell-Adapter USB
;alte ADS-Hardware ADS
UBATT=ON
;Bei UBATT=OFF wird der Batteriestatus nicht ?ber die Hardware ermittelt
;sondern fest auf „Batteriespannung vorhanden“ gesetzt.
;Workaround f?r den Hardwarefehler des LAPTOP DELL LATITUDE D600.
;Dieser ist nicht in der Lage den Batteriestatus richtig zu erkennen.

*************

retry: Repetition in the event of an error made by EDIABAS already, should therefore be made.

mode: In KBUS DS2 frames in K-bus messages are converted. Communication only at the individual DS2-control device on the K-Bus permitted.

ubatt: In UBATT = OFF, the battery status is not determined by the hardware but firmly "available battery voltage" on set.
Workaround for the hardware failure of the LAPTOP DELL LATITUDE D600.
This is not really in a position to recognize the battery status.

************

SAY THANKS!!

[djcristi]

my real ignition mod .

for those who are wondering why is not working with 20pin adapters: those adapters don't have the ignition pin/wire

[manocao]

i see this is source web of kkl mod
My DIS/INPA/SSS/CARSOFT/NAVCODER Interface. - Bimmerforums - The Ultimate BMW Forum
great bmw forum there

[yorugualoco]

i see this is source web of kkl mod
My DIS/INPA/SSS/CARSOFT/NAVCODER Interface. - Bimmerforums - The Ultimate BMW Forum
great bmw forum there

I post in several forums under my nick name "LOCUM" but it was unavailable here on DK

anyway you can take a look here (spanish language)
http://www.bmwfaq.com/f16/interface-...or-20-a-524852

[manocao]

i m8
got 1 more question:
i installed several inpa versions, some set interface as OBD and others as ADS by default, what's the difference? OBD=16pin and ADS=20pin connectors? how must i config .ini files with your modded interface? OBD or ADS?
thanks

edit: sorry, i found the answer or your other forum: Interface =STD:OBD

-----------------

Configuraciones para el DIS

EDIABAS (en windows)
Configuraci?n del c:\ediabas\bin\ediabas.ini, ojo no es el archivo completo, en negrita son los par?metros
que hay que poner dentro del archivo

;================================================= ============================
;EDIABAS 6.4.7 Configuration
[Configuration]
;================================================= ============================

Interface =STD:OBD
LoadWin32 = 1


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

;-----------------------------------------------------------------------------
; RemoteHost
; Description : server address/name
; Default = diaghead
RemoteHost = 192.168.68.1
;-----------------------------------------------------------------------------
; Port
; Description : IP communication port
; Value : 1000 < port < 30000
; Default =
Port = 6801

c:\ediabas\hardware\obdsetup.exe, que este todo ok

-------------------------

ps: i saw this info on ebay


this is serial rs232 interface




source: http://cgi.ebay.com/ebaymotors/BMW-I...motiveQ5fTools

[yorugualoco]

so, what was your question?

[oep]

maybe he's gets horny on bimers as chicks do..

[lee_hdi]

Is this to work with DIS software? or another piece of software?

Sorry if that seems a stupid question, I'm just starting with diagnostic software, so just doing a bit of research

[zeca]

hi
interface with the chip pins 17-18-20 ft232bm are bound together but when installing the BC546 transistor pin 20 is no longer linked to the 17 and 18 do not understand can you explain?
thanks

[yorugualoco]

hi
interface with the chip pins 17-18-20 ft232bm are bound together but when installing the BC546 transistor pin 20 is no longer linked to the 17 and 18 do not understand can you explain?
thanks

well, the reason to make Ignition circuit, it's to be able to do CAR KEY MEMORY and some others features in DIS or SSS.

If you don't do ignition circuit you still can diagnosis and clean error memory.

In ftdi232 BM/BL pins 17 and 18 are #ri and #gnd, if you solder them you will have allways battery ON, meanwhile pin 20 is #dsr and goes to ignition

[yorugualoco]

Is this to work with DIS software? or another piece of software?

Sorry if that seems a stupid question, I'm just starting with diagnostic software, so just doing a bit of research

mate have you READ the title of this thread?

[yorugualoco]

my real ignition mod .

for those who are wondering why is not working with 20pin adapters: those adapters don't have the ignition pin/wire

Mate why you say it doesn't work with 20 pins cars?

It work's on my 20 pin diag 530d E39, i think you are talking about ADS cars and NOT 20 Pins diag port

[oep]

Mate why you say it doesn't work with 20 pins cars?

It work's on my 20 pin diag 530d E39, i think you are talking about ADS cars and NOT 20 Pins diag port

Boys, chino obd2 to round connector is not fully populated (not all wires are connected, pin20) that's why is not working.
I already wrote this shit before, so you could read and make yours working correctly.