00:00 |
In the next step of our process we're going to open the file that we've read out of our ECU and create a new project.
|
00:06 |
Here we will be dealing of course with our OBD2 read, which we already know is a virtual file, the nice element of this is that while we lose any tune related information, we are going back to stock, the bonus here is that we are dealing with a stock file, so we can start fresh and we know that there's no baked in errors that another tuner has previously applied, we can basically make our tuning changes to suit exactly what we want them to suit.
|
00:34 |
So, let's open our OLS version here and what we want to do is start by clicking on our new project icon.
|
00:43 |
So, now we want to actually find the file that we're dealing with and we can see that one is already listed here, this is our virtual read, which is vr at the end of it .bin, otherwise we can always navigate to find the file itself.
|
00:59 |
So, let's just double click on that.
|
01:02 |
We can click through here and click next, it's going to look for any existing files that match and in this case we haven't got any files that do match this, so we can just simply click next.
|
01:13 |
It's going to extract the information relevant out of the file, we can click next again and now this gets us to the project file information that we really need to fill in here.
|
01:24 |
This has actually done a pretty good job of extracting most of this information already, leaving us with not a lot of work to do, which is nice but not always the case.
|
01:33 |
For a start, the client information here, not going to really bother filling that out, obviously it's an internal project here, we're not doing this for a customer.
|
01:41 |
It has already gone through and extracted all of the information around the vehicle, we can see this is a passenger car, it is an Audi Q7, it is the 4.2 TDI and in this case the model year is 2010.
|
01:55 |
Specifically, it's a 2011 but same build.
|
01:59 |
Again, we've got the option to add some user defined fields here and just really a personal preference, I've got nothing that I need to add to this.
|
02:08 |
We've got the information on the ECU here so this is a Bosch engine ECU, we can see it is an EDC17CP44 as I previously explained and we've got our version etc so nothing really necessary here.
|
02:25 |
Likewise, we've got our engine and most of this has been filled in, we don't have the producer here, but we can go through and we can select Audi from our drop down menu for the sake of completion or sake of completing this as much as we can.
|
02:41 |
Turbo diesel, the displacement, we've got also our output in terms of PS kilowatts and of course the torque and newton metres as well, so nothing really necessary to add in there.
|
02:55 |
Again with our project, not really a lot that I need to add into this.
|
02:59 |
Again this is more important when you are doing this for a production purpose or you are reselling these files.
|
03:07 |
For our purposes, not really too critical.
|
03:10 |
The other element that we will look at here is the communication protocol and it's already shown up that we have read this with the AutoTuner tool and it is an OBD read.
|
03:20 |
So, really in our perspective here, there's actually not been a lot that we've needed to do, which is nice and easy so we can click finish immediately.
|
03:29 |
Now, we've got the file loaded into OLS, it's going through and it's done its background map search and we can see that it has found 596 potential maps.
|
03:41 |
So, at this stage we've created our new project, we've updated that project information to reflect everything that's important to us, we're ready to move on with the next step of our process.
|