Volkslogger - Shut off the memory warning buzzer?

[BJen]

I fly with the sample rate on my VL set to give me about 9+
hours of data recording. That's sufficient for two normal
flights, and I usually dump it after every flight. However,
the thing begins complaining about low memory when it has 8
hours left, and it keeps complaining every few minutes. It
beeps and puts a message on that interrupts the display I
want to see. A few weeks ago it beeped about memory just as
I hit a turn, and I missed the turn beeps. I've tried
turning off warnings, but I can't seem to get this annoyance
fixed. Can anyone point me in the right direction?

[Ray Lovinggood]

Ah yes, the annoying beep for 'Only eight hours left!'
and this beeps every 256 seconds, or some such number.

This is the default setting for each time the recorder
is powered up.

To defeat the beeper, you can 'mash the buttons' and
kill that sucker. Let's see if I can do this from
memory (hah! I suffer from 'CRS')

Press (or mash, depends if you are an American living
above or below the Mason-Dixon Line) the top button
however many times it takes so the bottom line gives
you 'NAV INFO CFG1 CFG2' or something like that. You
need to select CFG1, I think. Then, select WRN (warnings),
Then select SND (sounds). Or maybe those two are backwards
(Lot of help, ain't I?) I believe at either SND or
WRN, you will find the selection for turning off the
annoying beeper.

It's there, you just have to find the proper key strokes.

Later, when I have a chance to sit down and play with
my Volkslogger, I could give you the exact steps.

Ray Lovinggood
Carrboro, North Carolina
(Down where we 'mash' buttons)

At 16:00 23 July 2003, Bjen wrote:
>I fly with the sample rate on my VL set to give me
>about 9+
>hours of data recording. That's sufficient for two
>normal
>flights, and I usually dump it after every flight.
> However,
>the thing begins complaining about low memory when
>it has 8
>hours left, and it keeps complaining every few minutes.
> It
>beeps and puts a message on that interrupts the display
>I
>want to see. A few weeks ago it beeped about memory
>just as
>I hit a turn, and I missed the turn beeps. I've tried
>turning off warnings, but I can't seem to get this
>annoyance
>fixed. Can anyone point me in the right direction?
>

[BJen]

Ray Lovinggood > wrote:

>Ah yes, the annoying beep for 'Only eight hours left!'
>and this beeps every 256 seconds, or some such number.
>
>This is the default setting for each time the recorder
>is powered up.

Are you saying that I need to kill this thing every time I
power up? I could swear I've turned off the warning beep in
the way you've described, but if it's resetting to default
on at every power up - then I may not have realized I was
correctly turning it off.

[Greg Arnold]

"BJen" > wrote in message
...
> Ray Lovinggood > wrote:
>
> >Ah yes, the annoying beep for 'Only eight hours left!'
> >and this beeps every 256 seconds, or some such number.
> >
> >This is the default setting for each time the recorder
> >is powered up.
>
> Are you saying that I need to kill this thing every time I
> power up? I could swear I've turned off the warning beep in
> the way you've described, but if it's resetting to default
> on at every power up - then I may not have realized I was
> correctly turning it off.

Yep, every time you power up. If you have two batteries, and change during
flight, better do quickly or the beep will be back.

[Jim Skydell]

Yep, you have to do this each time. I pasted the sequence of keystrokes
needed to do so on the face of the logger. I have had some discussions
with Garrecht regarding changing this nuisance. I don't recall the
details of what was said, but they consider this a very important
feature, and have no intent to change it.

[Dave Nadler \YO\]

You really do need to reset this warning every time it is
powered up. Garrecht says nobody ever complains about this,
so PLEASE everybody send him an email explaining how
stupid and annoying this is !
Best Regards, Dave

"BJen" > wrote in message
...
> I fly with the sample rate on my VL set to give me about 9+
> hours of data recording. That's sufficient for two normal
> flights, and I usually dump it after every flight. However,
> the thing begins complaining about low memory when it has 8
> hours left, and it keeps complaining every few minutes. It
> beeps and puts a message on that interrupts the display I
> want to see. A few weeks ago it beeped about memory just as
> I hit a turn, and I missed the turn beeps. I've tried
> turning off warnings, but I can't seem to get this annoyance
> fixed. Can anyone point me in the right direction?

[Greg Arnold]

"Dave Nadler "YO"" > wrote in message
...
> You really do need to reset this warning every time it is
> powered up. Garrecht says nobody ever complains about this,
> so PLEASE everybody send him an email explaining how
> stupid and annoying this is !
> Best Regards, Dave

It is the one bad feature of the VL (besides the incomprehensible menus).

[Mike Borgelt]

On Wed, 23 Jul 2003 11:29:59 -0400, BJen
> wrote:

>I fly with the sample rate on my VL set to give me about 9+
>hours of data recording. That's sufficient for two normal
>flights, and I usually dump it after every flight. However,
>the thing begins complaining about low memory when it has 8
>hours left, and it keeps complaining every few minutes. It
>beeps and puts a message on that interrupts the display I
>want to see. A few weeks ago it beeped about memory just as
>I hit a turn, and I missed the turn beeps. I've tried
>turning off warnings, but I can't seem to get this annoyance
>fixed. Can anyone point me in the right direction?


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.

If this feature was permanently disabled people would complain about
running out of memory without warning and it has to be set for 8 hours
or so to capture 99% of flights which might be done with the warning
up.

Mike Borgelt

Borgelt Instruments

[Joe Simmers]

Are you saying that I need to kill this thing every time I
> power up?

I also have a volkslogger and find I must turn this off every time I fly, or
I get the annoying beeping, If anyone knows how to disconnect this beeping
another way I would like to know!

Joe Simmers
asw19b

[Owain Walters]

Not as bad as running out of memory half way round
a badge or even worse a competition flight. I have
mine on 12 secs logging. It always takes a fix when
I get to the TP radius.

Change your sample rate to 12 or more. Your problem
will dissapear!

>It is the one bad feature of the VL (besides the incomprehensible
>>menus).
>
>
>

[Mark James Boyd]

>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

[Mike Borgelt]

On Thu, 24 Jul 2003 23:16:21 GMT, "Dave Nadler \"YO\""
> wrote:

>Remember, if you set a long time between samples, you will
>likely receive less than full distance credit with area turns...
>Best Regards, Dave
>
>
Presumably when you make for the next turnpoint you have actually made
a decision - so mark the point.

Mike Borgelt

[Mike Borgelt]

On Fri, 25 Jul 2003 10:54:23 +1000, Mike Borgelt
> wrote:

>Presumably when you make for the next turnpoint you have actually made
>a decision - so mark the point.
>
>Mike Borgelt


This also can make the scoring software work properly. The Aussie
scoring automation has a flaw I'm told. It assumes you are going to
the next turnpoint when the distance to it starts decreasing once you
are in the first TP area. If you think about this this ain't
necessarily so and can result in lots of distance not credited.

Marking the point where the pilot has made the decision and doing the
measurements between these points avoids this problem.

Mike Borgelt

[dhb]

I like the Colibri. Lot's more memory. Used in a "circular" type scheme. The
oldest data is over written. So you don't lose the current flight when you
fill up the memory, you lose the oldest flight. I set mine to a 2 second rate.
At that rate I can fly a long time before I lose a flight. Somewhere around
10.5 hours. There are a lot of other things that I don't like - but the memory
usage is one of the main reasons that I chose it over the competitors.
Dennis Brown


In article >, (Mark James Boyd)
wrote:
>>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
>
>

[Bert Willing]

I agree. I run a Colibri wth 2 sec intervall, and I have 29h of memory. The
other features of this bix are rather a pain, but that's what my
Ipaq/GPS_Log is for.

Bert

"dhb" > a écrit dans le message de
thlink.net...
> I like the Colibri. Lot's more memory. Used in a "circular" type scheme.
The
> oldest data is over written. So you don't lose the current flight when you
> fill up the memory, you lose the oldest flight. I set mine to a 2 second
rate.
> At that rate I can fly a long time before I lose a flight. Somewhere
around
> 10.5 hours. There are a lot of other things that I don't like - but the
memory
> usage is one of the main reasons that I chose it over the competitors.
> Dennis Brown
>
>
> In article >, (Mark James
Boyd)
> wrote:
> >>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
> >
> >


------------ And now a word from our sponsor ------------------
Want to have instant messaging, and chat rooms, and discussion
groups for your local users or business, you need dbabble!
-- See http://netwinsite.com/sponsor/sponsor_dbabble.htm ----

[Kirk Stant]

That's why I like the big old PrintTechnik GR1000 - Lots of memory so
can run several flights at 2 seconds, and it even shows the memory
available on the display when powered up so it is easy to erase when
full before a flight.

Another nice reason to run 2 seconds (aside from not having to spend
time programming the task in the logger) is that it makes the SeeYou
3d flights really smooth and fun to watch!

The last thing we need is another heads-down action (marking a
position) in the OZ, during a turn!

Now if someone would please put out a simple little Windows program to
download the GR1000, so I can use XP instead of DOS! I've have to use
my old Win98 PC booted to the DOS prompt to get reliable downloads,
and have not been able to get a successful download from an XP or
Win2000 machine yet.

How about it, SeeYou, please?

Kirk
66

[TwoZulu]

I still regret that I am not trusted to make my own decisions.
Please let us make the terribly dangerous decision to turn off the #$!^&^#!#
beeping!

Sorry, I get that way after spending too much time listening to incessant
beeping.

Bob

"Kirk Stant" > wrote in message
om...
> That's why I like the big old PrintTechnik GR1000 - Lots of memory so
> can run several flights at 2 seconds, and it even shows the memory
> available on the display when powered up so it is easy to erase when
> full before a flight.
>
> Another nice reason to run 2 seconds (aside from not having to spend
> time programming the task in the logger) is that it makes the SeeYou
> 3d flights really smooth and fun to watch!
>
> The last thing we need is another heads-down action (marking a
> position) in the OZ, during a turn!
>
> Now if someone would please put out a simple little Windows program to
> download the GR1000, so I can use XP instead of DOS! I've have to use
> my old Win98 PC booted to the DOS prompt to get reliable downloads,
> and have not been able to get a successful download from an XP or
> Win2000 machine yet.
>
> How about it, SeeYou, please?
>
> Kirk
> 66