OnCourse Software

Welcome to our Product Support Forums

still TOD too early

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 1 of 1  [ 4 posts ]
Author Message
mllgrennman
Post subject: still TOD too early
Posted: Wed Mar 15, 2017 9:48 pm
Offline
 
Posts: 393
Joined: Mon Feb 16, 2015 6:28 pm
 
FL 220...Cruise speed 300 kts...TOD should be +/- 66 miles.

ATC gave me TOD at 160 miles to destination.

I had last waypoint at 30 miles from destination and set to 10,000 ft at that waypoint.

What am I missing?

Attachments
logs.zip
(901.47 KiB) Downloaded 173 times


Top
Profile Quote
Dave March
Post subject: Re: still TOD too early
Posted: Thu Mar 16, 2017 12:07 pm
Site Admin
Offline
 
Posts: 6197
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Sorry but I can't see anything wrong here. As you approached IV you had 136 miles to go to CZMN which you'd set to 10,000'. PF3 generated its step descents at 17,000, 14,000 and 10,000. ATC then instructed you to descend to 17,000' at pilot's discretion!

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
Dave March
Post subject: Re: still TOD too early
Posted: Thu Mar 16, 2017 12:33 pm
Site Admin
Offline
 
Posts: 6197
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Just had another look at this and I can see there was in fact a problem. After ATC gives 'at pilot's discretion' descent we monitor to determine if and when you actually do commence that descent. If you don't commence your descent within a given time then you will be gently reminded to do so. This timer is set dependent on a couple of things, one of which is if you have or have not reached your calculated TOD. If you have then the timer is set to the user-setting nag time X 5 + 60. So yours is set to 120 seconds which would be reset to 660 or 11 minutes. If you're not yet at the TOD then the timer would be set to an even longer period before you are reminded about your descent.

I've just noticed this timer is not working correctly, which is why you received a reminder after just two minutes even though you had been give a 'at pilot's discretion' call.

This has now been fixed and will be in the next release.

Incidentally we are currently beta testing as I write! :)

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
mllgrennman
Post subject: Re: still TOD too early
Posted: Thu Mar 23, 2017 1:42 am
Offline
 
Posts: 393
Joined: Mon Feb 16, 2015 6:28 pm
 
thanks for the heads-up...ive been successful at getting the optimal TOD call by better flight planning and programming...this was a problem for me in the past...thanks again!


Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 1 of 1  [ 4 posts ]
Return to “PF3-ATC at its best”
Jump to: