reported earlier How the "GSPD Entry" work in conjunction with TOT?

[nickos86]

I've entered the TOT and GSPD for a target waypoint (selected it as TGT - it had a white square around it). It wrote a constant GS on the HSI instead of giving me the required GS I need to keep in order to be on time at the waypoint.

Does the GSPD works? Is there a know bug? Should I do something differently? 

 

Thanks. 

[Swift.]

The way GSPD used to work at least, is that it sets a fixed target GS for the waypoint sequence leg immediately preceding the target waypoint. What you might be seeing is what happens when you dont have a preceding leg? Do you have more than one or two waypoints in this flight plan?

[nickos86]

0-1-2. the TOT was for waypoint 2.

BTW, I've kept the speed until waypoint 1 as instructed by the HSI. Then switched to waypoint 2 and accelerated per the desired speed. Because it was the leg of the bomb run, I pressed 'WPDSG' and it completely changed the speed.

 

Seems like at the waypoint before the TGT you need to press WPDSG in order to get 'live' GS requirement. In WAYPOINT - it stay constant on the HSI   

 

[Swift.]

Are you assigning wpt 2 as the TGT in the SEQUFC menu?

[nickos86]

Yep. 

Flew to waypoint per the speed the HSI gave me. At waypoint 1 pressed the WPDSG and it brought the required GS in the HSI way below the desired speed I've entered (520). I guess that the WPDSG calculated the correct speed required to be on target on time. Without the WPDSG - the speed stays 520 const. 

[Swift.]

Interesting, I thought it should automatically designate the TGT assigned waypoint when you approach it. You have a track or something we can take a look at?

[BarTzi]

Here's a track showing it in action.

 

It's a two waypoint sqeuence, so you can speed it up.

 

You will notice that hitting WPDSG changes the required speed presented by the HSI (in this case by 5 knots). It seems that without pressing WPDSG on time, you will not get accurate information in your last leg. I'm not sure why WPDSG makes a difference here.

 

 

wpdsg tot.trk

[BIGNEWY]

We do have a report open for errors with TOT I have added the track and noted this issue also. thank you