Free Download Ncs Expert Ediabas

What is BMW Coding?

Download ALL BMW EDIABAS INPA NCS Expert WinKFP ESYS ISTA June 10, 2017 sales 0. BMW INPA 5.06 + EDIABAS 7.3.0 + NCS Expert 4.0.1 + WinKFP 5.3.1 + BMW Coding Tool V2. NCS Expert is included in the INPA package listed above. NCS Expert is easy to install (if you already have INPA working, NCS Expert will work too, with no further changes). Can code dozens of options in every module in the car (e.g., the automatic door locking at 5mph in the General Module). EDIABAS 6.4.3 – UPDATE. INPA 5.0.1- UPDATE. NCS Expert 3.0.8 – Complete. Then Press continue to start installation and press End to exit the installation. Step4: Run the file “03Setup3 INSTALL Instprog.exe”-1)Then Choose English, press continue, press continue again. Free download BMW Tools 2.12 for K+DCAN cable. Download BMW tools 2.12 this will give you updated NCS Expert @ v3.1, EDIABAS 7.2, and winkfp 5.1. This is so you don't have strange errors and so you can code your car back to default using the 'expert mode profile.' Help needed with NCS Expert.

BMW Coding is used to customize settings so a vehicle operates more as the individual desires.It is a really great way to customise your car, and enable features that the car didn’t have from factory, but it’s also very easy to screw things up!

What Tools you need for BMW Coding?

E-Series & R05x Mini:

*Interface = K+DCAN Cable (OBDII to USB) or ICOM

*ECU Data Files = SP-Daten

*NCS Expert = Coding Software

*WinKFP = Programming (Flashing) Software

*EDIABAS = Low Level ECU Communication Software used by NCS Expert & WinKFP

Fxx- / Ixx- / Gxx-Series, Mini (F05x/F06x), & Rolls-Royce:

*Interface = ENET Cable (OBDII to RJ45 Ethernet) or ICOM

*ECU Data Files = PSdZData

*E-Sys = Coding Software

*E-Sys = Programming (Flashing) Software

*ICOM A: main interface

*ICOM B: adapter for programming multimedia in E series

*ICOM C: adapter for old BMW with round 20 pin diagnostic plug

*ICOM D: adapter for motorcycles

BMW Coding Risk:

Just like jailbreaking an iPhone or any software mods, the warranty of the vehicle could be voided by coding. After all, it is a third-party intervention to the computers of the car, without the manufacturer’s approval. There is a risk that some systems might get broken if the operator does not do everything properly. Car coding should never involve an “I’ll just wing it” strategy.

There is also a risk of permanent damage to a vehicle’s electronic systems. In the worst cases, one of the car’s computers could receive irreparable harm and require replacement.

In most cases,it is safety to coding for you BMW.And before you coding,you would better to ask some question or search the features you want on google.There are many BMW coding forums,join them to talk about the coding topics.

Here are some BMW coding forums:

BMW F Series Guide:

BMW E-sys Software:

BMW F Series Coding & Reprogramming Knowledges:

BMW F Series Coding & Reprogramming Cases:

BMW E Series Guide:

Keep updating…

Here’s a user solution to change odometer from miles to km on BMW E-series by using NCS Expert step-by-step. Instruction: Part 1 – NCS Expert read miles 1. Connect your cable (BMW cable or emulator) to your vehicle’s OBD II port and to your computer.

Your vehicle’s ignition should be in the ON position, but your engine does not need to be running. Launch INPA and verify that it reads Battery: ON and Ignition: ON. You should also have a program called “EDIABAS Server” running in your task bar. If everything checks out, close INPA.

Hello guys i have nsc expert with only expertenmodus profile. I need the other profiles like revtor's; fister. Ncs expert profiles needed. May 15, 2017. NCS Expert will NOT run on a 64-bit operating system. This blog will guide you how use NCS Expert and cheap BMW INPA K+DCAN USB Interface to code E90 335i 2008 Digital Speedometer! Here you can download free INPA 5.02 and Ediabas 6.4.7 and check the installation guide step-by-step.

Leave the server running. Open “C: NCSEXPER WORK” and create an empty text file named “FSW_PSW.MAN”.

I just use NOTEPAD for this. Launch NCS Expert. Go to File ->Load profil and select “Revtor’s NCS Expert Profile”, click OK. Select “VIN/ZCS/FA” then “ZCS/FA f. This will tell NCS Expert to attempt to read your VIN from your vehicle’s ECU so you don’t have to type it in.

Select your chassis from the list and click OK. Then select which module you want NCS Expert to read your VIN from. Usually the first choice is fine. Click OK again to have NCS Expert read your VIN. You should see the CHASSIS, FG, and FA fields populated in the top part of the NCS Expert window. Select “Back”, then “Process ECU”.

You will be prompted to select a module. Select the module you want to read values from(in this case KOMBI OR AKMB) and click OK. Click OK again on the window that appears to return to the main NCS Expert window.

Select “Job” and choose “CODIERDATEN_LESSEN” from the menu. This will change the job from one that writes to one that only reads data. Many of the job names look very similar.

Always read job names carefully to ensure you select the correct one. At this point NCS Expert is relatively harmless, as all it can do is read from your car. Select “Execute job” to begin reading from your selected module. When you see “Coding ended” below the module name, the process has completed.

Once NCS Expert has read data from a module, it stores that data in a file called “FSW_PSW.TRC” (called a “trace file”) in the “C: NCSEXPER WORK” folder. This file contains some general information about your car, as well as all the values currently stored in the module you read from. Part 2 – NCS Expert write odometer from miles to km • Open “FSW_PSW.TRC”(you can use NOTEPAD) and find the field you wish to modify. Trace files are formatted as: FIELD_NAME field_value 2. Change the field value(s) to your desired settings(this is where you look for the WEG_EINHEIT field name, and change value to “km”), then save this file as “FSW_PSW.MAN”, overwriting the empty one you created earlier.

If you closed NCS Expert, follow steps 1-6 in the section above to get back to the correct screen. Otherwise, NCS Expert is ready to code your module as soon as the job is changed back to the default, “SG_CODIEREN”. Do this by selecting “Job” and then “SG_CODIEREN”, then click OK. Verify that the correct job appears in the “JOBNAME“ field. Click “Execute job” to have NCS Expert write the information from FSW_PSW.MAN to your vehicle. When you see “Coding ended” below the module name, the process has completed.

