KPower Vehicle Power Measurement, Power Chart Creation

I am relatively new to the VW/Audi sector, and I also have VCDS etc. Now, to my question: I have been unable to find any information about KPower. Has anyone here found anything, such as a manual, tips, or anything else that I could use to familiarize myself with it?

Thank you and best regards, Kevin

Hello Kevin,

Do you press the "F1" key or go to the "Help" menu in KPower?

For specific questions, it is best to upload the corresponding log file here.

The achievable measurement accuracy primarily depends on the test course (ideally uniform, a minimum length of 300m is recommended) and the competence of the operating personnel. Typically, measurement accuracy of +/-5% can be expected.

A button for direct data import from KOBD2Check, VCDS and other OBD2 software allows for easy use.
Other data recording sources are supported through a CSV file interface and import from Microsoft Excel tables: the following values must be included in a dataset: the time of the measurements (timestamp), vehicle speed, and engine speed.

The calculated performance curves can be printed and saved as a bitmap. Each dataset can be assigned and saved/loaded for individual vehicles.

Quote:

KPower - Performance Measurement Version 3.0.9 1. Usage Guidelines and Rights to the Program All rights and commercial use and distribution von KPower are owned by Kaufmann Automotive GmbH. Any form of private or commercial distribution is FORBIDDEN. Any transfer of this software to eBay or other Trading platforms lead to the filing of a criminal complaint. through us. For any damages caused by the use of this software Any damages that may arise will not be covered. At the Data acquisition requires attention to ensure that no one is put at risk. Vehicles are excluded. For all measurement trips conducted for data collection, must also be observed, and common sense. Using human reason. The operation of the Meß-Notebooks should be operated by a second person from the back seat. to be carried out. 2. Functions This program is used for approximate performance measurement based on Measurement blocks, generated by the diagnostic software VAG-COM, VCDS or GS-911 can be recorded. This allows for changes in the engine area (e.g., new air filters, (other air intakes, cargo air coolers, tuning chips, etc.) without Expensive and material-damaging test runs are being tested. 3. Procedure First, use VAG-COM to create a suitable log file: Measurement trip, for example, Engine control unit blocks 5 and 6 is recorded. Important is, that the speed and RPM are included in the log. During the measurement, you should accelerate in the 3rd or 4th gear. Let's go. Full throttle from approximately 1500 min-1 to the highest engine speed, then release the clutch and allow the vehicle to continue Release the clutch pedal. The measuring path should ideally be as level and even as possible. Is there a greater difference in gradient between acceleration- and deployment area, it is advisable to divide the measurement. Then manually combine the acceleration and roll values. Okay, here's the translation: Short, let's recap everything: - Rollen auf einer Messstrecke im 3. Gang, etwa 1000 min-1 - very slightly accelerate, speed increases very, very slowly - Start log file - Full throttle - at 4500 rpm (TDI, for gasoline engines, the corresponding maximum engine speed) Release the clutch and simultaneously release the accelerator pedal completely. Here, the acceleration performance effective on the wheels is measured. - Release the clutch until the speed is back to at least ~70km/h abgefallen ist (Automatic transmission: Neutral position). Here, we now measure the aerodynamic drag and wind resistance performance. - Stop the log file. Now the clutch can be released again and operated normally. continue. It is recommended to record the name for each measurement. to modify the log file so that multiple measurement values are not accidentally recorded. in the file. The log file then directly via the 'Import Log File' button. to be incorporated into the program. Manual input of acceleration and roll-over values is also possible. The values in the tables can be accessed via {METHOD}. Double-click to edit. If the program does not automatically identify the correct areas of the Log file indicates, this needs to be corrected manually. that only acceleration and deployment processes are included. The column names of the CSV log files are displayed on our VAG-COM Tailored distribution. Use a different or differently-language VAG-COM distribution, can it be necessary to adjust the settings for the import of Adjusting log files. 4. Frequently Asked Questions Q: My curves are showing a downward pointing "V" shape, what could be the cause? A The measurement was not recorded correctly, and most often also auch other acceleration or braking events in the log file as the actual 'measurement data'. Best, to do simultaneously with Start of the acceleration process: start logging with VAG-COM. Is the performance too high/too low? A: Has the correct vehicle weight been set? Larger or smaller wheels assembled? Difference between actual tire rolling circumference and Enter tire specifications! Q: My power/torque curve shows an 'over-specified', unrealistic high peaks in the lower speed range of the measurement. A: It is likely that the deceleration was already initiated before the data logging began. was abgeschlossen wurde. KPower detects stronger braking automatically, at Gentle braking during the rollout process cannot be 'high slip ratio' and the operation of the brake pedal under- will pass away. The same applies to steep inclines at the end of the Measurement -> In the 'Measurement' -> 'Expand' tab, the falsified Double-click to delete or measure again and correctly. Q: My power/torque curve shows a 'dip' in a Operating range in which the maximum torque is already achieved should. Why does it only appear in the measurement when the value is higher? RPM? A: It is likely that the measurement was taken in a "small" alleyway, so that The RPM range is traversed very quickly and in the critical Range: Only a few measurement values are available or the calibration process is gears (e.g. (Loading torque) does not yet allow for full torque. Simply measuring the critical speed range in a Repeat in a higher gear, so you can explore interesting areas. 'zoom out' Q:DMy columns in my log file are not being recognized... A: Set the correct column names and the correct measurement blocks log in, then it will work. Q: Which measurement blocks do I need to record? A: The following values must be present in the log file for each data row: his: Time (timestamp), speed, engine speed. Simple, suitable measurement blocks with the highest possible sampling rate. choose. Q: Can I also import data from a spreadsheet, e.g. Microsoft Excel or OpenOffice? A: Yes, using the 'Insert' buttons on the measurement page. Data in copy the table into the clipboard, cell in Select KPower from the list and click 'Insert'. Click the button. Q: Performance correction according to DIN (depending on ambient air pressure, (Ambient temperature) results in unusual values? These values should only be used for standard gasoline engines. to be amended. In engines with turbochargers, especially TDIs, is this performance review not applicable because the Motor control units employ different strategies and protection programs. use. For example, in TDI engines below a certain Ambient Air Pressure Threshold (e.g., 980 mbar) Injection Volume and the pressure has returned to normal, but it is not above 980mbar. Using DIN correction here would therefore make no sense. Have fun - Rainer Kaufmann

In connection with KOBD2Check:

Quote:

The settings for KOBD2Check logs and KPower are: Column name for time:s Column name for RPM: rpm Column name for speed: km/h Important is that in the settings, before and after s, rpm and km/h, there should not be Spaces are separated. The "old" version of KPower does not come with the log files from KOBD2Check. Very clear, because KOBD2Check provides much more values than VCDS. This causes unsuitable sugars to come out in the curves, you'll see for yourself. "Worth a try is the trick of increasing the sampling rate by logging additional" after the values in km/h to decelerate. Your Log 12-13-16 looks good so far Better than 12-13, see KPower file in the attachment. VCDS should work, that's slow enough. PS: We are working on an updated and improved version for KPower.

Best regards, Rainer

Instructions as PDF.

Many thanks for the quick and efficient help!

Tip: When selecting columns in VCDS logs, check what each line says to configure KPower correctly for each import.

It's simpler to use KOBD2Check right away.

Best regards, Rainer

When importing VCDS and KOBD2Check log files into KPower, pay attention to the following regarding the file format:

1. Do not convert the .csv file, it's best to delete the useless csvconv.exe. Otherwise, the log file may be destroyed and become completely useless, not just for KPower but generally.

File header as it appears in the un-converted original (Example):
Tuesday, 07, May, 2019, 14:01:33:28906-VCID:7BA2068213626E7FCBF-802E,VCDS Version: DRV 18.9.1,Data Status: 20190215 DS296.0
04L 906 026 FN,ADVMB,R4 2.0l TDI H24 2011,
,,G004,F0,G008,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,

Marker, Time, Loc. IDE00021, Time, Loc. IDE00075,,,,,,,,,,,,,,,,,,,,,
,MAKE,Engine Speed,MAKE,Vehicle Speed,,,,,,,,,,,,,,,,,,
,, /min,, km/h,,,,,,,,,,,,,,,,,,
,0.19,1404,0.07,34,,,,,,,,,,,,,,,,,,,,,
,0.41,1444,0.32,35,,,,,,,,,,,,,,,,,,,,,
,0.62,1478,0.50,36,,,,,,,,,,,,,,,,,,,,,
...[/code]

2. Make sure that the program settings in KPower contain the correct column names. Note that any spaces included in the file should also be included! So, maybe

Code:

" /min"

3. VCDS does not consistently generate column labels across different versions and measurement block options. The best way to log the correct time unit is to use s for seconds.

Example of a correct log file header:

Tuesday, 07, May, 2019, 14:01:33:28906-VCID:7BA2068213626E7FCBF-802E,VCDS Version: DRV 18.9.1,Data Status: 20190215 DS296.0
04L 906 026 FN,ADVMB,R4 2.0l TDI H24 2011,
,,G004,F0,G008,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,

Marker, Time, Loc. IDE00021, Time, Loc. IDE00075,,,,,,,,,,,,,,,,,,,,,
,MAKE,Engine Speed,MAKE,Vehicle Speed,,,,,,,,,,,,,,,,,,
,s, /min,, km/h,,,,,,,,,,,,,,,,,,,,,
,0.19,1404,0.07,34,,,,,,,,,,,,,,,,,,,,,
,0.41,1444,0.32,35,,,,,,,,,,,,,,,,,,,,,
,0.62,1478,0.50,36,,,,,,,,,,,,,,,,,,,,,
...[/code]

The line ",0.19,1404,0.07,34,,,,,,,,,,,,,,,,,,,,," now means: 0.19 seconds after the log started, a speed of 1404 /min was measured, and 0.07 seconds after the log started, a speed of 34 km/h was measured.

Best regards, Rainer