See You : "Task Not Finished"

No Mark, if you look at the noise trace it is reasonable, and at the
'photo landing' time noise is relatively low. The problem is clearly
the setting of the TP zone radius, and the 'photo landing' is at the
closest approach to the waypoint, since the flight path never enters the
zone within the radius set.

In SeeYou, go into Edit/Flight Properties/Observation Zone. Change the
two waypoint radii from 3km to 30km. The flight is now analysed as
completed at a speed of 82.58 kph.

Interestingly, the analysis also shows that every thermal was turning
right.

I have seen traces where SeeYou interprets a noise peak (due to opening
the DV panel for extra ventilation) as an engine run, but this isn't one
of them.

At 11:00 11 November 2008, Mark Dickson wrote:
I don't think the problem is with Seeyou, I think the problem is with
your
302. I often get a similar result from Seeyou using a 302. The problem
is
with the engine noise detector; despite having a pure sailplane the 302
is
too sensitive and picks up noise that is assumed to be engine noise by
Seeyou. Next time you open one of your flights in seeyou, right click,
select flight properties and check pure glider.
There is a modification that Dickie Feakes (UK) does to the 302 to solve
this problem; maybe you have someone in the US that can do the same.

I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

On Nov 11, 7:30*am, Big Wings wrote:
I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

I believe this is a known problem and I expect Naviter will be fixing
it. However if you set the correct UTC Offset in ToolsOptionsGeneral
this won't happen.

Darryl

On Nov 11, 7:41*am, Darryl Ramm wrote:
On Nov 11, 7:30*am, Big Wings wrote:

I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

I believe this is a known problem and I expect Naviter will be fixing
it. However if you set the correct UTC Offset in ToolsOptionsGeneral
this won't happen.

Darryl

NOT UTC, NOT 302A!
Problem was fixed by increasing the Observation zone radius in See
You, under 'Tools' / 'Options' / 'Observation zone'
Many thanks to 5Z (Tom) and everyone else who looked into this!

On Nov 11, 8:31*am, Uncle Fuzzy wrote:
On Nov 11, 7:41*am, Darryl Ramm wrote:



On Nov 11, 7:30*am, Big Wings wrote:

I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

I believe this is a known problem and I expect Naviter will be fixing
it. However if you set the correct UTC Offset in ToolsOptionsGeneral
this won't happen.

Darryl

NOT UTC, NOT 302A!
Problem was fixed by increasing the Observation zone radius in See
You, *under 'Tools' / 'Options' / 'Observation zone'
Many thanks to 5Z (Tom) and everyone else who looked into this!

I should have been clear, Tom clearly had nailed it, but the UTC
offset will catch people if a flight wraps as Big Wings reported. It
may not be an issue, or you may have the offset set correctly in
SeeYou on your PC. This comes up when people view a flight trace from
a different timezones, and may need to reset their UTC offset to work
around this.

Darryl