[101Duck]

Hi Guys,

have downloaded the v3 VM (and seeding) and require assistance.
I gave the VM my usb port and it has assigned com3. changed latency to 1. But absolutely no success. INPA dots don't go black. need to change my VO desperately (auto to man swap) and when trying to connect in NCS i get this error.log

[22:52:49.115] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[22:52:49.115] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error FRM_87

[22:52:49.116] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.116] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ

[22:52:49.116] [2016-08-27] [SERIE] 2000 Error COAPI4.CPP coapiReadAuftrag 4
[22:52:49.116] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ: A_PL2FRX

[22:52:49.120] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[22:52:49.120] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error FRM_87

[22:52:49.121] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.121] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ

[22:52:49.121] [2016-08-27] [SERIE] 2000 Error COAPI4.CPP coapiReadAuftrag 4
[22:52:49.121] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ: A_PL2FRX

[22:52:49.124] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[22:52:49.124] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error CAS

[22:52:49.125] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.125] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ

[22:52:49.125] [2016-08-27] [SERIE] 2000 Error COAPI4.CPP coapiReadAuftrag 4
[22:52:49.125] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ: A_E65CAS

[22:52:49.125] [2016-08-27] [SERIE] 1000 Warning COAPI.CPP coapiReadFgNr 9
[22:52:49.125] [2016-08-27] [SERIE] Error CAS

================================================== ==============================(2)
[22:52:49.130] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[22:52:49.130] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error CAS

[22:52:49.131] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.131] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FGNR_LESEN

[22:52:49.131] [2016-08-27] [SERIE] 2000 Error COAPI.CPP coapiReadFgNr 12
[22:52:49.131] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FGNR_LESEN: A_E65CAS



Can anyone assist? using a green chip K+DCAN USB INTERFACE cable. car is a 07 E90 335i

[Klooney]

Were all daten files imported into the various folders ie e60 daten files imported into NFS folder etc.?

[101Duck]

Originally Posted by 101Duck

Hi Guys,

have downloaded the v3 VM (and seeding) and require assistance.
I gave the VM my usb port and it has assigned com3. changed latency to 1. But absolutely no success. INPA dots don't go black. need to change my VO desperately (auto to man swap) and when trying to connect in NCS i get this error.log

[22:52:49.115] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[22:52:49.115] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error FRM_87

[22:52:49.116] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.116] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ

[22:52:49.116] [2016-08-27] [SERIE] 2000 Error COAPI4.CPP coapiReadAuftrag 4
[22:52:49.116] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ: A_PL2FRX

[22:52:49.120] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[22:52:49.120] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error FRM_87

[22:52:49.121] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.121] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ

[22:52:49.121] [2016-08-27] [SERIE] 2000 Error COAPI4.CPP coapiReadAuftrag 4
[22:52:49.121] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ: A_PL2FRX

[22:52:49.124] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[22:52:49.124] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error CAS

[22:52:49.125] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.125] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ

[22:52:49.125] [2016-08-27] [SERIE] 2000 Error COAPI4.CPP coapiReadAuftrag 4
[22:52:49.125] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FA_READ: A_E65CAS

[22:52:49.125] [2016-08-27] [SERIE] 1000 Warning COAPI.CPP coapiReadFgNr 9
[22:52:49.125] [2016-08-27] [SERIE] Error CAS

================================================== ==============================(2)
[22:52:49.130] [2016-08-27] [SERIE] 2000 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[22:52:49.130] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) IFH-0018: Initialization error CAS

[22:52:49.131] [2016-08-27] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[22:52:49.131] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FGNR_LESEN

[22:52:49.131] [2016-08-27] [SERIE] 2000 Error COAPI.CPP coapiReadFgNr 12
[22:52:49.131] [2016-08-27] [SERIE] Error in EDIABAS or in ECU description file (SGBD) FGNR_LESEN: A_E65CAS



Can anyone assist? using a green chip K+DCAN USB INTERFACE cable. car is a 07 E90 335i

Sorted this issue out. Turns out I needed to change the USB assignment to COM1 in the system and then it connected and worked fine.

