WinOLS Mastery: Map Identification & Editing: Step 6: Write File to ECU
Watch This Course
$299 USD
-OR-
Or
8 easy payments of only $37.38
Instant access. Easy checkout. No fees.
Step 6: Write File to ECU
04.50
| 00:00 | - The last step of our process of course is to write our new file into our controller. |
| 00:06 | Although the reality of this is it's going to become an iterative process because each time we make changes that we want to test with our calibration, we're going to need to of course write these into the ECU and then run the car on the dyno and just datalog to confirm the results and the fact that we're heading in the right direction. |
| 00:25 | However the process of writing is the same, regardless if it's the first time or the 20th time you are writing so let's jump into our software here and once we've made our changes, what we're going to want to do is come down here to our toolbar and click on the little export icon here. |
| 00:43 | Because we have made changes to the calibration, it's going to ask us to name this version. |
| 00:50 | It's up to you how you decide to name your files and here I'm just simply going to call this a stage one so we'll enter that. |
| 00:58 | We can add a description if we want, I'm just going to leave this at the moment but absolutely this is a great place to add information about changes you've made in this calibration or what it would suit, perhaps the fuel octane for example. |
| 01:13 | We'll click OK and that will create the new version that we're going to be exporting. |
| 01:19 | Now we need to decide on the format that we're going to be exporting in and this needs to match the tool that we're going to be using to program and we can see here we've already got bFlash highlighted here so this is the format we're going to be exporting in. |
| 01:36 | And it's given us a warning down the bottom here about the checksum status, we aren't using OLS to perform the checksum correction though, this will be done by our bFlash tool so that's fine. |
| 01:47 | We can come down and click OK and now we simply need to name the file and find the location for this so I'm just going to go ahead and place this with my other bFlash files. |
| 01:59 | For our naming strategy, I'm just going to follow the naming strategy we've already used so we'll use the vehicle's registration. |
| 02:07 | And then the type of vehicle. |
| 02:16 | And of course we're going to call this a stage one tune. |
| 02:23 | Right now we've got the file exported, it is in a format that the bFlash tool is going to be able to read so the next step of course is to open our bFlash software, make sure we are connected up to our interface so let's go ahead and do that. |
| 02:38 | Now in our bFlash interface here, we're going to come up to the top left in the toolbar here and click our vehicle selection. |
| 02:45 | We can manually go through and choose Volkswagen but when you're doing a lot of the same vehicle, you can also switch to the history tab here and it'll show us what we've done recently. |
| 02:55 | Now this one here is an OBD2 programming and that is of course what we're going to be doing here so we'll click on that and that will set us up for an OBD2 write. |
| 03:07 | Now what we want to do is select the write icon up here in the toolbar and we'll click write file. |
| 03:15 | Now we need to simply select our new file here which is this top one here, stage one and the bFlash interface will ask if we want to write that following file. |
| 03:27 | Of course at this point what we want to do is make sure that we are connected to the vehicle, make sure that the vehicle is powered up and we've got good battery voltage to the vehicle so that we're not going to end up going flat during the write process. |
| 03:42 | From here we can simply click yes and then we can allow bFlash to go through the process of writing the new file into the ECU, doesn't take too long. |
| 03:51 | Once that's complete we can then cycle the power to the vehicle and we can test the vehicle, start it and make sure that it actually is going to run and everything is working as we'd expect. |
| 04:02 | As I mentioned, this is an iterative process so we'll be doing a lot of this as we make changes to our file. |
| 04:09 | I will also mention here that we have done a bench read as well as an OBD2 read. |
| 04:14 | We have been working from our OBD2 file while we've been making changes to the map so we are going to be reading and writing via OBD2 once we've done our initial bench read. |
| 04:26 | That bench read really is just there as a safety backstop in case something goes wrong, that should allow us to recover the ECU if it does become unresponsive or somehow becomes bricked. |
| 04:38 | This brings us to the end of our worked example, remember if you do have any questions about this particular worked example, please ask those in the forum and I'll be happy to help you there. |