Depending on what you coded, you may need to turn your car off and back on again to verify the desired feature/behavior has taken effect. Open “FSW_PSW.MAN” and delete its contents. Save and close the file. That’s all about BMW E series odometer change, from miles to km, using coding software. Hope it helps!

Note: I do not hold any responsibility if you damage your car. DIY Guide to Flash Alpina B3 Flash: WARNING.If you don‘t know what your doing, dont be brave and blindly go into this advanced flashing of software into the TCU module. If your not too confident in doing this, either pay someone or just do without it.WinKFP is a very dangerous tool but yet its awesome and in terms of coding its pretty advanced. Proceed after reading this warning if you choose to do so. This flash will make the transmission run smoother, gear change will be more precise and crisp, rev match downshift is unbelievable, rev limiter is increased and overall driveability is increased. You will have a new indicator for gear selection in D mode which display D1, D2, D3,D4, D5 and in DS mode you will see S1, S2, S3, S4, S5 and the same for the M mode.

This single flash will make the car change gears more refined and crisp. You will no longer feel the lurching when the tranny shifts and it goes through the gears without even the slightest hesitation. It is indeed a must have flash if you own a E9x with a N54 engine. This Alpina TCU flash works for model years 3/07 till present N54/N55 engine (some N55 engines which are rare, exhibit the rpms jumping down to zero on each shift but acts normal in every other way.This can be addressed if you update your DME version if you have this erratic rpm issue after flash). If your production date is before 3/07, your out of luck and cant flash your car! Before you attempt this you should have some knowledge in coding and setting software. You need to confirm INPA software is working and communicating with car.

If you dont have INPA communicating, dont move beyond this point and go back and do some more research on getting it to work. There are plenty of DIY guides for setting up INPA, Ediabas, NCSexpert and WinKFP, You can purchase a proven INPA K+dcan cable that works. Once you have configured your laptop properly with INPA, NCS expert and WinKFP, you need to download Spdaten 53.0 which I have provided a link to download a condensed form for the strict purpose of this Alpina flash. The link for the SPdaten 53.0 is not the entire version and doesn't have the other data files needed to flash other modules if you need them, this is strictly for Alpina flash which makes the download much quicker. If you failed to download link, you can also buy hard drive containing INPA, Ncs expert,winkfp etc for BMW ICOM. Follow the guide how to import the SPdaten 53.0 data into Winkfp by downloading the PDF I have provided below.Once you have the data imported into Winkfp then you need to configure the Winkfp.follow this Once Winkfp is configured correctly your ready to begin the flash of your new Alpina B3 software into your car!!

IMPORTANT.For those using Procede or JB4 make sure the tune is set to VALET map 0 before you start the flash. Here we go: -Make sure your battery is good if not get a battery charger -Open drivers door and turn ignition ON (cluster guage on) Basically hit the start button twice without starting car. Recently, I just bought an BMW Icom D interface from obdii365.com; thought it has the KL15 problem, so I decided to rearrange all wires by myself. And luckily, i managed to use K+DCAN Cable & ICOM D for BMW Motorcycle diagnosis.

Device i used: interface K+Dcan USB cable (but i suggest BMW motorcycle scanner if you don’t mind the price, for it’s a more professional motorcycle diagnostic tool) Here are the steps that I have been following: 1. I cut all the big wire 2.

I used a multimeter in order to get the relationship between the pins and wires. I used continuity function. I ordered a female OBD2 ( cable and Vagcom cable both ok) because I broke mine trying to eliminate the plastic housing 4.Then i used this configuration below: Universal K-Line & CAN BUS Adaptor (K1600) Signal OBDII Socket BMW 10 pin Plug K1 15 (Ignition On) 1————————————————–10 Ground 4&5————————————————-4 CAN Hi 6—————————————————–7 K-Line 1 (BMS) 7—————————————–1 K-Line 2 (ABS) 8——————————————2 CAN Lo 14—————————————————–9 KL 30 (Bat+) 16—————————————————–6 How to setup bmw inpa K+Dcan cable? Notes 1/ Dependant on the software, model & adaptor cable used it may be necessary to invert RI # and DSR signals to for detection of battery and ignition as per the VAG KKL cable. 2/ This cable & access through the diagnostics port is yet to be tested INPA software Installation 1/ If the cable is supplied without drivers & utilities download them from FTDI 2/ Install driver Plug in cable, WinXP will find cable, point to directory with drivers, windows installs. 3/ Set the USB Serial port parameters /MyComputer/Properties/DeviceManager/Ports(Com&LPT/SerialUSB/Advanced Set the Latency timer from default 16 msec. To 1 msec Check USB Port No matches Port No set in INPA/EDIABAS (OBD2.ini) 4/ Install Mprog & modify the programming of the eeprom FT232RL We need to invert RI # and DSR # signals to fool the detection of battery and ignition.

After programming check your I/O Control settings, they must be: #C0 = RXLED #C1 = TXLED #C2 = POWERON #C3 = PWRON #C4 = SLEEP Invert RI ticked Invert DSR ticked Save settings How to setup ICOM D adapter？ 8 pins fitted but in wrong pin No’s Pin 01 – Vi/Sw Pin 02 – Sw/Rt Pin 04 – Ws/Ge Pin 05 – Ws/Bl Pin 07 – Ws Pin 08 – Gn/Ws Pin 09 – Br Pin 10 – Gn We need pins 1,2,4,6,7,9,10 (Pins 7 & 9 are K1600 CAN Bus) Plug with bike socket. Here is the customer solution to make ICOM Rheingold engineer software with BMW interface. Put it here for sharing. Disclaimer: This is a customer solution, so obd365 is not responsible for this.

Experienced skills are required here, or you would be at risks to have a try. Backgroud info: The customer did with KDCAN cable from China. It worked good with INPA on vmware xp sp3 and saw connected car (BMW E39). But when he tried to use BMW ICOM, it cannot see/ recognize the car. PCB of this cable looks that: Useful solution by he tried: In Rheingold, he clicked on the wrench key logo (settings), then clicked on VCI Config and selected the first option as shown here: The adapter was only bridging pins 7 and 8, so he was advised to go ahead and solder them together as shown here: And after soldering, it works!!! Rheingold and K+Dcan cable can recognized and diagnose BMW E39. Several versions of BMW INPA diagnostic software are available on the aftermarket.

