[OpenFlash]

Hi guys,
We made a few updates to the Template (new graphics) and Protocol to simplify things a bit. Instead of having MSD80/81 N54, MSD80 N52 and MSV70/80 N52 support on the same Template, we divided them up in 3 different Templates that you can upload yourself through the OpenFlash Manager software. This will prevent customers from accidentally configuring the device for the wrong car and not have access to some of the model specific features provided by the OFT. The following instruction is for those with MSD80 DME (2007 and up)

Several updates in the last few days so I'll go through things step by step. The following process should be done by all. Even those who configured the OFT correctly for their car. Mind you, even if you configured the OFT incorrectly, it will still read/write to the DME perfectly fine. But you will miss out on a few features so it's best to do it correctly at this early stage (pre-tuning). Of course, new units are now being shipped out with all these updates so new users who receive their units next week can skip over Steps 2, 3 and 4

Step 1: Download the OpenFlash Manager v1.06. This is the application used to load tunes, update template, download datalog files, etc,. It's a new version that was just made available last night. Just download it and run the setup file. It will automatically overwrite any older version so there is no need to delete any old files manually. Very simple. You can download OFM 1.06 here: http://www.procedetuning.com/328i/do...s-4/index.html

Step 2: Connect OpenFlash Tablet with a WIFI connection on your laptop. Let it run through the firmware update process. It will update to firmware 121 which was just made available last night. After the update process is complete (it may take over a minute), confirm that you see FW ver. 121 displayed on the OFT screen.

Step 3: To go Erase Data section and erase data. This will completely erase the device. There is no need to back anything up since you will re-read your stock DME again (it takes an hour). This is assuming you haven't modified your ROM at all. Which I assume is the case since we haven't posted any tunes up yet If you haven't installed the OFT yet (didn't do the initial DME read), you will get a message saying "The device has never been used". If so, move on to the next step.

Step 4: Download the MSD80 N51/52/53 Upgrade Template file (.SLT) from here:
http://www.procedetuning.com/328i/do...s-4/index.html
Go to "Upgrade" Section and select this file. Press "Start". This process will take 30 seconds or so. When done, disconnect OFT from laptop and go to your car.

Step 5: Plug OFT into vehicle. Go to Tuning section. Select your vehicle. When you highlight your vehicle, confirm that you see "Siemens MSD80" written at the bottom of the screen. Then continue and read the DME. This process will take 1 hour so make sure you have a reasonably healthy battery and that your headlights, stereo, interior lights, etc,. are turned off. Ignition power must be fully ON. This means that you will see the fuel gauge give a valid reading. Also, opening closing doors can turn off ignition unexpectedly as well, possibly aborting the reading process. So we recommend rolling down the driver's side window, closing the door and doing this process from outside the car. Presumably your arms will be long enough to press the ignition button and plug the OFT into the OBD2 port When the reading process is done, you will get a message notifying you and asking you to turn off ignition and press OK. So press OK.

Step 6: Now we will test the realtime data display. Start the engine. Navigate back to main menu in OFT. Go to Diagnostics and select Realtime Display. You should see this:

Confirm that you see Airmass and Relative load channels in there (3rd and 4th in the list). The presence of these two channels confirms that you have the correct non-turbo protocol loaded. If you have the N54 protocol loaded you will see Boost Target and Boost Actual there instead.

Step 7: Disconnect OFT from car and connect it to your laptop running OpenFlash Manager. Go to Download Data and download the "original file". Then please email this file to me (@ shiv@vishnutuning.com) if you haven't done so already AND confirm that you have the correct protocol loaded. I will respond with a tune file for you to upload

Cheers,
Shiv

P.S. Apologies for asking you guys to install the device a second time. I know that 1hr long read is a pain in the butt. But it's best we do this correctly now from the start.

[AlpineSwift]

In the read process now. Should be good to go in about half an hour.

[AMG KLR]

Thanks shiv I no longer have a subie OFT its now the MSV70 beta template

[OpenFlash]

Originally Posted by AMG KLR

Thanks shiv I no longer have a subie OFT its now the MSV70 beta template

