Bat and ign

[purplecty]

I am playing woth a dell d600 and a one stop electronics usb cable. The bat and ign are always on but as soon as i plug in the 20 pin connector the ignition dot goes blank and as soon as i take it out is goes black again. I can connect ysing INPA but GT1 DIS is giving me connection issues. Any ideas?

[David Mc]

It sounds like your cable is emulating the ignition signal and as soon as it sees the actual ignition signal, the signal is being inverted. You could try disconnecting Pin 16 on the 20 pin round connector end of the cable.

[purplecty]

It sounds like your cable is emulating the ignition signal and as soon as it sees the actual ignition signal, the signal is being inverted. You could try disconnecting Pin 16 on the 20 pin round connector end of the cable.

I am using a one stop electronics cable and had the same results with just the 16 pin plugged inside the car. I use it mainly for dcan and not for kcan but I should work both ways. Any recommended USB kcan cables that are known to work properly? Im building it for a friend. I use a dell d610 woth gerts cable and the 600 doesnt recognize anything using gerts cable. I read the serial port was the issuecso i need a good usb cable to get this going to provide him with. INPA functions even though the ign dot goes blank, but i cant get the copied DIS i put on there to recognize the head...

[David Mc]

Try using the custom ADS32.dll for DELL ads32-dell.dll.txt (delete the .txt extension and insert into your C:/EDIABAS/Bin folder). This driver inverts the ignition signal, which is the issue with some DELL serial ports. Gert's interface should work fine with this setup if the ignition signal was not detectable previously and you may find that your DCAN cable starts working correctly as well.

[purplecty]

Try using the custom ADS32.dll for DELL <img src="https://www.bimmerforums.com/forum/attachment.php?attachmentid=604092"/> (delete the .txt extension and insert into your C:/EDIABAS/Bin folder). This driver inverts the ignition signal, which is the issue with some DELL serial ports. Gert's interface should work fine with this setup if the ignition signal was not detectable previously and you may find that your DCAN cable starts working correctly as well.

Ok gerts cable never showed battery signal either... So just rename it to ads32.dll and put it the BIN folder?

[purplecty]

So i used this file with no changes. I can only connect to INPA using my ediabas 6.4.7 which has an obd.ini file i can adjust com port settings on for the usb i have on com2. Ediabas 6.4.3 will not connect and the initial install did not have an odb.ini file which i tried to copy over with no luck. With 6.4.3 it never shows bat or ign signals. The DIS is a copy from my other laptop so i went over the read this first doc and redid all thise settings and now in DIS i do not get the diagnostic head communication error. I now get no battery voltage is applied at terminal 15 or battery voltage is less than 9 volts automatic vehicle identification is terminated...


Should I try and get one of those switchable k+dcan cables off of ebay or Amazon? Any recommendations?

[David Mc]

When you installed the ads32-dell.dll file, did you rename it as ads32.dll (so that it replaced the original file in your EDIABAS/Bin folder?) If not, the software will be ignoring the new driver file and continuing to use the original.

[legoman67]

you should get accurate battery and ignition signals with Gerts cable. Theyve always worked for me.

Are you using the correct interface type in ediabas.ini?(STD:OBD or ADS) Ive noticed that if its set wrong those signals will act strange.

[purplecty]

When you installed the ads32-dell.dll file, did you rename it as ads32.dll (so that it replaced the original file in your EDIABAS/Bin folder?) If not, the software will be ignoring the new driver file and continuing to use the original.

Yep that's exactly what I did... I know these D600s had serial port issues that got updated with the D610 which i use as my own laptop using gerts cable with no issues.... The usb part is what gets me as I have never had a dedicated usb cable for kcan cars and mainly use on dcan cars which always gives me ignition and battery signals... The one stop cable comes with an adapter that can be used for older cars kcan cars...

[David Mc]

I have never known Gert's cable not to correctly show battery and ignition signal other than on the early DELLs, but this issue is easily corrected using the ADS32-dell.dll. The One-stop K+DCAN cable should also not present any problems (assuming you have run DCAN.exe and configured the comms settings for KCAN mode.

[purplecty]

Odd because gerts cable works fine on my dell D610 just not the D600... My car is a 3\99 build date...

I am using ediabas 6.4.7 with ibd.ini set on come2 and The usb cable is on com2. Dcan.exe loaded with com2 selected from the drop down box and when i choose kcan it recognizes the cable and makes the connection... Like i said INPA works but the ignition dot goes white once the usb cable gets plugged into thr car and DIS doesnt recognize the battery voltage...

[David Mc]

This may sound like a silly question, but how many instances of EDIABAS are you running on the D600? The symptoms sound exactly as if the ads32-dell.dll driver is not being used, is it possible that you may have installed the file in an EDIABAS/Bin folder that is not in use? To test the theory, all you need to do is rename the EDIABAS folder in which you placed the driver to EDIABAT, then test the software again. If there is a second instance of EDIABAS in use, the program will not be affected.

[purplecty]

This may sound like a silly question, but how many instances of EDIABAS are you running on the D600? The symptoms sound exactly as if the ads32-dell.dll driver is not being used, is it possible that you may have installed the file in an EDIABAS/Bin folder that is not in use? To test the theory, all you need to do is rename the EDIABAS folder in which you placed the driver to EDIABAT, then test the software again. If there is a second instance of EDIABAS in use, the program will not be affected.

