FPLCheck Version 1.6 FPLCheck is a basic tool that checks parameters in a Condor flight plan (fpl file) It has been tested with Condor 2 but should work also with Condor 1 USAGE : FPLCheck.exe can be run from a command line prompt or by double clicking the icon. If you want to use drag-and-drop mode to start it, it is recommended to create a shortcut on your desk. It is then possible to drag file(s) to the shortcut. Command line syntax : > FPLCheck [-v] [-help] [-nopopup] [-oklines] file(s) file can be a single file, or a whitespace separated list. * and ? can be used : (e.g. *.fpl, flight*.fpl, flight???.fpl, etc.) if a name contains whitespaces, enclose it between "" If no files are specified, a selection window pops-up. Multiple selections are possible. Options : -v : verbose mode (use if support is needed) -nopopup : disables information popups -OKlines : enables writing of all lines in the log file -en/-fr : force language -help : prints the command line syntax These options can also be specified in the file FPLCheck.ini Command line options (if any) supersede the corresponding options read in the .ini file Complete test results will be written to a logfile called FPLCheck.log (overwritten if already exists) and to the standard output if running in a command prompt window. FPLCheck.exe reads the list of parameters and values to check in a file (REQUIRED) called DEFAULT_CHECK.fpl by default. It is possible to select another file in the file dialog This file has the same structure as a Condor FPL file, except that different relation operators can be used: = : equal != : not equal < : less than <= : less or equal > : greater than >= : greater or equal [] : contains (character strings only) Numerical values are detected automatically. It is not possible to compare character strings and numerical values. For character strings, it is possible to give a list of values, separated by ";" For example: Landscape=AA2;FRN Numerical operators work for both numerical values and character strings. If a parameter and the required value have different types (floating point vs. integer) the integer value will be converted to floating point before comparison. Beware of rounding issues when comparing floating point values ! An equality threshold may be defined in the FPLCheck.ini file If two or more lines set constraints on the same parameter, these constraints will be ANDed. Hence, if a parameter must be between two values, two lines must be entered, eg: TurnpointHelpersRange<=5 TurnpointHelpersRange>=1 NOTE : This means also that it is not possible to exclude a range with inequalities, you will have to explicitly exclude values one by one (this works only for integer values, obviously). The following example will not work: TurnpointHelpersRange>=10 TurnpointHelpersRange<=5 But that one will: TurnpointHelpersRange!=6 TurnpointHelpersRange!=7 TurnpointHelpersRange!=8 TurnpointHelpersRange!=9 WILDCARDS AND SPECIAL PARAMETERS It is possible to add a wildcard at the end of a parameter name: * : any characters match | : used to identify the finish TP $ : used to identify all TPs except the start aerodrome (TP0) and the start (TP1) and finish TPs (TPn-1, if Count=n) ? : used to identify all TPs except the start aerodrome (TP0) and the start (TP1) and last TP before finish (TPn-2) and finish TPs (TPn-1, if Count=n) % : used to identify the last TP before finish (TPn-2), if there is at least one TP between start and finish Examples : TPSectorType*=0 : all TPs must be "classic" TPAngle|=180 : Finish sector = line TPAngle$=360 : all TP between start and finish (excluded) = cylinder TPAngle%=360 : last TP before finish = cylinder There are also 4 special parameters for start and finish altitudes (ONLY FOR CLASSIC TPs) StartMinAlt : start minimum altitude (same as TPWidth1) StartMaxAlt : start maximum altitude (same as TPHeight1) FinishMinAlt : finish minimum altitude (same as TPWidth|) FinishMaxAlt : finish maximum altitude (same as TPHeight|) ALTITUDES (ONLY FOR CLASSIC TPs) Minimum and maximum altitudes maybe specified as AMSL (default) or AGL, eg: FinishMinAlt>=200AGL NOTE : AGL is always computed locally, not relative to the start or finish airport, if any. It is also possible to use the base of the cumulus clouds (or the inversion layer in their absence) as an altitude reference. Examples: StartMaxAlt