Subject: Motec log file
From: paul lamar
Date: 7/25/2016, 5:30 PM
To: A10-Me-Earthlink




 Are you there?

 I am trying to extract logged data.

 what do they mean by venue?

 what do they mean by session?

 Do I have to answer all these question?

 If I extract a new file does that erase all the old files?

 Paul Lamar


 Paul, like I said before I am not a Motec expert but a session would
  probably be something like morning practice 1. A venue would be Road
  Atlanta.

 You would add comments like adjusted base fuel pressure from  32.5 to
 35 PSI.

 I don't think every line has to be filled out.

 The old files are not erased unless you delete them. Even if you
 extract them and send them to someone it keeps a copy. If you make a
  change to a file save it under a new name like 1b. You always want
 to be able to go back to the previous map if it was better. Barry

 Barry Bordes


 Thanks Barry.

 When I try to load one I get a blank screen with out the engine
 having been run. Here is a screen capture.

 Is there away to get a list of the logged files in the M800?

 Paul Lamar


Paul, if you look at your blank screen at the top select ..file, the drop-down
box should say something like ...file /open.   And a list of files from
previous
runs should show up. When you select one of them in a blank page will then become filled with data.


Barry Bordes


Thanks Barry I will try that.

We ran out of inputs when we put an exhaust manifold pressure sensor and an EGT sensor so that logged data is going into the Motec dash device.

The Motoc dash device has far more memory than the Motec
800 CPU.

Motec should have put a 64 Gig SD card in the $3000 M800 just like the $60 Maximite I used to measure the compression pressures :-)

Paul Lamar


Paul,

That information is there for you to keep track of the logged data. It's absolutely not required to be filled out, but serves you far better if you take the time to do so as you will be able to review this information in the data analysis software when you look at the data. Below is a good bit of information about the details editor you encountered. While I stole it from a dash product most will remain significant for downloading the ECU. It is your choice to erase the data after downloading it from the ECU and I generally recommend doing so. The M800 is a FIFO logger in that the oldest data will be lost as the newest data is recorded in memory.

-Simon Wagner


----------------------

Help on the Details Editor:

-----------------------

The Details Editor specifies the details for the Event, Venue and Vehicle.

Details used for Data Logging
All the details are attached to the logged data when unloaded so that
the logged data may be easily identified and other important parameters can be viewed.

The following details are specifically used for identifying the logged data.

Event Name
Session
Short Comment
Venue Name
Vehicle ID
Driver
The driver details are entered on the Vehicle Editor window, which is accessed by via the Manage Vehicles button.
Not all these fields need to be filled in, however filling in as many fields as possible will help to better identify the data.

Details used by the Configuration
Some of the details are attached to the configuration for use by the various calculations.

Venue Length used by Lap Speed Calculation, Missed Beacon Auto Lap Increment, and Auto Lap Distance Reset.

Best Lap Time used by Fastest Lap Logging to determine how much memory to allocate for the fastest lap.

Laps / Tank used by Laps Remaining calculation

Fuel Tank Capacity used by Fuel Remaining calculation.

Diff & Gear Ratios used by Gear Detection - Speed/RPM Ratio Calculation.

Details Confirmation
Confirmation of the details will be requested at certain times to make sure that the details are correct.

Confirmation is requested at the following times:

When first started on each day to ensure that the Event and Venue details are correct.

When sending the configuration to the Dash Logger to ensure that the items that affect the configuration are correct.

After retrieving the logged data to ensure that all details are correct before attaching them to the logged data.

Next Event Details
Event Name
Used to help identify the logged data.

For example: FF Round 1, 2007

Session
Used to help identify the logged data.

For example: Practice Session 1

Short Comment
Used to help identify the logged data.

Long Comment
Optional - Additional comments.



Default Venue
This is venue information used if the beacon type is BR2, BRX, Button or internally generated.

Select Manage Venues to change venues.

GPS venue selection
If the beacon type is selected to be GPS Coordinates, then the venue files used are shown in a list. To view or edit this list, use the Manage Venues button.

When these venues are sent to the device, the Dash Logger will automatically use the GPS co-ordinates of the venue closest to the current GPS location as the beacon.

When using this method, there is no need to change venue details between events.



Default Vehicle
This is the vehicle last used when downloading logged data or configurations. To view or edit the list of vehicles in use, click the Manage Vehicles button.

The Dash Logger automatically selects the vehicle file with the matching serial number from the vehicle list when downloading logged data or configurations.



 The Rotary Engine free News Letter. Powered by Linux. If you want
 off the list PLEASE let me know and I will remove  you.  ACRE NL web
 site. http://www.rotaryeng.net You Tube http://tinyurl.com/beqqxas
 Copyright 1998-2016 All world wide rights reserved.