Now to work out how to make INPA in english

[SchillerM]

Thanks OP for making this!
I finally got it running after some drama (SSD died, laptop isnt powerful enough, VirtualBox USB issues on Linux).
Did some basic programming on my F10 550i, planning to do maps and few more things then focus on E90 Map updates.

Anyways, thanks again. This is what I needed to take the plunge beyond Carly (new $adapter$ needed for F chassis was nail in coffin on keeping with it).
Matt

[MooreOfDerek]

Going to test this out! Thanks so much for the time and effort put in on this project. I am new to the forum and, I am already loving the communities efforts!

Thanks again,
Derek

p.s does the SPDATEN55 support the alpina b3 tcu flash?

[jellish]

I've tried both vbox and vmware, and the image just gets to "Windows is loading files..." and then reboots. Does this forever basically. Has anyone seen this problem?

[MooreOfDerek]

How much ram does your computer have installed?

[jellish]

Originally Posted by MooreOfDerek

How much ram does your computer have installed?

Sorted it out actually. For anyone else who has this issue, I had to enable VT-x in the BIOS for the image to load properly.

[Klonone]

thanks ,fantastic work

regards

[myculito]

I could really use one's help here:

1. Using this with a green pcb k+DCAN cable I bought from Amazon here: https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

2. I have the entire file copied over to my Windows 10 PC, and running via VMWARE

3. I first made sure the cable was installed on my Windows 10 PC, and it shows up as COM4.

4. When I'm inside the image via VMWARE, I make sure the cable is selected, and device manager within the image picks it up not as COM4, but as COM3.

5. I've had a hell of a time getting this thing to work. Can someone provide some guidance here?

[SchillerM]

Not sure if this is posted anywhere in here, but bouncing between different sites and reading threads I decided this could be useful, at east to myself, so sharing.

BMW Software installed in this VM
Rheingold 3.53
E-Sys Launcher 2.5.2.100 (ESys authentication bypasser - By Tokenmaster)
ZGW Search (ENet cable Checker) V2.0.0
BMW Coding 2.5
INPA 5.0.2
Tool32 4.0.3
WinKFP 5.3.1
NCS Dummy 0.6.0.6
ISTA-P Loader 4.5.0.0
SPDATEN 55
Easy Connect Tool 1.0.5320.35550
FSC Generator 1.0.0.2
SWID Reader .1
CIC Special Service Utility 1.0.4352.42177
K+DCAN Utility 2.0
ETK 3.1.20
NCS Expert 4.0.1

Other
LibreOffice 5.1
WinRAR 5.20
CutePDF Writer (PDF Printer)
7 Zip 15.14

Please let me know if I missed anything and I will update, or if more info is desired for a certain app.
Matt

[nate16]

Originally Posted by SchillerM

Not sure if this is posted anywhere in here, but bouncing between different sites and reading threads I decided this could be useful, at east to myself, so sharing.

BMW Software installed in this VM
Rheingold 3.53
E-Sys Launcher 2.5.2.100 (ESys authentication bypasser - By Tokenmaster)
ZGW Search (ENet cable Checker) V2.0.0
BMW Coding 2.5
INPA 5.0.2
Tool32 4.0.3
WinKFP 5.3.1
NCS Dummy 0.6.0.6
ISTA-P Loader 4.5.0.0
SPDATEN 55
Easy Connect Tool 1.0.5320.35550
FSC Generator 1.0.0.2
SWID Reader .1
CIC Special Service Utility 1.0.4352.42177
K+DCAN Utility 2.0
ETK 3.1.20
NCS Expert 4.0.1

Other
LibreOffice 5.1
WinRAR 5.20
CutePDF Writer (PDF Printer)
7 Zip 15.14

Please let me know if I missed anything and I will update, or if more info is desired for a certain app.
Matt

Sounds about right! I will be releasing a V4 of this VM with the latest and greatest spdatens and pszdata. My 2017 F80 is on a boat right now coming over from Germany.

[myculito]

Anyone?

