DIS connection issues after API successful test

[se93]

Its not over yet. jajaja. Connected my laptop to my E45 and tried to run a diagnostic. First of all, i had to manually identify the vehicle and withthe INPA/EDIABAS 100% compatible interface this should be done automatically. Tried to run a short test and got the following messages:

communication between poerating unit and diagnostic head is impaired fault number 200 159

diagnosis bus error 200 133

I found out after trying to run the diagnostic, that my battery is fully drained as its been about 2 weeks since i last started the E46 up. Can the problems be related to lack of battery charge or is there something that needs to be modified.? I did switch over the Fister as DavidMc told me.

After this, i went into INPA and connected with no problems at all.

What could be the issue?

Regards,
mark

Here are my specs

Interface = STD:OBD
Remotehost = 192.168.68.1
Port = 6801

hosts

127.0.0.1 localhost
192.168.68.1 diaghead diaghead
192.168.68.30 gt1ap gt1ap
192.168.68.32 gt1ap2 gt1ap2

BDFLUSHR to 30

I set VM to off
switched to Fister and restarted ediabas.ini to update

API test is successful with vm off and vm on

When i try to do a diagnostic, i do not have the auto select (Katvis has the same interface as i do and his does auto detect his vehicle) and i get the two error message above mentioned which are

communication between poerating unit and diagnostic head is impaired fault number 200 159

diagnosis bus error 200 133

Here is an update

am still up at hom (3:00AM) and after changing the ediabas.ini file when you type vi i saw that the one of the lines of the file said interface = remote, so i went ahead and changed it to Interface = STD:OBO

saved changes and exited. I ran an API test and failed. I went into DIS, diagnosis and for the first time today saw the CONNECT DIAGNOSTIC CONNECTOR AND SWITCH ON IGNITIION. IS THE BATTERY VOLTAGE OK

Then i got a message after following the above instructions: THE DIAGNOSTIC CONNECTOR IS NOT OK. NO VOLTAGE IS SUPPLIED TO TERMINAL `54 OR BATTERY VOLTAGE IS LESS THAN 9 VOLTS.

I selected the car manually and tried to run a diagnostic in the DSC system and got thiis meesage: DIAGNOSIS BUS ERROR FAULT NUMBER 200.45

As i mentioned perviously that i had not started up my E46 in about two weeks and was unaware of this after the first time i connected my laptop to the vehicle because i decided to remove the laptop/interface and start the car up and when i did, the battery was dead. I got a jumper from my wifes Ford and the car started up. I left the engine running for about 20 minutes and have been testing the DIS system with an unfully charged battery.

Where should i go from here? Kind of stuck at the moment. Was it correct on my behalf to change the interface in the ediabasl.ini from the unix screen to STD:OBO?

[David Mc]

Passing the APItest just means that the network necessary to facilitate communication between DIS and EDIABAS has been successfully established and is working. Trying to run a diagnostic on a car with a flat battery is like attempting to make a call on a cell phone with a flat battery - no chance - think of the diagnostic bus error as telling you that there is no call tone/service.
Correct interface settings in EDIABAS.ini depend on what interface you are using, whether you are using a USB adapter/PCMCIA card or a machine with a serial port. DIS puts a fair drain on the car electrical system, so chances are that if the car battery was flat and you have been attempting diagnostics whilst running the engine, you have been pulling charge out of the battery nearly as fast as you were putting it in.