[DWR]

Originally Posted by _TB_

If I would like to log shift times with TestO - what do I need to log then?

Just log input shaft and time.
I am sure you must be asking something else because that answer was too easy.

BTW, several have tried the Alpina tune with their diesel and been dissatisfied. What tricks have learned in order to make it work?

[_TB_]

Originally Posted by DWR

Just log input shaft and time.
I am sure you must be asking something else because that answer was too easy.

Yes, that is not accute enough if we need to monitor if shifttimes are improving when doing our own files. There must be something more accurate to monitor?

Originally Posted by DWR

BTW, several have tried the Alpina tune with their diesel and been dissatisfied. What tricks have learned in order to make it work?

Well.. I have always like the Alpina in D - with some issues.. S has been close to useless as shiftpoints was waaayyy to high. So I have been using D and M while I have been using the Alpina B3 file. Also remember my car has the ZF6HP19TÜ gearbox - like the B3.

The issues with Alpina-D are:

- No shifting at 100+ % throttle
- Dangerous downshifts if not being carefull (easy to overrev on kickdowns)

..and then the TCC will never lockup during warmup. Driving on the motorway in 6th and giving it some pedal will just make the revs climb.. Quite annoying!

With M you still need to be carefull not to overrev the engine when downshifting!


What I have been doing during some of the beta test is to repopulate the shiftmaps to fit my needs. I have not been able to overrev it yet, kickdown works just fine now. S is _soooo_ good now with the right shiftpoints, it shifts like lightning compared to std. (I suppose it is almost the same as the stage3 OTS map in the Xhp app) in D I can cruise at 59km/h in 5th, it shifts to 4th at ~38km/h. (When cruising with light throttle) Also torque reduction during shifts, and clutch timing on upshifts have been improved to the same values as the Alpina D3. (As it is more aggressive than the B3).

I have one last issue that is bothering me quite a bit. It still won't change at 100+ % throttle - despite all shiftmaps have been changed.


But for 90% of all, the OTS maps will be more than sufficient, the quality of them is really good, and the three levels will make sure there is a map for everybody. The reason I'm running a custom file is mainly because I like to tinker with binary files, and I want to learn from it. Do _NOT_ expect a good file can be made in an afternoon - it takes a lot of hours to get it right!

[Ibo24]

Was looking for this topic!

Is it possible to instal the sport transmission on a 330d-335d?

Like the Alpina to show D1, S1?

[wardpa]

Originally Posted by _TB_

But for 90% of all, the OTS maps will be more than sufficient, the quality of them is really good, and the three levels will make sure there is a map for everybody. The reason I'm running a custom file is mainly because I like to tinker with binary files, and I want to learn from it. Do _NOT_ expect a good file can be made in an afternoon - it takes a lot of hours to get it right!

Thank you for sharing your experience! This is what I am hoping for in the future: sharing knowledge on how to improve the calibration of the transmission.

I'm sure that the OTS files will be a huge improvement over the stock software, but none of the files really match my needs.

[Unklejoe]

Originally Posted by RBT-Tuning

The base file get's chosen based on your Vehicle VIN and yes, it is not a "one fits all" approach. Different cars, get different base files. It's a lot of work, but the only way to avoid problems. Anyone remember the problems some N55 have with the Alpina flash?

Nice. That sounds like quite the task!

And yes, I remember the N55 Alpina flash issues, as mine was one of the ones with problems. I had to bring the car to the latest integration level in order to get the RPM gauge to stop dropping to 0 during shifts. It still temporarily drops "too low" during shifts, but it's hardly noticeable.

Originally Posted by _TB_

Also torque reduction during shifts, and clutch timing on upshifts have been improved to the same values as the Alpina D3. (As it is more aggressive than the B3).

I wonder if the D3 being more aggressive than the B3 has something to do with the weaker input shaft on the 6HP21 when compared to the 6HP26?

I've seen pictures of snapped 6HP21 input shafts from high power 335i cars, which is why I personally won't be aiming to decrease shift times and torque reductions further than the Alpina B3 values.

I would think the diesel is even more abusive to the transmission, but I'm not sure.

[_TB_]

Originally Posted by Unklejoe

I wonder if the D3 being more aggressive than the B3 has something to do with the weaker input shaft on the 6HP21 when compared to the 6HP26?

D3 and B3 uses the same gearbox - the ZF6HP19TÜ.

[Unklejoe]

Originally Posted by _TB_

D3 and B3 uses the same gearbox - the ZF6HP19TÜ.

Oh sorry! That's good to know though

[trebila]

Sorry if I've missed it, but where can we download the xdf ?

[_TB_]

Some interesting things in the original BMW files..

I have been taking a very quick look at an 0DA for a Z4 with SAT transmission (option 2TB).
There are some rather interesting changes n the file compared to both Alpina and ori BMW.

What I did;

