MoTeC ADL2 EDL2 - Manual (Page 14)

12 Overview
Memory Occupied
The amount of memory occupied by Fastest Lap logging depends on how
many items are logged, how fast they are logged and the specified maximum
Lap Time. The effect on normal logging time is shown in the configuration
software.
Logging Setup Files
The logging list can be saved and loaded from a file. This allows multiple
logging setups to be used.
Retrieving the Logged Data
A personal computer is used to unload the logged data from the ADL2. The
logged data is then stored on the computer hard disk.
The logged data may be retrieved at very high speed (approximately 2.5
seconds per Mbyte when using USB or 20sec Mbyte when using CAN).
After each unload the user has the option to clear the logging memory.
The unload may be interrupted part way through if necessary by
disconnecting the computer. The partial unload will contain the most recently
logged data and will be stored on the computer hard disk. In this case the
ADL2 logging memory is not cleared and logging will continue as normal at
the end of the existing data. Next time the logged data is unloaded both the
new data and the previously partly unloaded data will be retrieved.
Track Map Sensor Requirements
In order for the logging analysis software to plot a track map the following
sensors are required and must be logged.
• Lateral G force
• Wheel
Speed
• Lap Beacon (Note that the ‘Beacon’ Channel must be logged)
• Longitudinal G force (Optional: See Below)
A Longitudinal G force sensor should be used if the vehicle has only one
wheel speed sensor. This allows the analysis software to eliminate wheel
lockups which is essential when creating or using a track map.