[martinlag]

Thanks again for all your help Shiv!

Once I get everything updated, should I proceed with the .dev file install?

[OpenFlash]

Originally Posted by martinlag

Thanks again for all your help Shiv!

Once I get everything updated, should I proceed with the .dev file install?

yep! Please email me if you run into any issue

[AlpineSwift]

Read complete. Shiv, if we already did a read on the DME prior to this update, do you want us to send the new read as well or does it make any difference?

[martinlag]

Originally Posted by shiv@vishnu

yep! Please email me if you run into any issue

Will do. Thanks man!

[OpenFlash]

Originally Posted by AlpineSwift

Read complete. Shiv, if we already did a read on the DME prior to this update, do you want us to send the new read as well or does it make any difference?

If you already did a read before and emailed it to me, the new read file you generate now will be the same. But might as well email it to me anyway. Along with confirmation that you are on the correct protocol.

[AlpineSwift]

Cool. Sending now.

[1QuikWS6]

Excellent instructions - worked flawlessly thru to the end

Now have new/correct protocol

Sent you my new Original ROM 1-16-14

[martinlag]

Side: I like the new background image! haha

[OpenFlash]

Emails answered! Please email me directly if you have any issues. It just so happens that there are a lot of new things happening all at once so I reserve the right to make mistakes this first round

Shiv

[AlpineSwift]

I guess I volunteer as the first one to get an error on this process.

[KingofKingz]

Nice writeup, shiv. Will go through this process in the afternoon and see what happens

[OpenFlash]

Hi just took a closer look at the ROMs that you guys sent me. Several of your guys have ROM type (CAL ID) MI20S. Funny thing is is that when I actually compared all M120S ROM files, they don't all share the same mapping values which is unlike any other MSD80/1 ROM I've seen. Usually, if two ROMs share the same CAL ID, they share these same mapping values. So it looks like I will have to create tune file individually for many of you guys since the patch function won't work if the original ROM files are different (useful safety feature). Which is probably why a few of you guys didn't see an automatically generated tune file when you uploaded the .dev file I emailed you.

I'll be doing this tomorrow (it's 2.10am now) and my eyes are blurry for looking at hex so map editing isn't the best idea right now

shiv

[1QuikWS6]

Originally Posted by shiv@vishnu

Hi just took a closer look at the ROMs that you guys sent me. Several of your guys have ROM type (CAL ID) MI20S. Funny thing is is that when I actually compared all M120S ROM files, they don't all share the same mapping values which is unlike any other MSD80/1 ROM I've seen. Usually, if two ROMs share the same CAL ID, they share these same mapping values. So it looks like I will have to create tune file individually for many of you guys since the patch function won't work if the original ROM files are different (useful safety feature). Which is probably why a few of you guys didn't see an automatically generated tune file when you uploaded the .dev file I emailed you.

I'll be doing this tomorrow (it's 2.10am now) and my eyes are blurry for looking at hex so map editing isn't the best idea right now

shiv

I haven't tried my tune Write yet, but my ROM type IS Cal ID MI20S as above

[KingofKingz]

So, sitting in the car right now. Hopefully doing everything correctly. Initially bought an 325i, but with the 3 stage manifold and the tune it should at least be a 330i. Therefore i selected 330i. So, lets see what happens.

Edit: everything went well. Send you my file, shiv.

[AMG KLR]

Would anyone be interested in the mounting solution for the oft?

[OpenFlash]

All issues should no be solved with the Tune file. I have create a new database that distinguishes between ROMs that have same CAL ID but different hardware ID

If you have emailed me your original ROM and are still waiting on a working Tune File, please email me (shiv@vishnutuning.com) and i'll send you the new .dev file to upload!

Cheers
Shiv

[1QuikWS6]

Originally Posted by AMG KLR

Would anyone be interested in the mounting solution for the oft?

Mounting solution?

[AMG KLR]

Originally Posted by 1QuikWS6

Mounting solution?

This fits it perfectly and attatches to vent
http://www.amazon.com/Bracketron-PHV.../dp/B0014S5FVQ