Even after 12 years of active service, the point needs to be HAMMERED into folks, 
that once started, KIWI-OSD needs to left to run for at least 15 minutes, and the 
Reset button pressed twice before using KIWI-OSD to time an event. Pressed once 
(after 15 minutes), to allow plenty of time for a current GPS almanac to be downloaded, 
getting either; “Previous times ok”, OR “Error: use field count” messages, and pressed 
again to restart KIWI-OSD.

Even then, it’s a good idea to record the entire 2nd restart sequence and a couple 
of seconds of time display.  Then should KIW-OSD display an unexpected 
“Error: use field count” message, at least you’ll have some video fields with good timings 
that is a basis for counting fields, thereby salvaging your observation.

Further, from an email:

Start the clock once the time display starts.  The download of the current almanac 
should take 12.5 minutes (Max.),provided the GPS has a good signal throughout.   
The established practice is to make Kiwi the first thing you setup and get going.  
Once you have the scope going, Kiwi would have completed it’s housekeeping, then simply 
press the reset button – twice and you should be good to go.

If one gets the "Error: use field count" message then what is the procedure to obtain accurate timings?  
We are told we must use the procedure but it isn't given anywhere.

The procedure is to;

- Start Kiwi
- Wait at least 15 minutes
- Reset, reset and record the startup sequence and a couple of seconds to calibrate the field counter to UT.
- Observe
- At the end of the observation press reset again. 
  - If you get a “previous times OK” then the observation times are ok.
  - if however you get an “error use field count” message, then you have to refer back to the calibration 
     recording and use the field counter.  NTSC video runs at 59.94 fields per second.   
     PAL runs at 50 fields per second.   Simple math should give you the duration between calibration and event times.