I have a few of them and will double check. I may have dumped it into my ediabas 6.4.3 folder and renamed it when changing to 6.4.7 which was the only one I had any success with... I will try later when i am home...

[David Mc]

Don't forget also that obd.ini must be placed inside your Windows folder in order to work with EDIABAS v6.4.3, whereas with v6.4.7 it goes inside c:/EDIABAS/Bin.

[purplecty]

Don't forget also that obd.ini must be placed inside your Windows folder in order to work with EDIABAS v6.4.3, whereas with v6.4.7 it goes inside c:/EDIABAS/Bin.

Ahhh ok that makes more sense for 6.4.3 I was wondering how that worked whuch is why i reverted to 6.4.7 because i couldn't get anything going with 6.4.3 using the usb cable... I will try soon and post back with results...

[purplecty]

Update: Changed to ediabas 6.4.3 - Added obd.ini with correct com port 2 that usb cable is assigned to - ran dcan.exe and chose com2 and kcan which showed done and recognized - Bat is black but ign stays white and INPA still works - DIS still will not connect and gives the switch ignition and and no voltage is applied at terminal 15 or bat voltage is below 9 volts automatic vehicle ident is terminated. I noticed the ignition dot goes black real quick and then white when i connect the 20 pin port.


Update: Feel like an idiot. Turned CAN off on dcan.exe and the bat and ign dot stay black using INPA but i still cant connect and diagnose using DIS. Automatic Vehicle doesnt work and manual ident cant even read the DME...

Changed to 6.4.3 and restarted server file and DISv44 finally recognizes and auto identified and carried out short test successfully. Why didnt it work with 6.4.7?

6.4.3 using inpa 3.01 is reading errors in german and 6.4.7 they come back in english which files need to be swapped over to 6.4.7 to have the errors in english?

Without any additional changes it now recognizes the car with DIS and 6.4.7. I'll just keep it on 6.4.7 since everything in INPA comes back in english and doesnt give me the language doesnt match error for the modules i tested it on which has errors return in german... What a fun past few days diagnosing this and getting it done correctly! Thank as always David now to get RHEINGOLD loaded and tested functional...

[328 Power 04]

Thank you David for posting the Dell ADS driver. I have been (lazily) looking for it here and there.

I used it to finally get my fairly modern Dell Latitude laptop to work through the Dell true serial port dock.
It is working fine on the Win7 x86 I dual boot to. Using INPA 5.0.1 with EDIABAS 6.4.7.


I have noticed that if the TinyADS interface isn't connected to car, it will show battery on and sometimes ign on. Then if I connect to car, the IGN will start working correctly. Not sure if this helps you.


Tested on my 99 Z3M coupe, and all functions worked as well as ICOM.







However.... I still can't get TinyADS to work with my 328is. I think it may be a case of the instrument cluster taking down communication, or corrupting the data lines. The TinyADS lights up the K-Line and RXD light as soon as I connect to the car without ignition on. Weird. Nothing communicates. Some VAG-KKL / K+DCAN cable communicate to K-Line modules.

[purplecty]

Thank you David for posting the Dell ADS driver. I have been (lazily) looking for it here and there.

I used it to finally get my fairly modern Dell Latitude laptop to work through the Dell true serial port dock.
It is working fine on the Win7 x86 I dual boot to. Using INPA 5.0.1 with EDIABAS 6.4.7.

I have noticed that if the TinyADS interface isn't connected to car, it will show battery on and sometimes ign on. Then if I connect to car, the IGN will start working correctly. Not sure if this helps you.

Tested on my 99 Z3M coupe, and all functions worked as well as ICOM.

However.... I still can't get TinyADS to work with my 328is. I think it may be a case of the instrument cluster taking down communication, or corrupting the data lines. The TinyADS lights up the K-Line and RXD light as soon as I connect to the car without ignition on. Weird. Nothing communicates. Some VAG-KKL / K+DCAN cable communicate to K-Line modules.

Are you using a Dell D600?

[328 Power 04]

No, I'm using a more recent Dell Latitude E6430. Nice powerful unit, i7 processor, USB3.0, etc.

[purplecty]

No, I'm using a more recent Dell Latitude E6430. Nice powerful unit, i7 processor, USB3.0, etc.

Yeah my D610 works fine without any modified files using gerts serial cable... The D600 I think is known to have issues... I will just get a cheap usb cable for my friend I am building this for with a 20pin adapter...

[MParallel]

Could be related, but in EDIABAS.ini there are settings for Batt/Ign handling.

[purplecty]

Could be related, but in EDIABAS.ini there are settings for Batt/Ign handling.

There are? Where?

[MParallel]

There are? Where?

Just seen this now.

If you search on ubatt / ign you will find it right away. Although I am not sure if this is an answer to your problem.

; 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

[MParallel]

....The TinyADS lights up the K-Line and RXD light as soon as I connect to the car without ignition on...

What exactly do you mean by light up? In the software of you have a cable with actual light for these two lines?

Reason I'm asking is that I have loanded a friend's "Gert" cable which has light on the connector, but I always only see 1 red light when plugged in.

I have a mini laptop with serial port (Com1, IRQ4, on address 3F8). In INPA the battery and ignition light work correctly. I can read my E36's cluster, OBC and Remote control modules without any problems (which coincidence or not, are modules that can only be read with ADS), but any othter module that I can read perfectly with OBD, give me an IFH-0009 error.

Seeing I can read these ADS only modules, I'm pretty sure (or was) that my ADS settings are all correct.

Could it be script files itself?