Here obdii365.com share INPA 6.4.3, 5.0.6 and 5.02 free download links with you all. Free download BMW INPA + NOTE: Most INPA software above are shared by forum members. Here obdii365.com introduces 2 ways of installing Ista-D Rheingold based on our customers’ experience. The first is if you have a proper installer (msi) and the second i call spoog en plak. The proper installer is if you are running the whole package Ispi, Ista-D and Ista-P, KSD and ETK etc. So it will work like the dealer software where everything is linked together with ISPI.

Spoog en Plak is if you are just running ista-D If you have down loaded the MSI and only running ista_D forget about it. Just download base file in my previous post in this thread. Delete the previous version 2.

Run RGCleaner 3. Unzip base files to program files 4. Using 7Zip extract SqLiteDbs to Rheingold folder. Send shortcut to desktop and run program 6. The License file is in Rheingold folder to register If you are running Ispi and need to update you first have to modify the MSI Installer with Here is a new update As for Iceman007 comment on E46 I normally get the BMW cable with the switch- it makes life easier.

You can buy or build an adapter cable that will join pin 7 & 8. The E46 was more K-Line so for communication pin 7 & 8 must be joined.

It is by downloading very large files from various places. Here is a version on torrent. As requested KSD and ETK http://blogs.rediff.com/eobd2/2016/02/27/2-ways-to-install-bmw-icom-ista-d-rheingold/. I bought my e90 325d 2007 with unnervingly clean exhaust tips and shortly after having DPF warning light come on. I drove 1,000km later still on and even after thrashing for miles on the motorway. Checking engine temp was above 75c etc etc – no joy.

I did an extensive research, and finally enabled the car to perform a regen, with the help of Inpa K+DCAN USB cable. In fact I think Any BMW code scanner will do. If interested this one I bought: Car won’t perform re-gen if • Engine temperature does not reach over >75c, and stay over this for a period of time (20/30 mins) • Some Fault codes are stored – Mainly and Ironicly the DPF fault code itself. • Over 20 Litres of Fuel in tank (I half filled the tank for good measure) Preparation Firstly I installed inpa software on my laptop.

The software is in a mini dvd that came with the package. I read fault codes and cleared them. Within a few miles drive I plugged in and checked again, they where back. I guessed these codes where stopping the car regenning and it was stuck in a loop.

How to do the BMW PDF re-gen – I engaged the engine temp in hidden OBC so i could see temp. – Plugged in laptop to car (battery fully charged) – Went for drive on M5. – Engage Cruise Control – Adjust car to over 50mph so engine temp runs at over 75 – my temp was reading 76 to 79 – Every 10’seconds clear the fault codes or take a passenger and get them to keep hitting the clear button on your fault code scanner. – Look at your OBC temp reading. – After about 10 miles my temp started rising and peeked at 93c, this is DPF doing its thing. – Rear view mirror = sooty clouds occupied by eggy smell later. – Exhaust tips sooty.

I suspect the EGR thermostat was the initial culprit but once it throws the DPF warning fault codes keep the car stuck a loop. I noticed the car was storing the dpf code before it was reporting it on the dash when i was driving too.

So the need to keep clearing codes obsessively when driving. Hope this helps any E90 owners.

NCS Dummy - Taking the expert out of NCS Expert NCS Dummy should make life with NCS Expert a bit easier. NCS Dummy parses keyword trace files ( FSW_PSW.TRC) or nettodata trace files ( NETTODAT.TRC) and retrieves all possible parameters, control unit data and order options for each function. The parsed trace files can be viewed and modified in a graphical trace editor or exported to text files. NCS Dummy can be used to compare two trace files and show the differences. Furthermore NCS Dummy can disassemble and assemble NCS Expert data files to achieve functionality that is not possible with a stock NCS Expert installation.

(626 kB) (1.34 MB) (1 kB) (1 kB) Requirements: • Microsoft Windows XP or later • Microsoft.NET Framework 3.5 Service Pack 1 () or Microsoft.NET Framework 4 () • Minimum display resolution of 800x600 for Windows XP/2003, 1024x768 for Windows Vista/7/8/10 (at 96 dpi - higher dpi settings require higher resolutions) • Local or remote access to the NCS Expert 'DATEN' folder If you find bugs or experience any problems with NCS Dummy, please let me know in this thread or contact me. When reporting bugs, always include the NCS Dummy log (right click on the log and select 'Copy Log' from the menu to put the entire log on the clipboard) and if applicable the keyword trace file ( FSW_PSW.TRC) or nettodata trace file ( NETTODAT.TRC) you are trying to parse. Please keep this thread on-topic - NCS Dummy only!

Questions concerning where to get or the usage of NCS Expert, what parameters to change to achieve certain functionality on your car. Will not be answered. Since this message is updated with each new NCS Dummy version, posts further down the thread may refer to older versions and are perhaps outdated or even incorrect for the current version. What's new since the last release?

• 0.6.0.7 (2016-02-18) • Fixed broken quick selection on chassis and module dropdowns by typing first letters. • 0.6.0.6 (2016-01-01) • Fixed layout issues on window rotate and aero snap (Windows 7 and later). • Fixed Hex Trace Viewer having incorrect window size on high-DPI displays. • Fixed backspace key accidentally opening Hex Trace Viewer when a nettodata trace file is loaded.

• Dramatically improved responsiveness of scrolling in the graphical trace editor with touchpad or touchscreen. • 0.6.0.5 (2015-11-21) • Fixed bug in assembly tool. The 'BESTELLUNG', 'KUNDENDIENST', 'ZEIT' and 'ZEITALT' fields in *AT.K00 files were not processed correctly. • Added file name prediction for opening disassembled DATEN files. • Added most recently used files to all 'Browse.' Button dropdown menus on the 'Modules and Traces' and 'Disassembly and Checksums' tabs and to the NCS Expert DATEN folder on the 'Options' tab.

• Added support for searching on whole words for order options in the find window. • Added warning when exporting to a FSW/PSW trace file if changes have been made that cannot be represented in the FSW/PSW format. • Added HEX trace viewer to display the hexadecimal layout of nettodata trace files. • Restored compatibility with Microsoft Windows 2000. May break again in the future. • 0.6.0.4 (2014-11-15) • Improved 'HEX/DEC' button functionality.

Clicking the button toggles between hexadecimal and decimal. Clicking while holding SHIFT toggles between hexadecimal and binary. The context menu which gives access to all three numeral systems at once can still be accessed by right-clicking the button.

