Markoz wrote on Aug 31^st, 2010 at 7:58am:


Yes they did, and thats how I meant it...  We WILL get INS in VC. Should have written it a bit different though. Actually cant wait for this to happen. 

Finally got the doppler to work without loading a flightplan. The 707 follows the first leg programmed to "A" perfectly. But the second leg programmed to "B" always calculates a wrong course on the map, e.g. when I tune in course 330 in "B", the plane will turn to HDG050... �

TheFinn wrote on Sep 1^st, 2010 at 6:47pm:


That is because it would seem the Doppler calculates both legs with the same point of origin, i.e your position when you activate the doppler. I beleive that is also why people got the 'miles to go' reading resetting down to 0 if their miles settings for leg A was longer than leg B. When setting up leg B, the miles to go should be leg A + leg B.

A : 50Nm 180 and B : 50Nm 90 will not create a L shaped flightplan but a V shaped one.

Cheers

Nico

The fact remains that when I set up the routes, the first time I switch to either A or B the distance resets to 13 miles and I never do get any route on the map.  This is before I even take off.  I have applied the fix.  It didn't help.  As far as I can tell, DNS is broken.  But whether you designed it that way or not, it does a dandy job of importing a whole flight plan lol

Yes it is working, except the course of the second leg is totally wrong (see my post)! For example:

1st leg programmed to "A":
Course: 300 Distance 20 miles

2nd leg programmed to "B":
Course: 330 Distance: 20 miles


The first leg works fine (in AUTO mode), and it switches to the 2nd leg automatically. BUT, now instead to turn to the programmed course of 330, the plane turns to a HDG of 050.  Even the leg on the map shows the wrong direction.... Thats some sort of wierd!

Tim Capps wrote on Sep 7^th, 2010 at 11:37am:

Hi Tim.

You MUST turn the Stage Selector to A AFTER you turn the Control Switch to MAN or AUTO. If you turn the Stage Selector to A before you turn the Control Switch to MAN or AUTO, it will reset the miles to 0 (zero).

More woes though!

I just did a flight from YMML (Melbourne) to YSSY (Sydney). I set A to 45^o and 372 miles and I set B to 5^o 10 miles. This should have given me a flight path to out over the coast off of Sydney then a 30^o intercept for ILS 34L. As the flight progressed, the heading slowly move to 38^o (instead of 45^o) which put me on the coast at Sydney, with an intercept on ILS 34L near impossible. Then, when I got to the start of B anyway, it turned to a heading of 225^o with a distance of 372 miles. It was returning me back to Melbourne!

On the other test I was doing, from Seattle, I set it all up on the ground just prior to takeoff. As soon as I turned the A/P to NAV, it turned to intercept the course. With my Melbourne to Sydney trip, it refused to set while I was still on the ground. It worked fine once I was airborne. It's sure got me beat.

Mark

Hi Tim.

I'm doing another flight at the same time as I'm writing this. YMML to YSSY again (because it's only 1 - 1.2 hours). I couldn't get it to accept the plan until airborne again! I am getting A to work (364 miles 45^o). B probably wont (12 miles at 12^o). I'll know in an hour. 130 miles down the track and my heading is now 43^o which looks like it wont get me far enough off the coast to enable a good ILS intercept.

After this. I'm going to try from the 707-300 Cleared for takeoff (KSEA) flight, and see if I can start it whilst on the ground, again, like the first time.

Mark

EDIT-Sep 7^th, 2010 at 2:09pm: I have just finished the flight. Have a look at the image. If you look closely at it, the B route line (white) is running back in the opposite direction to the A route line. Look at what I have entered for B though! After reaching the end of A, B changed to 360 miles to the south instead of 12 miles north.