1) Find a file that is intended for the SAT option.
Look in the GKE215 data folder, find the GKE215.ATS file, and search for option 2TB. Now find a car that matches your car as closely as possible. I chose a Z4 EU, left hand drive (code LM51). Now there is a file for SAT option. It is 7601494.

2) Find the corresponding 0da file for the file found above.
Open the GKE215.DAT and search for the number found before. Verify that the found number is matched to the same HW-NR as your own transmission (mine is 7591971). Then you have the 0da file to look for. For mine it is 7601495DA - which is A7601495.0DA.

3) Edit the file, remove the headers.
Copy the file to another destination - and then use your preferred text editor. Remove all the header lines. That is basically all the lines until the first line that starts with ":" Save the file as A7601495.bin

4) Convert the file
The 0DA file is stored in Intel HEX, so you need to convert that format to binary. Use your preferred program to convert the file from Intel Hex to binary - save the binary.

5) Insert "dummy" data to make the file 1MB like the backup from XHP. I used the backup created by XHP. You need to copy the part from 0x00000 to 0x50000 from the backup. I use a nifty little windows tool called SwiffFileKnife (SFK149.exe) to do this. Save the extracted data in a new file called preamp.bin.
Then we also need to copy the part from 0x80000 to 0x100000 in the backup. Save that segment to trail.bin.
Finally combine those three files to a "full" 1MB file that you can use to compare to another ori (or your backup).

cat preamp.bin >> combined.bin
cat A7601495.bin >> combined.bin
cat trail.bin >> combined.bin

..Now you have a 1MB file that you can use to compare to either your backup or any other 1MB file. The reason for making a 1MB file is that the XDF can be used to compare maps with directly in TunerPro.

!!Please be aware that is probably will NOT be possible to just copy the maps over to your backup and then flash it to the TCU as there may be differences in the code part of the original flash! This is solely for comparing maps in order to educate yourself on the changes made to the different versions from BMW.

..If you would like to dig a step further - use the Grundprogram file for the missing segments in the 0da file. I'l shall leave this as a challenge for you guys to figure out

[TDIwyse]

Originally Posted by _TB_

...
What I have been doing during some of the beta test is to repopulate the shiftmaps to fit my needs. I have not been able to overrev it yet, kickdown works just fine now....

Thanks for sharing the description/experiences!

One thing I'd like to be able to change is the high rpm shift points during full fueling. Right now my car shifts at the mid/upper 4600's rpm's. I'd like to move that higher in certain gears. Have you played with doing this, or can you describe how one might go about implementing a change like this with the tool?

[Unklejoe]

Originally Posted by _TB_

The reason for making a 1MB file is that the XDF can be used to compare maps with directly in TunerPro.

Does this mean that the locations of the tables are the same for all of the various firmwares (and thus one XDF to rule them all)?

I assumed that there were some slight differences in the addresses depending on the firmware, which would have required a different XDF for each.

[_TB_]

Originally Posted by Unklejoe

Does this mean that the locations of the tables are the same for all of the various firmwares (and thus one XDF to rule them all)?

I assumed that there were some slight differences in the addresses depending on the firmware, which would have required a different XDF for each.

I have only looked at a limited set of files, but they all had the same structure. .. But it is different how each software uses the maps.. Some are unused in some software versions and some are used.

I expect a single XDF to be released.

[Mik325tds]

First of all, thank you for beta testing and sharing your experiences here. This is exactly what I was hoping for this thread to keep going on.

Originally Posted by _TB_

Yes, that is not accute enough if we need to monitor if shifttimes are improving when doing our own files. There must be something more accurate to monitor?

Unfortunately, the accuracy of the shift-times will greatly depend on sample time. The more signals you log, the less sample time you'll get - unless you can get a CAN log. I know Pheno is working on a solution for that.
As far as values to log, here are the signals I usually log in Test-O:
Auslesen Fahrpedalwinkels (Throttle position)
Engine RPM auslesen
Auslesen des Motoristmoments (Current engine torque)
Auslesen des Istgangs (Current gear)
Auslesen des Wanderkupplung (TCC)
Auslesen AGS Schaltdiagramm/Kurvenfahrt

Originally Posted by _TB_

I have one last issue that is bothering me quite a bit. It still won't change at 100+ % throttle - despite all shiftmaps have been changed.

As you are already aware, the B3 cal uses different shiftmaps than the standard cal, so you'll have to be aware of which map you're currently in. Also, I have noticed that on the second 100% throttle input the program changes shiftmaps from XE to E.
The only way to be sure which map you're currently using is to log the signal Auslesen AGS Schaltdiagramm/Kurvenfahrt.

[TDIwyse]

Mik325tds, are you able to describe if/how one would be able to adjust the max shift rpm higher? Will it be possible to have a manual mode where the automatic up-shift occurs at specific rpm's for specific gear changes? For example, DS manual shift mode but automatic rpm's for upshift from 2nd to 3rd occur at one rpm, 3rd to 4th at a different rpm, 4th to 5th at a different rpm. Right now, these shifts occur around mid 4600's for my car and I'd like to be able to move some of the shift points up higher...

