CoTASA : COndor True Air Speed Alarm V3.2 CoTASA is a program which displays True Air Speed (TAS) and sounds an alarm. TAS is computed either using the ISA model or the one built in Condor As an option, it is possible to display an artificial horizon, the contents of the water-ballast, the Netto vario, a long-term integrator variometer, a Netto integrator, a G-meter, a skid indicator, a wallclock and two stopwatches. For flapped gliders it also shows the recommended flaps setting. It only works with Condor version 2 or 3 The active version is detected automatically NEW FEATURES: See Changelog.txt CoTASA now has a configuration application that can be launched independently or from CoTASA READING THE MANUAL IS HIGHLY RECOMMENDED All parameters can be modified via the configuration application. The application can be launched standalone or from CoTASA by pressing the "C" key when CoTASA has focus It is also possible to edit the file by pressing the "E" key when CoTASA has focus You will have to restart CoTASA for the modifications to be taken into account. It is also possible to read the manual (when CoTASA has focus - "H" key). INSTALLATION: If you use the installer, just follow the instructions. If you install over an older version of CoTASA, the existing CoTASA.ini file will not be replaced, CoTASA will update it with default values the first time it runs After an initial installation, you must run CoTASA before you can use CoTASA_Setup. If you use a ZIP package, unzip it into the desired folder, it is possible to make a shortcut on the desktop. If you already have installed CoTASA, copy your existing CoTASA.ini to the (new) Settings folder before running CoTASA. If a new installation is detected, it will open a dialog box so that you may fill in the access path(s) to the current pilot's folder(s), usually: C:\Documents\Condor\Pilots\YOUR_NAME If sending UDP datagrams (including extended data) is not enabled in Condor, CoTASA will also try to open the UDP.ini file (usually located in C:\Condor2\Settings) with a text editor in order to modify it, (see manual page 1). IF "ExtendedData1=" IS NOT PRESENT IN THE FILE YOU WILL HAVE TO INSERT IT If another application needs Condor UDP data, it is possible to enable UDP port forwarding: specify the port to which the UDP data must be forwarded (and, if needed, the IP address) in the CoTASA.ini file NOTES (more details in the manual): The first time it runs, you will have to enable CoTASA in the firewall so that it can get data from Condor Condor should be configured in “windowed” or “fullscreen emulation” (SETUP / GRAPHICS tab) so that the CoTASA windows always remain on top on the screen. If CoTASA stops when Condor starts (or does not start if Condor is already running), try to run it as administrator If the Aero theme (Windows 7) is activated, the CoTASA windows will not be transparent. In some configurations of Windows 10 (not precisely determined yet), CoTASA windows are not visible if they are transparent (text) or if they have transparent parts (corners of the artificial horizon). In this case, it is necessary to disable the transparency of the text window (Opacity> 0) and that of the corners of the artificial horizon (AH transparent corners = 0) The default key definitions have been set up initially for a French (AZERTY) keyboard, and they may conflict with some definition you made. Do not hesitate to review and change them if needed. If the message command has been mapped to a joystick button, CoTASA cannot detect it. In this case, it is possible to define a substitute key in the CoTASA.ini file. It may happen that CoTASA does not respond to keystrokes anymore. Until an automatic solution is developed, you will have to manually restart keystrokes detection by giving the focus to CoTASA and pressing the "K" key. In more rare situations, it may happen that keystrokes are not detected by both Condor and CoTASA. If this happens, activate the Windows Task Manager by CTRL-ALT-DEL, click on the "Processes" tab, then on the "Image Name" column header, select the CoTASA.exe line and click on the [End Process] button. It is possible to prevent CoTASA from accessing the keyboard when it does not have focus. To do so, you must set the KeyboardHook parameter to zero in the CoTASA.ini file. If you start a new flight Condor, you should also restart CoTASA in order to have up-to-date parameters. FILES: CoTASA_README.txt: README file CoTASA_LISEZMOI.txt: French version Changelog.txt: List of changes CoTASA.exe: Executable file CoTASA_Setup.exe : Configuration application CoTASA_Setup1_form.frm Forms definitions CoTASA_Setup1_form_FR.frm Forms definitions CoTASA_Setup2_form.frm Forms definitions CoTASA_Setup2_form_FR.frm Forms definitions CpwDLL_N.dll : Graphical library bass.dll: BASS sound library zlibwapi.dll: Zlib library Settings\CoTASA.ini: Settings (see file description below) Settings\CoTASA_default.ini: Default Settings (this file is read only, please do not modify) Settings\CoTASA_data.txt: Glider related data (see file format below) Settings\silhouette.txt : Outline of the glider displayed in the artificial horizon Manual\Manual_EN.pdf: Manual (English version) Manual\Manual_FR.pdf: Manual (French version) Lang\CoTASA_Lang_List.txt: List of available languages Lang\CoTASA_Lang_EN.txt: Messages file (English) Lang\CoTASA_Lang_FR.txt: Messages file (French) Lang\CoTASA_Lang_DE.txt: Messages file (German) Logs\Logfile.txt: Log file Sounds\VNE_0.wav VNE alarm (min level) Sounds\VNE_1.wav VNE alarm (2nd level) Sounds\VNE_2.wav VNE alarm (3rd level) Sounds\VNE_3.wav VNE alarm (max level) Sounds\Flaps_Up.wav Flaps up alarm Sounds\Flaps_Dn.wav Flaps down alarm Sounds\Landing.wav Flaps set to “Landing” Alarm sound files can be replaced by other sound files of comparable length. It is highly recommended to backup the original files beforehand. Some extra sound files are available in the Sounds folder