• Small number of new interpreted values. • Small number of new and corrected translations. • 0.6.0.3 (2014-11-05) • Added 'HEX/DEC' button to switch the numeral system between hexadecimal, decimal and binary for control unit data and mask. Decimal values are shown in blue, binary in green. • Added command line argument /tracefile= to load trace files.

This may be useful to those who want to assign the *.TRC and *.MAN extensions to NCS Dummy. It is recommended to name your trace files to a CHASSIS-MODULE-FILENAME.TRC structure so NCS Dummy will automatically set the chassis and module. For example: NcsDummy.exe /tracefile='C: NCSEXPER WORK E31-EKM.C25-FSW_PSW.TRC'. • Corrections to interpreted values.

• Small number of new and corrected translations. • 0.6.0.2 (2014-07-26) • Fixed nettodata quick export functionality not properly checking for invalid parameter data. • The graphical trace editor now shows interpreted values where the conversion is known. • Support for Microsoft.NET Framework 4.* so version 3.5 no longer needs to be installed on modern operating systems. • Added shortcut keys and context menu entries for copying and pasting in the chassis and module dropdowns. • Improved scrolling into view of functions and parameters when searching in the graphical trace editor. • Small number of new and corrected translations.

• 0.6.0.1 (2013-08-07) • Fixed 'MaxDropDownItems' crash at very high display resolutions. • Fixed broken shortcut key CTRL+C to copy a single line from the log. • Added the more familiar shortcut key F5 as an alternative to CTRL+ENTER to reload dropdowns and path textboxes. • Shortcut key F3 to find the next search item now also works when the focus is not on the graphical trace editor. • Searching in the graphical trace editor now scrolls the entire function into view (if possible) instead of only the found item. • Find window opens automatically after successfully filtering modules by keyword or order option. • Small number of new and corrected translations.

• 0.6.0.0 (2013-02-03) • Completely redesigned user interface. All user interface changes would make a list larger than the combined change logs of all previous versions. Listed below are just the highlights. • Resizable and maximizable application window. Window size and location are saved between sessions. • Moved the graphical trace editor to the 'Modules and Traces' tab and removed the 'Trace Editor' tab. • The graphical trace editor is now also used to display module contents or changes between trace files.

• The graphical trace editor is no longer sorted alphabetically but exactly as defined by the module description files. Together with the addition of groups this should make the trace editor contents much more logical. • The graphical trace editor now shows the complete module contents for nettodata trace files or all functions in the module for FSW/PSW trace files. Belajar Bilangan Biner Pdf Converter on this page. Items that do not occur in the loaded trace file are shown in a disabled state, but can be enabled and included in exported trace files. • Many 'Browse.' Buttons have now dropdown menus with shortcuts to useful functions. • 'Path to NCS Expert DATEN folder' moved to 'Options' tab.

• Second trace file input field hidden by default to save space for the graphical trace editor. To compare trace files either use the trace file 1 'Browse.'

Button dropdown menu or unhide the second trace file input field on the 'Options' tab. • Checkboxes to export translations, control unit data and order options moved to the dropdown menus of the 'Chassis Functions', 'Module Functions' and 'Trace Differences' buttons. The settings are saved individually for each button.

• Usage of order options is now enabled by default. This has a severe impact on the loading times of large chassis (like E60 and E89). If you think this is unacceptable disable 'Load order options' on the 'Options' tab but keep in mind you miss out on a lot of information. • Removed functionality to export function, parameter and option keyword lists. For those who used this to find the highest keyword identifier, the disassembly tool will now automatically add a commented entry with the next highest identifier at the end of disassembled keyword lists.

• NCS Dummy now follows the system font and has improved DPI awareness. Since Windows Vista/7/8 use a slightly larger font than Windows XP/2003 the application is scaled larger on these operating systems.

This has a negative effect on the available space for the graphical trace editor. For users of small displays command line argument /smalldisplay was added which decreases the font and log size to maximize the available space for the graphical trace editor. • The registry path where NCS Dummy stores its settings has been changed to HKEY_CURRENT_USER Software revtor NCS Dummy.

• Remember last loaded chassis between sessions (can be disabled on the 'Options' tab). • Filter modules by keyword or order option. • Filter modules by FSW/PSW or nettodata trace file. • Add parameters to functions from within the graphical trace editor and update the actual NCS Expert data files with the changes. This should greatly reduce the need for manual disassembly and assembly.

Backups are created on the first change and can be restored from within NCS Dummy. • Multiword functions are now linked. All changes to a multiword function are duplicated in its counterpart. • Ability to search backwards in the graphical trace editor by holding the SHIFT key while searching. • Ask to empty FSW_PSW.MAN trace manipulation file on application exit (can be disabled on the 'Options' tab).

• 10000+ new translations. • Small changes to the output of disassembled DATEN files (formerly called Ediabas files). Files disassembled with previous versions are not compatible with this version. • Checksum updater for ZST files. • Checksum updater for WinKFP/NFS files. • 0.5.0.5 (2011-11-07) • Fixed bug in disassembly tool.

The 'AUFTRAGSAUSDRUCK' field in *CVT.000, *SGET.000 and *SGVT.000 files was not processed correctly. • Drag and drop support for file path textboxes. • 0.5.0.4 (2011-11-02) • Fixed bug in trace editor tree view.

In some cases the tree view failed to render properly on Windows Vista and Windows 7 systems. • 0.5.0.3 (2011-10-26) • Fixed bug in trace editor nettodata export.

In some cases the exported nettodata trace file contained incorrect addresses. • 0.5.0.2 (2011-09-01) • Default text export folder. When set, NCS Dummy will use the specified folder as default export folder for text files instead of the WORK or DATEN folder. • Find by parameter keyword in the trace editor now works. • DPI awareness.

NCS Dummy will now scale correctly on displays with a dot pitch different from the default 96 dpi. • Improved usability on very low resolution displays. The application will now calculate the available screen space and if necessary resize and reposition itself accordingly. • 0.5.0.1 (2011-08-27) • Find functionality for the trace editor. You can search on keyword, hexadecimal data, address or order option in the currently loaded trace file. Use shortcut key CTRL+F to open the find window. • Small changes to the disassembly output.