[_TB_]

Originally Posted by Mik325tds

First of all, thank you for beta testing and sharing your experiences here. This is exactly what I was hoping for this thread to keep going on.


Unfortunately, the accuracy of the shift-times will greatly depend on sample time. The more signals you log, the less sample time you'll get - unless you can get a CAN log. I know Pheno is working on a solution for that.
As far as values to log, here are the signals I usually log in Test-O:
Auslesen Fahrpedalwinkels (Throttle position)
Engine RPM auslesen
Auslesen des Motoristmoments (Current engine torque)
Auslesen des Istgangs (Current gear)
Auslesen des Wanderkupplung (TCC)
Auslesen AGS Schaltdiagramm/Kurvenfahrt

Problem with logging several parameters from EGS is that it seems you get the same values for multiple reads. (When logging four values it seems it updates them one-by-one - leaving the other three with "old" values". I'll try to find a log that shows it, hard to explain when english is not your mothers tongue

Originally Posted by Mik325tds

As you are already aware, the B3 cal uses different shiftmaps than the standard cal, so you'll have to be aware of which map you're currently in. Also, I have noticed that on the second 100% throttle input the program changes shiftmaps from XE to E.
The only way to be sure which map you're currently using is to log the signal Auslesen AGS Schaltdiagramm/Kurvenfahrt.

It is a bit more complex, as there are multiple XE shift maps, multiple Steptronic maps etc. There is a good way of finding out exactly which map is used, but I'll let it be up to the developers to reveal how that is done. IMHO Schaldiagram will tell the strategy used, but not the actual map.
There are several maps that are used briefly at fast throttle changes and/or hard braking. Also it seems the uphill maps are used more often than I anticipated - even a small incline will switch to uphill map#1. Also separate maps for cruisecontrol - and according to ZF info, maps for when towing a trailer. The last one I have not logged any data for yet.

I find it massively interesting - but it is not a simple job. The amount of research that needs to be done in order to make a good remap is immense. You really have to give credit to the team for making three separate tunes for so many cars/gearboxes in such short timespan. That is really impressive!
I'm pretty sure most of the program has been decompiled and reverse engineered in order to do what they have been able to do.

[_TB_]

Originally Posted by TDIwyse

Mik325tds, are you able to describe if/how one would be able to adjust the max shift rpm higher? Will it be possible to have a manual mode where the automatic up-shift occurs at specific rpm's for specific gear changes? For example, DS manual shift mode but automatic rpm's for upshift from 2nd to 3rd occur at one rpm, 3rd to 4th at a different rpm, 4th to 5th at a different rpm. Right now, these shifts occur around mid 4600's for my car and I'd like to be able to move some of the shift points up higher...

The shiftpoints can be altered for each map. There are a total of 21 shift maps, not all are used (depending on SW version) - but you have full control of them all.

There are som many aspects of the files that are not defined in the current version of the XDF - almost everything is possible, you just need to define the right scalars/maps in the file. Hell I even bet it will be possible to reverse the gears, starting in 6th shiftting down as car starts to move. I would not advise to try that out

[TDIwyse]

Originally Posted by _TB_

The shiftpoints can be altered for each map. There are a total of 21 shift maps, not all are used (depending on SW version) - but you have full control of them all.

...

Thanks for the information.

[Unklejoe]

Could we effectively eliminate all of the extra "features" and "modes" of the TCU by setting all of the shift maps to the same values?

It might make it easier to isolate and test any changes.

[_TB_]

Originally Posted by Unklejoe

Could we effectively eliminate all of the extra "features" and "modes" of the TCU by setting all of the shift maps to the same values?

It might make it easier to isolate and test any changes.

Technically, that is possible.. I just can't see the need really.

[WreckerX5d]

Is it possible to alter the setting of each OTS map then? Say I wanted to eliminate the manual mode setting off the stage 3 map, and make the car auto shift like normal.

[_TB_]

Originally Posted by Wrecker335d

Is it possible to alter the setting of each OTS map then? Say I wanted to eliminate the manual mode setting off the stage 3 map, and make the car auto shift like normal.

No. Either you buy a complete remap (The OTS maps) or you make your own. There is no mixing them.

Honestly guys.. The team has worked pretty hard to give you three options to chose from - it is not quite simple to make it happen on such many different cars/hardware.

if you have weird wishes - like I do - then you make your own files

[pheno]

Originally Posted by _TB_

Problem with logging several parameters from EGS is that it seems you get the same values for multiple reads. (When logging four values it seems it updates them one-by-one - leaving the other three with "old" values". I'll try to find a log that shows it, hard to explain when english is not your mothers tongue

This is because with GS19D you can only request one parameter at a time. There's STATUS_IO_LESEN which gives you many results in one reply but I believe it does not have all the params you need.