×

Sale ends todayGet 30% off any course (excluding packages)

Ends in --- --- ---

WinOLS Mastery: Map Identification & Editing: Finding and Defining Maps - Shared and Remote Axis

Watch This Course

$299 USD

-OR-
Or 8 easy payments of only $37.38 Instant access. Easy checkout. No fees. Learn more
Course Access for Life
60 day money back guarantee

Finding and Defining Maps - Shared and Remote Axis

15.23

00:00 - The next map that we're going to find is our driver's requested torque or driver's wish map as it's often referred to.
00:08 Essentially the map that converts our driver's pedal positon into a requested relative torque value.
00:15 So the requested relative torque, this is a 0-100% value so it isn't a specific torque value in newton metres, it's relative torque as a percentage.
00:26 The added little complexity with this set of maps is that first of all, there are a number of different maps here as we'd expect by now and instead of using the, instead of including I should say, the axes at the start of each of the areas of map data like we've just looked at, this time each of the driver's wish maps shares the same axis values and these axis values are located at the end.
00:54 So let's jump into the laptop here, this is our screenshot of the sort of shape that we're looking for here.
01:02 So quite a specific shape and we can see we've got in this case, one, two, three, four, five and six of these maps.
01:14 So those are the maps that I've just circled here and obviously this screenshot is from a set of maps that have already been defined.
01:21 We can see that we've got this particular map here, the second one is the one that has been selected.
01:28 We can see at the same time out to the right hand side, we've got these other two areas that are also highlighted, this represents the axis values for all of these maps so this is what we're looking for.
01:41 Let's head back into our OLS software and we'll pick up essentially where we left off.
01:47 We are still on our driver's requested lambda values or tables I should say and now what we want to do is go ahead and find those drivers wish tables.
02:00 Now problem we've got here is we don't really specifically know whether we want to be going left or right and sometimes it is literally just a case of going in one direction to the end of the calibration data and finding out that it wasn't the right way that we chose.
02:16 I'm going to shortcut things here a little bit because I already know that the, I know the address for these particular maps that we're looking for and I know that we need to go out here to the left quite some way so let's just click to the left here and we're looking for an address of about 1CC so let's just go through until we find those.
02:48 And there we go.
02:50 So while I did sort of take a bit of a shortcut here, there really is no way of knowing sometimes and if you aren't just starting at the very start of a calibration and working your way through, defining the maps as you stumble across ones that you recognise and you are going through out of order like we are doing here, sometimes you will end up having to go back and forth until you find what you're looking for but here we do have our data.
03:16 Let's just change our X axis scaling a little bit so we've got a better idea of what we're looking at here.
03:23 And we can see our six tables, six maps and we've got our axis values out here on the right hand side.
03:32 So what we're going to do for the moment is just ignore the axis completely and I'm going to start by finding and defining this last map out here on the right hand side.
03:43 So what I'll do is I'm just going to put my cursor somewhere near where I think the end of that data is and this is just a visual representation, we don't have to be too accurate here but I can be pretty sure that the end of this table is somewhere around about here.
03:57 Let's now switch across to our text view.
04:00 Alright so at the moment everything's looking a little bit messy, let's just scroll down a little bit, so not working right at the end of our screen, we're right at the bottom of our screen.
04:10 And we really don't know what the size of this table is going to be.
04:14 And we're going to just manipulate our view here until what we've got out here on the right hand side starts to form something that makes a little bit of sense so right now, we've got our width set to 10, this is just wherever we happen to be.
04:30 So let's just add a few more columns and see what happens to the shape of our visual representation out on the right hand side.
04:38 So as we click M, what we can see is that there's now a bit of a diagonal trend forming and particularly what I'm looking for here is we can see we've got a line coming down here, it's not quite right, when this all gets to the right width to suit the size of our table, that should become a nice straight vertical line so let's go again, we'll press the M key one more time and now we can see that's exactly what we've got, we've got this vertical line here.
05:08 So this is starting to look a bit more like a table.
05:10 However, if we look at the entirety of the visual representation here, we can see it's still now quite right, sort of starts at nothing then jumps back up and then starts diving away so what we'll now do is use the control key and if we click on the right arrow key, we can see now we've actually got something that looks about right.
05:29 We've got values that kind of make sense here, we've got a bit of a shape to that that actually makes sense so now I'm pretty confident that I've got my table area.
05:40 And we can see up here we've got these values of zero.
05:44 Now remembering that this is a requested torque table.
05:48 It'd be fair to assume that when we are at a driver's pedal position of zero we would in fact be requesting 0% torque.
05:57 And then at the bottom here we've got these values here which hopefully we should be starting to recognise here, 32768, remembering when we divide that by a factor of itself, we get to 100% so this is starting to look like we've got values that would in fact be a driver's wish table.
06:16 So let's click on our top left corner here and we'll come out to the right here and then we're going to come down and we will see that the map structure, down the bottom left corner is a 12 x 16 so a width of 12 there and a depth of 16.
06:37 Let's press K to mark that map and we've got our map marked.
06:42 Obviously at the moment we don't have our axes defined, that's fine.
06:46 While we are here, let's have a look and see what we can do with those factors.
06:51 So let's double click on our map data and this is going to be our driver's wish table or driver's relative torque request, so we'll enter that.
07:09 OK we've got our name added there, I'm going to use control and A and then control and C, we'll tab down to our description, control V.
07:18 Can be as fussy with the information you're inputting here as you want.
07:22 What I would recommend is that you try and be consistent with your naming strategies.
07:26 That will certainly help across multiple files and it'll also help, once you start using folders which we'll look at a little bit later on in our practical section.
07:37 Let's come down here to our units and we know that this is going to be percent.
07:43 Let's have a look at our factors down the bottom here and we're going to of course click on our little function icon and click on our output radio button.
07:53 So we can see our table values while I'm doing this but let's just move this down a little bit further and if we change our divisor here and we'll enter 327 and .68, that will give us the range that we want.
08:10 We'll click on OK here and again, it's always a good idea to add a little bit of precision there so we'll add two decimal places there but again we've got what does make sense now as a driver's wish table.
08:23 Let's close that down and we'll press escape.
08:25 Now we need to find our axes.
08:28 And what we can see here is again when we escape out of this, already we've got OLS highlighting the next set of values down, thinking that this is the next set of tables and unfortunately it's dead wrong so we'll press delete and get rid of that.
08:43 Now let's just momentarily head back to our 2D view and we already know that our axes are located here at the end so let's go back to our text view and see what that looks like.
08:55 That corresponds with the data directly after our table and if we look at our first value here, we can see we've got a value of 12, now we already know that this corresponds to the width of our table, it's 12 x 16 so in this case, the first value after this is going to be the frist value of our X axis so we'll highlight that, right click and we will click there on address as X axis of the previous map so OLS knows that this is now going to be associated with that previous map, job done there.
09:30 Straight after our 12 values there for our X axis, we see that the next value is 16.
09:37 So again this indicates that the 16 values directly to the right of this are going to be the values of course for our Y axis so we'll highlight the first of those, right click and of course we're going to select address as Y axis of the previous map.
09:53 Alright so now that we've defined our axis, obviously these are going to be raw values but let's double click and see what everything looks like.
10:00 Alright so once you start getting familiar with these numbers, again these will start to make sense, you'll start to understand when you see these raw values, what the actual axis values are going to be.
10:11 So let's start with our Y axis here and we can see we've got values up to 65535.
10:17 And again from our logical values we know that 65536 is one of those values, obviously we're going to divide that out, we're going to get a value that's going to essentially be 100%.
10:29 This is going to be our driver's pedal position so let's double click on our Y axis and we'll enter exactly that.
10:43 When we come down to our factor here, we're going to click on the factor function icon, click on our output radio button and again I'll just move this out of the way so that we can actually see how those raw values change and we'll enter 65000, in this case we want 500 and then a decimal point, 0.36, that gets us to 0 to 100, we'll click OK and again we might want to add a little bit of precision into that axis as well, job done there, we can click OK.
11:18 The other axis that of course is going to go along with this is engine speed so let's double click on our engine speed axis.
11:27 At the moment 24000, possibly a touch optimistic for our little Volkswagen Golf but let's enter our description.
11:39 Our units of course are RPM and we can enter an ID for that and then for our value here we're going to enter a value of 0.25.
11:53 Straight away we've now got our values spanning 400 to 6000 RPM, makes sense there.
11:58 And again this is one of those cheat values that we've also included as a common factor for scaling the RPM axis.
12:07 Let's click OK, job done there.
12:10 Press escape, that is the fist of those tables now found and marked.
12:16 In this case, we're going to use the same techniques we've already looked at in terms of copying the map structure into the other maps we're going to define.
12:25 But this time there is one small change because each of these maps shares the same address for the X and Y axis, remembering we don't have that X and Y axis values repeated for each map.
12:37 Everything's going to be referencing those same X and Y axis values or addresses.
12:43 So what we can do here is right click and again we want to copy our map properties.
12:49 We want to of course continue with our description, our name, description, our factor, our offset etc, this time though when we come across to the right, we also want to click our data source plus address.
13:04 We want to make sure that we are only doing this for the X and Y axis, not the map data.
13:10 So essentially in plain English, what that's going to do when we paste this map structure into the other maps that we're doing to define, it's going to copy the map, X and Y axis addresses exactly as they are for the map just copied from.
13:27 So job done there, we'll click OK.
13:29 Let's now scroll up and we can now define our next map so looking at everything at the moment, basically exactly the same, we can see this line here of zeros, so it basically repeats the same trend that we've already seen so we'll click the top left corner, we want to now hold down our shift key and we'll use our right arrow key and we want to come across 11 for a total of 12.
13:56 One, two, three, four, five, six, seven, eight, nine, 10, 11.
14:00 Now of course we want to come down 16, or 15 for a total of 16.
14:05 So one, two, three, four, five, six, seven, eight, nine, 10, 11, 12, 13, 14, 15, 16.
14:11 We'll press the K key, that's going to mark that map, control V and now we can see that straight away we're not only applying our scaling factor to our map data, we've also copied in the address axes and the address scaling so our job's done there.
14:28 We'll press escape and we've now marked our second map.
14:33 Now we've got six of these maps, I'm not going to go through the process of marking each one but for the sake of completeness let's just do one more so we'll scroll up again.
14:42 So we are kind of working in reverse order here.
14:44 Again we find that first top left value where we've got that line of zeros, hold down our shift key and we'll mark across, holding down our shift key still we'll mark down.
14:57 K to mark that map, control V and our job's done so this is going to again be a rinse and repeat for the remaining maps so now we've see how we can find our driver's wish tables or maps and how we can define these maps when we've got a series of maps that use exactly the same axis.
15:18 Let's move on and have a look at one more demonstration.

We usually reply within 12hrs (often sooner)

Need Help?

Need help choosing a course?

Experiencing website difficulties?

Or need to contact us for any other reason?