Results 1 to 3 of 3

Thread: How to apply a push time to relative DTOTs

  1. #1

    How to apply a push time to relative DTOTs

    It appears that the CDU has a nifty little feature buried in its GPS time settings. If you have a set of waypoints you need to hit at a certain time, DTOT is an excellent feauture that gives you desired airspeed and early/late time of arrival on the HUD.

    Normally you'd need to know the push time to set the WP's DTOT, and do the math adding the push to the relative time.

    You can actually punch in all the relative times in the WPs on the ground. Once the push time is known, go to SYS > GPS > TIME, type the time in HHMMSS format in the scratchpad, and hit LSK1 (DTOT OFFSET). All the WPs in the DB with a DTOT set will be updated with the inserted time added.

  2. The Following 6 Users Say Thank You to Gliptal For This Useful Post:

    Emmy (24May19), ExNusquam (30May19), Hiccup (25May19), Kimi (07Jun19), Scaley (25May19), Snoopy (25May19)

  3. #2
    76th vFS Pilot Emmy's Avatar
    United States
       United States
    Join Date
    Jan 2018
    Posts
    430

    Awards Showcase

    Thanks Thanks Given 
    489
    Thanks Thanks Received 
    279
    Thanked in
    142 Posts
    We discovered during last week’s FN that you can do a UTC offset in the CDU and it does change the clock in the cockpit but this takes things to a whole different level!

  4. #3

    Da FAC?


    476vFG GC
    Founding member
    Stuka's Avatar
    Belgium
       Belgium
    Join Date
    Mar 2012
    Posts
    8,190

    Awards Showcase

    Thanks Thanks Given 
    1,239
    Thanks Thanks Received 
    5,652
    Thanked in
    2,482 Posts
    Quote Originally Posted by Emmy View Post
    We discovered during last week’s FN that you can do a UTC offset in the CDU and it does change the clock in the cockpit but this takes things to a whole different level!
    Looked a but further into this: we can use the trick as we did last week/yesterday to have ZULU time displayed in the aircraft, but the implementation is actually not correct.
    The main bug is that the A-10C takes the time as set in the editor as ZULU, and shifts that timezone to your location.

    Test on Tbilisi (GMT+4)
    Editor set to 08:00.



    The A-10C shows on the time page that GMT time is 08:00:00. That's where it goes wrong, it should show 04:00:00.



    Also, the time page is showing a wrong local time after adjusting the time. If I say that the local time is 4 hours ahead of GMT, I need to set +400. When doing that, the local time jumps to 16:00:00, making no sense at all (one would expect 12:00:00).


    It looks like he does GTM+(2xLCL ADJUST). When telling the we are in GMT+5, he indeed jumps to 18:00:00, confirming this.



    Ofcourse, while manipulation the ADJUST setting, we can match the time being shown on the clock, CDU, HUD,... with the correct ZULU time, but it remains wrong.
    In this case, I can set -200, and my displayed times in the systems will start matching the ZULU time in the Hornet.




    The Hornet however, shows the LOCAL time being 08:00:00, and when switching to ZULU time, it shows correctly 04:00:00





    Interested to see on how other aircraft show time.

    Providing CAS when you're all out of HUA!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Like our website?

You can help us by donating to cover our costs.

Many sincere thanks!


Search

Follow us

Twitter Twitter youtube iTunes Subscribe to our Podcast