You will have great difficulty with the Map axis definitions within RR however as Bosch motronic use a very different way of building the axis compared to other manufacturers.
The axis type and length still precede the maps, however because the map axis values are 8bit and the way they define them is as follows, they can't be populated in the same way as most other ecus.
Code:
For example;
In hexadecimal: 6C 0C 05 0A 0A 0A 04 0C 0D 07 10 0A 1E 60
Converted hex to decimal: 208 012 005 010 010 010 013 012 013 007 025 010 030 096
6C is RPM, the axis is 12 bytes long. In order to decipher axis labeling you work backwards. In hexadecimal FF is a blank byte, it tells the programming to ignore this byte or "reset". FF in decimal is 255. Starting at 255 you subtract the last byte's value and then use an engineer designated factor and offset. For RPM it's X*40. (Occasionally axis headers reference 256 for the equation, like this one)
256-96 = 160
160 * 40 = 6,400RPM
30 * 40 = 1200
6400-1200 = 5,200RPM
10 * 40 = 400
5400 - 280 = 4,800RPM
25*40 = 1000
5120-520= 3,800RPM
7 * 40=280
3800-280= 3,520RPM
13*40=520
3520-520= 3,000RPM
12*40=480
3000-480= 2,520RPM
13*40=520
2600-520= 2,000RPM
10*40=400
2200-400= 1,600RPM
10*40=400
1800-200 = 1,200RPM
10*40=400
1400-400= 800RPM
5*40=200
800-200= 600RPM
So as you can see, there's no simple way to define this in RR XML which means axis labels will need to be hard coded.
