More Glide Nav 2 questions - Need technical advice

Paul & Andy - that answers alot....thank you very much!

Andy, regarding Q3:

At the R4S contest, there were some people who drove in and gave the
GPS coordinates for a nice big open field to land it. I would have
loved to entered this into my GPS so I could see it on the moving
map. But, I had no idea who to do that, so throughout that primarly
unlandable area....I just flew as high as I could without taking
chances. I could have pushed the limit a little harder with that
specific knowledge of where the field was. The GPS could have pointed
me to an exact heading, and an exact distance.

Maybe there's a way to enter this into Glide Nav 2 easily?

On Mar 8, 3:17*pm, Scott Alexander
wrote:
Maybe there's a way to enter this into Glide Nav 2 easily?

The only way I know is to append it to a turnpoint file. GNII will
allow multiple TP files to be used at the same time. Rather than edit
the official contest file which could be subsequently updated by the
organizers, I'd suggest creating your own file in the same format and
adding your own landables to that file. Suggest you start with a
known good file.dat, add the new data in the same format, then delete
the original data. You can use the PDA editor to do this but I find it
easier to transfer the CF (or SD) card to a PC and do the edits
there.

Be sure to use the correct designation and altitude for the landable
points if you want to get valid glide data.

Andy

On Mar 8, 5:52*pm, Andy wrote:
On Mar 8, 3:17*pm, Scott Alexander
wrote:

Maybe there's a way to enter this into Glide Nav 2 easily?

The only way I know is to append it to a turnpoint file. *GNII will
allow multiple TP files to be used at the same time. Rather than edit
the official contest file which could be subsequently updated by the
organizers, I'd suggest creating your own file in the same format and
adding your own landables to that file. *Suggest you start with a
known good file.dat, add the new data in the same format, then delete
the original data. You can use the PDA editor to do this but I find it
easier to transfer the CF *(or SD) card to *a PC and do the edits
there.

Be sure to use the correct designation and altitude for the landable
points if you want to get valid glide data.

Andy

best practice: add new waypoints in SeeYou on a laptop, then d/l new
file to your Nav devices. there are certainly other ways to
accomplish the same task, but this is the one that catches and
corrects most potential problems. Obviously, this is something you
practice in the off season ;-).

-Evan Ludeman / T8

Scott, I hope you won't mind much if I also ask a Glide Navigator II
question:

How do you set it up to glide around two points?


Thanks,
Ray Lovinggood
Carrboro, North Carolina, USA

On Mar 8, 8:49*pm, rlovinggood wrote:
Scott, I hope you won't mind much if I also ask a Glide Navigator II
question:

How do you set it up to glide around two points?

Thanks,
Ray Lovinggood
Carrboro, North Carolina, USA

Uh, let me correct that: Glide around ONE point.

Thanks,
Ray
(Don't think the LS1 has quite enough L/D to make a glide around TWO
points in the area where I fly...)

Hi Ray,

Enter a task into GN II. Start flying the task. While navigating to a any
turnpoint in the task - touch the name of the active waypoint to pop-up the
list of turnpoints in the task. When the list is visible you will also see
a button on the right side of the screen labeled "To Finish". Most people
don't notice that button is there. It is only visible when the task list is
"popped-up". If you press the "To Finish" button the active waypoint window
will then show "Glide To Finish". GN II will still be navigating to the
turnpoint you were previously navigating to (a line is drawn from your
current location to the turnpoint - not to the finish), but the final glide
number will be from your current location, around all the remaining
turnpoints to the finish. If you find that you still need a lot of altitude
and want to again see the final glide to the turnpoint you are navigating
to, then touch the active waypoint button to pop up the turnpoint list and
select the turnpoint you are navigating to. It really is very intuitive -
once you notice the "To Finish" button and know what it does.

Best Regards,

Paul Remde
Cumulus Soaring, Inc.

"rlovinggood" wrote in message
...
Scott, I hope you won't mind much if I also ask a Glide Navigator II
question:

How do you set it up to glide around two points?


Thanks,
Ray Lovinggood
Carrboro, North Carolina, USA

Thanks Paul,

I thought "To Finish" in that application meant to head for Finish at
that time, thus bypassing any remaining turnpoints. That would be as
in a MAT when you have decided you've flown all the turn points you
can, and you're not going to attempt others, and you want to head
home.

I hope I can try this out soon!

Ray

On Mar 9, 6:43*am, rlovinggood wrote:
Thanks Paul,

I thought "To Finish" in that application meant to head for Finish at
that time, thus bypassing any remaining turnpoints. *That would be as
in a MAT when you have decided you've flown all the turn points you
can, and you're not going to attempt others, and you want to head
home.

I hope I can try this out soon!

Ray

Be careful here, however. To display "glide to finish", GNII needs to
understand exactly which turnpoints you've been to, and which ones you
still have to complete. If -- as we always do -- you punch in a few
alternatives as you end a MAT, trying to figure out a sequence which
will use up the available time, it is very easy for GNII to get
confused, and not know which turnpoints have been completed and yet to
go. If you punch in a few "glide to" options on the way, that can also
confuse it as GNII sometimes uses that as a signal that you have
indeed rounded a last turnpoint.. For example, suppose you're flying
over A on the way to turnpoint B, and A is the turnpoint following B.
You get low and wonder if you can make it back to A so you punch
"glide to A" as a landpoint. This tells GNII that you turned B, even
though you haven't.

Alas GNII does not (yet!) have a manual override on which turnpoints
have/have not been reached, so sometimes the only solution is to kill
the whole task, and then start a new one, with only the remaining
turnpoints.

John Cochrane