3lli0t 06-22-2015 03:27 AM
Quote:
Originally Posted by Mik325tds (Post 18128253)
Yes, that'll probably a single value in the cal file different from the standard cal file. Probably impossible to find unless it is in a field of same values.
What do you mean, with "only one mapping available in the data"?
That sounds not so nice :P.
My description concerning the mapping was a little bit confusing: For my HW-# there are min. 25 different files in the DATA which can be flashed. My actual ZUSB is for the N57 and there is no file for the M57 for the GKE215. The reason is, that the e92 325d from 2009 was one of the last models with the M57TU2UL, the 330d had already the N57 (245 HP), so BMW didn't develop an extra mapping for the M57 with GKE215.
Generally I would try to flash the Alpina Soft for the N54 and test the result. But I don't know if that could harm the transmission, because it's made for an entire different torque and power curve. On the other hand I have to start somewhere and like so see if it's possible to combine the Alpina-Soft with the standard-N57-mapping. The plan: Take the Alpina file and overwrite the N54-tables with the N57-tables. If this works I have a file with the alpina-display (Gears in D and DS) and can start to optimize the mapping. Now my question: Is it possible to isolate only the shift-maps und leave the rest?
Mik325tds 06-22-2015 06:41 AM
Quote:
Originally Posted by 3lli0t (Post 18129958)
That sounds not so nice :P.
My description concerning the mapping was a little bit confusing: For my HW-# there are min. 25 different files in the DATA which can be flashed. My actual ZUSB is for the N57 and there is no file for the M57 for the GKE215. The reason is, that the e92 325d from 2009 was one of the last models with the M57TU2UL, the 330d had already the N57 (245 HP), so BMW didn't develop an extra mapping for the M57 with GKE215.
Generally I would try to flash the Alpina Soft for the N54 and test the result. But I don't know if that could harm the transmission, because it's made for an entire different torque and power curve. On the other hand I have to start somewhere and like so see if it's possible to combine the Alpina-Soft with the standard-N57-mapping. The plan: Take the Alpina file and overwrite the N54-tables with the N57-tables. If this works I have a file with the alpina-display (Gears in D and DS) and can start to optimize the mapping. Now my question: Is it possible to isolate only the shift-maps und leave the rest?
First you have to find out if the cal files have the same structure for your HW number and the alpina flash. I use TotalCommander to do a binary file compare for that. If the files are the same length and the sectioning is the same you should see only differences in the data itself but not in the addresses. Best case would be if the HW number is the same for the alpina flash and your HW, but since it didn't flash I assume that is not the case.
As far as identifying the shift maps goes, I guess we'll have to wait until DWR shares his magic on that.
3lli0t 06-22-2015 11:05 AM
Quote:
Originally Posted by Mik325tds (Post 18130265)
First you have to find out if the cal files have the same structure for your HW number and the alpina flash. I use TotalCommander to do a binary file compare for that. If the files are the same length and the sectioning is the same you should see only differences in the data itself but not in the addresses. Best case would be if the HW number is the same for the alpina flash and your HW, but since it didn't flash I assume that is not the case.
As far as identifying the shift maps goes, I guess we'll have to wait until DWR shares his magic on that.
I compared the N54-Alpina file and the N57 file. The adresses are the same. If I make the right settings in WinOLS it finds around 100 maps, but I have no idea if the software is right .
Mik325tds 06-23-2015 03:37 PM
Quote:
Originally Posted by 3lli0t (Post 18131486)
I compared the N54-Alpina file and the N57 file. The adresses are the same. If I make the right settings in WinOLS it finds around 100 maps, but I have no idea if the software is right .
Wich one is the alpina file?
WinOLS will not help you. As DWR found out, the structure of the maps do not follow the Bosch standard structure, so WinOLS will not correctly identify maps. He used an excel file to read in the cal file and convert it to decimal numbers and then some magic on how to identify the maps. Hopefully, he'll let us in on how to exactly transfer that to other cal files. Success in this case certainly doesn't come without sweat.
Mik325tds 06-24-2015 06:12 AM
Quote:
Originally Posted by DWR (Post 18125262)
I'm in the midst of upgrading my map finding tool and have it inoperable right now. But you and the forum will have it shortly after I do . In the meanwhile, this is what I can tell you. After the first block of zeros, use the data value "534C" as the starting point, row1 and column1. The infield data for the shift maps is at row 7839, column 6, starting with value "0122". The maps do not follow Bosch format (that's why I could not find them at first), but rather run infield data consecutively, 10 columns, row 1 to 13, 10 maps, in that sequence.
I'm not quite sure I'm following you. In the file A7610591.0da row 7839 looks like this:
:10E4D00000010303000000140028026C030C03B6C3
Can't find 0122 anywhere close to that. The next 0122 is in row 8008 address :10EF6000. What am I missing?