Hi! I posted this on the SimBrief forum 9 days ago but disappointingly haven’t had any response:
"Hi! My Simbrief has always worked with Prosin A320 without problems but today I got the above error message in the MCDU when trying to import the Flight Plan. I checked and my Simbrief Pilot Number is still entered in the Prosim systems configuration. I tried generating a different flight plan but got the same message.
I just updated to 2407 AIRAC. If I understand this correctly from 2407 Navigraph introduced a new navigation database for Prosim users and publicised this in your 2407 Newsletter. It seems the major change was to shift to DFD (=Digital Flight Data). I’m wondering (from reading the Prosim forum) if that shift seems to have caused incompatibility issues? Does anyone have any ideas how I can fix this?
Thanks, Rich"
A user on the Prosim Forum suggested it was “Probably a problem with the DFD format.” Following other advice on the ProSim forum I updated Prosim to the latest pre release (1.67b12) and deleted and reinstalled the 2407 Navdata files but unfortunately I get the same error message. I’ve managed to revert both Simbrief and Prosim to - the last version that worked for me - 2405 (by moving all of the files out of ProgramData\Prosim-AR\Navdata and running the 2405 manual update). I just tried and the flight plan loads from Simbrief into the Prosim A320 MCDU as usual.
The route string I was using was EGGD/27 N0451F370 HAWF1X HAWFA L607 ALHAD UN859 VAPID L18 MID UL612 RESMI UM728 KETEX DCT KOTIS DCT KUKOR DCT UTUVA DCT LERGA DCT LIQID UY30 LATAM UY22 NISAR NISA7T LFMN/04L. I did notice that in the Prosim log file it said “Simbrief:No route between LIQID and LATAM on UY30” I tried two other routes from Simbrief - one worked the other gave this INVALID F_PLN UPLINK error. I am using Skalarki hardware.
I am a long time user of Navigraph and a subscriber to your full service, but there isn’t too much point in continuing if I have to freeze my data at 2405 - (except for access to Charts which I love!)
Do you have any suggesstions as to how I can solve this issue.
In general, the DFD is only a format change but no data change. The source itself is exactly the same as in the data structure before - it is only a new structure, which was implemented many months ago by ProSim.
So, the data structure change can’t be really the reason - at least, when ProSim has implemented the new structure correctly. Again the source to build the old and new format is 100% the same.
Ok, now I have checked the ProSim DFD format (AIRAC 2407), specially your example with the UY30 between LIQID and LATAM. This segment is valid for both directions. Here direct from the ProSim DFD 2407 database:
You see the direction restriction … at LIQID it´s NULL and from LATAM it´s only a forward airway. That means, LIQID ↔ LATAM should be possible, but the next segment from LATAM to MTL this is only a one-way LATAM → MTL.
You see this also very clear in our charts:
Segment: LIQID ↔ LATAM (both ways possible)
So, the data are correct - as conclusion, I assume it´s a bug in the ProSim implementation, due the NULL in the direction-restriction column at the LIQID waypoint. Fact is, that the data are consistent between SimBrief, our charts and also in the ProSim DFD database. I don´t see any data issue here sorry.
You can forward this analysis to ProSim if you want. I´m pretty sure, that this is an implementation issue of the new format in ProSim, sorry.
Just to report back Prosim support have solved my problem. They advise that “A definitive fix is not yet applied to the A320 releases. This is just a workaround before a new version is released.”
The solution is to go to C:\ProgramData\ProSim-AR\Navdata and delete NavData.dat, NavData_Stby.dat and ng_jeppesen_prosim.s3db. I just tried it and that fixed it for me.
Ah ok, thanks for the update Rich - that means you are not using the current cycle, because ProSim goes back to the cycle which was in the setup - as fallback.
Hi Richard. I’m getting out of my depth technically here but I don’t think so. Both Prosim System and Prosim Instructor Station show AIRAC 2407 and the 2407 based flight plan from Simbrief uploaded OK into Prosim. I didn’t delete the nd.db3 file from 30/06/24 in the C:\ProgramData\ProSim-AR\Navdata folder, so its presumably getting the data from there. Each time there is an AIRAC update Prosim System runs a database conversion at start up so that may produce the nd.db3 file.
Rich
