[stuartjohn24]

Hi everyone, I notice many people here on the forum are using dashsoft to code their cars. As you are aware with dashsoft you have direct access to the hex values that hold the coding parameters.

The problem is... What do they mean!? It's a painstaking task going through the NCS files to try and decode your options on the fly, therefore I had some free time and i have decided to make an interactive options calculator.

This is a screenshot of the calculator so far:

You simply select the options you have in your car/or want to have and it automatically generates the hex value for each byte of data in line 3002 of the MMI.

I should be finishing this off later this week, so keep posted!

I hope this will be useful!

Stuart

 

[Hamilton1974]

Sweeeeeeeeet!!!!!! :thumbup:

I just made a bid for a 2006 MMI and I've got Dashsoft ready and waiting at home so this was exactly what I needed!!

Awesome work!! :thumbup:

Edit: Just got confirmation that the seller accepted my bid for the FL MMI!

 

[PAPER]

Hi everyone, I notice many people here on the forum are using dashsoft to code their cars. As you are aware with dashsoft you have direct access to the hex values that hold the coding parameters.

The problem is... What do they mean!? It's a painstaking task going through the NCS files to try and decode your options on the fly, therefore I had some free time and i have decided to make an interactive options calculator.

This is a screenshot of the calculator so far:

You simply select the options you have in your car/or want to have and it automatically generates the hex value for each byte of data in line 3002 of the MMI.

I should be finishing this off later this week, so keep posted!

I hope this will be useful!

Stuart

Very Nice Stuart :thumbup:

Sent from my GT-N7000 using Bimmer App

 

[stuartjohn24]

Thanks guys, I'm just seeing how easy it is to build this into a small windows app that will output the data into a line of hex code that can be copied over to dashsoft.

Stuart

 

[Rookie2008]

Thanks Stuart.

 

[wjjklj]

This is very good work.

 

[Lastcombo]

Nice indeed,when your finished we should make it a Sticky:thumbup:

 

[AceFX]

Well done Stuart...... :thumbup:

Ace :typing:

 

[stuartjohn24]

Hi guys, thanks for the comments!

After a pretty hardcore tutorial session on MS Visual Basic, I have managed to compile the excel calculator into a small windows application that will generate line 3002 of the MMI for you, i have only programmed it to code the first two Bytes so far, the rest will follow quickly.

Basically select the options you want, hit the 'Generate' button and the hex string is shown at the bottom.

Here is a sneak peek so far, its my first ever program so its rough and ready at the moment, I will smarten it up later on.

Any feedback or comments will be welcomed.

Stuart

 

[AceFX]

Excellent output Stuart....... when I asked you about an excel spreadsheet, I didn't expect this......... this is SUPER DUPER :clap:

Well done mate :thumbup:

Do you need any codes from me or are you OK?

Can we develop this further to do the CAS, KOMBI, LMII etc?

Can post package today by the way..... $45 AUD about 30 GBP

Ace :typing:

 

[AceFX]

CAS for things like the CA,..... KOMBI for things like TFM, FLA, SEAT BELT, DIGITAL SPEEDO and LMII for things like FLA, AHL, LIGHTING OPTIONS etc...

Don't forget Rear Seat Heating option too.....

Ace :typing:

 

[stuartjohn24]

Hi ACE,

Thanks, yeah the spreadsheet works, but it's annoying as you need excel installed. Works much better like this and it's all one package.

I you have your MMI trace to hand it would be good to check it against this. The 8 bytes at the end hold little useful information. I will add is a couple of options for iPod and remove the legal disclaimer etc...

Yeah it would be possible to do the other modules, the LMA will be a mammoth effort! But if it's limited to common options it won't be too bad.

Thanks ACE, email me your PayPal and I will send the money.

Stuart

 

[Hamilton1974]

Rear Air Conditioning, is that for the seats or something else?
Bluetooth Handset and Telephone, with telephone does that mean the ability to pair any BT phone?

Looks great btw! Can't wait to try it out! :thumbup:

 

[stuartjohn24]

No, it's for the independent rear air con option on the Li's

You have to change the TCU and upgrade the MMI to the facelift version to enable full Bluetooth. ACE started a legendary thread on this back in Feb.

Thanks, should have it 90% functional tomorrow evening, PM me your email addresses and I will email it over. Unless someone can host it?

Stuart

 

[AceFX]

