TCU TurboLamik

Is there a possibility to do a open project from lamik xdf where we as user fill in explanations of maps and values
So we all could have little easier on tuning side?

Starting with torque calculations
Horizontal value is rpm
Vertocal is tps

I kept this whole map as 1200nm except first row under 500rpm

Then next is cal press/torque
Again, horizontal is rpm
Vertical is kpa, kilopascal

How to determine this map, what is that kpa for?

Then there is pressure/torque multiplier, and again value is kpa, what is this for

Then there is torque multiplier, that read torque is as i know from engine ecu calculated torque and multiplier on this
Is somehow increase value for transmission to increase or decrease trans clutch pressures.
Stock is 100%, increased it will decrease clutch slip but negative affect if overcompensating is what?

Offset engine torque, this propably is just added to ecu calculated base value

Torque corrected tps ? How to use this ?

To broadly answer your question, I assume your using an OEM can stream. Map (kpa) is not used as tq is sent from the ecu. The tq calculation requires different tables when using a stock ecu vs say a haltech.



Right click on the scalar, table, flag etc.. and select 'edit Parameter XDF info'.
You can edit the description, its name and even move it to a new location if you feel it makes more sense in a different folder within TunerPro.
Once done, in the toolbar select XDF and save it. The XDF only describes the bin file and each item location along with how it's displayed.
But a warning - don't change the address or data types as this will cause the incorrect location or datatype to be displayed or edited.
Bad news is you have to update the next XDF if there is a new update. The bin file should always use its matching XDF version.

Also you can use 'Ctrl - F' to find tables. Helps in a pinch when you are trying to find a table like lockup for example.

Hi.

I'm quite familiar tunerpro user so that is not my issue or issue at all.
I'm more qurious about parameter definitions values compared to something that can be calculated to more understanable tuning parameters.

Example if you have a 12x12 table where x is scaled as torque and y is scaled as value from 0 to 100 but there is no explanation to what that is compared, you can adjust values and assume it increase or decrease something but that's it, rest is to hope and go testing if it has some effect or not.

What i'm after is a topic where those tables and their functions is explaned to a level that we as tuning community could fill them to our own xdf's to do life easier.

I have done that same to my bmw n54 xdf, increase tables not be found in public xdf's and explanations to them, orginal xdf file size was somw 440kb and my own is in size of over 1.4 mb .. there is quite much help when it explain tables when you hoover over it..

We need explanations for many more things. Documentation is by far the weakest part of this system.

I totaly get it and agree but I was just suggesting as you learn and figure things out you can change the XDF yourself and add them. Even units for a row.
Also change the popup messages to your liking to help explain tables.

But to be honest I would rather see more updates, better bug tracking and add a user definable CAN TX/RX definition. The things you mentioned can all be changed within tunerpro and/or datalogged to observed the changes as you learn its affect.

https://drive.google.com/file/d/1fb5H-r ... p=drivesdk

https://drive.google.com/file/d/1rmWKxv ... p=drivesdk

This adx and xdf has live tracing for some tables.
Its a work in progress but feel free to add more.

I got side tracked and havent had a chance to do anything with it since last winter.

Maybe a GitHub project is appropriate if more people are interested in building the xdf to live trace and have better definitions