Please note that even though the changes are subtle, files disassembled with previous versions are not compatible with this version. • 0.5.0.0 (2011-06-14) • Use of background threads. Long operations are now performed on a background thread which keeps the user interface responsive. Progress is indicated by a progress bar in the header of the application. • New parser for NCS Expert data files. It turned out the new parser introduced in version 0.4.0.0 did have some issues left.

• Support for all types of nettodata trace files ( NETTODAT.TRC). The previous version only supported nettodata trace files with single byte data values. • Support for the partially corrupt NCS Expert data files KMBI_E38.C12 and ARS.C0E. • Strict mode for the parsing of keyword trace files ( FSW_PSW.TRC) in which no unresolved keywords are allowed.

This feature can be turned off in the options. • Cross references to the order options. When enabled, NCS Dummy will now include the order options for each parameter (if available).

This should be a tremendous help for the otherwise meaningless 'wert_01', 'wert_02'. The cross referencing is CPU intensive and may cause slow downs on slower machines for the E60, E65 and especially the E89 chassis. • Graphical trace editor.

When a keyword trace file ( FSW_PSW.TRC) or nettodata trace file ( NETTODAT.TRC) is loaded, a new tab 'Trace Editor' appears. In the trace editor you can view and modify the trace file. When starting from a nettodata trace file you can even add custom parameters. Now you no longer have to do all the hexadecimal mask calculations by yourself.

NCS Dummy does everything for you. • Disassembly and assembly of NCS Expert data files. Ever wondered what is in the NCS Expert data files or perhaps you even wanted to modify something? The functionality can be compared to the 'data2txt' application by 'russiane39'.

Please note that while the syntax is similar, it is not compatible. • NCS Dummy now stores its preferences in the Windows Registry ( HKEY_CURRENT_USER Software revtor software NCS Dummy ).

• Ability to set a custom text editor to open the exported files into. • Automatic check for newer versions of NCS Dummy and/or the translations at startup. For those concerned with their privacy, the feature can be disabled in the options, but all it does is downloading which contains the latest version number and translations date. No data is sent from your computer to the server. • Check for the correct Microsoft.NET Framework version at startup. This was already implemented in 0.2.1.1 but somehow got lost in 0.4.0.0. • Many, many other small improvements.

• 0.4.0.0 (2010-11-05) • New and much improved parser for NCS Expert data files. The old parser used masks to locate and identify data, whereas the new parser truly interprets the data file format. No more guessing. • Ability to display control unit data: This feature may be of use only to a small number of users, but it's what makes NCS Dummy extremely powerful.

NCS Dummy can tell you what data to expect at a certain address location in the module's coding memory and to a limited extent also what it means. This is a great aid if you intend to write custom data to a module to accomplish features impossible with the classic FSW_PSW.MAN trace manipulation. • Support for nettodata trace files ( NETTODAT.TRC): Because the new version is able to handle control unit data, it can also parse nettodata trace files.

Nettodata trace files often contain more information than the dumbed-down keyword trace files ( FSW_PSW.TRC). Nettodata trace files are a more reliable representation of the control unit's coding. Keywords may change between NCS Expert DATEN versions, but the binary data always remains the same.

• The new version maps nettodata and keyword trace files against the NCS Expert module file. The old versions used the module file only as reference and ignored them for trace differences. That makes the new version less tolerant for module version mismatches.

Make sure you select the same chassis and module as used in NCS Expert to generate the trace file. You can still compare trace files from different modules, but expect a lot of unresolved functions and parameters. • Automatic detection of chassis and module from the keyword or nettodata trace file name. If you rename your trace files to a CHASSIS-MODULE-FILENAME.TRC structure (for example E31-EKM.C25-FSW_PSW.TRC), NCS Dummy will automatically set the chassis and module (chassis E31 and module EKM.C25 in the example).

This should save time when working with many trace files. • Full export functionality for the second trace file.

In previous versions the second trace file could only be used for the differences. • 0.2.1.1 (2010-09-01) • NCS Dummy no longer uses a hardcoded list of supported chassis, but scans the NCS Expert DATEN folder for chassis instead. • Check for the correct Microsoft.NET Framework version at startup. • 0.2.1.0 (2010-07-07) • NCS Dummy now supports all known chassis: E31, E32, E34, E36, E38, E39, E46, E52, E53, E60, E65, E70, E83, E85, E89, K24, R50, R56, RR1 and derived chassis. • Support for translations of function and parameter keywords in the exported files.

• 0.2.0.11 (2010-07-02) • Added support for chassis E60. • 0.2.0.10 (2010-06-30) • Added support for chassis E89. • After a successful export you can now double-click on the log line to open the exported file immediately in the system's default application for text files. • 0.2.0.9 (2010-06-28) • Added support for chassis E85. • Improved NCS Expert data file parser. • 0.2.0.8 (2010-06-27) • First public release.

Because of numerous user interface changes in NCS Dummy 0.6.0.0 many instructions and manuals referring to NCS Dummy will have to be updated. Sorry about that but the new user interface should make the application much easier and faster to use. Code: FUNCTION KEYWORD ADDRESS (LENGTH) MASK PARAMETER KEYWORD DATA MASKED ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ SPEEDLOCK_X_KMH_MIN_C0E 00300017 (01) FF nicht_aktiv 00 00 8_kmh 08 08 3_kmh 03 03Sometimes the control unit data can also be helpful understanding meaningless parameter keywords like 'wert_01' and 'wert_02'. In the example below function 'MIND_ANZ_ZYKL_TIPP_BLK' has two parameters but the keywords are not descriptive as in last example.