I will send to your private email Stuart...

I know the LMII etc will be huge but I will work with you on it..

This is taking things with Dashsoft to the next level......

Ace :typing:

 

[AceFX]

I will also send the files for LM, MMI, CAS and KOMBI (pre and post facelift) to your private email....

Ace :typing:

 

[stuartjohn24]

Thanks ACE,

Yeah if its limited to the basics it should be pretty simple, I have already mapped out a lot of the memory locations anyway while looking for some hidden functions.

LMA and LM2 modules do not share the same memory addresses for the coding like the MMI, that's something to be aware of.

Stuart

 

[AceFX]

Hi Stuart,

I have sent email.....

Funny thing though with the LM....

I was reading through all the circuit diagrams the other day and I noticed an odd thing. The early LM had a lot of features, then when the first of the 'facelift' arrived, the LM had features dropped and additional modules were added to the car.

Then, in the final release of the 'facelift', BMW went back to the original LM setup, deleted the additional modules, and incorporated the extra features in the actual units themselves.

For example...the AHL. Early LM was setup to send the 'signal' to the headlights, then later, BMW added an AHL module that the LM had to communicate with to drive AHL, then in the late 'facelift', they went back to the design of the very first LM, and incorporated the AHL as part of the Headlights, and deleted the AHL module behind the Glovebox.

I was at my BMW Master Tech mates house the other night doing some experiments on my car and I brought this up with him.

He told me that it is normal for BMW to do this and go full circle on their modules....

Also, apparently, the E66 is the most advanced model that BMW made, and when they released the F01 and F02 a lot of features of the E66 were deleted and not carried over......howzat?

For example. Did you know that the wiper blades have variable park position?..... that is why they last so long...... and because of this .... they deleted it. The F01 and F02 do not have this feature........ and there are many more deleted features.

Next time you park your car, pay attention to the position of the wiper blades, and over a week, you will see they sit in different positions. oh, and they are heated on the windscreen, and they have a snow push feature etc.... the E66 is quite an amazing car.

And that 's coming from the horses mouth....

Ace :typing:

 

[J0HNT]

Hi stuartjohn24,

How is your project moving on?
I was wondering if this could help me out somehow.
With Dashsoft I did some changes to the MMI like the things AceFX explained in his excellent series of video's.
They work beautifully but... if I switch on the cruise control the arrow is not aligned to the speedo dial.
This is a negative error, it could be that the cruise control arrow is set to MLS/HR instead of KM/HR. :dunno:
Switching back to the original values in a bit of a thing, I can't find the bit of paper where I wrote my notes on.

Cheers,
John

 

[stuartjohn24]

Hi stuartjohn24,

How is your project moving on?
I was wondering if this could help me out somehow.
With Dashsoft I did some changes to the MMI like the things AceFX explained in his excellent series of video's.
They work beautifully but... if I switch on the cruise control the arrow is not aligned to the speedo dial.
This is a negative error, it could be that the cruise control arrow is set to MLS/HR instead of KM/HR. :dunno:
Switching back to the original values in a bit of a thing, I can't find the bit of paper where I wrote my notes on.

Cheers,
John

Hi J0HNT,

Its going well, I have stopped work on the calculator software directly at the moment to pursue a further ambitious project that is directly related, its basically a bench test facility that runs off the mains, it has an OBD interface built in and it mimics an E65/66, you can code and flash software to individual modules individually out of the car.

It got a bit more complicated than I first thought, the ignition status is sent via the K-CAN bus, I have built a circuit with a micro controller that sends the correct K-CAN messages to the modules under test to make them think the ignition is on, the MMI for example to make it 'wake up'. I had to sit in the car for hours with a CAN to USB module to find this magic ignition message!

Anyway Its all done so I can develop software and test it without the risk of bricking my own car!

Here is a picture of my old MMI up and running with just 4 wires connected running stand-alone on my test unit.

Anyway, onto your question, I'm afraid I cant help you, its a known issue, its because the alpina KOMBI has a higher top speed, thus the scaling for the arrow has changed, so 60mph on the standard KOMBI bay be at say 10 o clock, but on the alpina KOMBI it would be at say ten to ten. its written into the operating software, as yet there is no known way of changing it or making it tie up with the standard speed ratio on the standard KOMBI.

I know there were a group of people on BMWCODING forum trying to work this out, take a look over there, they may have found a solution.

Stuart