BMW Forums : BimmerForums banner
61 - 80 of 84 Posts
Discussion starter · #61 ·
"Reqested control unit: 'DME331, DM331k20' not found. Control unit found: "

I presume this is the error that's confusing you. IMO, this doesn't refer to the files in your computer, but to the actual DME in the car. Basically, after you select the DME331 from that menu, INPA tells you that it wasn't able to find that control unit in your car.

"Control unit found" would return the DME found in your car, if INPA would have the files for it and if it was able to automatically recognize it. But it doesn't, so it's just a blank after the ":". Meaning that it can't find any known DME's.

Hope it makes sense.
 
This would make sense, but it's strange because as even click on the M43, for example, it shows the error "no response from control unit" and here shows that it can not find the file, the original files is as INPY.
I'll add that Tool32 connected to my engine without a problem using the file DM331K20.PRG
 
Discussion starter · #63 ·
A bit off topic, but anyone knows what a "plausibility error" is? INPA says there's something wrong with the knock sensors on my car, but not really sure what it means by "plausibility". Error is not present now, but frequency is 40, so not something I would want to ignore. I know the knock sensors are pretty cracked, but they never threw a CEL yet.

Image
 
Wont throw a light till it reaches obd criteria in frequency, and fault length and time etc in a certain time frame etc etc till then it just logs them as a pending code this is to rule out spikes and sporadic false errors..
 
Discussion starter · #66 ·
Wont throw a light till it reaches obd criteria in frequency, and fault length and time etc in a certain time frame etc etc till then it just logs them as a pending code this is to rule out spikes and sporadic false errors..
Thanks mate, that explains it. :thumbsup

This script applies only to the engine with VANOS, I checked the fellow e36 325i VANOS and running. Unfortunately, my engine will not connect: (
Told you.. I wasn't expecting it to work with non vanos DME's.
 
Hi i have an ads interface on a bmw e36 2.5i vanos 93 before car was a 97 1.8i and i changed the engine, used FAL files .ipo and .png works like charm with ignition on, when i start the engine message pops up "data distubed" and live data works like hell in 1 min reads 1 time with lots of errors both software INPA and DIS. Any have same problem, is there a fix ? or is a problem because i have a obd chassis (97 witch is obd, not ADS) and a ADS dme (engine) ?
 
Discussion starter · #70 ·
I have the same issue, I think the data communication speed is too low. I don't think there's a fix for that, unless you want to convert your car to OBD2.
 
I loaded the files from this thread, and I'm still getting this error:



My car is a 1994 325iC, build date 9/93, and non-EWS.

I noticed that in the .zip that was uploaded, the DME331.PRG file has a modified date of 5/15/1997. When I open it in Tool32, this is the Information it displays:



Is this correct or did the ZIP I download have the wrong PRG file? Where can I find a PRG for a DME3.3.1 non-EWS?

Thanks in advance,
Tim
 
I did,
errors:
"SYS-0012: IDENTIFICATION ERROR. Program will be stopped!"
"Reqested control unit: 'DME331, DM331k20' not found. Control unit found: ". Program will be stopped!"
I loaded the files from this thread, and I'm still getting this error:

I noticed that in the .zip that was uploaded, the DME331.PRG file has a modified date of 5/15/1997.

Is this correct or did the ZIP I download have the wrong PRG file? Where can I find a PRG for a DME3.3.1 non-EWS?
Tim
Hello to all, Greetings from Versailles, FRANCE

I am the lucky owner of an ALPINA E36 B3 3.0 convertible from 02/1995, which is derived from a E36 325i with Vanos.
It also uses a slightly modified DME Bosch 3.3.1.



I am trying to perform diag on my car using INPA and/or DIS.

I have two different PCs and config to work with:
1. one Lenovo W520 with 8GB Ram on Win7 64b. It has VMware working fine with INPA/DIS/SSS for my other BMW car (E39 from 05/2002) but I have never been able to connect to the ADS port of my Alpina
2. an IBM T30 with 1GB Ram on XP SP3. I was hoping to be able to use that old config to use at least INPA (Version V5.0.6) EDIABAS is Version 7.3.0

For the interface, I have purschased that one from BMW OBD USB Diagnostic Fault Code Cable - This Lead allows full Coding, Programming and Diagnostics for your BMW/.
It works perfectly on my E39 and for many modules (like ZKE, airbagn etc) on my ALPINA E36 (as long as connected to COM1) but not for the DME !

As I was getting the same following messages , I googled and found this very interesting post.
1/ IFH-0006: COMMAND NOT ACCEPTED. Program will be stopped!
2/ Requested control unit: 'DM331K20' not found. Control unit found: '???'. Program will be stopped!
3/ EDIABAS-Error
ApiCheckJobStatus: Error #16
IFH-0006: COMMAND NOT ACCEPTED
API job error or no such result !
Continue script processing ?

I downloaded the File mistreku.zip file and placed the DME331.IPO in C:\EC-APPS\INPA\SGDAT and DME331.PRG in C:\EDIABAS\ECU.

After this, I get similar messages than grzesiek2304:
1/ IFH-0006: COMMAND NOT ACCEPTED. Program will be stopped!
2/ Requested control unit: 'DME331, DM331K20' not found. Control unit found: '???'. Program will be stopped!
3/ EDIABAS-Error
ApiCheckJobStatus: Error #95
SYS-0005: OBJECT FILE NOT FOUND
API job error or no such result !
Continue script processing ?

The INPA FAQ says:
1.8 EDIABAS error: Error (95) SYS-0005: OBJECT FILE NOT FOUND
Reason 1: No SGBD in C:\EDIABAS\ECU ==> Not the case obviously
Solution 1: Copy the SGBD into the Ecu directory.
Reason 2: No group file in C:\EDIABAS\ECU (for group call)
Solution 2: Copy the group file to C:\EDIABAS\ECU
Reason 3: No path definition C:\EDIABAS\BIN
Solution 3: Set the system variable (see 2.1)
Reason 4: Incorrect path definition in EDIABAS.INI ==> I need to check this
Solution 4: Set the EcuPath path in Ediabas.ini to C:\EDIABAS\ECU
Reason 5: The SGBD name contains reserved characters or is too long. Only 8 characters
are allowed (a-z, A-Z, 0-9, "_").

Also at that point Toolset32 returns error: EDIABAS Fehler 16 : IFH-0006: COMMAND NOT ACCEPTED and nothing else (see screen grab)


So, at this point here is my thinking:
1. I don't think that this is a problem with the interface, otherwise, I would not be able to connect to other modules.
2. I don't think that it is due to the modified ALPINA DME 3.3.1, as I can connect to it with carsoft (with a different interface)

So does any one can (particularly Mr FAL) point me to any possible reason of my problem ? I will perform any additional test that are needed to make progress

Questions ?
1/ Is that normal that the DME331.PRG file has a modified date of 5/15/1997 ??
2/ My Ediabas.ini file is still in Interface = STD:OBD state and not to Interface = ADS. Should I change it to ADS ?
3/ Do I have to set-up an OBD.ini file as I use OBD via USB ?

PS: if anyone think that I have a chance to connect INPA to the ADS port using my Win7 64b with VMWare machine I would be happy to give it another chance....

Many thanks in advance for your help.
 
Hi!

At first: Sorry for my bad english, I´m from Germany...
Did anyone manage to get to the NON-VANOS DME since then?
I copied the files from the user FAL, but no succes unfortunately.

I would be very happy, if someone had the correct files or a helpful answer on my issue!

Thanks in advance
 
61 - 80 of 84 Posts