Version 1.5.7
Application Guide
Data Log Lab is a car ECU data log graphical analysis tool. It enables rapid and meaningful analysis of the information that is hidden within the data logs output by various after-market replacement car ECUs. It offers far more functionality than the manufacturers’ original software and access to it in a far easier way. It’s combination of power and ease of use has already won it many satisfied customers. Here is a summary of its features:
· View any combination of data on a single large time-based graph.
· Compose your own analysis graphs using any of the engine parameters within the data log, e.g. O2 v RPM, MAP v Knock, etc.
· Produce instant Power and Torque curves.
· View accurate speed versus time graphs to give in-gear acceleration.
· Create your own preset time-based and data-based graphs.
Owners of Flyin’ Miata’s Link ECUs have the following additional features:
· Capture data logs from the ECU whilst driving.
· Amend all ECU settings within a comfortable GUI environment and upload changes to the ECU.
· View changes made by the ECU to your fuel and ignition timing.
· View 3D graphs of the fuel and ignition maps.
· Compare your fuel and ignition settings to the supplied benchmarks or to your own benchmarks.
· Copy settings from benchmarks and upload to the ECU.
· Save and Load ECU settings to create a library of configurations suitable for different events (daily driving, track driving, etc.).
· Launch the capture of new data logs from within the application.
The program has been developed in Visual Basic 6 and tested on Windows 95, 98, 2000 Professional, NT version 4.0, and Windows XP machines, with processor speeds from 100MHz, and total system memory from 4Mb. It runs quicker on the PCs with faster processors! The minimum recommendation is a 200MHz processor and 32Mb of memory. A screen resolution of 800x600 pixels or greater is required - the bigger the better as far as graph detail is concerned. The install requires approximately 15Mb of hard disk space.
The application supports most Windows Locale settings.
The application’s on-line help
requires a web browser installed on the computer.
Data Log Lab is able to analyse data logs generated from the following after-market ECUs and their related software:
|
ECU |
Software |
Web Site |
|
Apexi Power FC |
FC-DataLogIT |
|
|
Electromotive Tec-2 |
WinTec2 |
|
|
Electromotive Tec-3 |
WinTec3D |
|
|
Flyin’ Miata Link |
None required |
|
|
GEMS EMS |
GEMS GWv3 |
|
|
Hydra Nemesis 2.1 |
Nemesis 2.1 Software |
|
|
Innovate LM-1 and LM-3 |
LogWorks |
|
|
Link Engine Management Link |
PCLink |
|
|
Link Engine Management Link Plus |
PCLink |
|
|
Link Engine Management Plug-In |
PCLink |
|
|
Nissan OEM |
Nissan Datascan |
|
|
TurboXS UTEC |
CSV format files only |
|
|
Xede |
Xede Tuning Software |
|
|
Zeitronics ZT-1 |
Data Logging Software |
Note that
new ECUs are frequently being added to this list – check the Data Log Lab web
site (http://www.dataloglab.com/) for the latest information.
The software is fully compatible
with all Flyin’ Miata Link ECU chips dated up to 1st August 2005.
The additional Flyin’ Miata Link features within the application rely on software written by Ray Ayala and Jeff Thomson (MDOS.EXE and LINKWIN.EXE respectively) to acquire data logs and upload zone settings. Without both their software and assistance, many of the features of Data Log Lab would not have been possible. It is with their kind permission that I can include their software within the installation on Data Log Lab and save you guys some hassle.
My thanks go to Jason Cuadra and
Steve Willington who gave me invaluable advice for the power and torque
calculations and power graph curve smoothing, and Tony Schreiber who pointed me
in the right direction with the HTML of these instructions.
1. Uninstall any previous version of the software. Don’t worry about any files that you’ve created within the Data Log Lab directory structure, or about your personal settings – these will all remain intact.
2. Extract the archive (DataLogLab_v152.zip) to a temporary directory. This should give you the following files:
DataLogLab.msi
InstMsiA.exe
InstMsiW.exe
setup.exe
setup.ini
readme.txt
3. Before commencing installation be sure to look at the contents of the readme.txt file which will contain any late-breaking information or issues with the software. In addition, also check the Known Issues page on the Data Log Lab Web Site to see if any even-later-breaking information or issues have come up.
4. Run Setup.exe. The Microsoft Installer that the application uses may need to install some necessary files of its own and then request a re-boot of the computer before it automatically continues with the installation of the application.
5. You will need to accept the licence agreement to continue. After this, confirm the installation directory. You may get asked whether you wish to overwrite newer versions of some of the files the installer is trying to place in your windows/system directory – answer 'no' to these. A folder and icon will be created in the Start menu, and an icon placed on the desktop, either of which can be used to run Data Log Lab. Note that data logs and Link ECU setting files (MAP files) can be dragged and dropped on to the desktop icon to launch the application and automatically load the file, and if the file is a data log also automatically draw a Sample Graph of it.
The Welcome screen is shown the first time you run Data Log Lab. It performs two main functions: to explain how the 30-day trial period of Data Log Lab works and to let you tailor the initial configuration to the type of ECU you are going to use the program with. You’ll continue to see the Welcome screen when you run Data Log Lab until you’ve made your decision about which ECU to bias the application towards!
If you ever want to be given the option of choosing your ECU type again, simply delete the DataLogLab.ini file within the Program sub-directory of the installation directory (if you’ve installed to the default location this will be C:\Program Files\DataLogLab\Program\DataLogLab.ini). PLEASE BE AWARE THAT THIS WILL RESULT IN THE LOSS OF ALL CHANGES YOU HAVE MADE TO THE APPLICATIONS CONFIGURATION SINCE FIRST RUNNING IT.
Highlight the type of data log you want to configure Data Log Lab to use, or if you have an alternative Universal Data Log Definition file, highlight “<Other>”.
This field is only enabled if the Data Log Type is set to “<Other>”. If you have an alternative Universal Data Log Definition file, type the full path and file name of the definition file into the field, or use the Browse button to the right of the field to select the file.
1. If you are upgrading from a previous version of Data Log Lab do not worry about the following instructions – your settings will have been retained.
2. For new installations, follow these steps.
3. Run the application. The splash screen is displayed whilst the main application loads.
4. Once the continue button becomes available, press it to move to the main application.
5. Select the Options item of the Customise menu.
6. If you already have already purchased your software key, you can go to the General tab and enter it there. For more details on how to do this go to the Security Frame section of the Options window definition.
7. The File Locations and Power Graph tab is used to specify where various files the application needs to access are stored, and some defaults for use when generating Power Graphs. You can set the working directory (where all the files Data Log Lab generates will be saved by default), and your own background picture to be displayed in the graph windows of the application prior to actually drawing graphs. The default data log type for the Open File dialog when loading a data log should already be set based on your selection in the Welcome screen.
8. Whilst in the File Locations and Power Graph tab, if you’re not at sea level, set your ambient atmospheric pressure in the Default Atmospheric Pressure field (this is used to calculate the boost and vacuum data items), and set your typical ambient temperature and humidity.
9. The Data Item Definitions tab is used to control what data items (e.g. RPM, A/F ratio, ignition advance) are displayed and how they are displayed. Because Data Log Lab can load many data log formats some of the data items are only relevant to that type of data log. Your selection in the Welcome screen will have resulted in those not relevant to your ECU type being disabled. If there are still data items checked that you know are going to be of no interest to you, feel free to remove their checks as well. At some point in future once you are more comfortable with the application, re-visit the Data Item Definitions tab of the Options window to review the list of the checked data items again.
10. Click the OK button to exit the options window, and then select the Car Definition Editor item from the Customise menu. A car definition contains gearing, weight, and aerodynamic information that enables the application to accurately calculate torque and power. The application ships with a default configurations for various cars. If yours is there, or similar to one that’s there, simply amend the information to reflect your car, or alternatively check the car definitions files on the Data Log Lab web site to see if one already exists for your car that can be downloaded. See the Car Definition Editor section for more details on either of these processes.
11. Initial configuration complete!
12. Select the Options item of the Customise menu.
13. The FM Link ECU tab is used to set up the application specifically for your ECU. Firstly, in the Link ECU frame, set your ECU’s chip type and date. If Silent Defaults is checked, these defaults will be applied wherever necessary without informing you. If Silent Defaults is unchecked, a message will be displayed. This ‘applying of defaults’ typically occurs when loading in older data logs that have the information stored in a different enough format for the application to fail to find it.
14. Next, set the COM port of your computer that you use to connect to the Link ECU. This field can be found in the General Settings frame.
15. If you do not have the intake air temperature sensor fitted, you should change the Data logging/Upload program from ‘MDOS_AT.EXE’ to ‘MDOS.EXE’. Although Data Log Lab ships with the most current version of LinkWIN.EXE, for real-time fuel and ignition tuning, we recommend you install Stan Mahaffey’s excellent RTLink. Once RTLink has been installed, simply change the Data Logging/Upload Program to RTLink.EXE. For more information, see the RTLink section at the end of this documentation.
16. Configuration complete. Click OK to exit the options window.
Data
Log Lab ships with a built-in fully functional 30-day trial. After this is over, the application will
disable itself until a software licence is purchased and software key(s)
obtained. Each
installation of the software will require its own unique software key. The software licence entitles the purchaser
to unlimited software keys if they are for use solely on computers the
purchaser owns, or for use on a single workstation used non-simultaneously by
multiple people, but not both. In other
words, if you own several laptops and a desktop, you only need to by one
licence to install the software on all three machines (as long as they’re all
owned by you, or are not going to be used simultaneously), though you will need
to obtain three software keys. For
information on how to purchase a software licence and obtain a software key,
visit the Data
Log Lab web site.
Data Log Lab® v1.5.2 Copyright © 2005 Glenn Johnson.
All rights reserved.
By using, copying, transmitting, distributing or installing Data Log Lab, you agree to all of the terms of this License. If you do not agree to any of the terms of this License, then do not use, copy, transmit, distribute, or install Data Log Lab.
This is not free software. Subject to the terms below, you are hereby licensed to use this software for evaluation purposes without charge for a period of 30 days. After the 30-day evaluation period is over, the software will disable itself until a software license is purchased and a valid software key entered.
Unregistered use of Data Log Lab after the 30-day evaluation period is in violation of U.S. and international copyright laws.
Under no circumstances whatsoever should any unique software keys be given to other people.
Each installation of the software will require its own unique software key. The software licence entitles the original purchaser to unlimited software keys if they are for use solely on computers the original purchaser owns, or for use on a single workstation used non-simultaneously by multiple people, but not both. The software licence cannot be sold or transferred, but will remain the sole property of the original purchaser.
This software, and all accompanying files, data and materials, are distributed "AS IS" and with no warranties of any kind, whether express or implied. This disclaimer of warranty constitutes an essential part of the agreement. In no event shall Glenn Johnson be liable for any incidental, consequential, or punitive damages whatsoever relating to the use of Data Log Lab.
All rights of any kind in Data Log Lab that are not expressly granted in this License are entirely and exclusively reserved to and by Glenn Johnson. You may not rent, lease, modify, translate, reverse engineer, decompile, disassemble or create derivative works based on Data Log Lab. You may not make access to Data Log Lab available to others in connection with a service bureau, application service provider, or similar business. There are no third party beneficiaries of any promises, obligations or representations made by Glenn Johnson herein.
Copyright © 2005 Glenn Johnson. All rights reserved.
The application ships with a comprehensive help file (you’re reading it). This can be launched via its icon within the application’s folder in the Start menu, or in a semi-context sensitive way by pressing [F1] within any of the application’s windows. If this help file doesn’t answer your questions, visit Data Log Lab’s web site and check the ‘Frequently Asked Questions’ and ‘Known Issues’ pages, and if your question is still unanswered you can find details about who you can contact for additional assistance.
The bulk of this guide is a
screen-by-screen reference. Most people
like to jump straight in, have a play about, reach a ‘brick wall’ and then go
to the detailed reference. Therefore,
with most people in mind, here’s the Quick Start section!
1. Select the Open item of the File menu of the main screen of the application. Ensure that the Files of Type field is set to the type of data log you are about to open.
2. Using the Open dialog box, go find your existing data log and open it.
3. Watch the progress bar at the base of the screen as the file loads. If the application has trouble loading the data log it will report it to the screen.
4. Once the data log has loaded, the bottom right corner of the screen will show the sample number range from the data log, the From and To fields will be populated, and the Draw button will be enabled.
5. Click the ‘Overview’ entry in the Preset Graphs list and then press the Draw button. An overview of the entire file is now displayed in the main window.
6. OK, let’s look in more detail at a specific area of the data log. Click a point on the RPM line of the graph that corresponds to the centre of the region that you want to look at. If you’ve selected the point successfully, it will appear as a little black square.
7. Click on the ‘Knock Investigation’ entry in the Preset Graphs list, set the X field to ‘5’ and then click the button to the left of it with the picture of a ‘+’ in it (Zoom In button). Alternatively (and this is recommended), right-click the graph, highlight Zoom In and then highlight X 5 in the sub-menu next to it. Even more alternatively, right-click the graph, highlight Goto Sample, ensure that User Show Point Width is checked in the Goto Sample window and then press OK.
8. You should now have zoomed in to the sample that you clicked on, and be seeing much more information plotted on the graph. Have you noticed how clicking on a Preset Graphs list entry simply sets a pre-defined collection of check boxes against data items in the list below the Preset Graphs list?
9. Now we’re looking in some detail at a particular area of the data log. If you click one of the arrows at either end of the scroll bar beneath the graph, notice how the graph scrolls in that direction in small steps. If you click on the light grey areas either side of the scroll bar’s ‘button’, the graph moves in that direction in large steps. You can also click and hold down the scroll bar’s button with the mouse and then drag it freely to the left and right. When you let go, the graph will be re-drawn to that relative position of the data log.
10. Let’s return to the overview of the data log. Select the ‘Overview’ entry of the Preset Graphs list and then click on the Zoom Out Full button – the one immediately to the left of the X field.
11. Now we’ll look at a Scatter Graph of the data log. Select the Scatter Graph item of the Tools menu.
12. Double-click on the ‘Knock Profile’ entry of the Preset Graphs list (or any other entry if ‘Knock Profile’ isn’t displayed for your data log type).
13. Once the graph has drawn, what you are seeing is all the output of the knock sensor against RPM wherever that output was greater than a certain intensity. This particular graph is great as a first step after loading a log to quickly see whether you’ve had any knock and whether it is concentrated in particular areas of the RPM range.
14. Select one of the points on the graph that particularly interests you by carefully clicking it. Notice how all the details of the data log record that you highlighted are displayed in the Sample Details list. Next, click the Show Point button.
15. Now you’re back in the Sample Graph window with your selected sample centre stage on the graph. Select the ‘Knock Investigation’ entry of the Preset Graphs list and the click the Draw button.
16. Now you’re looking in detail at a knock event that you found quickly and easily using the Scatter Graph. You can click back into the Scatter Graph, highlight another point on it and click the Show Point button to move the Sample Graph on to that sample. You can also double-click a point on the Scatter Graph instead of clicking the Show Point button.
The Power Graph needs a single gear
1.5k RPM to redline run to be able to produce consistent results. Therefore, if you don’t already have a data
log with one of these in, best go generate one! For accurate figures, you also need to set the various aspects of
the drive train and aerodynamics of your car using the Car Definition Editor.
1. Ensure your Power Run data log is loaded into the application.
2. In the Sample Graph, Navigate around the data log and zoom in so that you can see slightly more of the data log than just the area where the Power Run occurred.
3. When displaying a Power Graph it is important that only an area of continuous acceleration is used as the basis of the calculation. This combined with the fact that the Power Graph window will inherit the displayed range from the Sample Graph, and the fact that it’s a lot easier to see the start and end of the power run in the Sample Graph, means that you want to ensure that the Sample Graph is displaying the exact start and finish of your power run before opening the Power Graph window. Got that? Re-read the paragraph if you haven’t because it’ll be worth it in the end!
4. OK. Let’s get the plot range of the Sample Graph dead right before we open the Power Graph window. We recommend displaying just the RPM, manifold air pressure or boost, and throttle position in the Sample Graph - the throttle position will tell you when you put your foot to the floor. Select a point on the RPM that corresponds to the start of the power run – usually when manifold air pressure reaches atmospheric pressure (around 100 kPa), or boost is noted. Right-click the graph to bring up its context menu and then select the Set Plot From item from it. This will simply place the sample number of the highlighted point into the Plot From field.
5. Select a point on the RPM series that corresponds to the end of the power run – typically just before the RPMs start to drop. Right-click the graph to bring up the context menu again and this time select Set Plot To and Draw Graph. The Sample Graph should now re-draw with just the power run range displayed. If you have any hiccups at either end, repeat the procedure until you just have an area of continuous acceleration displayed – remember you can zoom out if you need to. For Flyin’ Miata Link users, if during your power run, as you approached red line you passed the point where the Link’s MAP cut began, this will be evident on the Sample Graph as the MAP rising as pre-cut off ignition retard comes in. Ensure that the point you use to mark the end of the power run is not more than a couple of samples beyond the point where MAP starts to rise, else your Power Graph will ‘dragged down’ by the falling engine power after the MAP cut.
6. Select Power Graph from the Tools menu to open the Power Graph window. When the window opens it will immediately draw a Power Graph using the first Car Definition in the Car Definition list, and assuming the default Power Graph conditions as set in the File Locations and Power Graph tab of the main Options window. If the Car Definition that relates to your car isn’t the one first displayed in the Car field, then select the right one, and make a mental note to go to the Car Definition Editor later and move your Car Definition to the top of the list. If you have you car’s drive train details accurately set up in the application’s options, all you need to do next is set the Gear field in the Graph Contents frame and then activate the Draw Graph button.
7. Abracadabra! Power and Torque curves for that particular power run. Note that many external things can have quite an effect on these curves – wind, slope and curve of road, etc. We were very surprised at the different but consistent results obtained using two stretches of road that had slight slopes on: 20 lb.ft was the effect. Even tyre radius can have a dramatic effect: 5mm of wear can affect the power runs by 10 lb.ft.
8. Next step. It’s alright being able to produce power and torque curves, but what is really useful is being able to compare them from one tuning session to the next. We’ll load in a benchmark to be drawn on the graph along side your own curves.
9. Within the Power Graph window, select the Open item of the File menu. The application ships with an example power graph so find this and load it in. The field will display its name and the Action field will be automatically set to “Show”. Activate the Draw Graph button again and this time your power and torque curves will be accompanied by the benchmark.
10. Well I hope the comparison was good news. The example benchmark was generated from a ’97 1.8 Mazda MX-5 FMII turbo running about 14.5 PSI of boost, outside temp around 10 Celsius. In fact, if you ever want to see more details about the benchmark you have loaded, go to the Calculation Details item of the Benchmark menu to open up the Benchmark Details window.
11. You can create your own benchmarks by using the Save As/Save items of the File menu.
12. OK. The last aspect of the Power Graph is its derived Speed Graph. This is useful for finding in-gear acceleration times for comparison against your favourite super cars, etc.
13. With a Power Graph calculated and displayed, select the Speed Graph item of the Tools menu to open the Speed Graph window. If you have a power benchmark loaded, the Speed Graph will contain a series for your power run and the benchmark. The contents of the Graph Options frame can be used to change the units the speed graph is displayed in, and to move the benchmark curve relative to your own for comparison that is more accurate.
14. Finally, let’s use the Acceleration Time Query frame to tell us exactly how long it took you to accelerate between two speeds. Click the speed curve at a point that corresponds to the speed you want the acceleration timing to start from, this should result in the point being highlighted. Right-click the graph to bring up its context menu and then select the Set Speed From item from it. This will simply place the speed at the highlighted point into the Speed From field in the Acceleration Time Query frame.
15. Select a point on the speed curve that corresponds to the speed you want the acceleration timing to finish. Right-click the graph to bring up the context menu again and this time select Set Speed To and Calculate. The You and Benchmark fields within the Acceleration Time Query frame should now be populated with the calculated acceleration time. You will see the text ‘N/A’ in either of these fields if the speed range selected for the calculation is outside the speed range plotted for the power graph or the benchmark respectively.
Organising the application’s defaults
can be done with or without a data log loaded.
1. Select the Preset Scatter Graph Editor item of the Customise menu of the Sample Graph window to open up…wait for it…the Preset Scatter Graph Editor.
2. The Preset Scatter Graph Editor displays a list of all the existing Preset Scatter Graphs that have been defined. Click the New button to open the Preset Scatter Graph Details window.
3. Start by giving the preset graph a useful name. The graph we are going to create in the tutorial is extension of the ‘Knock Profile’ preset that ships with the application, so let’s call it ‘Knock Profile 2’.
4. The Licence Type field will default according to the application’s default data log type that was chosen in the Welcome window on initial install, or changed later in the File Locations and Power Graph tab of the application’s Options window. If this isn’t the type of licence that you want to create the Preset Scatter Graph for, select the right one.
5. Leave the Auto Draw field unchecked for now.
6. Next we set X Axis to ‘RPM’ and then Y Axis to ‘Knock’.
7. Next we click on the New button in the Filters frame to open the Scatter Graph Filter window. Set the Data Item field to “Knock” and the From field to “30”. This will pick up all samples that have a knock intensity greater than or equal to 30, with no upper limit. Click the OK button to create the first filter.
8. Click on the New button in the Filters frame again. Set the Data Item to “MAP” and the From field to “100”. This will ensure that we that we only see samples that occur under boost. If “MAP” isn’t shown in the Data Item field drop down list, it’s because your data log format doesn’t contain it - use “Boost” or another alternative instead.
9. Finally, lets give the points a distinctive look to make then stand out. Within the Point Details frame set Size to ‘10’, Shape to ‘3D Ball’, and Colour to ‘Red’.
10. Click OK to save the new Preset Scatter Graph to the list and return to the Preset Scatter Graph Editor.
11. For the next step we have to have a data log loaded, so…load a data log. Now go to the Scatter Graph and witness your new graph available in the Preset Graphs list. Click on it and then click the Draw Graph button to see if it returns any data. If you loaded the example Flyin’ Miata Link data log that ships with the application then should have returned an unhealthy number of samples!
This is not really a tutorial but a quick feature explanation. Every graph within the application can be right-clicked to bring up a context menu that contains a Copy Graph to Clipboard item. Selecting this will place a copy of the graph on the Windows clipboard, which can then be pasted down into your favourite graphics app. or word processor. If you want to paste it down into Word, select Paste Special from Word’s Edit menu, and then either ‘Picture’ or ‘Device Independent Bitmap’, otherwise the graph data will be pasted instead of the graph itself. Pasting the graph data into an application like Excel might actually be quite useful.
This tutorial assumes that you have set up
the locations of the Data Logging and Data Log Conversion programs in the
application’s options, and set the COM port of the computer you’re
communicating to the Link ECU through.
If you’re not using COM1 for communications, then go and look at the General Settings
frame for details of how to tell the application which one to use.
This tutorial also assumes that you have the
computer plugged into the Link and you’re ready to drive!
1. Select the New item of the File menu to open the New File window (makes sense so far, eh?). The File Type field should have defaulted to ‘Data Log’ and the cursor will be in the File Name field. A default file name corresponding to the current date will have been supplied if the appropriate option is selected within the application’s Options window, else type in a valid file name and hit the OK button - don’t worry about the Retain Binary File check box for now.
2. If you haven’t typed in the name of an existing file, the Data Logging/Upload program will run in its own window. Start the car if you haven’t already done so and go for a nice drive. Once you feel you’ve driven for long enough, quit the Data Logging Program, at the time of writing by pressing the ‘Q’ key.
3. The Data Logging program will close and the Data Log Conversion program will run briefly, and then the data log will be loaded into the application. You can now draw graphs to you heart’s content.
4. Note that the process of acquiring a data log results in it being saved in the working directory automatically so you don’t have to save it yourself.
One of the most useful features of the application is the ability to view and amend all of the zone data from the ECU and upload your changes. In this tutorial, we’ll go through amending some ignition zones and uploading them, so what we need to get started is an up-to-date data log from your car. If you don’t have one, go through the Acquiring a New Data Log tutorial for details of how to get one.
1. Load in a recent data log that you’re happy to use as the basis of the zone settings you’re going to upload.
2. In the Sample Graph window, select the Zone Data item of the Tools menu to open the Zone Data Editor window.
3. When the Zone Data Editor opens, it begins on the General tab. This is by far the most intimidating of the Zone Data Editor’s tabs. The zones have been brought together in logical groups depending upon their function, which isn’t necessarily the order they appear in the data logs, should you have looked at these manually in the past. But we’re not interested in the zones within this tab, we’re going to go straight to the Ignition Zones tab, by clicking on it now.
4. This tab and the Fuel Zones tab are laid out in exactly the same way. The first of the grids displays the zone settings loaded in from the current data log, with the RPM zones across the top and the MAP zones down the side. This should be familiar to you, so if it isn’t you really need to make yourself familiar by reading Flyin’ Miata’s Installation and Tuning instructions in some detail.
5. The second grid is the ignition zones settings from the benchmark that is currently displayed in the Benchmark field in the top right-hand corner of the screen. If the benchmark is not currently set to ‘Lambda/Knock Zone Changes’ then change it to this. The second grid now displays the zone settings at the end of the data log with changes made by the ECU whilst auto-tuning and detecting knocks.
6. The third grid simply shows the difference between the first and second grids. This grid will be completely empty if the data log zones and the benchmark zones are identical. By only populating the cells of the grid where there is a difference between the data log and the benchmark, the differences really stand out. To aid this ‘standing out’, negative differences are shown in red and positive differences in black.
7. OK, so let’s make some changes to the zone data (the top grid). What we’ll do first off is subtract 1 degree of timing from a single grid cell. Don’t worry about resetting these changes, as we won’t be permanently storing the values in your Link ECU.
8. Choose a zone (cell) that can do with having a degree of timing subtracted from it and double click it. You should now find the cell is available to edit, with an up/down button to its right. Press the down arrow of the up/down button four times to reduce the value by four and hence remove one degree of timing (remember these values are expressed in quarter degrees). Click another cell on the grid to store the value.
9. Instead of using the mouse to adjust the values you can use the cursor keys to move the highlight around the grid, then press F2 to open the edit box with the existing value in it, or press [Return] to open the edit box with no value in it. Once you have amended the value, press [Return] to store it in the grid, or [Esc] to abandon the change.
10. Another feature is the ability to alter a range of values together. Highlight a range of cells in the top grid by clicking a cell with the left mouse button and then dragging out a highlight. Letting go of the mouse button will leave the area highlighted. Now right-click anywhere in the grid to bring up the context menu. Select the Apply Offset item to open up the Offset dialog box.
11. The idea is that you enter an amount in the field in the Offset window that will be added to your range of highlighted cells. If you enter a negative number you will in effect be subtracting from the highlighted cells. Type ‘-4’ into the field (or press the down arrow of the up/down button four times) and then activate the OK button.
12. There you go – ‘4’ should have been subtracted from the highlighted cells. The benchmark grid also allows you to highlight an area of cells and bring up a right-click context menu. In this case, the Copy to Data Log item of the context menu will copy the values in the highlighted range of cells on the second grid to their respective positions in the first grid.
13. OK, let’s look at another way of editing the ignition (and fuel) zone values. Click on the Graph button to the right of the first grid. This will open up the 3D Graph window and display a 3D graph of the ignition zones – pretty, huh? But as pretty as this graph might be it also serves a practical purpose – it instantly shows you how smooth your timing curves are, and smooth is the name of the game with the Link ECU.
14. But we can also alter the zone values using the 3D Graph. Click on a bar on the graph and notice how its top and bottom are highlighted. Notice also how the MAP Zone and RPM Zone fields also change to tell you which bar you have selected, and the Value field changes to show the value of that zone. You can now adjust the value of the highlighted bar by changing the Value field, either by typing into it directly, in which case you need to complete your change by pressing [Return], or by using the up/down button to the right of the field. If you use the up/down button you can keep the mouse pressed down whilst the field value changes, and only when you release the mouse button will the graph be updated. Make sure for this exercise that you only reduce the values of the bars.
15. Another feature of the 3D Graph is that it can be rotated using the Rotation and Elevation fields, or, once a bar of the graph has been selected, by holding down the [Ctrl] key and moving the mouse. Rotating the graph may be necessary to see all of the bars on it, as by its very nature bars in the foreground may obscure bars in the background.
16. Use the OK button to close the 3D Graph and see how the values in the first grid of the Ignition tab are updated to reflect the changes made within the 3D Graph window.
17. Now it’s time to perform an upload. To do this the computer must be plugged into the car (doh!), the ignition turned on but the engine not started. Click the Upload button at the bottom left of the Zone Data Editor window to open up the Upload Zone Settings window. If the Upload button is disabled, this is because the data log’s and application’s Chip Date and Engine Size do not match – it’s potentially dangerous to upload to a different ECU so the application disables the button. It’s beyond the scope of this tutorial to explain how to match the data log and application settings, therefore for now ensure that the contents of the FM Link ECU tab of the Options window match your car and ECU and acquire a fresh data log.
18. Assuming you can, click the Upload button. Make sure that the Permanently Store box is NOT checked, the Verbose box is NOT checked, the Verify Upload box IS checked, the Upload Changes Only box is NOT checked, and that the Set Auto Tune Mode field is set to ‘No’.
19. This collection of options will cause an upload and verify of all the zone settings without permanently storing them on the Link ECU, and without changing the tuning mode of the Link ECU. This means that when you turn the ignition off, your Link ECU will return to its previous settings. For future reference, only uncheck the Verify Upload box once you have done many uploads without verification errors, i.e. you have confirmed the consistent and correct working of your computer and serial cable, etc. The Upload Changes Only section allows you to upload just the zones you have changes rather than all of them, AS LONG AS YOU HAVE A COMPARISON FILE WHICH REFLECTS THE CURRENT LINK ECU SETTINGS. If you choose a comparison file that is actually different to the current Link ECU settings, you might not get all your changes uploaded.
20. After ensuring the check boxes in the Upload Zone Settings window are the same as that specified in step 18, click the OK button to continue.
21. Next, the Upload Confirmation window opens. We cannot over-stress the importance of taking the time to make sure the Engine Size and Chip Date fields accurately reflect the Link ECU that is installed in your car. If they do not then click the No button and go to the FM Link ECU tab of the Options window of the application and correct the discrepancies. It is imperative that you understand the potential consequence of uploading to the wrong chip version: SERIOUS DAMAGE COULD OCCUR WHEN THE ENGINE IS SUBSEQUENTLY STARTED. This is because different versions of the ECU store the same zone data in different formats. For example, early 1.6 chips store an ignition trim of ‘-3’ as the number ‘243’. Later 1.6 versions and all 1.8 versions store a trim of ‘-3’ as the number ‘8’, and if ‘243’ was uploaded into them by mistake, the ECU would attempt to implement a trim of ‘+55.75’. Not conducive to engine life, eh? You have been warned – you must LOOK at the engine size and chip date displayed in this window before proceeding with the upload.
22. So assuming the Engine Size and Chip Date fields contain the correct values, click the Yes button to continue. The Data Logging/Upload program will now run in its own window and you can watch it upload the two hundred and fifty six zones and then verify them. Once it has finished it will quit automatically and you will be returned to the Zone Data Editor.
23. There you go, then. A successful zone data change and upload. If you want to restore your ECU to its original state you have two options: the first is simply turn the ignition off on the car, assuming that you hadn’t checked Permanently Store in the Upload Zone Settings window; the second is to set the Benchmark field in the Zone Data Editor to ‘Original Zone Settings’, highlight the entire contents of the second data grid on the Ignition tab, right-click the second grid to bring up the context menu and select the Copy to Data Log item to replace all the ignition zones with their original values, and then perform another upload.
24. If you wish to permanently save your new zone data, close the Zone Data Editor using its OK button, and then choose the Save As item from the File menu of the Sample Graph window and give the file an appropriate name. This will create a MAP file of just the zone data (no data log). There isn’t any way of saving a data log file containing the original data log and your new zone settings (sorry).
This is the starting point of the
application. From here you load data
logs, acquire new data logs, save Link Zone Setting files (MAP files), access
all of the analysis and zone data editing tools, and configure the application.
Depending upon whether a data log
or a MAP file is loaded, different menu options will be enabled or
disabled. If an Flyin’ Miata Link MAP
file is loaded, you can’t access the Sample, Scatter, and Power Graphs as these
are all data log related. Only if you
load a data log from a Flyin’ Miata Link ECU that has zone setting information
in it will you be able to access the Zone Data Editor.
For Flyin’ Miata Link ECU users only, use this menu option to acquire a new data log or download the Link ECU settings from the car. Selecting this option will open the New File window.
After a new data log is captured
and then loaded, if the application’s Scatter
Graph Auto Draw box is checked, all Preset Scatter Graphs that have
their Automatically Draw After a File
is Opened box checked will be drawn in new Scatter Graph windows.
Select the type of file you would
like to acquire and give it a valid file name.
If you have the Suggest New File Names
feature enabled in the application’s options, the application will supply a
file name for you consisting of the current date and a sequence letter. Activate the OK button to begin data
logging. If you enter the name of an
existing file, you will be asked to confirm that you want to overwrite it. The following will now occur depending upon
the type of file you’re acquiring:
New Data Log:
1. Data logging program launches in its own window.
2. Once you have finished logging, you manually quit the data logging program.
3. The data log conversion program runs automatically and quits when it is finished.
4. The data log is created in the application’s working directory with the name you specified.
5. The data log is loaded into the application.
Zone Settings (MAP file):
1. Data logging program launches in its own window and quits automatically once it has acquired all of the zone settings.
2. The MAP file is created in the application’s working directory with the name you specified.
3. The MAP file is loaded into the application.
4. Note that the ECU version and date are not down loaded from the Link ECU, but are appended from the application’s defaults.
As can be seen from the steps above, the new file is created on disk before it is loaded into the application, therefore, unless you make any subsequent changes to the zone data that you want to keep, you don’t have to save the file from within the application.
This field is only enabled when acquiring a new data log. If the field is checked, the binary file that is loaded into the data log conversion program in step 3 above will also be saved in the application’s working directory with the same name as the data log, except with an extension of ‘bin’. ‘Why do I want this file?’ you may ask. Three reasons, the first: if you are short of disk space, the binary file is typically a quarter of the size of the data log, and using the Convert Binary Log File option of the Tools menu you can regenerate the data log when ever you wish to see it. So…you don’t need to keep the large data log files, you can just keep the smaller binary files, but obviously there is an inconvenience factor. The second reason to keep the binary files is that they actually contain more information that the data conversion program puts in the data logs, so if any future enhancements to the data conversion program result in more data coming out of it, you’ve still got the binary files from your existing data logs to generate new, more detailed data logs. The third reason is because there may be times when Flyin’ Miata require the extra information in the binary file whilst supporting their products and may ask if you can send it to them for analysis.
Whether this check box starts off checked or unchecked each time you open the New File window is determined by the setting in the Miscellaneous Defaults frame of the General tab of the Options window.
With the advent of data tagging the
need has now arisen to look at your laptop’s display whilst driving. Personally we have trouble finding the time
to look at our cars’ existing instrumentation let alone try and read the
display on a laptop sitting on the passenger seat! However, things can be done to make life a little easier – the
Data Logging/Data Upload program can be set to open either full screen or
sufficiently large enough to fill the Windows desktop. In Windows 95 and 98, find the LinkWIN.pif
file in the Data Logging/Data Upload program’s directory, right click it, and
select the Properties item from the menu. Here the font, or whether the application opens full screen can
be set. In Windows 2000 or XP, once the
Data Logging/Data Upload program is running, right click its title bar and
select the Properties item from the menu. Here the font or whether the application opens full screen can be
set.
Use this menu option to load in an existing Data Log file or Link ECU settings file (MAP file). Be sure to set the Files of Type field in the File Open dialog to the type of data log you want to load. This is important as the application cannot necessarily tell from a file’s extension what type of data log it is – many formats use the same file extension.
After a data log is loaded, if the
application’s Scatter Graph Auto Draw
box is checked, all Preset Scatter Graphs that have their Automatically Draw After a File is Opened
box checked will be drawn in new Scatter Graph windows.
This menu option is only enabled if you have a Flyin’ Miata Link ECU data log or MAP file loaded.
Once you’ve already saved a file
using the Save As item of the File menu, this menu option will be
enabled to allow you to re-save the file using the same file name.
This menu option is only enabled if you have a Flyin’ Miata Link ECU data log or MAP file loaded.
Use this menu option to create a
Link ECU settings file (MAP file) of the currently loaded zone data. These may have been obtained by loading a
data log or another MAP file.
This menu option will allow you to save a data log out in a spreadsheet-friendly CSV (Comma Separated Variable) text file. This file can then be loaded into a spreadsheet and its contents analysed to your heart’s content. The file will contain only the data items shown in the window’s data item list, and only the sample range specified in the window’s From and To fields. Exporting all the data items from a large data log can take some time and generates a large file!
This menu option will print the displayed graph. A standard printer selection dialog will open to allow you to choose and configure your printer.
Once you have started loading and saving files, a recently used file list is maintained within the File menu. Selecting one of these files will load it in, if it still exists!
After a data log is loaded, if the
application’s Scatter Graph Auto Draw
box is checked, all Preset Scatter Graphs that have their Automatically Draw After a File is Opened
box checked will be drawn in new Scatter Graph windows.
When the application is first ran, this menu option will reflect the permanent setting of the Scatter Graph Auto Draw check box in the Options window. However, changes made to the menu option will not be reflected in the Options window setting. In other words, this allows you to temporarily override the Options window setting for the loading or acquiring of an individual data log.
Use this item to exit the
application!
Use this item to copy the displayed graph to the clipboard so that it can be pasted down into other applications. Once within the other application, you may have the choice of pasting down the chart or the data that the chart is displaying in several formats. This will be revealed in the other application’s ‘Paste Special’ menu.
Use this menu option to update the highlighted Preset Sample Graph with the current checked data items and Fix Graph Max settings – handy for tweaking the data items of the preset graphs.
Use this menu to create a new
Preset Sample Graph based on the currently checked data items and Fix Graph
Max settings. You’ll be prompted
for a name for the new preset graph.
The new graph will be given the Licence Type of the data log that is
currently loaded.
Once a graph has been drawn, this
menu can be used to navigate around it.
Various entries within the menu will be disabled when they are not
applicable (e.g. the Start item will be disabled when the start of the graph is
already displayed).
The Zoom In and Zoom Out items will show sub menus from which the degree of zoom can be selected. When performing a zoom operation it is always centred around the highlighted point on the sample graph.
Once a second and subsequent graph is drawn, this menu item will be enabled. Selecting this item will return the graph to its previous plot range. However, this isn’t like a multi-level undo – it works as a toggle switching between the last two graphs displayed.
Select this to open the Goto Sample window. From here, you can draw a Sample Graph with a specified sample at its centre. This is the easiest way of going straight to a known sample.
Select this to create a temporary data tag based on the current entries in the Plot From and Plot To fields. This is useful as it allows you to return to an area of the data log quickly by double clicking the data tag in the Data Tags window.
This item opens the Data Tags Window to display a list of the tagged regions of the currently loaded data log. See the Data Tags Window explanation for more information about data tagging.
This menu item will only be enabled if a Flyin’ Miata Link ECU data log is loaded. It toggles on and off the Zone Influence section of the Graph Contents frame.
Use this window to go straight to a known sample within the data log and draw a Sample Graph with it at the centre. You can enter either a known sample number or the approximate time within the data log that it occurred.
Enter a sample number here directly.
Enter the approximate time of the sample in seconds. The application will find the nearest sample to the time entered.
If this box is checked, the resulting Sample Graph will cover a range of samples as specified in the Show Point Sample Graph Width parameter. If unchecked, the resulting Sample Graph will retain the same range of samples as the last graph drawn.
This menu option is only enabled if you have a Flyin’ Miata Link ECU data log or MAP file loaded.
This item launches the Zone Data Editor. Here all of the Link ECU settings can viewed, amended, and
uploaded. This menu option will be
disabled if no zone data is present.
This could be as a result of not having loaded or acquired any data yet,
or the file loaded/acquired not having any zone data within it.
This menu item launches a new Scatter Graph.
Note that you can have many Scatter Graphs open at once. The Scatter Graph will inherit the plot
range of the Sample Graph if the Scatter Graph
Auto Filter option is selected.
This menu item will be disabled if a data log is not present.
This menu item launches a new Power Graph. Note that you can have many Power Graphs open at once. The Power Graph will inherit the plot range of the Sample Graph, though this may be changed. Life is made considerably easier if the Sample Graph is displaying the relevant data for the Power Graph before this menu option is selected. This menu item will be disabled if a data log is not present.
This menu item will be disabled if a data log is not present.
This menu item will ask the computer to display the data log in the application that is associated to the data log’s file extension, e.g. files with a “txt” extension may display in Notepad.exe, files with a “csv” extension may display in Microsoft Excel, etc. The application that your computer opens to display your data log can be set within Windows Explorer by selecting Tools->Folder Options and navigating to the File Types tab. If your computer’s default text editor is NOTEPAD.EXE, you’re using Windows 95 or Windows 98, and you’re likely to use this menu item a lot, I’d highly recommend changing the default text editor to something else, e.g. WORDPAD.EXE, as you’ll soon get fed up with Notepad saying the file’s too large would you like to use Wordpad instead…
This menu option is only applicable to Flyin’ Miata Link ECU users.
This menu item will launch the Binary Log File Converter, where the binary log files generated by the data logging program can be converted to data logs and loaded into the application. If when acquiring a new data log, the Retain Binary File check box in the New File window is checked, the binary file that is generated by the data logging program and loaded into the data log conversion program to generate a data log, will also be saved in the application’s working directory with the same name as the data log, except with an extension of ‘bin’.
‘Why do I want this file?’ you may
ask. Three reasons, the first: if you
are short of disk space, the binary file is typically a quarter of the size of
the data log, and using this menu item you can regenerate the data log when
ever you wish to see it. So…you don’t
need to keep the large data log files, you can just keep the smaller binary
files, but obviously there is an inconvenience factor. The second reason to keep the binary files
is that they actually contain more information that the data conversion program
puts in the data logs, so if any future enhancements to the data conversion
program result in more data coming out of it, you’ve still got the binary files
from your existing data logs to generate new, more detailed data logs. The third reason is that there may be times
when Flyin’ Miata require the extra information in the binary file whilst
supporting their products and may ask if you can send it to them for analysis.
This menu item opens the
application’s options window. Here the set up of the application is
configured.
This menu item opens the Preset Sample Graph Editor. Here you can set up your own or amend the
existing preset sample graphs for use in the application’s main window.
This menu item opens the Preset Scatter Graph Editor. Here you can set up your own or amend the
existing preset scatter graphs.
This
menu item opens the Car
Definition Editor.
Here you can set up your own or amend the existing car definitions.
This menu launches the Zone Data Benchmark Editor. Here you can set up your own Link ECU
setting benchmarks for comparison against your Data logs within the Zone Data
editor.
This menu item will launch your
computer’s default web browser to display the application’s on-line help.
This window displays the application’s summary, showing licence and trial information, etc. The most important piece of information that it displays is the Installation Unique ID. This is required to obtain a software key that works with this installation of the software.
The Universal Data Log Definition
Details section shows information about the currently loaded data log
definition file, determined within the File
Locations and Power Graph tab of the Options window.
Within
this frame are the controls that determine the contents of the graph and
display detailed information about any point highlighted upon it.
Together these determine the range
of samples the graph will cover. The
values entered within these fields must be within the range of samples loaded,
which is displayed in the right hand end of the status bar at the base of the
window. A range greater than 1,000
cannot be entered without checking the Quick check box. This is because the graph cannot handle
displaying more than this number of points horizontally. If you leave either field blank, the
application will fill it in with the relevant end of the loaded sample range.
Once
you have determined your graph’s contents, activate this button to actually
draw the graph. It’s the default button
for the Sample Graph window, so just hitting the return key whilst the
window is active will re-draw the graph as well.
Checking this option will significantly speed up the display of graphs of more than 500 samples in range by thinning out the data. The number of samples that are ‘thinned out’ is determined to ensure that 500 points are plotted horizontally. This means that if you display a plot range from 1 to 30,000, the graph will only contain 1 in 60 samples. This is the trade-off for displaying the graph quickly, and hence it can be deduced that its use is only to quickly navigate around the graph or obtain an overview, as it’s quite possible for transient information to get lost, with the exception of the knock sensor output where any peaks will always be displayed.
Normally the vertical scale of the
graph is determined by the application each time a graph is drawn to best suit
the data displayed. This results in it
changing as you page and scroll left and right through the data log, which some
folks find disconcerting. If you check
the box, you can then enter a fixed maximum value for the vertical scale that
will not change, no matter what data is displayed on the graph. The value you enter here may be adjusted by
the application so that it can make a sensible vertical scale with a useful
number of divisions. If data is graphed
that is higher in value than the number specified as the vertical scale
maximum, it will not be seen.
This button will zoom in the view of the
graph by the amount specified by the X field to the right, centred on
the highlighted data point of the graph.
This button will be disabled if a graph is not currently displayed.
This button will zoom out the view of the
graph by the amount specified by the X field to the right, centred on
the highlighted data point of the graph.
This button will be disabled if a graph is not currently displayed, or
the plot range of the graph matches the load range of the data log.
This button will zoom out to show all the
loaded samples. This button will be
disabled if a graph is not currently displayed, or the plot range of the graph
matches the load range of the data log.
This combo is used to set the amount of zoom
the Zoom In and Zoom Out buttons are to apply.
The Preset Graphs are simply predefined sets of checked Data Items in the Sample Details list and Fix Graph Max settings. The application ships with a few examples, but you can create your own using the Preset Sample Graph Editor. Upon selecting a Preset Graph, the settings of the Data Item check boxes of the Sample Details List will change.
Only the Preset Graphs that have the same
Licence Type as the loaded data log are displayed, so for instance, if you load
a FM Link data log you’ll see a different set of Preset Graphs than if you load
an Electromotive Tec-3 data log.
This list displays all of the data items that are relevant to the type of data log that is currently loaded. Its first use is to select the different types of data that will be displayed on the Sample Graph. This is done by checking the box to the left of each Data Item name. After the selections are changed, the graph must be re-drawn for the changes to take effect
The second use of this list is to display the details of the data log at the point in time of the currently highlighted data point on the graph. If a graph is not displayed the Value column will contain no information.
Once a Sample Graph has been drawn, clicking on a data item that is displayed on the graph will result in the graph’s data point changing to that series.
For a detailed description of what each Data Item displays see the section Data Item Explanation.
The set of Data Items that are displayed in
the list can be restricted to only those of interest to the User. This is done using the Data Item Definitions
tab of the Options window.
Checking this box will reduce the contents of the Sample Details list to only those data items that are checked, typically the contents of the Sample Graph you are drawing. This is a handy way of temporarily hiding the data items you are not currently interested in to make it easier to see those that you are. Un-checking the box will restore the hidden data items.
This frame is only displayed if you have a Flyin’ Miata Link ECU data log loaded, and the Zone Influence item of the View menu is checked.
The Zone Influence indicator represents the
instantaneous amount of interpolation that the Link ECU is performing between
fuel and ignition zones at the highlighted point on the Sample Graph (if “Interpolation…fuel and ignition zones”
doesn’t mean very much then have a look at Flyin’ Miata’s instruction manual
for the Link). At each corner of the
square is an ignition/fuel zone number.
The closer the cross hair is to a zone number the more influence that
zone is having on the fuel and timing the ECU is supplying.
The graph displays the data you select over the sample range you select, with time in seconds forming the X Axis and a generic number scale forming the Y Axis. Once a graph has been drawn, you can zoom in and out of it, scroll left and right, and move straight to the beginning and end (assuming you’re only displaying a portion of the total data loaded). All of this can be achieved in a variety of ways: below the graph is a scroll bar that can be clicked and dragged, to the left of the graph are the zoom controls and above the graph is the zoom menu of the main window. In addition to these, you can right click the graph to bring up a context menu that repeats these actions and performs a few of its own.
The buttons to the bottom left can be used to move the highlighted data point on the graph one sample at a time in either direction. Note that if the graph is a Quick Graph, i.e. displays thinned out data, the highlighted data point may jump more than one sample at a time.
Clicking on a point on the graph
will result in the details of the data log at that point in time being
displayed in the sample details list.
The data item corresponding to the graph series clicked on will also be
highlighted in the sample details list.
Performs the same action as the Copy
item of the Edit menu.
This menu option will print the displayed graph. A standard printer selection dialog will open to allow you to choose and configure your printer.
This will insert the sample number
of the currently highlighted data point on the graph into the Plot From
field without re-drawing the graph.
This will insert the sample number
of the currently highlighted data point on the graph into the Plot From
field and then re-draw the graph.
This will insert the sample number
of the currently highlighted data point on the graph into the Plot To
field without re-drawing the graph.
This will insert the sample number
of the currently highlighted data point on the graph into the Plot To
field and then re-draw the graph.
This performs the same action as
activating the Draw button.
Once a second and subsequent graph
is drawn, this menu item will be enabled.
Selecting this item will return the graph to its previous plot
range. However, this isn’t like a
multi-level undo – it works as a toggle switching between the last two graphs
displayed.
Select this to open the Goto Sample window. From here, you can draw a Sample Graph with a specified sample at its centre. This is the easiest way of going straight to a known sample.
Select this to create a temporary data tag based on the current entries in the Plot From and Plot To fields. This useful as it allows you to return to an area of the data log quickly by double clicking the data tag in the Data Tags window.
This performs a combined action of
setting the amount to zoom in and then zooming in, centred on the highlighted
data point of the graph.
This performs a combined action of
setting the amount to zoom out and then zooming out, centred on the highlighted
data point of the graph.
This performs the same action as
activating the Zoom Out Full button.
As if all the above methods of navigation were not enough, the graph also has the following keyboard shortcuts:
|
Key Combination |
Action |
|
<Ctrl><è> |
Page Right. The key press auto-repeats. |
|
<Ctrl><ç> |
Page Left. The key press auto-repeats. |
|
<Alt><è> |
Scroll Right. The key press auto-repeats. |
|
<Alt><ç> |
Scroll Left. The key press auto-repeats. |
|
<Shift><è> |
Move highlighted data point to the right. This will cause a graph scroll as you reach the right hand edge of the graph. The key press auto-repeats. |
|
<Shift><ç> |
Move highlighted data point to the left. This will cause a graph scroll as you reach the left hand edge of the graph. The key press auto-repeats. |
|
<Shift><é> |
Move highlighted data point to the next highest graph series. Once the highest is reached, the highlight will move to the lowest. |
|
<Shift><ê> |
Move highlighted data point to the next lowest graph series. Once the lowest is reached, the highlight will move to the highest. |
|
<Ctrl><Home> |
Move to the start of the graph |
|
<Ctrl><End> |
Move to the end of the graph |
|
<Ctrl><I> |
Zoom In by amount in X field. |
|
<Ctrl><O> |
Zoom Out by amount in X field. |
|
<Ctrl><F> |
Zoom Out Full |
|
<Ctrl><P> |
Draw previous graph range |
|
<Ctrl><G> |
Open Goto Sample window |
|
<Ctrl><N> |
Create a new Data Tag |
This window lists all of the tagged areas of the loaded data log (data tagging is done whilst acquiring a data log to mark areas of interest – Flyin’ Miata Link ECU users only), and any temporary tags created after the data log is loaded.
If you have checked the Auto Open Data Tag Window box in the General Settings frame of the FM Link ECU tab of the Options window, then this window will be displayed whenever a data log is loaded that contains data tags. Alternatively, select the Data Tags item of the View menu to open the window.
To view one of the tagged areas on the Sample Graph, highlight the tag and click the Show button. Alternatively, double click the tag or hit [Enter] on the keyboard.
To create a temporary data tag at any time whilst a Sample Graph is drawn, select New Data Tag from the Sample Graph’s View menu or right-click menu, or press the New button in the Data Tags window. A data tag will be created using the current contents of the Sample Graph’s Plot From and Plot To fields.
To delete a data tag, highlight it and press the Delete button. Note that if you delete a data tag that was loaded from a data log (Flyin’ Miata Link Users), you only delete it from the list here – the data log remains unaltered.
“What on Earth is a data tag?” you might ask. A data tag is simply an area of interest of the data log. By recording it as a data tag, you can simply double-click it in this window to cause the Sample Graph to plot that area.
This window is only applicable to
owners of Flyin’ Miata Link ECUs. It
allows the viewing, alteration, and upload of all of the Link ECU
settings. The screen is divided into
four tabs. The second tab displays the
fuel zones, the third tab displays the ignition zones, the fourth tab displays
any notes that have been recorded against the collection of zone settings,
whilst the first tab displays everything else.
This tab organises the zone
settings into logical framed groups, applying various restrictions to the
values that can be entered in each.
Each numeric field has an ‘up down’ control to its right which allows
alteration of the field’s value by using the mouse. Note that the following instructions will not attempt to explain
the purpose of the individual zone settings – that’s best left to Flyin’
Miata’s Link Tuning Manual. The grids that the Boost Targets,
Acceleration Pump, and Auto Tuning Targets are entered into are designed to
work in a spreadsheet-like manner. The
cursor keys can be used to move between the cells, typing directly into the
cell will overwrite the existing entry, and pressing F2, [Return], or
double-clicking will allow editing of the existing entry.
|
Field |
Values and Description |
|
Choke Scale |
0 to 255 |
|
Choke Decay |
0 to 255 |
|
Cold Fuel |
0 to 255 |
|
Hot Restart |
-70 to +185 |
|
Prime Factor |
0 to 255 |
|
Prime Delay |
For 1.8 only, chips dated after 24th Jan 2003, 0 to 255 |
This frame is only enabled if the
loaded data log or MAP file is for a normally aspirated engine.
|
Field |
Values and Description |
|
Sensitivity |
Wastegate sensitivity, 0 to 255 |
|
Base Pres. (kPa) |
The boost level the mechanical wastegate actuator is set to, 15 to 100. Note that this is subtly different to the WG BASE screen on the Link keypad where you enter a combination of atmospheric pressure and the mechanical wastegate actuator. Here you enter just the mechanical wastegate actuator, e.g. if your car has an 8PSI wastegate actuator you enter 55kPa. |
|
RPM |
Wastegate RPM, 2000 to 7200 in increments of 100 |
|
TPS Target Control |
1.8 only, enables TPS boost target control. |
|
WOT Target Control |
1.6 only, enables WOT boost target control. |
|
IAT Target Control |
Only for ‘96/’97 1.8 ECU with chips dated on or after 10th February 2005. Checking the box enables intake air temperature boost target control. |
|
MAP Limit (KPa) |
0 to 255, 255 = OFF |
|
Rise Rate Weight |
Used to calculate the point before target MAP that the ECU comes out of spoolup assist, 0 to 255 (only enabled for chips dated on or after 10th February 2002) |
|
Closed Lp –ve |
Closed loop negative gain, 0 to 40 (only enabled for chips dated on or after 6th December 2000) |
|
Closed Lp +ve |
Closed loop positive gain, 0 to 40 (only enabled for chips dated on or after 6th December 2000) |
|
Boost Hysteresis |
The amount that the boost error (plus rise rate) is allowed to bounce around without triggering a 1/2 WG pulse, 0 to 255 (only enabled for chips dated on or after 10th February 2002) |
|
Overshoot Supp. |
Spool-up Overshoot Suppression, 0 to 255 (only enabled for chips dated on or after 11th March 2001) |
|
Droop Supp. |
Spool-up Droop Suppression, 0 to 255 (only enabled for chips dated on or after 11th March 2001) |
|
Acceleration/deceleration map hysteresis, 0 to 255 |
This
frame is only enabled if the loaded data log or MAP file is for a normally
aspirated engine.
|
Field |
Values and Description |
|
Boost Targets/ Wastegate % |
This allows specification of whether the following targets are expressed in terms of boost or wastegate actuator solenoid duty cycles. |
|
Boost Targets Grid |
A target can be entered for each 500 RPM increment from 2500 through to 7500. If the targets are being expressed in terms of boost, values can be entered between 100 and 255. If the targets are being expressed in terms of wastegate actuator solenoid duty cycles, values can be entered between 0 and 100. If a value is entered into the first grid position you will be asked whether you would like it copied to the rest. |
1. Highlight an area of the grid.
2. Right-click the grid to open the context menu and select the Apply Offset item.
3. Enter a value to be added or subtracted from the cells in the highlighted area and press the OK button.
4. The offset has been applied to the highlighted cells.
This
entire frame will be disabled on all chips dated before 1st March
2001. All chips produced after this
date require an intake air temperature sensor to be fitted.
|
Field |
Values and Description |
|
|
Fuel Low Slope |
Fuel correction slope from 0 Celsius down to –30 Celsius, units of 1/128, range 0 to 255. This field is only displayed for chips dated before 15th Feb 2003. |
|
|
L3 Low MAP |
MAP below which L3 correction won’t occur. This field is only displayed for chips dated after 15th Feb 2003 |
|
|
Fuel High Slope |
Fuel correction slope from 25 Celsius up to intake air temperature limit, 1/128, range 0 to 255. This field is only displayed for chips dated before 15th Feb 2003. |
|
|
Intake Comp. |
Intake air temperature compensation. This field is only displayed for chips dated after 15th Feb 2003 |
|
|
Ignition Start (‘C) |
Ignition timing retard start temp, Celsius, range 25 to 150 |
|
|
Ignition Slope |
Ignition timing retard slope, units of 1/256 degrees of Ignition/degrees Celsius, range 0 to 255 |
|
|
25 to 80. This field is only displayed for chips dated on or after 1st March 2001. |
||
|
Advance Limit |
0 to 50. This field is only displayed for chips dated before the 6th December 2000. |
|
|
Field |
Values and Description |
|
Target RPM |
500 to 2500 in increments of 50 |
|
Hot IAC/Run IAC |
16 to 85 |
|
Cold IAC/Start IAC |
16 to 85 |
|
A/C Idle % |
0 to 25 |
|
IAC Rate |
0 to 255. This field is only displayed for chips dated on or after 18th September 2001 |
|
TPS Idle Sw. |
Checkbox. For ‘96/’97 1.8 ECU with chips dated on or after 18th April 2003, or for standard 1.8 ECU with chips dated on or after 27th June 2004. |
|
Idle Stabilisation |
Checkbox. For ‘96/’97 1.8 ECU with chips dated on or after 1st May 2003. |
|
1.8 TPS |
Checkbox. For 1.6 Mk 1 ECUs dated on or after 1st January 2003. |
|
Field |
Values and Description |
||||||||||||||||||||||||||||||||||||||||
|
Type |
This field enables the selection of the auto tuning type: “Off”, “Lambda”, “L3”, or “L3+L4”. The available options will change depending upon the combination of engine size, ECU version, and chip date. The field will always contain “Off” and “Lambda”, but additional entries are shown according to the tables below: For 1.6 Mk1 ECUs:
For 1.6 Mk2 and standard 1.8 ECUs:
For ‘96/’97 1.8 ECUs:
|
||||||||||||||||||||||||||||||||||||||||
|
Master Fuel |
For chips dated before 10th June 2002. Allow Lambda tuning to alter Master Fuel value if necessary |
||||||||||||||||||||||||||||||||||||||||
|
O2 Sensor |
For chips dated after 9th June 2002. This combo allows selection of auto tuning by stock narrow-band O2 sensor, and/or an after-market wide-band sensor connected in place of the EGR system. Additionally, for ‘96/’97 1.8 ECUs dated on or after 8th May 2004, an option of “NB+WB” is present if the Type field is set to “L3” or “L3+L4”. This setting uses the stock narrow-band sensor for auto-tuning when the MAP is less than 64 kPa (O2 target obtained from the Idle cell of the O2 Targets Frame), and the after-marker wide-band sensor when the MAP is greater than 64 kPa (O2 target obtained from the remaining cells of the O2 Target Frame). The narrow-band sensor is more accurate and reacts quicker than the wide-band under these low-load circumstances. This field can only be set to wide-band when the EGR Recirc. Field in the Miscellaneous Frame is unchecked. This field will be disabled if the Type field is set to “Off”. |
||||||||||||||||||||||||||||||||||||||||
|
Targets Grid |
0 to 127. The values entered into the Val row of this grid change depending upon the setting of the O2 Sensor Type field: NB Linearised NB sensor output values as seen in the O2 data item. WB Auxiliary input voltage NB+WB Idle cell as “NB”, remaining cells as “WB”. When an auxiliary input voltage needs to be specified, the figure entered is calculated according to the following formula: grid value = 128 – (voltage * 25.6) The Conv row shows the values entered into the Val row with the conversion files specified in the Aux Input Conversion File and Narrow Band Oxygen Sensor Conversion File fields of the Options Window applied to them, depending upon whether the target is a NB O2 Sensor value or an Auxiliary Input Voltage. |
|
Field |
Values and Description |
|
Trim (deg) |
-5 to +5 in 0.25 increments (degrees before top dead centre) |
|
Knock Light |
For MK1 1.6 ECUs with chips dated on or after 27th June 2004 and ‘96/’97 1.8 ECUs with chips dated on or after 30th Aug 2003. When this field is checked, if the ECU detects knock during driving the CEL light on the dashboard will light up. |
|
Knock Thr. |
0 to 255, 255 = OFF |
|
Field |
Values and Description |
|
Master Fuel |
0 to 255 |
|
Quad Injector Driver Mode |
1.6 only. Indicates the use of four-injector driver mode. This field is only enabled for chips dated on or after 11th March 2001. |
|
Injector Offset |
For ‘96/’97 1.8 ECUs only, and chips dated after 1st June 2003, -128 to 127 |
|
Offset Slope |
For ‘96/’97 1.8 ECUs only, 0 to 255 |
|
Overrun MAP |
15 to 85 |
|
Decel Fuel Scale |
0 to 255 (only enabled for chips dated on or after 19th December 2001) |
|
Acceleration Pump Grid |
0 to 255 |
|
Field |
Values and Description |
|
Def Atmos. (KPa) |
Default atmospheric pressure, 75 to 100 |
|
Fan Temp (‘C) |
70 to 110, 1.8 cars only |
|
Coolant Limit (‘C) |
0 to 140 |
|
Acceleration/deceleration map hysteresis, 0 to 255 |
|
|
Debug Data |
For ‘96/’97 1.8 ECU only, 0 to 255 |
|
TPS Offset |
1.8 only, -128 to 127 |
|
TPS Scale |
1.8 only, 0 to 255 |
|
Rev Limit (RPM) |
5000 to 9000 in 100 RPM increments |
|
VICS Act. RPM |
For ‘96/’97 1.8 ECUs only. When using the narrow band heater circuit to drive other equipment (e.g. to activate a VICS system), this is the RPM after which the voltage on the circuit will be set to zero. |
|
Volt. Correction |
For chips dated before 25st Jan 2003, 0 to 255 |
|
Speedo. Calib. |
For chips dated after 24st Jan 2003, 0 to 255 |
|
EGR Enabled |
1.8 only. Turns exhaust gas recirculation on and off. Enabling this field will disable the Wide Band O2 field in the Auto Tuning frame. |
|
MAP/Knock Cntrl |
1.6 only. Indicates the presence of a MAP and Knock sensor |
|
Alt EGR Curve |
For ‘96/’97 ECUs dated on or after 2nd July 2004, if the EGR Enabled checkbox is checked, this field can be checked to force the ECU to use a slightly different EGR schedule. |
|
Security Enabled |
For chips dated after 1st Mar 2001, checking this field will turn the security feature on that will require the keypad or serial link box to be connected before the ECU will work. |
This frame contains additional non-zone data
information.
|
Field |
Values and Description |
|
MAP ID |
This is the original reload that the zone settings are based on |
|
Engine Size |
1.6 or 1.8. Changing the value of this field will change the following screen prompts: 1.6: WOT Control MAP/Knock Sensor Exhaust Gas Recirc Fan On Temp disabled TPS Offset and Scale disabled Quad Injector Mode enabled (if chip date on or after 11th March 2001) 1.8 TPS 1.8: TPS Control Exhaust Gas Recirculation Fan On Temp enabled TPS Offset and Scale enabled Quad injector mode disabled Idle Stabilisation |
|
Chip Date |
The following functionality is enabled as this field is changed: On or after 20th June 2000: L3 Mode enabled On or after 6th Dec 2000: Closed Loop –ve and +ve enabled Advance Limit disabled On or after 1st Mar 2001: Air Temp. Correction Frame enabled Intake Limit enabled Hot IAC becomes Run IAC Cold IAC becomes Start IAC Security Enabled enabled On or after 11 Mar 2001 Overshoot Supp. enabled Droop Supp. enabled Quad Injector Mode enabled (if engine size is 1.6) On or after 18 Sep 2001 IAC Rate enabled On or after 19th Dec 2001 Decel Fuel Scale enabled On or after 10th Feb 2002 Boost Hysteresis enabled Rise Rate Weight enabled On or after 10th June 2002 Wide Band O2 auto tuning enabled Master Fuel auto tuning disabled On or after 25th Jan 2003 Speedo. Calib. enabled Volt. Correction disabled Prime Delay enabled On or after 15th Feb 2003 Fuel Low Slope disabled Fuel High Slope disabled L3 Low MAP enabled Intake Comp. Enabled On or after 18th April 2003 For ‘96/’96 1.8 ECUs, TPS Idle Sw. enabled
On or after 1st May 2003 Idle Stabilisation enabled. On or after 1st June 2003 15V Offset enabled On or after 20th June 2003 For Mk1 1.6 ECUs, Knock Light is enabled On or after 30th August 2004 For ‘96/’97 ECUs, Knock Light is enabled On or after 19th April 2004 Activatn RPM enabled On or after 16th May 2004 O2 Sensor can be set to “NB+WB” On or after 27th June 2004 For standard 1.8 ECUs, TPS Idle Sw. enabled. On or after 2nd July 2004 For ‘96/’97 1.8 ECUs, Alt EGR Curve enabled. On or after 10th February
2005 For ‘96/’97 1.8 ECUs, IAT Target Control enabled. |
|
Atmos. Pres. |
This is the atmospheric pressure loaded in with the Data log or MAP file. |
The Engine Size and Chip Date fields have a use when trying to perform an upload of data from a file with a different chip date and engine size to the ECU in your car, as defined in the FM Link ECU tab of the Options window. Under these circumstances the Upload button will be disabled. There is good reason for this: as new versions of the chips have been released, features have been added and removed. Problems could occur if individual zones are not uploaded because there are no values in the loaded file for them, but the ECU requires them for successful operation.
All is not lost, however, as all you need to do is change the Engine Size and Chip Date fields to match the ECU in your car, though I would advise against trying to convert settings from a 1.6 car to a 1.8 car and vice versa. As you change these fields, you may see certain zones enable and disable according to the new engine size and chip date – these in particular must be checked for valid entries before commencing an upload.
This
tab is divided into three frames. The
first contains the currently loaded settings, the second contains the settings from
the benchmark shown at the top of the window, and the third shows the
difference between the two. For data
logs and MAP files of forced induction engines, the zones 600 and 605 are
coloured black and inaccessible. As
well as the data in the ‘This Data log’ grid being editable in the same way as
the grids in the first tab, each grid also has a context menu accessible with
the right mouse button:
1.
Highlight an area of the This Data log grid.
2.
Right-click the grid to open the context menu and
select the Apply Offset item.
3.
Enter a value to be added or subtracted from the cells
in the highlighted area and press the OK button.
4.
The offset has been applied to the highlighted cells.
To the right of each grid is a button
labelled Graph. Pressing this
button will open the 3D Graph window and show the contents of the associated
grid as a 3D bar chart. If the
associated grid is editable then the contents of the graph will also be
editable. See the description of the 3D
Graph window for more details.
This tab is divided into three frames. The first contains the currently loaded
settings, the second contains the settings from the benchmark shown at the top
of the window, and the third shows the difference between the two. For data logs and MAP files of forced
induction engines, the zones 600 and 605 are coloured black and inaccessible. As well as the data in the ‘This Data log’
grid being editable in the same way as the grids in the first tab, each grid
also has a context menu accessible with the right mouse button:
To the right of each grid is a button
labelled Graph. Pressing this
button will open the 3D Graph window and show the contents of the associated
grid as a 3D bar chart. If the
associated grid is editable then the contents of the graph will also be
editable. See the description of the 3D
Graph window for more details.
The
Notes tab allows some descriptive information to be recorded against the
zone settings. This is no word
processor – there’s no fonts and paragraph settings, etc. There are tabs however – you just have to
use [Ctrl][Tab] to insert them, as [Tab] on its own will move the focus on to
the next item. Any notes entered here
will be saved if you save the zone values, using the Save As item of the
File menu of the Sample Graph.
Use this to select which benchmark zone
settings are compared against in the Fuel and Ignition tabs. If a Data log has been loaded, the list of
benchmarks will include ‘Lambda/Knock Zone Changes’, which will show all the
zone alterations made by the ECU during the Data log, and ‘Original Zone
Settings’, which will show the zone settings originally loaded from the Data
log.
Pressing this button will open up a second
Zone Data Editor to view all of the details of the selected benchmark. This Zone Data Editor will not allow
alteration of any of the fields. The
zone data of each of the benchmarks can be amended using the Benchmark Editor.
This button will open up the Copy Benchmark window.
This is used to copy groups of zone values from the benchmark. Click the Everything checkbox to highlight all the other check boxes, otherwise click the individual checkboxes to determine what areas of data to copy. The Air Temp Correction check box will be disabled if the chip date from the loaded file or the benchmark is before 1st Mar 2001. The Wastegate and Boost Targets checkboxes will be disabled if the benchmark is from a normally aspirated data log. Finally, click OK to copy the selected zones.
Don’t be disappointed if copying anything other than ‘Fuel Zones’ and ‘Ignition Zones’ from the ‘Lambda/Knock Zone Changes’ and ‘Original Zone Settings’ has no effect…think about it, and then contact support if you’re not sure!
This window is particularly useful if you want to copy settings from one file to another. This can be achieved in the following simple steps:
1. Temporarily add a zone data benchmark of the file which is the source of the copying
2. Load the file which is the target of the copy
3. Open the Zone Data Editor and set the Benchmark field to the new temporary benchmark created in step 1
4. Use the Copy button to open up the Copy Benchmark window, select the areas of zone data you want to copy, and then click OK.
5. Delete the temporary zone data benchmark if you don’t want to keep it.
This button is used to upload the zone data to the Link ECU. Obviously, the computer needs to be connected to the car at this point! Upon pressing the button the Upload Zone Settings window will open.
This button is only enabled if the chip date and engine size from the file being viewed in the Zone Data Editor match the chip date and engine size of the ECU in your car, as defined in the Link ECU tab of the Options window. There is good reason for this: as new versions of the chips have been released features have been added and removed. Problems could occur if individual zones are not uploaded because there are no values in the loaded file for them, but the ECU requires them for successful operation.
All is not lost, however, as all you need to
do is change the Engine Size and Chip Date fields in the Zone
Data Editor to match the ECU in your car, though I would advise against
trying to convert settings from a 1.6 car to a 1.8 car and vice versa. As you change these fields you may see
certain zones enable and disable according to the engine size and chip date –
these in particular must be checked for valid entries before commencing an
upload.
Check this box if you want the changes to be
permanently stored in the Link. If this
isn’t checked, once the car’s ignition has been turned off the newly uploaded
changes will be lost.
Check this box if you want the upload to be
verified. This has the advantage of
ensured what you want uploading actually gets uploaded, but at the expense of
the time it takes. Only un-check this box once you have gained the confidence of
many uploads without verification error.
Check this box to see more detailed
information in the Data logging/Upload program window as the zone settings are
uploaded. This will slow down the
upload and verification procedures.
This one can be a real time saver. If this box is checked, rather than perform
a complete upload, the application will only upload the zones that have been
changed. To work out which zones have
been changed a Change Comparison File is specified, which is simply the Data
log or MAP file that contains the zone settings that are currently in the
ECU. Bear in
mind that any discrepancy between the contents of this file and the current
contents of the ECU may result in some of your changes not getting uploaded.
These fields are only enabled if the Upload Changed Only check box is checked. You can type the full path and name of a file into the field directly, select one of the application’s recently used files from the list box, or press the Browse button to find and select the file. The engine size and chip date of the comparison file must match the application defaults, which presumably are set to those of your car. Double-clicking a file in the list will select it and move on to the Upload Confirmation Window
This drop down allows you to set the tuning mode the ECU will be left in after the upload. Note that this change will only be in effect until the ignition is turned off. The Options are:
No (leave the auto tuning as it is)
Coarse No Idle
Fine No Idle
Fine With Idle
Once
you have set your upload options, click the OK button to move to the Upload
Confirmation window.
This
window contains a very important warning which you must confirm acceptance of
before the application will start the upload.
The application displays the Link ECU engine size and chip date it is
expecting to be uploading to. It is imperative
that you understand the potential consequence of uploading to the wrong chip
version: SERIOUS DAMAGE COULD OCCUR WHEN THE ENGINE
IS SUBSEQUENTLY STARTED.
This is because different versions of the ECU store the same zone data
in different formats. For example,
early 1.6 chips store an ignition trim of ‘-3’ as the number ‘243’. Later 1.6 versions and all 1.8 versions
store a trim of ‘-3’ as the number ‘8’, and if ‘243’ was uploaded into them by
mistake, the ECU would attempt to implement a trim of ‘+55.75’. Not conducive to engine life, eh? You have been warned – you must LOOK at the engine size and chip date displayed in
this window before proceeding with the upload.
After you have responded to the dialog, the application will run the Data logging/Upload program in a separate window and begin to upload and optionally verify the zone data. Once complete, the Data logging/Upload program will close and you will be returned to the Zone Data Editor, reporting any errors it encountered.
In case you’re interested, the command that
Data Log Lab issued to the Data logging/Upload program is stored in a file
named UploadCommand.txt in the Data logging/Upload program directory.
This button is used to change the application’s default Link ECU type and chip date to those in the current data log. Pressing the button will show a confirmation prompt. Responding “Yes” to the confirmation prompt will replace the settings, as if the Options Window had been opened and the fields manually set.
The
power of the 3D graph is its ability to instantly portray a meaningful image of
all of the fuel or ignition zones. To
give the best ‘perspective’ on the data the graph can be freely rotated in
three dimensions using the fields within the Orientation frame or by
selecting the chart and dragging it using the mouse.
Right
clicking the graph will bring up a context menu allowing the graph to be copied
to the clipboard or printed.
Use
this field to set the number of degrees of rotation of the chart. The up/down buttons to the right of the
field will increment/decrement the field by ten degrees.
Use
this field to set the number of degrees of elevation of the chart. The up/down buttons to the right of the
field will increment/decrement the field by ten degrees.
Activating
this button will return the orientation of the graph to the application’s
defaults.
Click
on the chart so that an aspect of it is highlighted, and then hold down the
[Ctrl] key on the keyboard – notice how the cursor has changed. With the [Ctrl] key held down, move the
mouse and watch the wire frame of the chart rotate. Once the wire frame is in the position you desire, release the
[Ctrl] key and the graph will be re-drawn in the orientation of the wire frame.
Although
this method of graph rotation is quick it can give some unexpected
results. However, using the Rotation
and Elevation fields works as expected every time.
The
fields within this frame are used to select a bar on the chart and amend its
value.
Use
this field to select the MAP Zone of the bar that’s value you are interested in
viewing or amending. Upon selecting a
value in this field the Value field will be updated to show the value of bar
that’s specified by the combination of the MAP Zone and RPM Zone fields.
Use
this field to select the RPM Zone of the bar that’s value you are interested in
viewing or amending. Upon selecting a
value in this field the Value field will be updated to show the value of bar
that’s specified by the combination of the MAP Zone and RPM Zone fields.
This
field presents the value of the bar that’s specified by the combination of the MAP
Zone and RPM Zone fields for amendment. If you type into the field directly, pressing [Return] will
update the graph with the new value. If
you use the up/down arrows to the right of the field to update the value, once
the arrow has been released, the graph will be updated.
If
the graph is being used to display ‘Benchmark’ or ‘Difference’ data, the Value
field will be disabled so that the data cannot be amended.
In
addition to using the MAP Zone and RPM Zone fields to specify
which bar to amend, you can simply left-click the bar using the mouse. The top and bottom of the bar that you
clicked on will be highlighted and the MAP Zone, RPM Zone, and Value
fields all updated to match.
If
the graph is being used to display ‘Benchmark’ or ‘Difference’ data, the Value
field will be disabled so that the data cannot be amended, and the OK and
Cancel buttons will be replaced by a Close button. The Close button has the same
functionality as the Cancel button.
If
you exit the 3D Graph using the OK button, any changes made to the zone
data will be brought back to the Zone Data Editor and the relevant grid
updated. If you exit using the Cancel
button, any changes will be lost.
The Scatter Graph is used to generate
comparisons of one of the Data log’s data items expressed against another
across the entire length of the data log, optionally filtered by other data
items. The usefulness of this graph is
best illustrated by some examples:
You can filter the data displayed by any
number of the data log’s parameters.
The application ships with some useful presets, which can be added to
using the Preset Scatter Graph Editor.
This menu option will print the displayed graph. A standard printer selection dialog will open to allow you to choose and configure your printer.
This menu option will allow you to save the details of the data items that are displayed on the Scatter Graph in a spreadsheet-friendly CSV (Comma Separated Variable) text file. This file can then be loaded into a spreadsheet and its contents analysed to your heart’s content. The file will contain details of the filters applied to the Scatter Graph, the Sample No., X-Axis and Y-Axis data items, and any other data items currently being shown in the Sample Graph window’s Sample Details and Graph Data Selection List.
Use
this to close the scatter graph window.
Use this item to copy the displayed graph to the clipboard so that it can be pasted down into other applications. Once within the other application, you may have the choice of pasting down the chart itself in several formats, or the data that the chart is displaying. This will be revealed in the other application’s ‘Paste Special’ menu.
Use this menu option to update the highlighted Preset Scatter Graph with the screen’s current field settings – handy for tweaking the preset graphs.
Use this menu to create a new Preset Scatter Graph based on the screen’s current field settings. You’ll be prompted for a name for the new preset graph, and the graph will be associated to the Licence Type of the currently loaded data log.
Select this menu item to hide and show the Sample Details frame. Whether the Sample Details frame is shown when a Scatter Graph window is opened can be set using the Sample Details in Scatter Graph setting in the Options window.
Specify the type of data to display in the
X-Axis. The Data Items listed are only
those that are relevant to the type of data log that is currently loaded.
Specify the type of data to display in the
Y-Axis. The Data Items listed are only
those that are relevant to the type of data log that is currently loaded.
This frame allows a collection of filters to be applied to restrict the data that is plotted on the graph. If the loaded data log is larger than 5,000 samples you must specify at least one filter – this is in your best interests; it takes a long time to draw a graph with more than 5000 points on it! To add a new filter click on the New button, to change the details of an existing filter first highlight the filter and then click the Modify button, and to delete a filter highlight the filter and then click the Delete button.
Start by selecting the Data Item that the filter is to apply to. The Data Items listed are only those that are relevant to the type of data log that is currently loaded. Depending upon the Data Item chosen, a From and To range of values is entered or a specific value is chosen from the combo box in the From field. The picture above shows the process of creating a filter with a Data Item that requires a specific value to be chosen. The filters are ‘inclusive’ filters, i.e. by specifying a range of values a sample’s Data Item must fall within that range for it to be plotted. For Data Items that require a specific value to be chosen, a sample’s Data Item must have that value for it to be plotted. If more than one filter is created, a sample must satisfy all the filters for it to be plotted. If the Sample Graph is not displaying the data log’s full sample range when the Scatter Graph is launched a filter may automatically be created for the sample number range the Sample Graph is displaying, depending upon the setting of the Scatter Graph Auto Sample Filter checkbox in the Miscellaneous Defaults frame of the General tab of the Options window.
These allow the appearance of the points that are plotted on the graph to be determined by the user. Smaller points allow a more precise graph, but become more difficult to click on to see the sample details over on the right-hand side of the window.
The Preset Graphs are simply predefined sets of Axis, Filter, and Point Style frame values. The application ships with a few examples, but you can create your own using the Preset Scatter Graph Editor. Upon selecting a Preset Graph, the settings of the adjacent Graph Contents Frame fields will change.
Only
the Preset Graphs that have the same Licence Type as the loaded data log are
displayed, so for instance, if you load a FM Link data log you’ll see a
different set of Preset Graphs than if you load an Electromotive Tec-3 data
log.
Once
you have determined your graph’s contents, activate this button to actually
draw the graph.
This
is a very handy button indeed. Once you
have highlighted a point on the scatter graph, activating this button will
switch focus to the Sample Graph with the sample in question shown in
the centre of the graph. You can also
achieve the same result by double-clicking a point on the Scatter Graph. The width of the Sample Graph displayed (in
terms of data log samples) is determined by the Show Point Sample Graph
Width setting within the Miscellaneous Defaults frame of the General
tab of the Options window.
This list displays the details of the data log from the point in time of the currently highlighted data point on the graph. It contains all of the Data Items that are relevant to the type of data log that is currently loaded. If a graph is not displayed the Value column will contain no information.
For a detailed description of what each Data Item displays see the section Data Item Explanation.
The
set of Data Items that are displayed in the list can be restricted to only
those of interest to the User. This is
done using the Data Item Definitions tab of the Options window.
Once
a graph has been drawn, a single click on any of the points on the graph will
display the details from the data log sample it represents in the Sample
Details frame. Double clicking a
point on the graph will bring the Sample Graph to the front and display within
it the data point highlighted on the Scatter Graph. Right clicking the graph will bring up a context menu allowing
the graph to be copied to the clipboard or printed.
The
Power Graph is used to generate power and torque curves from sections of your
data log. It’s not clever enough to
work these things out from your data log in general, but requires that you
actually perform a ‘power run’ whilst data logging. This consists of a 1500 RPM through to 7000 RPM+
foot-to-the-floor acceleration in a known gear. The higher the gear, the lower down in the rev range you’ll
achieve your target boost and you’ll have a smoother graph… but you’ll also run
a higher risk of getting caught speeding!
A
nice touch is the ability to save your power graphs to disk and then load them
back in as benchmarks for later runs.
This enables you to easily do back-to-back comparisons of the
performance upgrades or ECU tweaks on your car. If you generate a power graph that you are particularly proud of
you can use this feature to save it for posterity or pass it to your
friends. The screen shot above shows a
benchmark displayed along side the actual run being plotted.
Note
that the figures generated by the calculations are all at the wheels. You can guesstimate your engine’s power by
adding an appropriate amount to cover drive train losses. For two wheel drive vehicles this is
typically in the 25-30 HP range (or its equivalent), and for four wheel drive
it can be as high as 100 HP (or its equivalent).
There’s
no rocket science involved in these calculations. The application calculates the speed of the car based on the RPM,
gear ratio, final drive ratio, and circumference of the tyre (you have to tell
it what gear you were in at the time if your data log does not contain
speed). Knowing how frequently samples
are created in the data log, we have a change in speed over time, or
acceleration. Knowing the weight of the
car we can work out the power required to accelerate. That just leaves another calculation to compensate for
aerodynamic drag and other frictions, and allowing you to define a compensation
factor for each of the other gears in comparison to your “1:1” gear (4th on a
5-speed, 5th on a 6-speed). Once your
Power and Torque are calculated, you can then apply standard SAE J1349
correction to compensate for variations in environmental atmospheric conditions
(i.e. cold day, high elevation, etc.) There is one other ‘compensation factor’
that can be applied to the calculation: Dyno Factor. Unfortunately experience shows that the real
world rarely measures up to the theoretical world, and so if your ‘real world’
power and torque curves seem to be falling short of dyno results, and you can’t
convince yourself that you were going uphill or had a head wind, etc., you can
specify a straight percentage to add to the power and torque curves before they
are plotted.
Factors
which aren’t included in the calculation but which will affect the results to
varying degrees are:
·
Whether the road was level
·
Whether the road was curved
·
Wind
·
Wheel spin (detectable or not)
·
Tyre wear – 5mm off the tyre’s radius has a significant
effect!
·
Inaccuracies in any of the parameters you enter!
The easiest way of minimising the effect of
these is to compare runs on the same stretch of road under similar weather
conditions.
The
Power Graph will inherit the plot range of the Sample Graph (thought this can
be edited within the Power Graph). Life
is made considerably easier if the Sample Graph is displaying the relevant data
for the Power Graph before the Power Graph item of the Tools menu
is selected. Note that when the window
is first opened, if the Power Graph Auto Gear Selection option is checked in the Options window, and there is speed information in
the data log at the sample specified in the Plot Range From field, the
application will automatically set the Gear field and draw the Power
Graph.
- Unless you have your own private test track, the recommendation is that power runs are performed in third gear to keep speeds relatively sane on public roads. Because the start of a third gear power run at 1,500 RPM is likely to be around 10/15 MPH, the recommendation is also that the run is performed at a point where you would normally be joining the road from a junction (rather than just slowing down to that sort of speed in the middle of a section of road). If you can find a stretch of dual-carriage way about half a mile long with a small roundabout at each end then you’re sorted!
- If the Power Graph contains an unusual “kick” at the beginning or end then this is most likely a blip in the RPM output of the ECU – the RPM output from most ECUs is a little erratic hence the need for smoothing. Simply extend the range the Power Graph is plotted over by one sample at a time at the end the kick is seen, until the kick is brought back into line.
- For better consistency, you can use the Benchmarking feature of the Power Graph to average several power runs – see the Bench. Action field for details.
- If the figures produced are lower than expected consider the following:
1. The figures produced are AT THE WHEEL. For 2-wheel drive cars add 25 to 30 hp to give engine output. For 4-wheel drive cars add somewhere between 60 to 100 hp to give engine output (yup, you read right – 60 to 100 hp depending upon car make and model). The latest theory is that drive train losses are a fixed amount + a percentage of the engine’s power output, where the fixed amount is around 10 to 12 hp, and the percentage is around 10% for front wheel drive, 12% for rear wheel drive, and 20% for four wheel drive.
2. Make sure you accurately specify your vehicle weights (kerb and contents), including all car contents – driver, passengers, ICE equipment. The higher the figure entered as the vehicle weight, the higher the resulting torque and power output from the calculations.
3. Tyre/wheel radius. Depending upon other gearing aspects, a 5 mm error in the radius may result in a 10 lb.ft error in the torque curve.
4. Avoid wet roads. These can cause the obvious wheel spin that results in reduced acceleration and hence reported power output, but also a wet road causes more drag and reduces acceleration even further.
5. Don’t drive up hill! Power runs on roads with barely enough slope to cause the car to roll if the hand brake was released, can easily have a 10 lb.ft effect on the torque curve.
6. If you’re unsure whether a length of road is level or not, do power runs in both directions. If the power runs yield identical results the road is flat…or you had a head wind down hill and tail wind up hill that bizarrely cancelled out the slope effect…
Use
this menu option to open a power graph benchmark file (POW file), as created by
the application. Once the benchmark has
loaded, its name is displayed in the Benchmark Name field, and the Display
Action field will be enabled.
Once
you’ve already saved a power graph file using the Save As item of the File
menu, this menu option will be enabled to allow you to re-save the file quickly
using the same file name. After
selecting the menu item the Power Benchmark Comments window will open
displaying any previous comments you recorded against the benchmark for editing
and re-saving.
Use this menu option to save the displayed power graph as a benchmark, for later use in comparing against your other power runs, or for exchanging with your mates. After supplying a file name the Power Benchmark Comments window will open allowing you to enter some comments to be saved along with your benchmark.
This menu option will print the displayed graph. A standard printer selection dialog will open to allow you to choose and configure your printer.
Once
you have started loading and saving benchmark files, a recently used file list
is maintained within the File menu.
Selecting one of these files will load it in as a benchmark, if it still
exists!
Use
this item to close the Power Graph. If
you have made any changes to car definitions within the window you will be
asked whether you’d like to keep the changes.
Use this item to copy the displayed graph to the clipboard so that it can be pasted down into other applications. Once within the other application, you may have the choice of pasting down the chart itself in several formats, or the data that the chart is displaying. This will be revealed in the other application’s ‘Paste Special’ menu.
Use
this item to call the Car Definition Details window to edit the details of the currently
selected car definition.
Once
a benchmark has been loaded, this menu will be enabled.
This
item will open up a window to display the calculation settings used to generate
the benchmark file, just so folks remain honest in their ‘claims’!
See the Car Definition Details window for an explanation of the majority of the fields.
The ambient environmental conditions entered into the Power Graph calculation.
This field displays the SAE Correction Factor used to calculate the benchmark, and also the environmental conditions supplied to calculate the correction factor.
Once a power graph has been drawn, the Tools menu will be enabled.
This
item of the menu will open up a Speed Graph window based on the data used to generate the
power and torque curves.
This
item of the menu is used to copy the calculated power, torque, and speed data
back to the data items of the Sample Graph. Here they can be seen along side the rest of the data log data
items. This is the only way the power
and torque data items are populated in the Sample Graph, they can’t be
calculated as a data log is loaded because the application has no idea what
gear you were in at any point in time.
The
parameters within this frame allow you to choose a car definition, tweak a
couple of its parameters that might vary between data logs, and enter the
environmental conditions.
The Car Definition to base the Power Graph on. Select from the list which of your preset car definitions is to be used as the basis for the power calculations. The car definition contains the gearing, weight, and aerodynamic details of the car. When the Power Graph window opens, the first Car Definition in the list is automatically selected. If this isn’t the one you use most often, simply change the order of the Car Definitions using the Car Definition Editor. Note that when the window is first opened or upon selecting a new Car Definition, if the Power Graph Auto Gear Selection option is checked in the Options window, and there is speed information in the data log at the sample specified in the Plot Range From field, the application will set the Gear field automatically.
Unfortunately, the RPM output from the most ECUs (that the power and torque calculations are based on) is not particularly smooth and jumps in quite inconsistent steps. This means that the application must attempt to smooth the RPM to reveal its trend before the power and torque calculations use it. The higher the number entered in this field the more smoothing will be applied to the curves, but the trade-off here is with missing genuine spikes. It is best to use as little smoothing as you can get away with, which is typically between “3” and “8” in this field.
This is your best guesstimate of the weight
of the car driver and accessories during the power run. This figure is added to the Car Kerb
Weight figure in the Car Definition for use in the power
calculations. Increasing the weight
raises the torque and power curves, decreasing the weight lowers the torque and
power curves. If this doesn’t seem to make
sense, remember that we already have the acceleration of the car – if that car
weighed 10 tons it would have required a lot more power to move it than if it
weighed 10 kg…
The
gear that the power run was done in. If
the Power
Graph Auto Gear Selection option is checked in the Options window, and there is speed information in
the data log at the sample specified in the Plot Range From field, the
application will set the Gear field automatically.
Set
this to the units that you want to display the power curve in. ‘Imperial’ means ‘hp’ and ‘lbft’, and
‘Metric’ means ‘kW’ and ‘Nm’. When this
field is changed, you will be asked whether you want the existing entry in the Contents
Weight field converted to the new units.
This set of fields allows the ambient environmental conditions to be set. They are defaulted from fields set in the File Locations and Power Graph tab of the Options window, and in some cases from the data within the data log. They are used in the aerodynamic drag SAE correction calculations.
The environmental ambient temperature as would be read directly from a thermometer. If your data log contains manifold air temperature then this field will default to the lowest value found in the entire data log. Unless the data log covers you starting your car from cold this is unlikely to be the actual outside temperature, but may serve as a guide to correctly setting it.
This field lets you choose the way in which humidity is expressed: based on Relative Humidity, or based on Wet Bulb Temperature. The label of the field below is changed as appropriate.
The environmental relative humidity. This field is only displayed if the Humidity Type field is set to “Relative Humidity”.
The environmental wet bulb temperature. This field is only displayed if the Humidity Type field is set to “Wet Bulb Temp”.
The environmental atmospheric pressure. This is used to compensate for increased elevation as well as default weather conditions. If your data log contains a reading of this (currently Flyin’ Miata Link ECU data logs only), then this field will be defaulted from the data log rather than the default setting in the SAE Correction frame of the Options window.
This checkbox is used to turn on SAE
correction when generating the Power Graph.
The Correction Factor displayed below is applied to all Power and Torque
figures.
The SAE J1349 Correction Factor as calculated from the environmental conditions specified in the fields above it.
If you have a power benchmark loaded, its
name will be displayed here.
This field is enabled once a Benchmark has been loaded. “Hide” will plot just the data log’s power curve, “Show” will plot both the data log’s power curve and the benchmark, “Average” will plot the benchmark and an average of the data log’s power curve and the benchmark.
“Average” can be used to average the results of several Power Runs for more consistent results. Here’s how we recommend using the feature (the example assumes the average of three Power Runs is required):
1. Generate the Power Graph for the first Power Run.
2. Create a benchmark file from this Power Graph.
3. Generate a Power Graph for the second Power Run.
4. Load the benchmark created in step 2. and set the Bench Action field to “Average”.
5. Re-generate the Power Graph from step 3 and notice that the curves displayed for “Your Data” are an average of the second Power Run and the benchmark.
6. Create a second benchmark file from the Power Graph. This benchmark is the average of the first and second Power Runs.
7. Generate a Power Graph for the third Power Run.
8. Load the benchmark created in step 6. and set the Bench. Action field to “Average”.
9. Re-generate the Power Graph from step 7 and notice that the curves displayed for “Your Data” are an average of the third Power Run and the benchmark. You are now looking at an average of all three Power Runs.
Together these determine the range of samples the graph will cover. The values entered within these fields must be within the range of samples loaded, which is displayed in the right hand end of the status bar at the base of the window. A range greater than 1,000 cannot be entered, but to be honest, if it took longer than this to do a power run, you’ve got some serious problems with your car!
Note
that when the window is first opened or upon changing the Plot Range From
field, if the Power Graph Auto Gear Selection option is checked in the Options window, and there is speed information in
the data log at the sample specified in the Plot Range From field, the
application will set the Gear field automatically.
Once
you have determined your graph’s contents, activate this button to actually
draw the graph. This is the window’s
default button, so hitting the Return key whilst the window has focus will
activate the Draw Graph button.
Once a graph has been drawn, right clicking it will bring up a context menu allowing the graph to be copied to the clipboard or printed.
Underneath
the graph, peak power and torque fields are displayed for the data log and a
benchmark, if loaded. In addition, a
theoretical top speed for the data log and benchmark are also displayed based
purely in aerodynamic drag, and assuming the car’s gearing is sufficiently tall
to reach this speed.
The purpose of the speed graph is to display and calculate in-gear acceleration times in comparison with power benchmarks.
Within this frame, the units of speed can be set and the benchmark moved relative to your speed curve for better side-by-side comparison.
You enter a range, click the Calculate button, and then the application will tell you how long it took to accelerate between those speeds. If either end of the speed range is outside of the speed covered by the benchmark or the power run, you’ll see ‘N/A’ reported back from the calculation.
An alternative way of setting the start and end speeds is to click a point on one of the graph series and then right-click to see the context menu – see below.
Points on both the speed curves can be highlighted by left-clicking on them. Once a point has been highlighted, a right-click on the graph will open the graph’s context menu.
Performs the same action as the Copy item
of the Edit menu.
This menu option will print the displayed graph. A standard printer selection dialog will open to allow you to choose and configure your printer.
Selecting this item will copy the speed at the highlighted data point into the Speed From field in the Acceleration Time Query frame.
Selecting this item will copy the speed at the highlighted data point into the Speed From field in the Acceleration Time Query frame, and then immediately perform the acceleration calculation.
Selecting this item will copy the speed at the highlighted data point into the Speed To field in the Acceleration Time Query frame.
Selecting
this item will copy the speed at the highlighted data point into the Speed
To field in the Acceleration Time Query frame, and then immediately
perform the acceleration calculation.
This menu item only applies to Flyin’ Miata Link ECU data logs.
This window is used to convert a binary log file generated by the data logging program in to data log that the application can load. When acquiring a new data log, you have the option of Retain Binary File. If this field is checked, the binary file that is generated by the data logging program and subsequently loaded into the data log conversion will also be saved in the application’s working directory with the same name as the data log, except with an extension of ‘bin’. ‘Why do I want this file?’ you may ask. Three reasons, the first: if you are short of disk space, the binary file is typically a quarter of the size of the data log, and using the Convert Binary Log File option of the Tool menu you can regenerate the data log when ever you wish to see it. So…you don’t need to keep the large data log files, you can just keep the smaller binary files, but obviously there is an inconvenience factor. The second reason to keep the binary files is that they actually contain more information that the data conversion program puts in the data logs, so if any future enhancements to the data conversion program result in more data coming out of it, you’ve still got the binary files from your existing data logs to generate new, more detailed data logs. The third reason is that there may be times when Flyin’ Miata require the extra information in the binary file whilst supporting their products and may ask if you can send it to them for analysis.
This
is the binary file (extension of ‘bin’) that is to be converted. The browse button to the right of the field
can be used to locate the file if you are unsure of its whereabouts. If you use the Data logging/Upload program
outside of Data Log Lab, you may have its binary output files lying around and
want to convert these (extension of ‘dat’).
To this end you can specify and select files with an extension of ‘dat’
as well as ‘bin’.
This is the name to be given to the new data log and the location it will be created in. The browse button to the right of the field can be used to navigate the file system to find an existing directory or file existing file (any existing file will be overwritten).
This field will default to the directory a file was last loaded from plus the name of the file selected in the Path and File Name of Binary File field with a “.txt” extension.
If
this box is checked, after the binary file has been converted it will be loaded
into the application. Fairly self
explanatory really…
This window is used to configure
the application.
The General tab is used to
specify various default options that the application uses in its operation and
to maintain software key details.
This field allows an engine coolant temperature to be set that the application will look for whenever a data log is loaded to determine the initial Plot From field value of the Sample Graph. In other words, set this to ’80’ and when you load a data log the Plot From field of the Sample Graph will be set to the first sample where the coolant temperature is greater than or equal to 80 degrees Celsius, so if you then immediately hit the Draw button you won’t be distracted by the part of the data log where engine temperature was coming up to speed.
This is the width, in samples, of the Sample Graph drawn when you click on the Show Details button within the Scatter Graph.
This is the default width, in samples, of the Sample Graph drawn when you first load a data log or acquire a new one.
This is the number of lines within a Link Plus data log generated each second. This field defaults to 7.0 Hz that has been established by trials. Once Link Engine Management confirms the exact frequency, this can be entered here for better accuracy when calculating Power Graphs.
This field allows the background colour scheme of all the graphs in the application to be chosen, default being “Grey”.
If you put a check in this box, whenever you
open a Scatter Graph a Sample Details frame will be displayed in it.
Only applicable to Flyin’ Miata Link owners.
If this box is checked then when the Sample Graph’s New File window opens, the file name will be suggested for you. The file name follows the format YYYY-MM-DDx according to the system date, where x is a sequence letter starting at “a” in incrementing towards “z”. The sequence letter will reset to “a” each day. The order of year, month, and day elements ensures that the files created will list in date order when sorted alphabetically.
This setting is great for getting a quick overview of each data log as you first load it. If this box is checked, when opening or acquiring a new data log, all Preset Scatter Graphs that have their Auto Draw After a File is Opened indicator checked with be automatically plotted in new Scatter Graph windows.
This check box can be temporarily overwritten by the an option in the Sample Graph’s File Menu. This setting isn’t permanently stored, and when the application is ran again will revert to the setting of this field.
If this box is checked, when opening a new Scatter Graph, a filter will automatically be created of the sample range displayed within the Sample Graph window.
This frame is used to enter registration and licence information. The application comes with a built-in 30-day trial. Once this has expired, you need to purchase a software key to continue using it. Look in the About item of the Help menu for details of how to obtain a software key.
After
adding or removing software keys be sure to re-start the application to ensure
that all appropriate features are enabled.
Enter the name of the individual to whom the
software is registered. This field is
case sensitive and directly related to the software keys. Until a Registered Name has been entered,
the Software Keys frame will not be enabled.
Once the Software Keys frame is enabled by entering a Registered Name, the following actions can be performed.
Click the New button to open the Software
Key window where the details of the new key can be entered.
Highlight the software key by clicking on it
in the list and then click the Modify button to open the Software Key
window where the details of the highlighted software key will be available to
edit.
Highlight the software key by clicking on it
in the list, and then click the Delete button. You will be asked to confirm the deletion. If you accidentally delete the wrong
software key, the only way of retrieving it is to cancel out of the Options
window.
Select the appropriate key type and then
enter the software key in the Key field. Due to the non-English language nature of the key, we’d recommend
copying and pasting it from your Software Key Document. Note that the key displayed in the screen
shot is not a valid one!
This contents of this tab are only applicable to users with a Flyin’ Miata Link ECU.
Here you set your Link ECU chip
information. This information is used
in two ways:
This combines the ECU’s engine size and chip version. Options are:
Enter a date in the format ‘dd-mmm-yyyy’,
where ‘dd’ is the day of the month, ‘mmm’ is the three-character abbreviation
of the month, and ‘yyyy’ is the year, including century. Therefore the 1st December 2000 would be
’01-Dec-2000’.
If the Silent Defaults option is
checked, the defaults entered on this tab will be applied wherever necessary
without informing the user. If the Silent
Defaults option is unchecked, a message will be displayed.
The fields within this frame are used to
determine the default settings of the check boxes within the Upload Zone
Settings window.
Check
this box if you want the changes to be permanently stored in the Link. If this isn’t checked, once the car’s
ignition has been turned off the newly uploaded changes will be lost.
Check
this box if you want the upload to be verified. This has the advantage of ensuring that what you want uploading
actually gets uploaded, but at the expense of taking extra time to do it. Only un-check
this box once you have gained the confidence of many uploads without
verification error.
Check
this box to see more detailed information in the Data logging/Upload program
window as the zone settings are uploaded.
This will slow down the upload and verification procedures.
This one can be a real time saver. If this box is checked, rather than perform a complete upload, the application will only upload the zones that have been changed. To work out which zones have been changed a Change Comparison File is specified, which is simply the Data log or MAP file that contains the zone settings that are currently in the ECU. Bear in mind that any discrepancy between the contents of this file and the current contents of the ECU may result in some of your changes not getting uploaded.
Set the field to the computer’s COM port
number that is used for communication with the Link ECU.
This field defines the default value for the Retain Binary File check box in the New File window.
‘Why do I want to retain this type of file?’ you may ask. Two reasons, the first: if you are short of disk space, the binary file is typically a quarter of the size of the data log, and using the Convert Binary Log File option of the Tool menu you can regenerate the data log when ever you wish to see it. So…you don’t need to keep the large data log files, you can just keep the smaller binary files, but obviously there is an inconvenience factor. The second reason to keep the binary files is that they actually contain more information that the data conversion program puts in the data logs, so if any future enhancements to the data conversion program result in more data coming out of it, you’ve still got the binary files from your existing data logs to generate new, more detailed data logs. There is a third reason – there may be times when Flyin’ Miata require the extra information in the binary file whilst supporting their products and may ask if you can send it to them for analysis.
If you put a check in this box, whenever you load a data log with any tags within it, the Data Tags Window will open automatically.
The fields within this frame are
used to determine the starting position of the 3D graphs that can be displayed
from the Zone Data Editor of the fuel and ignition zones. The fuel and ignition default values are
different because of the way in which the fuel zone values typically increase
with RPM and MAP, where as the ignition zone values typically decrease with RPM
and MAP. Therefore a good angle to view
the fuel zones is not necessarily a good angle to view the ignition zones.
This
tab is used to specify where various Link-related files the application needs
to access are stored. The Data logging/Upload
Program and the Data log Conversion Program (these files are used by the
application to acquire new Data logs and download and upload Link ECU settings)
are LINKWIN.EXE, and MDOS.EXE respectively, and can be found within their own
like-named directories within the application’s installation directory. If you do not have the intake air
temperature sensor fitted, you should change the data logging/Upload program
from ‘MDOS_AT.EXE’ to ‘MDOS.EXE’.
This program is used by the application to
acquire new data logs and zone data, and to upload zone data to the Link
ECU. The browse button to the right of
the field can be used to locate the file if you are unsure of its whereabouts. At the time of writing this programs is
named LINKWIN.EXE, can be found within the LINKWIN sub-directory of the
application’s installation directory.
This program is used by the application to
convert the data logs acquired by the Data Logging/Upload Program into a format
that the application can understand and load.
The browse button to the right of the field can be used to locate the
file if you are unsure of its whereabouts.
At the time of writing this programs is named MDOS.EXE, can be found
within the MDOS sub-directory of the application’s installation directory. If you do not have the intake air
temperature sensor fitted, you should change the Data logging/Upload program
from ‘MDOS_AT.EXE’ to ‘MDOS.EXE’. Although
Data Log Lab ships with the most current version of MDOS_AT.EXE, for real-time
fuel and ignition tuning, we recommend you install Stan Mahaffey’s excellent RTLink
application. Once installed, simply
change the Path and File Name of Data Log Conversion Program to
RTLink.EXE. For more information see
the RTLink section
at the end of this documentation.
If you are using the Link’s auxiliary input for an alternative use, e.g. wide band oxygen sensor or exhaust gas temperature sensor, then this field is used to specify the conversion file the program will use to scale the input voltage to something more meaningful. For more information see the Auxiliary Input Conversion Files section.
This entry lets you specify the conversion file used to derive the A/F (air/fuel ratio) data item from the narrow band (stock) oxygen sensor’s input. This allows a conversion file to be selected that suits your fuel characteristics or to display lambda figures rather than air/fuel ratio. For more information see the Narrow Band Oxygen Sensor Conversion Files section.
This frame is used to specify where various
files the application needs to access are stored.
The
working directory is where all your new Data logs, Link ECU setting files, and
Power Graph files will be saved by default, and the starting point for the File
Open dialog each time the application is ran.
The browse button to the right of the field can be used to create and/or
pick a directory.
You can set the background picture to be displayed in the graph windows of the application prior to actually drawing graphs. The browse button to the right of the field can be used to select the picture. The picture must be in one of the following formats: bmp, dib, gif, jpg, wmf, emf, ico, or cur.
If you are using the application’s Universal Data Log licence, this is where the definition file for your particular data log format is specified. When the application is first ran and the Welcome screen displayed, if you choose a data log format that uses the Universal Data Log licence, the definition file will already be populated here.
The application ships with definition files for a variety of data log formats which can all be found within the Universal Data Log Format subdirectory of the application’s main installation directory (“C:\Program Files\DataLogLab\Universal Data Log Formats\” if the application has been installed to the default location).
Once the new Data Log Definition file has been specified, press the Load button to load it into Data Log Lab. A message will be displayed confirming successful loading or highlighting a problem with the definition file contents. If the file does have a problem, either it must be corrected and the Load button pressed again, or the field must be set to a valid definition file or cleared. If the field is cleared, the Universal data log format reverts to a default Hydra definition that ships with the application.
Once the new Data Log Definition file has loaded successfully, the “Universal” entries in File Type combos in Default File Type field, the File Open window, the Preset Sample Graph Editor, and the Preset Scatter Graph Editor will all be updated with the description from the new Data Log Definition file.
You can create your own definition files or tweak the ones that ship with the application. See the Universal Data Log Definition File section for more information.
Every time you load a data log definition file with a different name (not file name), all the Data Items in the definition file will be re-checked in the Data Item Definitions tab to ensure they can all be seen.
Set
this field to the type of data log you most frequently load. This will be the default value in all
windows that require a file type to be entered.
This frame is used to specify various Power Graph related defaults for the application. The environmental information here is used in the calculation of
aerodynamic drag and the SAE correction factor.
The environmental ambient temperature as would be read directly from a thermometer. When a Power Graph window is first opened, if the data log contains intake air temperature, the lowest value found in the data log will be used in preference to this value.
This field determines the manner in which the humidity is defined – as Relative Humidity or Wet Bulb Temperature. There’s no difference in the results when calculated from Relative Humidity or Wet Bulb Temperature, it’s just whichever is the most convenient for you to use.
The environmental relative humidity. This field is only displayed if the Humidity Type field is set to “Relative Humidity”.
The environmental wet bulb temperature. This field is only displayed if the Humidity Type field is set to “Wet Bulb Temp”.
The environmental atmospheric pressure. This is used to compensate for increased elevation as well as default weather conditions.
For non-Universal data log formats only: This is the ambient air pressure the application will use to work out the Boost and Vacuum data items if they or the ambient air pressure is not read from the data log – the application assumes that the MAP data item is absolute. In other words, if you live in the mountains and this is set to 90 kPa, when you read in a data log with MAP at 200 kPa, the application will calculate your Boost data item at that point as 200-90 = 110 kPa = 16.0 PSI. If you data log contains “gauge pressure” rather than absolute, this is used to calculate the absolute MAP.
Check this box to default SAE correction on. SAE correction takes account of the changes in power output due to environmental conditions to give you a standardised power and torque curve, i.e. with SAE correction turned on, you shouldn’t see an increase in power output as the ambient temperature falls.
The SAE J1349 Correction Factor as calculated from the environmental conditions specified in the fields above it.
If this box is checked, the Power Graph window will always try to set the correct gear for the graph that you’re trying to draw. It can only do this if there is speed information present in the data log at the sample specified in the Power Graph’s Plot Range From field. It will try to guess the power run gear when the Power Graph window is opened, after selecting a Car Definition, of after changing the Plot Range From field. If your data log is not loaded with speed information, once a Power Graph has been generated and the Power Graph window’s Copy to Sample Graph menu option invoked, speed information will be created for that section of the data log along side the power and torque information.
If the Auto Gear Selection check box is checked, this field will be enabled. Use this to select the units of speed within your data log. If they are not “Miles per Hour” or “Kilometres per Hour”, select the option “Other”. If you get this selection wrong or load a data log with the speed expressed in different units, the Auto Gear Selection process in the Power Graph window will not perform as expected.
If the Auto Gear Selection check box is checked, this field will be enabled. If the Speed Units field is set to “Other”, this field will be enterable. The field is used to enter an amount to multiply the speed data in your data log by to convert it to meters per second. If you’ve selected “MPH” or “KPH” in the Speed Units field, this figure is calculated for you and this field is display-only, so you don’t need to worry about it. If you’ve selected “Other” in the Speed Units field, you’ll need to supply this figure yourself. This value is needed by the Auto Gear Selection process in the Power Graph window. If you get this selection wrong or load a data log with the speed expressed in different units, the Auto Gear Selection process in the Power Graph window will not perform as expected
For data logs loaded using a Universal Data Log Definition file, the definition file may contain a speed conversion factor of its own for use with the Power Graph’s auto gear selection feature (see the Advanced Features sub-section of the Universal Data Log Definition Files section for more information). If the definition file does contain a speed conversion factor, and a data log of that format the definition file describes is loaded, this information will always be used in the Power Graph window for auto gear selection in place the settings of this field and the Speed Units field.
This tab is used to specify which of the Data Items are available within the application and their appearance on the Sample Graph. If there are certain Data Items that are of no interest to you (and I’m sure there will be!), by removing the check box to the left of each of them they won’t appear in the Sample Details lists of the Sample Graph and Scatter Graph. For a definition of what each Data Item represents see the Data Item Explanation section. Certain Data Items are mandatory and cannot be unchecked.
Note that all non-Universal Licence Types share a common set of Data Items and hence changes to the appearance of a Data Item under one Licence Type will be seen under another Licence Type – Data Items of this type are e.g. RPM, Boost, Power, Torque. The Universal Licence Type has its own dedicated set of appearance settings so that changes to these won’t affect the appearance under other Licence Types.
Once you choose a Licence Type, the list below will only contain the Data Items that are relevant to that Licence Type. The Data Items relevant to the “Universal” Licence Type will change depending upon the Data Log Definition file specified in the Path and File Name of Universal Data Log Definition File field of the File Locations and Power Graph tab of this window.
This contains all the Data Items that are relevant to the Licence Type field entry. The contents can be sorted by any of the three columns by clicking on the column header. The tooltips for each of the items in the list is comma separated a list of the data log columns that populate that Data Item.
The thickness of the line representing the
highlighted Data Item on the Sample Graph.
The style of the line representing the
highlighted Data Item on the Sample Graph.
The colour of the line representing the highlighted Data Item on the Sample Graph. The button to the right of the field is used to open the colour selector where any of the system colours can be selected or your own created.
This is the amount by which the values in the Data Item will be multiplied for display in the Sample Graph. Because the Sample Graph has only one vertical scale that must cope with all Data Items, many are “scaled” for a better fit. For example, RPM is divided by 100 (scaling factor of 0.01) so that 5,000 RPM is seem as “50”, where as A/F ratio is multiplied by 10 (scaling factor of 10) so that 15:1 appears as “150”. If you’re not happy with the application’s defaults then change here.
This button will restore the current highlighted Data Item’s configuration to the defaults. For non-Universal licence types, these are the defaults that the application ships with. For the Universal licence type, this may be default values set in the Data Log Definition file for that Data Item. For any properties that the Data Log Definition file doesn’t contain, the application defaults will be used.
Clicking this button will check all the Data Items in the list.
Clicking this button will un-check all the Data Items in the list, apart from those that are mandatory and must always be included.
This window allows the maintenance
of the preset graphs available in the Sample Graph window. The graphs
are listed by the Licence Type they are associated to.
Click the New button to open the Preset
Sample Graph Details window where the details of the new preset graph can
be entered.
Highlight the preset graph by
clicking on it in the list and then click the Modify button to open the Preset
Sample Graph Details window where the details of the highlighted preset
graph will be available to edit. You
can also double-click the entry to perform this function.
Highlight the preset graph by
clicking on it in the list, and then click the Delete button. You will be asked to confirm the
deletion. If you accidentally delete
the wrong preset graph, the only way of retrieving it is to cancel out of the
editor.
The order in which the preset graphs are displayed can be altered by using the two buttons in the bottom right corner of the Preset Graphs frame. Highlight a preset graph by clicking on it and then click the up or down button to change its position in the list.
This window allows the definition of a Preset Sample Graph.
The name of the Preset Sample Graph, displayed in the Preset Graphslist in the Sample Graph window.
The Licence Type field is passed through from the Preset Sample Graph Editor window and cannot be changed. The Data Item list below it only displays the Data Items that are applicable to the Licence Type.
Check the box to the left of a Data Item to include it in the preset graph. If a Data Item has a red square to left of it this means that it has been permanently hidden from view in the Sample Graph, so selecting it will not serve any great purpose…unless you show it again by checking it in the Data Item Definitions tab of the Options window.
Normally the vertical scale of the graph is determined by the application each time a graph is drawn to best suit the data displayed. This results in it changing as you page and scroll left and right through the data log, which some folks find disconcerting. If you check the Fix Graph Maximum checkbox, you can then enter a fixed maximum value into the Graph Maximum field for the vertical scale that will not change, no matter what data is displayed on the graph. The value you enter here may be adjusted by the application so that it can make a sensible vertical scale with a useful number of divisions. If data is graphed that is higher in value than the number specified as the vertical scale maximum, it will not be seen.
Use this to load a graph definition from a Preset Sample Graph file into the graph being edited. Popular Preset Sample Graph files are available to download from the Data Log Lab web site. When you load a Preset Sample Graph file, if it was designed for a different Licence Type or includes Data Items that are not displayed in the list on the screen, an appropriate error message will be displayed, but the suitable information in the file will still be loaded.
Use this to save the graph definition to a Preset Sample Graph file. The application will ask whether you wish to include the Licence Type in the Preset Sample Graph file it creates. A Preset Sample Graph file with a Licence Type in it will cause an error to be displayed if it is subsequently loaded into a Preset Sample Graph that is being created against a different Licence Type.
This window allows the maintenance
of the preset graphs available in the Scatter Graph window. The graphs
are listed by the Licence Type they are associated to.
Click the New button to open the Preset
Scatter Graph Details window where the details of the new scatter graph can
be entered.
Highlight
the preset graph by clicking on it in the list and then click the Modify
button to open the Preset Scatter Graph Details window where the details
of the highlighted preset graph will be available to edit. You can also
double-click the entry to perform this function.
Highlight
the preset graph by clicking on it in the list, and then click the Delete button. You will be asked to confirm the deletion. If you accidentally delete the wrong preset
graph, the only way of retrieving it is to cancel out of the editor.
The order in which the preset graphs are displayed can be altered by using the two buttons in the bottom right corner of the Preset Graphs frame. Highlight a preset graph by clicking on it and then click the up or down button to change its position in the list.
The name of the preset graph.
The Licence Type field is passed through from the Preset Sample Graph Editor window and cannot be changed. The Axis and Filter Data Item combos only contain the Data Items that are applicable to the Licence Type.
All Preset Scatter Graphs with this box checked will be drawn in a new Preset Scatter graph window whenever a file is opened, if the Scatter Graph Auto Draw box in the application’s options is checked.
Specify the type of data to display in the X Axis. If a Data Item has a red square to left of it this means that it has been hidden from view in the Sample Graph, so selecting it will not serve any great purpose…unless you reveal it again. For details on how to hide Data Items that you’re not interested in, the Data Item Definitions tab of the Options window.
The field only
contains the Data Items that are applicable to the Licence Type.
Specify the type of data to display in the Y Axis. If a Data Item has a red square to left of it this means that it has been hidden from view in the Sample Graph, so selecting it will not serve any great purpose…unless you reveal it again. For details on how to hide Data Items that you’re not interested in, the Data Item Definitions tab of the Options window.
The field only
contains the Data Items that are applicable to the Licence Type
This frame allows a collection of filters to be applied to restrict the data that is plotted on the graph. To add a new filter click on the New button, to change the details of an existing filter first highlight the filter and then click the Modify button, and to delete a filter highlight the filter and then click the Delete button.
Start by selecting the Data Item that the filter is to apply to. Depending upon the Data Item chosen, a From and To range of values is specified or a specific value is chosen from the combo box in the From field. The picture above shows the process of creating a filter with a Data Item that requires a specific value to be chosen. The filters are ‘inclusive’ filters, i.e. by specifying a range of values a sample’s Data Item must fall within that range for it to be plotted. For Data Items that require a specific value to be chosen, a sample’s Data Item must have that value for it to be plotted. If more than one filter is created, a sample must satisfy all the filters for it to be plotted.
If a Data Item has a red square to left of it this means that it has been hidden from view in the Sample Graph, so selecting it will not serve any great purpose…unless you reveal it again. For details on how to hide Data Items that you’re not interested in, the Data Item Definitions tab of the Options window. The Data Item field only contains the Data Items that are applicable to the Licence Type
These allow the appearance of the points that are plotted on the graph to be determined by the user. Smaller points allow a more precise graph, but become more difficult to click on to see the sample details over on the right-hand side of the window.
Use this to load a graph definition from a Preset Scatter Graph file into the graph definition being edited. Popular Preset Scatter Graph files are available to download from the Data Log Lab web site. When you load a Preset Scatter Graph file, if it was designed for a different Licence Type or includes Data Items that are not displayed in the Axis fields, an appropriate error message will be displayed, but the suitable information in the file will still be loaded.
Use this to save the graph definition to a Preset Scatter Graph file. The application will ask whether you wish to include the Licence Type in the Preset Scatter Graph file it creates. A Preset Scatter Graph file with a Licence Type in it will cause an error to be displayed if it is subsequently loaded into a Preset Scatter Graph that is being created against a different Licence Type.
Car Definitions are used by the Power Graph to calculate power and torque curves from a data log: when you plot a Power Graph you specify the Car Definition that describes the car the data log is from. The Car Definition contains details of the tyres, wheels, gearing, weight, and aerodynamics of a car – all the information the Power Graph needs to accurately calculate power and torque.
The application allows you to have as many car definitions as you wish, and to save and load them as car definition files (.car). This enables you to easily pass your car details on to a friend along with your data logs so that they too can share in the joy of your newly found 20 hp (for example). This also means you can visit the Data Log Lab web site and download from a library of car definitions if you’re not sure what the details of your car are, and you can even contribute to the library by passing on your own car definition creations.
To load in a car definition file, click the Create button to open the Car Definition Details window, and then click the Load button. See below for more details.
Click the New button to open the Car
Definition Details window where the details of the new car definition can
be entered.
Highlight the car definition by clicking on
it in the list and then click the Modify button to open the Car
Definition Details window where the details of the highlighted car definition
will be available to edit. You can also
double-click the entry to perform this function.
Highlight the car definition by clicking on
it in the list, and then click the Delete button. You will be asked to confirm the deletion. If you accidentally delete the wrong car
definition, the only way of retrieving it is to cancel out of the editor.
The order in which the car definitions are displayed can be altered by using the two buttons in the bottom right corner of the Car Definitions frame. Highlight a car definition by clicking on it and then click the up or down button to change its position in the list.
The car definition at the top of the list is the default one selected when a Power Graph window is opened, so you want to put your favourite car definition at the top of the list.
This window is used to define various physical attributes of a car that are used in the calculations within Power Graph windows.
Clicking this button will open a Load dialog where a car definition file can be selected. Upon loading, all fields will be replaced with the values from the file.
Clicking this button will open a Save dialog to allow a file name to be specified and a car definition to be generated. If you have a car definition that may be useful to others, go to the Data Log Lab web site for information on how to make it available for others.
Hopefully these two are self explanatory…
This changes the units that various fields
within the window are defined in. Where
units are applicable, it is indicated within the fields’ captions. When this field is changed, you will be
asked whether you want the existing contents of the other fields in the window converted
to the new units, e.g. Tyre Radius of 11 inches converted to 279.4 millimetres.
Here the gear and final drive ratios are
entered as decimal numbers. If your car
only has a 5-speed gearbox, just reproduce 5th gear in the 6th gear field.
This allows you to specify a percentage that
is applied to each power curve depending upon the gear that the run was done
in. It is designed to compensate for
extra drive train losses when running in gears other than the ‘1:1’ gear
(typically 4th on a 5-speed, 5th on a 6-speed).
The wheel dimensions can be specified in three different ways: by entering the tyre size, the tyre manufacturer’s revolutions per mile (or kilometre) figure, or measuring the radius from the ground to the centre of the hub.
Click this field to enable the Width, Profile, and Wheel Diameter fields.
Enter the tyre manufacturer’s revolutions per mile (or kilometre) figure. The units for this figure are determined by the Units field setting.
Here you specify the straight-line distance
between the road surface and the centre of the hub of the rear wheel. This typically less than the radius of the
tyre measured when the wheel is off the car as the weight of the car obviously
squashes the tyre. There is heated
debate over whether the “squashed” radius is more accurate or not. The counter argument is that at speed, the
centrifugal forces increase the size of the tyre and hence the radius returns
to normal. If anyone has a definitive
answer please let us know!
The aero dynamic properties of the car can be defined in two ways: the conventional coefficient of drag and frontal area combination, or a more unconventional known wheel power to maintain a set speed. The later is really for situations where the coefficient of drag or frontal area is not known, though most manufacturers publish these figures.
Note that the addition of wider tyres and or spoolers and aerodynamic aids, increases the coefficient of drag and/or frontal area of the car, so if your car is heavily modified you should compensate for it in here.
Increasing the number in this field will
result in smoother graphs, but at the expense of flattening the peaks of the
curves. Unfortunately the RPM output of
most ECUs is a little erratic (generate a power curve with a smoothing factor
of ‘2’ to demonstrate), and so the need for the smoothing. The default value gives a good compromise
between smoothness and missing the peaks.
If for whatever reason the power curves
generated by the application fall short of dyno run results, this field can be
populated with a straight percentage to apply across the curve. The reasons for the ‘real world’ power
curves not matching your dyno results are probably too political too discuss
here!
The normal gear that you perform your power
runs in. The higher the gear, the lower
down in the rev range you’ll achieve your target boost and you’ll have a
smoother graph, but you’ll also run a higher risk of getting caught speeding!
This is the manufacturer’s quoted figure for the weight of the car in standard form with lubricants and half a tank of petrol, i.e. not including those huge wheels, amp, sub, rear wing, etc.
This where you take account of all those optional extras, but most importantly the driver’s and passengers’ weights. Don’t be tempted to skimp on this figure as increasing the weight raises the torque and power curves, decreasing the weight lowers the torque and power curves!
The computer will do a little maths for you here and add together the Car Kerb Weight and Car Contents Weight.
This is applicable to Flyin’ Miata Link ECU users only.
This window allows the maintenance of the Zone Data Benchmarks that are available in the Zone Data Editor. Benchmarks are created by loading in a data log or MAP file. The application ships with benchmarks of the initial settings for both N/A and turbo, and 1.6 and 1.8 engines. Clearly most of these are irrelevant to a particular set up and so you may want to delete these straight away. The benchmarks can be restored later if required as the application also ships with the MAP files that each benchmark was generated from.
Click the New button to open
the Benchmark Details window where the details of the new benchmark can
be entered.
Highlight the preset graph by
clicking on it in the list and then click the Modify button to open the Benchmark
Details window where the details of the highlighted benchmark will be
available to edit. You can also
double-click the entry to perform this function.
Highlight the benchmark by clicking
on it in the list, and then click the Delete button. You will be asked to confirm the
deletion. If you accidentally delete
the wrong benchmark, the only way of retrieving it is to cancel out of the
editor.
The order in which the benchmarks are displayed can be altered by using the two buttons in the bottom right corner of the Preset Graphs frame. Highlight a benchmark by clicking on it and then click the up or down button to change its position in the list.
The name of benchmark.
The full path and file name of the data log or MAP file it is to be created from. The Browse button to the right of the File field allows the file to be selected. Click the OK button to load in the zone data and create the new benchmark.
Once a valid path and file name are present in the File field, click this button to load the file.
Use this button to create a MAP file of an existing benchmark. This handy in case the original file has been mislaid, etc.
By clicking this button, the Zone Data Editor will open and allow all the individual zone values for the benchmark to amended.
Following is an explanation of the data items available within the application. The presence of a column name against a data item for a given ECU indicates that the data item is populated by that ECU’s data log files. The ID and Default Characteristics will be of interest to those working with Universal Data Log Definitions.
|
Name and ID |
Description |
Explanation |
Default Characteristics |
|||||||||||||||||||||||||||||||
|
A/C 27 |
A/C Switch |
|
Indicates that the A/C switch inside the car was turned on. |
|
||||||||||||||||||||||||||||||
|
A Temp 31 |
Air Temp |
|
Intake air temperature in degrees Celsius. |
|
||||||||||||||||||||||||||||||
|
AD1 55 |
Analogue
Digital Input 1 |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
AD2 56 |
Analogue
Digital Input 2 |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
AD3 57 |
Analogue
Digital Input 3 |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
AD4 58 |
Analogue
Digital Input 4 |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
A/F 36 |
A/F Ratio |
|
For FM ECU data logs, this is derived from the standard O2 sensor output based on observations from the dyno at FM. For Link Plus data logs, this is derived from the tables given within the Link instructions. Most narrow band (conventional) O2 sensors start to read lean under prolonged boost, as they are over-heated. For UTEC users, if your data log contains a wide-band O2 column, then the A/F data item will contain this value instead of the narrow-band figure. |
|
||||||||||||||||||||||||||||||
|
A/F Tgt 83 |
A/F
Target |
|
For FM Link ECU data logs, this is derived from the auto tuning targets, MAP, and RPM. It takes account of Auxiliary Input and NB O2 sensor conversion files, as well as the auto tuning and sensor settings. The value is an interpolation based on MAP (the centre points are those displayed in the Fuel and Ignition tabs of the Zone Data Editor), but at lower MAP values, the A/F target is determined by auto tune type and RPM as well: When auto tuning type is “off” or “lambda” and MAP < row 2 centre point (43 kPa for N/A, 60 kPa for FI), if the RPM < 2k, the A/F target is zone 26, and if the RPM >= 2k the A/F target is zone 27. When the auto tuning type is “L3” or “L4”, if the MAP value is less than 64 kPa, the A/F target is zone 26. If the O2 Sensor Type is set to “NB+WB” then you must ensure that both the Auxiliary Input and NB O2 sensor conversion files use the same units (i.e. both lambda or both air fuel ratio) to get a consistent value in the data item under all conditions. |
|
||||||||||||||||||||||||||||||
|
ATR 34 |
Air Temp
Retard |
|
The instantaneous amount of ignition retard the FM Link is performing based on the settings of the Ignition Start and Ignition Slope zones. |
|
||||||||||||||||||||||||||||||
|
Aux CF 41 |
Aux
Input Converted Fast |
|
These data items show the voltage present at the auxiliary input of the FM Link. Normally this is unused on a 1.6 and controlling the EGR on a 1.8. If you decide to build your own wide band O2 sensor or exhaust gas temperature gauge (for instance), the auxiliary input can be used to data log the device’s output. A conversion file can be set up and used by the application to take the 0-5 volt input and transform it into something meaningful, e.g. an A/F ratio (see Auxiliary Input Conversion Files). The “Native” data items display the voltage on the auxiliary input whilst the “Converted” data items show the transformed values. Later 1.6 Links will report the auxiliary input voltage in the data log. For the 1.8 Link, if EGR recirculation is disabled, the auxiliary voltage will be reported in the data log at the expense of TPS information, however Throttle data item will still be accurately populated. In both of these cases the auxiliary input voltage will appear on every line of the data log and thus have a high sample rate. The application will take this data and create the “Fast” data items. In addition to this, the auxiliary input voltage will also appear in the data log on the periodic status lines. The application will take this data and interpolate for the samples between to create the “Slow” data items. Clearly the “Fast” data items are more accurate than the “Slow” data items based on sampling frequency. |
|
||||||||||||||||||||||||||||||
|
Aux CS 40 |
Aux
Input Converted Slow |
|
|
|||||||||||||||||||||||||||||||
|
Aux NF 39 |
Aux
Input Native Fast |
|
|
|||||||||||||||||||||||||||||||
|
Aux NS 32 |
Aux
Input Native Slow |
|
|
|||||||||||||||||||||||||||||||
|
BCL 75 |
Boost
Closed Loop |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Boost 37 |
Boost
(PSI) |
|
When manifold air pressure is above ambient atmospheric, this data item will contain the amount above, converted to pounds per square inch. Ambient air pressure will be read from the Default Atmospheric Pressure application setting if it is not read in from the data log. For UTEC data logs, this may be read in from the data log directly. |
|
||||||||||||||||||||||||||||||
|
CAS Err 2 |
CAS
Error |
|
Indicates a CAS error on that sample. |
|
||||||||||||||||||||||||||||||
|
Ch Purge 29 |
Charcoal
Purge |
|
Indicates charcoal canister purge occurring. |
|
||||||||||||||||||||||||||||||
|
Comp 19 |
Compressor
Clutch |
|
Indicates the air conditioning compressor clutch is engaged. |
|
||||||||||||||||||||||||||||||
|
Cnd Fan 26 |
Condenser
Fan |
|
Indicates the air conditioning condenser fan is running. |
|
||||||||||||||||||||||||||||||
|
CR 49 |
O2
Closed Loop Correction |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
C Temp 23 |
Coolant
Temp. |
|
Engine coolant temperature in degrees Celsius. |
|
||||||||||||||||||||||||||||||
|
Dwell 4 |
Ignition
Dwell |
|
None, Long, Short |
|
||||||||||||||||||||||||||||||
|
EGR 11 |
EGR
Position |
|
EGR position on a 1.8. |
|
||||||||||||||||||||||||||||||
|
EGOV 50 |
O2
Sensor Voltage |
|
Read directly from the data log |
|
||||||||||||||||||||||||||||||
|
Eng Fan 25 |
Engine
Fan |
|
Indicates the engine fan is running. |
|
||||||||||||||||||||||||||||||
|
Fuel P 12 |
Fuel
Pump Running |
|
Indicates the fuel pump is running. |
|
||||||||||||||||||||||||||||||
|
Fuel ZV 66 |
Fuel
Zone Value |
|
For the FM Link this figure is calculated from the fuel zone values loaded in using interpolation between the zone intersections. For Link Plus this is read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Fuel% M 74 |
Modified
Fuel % |
|
The ECU modified injector duty cycle. |
|
||||||||||||||||||||||||||||||
|
GAMA 48 |
GAMA
Fuelling Correction |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
GFG 60 |
GFG |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
GPO1 51 |
General
Purpose Output 1 |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
GPO2 59 |
General
Purpose Output 2 |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
IAC 16 |
IAC
Position |
|
Idle air control valve position. |
|
||||||||||||||||||||||||||||||
|
IAdv 21 |
Ignition
Advance |
|
Ignition advance in degrees before top dead centre. |
|
||||||||||||||||||||||||||||||
|
IAdv M 73 |
Modified
Igntn Advance |
|
The ECU modified ignition advance. If the data log states ‘ECU’, the value in IAdv will be duplicated. |
|
||||||||||||||||||||||||||||||
|
Idle Sp 65 |
Idle
Speed Control |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Ign ZV 67 |
Ignition
Zone Value |
|
For the FM Link this figure is calculated from the ignition zone values loaded in using interpolation between the zone intersections. For Link Plus this is read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
INJ% 14 |
Injector
% |
|
The duty cycle of the fuel injectors as a percentage of their total capacity. |
|
||||||||||||||||||||||||||||||
|
INJW 13 |
Injector
Width |
|
The length of the fuel injector ‘open’ pulse in milliseconds |
|
||||||||||||||||||||||||||||||
|
Knock 20 |
Knock
Sensor |
|
Knock sensor output. |
|
||||||||||||||||||||||||||||||
|
Knock C 30 |
Knock
Count |
|
Count of knock events that the Link has seen in the data log. |
|
||||||||||||||||||||||||||||||
|
Knock E 42 |
Knock
Event Indicator |
|
Indicates the Link registered a knock event on the sample. |
|
||||||||||||||||||||||||||||||
|
Knock T 33 |
Knock
Threshold |
|
The knock threshold the Link is using based on the value of the Knock Thr zone. |
|
||||||||||||||||||||||||||||||
|
KNR 62 |
Knock
Control Retard |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
L3 35 |
L3
Adjustment |
|
The amount of L3 adjustment. |
|
||||||||||||||||||||||||||||||
|
L3 Idle 70 |
L3
Adjustment Idle |
|
The amount of L3 adjustment at idle |
|
||||||||||||||||||||||||||||||
|
L4 69 |
L4
Adjustment |
|
The amount of L4 (slow L3) adjustment |
|
||||||||||||||||||||||||||||||
|
Lambda 6 |
Lambda
Adjustment |
|
The lambda adjustment character: +, -, =, ?, A, D, E, T, V, X, and [space]. |
|
||||||||||||||||||||||||||||||
|
LS 76 |
Load
Site |
|
Read directly from the data log |
|
||||||||||||||||||||||||||||||
|
MAF 71 |
MAF
Voltage |
|
Voltage output from the mass air flow meter (WRX). |
|
||||||||||||||||||||||||||||||
|
MAF Hz 81 |
MAF
Hertz |
|
Frequency output from mass air flow meter (EVO). |
|
||||||||||||||||||||||||||||||
|
MAF D 79 |
MAF
Digital |
|
Output from the mass air flow meter converted to a digital number between 0 and 255. |
|
||||||||||||||||||||||||||||||
|
MAF M 72 |
Modified
MAF Voltage |
|
The ECU modified MAF voltage (WRX). |
|
||||||||||||||||||||||||||||||
|
MAF M Hz 82 |
Modified
MAF Hertz |
|
The ECU modified MAF frequency (EVO). |
|
||||||||||||||||||||||||||||||
|
MAP 5 |
Manifold
Air Pressure |
|
Manifold air pressure in kPa. For UTEC data logs, this may be read in from the data log directly (and converted to kPa) or calculated. If calculated it is based on the Default Atmospheric Pressure application setting. |
|
||||||||||||||||||||||||||||||
|
MAP D 78 |
MAP
Digital |
|
Read from the data log. |
|
||||||||||||||||||||||||||||||
|
MAP Lmt 43 |
Map
Limit Event Indicator |
|
Indicates the MAP limit was hit and the Link has stopped controlling the waste gate. |
|
||||||||||||||||||||||||||||||
|
MLP 77 |
Map Load
Point |
|
Read from the data log. |
|
||||||||||||||||||||||||||||||
|
Neutral 18 |
Neutral
Switch |
|
Indicates the gearbox is in neutral. |
|
||||||||||||||||||||||||||||||
|
O2 7 |
O2
Sensor |
|
The output of the O2 sensor. |
|
||||||||||||||||||||||||||||||
|
O2A 8 |
O2
Affector |
|
None, Accel, Decel. |
|
||||||||||||||||||||||||||||||
|
PRC 28 |
PRC
Valve |
|
PRC valve position… |
|
||||||||||||||||||||||||||||||
|
Power 45 |
Power |
|
This is the instantaneous power being produced. This data item is not populated when a data log is loaded, but from within a Power Graph window once it has been calculated using its Tools menu. The units of the data item are the units that were chosen within the Power Graph. |
|
||||||||||||||||||||||||||||||
|
PWOFF 47 |
Injector
Off Width |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Rev Lmt 44 |
Rev
Limit Event Indicator |
|
Indicates that the rev limit has been reached and the Link is taking drastic action to prevent the revs raising any further – you would have felt this one! |
|
||||||||||||||||||||||||||||||
|
RPM 3 |
RPM |
|
Engine crankshaft revolutions per minute. |
|
||||||||||||||||||||||||||||||
|
Sample 1 |
Sample No. |
|
For FM Link and Link Plus this is the sample number straight from the data log line. For Tec-2, Tec-3, and UTEC data logs this is sequence number of the line in the data log. |
|
||||||||||||||||||||||||||||||
|
Secs 63 |
Seconds |
|
The time in seconds into the data log. For FM Link and Link Plus data logs generated from PCLink version before 2.4, this is the sample number read from the data log multiplied by the data log line frequency. For Tec-2, Tec-3, and Link Plus data logs generated from PCLink version 2.4, this is read directly from the data log. For UTEC data logs, if the data log format contains the time it will be read directly, else it will be calculated assuming a line frequency of 5 Hz. |
|
||||||||||||||||||||||||||||||
|
SIA 61 |
Secondary
Ignition Advance |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Speed 24 |
Speed |
|
Speed of the car. For FM Link ECUs this data item is only populated on pre-air temperature correction 1.8 Links. |
|
||||||||||||||||||||||||||||||
|
TDUTY 52 |
Aux
Injector % |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Throttle 15 |
Throttle
Switch |
|
Indicates the position of the throttle switch: Idle, WOT, None. |
|
||||||||||||||||||||||||||||||
|
Torque 46 |
Torque |
|
This is the instantaneous torque being produced. This data item is not populated when a data log is loaded, but from within a Power Graph window once it has been calculated using its Tools menu. The units of the data item are the units that were chosen within the Power Graph. |
|
||||||||||||||||||||||||||||||
|
TPS 17 |
Throttle
Position Sensor |
|
Throttle position sensor output. |
|
||||||||||||||||||||||||||||||
|
TPS D 80 |
TPS
Digital |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
TPWON 53 |
Aux
Injector On Width |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
TPWOFF 54 |
Aux
Injector Off Width |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Tumble 68 |
Tumble
Generator On |
|
Read directly from the data log. |
|
||||||||||||||||||||||||||||||
|
Vacuum 38 |
Vacuum
(in Hg) |
|
When manifold air pressure is below ambient atmospheric, this data item will contain the amount below, converted to inches or Mercury. Ambient air pressure will be read from the Default Atmospheric Pressure application setting if it is not read in from the data log. For UTEC data logs, this may be read in from the data log directly. |
|
||||||||||||||||||||||||||||||
|
Volt 22 |
System
Voltage |
|
Car system voltage. |
|
||||||||||||||||||||||||||||||
|
WGCM 9 |
Wastegate
Control Mode |
|
Wastegate control mode: N/A, Closed, Open |
|
||||||||||||||||||||||||||||||
|
WG% 10 |
Wastegate
% |
|
The duty cycle of the solenoid controlling the turbo waste gate as a percentage of its total capacity. For UTEC data logs this is a percentage calculated from the “BOOST (OL)” column, rather than the value in the column. |
|
||||||||||||||||||||||||||||||
|
Zone 64 |
Zone
Number |
|
For FM Link this is calculated. For Link Plus this is read directly from the data log. |
|
Data Log Lab can support almost any ECU data log format using its unique Universal Data Log loading feature. This feature only needs a simple definition file to be created and loaded into the application, and then data logs of that format can be loaded and analysed. Data Log Lab currently ships will definition files that cover the following ECUs and software:
· All Nissan cars with Consult ports via Nissan Datascan software (http://home.iprimus.com.au/tkolo/datascan.htm).
· Apexi Power FC via FC-DataLogIt software (http://www.fc-datalogit.co.nz/).
· GEMs Mitsubushi Evo ECUs via their own DLOG99 software (http://www.gems.co.uk/)
· Hydra Nemesis (http://www.hydraems.com/)
· Innovate LM-1 and LMA-3 via LogWorks software (http://www.innovatemotorsports.com/products.php)
· Xede (http://www.xede.com.au/)
· Zeitronix ZT-2 Wideband AFR Meter via its own data logging software (http://www.zeitronix.com/)
The definition files for each of these ECUs can be tweaked or copied as a starting point for creating a new definition file. If the application has been installed to the default location, the definition files can be found here:
C:\Program Files\DataLogLab\Universal Data Log Formats\
Before we get into the nitty-gritty of how to create your own definition files, some basic information about the concepts needs to be explained.
1. Data Log Lab has a number of “pigeon holes” (currently 83) that the contents of data log columns can be placed into. Associated to each of these is a name, description and a collection of properties describing how it appears in the data log, and how it is to be displayed within Data Log Lab.
2. The standard set of “pigeon holes” covers most of the types of information normally contained in a car ECU data log, but also some quite specific ones used by the standard set of hard-coded data log formats that Data Log Lab supports (FM Link, Tec-2, UTEC, etc.)
3. When creating a Data Log Definition file, we are giving some information in general about the data log, then describing what columns are in the data log and their format, in which “pigeon hole” in the application we want to store the data and in what format, and how we want the application to display that information. Some basic pieces of information for each data log column are:
· The title of the column in the data log
· How many decimal places it has in the data log
· The ID of the “pigeon hole” in which to place the column value
· The name of the column to be displayed in Data Log Lab
· The description of the column to be displayed in Data Log Lab
· How many decimal places to display in Data Log Lab
· Whether the data needs to be scaled up or down to better fit on Data Log Lab’s Sample Graph (e.g. RPM is typically divided by 100 for display, and lambda value multiplied by 100 for display).
4. A data log does not have to contain all of the columns that are specified within the Data Log Definition, though the data log must contain a time stamp if the Data Log Definition does not have a set frequency of samples (LineFrequency parameter explained below).
5. The Data Log Definition file is a plain text file that can easily be created in Notepad, Word, etc. If using a word processor to create the file, be sure to save the file in a “plain text” format with a “.txt” file extension.
6. Data logs must also be in a plain text format, i.e. can be loaded and viewed in a simple text editor such as Notepad. If you load your data log in to Notepad and all you see is strange characters, then the data log is most likely in a binary format and Data Log Lab will not be able to deal with it. Under these circumstances, you may find that your ECU software allows you to save or export the data logs into a plain text format, such as CSV (Comma Separated Variable) typically for use with a spreadsheet such as Microsoft Excel.
7. Look at the example Data Log Definition files in the directory C:\Program Files\DataLogLab\Universal Data Log Formats\ (if you installed the application to its default location).
The Data Log Definition starts with a section that lists the overall properties of the data log file, and then has a section for each of the data log’s columns that describes the columns’ properties:
[DataLogDefinition]
(Overall data log details)
[Column]
(Properties of first column)
[Column]
(Properties of second column)
[Column]
(Properties of third column)
[Column]
…
For our explanation of the Data Log Definition file contents we will use the following snippet of data log as an example:
Super
ECU v1.2
Time
,Coolant,AFR (:1),Engine,...
Stamp,Temp ,
,Speed ,...
0,
90, 14.8, 900,...
1000,
91, 14.9, 850,...
2000,
91, 15, 700,...
...
If we look at the details of a typical general information section:
[DataLogDefinition]
Name=Hydra Nemesis 2.1 (MX-5 Miata)
Version=1.00
Comments=For Hydra software v2.16
FileExtension=csv
FileIDTextLinesBefore=0
FileIDTextColumnsBefore=0
FileIDText=Super ECU
ColumnHeadersLinesBefore=2
DataLinesBefore=4
DelimiterAsciiCharacter=44
LineFrequency=10
This section (and hence the definition file) starts with the Data Log Definition Header: [DataLogDefinition]. The parameters below are explained below in the context of the example data log in the Introduction section above.
|
Parameter Name |
Mandatory |
Explanation |
|
Name |
Y |
This is the name or description of the data logs that the definition covers. It will be seen in Data Log Lab in the File Type field of the File Open window reached from the main Sample Graph. |
|
Version |
|
This parameter is used to specify a version number against the Data Log Definition. This information is displayed in the application’s About window. |
|
Comments |
|
This parameter is used to add any comments about the Data Log Definition. This information is displayed in the application’s About window. The value of the parameter must not contain formatting or control characters, e.g. carriage returns. |
|
FileExtension |
Y |
This is the file extension of the data log files. It must be a valid file system file extension, i.e. can’t contain many of the symbol characters. |
|
FileIDText |
|
This is some text that always appears in a fixed place within your data log that can be used to identify it. It acts as a double-check that you haven’t just tried to load the wrong type of file. It’s typically the first column header, if that column is always present, but can be some text that always appears. In the above example we can use the text “Super ECU”. It’s best not to include the version number, as when you upgrade the ECU or its software you’d need to alter the Data Log Definition file. |
|
FileIDTextLinesBefore |
|
This is the number of lines that must be skipped from the start of the data log before the line is reached that the FileIDText is on. In the above example, because the ID text is on the very first line, we don’t have to skip any, so this parameter can be set to “0”. |
|
FileIDTextColumnsBefore |
|
This is the number of columns that must be skipped on the line that contains the FileIDText before the text is reached. In the above example, because the ID text starts from the very first text position, this parameter can be set to “0”. |
|
ColumnHeadersLinesBefore |
|
This is the number of lines that must be skipped from the start of the data log before the line that contains the column headings is reached. Note that the Universal Data Log Loader only checks a single line of the data log for column headers, so if you have column headers that are spread over several consecutive lines, you need to identify the single header line that enables each column to be uniquely identified. In the above example, the first line of column headers is the one that uniquely identifies the columns, so this parameter is set to “2”. |
|
DataLinesBefore |
|
This is the number of lines that must be skipped from the start of the data log before the first line of data in the data log is reached, so in the example data log above, this parameter would be set to “4”. |
|
DelimiterAsciiCharacter |
Y |
This is standard ASCII number of the character that separates the columns in the data log. This will most likely be a comma (44), or a tab (9). In the above example it’s a comma, so this parameter is set to “44”. |
|
LineFrequency |
|
For data logs that don’t have a time stamp column, this is the number of lines that are recorded in the data log each second. Either this parameter must be set, or a time stamp column must be later defined (column associated to Data Log Lab Data Item 63). This parameter can be set to a value with decimal places, e.g. “20.56”. In the above example, we have a time stamp column and hence this parameter does not need to be set. |
|
AutoGearSpeedFactor |
|
This is used in conjunction with Power Graph’s auto gear selection feature. The value put against this parameter is used by the application to convert the speed information in the data log from its own units to meters per second, for use by the auto gear selection feature when a data log of the type the definition file describes, is loaded. Some common values for this field is: Miles per hour to meters per second: 0.44704 Kilometres per hour to meters per second: 0.27778 Note that when this parameter is set, for data logs loaded using it, the auto gear selection feature will use the parameters value in place of the conversion factor settings specified in the Options window. |
Now let’s look at the details of a typical Column Definition section.
[Column]
Name=C Temp
Description=Coolant Temp (C)
ColumnTitle=coolant
DataItemID=23
Type=1
ColumnDecimalPlaces=0
DisplayDecimalPlaces=0
DisplayFactor=1
Each Column Definition Section starts the header: [Column]. The example above deals with the Coolant Temperature column of the example data log in the Introduction section:
|
Parameter Name |
Mandatory |
Explanation |
|
Name |
Y |
This is the short name to be given to the data item that the column value is to be loaded in to. The name appears throughout Data Log Lab in sample detail lists and data item drop down lists. The name should be unique. |
|
Description |
Y |
This is the long name to be given to the data item that column value is to be loaded in to. This is seen in various places within Data Log Lab. |
|
ColumnTitle |
Y |
This is the unique column title as it appears in the data log, and is used by Data Log Lab to identify the column. Where the data log column titles are spread over more than one line (like the example data log in the Introduction section), this property should only contain the portion of the column title on the line specified in the ColumnHeaderLinesBefore property in the Data Log General Information section of the Data Log Definition. For the example data log, this just wants to be the text “coolant”. This property is NOT case sensitive. |
|
DataItemID |
Y |
This is the numeric ID of the Data Item that the data log column value is going to be put into – see section the Data Item Explanation section for a complete list of the Data Items and their default use and properties. It’s always best to find a Data Item that has the same default use as the data log column (i.e. associate the RPM column in the data log with the standard RPM Data Item in Data Log Lab), but because all properties of the Data Item can be configured this is not strictly necessary. The main advantage of associating the data log column to an existing Data Item is gaining re-use of existing Preset Sample Graph and Preset Scatter Graph definitions. For example, a preset graph of RPM against A/F ratio will continue to show those two parameters for your new data log, rather than show, for example, Boost against Throttle Position because that’s what you’re now putting into the RPM and A/F Data Items. |
|
Type |
Y |
1 = Numeric, 2 = Text List For all columns that are a number, set this to “1”. For columns that contain a set of text values, e.g. “On” and “Off”, set this to “2”. Columns with text values in them are covered in the Advanced Features section below. |
|
ColumnDecimalPlaces |
Y |
This parameter is used to indicate the number
of decimal places the column value has in the data log. There’s no problem with setting this
larger than necessary, but if you set it too small the extra decimal places
in the data log will not be seen in the application. |
|
DisplayDecimalPlaces |
|
This parameter is used to indicate the number of decimal places that will be displayed for the column in the sample detail lists within the application. If you want to see all the detail that’s in the data log, set this the same as the ColumnDecimalPlaces parameter. If you want to see less detail then reduce the value of this parameter as appropriate. If this parameter is not set, the number of display decimal places that are specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
|
DisplayFactor |
|
This parameter controls the scaling of the data item on the Sample Graph within the application. The idea is that all data items are scaled up or scaled down so that they display in roughly the same range of the Sample Graph’s Y-Axis, which is normally between 0 and 250. A value of “1” will draw a line on the Sample Graph for the data item, that can be directly read off of the scale on the left hand side of the graph. A value of “0.01” will display the line at 1/100th of the data items value (typically used for RPM so that “5000“ is displayed as “50”. A value of “100” will display the line at 100 times the data item’s value (typically used for lambda, so that “1.00” is displayed as “100”. Note that this parameter does not change how the data item is displayed in the Sample Details lists within the application, i.e. a value of “1000” will still be displayed in the Sample Details lists even if it is displayed with a factor of “0.01”. If this parameter is not set, the display factor that is specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
This section covers the more advanced features of the Universal Data Log loader. Firstly a list of more advanced facts:
1. Some Data Items (indicated by a “Y” against their “Mandatory” parameter in the Data Item Explanation section) will always be available within Data Log lab even if you don’t have them in your Data Log Definition. This is because these are calculated through various operations within the application. If you do include them in your Data Log Definition, their values loaded from the data log will be overwritten by those same operations within the application, when they are performed.
2. Look in the C:\Program Files\DataLogLab\Universal Data Log Formats\Example Columns\ directory (assuming you installed the application to its default location) for some examples of the conversion of column values as they are loaded.
This scenario is typically used where you have a Data Log Definition that wants to cover more than one data log format, and there are slight differences in column titles between the different formats. Here you put many Column Definitions in the Data Log Definition that populate the same DataItemID but each has a different ColumnTitle specified. If the data log you load contains either column, the Data Item will be populated. If the data log contains both columns, as the columns are processed by the application from left to right (as they appear in the data log), the right most column’s values will be the ones left in the Data Item.
Remember that a data log does not have to contain all of the columns specified in the Data Log Definition, though the data log must contain a time stamp if the Data Log Definition does not have a set frequency of samples (LineFrequency parameter).
An important note about populating the same Data Item from more than one column in the data log is that in the data log definition file, the column parameters affecting the Data Item must be consistent across each column definition that populates it, i.e. they must have the same DisplayDecimalPlaces, same Offset, same DisplayFactor, etc., else results may be not what you’re looking for. The display properties of the last column in the data log definition that populates the Data Item will determine how it appears in Data Log Lab.
This scenario is typically used where you have e.g. a “Boost” column and you want to populate “Boost” and “Manifold Air Pressure” data item, or if you want to have several versions of a column each converted to different units of measurement. Simply create a column definition for each Data Item you want to populate, all having the same ColumnTitle parameter setting.
This type of Column Definition allows you to display text format columns in your data log within Data Log Lab as the original text values, i.e. if you have a column in your data log that contains the text “On” and “Off”, you can then see the text “On” and “Off” in the Sample Details list within Data Log Lab.
Here’s an example of a column definition for a text list column:
[Column]
Name=Neut Sw
Description=Neutral
ColumnTitle=Neutral
DataItemID=18
Type=2
ColumnDecimalPlaces=0
Offset=0
DisplayColour=180000
DisplayLineWidth=3
DisplayLineStyle=1
[Values]
Off
On
The text values that can appear in the column are listed under a header of [Values] after the rest of the column parameters. Unlike the rest of the parameters, this is a straight list of text values without any equals signs.
This column can still be plotted on Sample Graphs and Scatter Graphs as each text value is given a numerical value within Data Log Lab based on its sequence number in the list under the [Values] header, so in the above example “Off” is given a value of “1”, and “On” is given a value of “2”. This in turn means that all the display formatting parameters under the Column Definition can be used to control exactly how the column appears on the Sample Graph. It’s worth noting that although you can list as many text strings as you want under the [Values] header, this is likely to be a small number and so you’ll need a high DisplayFactor parameter setting on the column to accurately see the different values on the Sample Graph.
|
Parameter Name |
Mandatory |
Explanation |
||||||||||||||||||||
|
Offset |
|
This parameter enables Data Log Lab to deal with negative numbers. Data Log Lab’s Sample Graph can’t display negative numbers, and so data items that cover a positive and negative range are given a positive offset to move them up the Y-Axis scale so that they never drop below zero. This offset typically positions zero at the “100”, so that negative numbers appear less than “100” and positive more than “100”. Note that the Offset is expressed in the original units of the column, so that if your column range covers –1000 to +1000 and hence you have a DisplayFactor of “0.1”, your Offset will be “1000” to reach the 100 line on the Y-Axis. Note that this parameter does not change how the data item is displayed in the Sample Details lists within the application, i.e. a negative value will still be displayed in the Sample Details lists. If this parameter is not set, the Offset that is specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
||||||||||||||||||||
|
DisplayZero |
|
This parameter effects how column values of zero are displayed in the Sample Details list within the application. If this is set to “N”, then rather than “0” before displayed, the Sample Details list will display nothing for data item. If this parameter is not set, the Display Zero setting that is specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
||||||||||||||||||||
|
DisplayColour |
|
This parameter affects the default colour of the Data Item’s line in the application’s Sample Graph. It is a number between 0 and 16,777,216 that represents a 24-bit RGB colour in standard format. Hint: to find out the number that represents your favourite colour, set the colour of a Data Item using the Data Item Definitions tab of the Options window, and then exit Data Log Lab. If you then look in the Data Log Lab configuration file (C:\Program Files\DataLogLab\Program\DataLogLab.ini for an installation to the default location), and then look by the ID of the data item you set under the “[Data Item Display Properties]” section, you’ll set the number that represents your colour in the “Item n Colour=” line. If this parameter is not set, the Display Colour that is specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
||||||||||||||||||||
|
DisplayLineWidth |
|
This parameter affects the thickness of the Data Item’s line in the application’s Sample Graph. It is a number from 1 to 5 relating to the Line Width field in the Data Item Definitions tab of the Options window in the following way: 1 Thinnest 2 Thinner 3 Medium 4 Thicker 5 Thickest If this parameter is not set, the Display Line Width that is specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
||||||||||||||||||||
|
DisplayLineStyle |
|
This parameter affects the pattern of the Data Item’s line in the application’s Sample Graph. It is a number from 1 to 3 relating to the Line Style field in the Data Item Definitions tab of the Options window in the following way: 1 Solid 2 Dotted 3 Dashed If this parameter is not set, the Display Line Style that is specified in the Data Item’s internal definition will be used instead, see the Data Item Explanation section for each Data Item’s characteristics. |
||||||||||||||||||||
|
ColumnMinimumValue |
|
This parameter can be used to constrain the values read in from the data log. If this parameter is set, when the value of the column in the data log drops below it, the parameter value will be used instead. This has the effect of supplying a minimum value that the Data Item in the application will never drop below, regardless of what is in the data log. This might typically be used where there are glitches in the data log that have values that are wildly different from typical, and hence their display will mess up the presentation of Data Log Lab graphs unacceptably. |
||||||||||||||||||||
|
ColumnMaximumValue |
|
This parameter can be used to constrain the values read in from the data log. If this parameter is set, when the value of the column in the data log rises above it, the parameter value will be used instead. This has the effect of supplying a maximum value that the data item in the application will never rise above, regardless of what is in the data log. This might typically be used where there are glitches in the data log that have values that are wildly different from typical, and hence their display will mess up the presentation of Data Log Lab graphs unacceptably. |
||||||||||||||||||||
|
ConversionFactor |
|
This parameter allows a column value to be multiplied by an amount as it is loaded into Data Log Lab, and might typically be used to convert it from one unit to another. Set the parameter to value less than “1” to perform a division, e.g to divide by 2, multiply by 0.5. |
||||||||||||||||||||
|
ConversionOffset |
|
This parameter allows an amount to be added or subtracted from a column value as it is loaded into Data Log Lab, and might typically be used to convert it from one unit to another. Set the parameter to a negative value to subtract rather than add. |
||||||||||||||||||||
|
ConversionFactorFirst |
|
This parameter allows control over which of the ConversionFactor and ConversionOffset parameters is allowed to process the column value first. If this parameter is set to “Y”, the column value will first be multiplied by the Conversion Factor before it then has the ConversionOffset added to it. If this parameter is set to “N”, the column value will first have the ConversionOffset added to it before being multiplied by the ConversionFactor. |
||||||||||||||||||||
|
AllowSetToMinimumValue |
|
This parameter is closely associated to the ColumnMinimumValue parameter. By setting this to “Y”, if the column value drops below the minimum value, the data item value will not be updated but left at whatever value it currently is. |
||||||||||||||||||||
|
AllowSetToMaximumValue |
|
This parameter is closely associated to the ColumnMaximumValue parameter. By setting this to “Y”, if the column value rises above the maximum value, the data item value will not be updated but left at whatever value it currently is. |
||||||||||||||||||||
|
ConversionType |
|
This allows you to apply a predefined conversion to a column as it is loaded. The values for the parameter are:
|
||||||||||||||||||||
|
Smooth |
|
This parameter is used to artificially smooth Data Item values between their changes, and is typically used with the ConversionType parameter above to generate fractions of a second on truncated time stamps, or can be used to try to smooth column where the values appear very stepped. After a data log has been loaded, the application will pass through the data of all columns with this parameter set to “Y”, and interpolate between points where the data item value changes, e.g.:
|
Your Data Log Definition file can contain Preset Sample Graph Definitions after the Column Definitions. These Preset Sample Graph Definitions will be loaded when the whole definition file is loaded, and added to those shown in the Preset Sample Graph List of the Sample Graph window when one of your data logs is loaded. The definition looks similar to the contents of a Preset Sample Graph file created through the Save button of the Preset Sample Graph Details window:
[Sample
Graph]
Name=A/F Investigation
Data Items=7,23,21,13,14,5,3,24,17,55,36
Fix Graph Max=N
Graph Max=10
Each Preset Sample Graph Definition section
starts the header [Sample
Graph] and
then continues with the following parameters:
|
Parameter Name |
Mandatory |
Explanation |
|
Name |
Y |
The name of the Preset Sample Graph. |
|
Data Items |
Y |
A comma separated list of the Data Items that are to be checked for the Preset Sample Graph. |
|
Fix Graph Max |
Y |
Set to “Y” if you want the vertical scale of the Sample Graph to be fixed for the Preset Sample Graph. |
|
Graph Max |
Y |
If you have set the Fix Graph Max parameter to “Y”, the highest number that you want the vertical scale on the Sample Graph to reach. The value you enter here may be adjusted by the application so that it can make a sensible vertical scale with a useful number of divisions. If data is graphed that is higher in value than the number specified as the vertical scale maximum, it will not be seen. If Fix Graph Max is set to “N”, this field does still need to be supplied but its value is not important. The recommendation under these circumstances is to set it to “200”. |
You
can have as many Preset Sample Graphs in your Data Log Definition as you want.
Your Data Log Definition file can contain Preset Scatter Graph Definitions after the Preset Sample Graph Definitions, or directly after the Column Definitions if you have no Preset Sample Graph Definitions. These Preset Scatter Graph Definitions will be loaded when the whole definition file is loaded, and added to those shown in the Preset Scatter Graph List of the Scatter Graph window when one of your data logs is loaded. The definition looks similar to the contents of a Preset Scatter Graph file created through the Save button of the Preset Scatter Graph Details window:
[Scatter
Graph]
Name=Lambda Idle
Point Colour=550000
Point Shape=8
Point Size=6
X Axis=3
Y Axis=55
File Open Draw=N
[Filter]
Data Item=5
From=
To=60
[Filter]
Data Item=3
From=
To=1200
Each Preset Scatter Graph Definition section
starts with the header [Scatter Graph] and then continues with the following parameters:
|
Parameter Name |
Mandatory |
Explanation |
|
Name |
Y |
The name of the Preset Scatter Graph. |
|
Point Size |
Y |
The size of the points plotted on the Scatter Graph, from “1” to “10”. |
|
X Axis |
Y |
The ID of the Data Item that is plotted on the X Axis. |
|
Y Axis |
Y |
The ID of the Data Item that is plotted on the Y Axis. |
|
File Open Draw |
Y |
See the definition of the File Open Draw checkbox in the Preset Scatter Graph Details window. |
|
Point Colour |
|
This parameter affects the colour of the points plotted on the Scatter Graph. It is a number between 0 and 16,777,216 that represents a 24-bit RGB colour in standard format. Hint: to find out the number that represents your favourite colour, create a Preset Scatter Graph with the point colour set how you like it, and then save the Preset Graph from the Preset Scatter Graph Details window. Open the file you’ve just saved in a text editor or word processor, and look for the line “Graph 1 Point Colour=”. The number to the right of this is the 24-bit RGB colour number. |
|
Point Shape |
|
The shape of the points plotted on the Scatter Graph: 0 3D Ball 1 Circle 2 Dash 3 Diamond 4 Down triangle 5 Plus 6 Square 7 Star 8 Up Triangle 9 X |
After
the main Preset Scatter Graph Parameters are the filters of the Scatter
Graph. Each Filter Definition section
starts with the header [Filter] and then continues with the following
parameters:
|
Parameter Name |
Mandatory |
Explanation |
|
Data Item |
Y |
The ID of the Data Item that the Filter is being applied to. |
|
From |
Y |
The starting value of the range the Filter covers. This parameter does not have to be set to a value (when the filter range is has no start), but at least one of the From and To parameters does need to be set. For a Data Item that is populated by a Column Definition of Type 2 (Text List), this field is set to the sequence number of the text value in the list after the [Values] header of the column definition. |
|
To |
Y |
The finishing value of the range the Filter covers. This parameter does not have to be set to a value (where the filter range is open ended), but at least one of the From and To parameters does need to be set. For a Data Item that is populated by a Column Definition of Type 2 (Text List), this field must not be set. |
You
can have as many Filters in your Preset Scatter Graph Definition as you want, and
as many Preset Scatter Graph Definitions in your Data Log Definition as you
want.
The first step of testing your Data Log Definition file is to confirm that it loads successfully. The easiest way of doing this is by using the Load button associated to the Universal Data Log Definition File field in the Options window. Set the field value to the path and file name of your definition file and then hit the Load button. You’ll either get an error message about the first problem encountered, or a message saying that the definition file was loaded successfully. If you get an error message, fix the problem, save the definition file, and then try loading it again. Repeat until all loading errors are resolved. The next step is to check that each column is loading and displaying as planned by loading one of your data logs, and confirming any Preset Sample Graphs or Preset Scatter Graphs in your definition file are performing as planned.
Note that all error messages give a context in their text, e.g. the name of the Column Definition that is causing the problem.
|
Error Message |
Likely Cause |
|
Error loading data log definition - column data incomplete |
A Column Definition does not contain all mandatory parameters: Name Description ColumnTitle DataItemID Type ColumnDecimalPlaces |
|
Error loading data log definition - column definitions not found |
A line exists within a Column Definition that the loader does not recognise as a standard parameter or header. |
|
Error loading data log definition - column minimum and maximum values to not form a valid range |
A Column Definition has ColumnMinimumValue and ColumnMaximumValue parameters set, but they do not form a valid range (ColumnMinimumValue is greater than ColumnMaximumValue). |
|
Error loading data log definition - column type does not allow values but definition contains them |
A Column Definition Type parameter is set to “1”, but the column definition contains a section for text lists ([Values]). |
|
Error loading data log definition - column type does not match data item type |
Within a Column Definition a reserved Data Item ID has been specified but the Type column does not match it. The following Data Items IDs must be defined as Type 1 if they are used within a Column Definition: 3, 23, 24, 31, 45, 46, 63. |
|
Error loading data log definition - data item cannot be used |
A Column Definition DataItemID parameter is set to a data item that cannot be used. |
|
Error loading data log definition - data item not found |
A Column Definition DataItemID parameter is set to a data item that does not exist. Only “2” to “83” can be used. |
|
Error loading data log definition - file not found |
The Data Log Definition file specified in the Universal Data Log Definition File field in the Options window cannot be found. |
|
Error loading data log definition - header definition not found |
The Data Log Definition file does not start with the standard header: [DataLogDefinition] |
|
Error loading data log definition - invalid column attribute |
A line exists within a Column Definition that the loader does not recognise as a standard parameter or header. |
|
Error loading data log definition - invalid definition name |
The Data Log Definition Name parameter is set to an invalid value. |
|
Error loading data log definition - invalid file extension |
The Data Log Definition FileExtension parameter is set to an invalid value. |
|
Error loading data log definition - invalid header attribute |
A line exists within a Column Definition that the loader does not recognise as a standard parameter or header. |
|
Error loading data log definition - missing mandatory header data |
The Data Log Definition file does not contain all mandatory parameters: Name FileExtension DelimiterAsciiCharacter |
|
Error loading data log definition - no column values in definition |
A Column Definition Type parameter is set to “2” (text list), but the column definition does not contains a section for the text list values ([Values]). |
|
Error loading data log definition - no time column or line frequency |
The Data Log Definition does not have a LineFrequency parameter and there is not a time stamp column defined. One of these two must be supplied. |
|
Error loading data log definition - preset sample graph data item not in data log definition |
A Preset Sample Graph Definition has a Data item specified in its Data Items parameter that is not populated by any of the Column Definitions in the Data Log Definition. |
|
Error loading data log definition - preset sample graph definition incorrect |
A Preset Sample Graph Definition does not have its Name parameter set. |
|
Error loading data log definition - preset scatter graph definition incorrect |
A Preset Scatter Graph Definition does not have its mandatory parameters set: Name Point Size X Axis Y Axis |
|
Error loading data log definition - preset scatter graph filter definition incorrect |
A Filter Definition of a Preset Scatter Graph Definition does not have its mandatory parameters set: Data Item To or From |
|
Error loading data log definition - preset scatter graph filter data item not in data log definition |
A Filter of a Preset Scatter Graph Definition specifies a Data Item that is not populated by any of the Column Definitions in the Data Log Definition. |
|
Error loading data log definition - preset scatter graph filter from value not in data item value list |
A Filter of a Preset Scatter Graph Definition has its Data Item parameter set to a Column of Type = 2 (Text List), but the Filter From parameter does not match any of the Value entries against the column Definition. |
|
Error loading data log definition - preset scatter graph X-axis data item not in data log definition |
A Preset Scatter Graph Definition has its X Axis parameter set to a Data Item that is not populated by any of the Column Definitions in the Data Log Definition. |
|
Error loading data log definition - preset scatter graph Y-axis data item not in data log definition |
A Preset Scatter Graph Definition has its Y Axis parameter set to a Data Item that is not populated by any of the Column Definitions in the Data Log Definition. |
|
Question |
Answer |
|
There’s so many data items in the list on Sample Graph and Scatter Graph it’s difficult to see the wood for the trees – how can I reduce the number? |
Go to Data Items Definitions tab of the Options window, set the Licence Type field to the data log format you use, and then go down the list of Data Items and uncheck any that you know you’re not interested in. Click OK to close the Options Window. Your Sample Graph will now be updated with your revised data item list. Secondly, make use of the Checked Data Items Only checkbox on the Sample Graph. This will reduce the data item list even further to show only those that were plotted on the last graph. |
|
How do I quickly find a power run in my huge data log I was recording all the way to work? |
1. Load the data log. 2. On the Sample Graph, click the “Overview” preset graph and then the “Draw” button. 3. You are now looking at your entire data log from start to end. The areas of maximum boost will be seen by the peaks in the MAP line on the graph. Click the peak that you’re after. 4. Right-click the graph and select Goto Sample. 5. Ensure that User Show Point Width is checked and then click OK. 6. Bingo! You’re looking in detail at the area of interest in your data log! 7. You can now make a temporary data tag of the area by right-clicking and selecting “New Data Tag”, and you’ll be able to return to it quickly. |
|
Can I load more than one data log at a time? |
No…but you can run the application more than once at the same time thereby enabling you to peruse more than one data log simultaneously. |
|
Can I use Data Log Lab to produce 0-60 and 0-100 timings? |
Yes! Let's look at the 0-60 example: The theory is that you start data logging, hold your revs at say 4k for a couple of seconds to get a reference point, and then go for it! The rise in MAP/TPS should indicate the point at which the clutch began to engage. You then plot a Power Graph of the complete 0-60 run, calculated in the gear in which you reach 60mph (e.g. 2nd), and then plot a Speed Graph to see how long it took to arrive there. The Power Graph will look completely nuts, and the beginning of the Speed Graph will read high, but the end of the Speed Graph will be accurate and can be used to read off the time. The same theory applies to a 0-100 time, except the Power Graph would need to be calculated in, e.g. 4th gear. |
Just in case you feel the urge to launch Data Log Lab from another application or the command line prompt, you can append the name of a data log or MAP file to automatically load, e.g.:
“C:\Program Files\DataLogLab\Program\DataLogLab.exe” C:\Temp\Miata.txt
Once the application’s splash screen has been confirmed it will load the file, and if that file is a valid data log, check the Quick Graph check box and go on to draw a Sample Graph.
This functionality also means that you can drag and drop data logs and MAP files on to the application’s desktop icon.
For if Data Log Lab cannot decipher the file format of the data log you’d like it to load, you can append a pipe symbol and number from the list below to tell Data Log Lab what the file type is:
1 FM Link Data Log
2 FM Link MAP File
3 Tec-2 Data
4 Tec-3 Data Log
5 LinkPlus Data Log
6 UTEC CSV Data Log
7 UTEC Fixed-Width Data Log
The application offers the ability to apply a conversion file to the auxiliary input voltage data logged from the Link. Normally the auxiliary input is unused on a 1.6 and controlling the EGR on a 1.8. If you decide to fit a wide band O2 sensor or exhaust gas temperature gauge (for instance), the auxiliary input can be used to data log the device’s output.
A conversion file needs to be set up for the application to use to translate the 0-5 volt input into something meaningful, e.g. an A/F ratio, lambda value, or EGT. The application ships with conversion files specifically for AEM, DIY and FJO type wide band oxygen sensors for a variety of fuels. These can be found in the directory “C:\Program Files\DataLogLab\Conversion Tables” on a normal installation. The application has the AEM figures built in for default use.
To create your own conversion table we recommend taking one of these, copying it to a new file name, and then adapting it to suit. The format of these files is very specific: a header line and then detail lines that relate an input voltage to a display number. The first few lines of a file might look like this:
Data
Log Lab Aux Input Conversion Table
0=8500
156=8710
312=8940
468=9150
624=9390
780=9600
936=9790
1092=10010
On
the left of each “=” is the auxiliary input voltage in millivolts (1000th
of a volt), i.e. “1250” means 1.250 volts.
On the right of the “=” is the value this converts to. This value will be plotted on the Sample
Graph divided by 100, and displayed in the Sample Details List
divided by 1000, i.e. “16700” would be plotted as “167.0” and seen in the Sample
Detail Window as “16.70”.
The
file must contain the header line and then the detail lines in increasing
voltage. The number of detail lines is
up to you – the application will interpolate between them if the voltage in the
data log line is not an exact value in the conversion file. If a conversion file you create is invalid,
the application will report an error when trying to load it, and then use a
default of the “AEM WBO2” conversion file instead.
The
conversion file that the application uses is set in the File
Locations tab of the Options Window. This file is only used when a data log is
loaded; so changing its value will not affect the currently loaded data log.
The
application ships with conversion files for a variety of different wide band
units and a variety of fuels. Each
country’s fuel mix has a slightly different stoich air fuel ratio, e.g. in the
US it’s 14.7:1, UK “normal” unleaded is 14.2:1 and UK “super” unleaded is
14.4:1. All oxygen sensors actually
output a voltage related to lambda rather than A/F ratio, with the A/F ratio
figure being derived from the lambda figure.
So with UK and US unleaded fuel, the sensor will output the same voltage
when complete combustion occurs (stoich) corresponding to lambda = 1, but in
the US the A/F ratio is 14.7:1 and in the UK the A/F ratio is 14.2:1. The A/F ratio at any other lambda value is
calculated by multiplying the stoich A/F ratio by the lambda value. So, taking our illustration further, when
lambda = 0.8, in the US the A/F ratio is 14.7 x 0.8 = 11.76:1, but in the UK
the A/F ratio is 14.2 x 0.8 = 11.36:1.
When
aiming for a specific A/F target under boost we’re really over-fuelling to cool
the charge temperature. The cooling
effect is actually related to the lambda value rather than A/F ratio, so if in
the US we’re aiming for 11.0:1, this corresponds to a lambda value of
0.75. For the same cooling effect in
the UK, we have an A/F target of 14.2 * 0.75 = 10.65.
All
OEM ECUs work exclusively with lambda values rather than A/F ratios as these
remain constant across fuel mixes.
For
best use of the A/F Target data item and resolution of auto tuning targets in
the Zone Data Editor, be sure to have the auxiliary input conversion file and
the narrow band oxygen sensor conversion file in the same units, i.e. both
lambda or both A/F ratio, and if A/F ratio both to be based on the same stoich
A/F ratio.
A
conversion file can be set up to convert the linearised output from the narrow
band oxygen sensor to something a little friendlier, e.g. lambda value or air
fuel ratio. The application ships with
conversion files for lambda and various worldwide fuels. These can be found in the directory
“C:\Program Files\DataLogLab\NB O2 Conversion Tables” on a normal
installation. The application has
historical figures built in based on US fuel with a stoich air fuel ratio of
14.7:1, though these have since proved inaccurate so we recommend you populate
the Narrow
Band Oxygen Sensor Conversion File field in the Options window with one of the
shipped files for greater accuracy.
To create your own conversion file we recommend taking one of the shipped ones, copying it to a new file name, and then adapting it to suit. The format of these files is very specific: a header line and then detail lines that relate a linearised O2 (O2 data item) value to a display number. The first few lines of a file might look like this:
Data
Log Lab Conversion Table
20=22190
35=20233
47=18668
56=17493
64=16449
70=15667
72=15406
73=15276
74=15145
On
the left of each “=” is the linearised O2 data item value. On the right of the “=” is the value this
converts to. This value will be plotted
on the Sample Graph divided by 100, and displayed in the Sample
Details List divided by 1000, i.e. “16700” would be plotted as “167.0” and
seen in the Sample Detail Window as “16.70”.
The
file must contain the header line and then the detail lines in increasing
linearised O2 value. The number of
detail lines is up to you, but unlike the auxiliary input conversion file, the
entries in this table are not interpolated between, but the closest entry
picked instead. The shipped files
contain every linearised O2 value a FM Link data log can contain (this is not a
continuous count as there are only thirty four covering the range “20” through
“126”), so these are best used as a starting point when creating your own. If a conversion file you create is invalid,
the application will report an error when trying to load it, and then use a
default of historical data mentioned above instead.
The
application ships with conversion files for a variety of different fuel
mixes. Each country’s fuel mix has a
slightly different stoich air fuel ratio, e.g. in the US it’s 14.7:1, UK
“normal” unleaded is 14.2:1 and UK “super” unleaded is 14.4:1. All oxygen sensors actually output a voltage
related to lambda rather than A/F ratio, with the A/F ratio figure being
derived from the lambda figure. So with
UK and US unleaded fuel, the sensor will output the same voltage when complete
combustion occurs (stoich) corresponding to lambda = 1, but in the US the A/F
ratio is 14.7:1 and in the UK the A/F ratio is 14.2:1. The A/F ratio at any other lambda value is
calculated by multiplying the stoich A/F ratio by the lambda value. So, taking our illustration further, when
lambda = 0.8, in the US the A/F ratio is 14.7 x 0.8 = 11.76:1, but in the UK
the A/F ratio is 14.2 x 0.8 = 11.36:1.
When
aiming for a specific A/F target under boost we’re really over-fuelling to cool
the charge temperature. The cooling
effect is actually related to the lambda value rather than A/F ratio, so if in
the US we’re aiming for 11.0:1, this corresponds to a lambda value of
0.75. For the same cooling effect in
the UK, we have an A/F target of 14.2 * 0.75 = 10.65.
All
OEM ECUs work exclusively with lambda values rather than A/F ratios as these
remain constant across fuel mixes.
For
best use of the A/F Target data item and resolution of auto tuning targets in
the Zone Data Editor, be sure to have the auxiliary input conversion file and
the narrow band oxygen sensor conversion file in the same units, i.e. both
lambda or both A/F ratio, and if A/F ratio both to be based on the same stoich
A/F ratio.
|
Question |
Answer |
|
My laptop doesn’t have a serial port – can I still connect it to the Link serial box? |
What you need is a USB to serial converter. Although I have no personal experience, I know that some folks have had success with these whilst others have had failure. A known “good” experience was had using an Inland Pro USB-serial converter (p/n 08303) with Windows ME on a Compaq 1215 laptop. |
|
When attempting to data log and/or upload LinkWIN opens up but just sits there neither sending nor receiving. |
I have to change the lead between my PC and the Link serial box about every six months, as they don’t seem to be able to take the constant winding and unwinding. The symptoms of this also include being able to data log but not upload…don’t understand that one personally. Billy Hodgson provided this solution to a Win 98SE problem where neither data logging or uploaded was working: Add the line “Com[n]AutoAssign=-1” to system.ini under the [386Enh] heading if it isn’t already there, where [n] is the com port number you are trying to use. |
|
When attempting to upload data to the Link ECU I sometimes encounter the following LinkWIN errors: "-2, Response to Stop/Resume log data output command timed out." Or “-7, Store command NAK'd.” What causes this? |
This error means that the computer could not establish a connection to the Link ECU. Some of the reasons this might have occurred are: The engine is not switched on. The ignition key must be in the 'engine run' position, although without the engine running! The Link is still 'booting up'. Leave a few seconds between turning the ignition on and starting the upload. You have a hardware problem with your PC to Link Serial Box, the Serial Box itself, or the ribbon cable to the Link. The easiest way of eliminating these is to find someone local who you can try swapping bits with. Failing this, I'd recommend a new PC to Link Serial Box lead next as this is the cheapest! The car is in gear or the clutch is pressed. The accelerator pedal is being pressed. The idle switch is incorrectly adjusted and not closed when your foot is off of the accelerator pedal. |
|
When I attempt to acquire a new data log I get the error message 'Unknown File System Error' - can you give me any pointers? |
With Windows NT and Windows 2000 you have to make sure that the user account you log in to run Data Log Lab has full read and write access to the Data Log Lab installation directory and its sub-directories. After OK is pressed in the New File window, Data Log Lab tries to delete any old working files in the LinkWIN and MDOS sub-directories. If your user account doesn't have permission to delete files in these directories then you'll see the error message. |
|
I have a data log from a chip with a different date to my own and I would like to upload it into my chip, however the Zone Data Editor won't enable the Upload button unless the dates are the same. How do I upload the settings? |
What you most definitely mustn't do is change your chip date in the Link ECU tab of the Options window - this absolutely must be set to the version of the chip you have installed in your car at all times! What you do instead is load the data log, go to the Zone Data Editor and change the Chip Date field in the General Information frame to that of your chip. As you do this you may notice various field prompts change or become enabled as the features available on your chip are applied to the data log. If you didn't catch which fields changed go to the on-line instructions by pressing the [F1] key, and look at the section on the General Information frame of the General tab of the Zone Data Editor, which lists the features that are available by chip date. Before uploading make sure that all the fields, particularly the ones that have had their prompts changed or become enabled, have valid settings in them. Although it's most definitely not recommended, this method also applies to uploading zone settings from a data log from a chip with a different engine size. |
|
How do I copy zone settings from one data log to another? |
The easiest way of doing this is via the Zone Data Editor Benchmark feature. 1. Temporarily add a zone data benchmark of the file which is the source of the copying. 2. Load the file that is the target of the copy. 3. Open the Zone Data Editor and set the Benchmark field to the new temporary benchmark. 4. Use the Copy button to open up the Copy Benchmark window, select the areas of zone data you want to copy, and then click OK. 5. Delete the temporary zone data benchmark if you don’t want to keep it. |
|
How do I make use of the 'InjW' series in the Sample Graph? |
The main use of this series will become apparent with the release of the air temperature correction hardware that Ray Ayala and Flyin' Miata and currently working on. From the horse's mouth: "Where the O2 data is on target (usually with the help of L3) it indicates how much fuel is required at that point, and that information is required to set up the air temperature compensation slopes". |
This question is asked a lot. Personally, I find it handy to have a keypad plugged in and sitting in the glove box when I’m not data logging, but you don’t need a keypad if you have the Data Log Lab software. A lot of the steps detailed in the set-up sections of Flyin’ Miata’s ECU installation and tuning document will certainly be significantly slower using data logging, but they can be done as all the necessary data is output in the data logs. However, there are certain steps where it may not be immediately apparent:
The equivalent of ‘IGN SETUP +10’ keypad screen is achieved by ensuring your ignition trim is set to zero and all of your ignition zones set to ‘40’ via an upload. After the base timing has been set, the original ignition zone vales can be restored by uploading the relevant default MAP shipped with the application.
This is achieved by performing a data log, adjusting the TPS Offset and TPS Scale Factor settings in the Zone Data Editor, uploading, performing a data log, repeating the process until the fields are set correctly.
Look at the TPS values logged at both idle and WOT. The goal is to get the WOT TPS to be between 98 to 102 and the idle TPS to be between 10 and 20.
· The difference between WOT and idle values should be between 80 and 90. If the difference is too low, raise TPS Scale Factor proportionately. If it's too high, reduce TPS Scale Factor proportionately. Repeat as required.
· Look at only the WOT TPS value. If it is over 102, reduce TPS Offset by the amount over 100. If TPS is under 98, increase TPS Offset by the amount below 100.
This one’s a little trickier - you won’t have the benefit of the real-time feedback the keypad offers. However, as long as Lambda and Master Fuel auto tuning are enabled and L3 auto tuning is disabled, the ECU will be auto tuning whilst you data log. When you upload these auto tune settings, ensure that the Set Auto Tune Mode field in the Upload Zone Settings window is set to ‘Coarse No Idle’ to put the ECU into the correct tuning mode.
The tuning instructions ask that you stay within a set ‘row’ and accelerate from 2k to the redline several times, and then move on to the next row. We’re going to have to use the boost gauge to work out what row you’re in:
row 200 12 inch mercury vacuum 30 cm mercury vacuum
row 300 0 inch mercury/0 PSI 0 cm mercury/0 kPa
row 400 6 PSI 140 kPa
row 500 12 PSI 180 kPa
row 600 15+ PSI 200+ kPa
The data log can be examined for the same symbols which are displayed in the keypad, and like the keypad, as your auto tuning continues you will see ‘=’ symbols rather than ‘+’ and ‘-‘ within the data log. These symbols can also be seen in the Sample Details frame of the Sample Graph as you click on the series displayed in the graph.
Each time you stop and examine your data log, don’t forget to copy the new fuel zone settings from the ‘Lambda/Knock Zone Changes’ benchmark and perform an upload to the ECU.
Although Data Log Lab ships with the most current versions of versions of LinkWIN, for real-time fuel and ignition tuning, we recommend you install Stan Mahaffey’s excellent RTLink. Once RTLink has been installed, simply go to the FM Link ECU tab of the Options window and change the Data Logging/Upload Program to RTLink.EXE.
RTLink brings real time display to the Link ECU. It displays the current zone, all zones visited during the run, and any auto-tuning alterations made to them. It provides audible feedback to aid driving in zone centres for tuning purposes, and provides a display of various other engine parameters including water and intake air temps, NB and WB O2 sensor output. It integrates smoothly with Data Log Lab and comes with exhaustive documentation. It can be downloaded from its home page on the Flyin’ Miata web site.
1. After using a context menu on a graph (right-click menu), a further click is required on any part of the application before controls and menus can be selected.
1. Latest Flyin Miata chip features added to the Zone Data Editor: TPS Idle, L4 disabling, Check Light disabling, alternate EGR schedule, NB/WB combination auto tuning.
2. Tool tip corrections in the Zone Data Editor.
1. FM Link chip version definition extended in Options window to allow more accurate MAP file acquisition. (When a Zone Settings (MAP) file is acquired, the ECU chip type and date are not received from the ECU and so the application substitutes those details defined in Customise->Options->FM Link ECU).
2. FM Link A/F Target data item added. For a full explanation, see the Data Item Explanation section.
3. FM Link Zone Data Editor fixes and enhancements:
a. Idle MAP has been renamed to Overrun MAP and moved from the Idle frame to the Fuel frame.
b. MAP deadband has been moved from the Wastegate frame to the Miscellaneous frame.
c. Auto Tuning frame now includes Auto Tuning Targets and has been moved.
d. Auto Tuning Targets now show Equivalent A/F ratio or lambda values.
e. Fuel frame has been created to gather together fuel related zones.
f. O2 Targets frame has been removed.
g. Acceleration Pump frame has been removed.
h. Prime Delay and Debug Data were editing each others values. Now they’re editing their own.
i. Prime Factor upper limit is no longer tied to Master Fuel setting.
j. Latest chip features added: Idle Stabilisation, IAT Boost Target, 1.8 IAC on a 1.6 engine.
k. Auto Tuning Sensor “NB+WB” option removed unless Auto Tuning Type set to “L3” or “L3+L4”.
l. Fuel frame changes: 15v Offset field renamed to Injector Offset and Sens Scale field renamed to Offset Slope
m. Copy Benchmark window reflects changes to field groupings above.
n. For normally aspirated data logs, the Wastegate and Boost Targets frames are now disabled, but zf600 and zf605 in the Fuel Zones tab and zi600 and zi605 in the Ignition Zones tab are now enabled.
4. Sample Graph now has temporary override of the Scatter Graph Auto Draw setting in its File Menu.
5. Scatter graph export facility added.
6. Tec-3 data log loading now deals with the latest version of data log generated from WinTEC3.
7. LinkPlus data log loading now supports data logs generated by Link Engine Managements PCLink v2.4 software.
8. Windows 98 fatal load error fixed.
9. Bug in FM Link MAP file name auto-incrementing fixed.
10. Fixed problem preventing loading of UTEC type 4 fixed width data logs.
1. Universal Data Log Loading added.
2. Maximum length of data log load increased to 300,000 records.
3. New high-contrast graph colouring options.
4. Aerodynamic properties in car definitions enhanced to allow drag coefficient and frontal area to be specified.
5. Preset graph lists only contain those applicable to the licence type of the loaded data log.
1. Unit conversion of existing entries now added to Car Definition and Power Graph windows.
Use Add/Remove programs in the
Control Panel. If you have any saved
application files within the installation directory, the un-installation process
will not remove the installation directory.