WinOLS Mastery: Map Identification & Editing: WinOLS Software and Function Tour
Watch This Course
$299 USD
-OR-
Or
8 easy payments of only $37.38
Instant access. Easy checkout. No fees.
Learn more
WinOLS Software and Function Tour
08.53
| 00:00 | - In this module, we're going to take a look at the properties information that we need to complete or fill out when we're starting a new project so let's do this by jumping into our OLS software and as usual you can follow along by using the file supplied at the bottom of this module. |
| 00:19 | What we want to do is start by heading across to the new project icon in our toolbar here and click on this. |
| 00:28 | This gives us the option of where we want to import our project or file from. |
| 00:33 | In this case we're going to be dealing with our bFlash files. |
| 00:38 | Specifically here we're actually going to be using a file that we downloaded out of our MK5 Volkswagen Golf, in order to see that process, we cover this at the end of our practical skills section. |
| 00:51 | So the one we're going to choose here is our MK5 Golf stock file .bdc this is a bFlash file. |
| 01:00 | So this is an OBD2 read so let's click on that. |
| 01:04 | Once we've selected the file, OLS will open up this import wizard new project window which we can see here and there are a few pages of information we're going to go through, at the moment we're on the information page, not really anything we need to change here, we can click on next. |
| 01:20 | Now OLS is going to go through our available files and it's going to check for similar projects and what it's saying here is that it has found this project already that we've got imported, that is a 100% match. |
| 01:38 | So in this case, we've got a number of radio buttons here that really define what OLS is going to do. |
| 01:46 | Typically what we would end up with is normally cancelling the import and instead we'd open the existing project. |
| 01:53 | It's 100% match so really there's no reason for us to start another project all over again. |
| 01:59 | In this case for the sake of our demonstration, I am going to click ignore similar projects and continue. |
| 02:05 | So we can come down and click next. |
| 02:07 | The next part of this process is that OLS will look online for available check sum modules for this file. |
| 02:15 | Now for our purposes, this really isn't that important because our check sum correction is going to be handled with our bFlash tool. |
| 02:24 | So this is outside of OLS, however depending on the tool you're using, you may want to purchase the check sums for this so this will go through, search for check sums and it has said that the file was recognised successfully and we can purchase the following module to correct the data. |
| 02:43 | In our case again, we don't need to do this so I'm going to click on no and we're going to click on exit. |
| 02:49 | We can now click on next and this is the properties that OLS has actually extracted already from the raw binary file. |
| 02:58 | So this is going to be added in in our next screen. |
| 03:02 | So again we can check this, no need in our case to make any changes, we'll click on next and now we actually get to our project properties. |
| 03:11 | Now on face value this is very tempting to essentially just click finish and ignore. |
| 03:17 | And particularly if you are only doing one or two cars for yourself, that may not cause you any issues. |
| 03:25 | However over time as you start tuning more and more vehicles, spending a little bit of additional time here on the project properties can really help you separate different files and keep an understanding of what you've done, this is really important, particularly if you are going to start reselling these files to other tuners. |
| 03:45 | So I would urge you to familiarise yourself with the project properties and do as thorough job as possible of completing this information as accurately as you can. |
| 03:55 | Now you can always come back and modify this later and we'll show the icon for doing so in a moment but let's go through this. |
| 04:04 | So first of all we've got the client and in this case I'm not really too worried about the client, we're doing this internally for ourselves so it's not particularly important, whether you choose to fill that out is really personal preference. |
| 04:18 | We move on next to our vehicle and this is one that we really do want to fill in as completely as we can. |
| 04:26 | So we can see that some of the information has already been extracted automatically. |
| 04:29 | So we've got the fact that it is a passenger car, it's a Volkswagen and it is a Golf. |
| 04:34 | There's a little bit more information we can choose to add in here. |
| 04:37 | So it is a build five, the type of engine, it is a 2.0 TFSI GTI engine. |
| 04:46 | This skips us through the characteristic and we can choose the model year which in our instance here is 2008. |
| 04:55 | Alright so that's our vehicle information filled out reasonably thoroughly there, that's going to be a good reference when we come back to this at a later point. |
| 05:02 | We've got the ability to add some user defined information if you require. |
| 05:06 | In our case, we're going to leave that blank as well. |
| 05:09 | Then we move onto the ECU so this is important information, however this should be extracted from the binary file by OLS so while it's worth checking and making sure that it all makes sense, in our case we shouldn't actually have to manually update this. |
| 05:26 | What we can see here though is that it is a Bosch ECU and more specifically it's a Bosch MED9.1.5 so that is the controller family. |
| 05:37 | We've also got the software variant which is this data here and we've talked about software variants inside of the course so really important to make sure that we do have the software variant. |
| 05:51 | Moving down, we also have some information around the engine. |
| 05:56 | This hasn't been filled in, and again personal preference here, I do like to be as accurate as possible with this so let's go ahead and complete this. |
| 06:04 | In this case, the engine name is an EA113. |
| 06:11 | It is a turbo petrol of course, a 2.0 litre displacement. |
| 06:17 | Output, this can vary depending on the specifics of your market and your model, I'm going to list this as a 147 kW variant and 280 newton metres of torque. |
| 06:31 | If you want, you can also add information around the emissions standards that this engine complies to and of course the type of transmission, in our case DSG. |
| 06:42 | Moving on, we can also add some information around the project and this again, probably more relevant if you are doing development work for a production tune file. |
| 06:55 | So for example if we skip down here to our project type, at the moment that is listed as in development, if we click on this we can have this as finished, no state, to do, etc, to suit, so basically making sure that this file, if you're going to resell it, doesn't actually get accidentally resold when it is still a work in progress. |
| 07:17 | Likewise for reselling, we can specify exactly what this is. |
| 07:22 | The price in terms of how many credits it is, what the project type is an any details about it. |
| 07:27 | So in other words if it's a stage 1, it's going to pick you up 20 kW or whatever that may be. |
| 07:33 | Lastly we have the communication protocol and some information has been picked up here. |
| 07:40 | However can be beneficial to add a little bit more, specifically here the read hardware is listed as bFlash so that's fine, we obviously used our bFlash interface, however if we double click on this, or click on our icon I should say, and we come down here to bFlash and expand on that, we can choose whether this is a bench boot mode or OBD read. |
| 08:02 | In this case as we know, I did import the OBD2 read so we will update this, and this again just gives us an instant verification of how that file was obtained. |
| 08:14 | Alright we can now click finish and that will complete the import into OLS. |
| 08:21 | Now if you do want to come back and adjust the project details at a later point in time, you will find the little icon in the toolbar up here, we can click on that and that gets us exactly back to where we were so while this is a reasonably simple task, it does really pay dividends if we take the time and fill this out as accurately as we can and you will be thankful of this once your library of tune files and projects starts to grow. |
