FRDL reads from and writes to a number of files on both the host computer and on the logger. This is a summary of what they all are.
The championship configuration fileThe file always has the extension .frdc
This is the 'master file' containing all the information about the championship, so everything from the Championship settings and task settings pages as well as a list of all the loggers which have been connected.
The file is named and located by the user from the 'New championship' dialog and can be opened from the 'Open championship' dialog, or can be copied to a new location via the 'Save as' dialog.
It is recommended that the championship configuration file is located on the host computer and not on a network share because all the log files from loggers are backed up to sub-folders of the folder the championship configuration file is in, and it will be very slow to send all the backup data across the network compared to saving it locally.
Before a change is saved to the championship configuration file a backup copy of the previous one is saved to the same location with the file extension .bak. To revert to an earlier version of the championship configuration file simply rename the appropriate file by changing .bak to .frdc and then opening that file in FRDL.
Logger backup filesThe first time a logger is read by FRDL a sub-folder is created in the folder where the championship configuration file is located. Each of these sub-folders is named according to the CIMA file naming protocol and it contains a copy of all log files found on the logger and backup copies of the logger configuration file.
Output igc filesThese are saved in the location configured on the championship settings page. It is recommended it is the location where the flight analysis program will be reading them from.
igc files are named according to the CIMA specification:
FRDL never overwrites a file but saves a new file every time a logger is read, and names it as a new version according to the protocol above. 35 versions of a file are possible, versions are named 1-9 then A-Z.
If the igc files location as set in Championship settings page is unavailable (eg is on a network share which has neen disconnected), then FRDL will save output .igc files in the same folder as the championship configuration file. The operator will be alerted to this with an error message, and advised to re-establish the connection and read the logger again so the output file is saved to the intended location.
Logger configuration fileFRDL writes a file named logger.frdl to each logger the first time it reads it, and thereafter maintains the contents. This file identifies the logger to FRDL and should not be deleted or edited during a championship.
Every time a logger is read, a backup copy of the Logger configuration file is copied to the logger's backup location with a name created from the current date and time and _logger.bak eg 20090419105651_logger.bak. If a logger file is inadvertently deleted from a logger it can be restored by copying the most recent backup to the root of the logger and renaming it logger.frdl
AUTORUN.INFFRDL creates a folder named AUTORUN.INF on the logger, and puts one file in that folder named README.TXT. This folder is part of FRDL's defence against Viruses, Trojans and Worms, see Protecting against malware for a full explanation.
Do not place any files or sub-folders in this folder as they will be deleted without warning the next time the logger is read by FRDL.
FRDL configuration fileFRDL maintains some general configuration settings in a file named FRDL_session_Properties in the user's configuration folder. This file should never be edited.