TP - Known Problems , Frequently asked Questions,... and Workarounds
How to report a problem - Must Gather
zip together your competition directory and the RACE mdb file and email it to the developer. It is a good idea to have all your files related to a competition under one directory. That makes the zip file creation much easier. And send you tp.ini file . Describe the problem in the email, eg Pilot 54 does not score ... or track is cut off too early. Or why does pilot x not get the turnpoint ?
Install
- I copied the TP code directory and samples from a CD and nothing works!!!
The files and directories all became probably read only when they got copied
from the CD to disk. Because the CD is a read only device. Use Properties of
the directories and switch them to read and write and apply to all files and
subdirectories.
- Something hangs, nothing
works suddenly, And after restarting TP you got funny behaviour,...
use CTRL ALT
- Trying to read a RACE Bulk XML is not working. You need to update your MS IE to 5.5 SP2. Sorry.. what ??? Get from Microsoft the Internet Explorer 5.5 Service Pack 2 and install it. Or nowadays use IE 6.
Setup
- Why do we need a SS
turnpoint defined twice? RACE works on the basis that a turnpoint is also
used as a SS. In
- I am getting this
.
Use SETUP/COMP/CREATE and SAVE it again. Same for SETUP/TASK/MODIFY. After
saving all the different settings, this message should go away. - Do not use an & or : if a turnpoint description. Any XML or KML file created from it will not work
- I received waypoints created by some Garmin software in something funny format. How do I convert them to csv? Use GPSBABEL , and output the waypoints into Fugawi. Notepad edit the Fugawi file, and remove the top comment lines. Now you got a file which is close to csv. Rename the file to xxx.csv and then open it in a spreadsheet program. Delete some unused columns. Re-arrange the remaining columns to look like a csv that we use for TP.... easy ?
- Why do we need an SS turnpoint defined twice ???. Another answer... An SS turnpoint can have a 1 km SS radius and then it is a 400 meter radius turnpoint. To check the correct sequence of events, the pilot first has to cross the SS 1 km radius in a given time window. Only afterwards he is allowed to enter the 400 meter radius. So the code has to be given that sequence. First takeoff, then the SS 1 km turnpoint, then the 400 meter turnpoint. If the SS is 400 meter and the turnpoint is 400 meter, still make it two entries.
- COMPNAME not found, UPLOAD.csv, comp_id.csv not found ,... oops, with 4.10.15 in the ini file COMPNAME got replaced with COMP_ID. Climb into the tp.ini file and the compwhatever.ini file and replace the COMPNAME=whatever with COMP_ID=whatever
- A client is setup to use F:\whatever as the compdirectory. But he keeps changing back to C:\whatever. The Master directory F: got in the comp.ini file a TP_Comp directory entry that points to C: erase the comp.ini file. Make sure the comp.ini file in F: Drive will only have info that is relevant and the same for all clients. Comp.ini usually only has the current active task id.
- Older comps do not load properly. Rename in the compdirectory the Settings.ini to comp.ini. and in the TaskXX directory the Settings.ini to task.ini. Check with a new created comp which file names have changed.
- COMPDIR needs a \ at the end. tp.ini file, COMPDIR=C:\AA21 must be COMPDIR=C:\AA21\ for compid.csv or UPLOAD to work
- COMPNAME has to be 6 characters long. ABCDE no good. COMPNAME=ABCDEF to make sure pilot numbers are written into GPS.
- If the PC time is set to AM and PM mode, TP can not define the [TIME] Section values correct
Create a TASK.ini file and then modify the [TIME] Section by hand to 24 hour
format
For the date use
Make sure the PC Regional Settings under My Computer - Control
Panel , TIME tab is HH:mm:ss
And the date is dd-MMM-yy or dd-MMM-yyyy with a date separator - or
:
- Time format of PC has to be
HH:mm:ss , 24 hour mode and dd-MMM-yyyy date
- If the date is MM/dd/yy then IGC conversions fail and they fly on the wrong day. Make it dd/MM/yy
- RACE direct interface requires a link to the RACE database. Either via Map Network drive or get a copy of the mdb file.
- When I try to import a XML file RACE gives an error. RACE does not want to export or import any xml file. Upgrade IE to IE6. The xml parser code used by RACE is included inside Internet Explorer 6.
- Install Package goes into C:\ProgramFiles\TP\, while zipped updates end up in C:\TP
Either when unzipping, make sure the right directory level is set. Or afterward
by hand move TP directory contents into the right place.
- Only C: drive works by default, code does not pick up that the comp is in D drive. In Task load, by hand choose D drive
- What is a recommended Directory structure? I got a C:\COMPS directory where I keep all my competitions. In the C:\COMPS I got for each competition a subdirectory. Like PG2004 for the Paragliding Nationals 2004. Or BB2004 for Barberton 2004.
- Why are those competition subdirectories 6 characters long? Can I make them longer or shorter? The competition subdirectory is linked with the COMP ID which goes into the GPS to identify the pilot. Historically the GPS 12 can handle 6 characters for a waypoint. And a waypoint is used to identify the pilot at the competition. You could make it less than 6, but that has never been tested. Make it 6 characters long to avoid problems.
- Where shall I put the RACE database? By default RACE creates the database in the C:\Program Files\RACE\DATA directory. I then move the mdb file into my C:\COMPS\whatever competition directory to have it all together. After a comp I zip together the whole comp into a whatever.zip file. And 1 or 2 or many years later when we have a competition again at that site then we can reuse the previous turnpoints from that zip file.
- How do I get those tunrpoints into RACE? First define a competition in RACE. Then define in TP where the RACE mdb file is located. Then use RACE/Turnpoint/whatever.csv>RACE to feed RACE with your turnpoint info
- Can not see a scroll bar
The
scrollbar issue wasn't really a scrollbar issue at all, but a screen
resolution/window
size issue.
It
happens that I'm using a good desktop computer with a 1024 screen
resolution,
but also running the software on a small out of date WIN98SE
laptop
with only 800x600 screen resolution. On this small computer the task
window
doesn't fit on the screen and also even when you maximize it, it
doesn't
have an horizontal scroll bar for the whole window (only for the
turnpoints)
but it shows truncated.
Scoring
- Why do those background colors change? Done by a request from Brad.
- Different background colors for different GPS devices. For scorers who run multiple COM ports off one computer
This way one knows that one is busy scoring a Compeo now, while the Garmin is still downloading. And the Aircotec is waiting to be scored.
Or one sees that I am busy now with Garmin 2, not Garmin 1. It can get confusing and chaotic when one only has one person doing the scoring. And the person opted to run multiple COM ports in parallel downloading different GPS devices at the same time.
- Getting this
and then
You have not defined a Task in RACE yet.
Before creating a Task in TP, create the Task in RACE so that we get the correct Task ID from RACE
And this task has a 4km GPS error !!!! Resulting in a weird SS start and screwed up crossing times. GPS error should nowadays be 0.
- I downloaded my tracks with a wrong GPS error set to 4. Now I change it to 0. Do I have to download everyone again? - No. One has to re-score everyone using the pilotdata files.
- RunTime Error .... Get latest code install package and install code again. Plus add on top latest tp.exe file. Then reboot
- What is the difference between Cut Off and Stop Flying Time? ..........
From an organizers recovery point of view we want the pilots to land and get to the road for the truck to collect them. If we got pilots who fly late until sunset and land then one has to find them in the dark. So we set a cut off time. What can also be used as a task stop time. In case the weather goes bad. But then we might still have pilots who are over terrain where it is difficult to land , no roads, and they could fly towards some easy landing or get close to a road. So we cut the track off a Cut Off time. And Stop Flying is when the track has to show that they are on the ground. We penalize a pilot, 0 score foe example, if he is still flying after stop flying. Because he delays the recovery of the other pilots and get them to scoring.
Normally we say cut off is the same as goal closes, truck leaves goal. And 1 hour later stop flying.
Sometimes GPS get switched on after Stop Flying during a recovery. When a pilot uses his GPS to locate another pilot. In that case the software will give out a warning and if you accept the score, this pilot will get 0. But one can overwrite it by not scoring this track segment. Just watch out into Auto Mode , Auto Mode is not clever enough to make this decision.
- How do I process a pilot with multiple GPS devices? One pilotnumber like 84, one pilot name, but a MLR track and a Compeo and a Garmin and a Log-It... By default the track file gets called 084TRK.csv and one would overwrite the different tracks. Solution ... either allocate for the pilot a number like 84 , and call his first track 841, his 2nd device track 842,... Or download the track and rename by hand the files to 084MLRTRK.csv and 084GARTRK.csv
- We have a fun comp. And the pilot has no GPS. But we got his landing coordinates. How can we score him? .... Option 1 : If you use RACE score him direct in RACE by typing in his landing coordinates. Option 2: Take an existing already successfully scored short pilot track in the pilotdata directory. And copy it to the pilotnumberTRK.csv of the pilot. Have a few points from the original track at the beginning. Delete the rest. And edit the last line to have the pilots coordinates in decimal degrees. If your coordinates are deg decimal minutes, divide the decimal minutes by 60 to get the fraction for the decimal degrees. The score him inside TP via Menu Pilotdata.
- I am getting corrupted track file errors. Or when downloading files I see someone else track afterwards!!!! Possible cause... in a network setup, you all are using the same workdirectory. What is a no,no,no. Each computer needs its own work directory. You can all share and point to the same competition directory. But each computer MUST have its own unique work directory. The workdirectory is defined in Setup/Comp/Create.
- Can not run multiple downloads in parallel. One TP can only run one active window. To run multiple downloads one has to first ...
- Define multiple COM Ports in the GARMIN/SETUP
- Start multiple copies of TP on the computer
- Then keep track of which window is which port .... ( good luck, it can get hectic at scoring sometimes)
- Why is there a GARMIN1 and a GARMIN2,... ? You can use 1 copy of TP with multiple Garmin cables connected to the COM Ports. For example having GARMIN1 as the round plug and GARMIN2 as the eTrex/eMap plug. This avoids having to switch cables at the back of your PC. But only score 1 pilot at a time. Only download one pilot at a time. Somehow Windows or VB can not run multiple serial interfaces in parallel through one process. One can start multiple copies of TP, and each one will have its own serial interface thread and then they can run in parallel.
- What does that file count 8 Pilot 3 Barry mean? File Count 8 means you got 8 track logs up to now. Means 8 pilots have scored. In the evenings you need to know if all pilots have been accounted for. Or if a pilot has gone missing and you have to initiate a search and rescue. As we score the number goes up. The meetdirector has to give you some idea on how many pilots you expect to score. Either form a Check-out sheet that was done at launch. Or you know the total amount of pilots that have entered. Minus the DNF and ABS pilots..... And Pilot 3 Barry means the current track log scored is from Pilot Number 3 and you called him Barry when you allocated the number and gave him the turnpoints into his GPS.
- Why is that pilot not scored properly ???
The Task got defined with a SS crossing from Outside.
One has to change the Task Definition to SS crossing from Inside.
Either use Setup/Task/Modify and make it Starting from Inside.
Or change the Task.ini file to have this entry SS_FROM_INSIDE_OR_OUTSIDE=I
- Why is comp_id only 6 characters long? 6 characters is a bit small to distinguish a competition. Why not make it longer? 6 characters is the common longest id size that one can store in most GPS devices. Started off with GPS 12 only allowing for 6 character id fields. To identify a pilot in a unique way for each comp opted to use that approach and we have to live with those 6 characters.
- I get a Black track. Pilot scored to takeoff.? Max_Non_Move too low, pilot moved at take off = took off, then stopped = landed. Change MAX_NON_MOVE to 0 to ignore or make it bigger in seconds. Switch off stationary check.
- Still getting a black track, and RACE xml makes everyone DNF? Did you combine TO and SS with a 1km inside start? First make a TO, then add it again as a SS from inside.
- Not seeing a track by a pilot who did a 2nd attempt? But Dynamic Zoom shows a track? Pilot probably got a high sample rate. Moved on takeoff = took off, then stopped = landed. Set Max_Non_Move much higher or make it 0, to deactivate stationary checking, and rescore.
- Analyze track window refuses to open. A dll for the slider is missing. Code got probably installed by only copying the tp.exe file. Instead of using the full install package.With TP 4.9 a slider got introduced in the Cylinder Analysis track window. If the code can not find the slider.dll it falls over. Get a proper install package, even if it is backlevel , but TP4.9 or higher. And make a new install of the code. Then replace the old backlevel tp.exe with the latest tp.exe code level.
- What is that slider for in the Cylinder scoring? It influences in AUTO REDO scoring mode how long a result gets displayed. Before the next pilot gets processed.
- Only 1 point in a SS Cylinder will not score the TP. Fixed with TP4.11.15. In the meanwhile use the overrule option.
- Trouble talking with Compeo, MLR,... any of the faster IO Coms. Make sure the PC's Serial port settings are flow control off, fifo full on. A common problem with high baud rates can occur, especially on Laptops, that somehow the serial port comms fall over. One workaround is to use a USB serial port interface instead if your Laptop got a USB.
- Why do those cylinders look like ellipses? Not round at all? Some windows are using Mercator Projection. Coordinates are used as a grid. Not distances. In Mercator projection 1 minute has the same distance in North South and East West. But 1 minute is not the same distance on the ground. Unless you are at the equator. So Circles get distorted. Got it? If not , go and hold your comp along the equator and those cylinders will be round. Other extreme, go to the pole and your cylinders will be squashed in Mercator projection. Or use the dynamic zoom window, which uses true distance projection.
- Scoring a track and no track visible at all.
Delete any previous old outdated tracks of the pilotnumbertrack.csv file.
Can be caused by a 1 - 0 -1 or 1 - 0 - 0 - 1 track segment in between.
1 indicates a new track segment.
- Also if a GARMIN track file starts with track segments 1 - 0 - 1, sometimes causes that no track is displayed
Delete the first 2 track segments 1,0 and start with the 1 as first record
- If there is no SS then total task km might be wrong . Should be fixed by now?
Make 1st TP Starttarp and set times to be open for the whole task
- TP crashes but does not die. Use Ctrl Alt Del and kill TP processes
- How to I activate the AUTO REDO Mode in Pilot scoring tick? Use the COMP/CREATE and tick it, do not save.
- PILNRID.csv file location varies. Should be fixed with 4.10.
Sometimes the code wants the PILNRID.csv file in the top competition directory,
compdir. And sometimes in the TASKx sub directory.
PILNRID.csv is supposed to be located in the competition directory.
If there is a problem finding it, also put it into the TASKx directories and
into RACE/DATA directory.
- Problem finding an comp_id.csv file... copy an comp_id.csv into the TASKx directory
- In a race to goal, when using xml bulk transfer to RACE, all pilots get individual SS times. After bulk xfers, redefine the task in RACE as a race to goal. Which will reset everyone's SS back to when the task opens.
- Mercator projection does not show true distance ... a cylinder should be shown distorted to an ellipse in Mercator projection. Code use Mercator for task draw and full screen interactive zoom. While for fixed zoom around a turnpoint the code will do a true distance calculation and projection
- an SS can only be the first TP after take off for the Option 1 and 2 AllOnAll and follow track scoring method. Use Option 3 Cylinder score if there is a turnpoint before the SS
- Track is all red. Date in TASK.ini file might be wrong. Have a look at the TASK.ini file in the Taskx directory and make sure the Taskdate and format is correct
- Using a Cylinder Goal the track stops before reaching the goal. But pilot gets goal...? This can be a projection problem. The code stops drawing the track once the pilot crossed the cylinder and reached goal. The distance is calculated based on the FAI formula. Which caters for the spherical earth shape. While the track display onto the task is drawn in a very basic, simple approach using a Mercator projection. A cylinder should be in fact an ellipse.
- 2nd possibility, track stops before pilot crossed cylinder goal. GPS_ERROR is set too big. Like 0.02, 20m, make it 0.002 or 0.004. Or 0, of you want.
- Aircotec TN download and Com port in use. Exit out of TP. CTRL ALT Del and kill any TPGPS. The fire up TP again.
- Initial SS Circle does not match pilot crossing point. SS circle radius initially is drawn in mercator distance 1-1 projection. What is wrong. Once we got the crossing point , which is calculated based on FAI distance formula, we draw a true distance point through this one
- One TP can not run multiple Garmin downloads, they block each other. The active window does the comms, the inactive ones stop. ... To run multiple Comports in parallel, eg some GARMIN downloads and a MLR and whatever ... , start multiple copies of TP which use different Com ports. I recommend to run one 1 PC to 1 GPS device download. At KZN2002 we ran multiple com ports , and the operator got confused and stressed , having to handle multiple pilots.
- How do I add another waypoint into TP? Add the waypoint in a GPS, download the waypoint and track info in TP without scoring. Then click on the waypoint and the code offers you to copy it into the list of official turnpoints. Or use SETUP/TASK/CREATE and Add button and type in the coords. Or look for the WAYPOINTx.csv in your working directory. Open it with a (Notepad) editor. Copy / paste across into the comp_id.csv file the waypoint info that you want to use.
- Error Missed Start Section by 2.0 km or by 1.6 km .... Now what??? Can the code not decide? SS had a 400 meters radius. Now one has to decide if a pilot gets scored up to the beginning of the radius or to the turnpoint center. With small SS cylinders it does not really matter. But if the SS cylinder radius is 10 km and not a turnpoint and the pilot lands 400 meters short of the cylinder ... what is he supposed to get? 400 meters short, or 10.4 km short of a turnpoint that is not part of the task. Confused? Me too.
- I have a problem wit the code. Use the Report the Problem Option. And when I then use the older code it works fine. But my RACE result does not get updated by the older code level??? ..... Only the latest code is maintained to support a RACE XML interface. You will have to write the score down on paper and feed RACE by hand. If I have to maintain older levels of code and newer levels, then the code becomes even more spaghetti as it is.
- Redo All and Auto Accept are not enabled in Pilotdata when I try to score all tracks in one shot.. How do I make them active? Use Setup/Comp/Create and tick the Auto Redo and Auto Score.
- Why is the Start of Speed Section (SS) Cylinder and the white line, that shows where the pilot gets the SS accepted, not the same?
The Overview uses Mercator projection. NS and EW are the same units. In real life EW and NS distances based on coordinates are only the same at the equator. And the SS cylinder would be distorted. Here we got a biiiig 13km SS cylinder and one can see the deviation.
The white line is showing the true distance of 13km from the center using the FAI CIVL distance formula.
- My pilot track is a black line only and the takeoff gets not accepted?
The time of the track log is not correct. Or the Timezone Offset is not correct for the comp. Or the times for the Open and close window are wrong. Maybe you use AM and PM istead of 24 hour mode in your Local Computer settings?
But why is this track black? The track wrapped. It does not show that the pilot took off in the time window and within the designated take off area. Therefore the track is initially black. It only gets color as the pilot flies again over the takeoff area.
One can overrule this score by Unticking the Check for Take Off ( maybe)
But one might have to restart TP, untick, and then score the pilot.
GARMIN
- Ony the SCORE a Pilot button is active. Can not Send Turnpoints. The AUTO SCORE MODE is ticked. Untick the AUTO SCORE Mode. In AUTO SCORE MODE one can only score and do nothing else. Idea is to have a self service mode for pilots. And to avoid them playing around and trying other buttons, everything else is deactivated.
- I click on GARMIN and all my GARMIN1,2,3 are dimmed. Can not use them. Only SETUP is active? No COM Port has been defined yet for a GARMIN Interface. Use the GARMIN/SETUP , Enter the Number of COM Ports ( normally 1 ) that you plan to use. And then Enter which COM Port you are connecting to the GARMIN cable.
- Using a new GARMIN 76S or 72 I can not see any of those turnpoints? By defaults the 72,76,.. show the nearest waypoints. Choose in the Garmin to see all waypoints by name and they should be there.
- GPS 12 4.0 software level is not supported. Update to 4.57 or higher
- GARMIN GPS interface written to latest IO specs of Garmin. Older GARMIN code levels can have handshaking problems. Try to update GPS to latest code level. A very new code level might also have a new handshake protocol which the TP does not know about yet.
- During GARMIN download, Expecting a PID Error message..... The GPS has acquired satellites and the track sampling is still on.
The GPS is still collecting track points while downloading.
If the track log sample rate is high, then switch off track recording mode in
GPS.
Otherwise try again. Make sure the GPS can not receive any satellites.
At the beginning of a download the GARMIN GPS tells the computer that it has
got x amount of track points.
If the download takes quite long, and the GPS track sample rate is every
second, then in the meanwhile more track points have been added. And the
communication between GPS and PC gets confused. After the track download
the code expects a PID packet of waypoint data. Instead it still gets a track
log packet of the new point(s).
- Expect a PID during GARMIN download , 2nd possibility .... Com protocol changed.
Hit enter and ignore. Should work Older GPS software levels only give ID
and software level.
Newer software level give make/id, level and protocol info. But some
combinations do not work according to specs in the IO manual.
Check if GARMIN code is up to date, e.g. GPS12 on 457 or 458 in 2001.
Can also be caused by a new software version. With a changed
communication format.
The IO Specs documentation of Garmin are not always up to date and there are
some data formats out that are not documented.
Or a PID format has never been tested for a certain GPS..
See GARMIN IO Protocol for software level and interface version that is
supposed to be used.
If all fails, use Gardown or Gartrip , save in gd format and then use the TP
CONVERT TRACK GARDOWN to CSV option.
Then rename the file to pilotnumber.csv and put it in the days pilotdata
directory.
- eMAPs and eTrex have no comment section, no place to store the compname. Documentation says they got, but in reality it is not there.
- Locked Com Port in GARMIN Download.
Use CTRL ALT DEL and check if another TP process is running. Kill the TP
processes.
Com Port might be locked by the the infrared port. Com Port might be defined
for the mouse ?
Compeo, Braeuniger Galileo
Why is my date out? Instead of 070804 it shows 080704 for
the track log.!!!!
Your computer date format is set to MM/dd/yy while it should be
dd/MM/yy.
The IGC track does not convert into a proper csv track and looks wrong.!???
Have a look at the IGC file with notepad or some other editor.
Are the B records all looking the same. Or are there some that have a
different length?
Delete the ones that look garbled.
And then convert again from IGC to csv and rescore the pilot.
Use some other 3rd party free code which downloads the IGC track and then
score in TP the IGC track.
See the Tips for COMPEO for some more
info .
MLR
- MLR Pilot number does not match error. It is a floating point to integer conversion problem. The pilot number becomes a floating point in the coordinate field. When converted back there is a rounding error and the number might be different from the clear text number.
- MLR time travellers. MLR time stamps tend to jump and come back from the future.
-32.4248454999179,18.7051857076585,471355327,0,1336
-32.4242373090237,18.7050439696759,471355332,0,1351
-32.423881245777,18.7054975982755,471355337,0,1372
-32.4235359113663,18.7057338003069,471355342,0,1390
-32.4235433712602,18.7059598602355,471355347,0,1403
-32.4237047228962,18.705501370132,471355352,0,1416
-32.4235274456441,18.7049245275557,471607261,0,1422
-32.4235274456441,18.7049245275557,471607266,0,1422
-32.4235274456441,18.7049245275557,471607267,0,1422
-32.4235274456441,18.7049245275557,471355429,1,1422
-32.4231554567814,18.7063109781593,471355434,0,1422
-32.4234962649643,18.7064540572464,471355439,0,1422
-32.4219959042966,18.7064850702882,471355444,0,1422
- Dec 2004 Bigair recommends to use Firmware level 2.70. 2.80 generates erroneous trackpoints.
Magellan
See the Communicating with a MAGELLAN for some more info , if that does not work , then use those tips here
- How do I load turnpoints into a Magellan? Use TP Convert/Gardown/Waypoint/csv>Gardown and create a gd file. Use GARTRIP, in Setup use Magellan 4800 device. Put Magellan into 4800 NMEA 2.1 Mode. Then write the turnpoints from the gd file to the Magellan
- How do I score a Magellan Sporttrak? Use Gartrip, download the track, save as pilotnumber.gd gardown format. Save the .gd file into the task pilotdata directory. Use TP/Convert/Gardown/Track gd>csv and create a pilotnumber.csv file. Then score the pilot in TP
- But Gartrip only gives me 500 track points in the trial version??? Use G7toWin instead from http://www.gpsinformation.org/ronh/ and save as gd or igc.
Log_It
- The current TP code only processes the 1st track log on a Log_It .
One can use the RobLog interface code which
comes with the RobLog logger code to process multiple tracks.
- USB Serial port can not handle baudrate changes
RobLog
- The current TP code only processes the 1st track log on a RobLog.
The RobLog interface code which comes with
the logger code can download multiple tracks.
If there is a problem that a pilot did not clear his tracklog, use the RobLog
provided code, then hand edit the file to cut out the track and then process
that one in TP
Conversions
- CSV>IGC why do I not see my xyz.csv file? Because the code looks for xyzTRK.csv. To avoid converting any none track csv files the name has to end with whateverTRK.csv. The code is based on the assumption that one wants to convert a track from a pilot in the comp to IGC.
- OZI plt output time is wrong. Maybe the Timezone offset is not correct?
RACE related
- GAP 2002 does not work. Yeah. Somehow GAP 2002 requires some extra info. We have to score using GAP 2000
Back to Index for TP Code