Originally Posted by myculito

I could really use one's help here:

1. Using this with a green pcb k+DCAN cable I bought from Amazon here: https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

2. I have the entire file copied over to my Windows 10 PC, and running via VMWARE

3. I first made sure the cable was installed on my Windows 10 PC, and it shows up as COM4.

4. When I'm inside the image via VMWARE, I make sure the cable is selected, and device manager within the image picks it up not as COM4, but as COM3.

5. I've had a hell of a time getting this thing to work. Can someone provide some guidance here?

[SchillerM]

Originally Posted by myculito

Anyone?

The one thing I tried when getting USB to work was just using a thumbdrive, once i could see the thumbdrive in VM all was well.
Sorry, not much more help than that..
Matt

[PichaDis11]

Originally Posted by myculito

Anyone?

Have you tried changing the com port in the VM to COM1?

Originally Posted by nate16

Sounds about right! I will be releasing a V4 of this VM with the latest and greatest spdatens and pszdata. My 2017 F80 is on a boat right now coming over from Germany.

Congrats and the new ride Nate.

[MooreOfDerek]

Originally Posted by myculito

Anyone?

Go into properties and change it to com1?

[myculito]

So to confirm, I do the following?

1. Connect the com to the machine while in Windows 10 first

2. Go into the VM, have the VM pick up the cable

3. Go into the VM device manager, and switch the cable's COM port to COM 1?

I believe I tried to do that initially, but the VM device manager said that COM1 was already "in use"

Originally Posted by MooreOfDerek

Go into properties and change it to com1?

Originally Posted by PichaDis11

Have you tried changing the com port in the VM to COM1?

[PichaDis11]

Originally Posted by myculito

So to confirm, I do the following?

1. Connect the com to the machine while in Windows 10 first

2. Go into the VM, have the VM pick up the cable

3. Go into the VM device manager, and switch the cable's COM port to COM 1?

I believe I tried to do that initially, but the VM device manager said that COM1 was already "in use"

Accept the change.

[opjose]

You can also plug the cable in, and in the VBOX settings for the VM, "add" the USB "device" found by the host O.S..

When you do so choose the option to add the detected entries.

When you start the guest VM it will find the new USB device.

It will automatically install the drivers for the interface but fail to find the serial port drivers, which are already present in the guest VM... just point the windows driver installer to the driver folder (it may be already set!), and the port will be added.

Mine came up in the VM as COM10, which I then changed to COM1 (and yes I saw the same "conflict" message).

Doing things this way has a few advantages...

- The guest VM starts up w/o needing the cable hooked up first.
- The guest VM has direct access to the USB hardware resulting in less latency.
- You can plug the adapter into different USB ports and the guest VM still detects it.

[vmhelper00]

Originally Posted by nate16

Sounds about right! I will be releasing a V4 of this VM with the latest and greatest spdatens and pszdata. My 2017 F80 is on a boat right now coming over from Germany.

Great! Hit me up for any VM tuning needs.

[myculito]

That worked, thank you!

Originally Posted by opjose

You can also plug the cable in, and in the VBOX settings for the VM, "add" the USB "device" found by the host O.S..

When you do so choose the option to add the detected entries.

When you start the guest VM it will find the new USB device.

It will automatically install the drivers for the interface but fail to find the serial port drivers, which are already present in the guest VM... just point the windows driver installer to the driver folder (it may be already set!), and the port will be added.

Mine came up in the VM as COM10, which I then changed to COM1 (and yes I saw the same "conflict" message).

Doing things this way has a few advantages...

- The guest VM starts up w/o needing the cable hooked up first.
- The guest VM has direct access to the USB hardware resulting in less latency.
- You can plug the adapter into different USB ports and the guest VM still detects it.

[335Owner]

Hey everyone, i downloaded and got the VM, but every time i try to start it using Virtual box 5.0.8 it just reboots. It gets to the initial screen 'Windows is loading files' with the progress bar at the bottom. Straight after that it reboots and does it all over again. Did anyone else have issues trying to boot up the VM??