A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Soaring
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Volkslogger - Shut off the memory warning buzzer?



 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #10  
Old July 24th 03, 07:51 PM
Mark James Boyd
external usenet poster
 
Posts: n/a
Default

Set the sample rate to one very 10 to 12 seconds or so. Even 20 isn't
unreasonable and this problem goes away. The sample rate automatically
increases in the OZ anyway. There is no really good reason to sample
more than 5 or 6 times a minute except in the OZ. Reduces download
time and file size too.


Since I don't ever use any waypoints in the VL (because it will
then self-declare if there is a power interruption, can be
awkward to explain) my sample rate
is always the same. I use 9 seconds, because I recall
in the FAI docs (section 3c 7.1b) about a 10 second
sample rate for records/badges. This is the most frequent
rate I've seen in any doc, so I use it and it's frequent enough to
show an unambiguous 360 off tow and good OZ penetration,
yet long enough to ensure recording all day long without the
annoying lowmem beeping.

The FAI docs mention that a power interruption can be
overlooked if a good interpolation of the course is done (3c 13.8),
but these same documents also mention the latest declaration made before
takeoff is the valid one (section 3 4.4.2 a). It's
a little hard to explain if you have two traces with different
declarations because of an in flight power interruption...

So I use 9 seconds, enter no course and no waypoints,
and make sure the memory is cleared each day. Then I do all
written declarations (this is great too since I always have
a valid declaration for every flight, even if it's a year old,
and I don't have to fool with the VL). I then use a moving map Pilot III
GPS for course and waypoints, and reference the VL only for
altitudes recorded. So far I've had no discrepancies greater
than 50 feet between the VL and Pilot III GPS. I was
once grateful I checked the VL altitude, as the pressure alt
recorded was too low for the badge I wanted, and I spent
another 30 minutes climbing an extra 400 feet to the tippy top
of the thermal to make sure I was high enough for the VL.

I can't recommend ever using the VL for anything other than vertical
navigation. There are too many other products out there which
do a better job for horizontal navigation and are much more user
friendly.

Mark Boyd


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Has Southwest Airlines banned aspartame from the cockpit? Dylan Smith Piloting 42 August 31st 04 03:10 PM
For Keith Willshaw... robert arndt Military Aviation 253 July 6th 04 05:18 AM
S-TEC 60-2 audio warning Julian Scarfe Owning 7 March 1st 04 08:11 PM


All times are GMT +1. The time now is 11:26 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.