Frequently Asked Questions

Frequently Asked Questions

All Data Log Formats

Date Added

Question

Answer

09-Feb-2003

I really hate manuals and Data Log Lab has such an extensive one - what do I need to read to get started?

I sympathise with this viewpoint - I personally like to just dive in to new software and get a feel for it, then hit a brick wall, then go to the manual.
I'd recommend every new user does at least the following:
* Make sure you go to Customise->Options->Data Item Definitions and reduce the number of data items displayed to make your life easier. It's covered in the instructions (just hit F1 whilst in the Options window), but basically a good portion of the data items aren't relevant to each individual ECU and so can immediately be weeded out.
* Use the Right-click menu on the sample graph for speed.
* If you're using the Power Graph functionality, give that section of the instructions a thorough read on what to do. It contains many tips of how to do a power run in your car as well as how to generate the Power Graph accurately.

03-Feb-2003

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 Use 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!

03-Feb-2003

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.

03-Feb-2003

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.

 

Flyin' Miata Link ECU Data Logs

Date Added

Question

Answer

03-Mar-2002

When attempting to upload data to the Link ECU I get the following error the first time I try:

"-26 Zone map load aborted because engine was running."

However, 2nd or subsequent attempts usually work.

or

the changes upload to the ECU but then I get the error:

"-7 Store Command NAK'd".

1. There is an issue with version 1.18 of LinkWin that causes this error if an upload is attempted within the first 30 seconds or so after turning the car's ignition on.  This is being investigated, but in the mean time you'll have to wait 30 seconds unfortunately!

2. You can get this error if your TPS isn't adjusted properly.  If the car's idle switch isn't closed, LinkWIN won't allow upload.  If you have a Link keypad, turn the ignition off, connect the keypad, turn the ignition back on.  If the IDLE window contains a "*" then the idle switch is closed.  If it doesn't, try pulling the accelerator up with your foot, or dabbing it a few times.  If there's still no "*" displayed, then you need to adjust the TPS, or you have your foot on the accelerator!

3. The car must be in neutral and the clutch pedal must not be pressed.

03-Mar-2002

When attempting to upload data to the Link ECU I sometimes encounter the following LinkWIN error:

"-2, Response to Stop/Resume log data output command timed out."

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:

  1. The engine is not switched on.  The ignition key must be in the 'engine run' position, although without the engine running!

  2. The Link is still 'booting up'.  Leave a few seconds between turning the ignition on and starting the upload.

  3. 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! 

  4. Some folks have resolved this problem by upgrading their Link chip to the latest version.  There may be an issue where a faulty chip causes this type of failure without affecting the changing of zones using the keypad.

14-Feb-2002

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.

14-Feb-2002

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.

20-Jun-2001

Flyin' Miata's latest chip versions allow 30 seconds of data logging without the engine running.  However, when I acquire a data log in this way, I get error messages saying 'Problem loading chip date' and 'Problem loading atmospheric pressure'.  Is there really a problem?

Assuming you have accurate information entered in the Link ECU tab of the Options window, then there isn't a problem as the chip date and default atmospheric pressure will be substituted from there.  However, there might be a problem if you are data logging somebody else's car that has a different chip date.

The two error messages can be suppressed by checking the Silent Defaults box in the Link ECU tab of the Options window.  However, I don't recommend this as it also won't make you aware of the application substituting missing chip version information under other circumstances.

24-Apr-2001

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 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.

22-Feb-2001

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.

22-Feb-2001

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 which 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.

20-Feb-2001

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".