Results 1 to 24 of 24

Thread: Customize INPA Engine Script Selection

  1. #1
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90

    Customize INPA Engine Script Selection

    I’ve been wondering how I can get my car’s exact DME and engine reference to show up in INPA’s ‘Script selection’ > Engine selection menu. I hope that the experts out there can have a look and comment/advise regarding my observations below.

    Note: The reason I’m attempting this customization is because when I select the current closest engine selection:
    ME9.2 / MEV9 for N45 / N46

    I get the following error:

    Checking versions
    Versions do not match.
    Malfunction possible!

    My car is a 2007 E90 320i with MV1746 DME and N46TU2 engine. But my current INPA installation only shows the selections shown below:
    <INPA E90 Engine Menu (click to enlarge)>
    INPA E90 Engine Menu(cut).jpg

    I have realized that under the INPA > CFGDAT folder that the following files contain the menu selections for engines.

    MOTOR.ENG (or MOTOR.GER)
    * And in my car’s case:
    E90.ENG (or E90.ger)

    If I add my engine’s control unit(DME) related *.ipo reference and description text as a new ENTRY, I should be able to get my engine’s info included in the ‘Script selection’ > Engine > DME/engine selection menu.

    Currently the files MOTOR.ENG and E90.ENG include the entries below:
    < MOTOR.ENG >

    [ROOT_4]
    DESCRIPTION= 4 Cylinder
    ENTRY= DDE21,DDE 2.1 for M41,
    ENTRY= DDE30,DDE 3.0 for M47,
    ENTRY=DDE50K47,DDE 5.0 for M47 new,
    ENTRY= DDE6M47,DDE 6.0 for M47 new 2nd,
    ENTRY=,,
    ENTRY= BMS43,BMS 43 for M43,
    ENTRY= BMS46,BMS 46 for M43,
    ENTRY=,,
    ENTRY= ME9_4N,ME 9.2 for N42,
    ENTRY=ME9NG4TU,ME9.2 / MEV9 for N45 / N46,
    ENTRY=,,
    ENTRY= BMSCP,BMS CP for NG,
    ENTRY=,,
    ENTRY= DME13,DME 1.3 for M40,
    ENTRY= DME17,DME 1.7 for M42 / M43,
    ENTRY= DME524,DME 5.2 for M44,


    < E90.ENG >

    [ROOT_MOTOR]
    DESCRIPTION=Engine
    ENTRY= D50M47,DDE 5.0 for M47 TU,
    ENTRY= DDE6M47,DDE 6.0 for M47 TU2,
    ENTRY=,,
    ENTRY= D50M57,DDE 5.0 for M57 TU,
    ENTRY= DDE6M57,DDE 6 for M57TOP / M57TU2,
    ENTRY=,,
    ENTRY=ME9NG4TU,ME9.2 / MEV9 for N45 / N46,
    ENTRY= MS450,MS 45.0 for M54,
    ENTRY= MSV70,MSV 70.0 for N52 (NG6),
    ENTRY= MSV80,MSV 80.0 for N52KP (NG6),
    ENTRY= MSD80,MSD 80.0 for N43 N53 & N54 with EWS4/CAS,
    ENTRY=,,
    ENTRY= MSS60,MSS60 for S65 (M3),
    ENTRY=,,
    ENTRY=EKPM60_2,Fuel Pump EKP,


    If I select the closest match as is and look under Information, I get the following information about my DME:
    <Rework Program & Control Unit Description (click to enlarge)>
    Rework Program & Control Unit(reduced).JPG

    Under INPA > SGDAT folder, I found the following files of interest that may be related to my car’s DME (model: MV1746).
    02MEV1721.ipo (modified 3/29/2006)
    03MV1746.IPO (modified 5/9/2006)
    MEV17_2.IPO (modified 8/30/2005)

    Now, based on the observations so far, I am considering adding an ENTRY to files ‘MOTOR.ENG’ and ‘E90.ENG’ such as:

    ENTRY=*03MV1746,MV1746 for N46N,
    *As in ‘03MV1746.IPO’

    < Questions >
    1. Would adding such new ‘ENTRY’ then saving the file produce the desired menu entry in INPA?
    2. Among the 3 *.ipo files of interest(02MEV1721.ipo, 03MV1746.IPO, MEV17_2.IPO), is there a definite way I can determine which one INPA must reference?
    Last edited by tinkerman; 04-03-2013 at 08:49 AM.

  2. #2
    Join Date
    Dec 2007
    Location
    Queensland, Australia
    Posts
    4,286
    My Cars
    E70 3.0sd E21 323i
    You need to do some reading on how INPA works. Go to c:\INPA\DOKU and read the Inpa English .pdf file. You may also benefit from using TOOL32 to read which jobs can be executed from a particular .grp file. Make sure that you are using the appropriate interface and version of EDIABAS when attempting to execute the SGBD file or you will get errors.

  3. #3
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Thanks, I'll check out the document. Yeah, IcemanBHE mentioned in another thread about using Tool32 and PRG files to determine which file actually communicates with the module, then to look under INPA > SGDAT folder for the closest match of an *.IPO file. I'll do some further digging and be back.

  4. #4
    Join Date
    Jun 2010
    Location
    United Kingdom
    Posts
    99
    My Cars
    None
    Try these:
    tinkerman.zip

    MEV17N46.prg and D_MOTOR.grp in C:\EDIABAS\ECU
    MEV17N46_FAL.ipo in C:\EC-APPS\INPA\SGDAT

    Change E90.ENG with:
    [ROOT_MOTOR]
    DESCRIPTION=Engine
    ENTRY= MEV17N46_FAL,MEV17 for N46Tü2,


    Post back and let me know how you get on.

    P.S. 02MEV1721.ipo and 03MV1746.IPO are CABD control files for coding with NCS, not diaganostics with INPA. Hope that helps mate!
    Last edited by FAL; 04-04-2013 at 02:35 PM.

  5. #5
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Can’t thank you enough FAL! It’s 4AM where I am so I’ll have to try out what seems to be a custom made IPO file(?!) after some rest.

    But I must ask a few things about your NCS related comment:
    "P.S. 02MEV1721.ipo and 03MV1746.IPO are CABD control files for coding with NCS"

    1. How on earth do you know this? What reader program if any did/do you use if any?

    2. I noticed that 02MEV1721.ipo and 03MV1746.IPO are not in my NCSEXPER > SGDAT folder. Is that where they need to be? I ask because I don’t see a ‘CABD’ folder. I’m hoping that this would resolve the VO read issue I’m having in NCS.
    http://forums.bimmerforums.com/forum...FA)-Read-Issue

    Basically, I’m getting the following error and NCS is not initially reading the VO.
    “ Following feature is invalid for FA: $8AF ”
    I’m hoping that the CABD control files might do the trick if they are in the proper folder.

    Update: After updating to SP-Daten V49, the initial VO read in NCS proceeded normally.
    Last edited by tinkerman; 04-09-2013 at 02:40 PM.

  6. #6
    Join Date
    Jun 2010
    Location
    United Kingdom
    Posts
    99
    My Cars
    None
    Quote Originally Posted by tinkerman View Post
    But I must ask a few things about your NCS related comment:
    "P.S. 02MEV1721.ipo and 03MV1746.IPO are CABD control files for coding with NCS"

    1. How on earth do you know this? What reader program if any did/do you use if any?
    I was wrong, they're both *.ipo files for controlling the flash process in WinKFP/NFS, not NCS. They're not for a GUI, so are not really "human readable". My apologies for confusing you. It's been a long day...

    CABD *.ipo files for NCS, usually start with A_, so for example coding a SPEG module uses A_R56RW.ipo and SPEG56.prg
    CABD *.ipo files for WinKFP/NFS, usually start with a number, so for example flashing a SPEG module uses 16SPEG56.ipo and 10FLASH.prg
    Last edited by FAL; 04-04-2013 at 04:16 PM.

  7. #7
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Using the files provided by FAL, has allowed me to access the correct DME/engine related files, but even with SP-Daten V49 updated on my laptop, the initial error(below) still appears:

    Checking versions
    Versions do not match.
    Malfunction possible!

    I decided to push on with using INPA to see what would happen. This time, I started the engine to get an idea of ‘realtime data’ in INPA.

    But with every new function window(i.e. ‘Digital1’, ‘Analog2’ etc.) various API/SYS errors resulted and appeared before each data value, not showing the entire set of data all at once. In other words, I had to close each error message window for the next data value to show on the window.

    <Digital1/2 Error>
    ApiResultDigital: Error #98
    SYS-0008: JOB NOT FOUND
    API job error or no such result!
    Continue script processing?

    <Analog1/2/3 Error>
    ApiResultAnalog: Error #134
    API-0014: RESULT NOT FOUND
    API job error or no such result!
    Continue script processing?

    I can see data in bar graphs and blackened dots, but they are static (NOT ‘realtime’).

    What could be causing these errors?
    Last edited by tinkerman; 04-16-2013 at 01:48 PM. Reason: typo correction

  8. #8
    Join Date
    Sep 2010
    Location
    england
    Posts
    350
    My Cars
    1998 bmw m3 coupe smg
    SYS-0008: JOB NOT FOUND
    EDIABAS_SYS_0008
    Meaning:
    The job couldn't be found in the ECU description file.
    Causes:
    The job is missing in the description file, or the description file is wrong.
    Error correction:
    Check if the desired job exists in the description file. The program BESTINFO (contained in the RUNTIME SYSTEM) can be used to list all job names:
    bestinfo <Name of the description file with path and extension>
    Also check exactly if the job is spelled correct.
    If the desired job does not exist in the description file, extend the description file by the job.
    Target system:
    WIN SCO QNX

    - - - Updated - - -

    API-0014: RESULT NOT FOUND
    EDIABAS_API_0014
    Error interrogating a result.
    Causes:
    The result requested from the application program was not returned in the required result record by the job.
    Error correction:
    Add result in the result record.
    If applicable, contact the developer of the application program.
    Target system:
    WIN SCO QNX

  9. #9
    Join Date
    Apr 2011
    Location
    Mcloud, Oklahoma
    Posts
    3,100
    My Cars
    '99 323is, '00 323i 528i
    Version Mismatch is basically a language issue. (.ie not all of the files being used are of the same language)
    So you may have an .ipo file that is English Imperial and a .prg file that is English Metric. (or German, etc, etc)
    German Metric and English Metric files will usually play nice together, but mixing metric and imperial can throw live data values off.

    Attached some error document information to browse through.
    Attached Files Attached Files

  10. #10
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Much thanks!!! Will keep digging!

    - - - Updated - - -

    Quote Originally Posted by FAL View Post
    Try these:
    tinkerman.zip

    MEV17N46.prg and D_MOTOR.grp in C:\EDIABAS\ECU
    MEV17N46_FAL.ipo in C:\EC-APPS\INPA\SGDAT

    Change E90.ENG with:
    [ROOT_MOTOR]
    DESCRIPTION=Engine
    ENTRY= MEV17N46_FAL,MEV17 for N46Tü2,


    Post back and let me know how you get on.
    ...
    FAL, can you check/confirm if the files you provided are metric or imperial? Thank you!!!
    Last edited by tinkerman; 04-09-2013 at 03:12 PM.

  11. #11
    Join Date
    Jun 2010
    Location
    United Kingdom
    Posts
    99
    My Cars
    None
    Quote Originally Posted by tinkerman View Post
    FAL, can you check/confirm if the files you provided are metric or imperial? Thank you!!!
    German Metric *.prg file and English Metric *.ipo
    Quote Originally Posted by tinkerman View Post
    <Digital1/2 Error>
    ApiResultDigital: Error #98
    SYS-0008: JOB NOT FOUND
    API job error or no such result!
    Continue script processing?

    <Analog1/2/3 Error>
    ApiResultDigital: Error #134
    API-0014: RESULT NOT FOUND
    API job error or no such result!
    Continue script processing?

    What could be causing these errors?
    These errors are happening because of a problem with the *.ipo file i gave you. When INPA runs the *.ipo file, it is trying to call certain "jobs" from the *.prg file via Ediabas - unfortunately these "jobs" do not exist within that *.prg, hence the errors. I will have another look at the *.ipo for you and try again.

  12. #12
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    FAL,
    I really appreciate your help! I’m sure many others too with E90 320i models in non-US regions.

    Just a reminder, I’ve updated SP-Daten to V49.0 and installed the files using the help of BMW Coding Tool V.2.5.0.
    I’ve also updated BMW Standard Tools to version 2.12
    EDIABAS 7.3.0
    INPA 5.0.6
    NCS Expert 4.0.1
    NFS 5.2.9
    WinKFPt 5.3.1
    KMM 4.31.1

    Just a Side Note:
    From the default EDIABAS.INI, I changed the "LoadWin32 = 0" to "LoadWin32 = 1" just in case there are any 16bit info that would need to be interpreted into 32bit info.

    But I left other settings such as the network settings in the default settings, for I am not using any virtual machines requiring networking at least with this version of EDIABAS (I do have a folder with EDIABAS version 6.4.7 files stored in a different directory than C:\ so that I can use DIS V57 when needed, by swapping out the entire contents of the C:\EDIABAS folder which currently has version 7.3.0 files).

    Today, I gave INPA a try, and got the same errors when trying to access the engine while running, whether I chose the MEV17N46 or the other ME9NG4TU selection for DME.

    On the other hand, I was able to access almost all(29 windows) of the data sets under CAS. The only one that popped an error was ‘CAS – STATUS_ELV_WERTE’.

    If there is anything I can do to help, please don’t hesitate to let me know.
    Last edited by tinkerman; 04-12-2013 at 02:11 PM.

  13. #13
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    FAL,

    I ran into an interesting post:
    http://www.babybmw.net/viewtopic.php?f=29&t=45966

    in which there is the following entry:
    ENTRY= ME17R4 ,ME17.2.1 / MEV17.2.1 für N45TÜ/ N46TÜ2 ,

    I looked in my INPA>SGDAT folder and found:
    me17r4.ipo (modified date 2008-05-14)
    ME17R4.ini (modified date 2008-05-05))

    I am considering giving this entry a shot. I’m attaching the files with 'bogus extensions'(*.pdf / *.txt) to make them uploadable(hopefully they'll work fine if the added extensions at the ends are just deleted), but if you happen to have later versions, please do have a look at those. Thanks!!!
    Attached Files Attached Files
    Last edited by tinkerman; 04-13-2013 at 03:49 PM.

  14. #14
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Under INPA > CFGDAT, I edited the E90.ENG file by adding the following entry:

    ENTRY= ME17R4,ME17.2.1 / MEV17.2.1 for N45TU/ N46TU2

    Then with all fingers and toes crossed I pressed the selection in the Engine selection menu. The following error popped up:

    Versionskontrolle
    Nicht zusammenpassende Versionen.
    Fehlfunktion ist möglich!

    This is the same initial error I got before (in English)
    Checking versions
    Versions do not match.
    Malfunction possible!

    ***Update: The initial error seems to be a matter regarding language mismatch between files, but there is not any indication of a metric vs. empirial mismatch.***

    I was bracing for more “CLANG” tones and error messages as I pressed on with real-time reads of the engine.

    But for the first time, I had the, ‘IT’S ALIIIIIIIVE!!!’ moment as I noticed that every ‘job’ would return all data in real-time without a single error (while checking out the engine through the DME). I took about 50 screen shots of different menus and real-time data shown in individual windows. It was mostly in German, but I don’t mind learning some German.

    I’m under the impression that I’ve found the right *.ipo file:

    me17r4.ipo for my N46TU2 engine with MV1746 DME

    If any experts out there can confirm or know for certain otherwise, I’d very much appreciate you chiming in.
    I attached a couple of screenshots for reference.
    Attached Images Attached Images
    Last edited by tinkerman; 04-16-2013 at 02:00 AM.

  15. #15
    Join Date
    Dec 2012
    Location
    Hadley
    Posts
    13
    My Cars
    2002 bmw 330xi
    Got everything working tinkerman?

  16. #16
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Quote Originally Posted by tnhl1989 View Post
    Got everything working tinkerman?
    I think so (unless you have some pointers?). In the attached images of my previous post, btw, the "?" that appear are due to having had the Windows OS' 'Region and Language' > Administrative tab > Language for non-Unicode programs, set to Korean. When this is changed to German(and rebooted), "?" and any other 'strange' characters appear 'correctly'(in German).

  17. #17
    Join Date
    Dec 2014
    Posts
    4
    Hi tinkerman, think I may be having similar communication issues like yours.I can select F2 and select E87 then select engine, this brings up a variety of dde files, mine being dde 5.0 m47. I select it and get a pile of errors! Now if I press shift and F7 it give me a cylinder selection then a selection for m47 files, theres an extra one there that says M47 new! This will let me into the ecu to read the live values although there are still multiple errors trying to access some of the modules.

    If I could get the script from Shift + F7 selection to the F2 selection into the E87 folder it may let me use the rest of the functions. I have been hunting around in the CFGDAT folder, found the E87 folder and its missing my ECU D60M47A0.

    //************************************************** ********************
    //*
    //* Nacharbeitsauswahl INPA
    //*
    //* Datei E87.ENG
    //*
    //************************************************** ********************
    //* Gall TI-430
    //************************************************** ********************
    //* History:
    //* 11.02.2004 rd V0.01 Erstellung
    //* 16.02.2004 rd V0.90 Umstellung auf 32-Bit INPA
    //* 17.03.2004 rd V0.92 Kommunikationssysteme überarbeitet
    //* 04.04.2005 GA V0.93 MSV80 dazu
    //* 29.04.2005 gr V0.94 MSV70 dazu
    //* 12.08.2005 GA V0.95 FAS_PLX, BFS_PLX dazu
    //* 06.02.2006 gr V0.96 FRM_70, JBBF70 added
    //* 28.03.2006 GA V0.97 RDC_GEN2 dazu
    //************************************************** ********************


    [ROOT]
    DESCRIPTION=Select E87 V0.97
    ENTRY= EXX,Functional jobs,


    [ROOT_MOTOR]
    DESCRIPTION=Engine
    ENTRY= D50M47,DDE 5.0 for M47 TÜ,
    ENTRY= DDE6M47,DDE 6.0 for M47 TÜ2,
    ENTRY= DDE7N47,DDE 7.0 für N47,
    ENTRY=,,
    ENTRY=ME9NG4TU,ME9.2 / MEV9 for N45 / N46,
    ENTRY= MSV70,MSV 70.0 für N52 (NG6),
    ENTRY= MSV80,MSV 80.0 for N52KP (NG6),
    ENTRY=,,
    ENTRY=EKPM60_2,Fuel pump EKP,


    [ROOT_GETRIEBE]
    DESCRIPTION=Transmission
    ENTRY= GS19,Gearbox Control Module GS19,


    [ROOT_FAHRWERK]
    DESCRIPTION=Chassis
    ENTRY= DSC_87,Dynamic Stability Control,
    ENTRY=RDC_GEN2,Tire Pressure Monitoring,


    [ROOT_KAROSSERIE]
    DESCRIPTION=Karosserie
    ENTRY= MRS5,Airbag,
    ENTRY= AHM_E65,Trailer Module,
    ENTRY= CAS,Car Access System,
    ENTRY= DWA_E65,Alarm System,
    ENTRY= SINE_65,DWA Sirens and Tilt Sensor,
    ENTRY= ZBE_E87,Ergo Commander,
    ENTRY= FRM_87,Footwell module driver,
    ENTRY= FRM_70,Footwell Module Driver II (FRM_70, from 03/07),
    ENTRY= KOMB87,Instrument cluster,
    ENTRY= JBBF87,Junction Box Passenger,
    ENTRY= JBBF70,Junction Box Passenger II (DCAN),
    ENTRY= IHKA87,Air conditioning control,
    ENTRY= PDC_E87,Park distance control,
    ENTRY=PGS_65_2,Passive go system,
    ENTRY= FZD_87,Functional center roof,
    ENTRY= RLS_87,Rain and light sensor,


    [ROOT_KAROSSERIE_SITZ]
    DESCRIPTION=Seat Modules
    ENTRY= FAS_PLX,Seat Module Driver (new),
    ENTRY= BFS_PLX,Seat Module Passenger (new),
    ENTRY= FAS_87,Seat Module Driver,
    ENTRY= BFS_87,Seat Module Passenger,


    [ROOT_KOMMUNIKATION]
    DESCRIPTION=Communication Systems
    ENTRY= MCGW60,MOST/CAN-Gateway MASK,
    ENTRY= CCCG60,MOST/CAN-Gateway CCC,
    ENTRY= RAD2_GW,MOST/CAN-Gateway Radio 2,
    ENTRY= CCC_60,Car Communication Computer CCC,
    ENTRY= CCCA60,Car Communication Computer (Application),
    ENTRY= ASK_60,Audio System Controller CCC,
    ENTRY= ANT_60,Aerial Tuner,
    ;ENTRY= SVS_60,Voice Processing System,
    ENTRY= CID_87,Central information display color,
    ENTRY= MASK60,Audio System Controller MASK,
    ENTRY= RAD1,Radio 1/2,
    ENTRY= DAB_60,Digital radio terrestrial DAB,
    ENTRY= IBOC60,Hybrid radio USA IBOC,
    ENTRY= SAT_60,Digital Satellite Radio USA,
    ENTRY= CDC_E65,Audio CD Changer,
    ENTRY= NAV_60,Navigation System CCC ECE/US,
    ENTRY= TEL_E65,Telephone,
    ENTRY= AMP_60,Top hi-fi Amplifier,
    ;ENTRY= VID_E65,Video Module,

    Can I just add my ecu to the script? Is this what worked for you?

  18. #18
    Join Date
    Dec 2007
    Location
    Queensland, Australia
    Posts
    4,286
    My Cars
    E70 3.0sd E21 323i
    Try this:-

    //************************************************** ********************
    //*
    //* Nacharbeitsauswahl INPA
    //*
    //* Datei E87.ENG
    //*
    //************************************************** ********************
    //* Gall TI-430
    //************************************************** ********************
    //* History:
    //* 11.02.2004 rd V0.01 Erstellung
    //* 16.02.2004 rd V0.90 Umstellung auf 32-Bit INPA
    //* 17.03.2004 rd V0.92 Kommunikationssysteme überarbeitet
    //* 04.04.2005 GA V0.93 MSV80 dazu
    //* 29.04.2005 gr V0.94 MSV70 dazu
    //* 12.08.2005 GA V0.95 FAS_PLX, BFS_PLX dazu
    //* 06.02.2006 gr V0.96 FRM_70, JBBF70 added
    //* 28.03.2006 GA V0.97 RDC_GEN2 dazu
    //************************************************** ********************


    [ROOT]
    DESCRIPTION=Select E87 V0.97
    ENTRY= EXX,Functional jobs,


    [ROOT_MOTOR]
    DESCRIPTION=Engine
    ENTRY= D50M47,DDE 5.0 for M47 TÜ,
    ENTRY=DDE50K47,DDE 5.0 for M47 new,
    ENTRY= DDE6M47,DDE 6.0 for M47 TÜ2,
    ENTRY= DDE6M47,DDE 6.0 for M47 new 2nd,
    ENTRY= DDE7N47,DDE 7.0 für N47,
    ENTRY=,,
    ENTRY=ME9NG4TU,ME9.2 / MEV9 for N45 / N46,
    ENTRY= MSV70,MSV 70.0 für N52 (NG6),
    ENTRY= MSV80,MSV 80.0 for N52KP (NG6),
    ENTRY=,,
    ENTRY=EKPM60_2,Fuel pump EKP,


    [ROOT_GETRIEBE]
    DESCRIPTION=Transmission
    ENTRY= GS19,Gearbox Control Module GS19,


    [ROOT_FAHRWERK]
    DESCRIPTION=Chassis
    ENTRY= DSC_87,Dynamic Stability Control,
    ENTRY=RDC_GEN2,Tire Pressure Monitoring,


    [ROOT_KAROSSERIE]
    DESCRIPTION=Karosserie
    ENTRY= MRS5,Airbag,
    ENTRY= AHM_E65,Trailer Module,
    ENTRY= CAS,Car Access System,
    ENTRY= DWA_E65,Alarm System,
    ENTRY= SINE_65,DWA Sirens and Tilt Sensor,
    ENTRY= ZBE_E87,Ergo Commander,
    ENTRY= FRM_87,Footwell module driver,
    ENTRY= FRM_70,Footwell Module Driver II (FRM_70, from 03/07),
    ENTRY= KOMB87,Instrument cluster,
    ENTRY= JBBF87,Junction Box Passenger,
    ENTRY= JBBF70,Junction Box Passenger II (DCAN),
    ENTRY= IHKA87,Air conditioning control,
    ENTRY= PDC_E87,Park distance control,
    ENTRY=PGS_65_2,Passive go system,
    ENTRY= FZD_87,Functional center roof,
    ENTRY= RLS_87,Rain and light sensor,


    [ROOT_KAROSSERIE_SITZ]
    DESCRIPTION=Seat Modules
    ENTRY= FAS_PLX,Seat Module Driver (new),
    ENTRY= BFS_PLX,Seat Module Passenger (new),
    ENTRY= FAS_87,Seat Module Driver,
    ENTRY= BFS_87,Seat Module Passenger,


    [ROOT_KOMMUNIKATION]
    DESCRIPTION=Communication Systems
    ENTRY= MCGW60,MOST/CAN-Gateway MASK,
    ENTRY= CCCG60,MOST/CAN-Gateway CCC,
    ENTRY= RAD2_GW,MOST/CAN-Gateway Radio 2,
    ENTRY= CCC_60,Car Communication Computer CCC,
    ENTRY= CCCA60,Car Communication Computer (Application),
    ENTRY= ASK_60,Audio System Controller CCC,
    ENTRY= ANT_60,Aerial Tuner,
    ;ENTRY= SVS_60,Voice Processing System,
    ENTRY= CID_87,Central information display color,
    ENTRY= MASK60,Audio System Controller MASK,
    ENTRY= RAD1,Radio 1/2,
    ENTRY= DAB_60,Digital radio terrestrial DAB,
    ENTRY= IBOC60,Hybrid radio USA IBOC,
    ENTRY= SAT_60,Digital Satellite Radio USA,
    ENTRY= CDC_E65,Audio CD Changer,
    ENTRY= NAV_60,Navigation System CCC ECE/US,
    ENTRY= TEL_E65,Telephone,
    ENTRY= AMP_60,Top hi-fi Amplifier,
    ;ENTRY= VID_E65,Video Module,

    - - - Updated - - -

    Basically, for everything to work in INPA you need to have a correct .PRG file in EDIABAS/Ecu, a pointer in INPA/CFGDAT/INPA.ini to point to the correct SGBD variant file, an SGBD file for the variants in INPA/CFGDAT (in this case E87.ENG) and corresponding .IPO files for each variant in INPA/SGDAT. In this case, although the SGBD file for the E87 is missing the entry for your engine, the appropriate entries are included in the MOTOR.ENG SGBD file and the fact that they work from there indicates the presence of the necessary .IPO files.

  19. #19
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Hi ricky500,

    According to FAL in another forum, the ECU 'D60M47A0' is referenced by DDE6M47.IPO.

    If so, I don't think you need to edit the scripts in the CFGDAT folder as you've indicated:

    [ROOT_MOTOR]
    DESCRIPTION=Engine
    ENTRY= D50M47,DDE 5.0 for M47 TÜ,
    ENTRY= DDE6M47,DDE 6.0 for M47 TÜ2,
    ...

    Now, you should check in the SGDAT folder for the file DDE6M47.IPO.
    If the .ipo file is present, then next time in INPA for Engine script select:

    DDE 6.0 for M47 TÜ2

    Doing so will call upon DDE6M47.IPO and you should not get as many errors. You still might get the language incompatibility related message(below) initially but that is just an inconvenience that can be ignored:

    Versionskontrolle
    Nicht zusammenpassende Versionen.
    Fehlfunktion ist möglich!

    (in English)
    Checking versions
    Versions do not match.
    Malfunction possible!

    If you continue to get other communication errors, you should try searching by the error code. If you don't find a solution post the exact error message.

    Note: The reason I had to edit my script (regarding the Engine in CFGDAT) is because my original script did not include the 'ENTRY' for the .ipo file that refers to my car's engine. Of course it was handy that my SGDAT folder did have that particular .ipo file, but its name was unexpectedly quite different than the ECU model name (i.e. ECU = MEV17.2.1 / IPO file = ME17R4.IPO).
    Last edited by tinkerman; 12-21-2014 at 12:03 AM.

  20. #20
    Join Date
    Dec 2007
    Location
    Queensland, Australia
    Posts
    4,286
    My Cars
    E70 3.0sd E21 323i
    Tinkerman, adding the entry DDE50K47 to the Engine section of the E87.ENG file allows INPA to access the DDE50K47.IPO required for the new M47 engine. The way the software operates is fairly simple and is explained in the .pdfs found in your c:/INPA/Doku and c:/EDIABAS/Doku folders. Editing CFGDAT files is the simplest part of the process, but since .IPO files are compiled from .IPS files and .PRG files are all encrypted, these are much more difficult (at least for me) to modify. Fortunately as later versions of INPA have been released, BMW has done most of the legwork by providing updated .PRG files and .IPO files, but during the process has often also made many older .ENG/.GER files redundant. Sensible editing of files in the CFGDAT folder, combined with careful review of .IPO file creation dates (to confirm that they are compatible with the version of EDIABAS you are using) and judicious adding of .PRG files to your EDIABAS.Ecu folder is a great way to ensure that your version of INPA has the broadest applicable model coverage.
    When editing files in the INPA/CFGDAT/(Variant).ENG file, the ENTRY= provides the prefix of the relevant .IPO file, followed by a description of Model applicability, In this case ENTRY=DDE50K47 (.IPO) is used for DDE 5.0 with the new M47 engine.
    Probably one of the easiest ways to check the applicability of a particular SGBD file is to load it into Tool32 and read the model applicability from there.
    Last edited by David Mc; 12-21-2014 at 12:39 AM.

  21. #21
    Join Date
    Feb 2013
    Location
    Korea
    Posts
    172
    My Cars
    '07 320i E90
    Hi David,
    My previous reply to ricky500 was being written as your post #18 was being uploaded I think, so I was not intending to
    oppose your reply. Just wanted to suggest that ricky500 try the

    DDE 6.0 for M47 TÜ2

    selection for engine next time and see if it works for his car, as it is suppose to access the ECU D60M47A0 he mentioned by calling on the DDE6M47.IPO.

    Thank you for your explanations.
    Last edited by tinkerman; 12-21-2014 at 02:50 AM.

  22. #22
    Join Date
    Dec 2007
    Location
    Queensland, Australia
    Posts
    4,286
    My Cars
    E70 3.0sd E21 323i
    No worries J.J. I know that you are interested in INPA (as are we all) and just thought that I may save members from having to read the translated version of BMW's explanation of the software (it runs about 79 pages and is not easy reading!) INPA relies on responses to a predetermined set of data queries, which are model/variant dependent. This is where guys with pre-EWS vehicles run into problems as during interrogation of the car's ECU, INPA looks for a response from the EWS (which it does not get), causing the software to hang and return an error message. Tool32 is a little more flexible in that it allows some commands to be executed independently, which is how a mutual friend of ours managed to edit an .IPO file allowing a pre-EWS car to be diagnosed using Tool32 (by ignoring the fact that no response was received from the EWS, which would have caused INPA to stall).
    About the only way I have succeeded in reading anything sensible from an existing .prg file is by using a hex editor program, but without the benefit of a program like NCS dummy to allow me to analyse and calculate appropriate hex values and corresponding addresses, messing with the files would just result in an unusable file.
    As FAL has previously stated, the fact that INPA has also been used in conjunction with several versions of EDIABAS is also problematic as some functions provided for older cars under EDIABAS v6.4.3 need WinELDI to be running and EDIABAS v6.4.7 was developed without support for this structure.

  23. #23
    Join Date
    Dec 2017
    Location
    new york
    Posts
    1
    My Cars
    320i
    Hey there FAL, could you post those files again to a new site? The rapid share link doesn't seem to be working. Thanks.

  24. #24
    Join Date
    May 2019
    Location
    UK
    Posts
    3
    My Cars
    E60

    INPA Error when selecting engine

    Quote Originally Posted by macea0 View Post
    Hey there FAL, could you post those files again to a new site? The rapid share link doesn't seem to be working. Thanks.
    I have a similar problem with an E87 116i 2007 with N45 engine. INPA reports that the requested control unit is not found. Says it found ME17N45, not ME9N45 and several other variants it expects. Says program will be stopped.

    There are no other options to select for N45 engine. I can select different engines but get various errors. I am trying to diagnose a VANOS fault. Can anyone tell me if there is a version of INPA that supports this DME or if I can load or modify a file to overcome it?

    Thanks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •