Thursday, June 20, 2019

WinKFP Expert - What is 0da & 0pa?

So i'm updating a DME module with winKFP
There are circumstances that are forcing me to update the module using the expertmode in winkfp.
I end up flashing 2 files: a program file and a data file (0pa and 0da).

What i would like to know:
- What is the definition of a program file? What does it do with the DME? What kind of info is stored in this file?
- What is the definition of a data file? What does it do with the DME? What kind of info is stored in this file?
- What is the relationship between the above files? Can they be interchanged? Is it possible to flash 1 of the above without flashing the other one?

Kind regards.

The file 0pa corresponds to HARDWARE NUMBER and the 0DA is SOFTWARE NUMBER.

The content contains the vehicle information and cartography, you can open them with notepad to have a preview of the content.

How to flash FRM3 in ISTA-P expert mode?

So I got FRM3 that has wrong flash in it due it being fixed. Comfort mode won't flash the correct ZB. So how do I do it in expert mode? 

OK, here are the steps....

Go to the data file for your FRM3 in C:\BMW\ISTA-P\BMW\Services\data\ecudata\E89\data for example, open the FRMR3 folder. 
Look for a file 9249091.opa 
If you don't find it open the .his file in notepad and look for this number on the left, then pick the new number on the right and continue till you have the latest file. 
That latest will be the correct latest .opa based on your datens.

Create a develop folder in C:\EC-Apps\NFS\DATA. In that folder copy the .opa file from above.

Open coapi.ini file in C:\EC-Apps\NFS\CFGDAT. In that file write your opa name as below
ZBNUMMER = xxxxxxx
SWNUMMER = xxxxxxx where X is the .opa or ZUSB no.

Now open comfort an emulate an update then note the P-ABD and P-SGD nos. Also note the ECU address.

Go to expert mode and load the three above and program file, load your vin and then program program file only. In configurations enable boot sector update and UIF update

Try it we see. Takes a few steps to get expert mode going.

Sunday, July 15, 2018

BMW F series Information correction of maintenance history

Information correction of maintenance history in the f bodies with system-Evo System

Wednesday, June 20, 2018

BMW G30 Retrofit ICAM

BMW G30 Retrofit ICAM  (icam)

HU_NBT_EVO > EXBOX 3001 > CAM_ECU = wert_25 
HU_NBT_EVO > EXBOX 3001 > CAMERA_SYSTEM = icam2_rvc 
HU_NBT_EVO > EXBOX 3001 > MACRO_RV_C = aktiv 

TRSVC - aka ICAM in REINGOLD\ISTA (always displays and when rear view camera 3AG and when cameras 5DM and 5DN)

E_Sys ICAM4 for G-ser

Tuesday, April 17, 2018

How to install E-sys 3.30.0 with Java 32 bit

Free download BMW E-sys 3.30.0  software:

How to install E-sys 3.30.0 with Java 32 bit:
For flashing failure risks to minimize, you need as much JAVA memory as you can have.
E-sys 3.30.0 comes standard with Java 32 bit, maximizing usable memory to 2Gb (actually less, because runtime uses lots of Mb’s as well. Thx Tokenmaster).
Default setting in E-sys 3.30.0 is 1024Mb. You can change it (in esys.bat; thx Shawn)to about 1500Mb. If you set too high, E-sys won’t start anymore. Just trial&error.
If you want more usable memory to further reduce memory related flash failures, upgrade Java to 64bit:
1. Download/Install vcredist_x64.exe (see link)
2. Download/Install JRE 8 x64 (see link)
3. Delete JRE folder in c:\EC-apps\ESG\E-Sys\jre
4. Rename just installed JRE 8 x64 folder(c:\Program Files\Java\jre1.8.0_144) to JRE and move to c:\EC-apps\ESG\E-sys\jre.
5. Change memory setting in esys.bat:
:set OPTION_MEMORY=-Xmx3000m (or 2048 or 4000 or whatever)
6. Run E-sys and close E-sys
7. Open last LOG file in c:\Data\Logs\
8. Search for : “Java (max)” Without quotes to check your present max usable memory
9. Use E-sys software with decreased flash failure risks
For me this was solution for NBT flash issues!

BMW ENET E-sys 3.30.0 Feedback

BMW ENET E-sys 3.30.0 review: 
I tested it by psdzdata 3.62.1 for coding and programming ok.
But for FDL coding, because CAFD was trimmed,so refer to launcher+E-sys 2.8.1+psdzdata for reference,for example “startup_emblem” countered the 32th from bottom of 3001,in the “Ausgelesen” of “Werte=00”,changed to “01”,so got the error:
“Failed to sign FDL[C158],EstCmCryptgraphicExcetion:SignHandler can not be initialized with data from EST.
For FDL Coding, E-Sys Launcher provides both an .EST Token Solution for signing Coding Changes, and CAFD Mapping to add back in and display the Trimmed Data.
You do not have .EST Token solution, so you have EST error. So, either a real BMW AG .EST Token file is needed or E-Sys must be patched to accept a non-OEM .EST Token file.
Beyond Token, you also need either Untrimmed PSdZData from BMW AG’s vault. Without Untrimmed PSdZData, you can resort to “counting” method as you did, or similarly using FDL Storage Info (Address and Bitmask), which spares you the counting, but both methods are tedious and make the assumption that Current CAFD versions FDL Code structure is same as previous version, an assumption that is not always true. Without Untrimmed PSdZData, FDL Coding is best left to older E-Sys 3.23.4 / 3.27.1 / 3.28.1 and E-Sys Launcher.

Monday, March 5, 2018

E-sys launcher 3.27 on VMware 2018 solution

This is in no way to frustrate developer, but with very little reply from TM or no reply at all we still need to code our bimmers, so this is offered as a temporary solution for FREE

Download both files:
Note that pszd v63 lite included for coding
Install VMware which is already set with 2016 date.

After installation of VMware place folder "Windows 7 x64" to user\documents\Virtual Machines\