Jump to content

Recommended Posts

Posted

After some (self induced) errors yesterday, I think it might be useful to publish a few thoughts on the AIRAC cycle. As is known aviation data is published in cycles of 28 days, always starting on a Thursday, I believe 0900UTC. 

Yesterday 24 March was such a date when cycle 2203 came into force.

  • download your data file with the Navigraph FMS Data Manager
  • Startup the CL650, and IMPORTANT - tick the box  to 'Use real world date and time'
  • If you don't you'll mess like me, having a date in the PAST cycle : unable to download the Simbrief FPL, STATUS of the database staying yellow 
  • Don't try to change the date in the FMS STATUS page, it led to a CTD with me
  • In the STATUS page cycle the OLD for the NEW database 

And you are good to go 

These are the next cycles for 2022

image.png.80df6bb4ec304b69a42c04d9881b3499.png

Posted

Hi Rastuasi, CTD happened after I tried to verwrite the data in the STATUS field, not by not having teh correct database.

But what defintely did not work for me was RECALLING the Simbrief Flightplan with a sim date that was outside of the Navdatabase date field . When I changed the sim date to fall within the Navdatabase period , I was able to recall again. Odd? 

Posted
1 hour ago, FYG001 said:

Hi Rastuasi, CTD happened after I tried to verwrite the data in the STATUS field, not by not having teh correct database.

But what defintely did not work for me was RECALLING the Simbrief Flightplan with a sim date that was outside of the Navdatabase date field . When I changed the sim date to fall within the Navdatabase period , I was able to recall again. Odd? 

The CTD was reported to the CTD forum I assume?

I believe the flight plan uplink checks the nav data cycle used in Simbrief against what’s loaded in the sim to ensure referential integrity.

Posted
1 hour ago, FYG001 said:

Hi Pils, sorry no, I did not report the CTD in the CTD forum, it was such a stupid move to try to overwrite the date that I did not deem it right to report ;-)

If you don’t mind reproducing it then please do. Any crash is one we want to hear about.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...