However in this case the function keyword reveals what the data represents: 'MIND_ANZ_ZYKL_TIPP_BLK' or 'Mindestanzahl Zyklen Tipp-Blinken'. In English that is 'Minimum number of flashes for one-touch turn signals' (don't worry; there are translations for this one in NCS Dummy).

With one-touch turn signals the indicators flash 3 times when shortly tapping the turn signal lever. Looking at the data this learns us that 'wert_01' disables the one-touch turn signal functionality and 'wert_02' enables it.

Mask 1C (0 to 7) also learns us that the function can accept other values than those two. In other words; there's a good chance that you can change the amount of flashes for the one-touch turn signal functionality. Code: FUNCTION KEYWORD ADDRESS (LENGTH) MASK PARAMETER KEYWORD DATA MASKED ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ MIND_ANZ_ZYKL_TIPP_BLK 00340506 (01) 1C wert_01 01 04 wert_02 03 0CFor keywords of which the conversion is known NCS Dummy displays the interpreted value in the graphical trace editor. If you know a conversion that is not yet implemented, please mail it to. Order Options One of the shortcomings of the translations in NCS Dummy is that they do not always clarify the meaning of functions and parameters. NCS Dummy tries to provide a helping hand by displaying extra information for each parameter that has cross references to the order options.

While the order options are not exactly always in a human readable format, they could be a great aid for interpreting meaningless parameters like 'wert_01', 'wert_02'. The displayed order options can be looked up in the ZST.000 (ZCS) or AT.000 (FA) file in the C: NCSEXPER DATEN folder. The example below shows the order options for each parameter of function 'KL_PREDRIVE_AUSWAHL' from the E60 instrument cluster.

Code: AUTOM_LICHT_KONTROLLE aktiv HEIMLEUCHTEN wert_02 MIND_ANZ_ZYKL_TIPP_BLK wert_02 QUITT_BLK_SICHERN nicht_aktivThe main limitation of this representation is that each function in the module must have a function keyword defined in the module description file and each data value for these functions must have a parameter keyword defined. If no keyword exists the function or parameter cannot be represented in this format. Take for example function 'MIND_ANZ_ZYKL_TIPP_BLK'. As seen before (chapter 3.1.2. Control Unit Data) this function controls the number of flashes for the one-touch turn signal functionality.

The function has 2 predefined parameters - 'wert_01' (flash once) and 'wert_02' (flash 3 times) - but actually accepts up to flashing 7 times. If you want to recode the module to, say, flashing 5 times that's not possible with the FSW/PSW format because there's no parameter keyword defined for data value 5. Naturally there are ways around that, like adding new parameters in module functions mode, but some changes are simply impossible to achieve through FSW/PSW manipulation. Nettodata (see later) provides an alternative that doesn't suffer from this limitation. Now assume you managed to code a non-predefined data value to the module for function 'MIND_ANZ_ZYKL_TIPP_BLK' and afterwards read an FSW/PSW trace file from the module with NCS Expert (and unmodified DATEN), NCS Expert will not be able to represent the function because there's no predefined keyword for the data value. NCS Expert then omits the function from the FSW/PSW trace file! In the past NCS Dummy didn't display the omitted functions either, but starting from version 0.6.0.0 omitted functions are shown in the graphical trace editor as excluded (unchecked gray functions) and can be included by checking one of the parameters.

Note that with an FSW/PSW trace file loaded, the graphical trace editor only shows items that can be represented in the FSW/PSW format. Properties and unoccupied blocks are not shown. The only way to visualize and manipulate these is through nettodata. Nettodata Whenever NCS Expert reads a module's coding to the FSW/PSW trace file, it also creates a nettodata trace file - NETTODAT.TRC. This nettodata trace file is actually an intermediate file that is used by NCS Expert when translating the module's binary data to keywords.

The nettodata trace file is very interesting because it contains an almost exact binary dump from the module's coding memory. Below is an excerpt of a nettodata trace file. Code: B 003,80,07,30,00,00,28,05,AA,FF,00,00,00,00,00,00,00 B 003,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 B 003,5D,90,42,50,96,1A,23,32,32,01,05,06,0C,43,64,AF B 003,96,1E,40,0F,0A,32,0A,50,78,64,14,32,64,1E,0A,07 B 003,0A,00,0A,06,1E,02,3C,96,02,0A,20,07,0D,00,00,00 B 003,0A,0D,1E,32,08,0A,32,19,1E,10,40,30,14,3D,19,15When working directly with the module's binary data no keywords are used and the limitations of FSW/PSW traces do not apply. You have total control over the binary data in the module and therefore nettodata manipulation may seem like the holy grail of coding. However, nettodata has serious limitations as well. The biggest issue is the fact that many modules do not support nettodata coding. This is actually rather stupid because modules are obviously not coded with keywords but binary data.

Even when coding from an FSW/PSW keyword trace manipulation file, NCS Expert translates all keywords to binary data that is very much like the nettodata format. There's no good reason why a module cannot be coded with nettodata but the job to do so is missing for many modules. If the NCS Expert jobs list does not contain 'NETTODATEN_CODIEREN', nettodata coding is not supported by the module.

From the pre-E60 era not a single module supports nettodata coding. A second issue is that even when a module supports nettodata coding, it does not always work. Sometimes the process already fails during coding, other times coding is successful but the changes are not working or are lost upon the next restart of the module. It seems NCS Expert performs additional post-processing steps for FSW/PSW coding that are not done for nettodata coding. These issues make nettodata coding only useful in a few specific cases. In all other cases it's better to use FSW/PSW coding instead and - if custom data values are required - make changes by adding new parameters in module functions mode (preferred) or via disassembly (see later).

Despite all this, reading nettodata from modules is still very useful as nettodata trace files often contain more information than FSW/PSW trace files. This extra information can even be useful to achieve certain functionality via FSW/PSW coding. While you cannot export nettodata trace files when an FSW/PSW trace file is loaded in NCS Dummy (there's not enough information in the FSW/PSW trace file to reconstruct the nettodata), you can export FSW/PSW trace files when a nettodata trace file is loaded. However keep in mind that when a nettodata trace file is loaded, the graphical trace editor shows all functionality of the module and FSW/PSW trace files cannot represent all of it. So making changes to items that cannot be represented by FSW/PSW trace files, exporting the FSW/PSW trace manipulation file and recoding the module with it, obviously will not work.

The graphical trace editor displays items that cannot be represented by FSW/PSW trace files in italic. Adding custom data As seen before (chapter 3.1.2.

Control Unit Data) functions often accept more data values than defined by the parameters. Adding new parameters in module functions mode (see chapter 3.1.4. Adding New Parameters) is one way of providing custom data values and works great for functions, but special functions like properties and unoccupied blocks do not support predefined and new parameters. This restriction can be circumvented when working with nettodata where direct manipulation of the binary data is possible without the need of predefined or new parameters.

When a nettodata trace file is loaded NCS Dummy allows you to add custom data for functions, properties and unoccupied blocks. Adding custom data is very similar to adding new parameters in module functions mode. To do so, right-click on a function or function parameter and choose 'Add Custom Data' from the popup menu.

A new (fake) parameter is added to the function and you can enter a custom data value for it. Note that unlike with adding new parameters in module functions mode, the NCS Expert DATEN files are not updated and only a single custom data value can be set per function!

Once satisfied with the changes to the trace coding, export the NETTODAT.MAN trace manipulation file ('Export Nettodata' >'Export NETTODAT.MAN') and recode the vehicle as explained in chapter 6.3. Coding modules with NETTODAT.MAN trace manipulation file. Do not export to and recode with a FSW/PSW trace manipulation file because FSW/PSW trace files cannot represent the custom data values. If something is wrong with the entered data, for example a data value outside the mask, NCS Dummy will highlight the faulty parameter and data field in red and prevent you from exporting the trace file until the fault is corrected. In the example above functions 'HEIMLEUCHTEN' and 'MIND_ANZ_ZYKL_TIPP_BLK' have custom data values applied. Remember that data values are always hexadecimal! For certain items adding custom data is your only option.

However when working with functions (as in the example above) adding new parameters in module functions mode is preferred over adding custom data in trace functions mode. You may still use nettodata and custom data because it's a quick way to make advanced changes to a module's coding without modifying any NCS Expert DATEN files, but if you experience issues (coding fails or does not stick) use the preferred method instead. HEX Trace Viewer Normally NCS Dummy is always used in conjunction with NCS Expert to recode modules. However in some cases it might be necessary to program the module's EEPROM directly with special tools. EEPROM programming is outside the scope of this user manual but starting from NCS Dummy 0.6.0.5 a HEX trace viewer is available which might come in handy when working with EEPROMs.

The HEX trace viewer provides a hexadecimal overview of the module's coding memory. The HEX trace viewer may seem very similar to viewing the content of a nettodata trace file in a plain text editor, but the HEX trace viewer actually displays the data in the same layout as the HEX editors that are usually used in conjunction with EEPROM programmers. In addition you can make changes in the graphical trace editor and see the changes immediately reflected in the HEX trace viewer. The HEX trace viewer can be opened only when a nettodata trace file is loaded: From the 'Export Nettodata' dropdown menu select 'Hex Trace Viewer.' Or press CTRL+H. It is not possible to use the HEX trace viewer with FSW/PSW trace files, nor is it currently possible to load or export EEPROM dumps directly. When a function is selected in the graphical trace editor, the bytes spanned by the function are highlighted in the HEX trace viewer.

Bytes that have changed from the originally loaded nettodata trace are displayed in red. Invalid data is indicated with XX. Byte positions that were not in the nettodata trace file are displayed as blanks. Partially masked bytes are underlined.

Pay attention to partially masked bytes because their value may not reflect the actual value in the EEPROM! Trace Differences The trace differences show the differences between two trace files. NCS Dummy automatically switches to trace differences mode after setting chassis, module and loading two trace files. If the second trace file is invalid NCS Dummy falls back to trace functions mode. Trace differences mode can be distinguished easily from module functions mode and trace functions mode by the black and blue numbered bullets in front of parameters. Starting from NCS Dummy 0.6.0.0 the second trace file input field is hidden by default to save space for the graphical trace editor. The second trace file can be loaded via the 'Browse.'

Button for 'FSW/PSW or Nettodata trace 1'. Choose 'Compare Trace 2.' Or 'Compare Recent' from the button dropdown menu to load the second trace file.

Download Ncs Expert

If you use the trace differences functionality often and don't mind losing a few lines in the graphical trace editor you can re-enable the second trace file input field. To do so, uncheck 'Hide FSW/PSW or Nettodata trace 2' on the 'Options' tab.

Note that you can only load the second trace file when a first one is already loaded for 'FSW/PSW or Nettodata trace 1'. The trace differences are not a simple text based comparison but compare addresses and binary data - even for FSW/PSW trace files. Therefore you can mix FSW/PSW and nettodata trace files but both must be of the same chassis and module! Trace file 2 is only used for the trace differences.

It does not have trace functions. Trace differences legend: • Group - Groups usually combine functions and properties that have related functionality. • FUNCTION - Functions describe certain programmable functionality in a module and have a list of one or more predefined parameters. Note that in trace differences mode only parameters that are used in both trace files are shown and multiword functions are not highlighted as in module functions mode and trace functions mode (the counterpart may not even be shown if it has no differences). • PROPERTY - Properties are similar to functions but do not have predefined parameters. • - - Unoccupied blocks are not really unoccupied, but usually contain data that should not be changed afterwards. • UNRESOLVED and - - Unresolved functions are defined in the trace file but do not exist in the module description file.

Free Download Ncs Expert Ediabas Windows 10

This means almost always the wrong chassis and or module are set for the loaded trace file. By default NCS Dummy uses strict reading and will error on unresolved items but strict reading can be disabled on the 'Options' tab.

• TRACE FILE 2 - Functions, properties and unoccupied blocks that occur in the first or both trace files are shown in black. Those that occur only in the second trace file are highlighted in blue. • trace 1 parameter - Black parameters occur in trace file 1 • trace 2 parameter - Blue parameters occur in trace file 2. • unresolved parameter - Unresolved parameters are defined in the trace file but do not exist in the module description file (see UNRESOLVED above).

• - - Fake placeholder keyword for initial data value of an unoccupied block. • - - Fake placeholder keyword for parameter data values for which no keyword exists. Trace differences can be exported to a plain text file. To do so, click the 'Trace Differences' button and choose 'Export.' From the dropdown menu. Similar to the module and trace functions the items to be included in the exported file can be set with 'Include Translations', 'Include Control Unit Data' and 'Include Order Options'. Pay attention when one or both trace files are nettodata trace files.

You may get unexpected results if you do not include control unit data: If all differences are in the control unit data, the graphical trace editor shows will correctly show the differences but the exported file is empty! Below is an excerpt of exported trace differences with control unit data and translations but no order options. Code: SWT_EINTRAG: 083A '10_seconds' SWT_EINTRAG: 083B '20_seconds' SWT_EINTRAG: 083C '30_seconds' SWT_EINTRAG: 083D '40_seconds' SWT_EINTRAG: 083E '50_seconds' SWT_EINTRAG: 083F '60_seconds'Head back to the disassembled LM2_E6X.C35 module description file and add the new parameters. It may seem tempting to remove the original 'wert_01' entry because it is now redundant (parameter 083B shares the same data value) but you should never remove existing parameters as that may break the central coding key (ZCS) or vehicle order options (FA) functionality in NCS Expert! It is safe to have multiple parameters sharing the same value, but you should never add multiple parameters with the same identifier (keyword) and different data values. That will break the module description file! I use NCS regularly on E38s.

I have all the options printed out in ENGLISH, so I know my choices. Ive actually not tried it on the E31 yet.I didn't bother translating the German parameter names and values. For the E31 it's a doable amount, but then I'd have to do the same for the other models.

That's over 3000 parameter names and over 1000 parameter values. I have better things to do. Of course, if anyone feels like translating all parameter names and parameter values, go ahead. I can change NCS Dummy to show an extra column with the translations. If you want a bare list of parameter names and/or parameter values, just launch NCS Dummy with command line parameter /mode=verbose (NcsDummy.exe /mode=verbose). This will enable the 'Export Parameter Names' and 'Export Parameter Values' buttons.

I recommend using Hex Code sorting for these files as this tends to group related stuff which should aid translating. My main reason for writing the NCS Dummy application was to figure out all possible values for each parameter.

If the value is 'nicht_aktiv', the other possible value is quite obvious. You don't need NCS Dummy for that. But quite a few parameters have values which are simply impossible to guess or will be at best a lucky guess. In that case your only options are to gather FSW/PSW trace files from other cars in hope those will contain different values for these parameters, or decoding the binary files by hand. NCS Dummy automates the latter, quickly providing a reliable overview of all possible parameter values of all parameter names in a module or trace file. Coming from the E38 I'm sure you'll be disappointed with the limited coding functionality of the E31, but nevertheless it's informative to know what's going on in certain modules. Is there any way you can add the e90 family into the program?

It consists of the e90/e91/e92/e93/e90 M/e92 M (E9x family)?I'm not sure the E9x family is supported by NCS Expert. At least my version (3.1.0) doesn't show any vehicle younger than the E89, but perhaps there are newer versions. Without NCS Expert data files for the chassis, I cannot update NCS Dummy. If your NCS Expert version does support the E9x family, have a look in the 'EDIABAS NCSEXPER DATEN ' folder, put the E9x folders in a ZIP archive and send the archive my way ( ). I'm not sure the E9x family is supported by NCS Expert. At least my version (3.1.0) doesn't show any vehicle younger than the E89, but perhaps there are newer versions.

Without NCS Expert data files for the chassis, I cannot update NCS Dummy. If your NCS Expert version does support the E9x family, have a look in the 'EDIABAS NCSEXPER DATEN ' folder, put the E9x folders in a ZIP archive and send the archive my way ( ).I read on another forum that E89 is what is used for the E9x series as well. Would you mind adding that to your program. It is a very useful tool.

Thanks again. I read on another forum that E89 is what is used for the E9x series as well.

Would you mind adding that to your program. It is a very useful tool.

Thanks again.I've updated NCS Dummy to version 0.2.0.10 which includes support for the E89. I've also added a new feature: If you export a file with NCS Dummy and then doubleclick on the log line which starts with 'Successfully exported.' The exported file will be opened in your system's default application for text files (*.txt). This should save you from always returning to the filesystem to locate and open the exported file. You can also force NCS Dummy to open the exported files automatically by launching the application with command line parameter /autoopenexported=1 (NcsDummy.exe /autoopenexported=1). If you want this behavior but do not want to enter the command line on each start up, create a shortcut to the application and add the command line parameters to the shorcut's Target.

If you're interested, I do have all of my E39 fsw/psw files - the first thing I did when I had access to NCS was to make backups up all the FSW/PSW file.Please yes, send them to me. Even though I don't really have a purpose for them now, it may be helpful in the future to have a bunch of real world trace files. Perhaps for future NCS Dummy functionality, perhaps if I ever get myself an E39. I also hope at least a few people with an early or USA spec E31 send me their trace files. I'm interested in the differences to later or ECE spec E31.

I'm not sure the E9x family is supported by NCS Expert. At least my version (3.1.0) doesn't show any vehicle younger than the E89, but perhaps there are newer versions.

Without NCS Expert data files for the chassis, I cannot update NCS Dummy. If your NCS Expert version does support the E9x family, have a look in the 'EDIABAS NCSEXPER DATEN ' folder, put the E9x folders in a ZIP archive and send the archive my way ( ).Hello! What a great piece of software! Thankyou for taking the time to develop that.

I'm sure it will be of great help, to a lot of people. With regards to updating NCS, i have the 'daten' files from ISTA/P v2.37, if you would like them? Kind Regards, FAL. I've updated NCS Dummy to version 0.2.0.10 which includes support for the E89. I've also added a new feature: If you export a file with NCS Dummy and then doubleclick on the log line which starts with 'Successfully exported.' The exported file will be opened in your system's default application for text files (*.txt).

This should save you from always returning to the filesystem to locate and open the exported file. You can also force NCS Dummy to open the exported files automatically by launching the application with command line parameter /autoopenexported=1 (NcsDummy.exe /autoopenexported=1). If you want this behavior but do not want to enter the command line on each start up, create a shortcut to the application and add the command line parameters to the shorcut's Target. Please yes, send them to me.

Even though I don't really have a purpose for them now, it may be helpful in the future to have a bunch of real world trace files. Perhaps for future NCS Dummy functionality, perhaps if I ever get myself an E39.

I also hope at least a few people with an early or USA spec E31 send me their trace files. I'm interested in the differences to later or ECE spec E31. Feel free to link, but I prefer to keep this thread in the E31 section as it was written especially for the E31 (even though the E31 doesn't really offer much possibilities with coding).Thank you. Revtor - thanks Please add E70 or all E31_PFAD_DATEN =. Daten e31 E32_PFAD_DATEN =. Daten e32 E33_PFAD_DATEN =.

Daten e33 E34_PFAD_DATEN =. Daten e34 E36_PFAD_DATEN =. Daten e36 E38_PFAD_DATEN =. Daten e38 E39_PFAD_DATEN =. Daten e39 E46_PFAD_DATEN =.

Daten e46 E52_PFAD_DATEN =. Daten e52 E53_PFAD_DATEN =. Daten e53 E60_PFAD_DATEN =. Daten e60 E65_PFAD_DATEN =. Daten e65 E70_PFAD_DATEN =. Daten e70 E83_PFAD_DATEN =.

Daten e83 E85_PFAD_DATEN =. Daten e85 E89_PFAD_DATEN =. Daten e89 K24_PFAD_DATEN =. Daten k24 R50_PFAD_DATEN =. Daten r50 R56_PFAD_DATEN =. Daten r56 RR1_PFAD_DATEN =.