Hello,

After following the procedure to convert the P2ADynamicData.mdf file to a P2ADyamData.db file, 
I received an error as shown in the attached screenshot. 

Thank you for your help.

François.

 

Hello,

Is there anyone who can help me?

How do I use the latest version of Airac without converting?

Thank,

Download and install the Full version of P2A again.  You can just install it over what you have now so you will get a working database.

Then use the Navigraph Auto Update button in the DataMnt utility, Data Updater tab.  

Dave

I'll try this this weekend and let you know if it works. 

Thanks so much for your help.

Hello Dave,
As promised, we implemented your suggestion, and the update went through correctly.

We have another problem. We are working with P3D V3 and IFLY. 
We added the voices as indicated on the website. We have followed the tutorials several times regarding creating a flight plan, 
but when we connect to the simulator, the radio panel activates after a few seconds, which is normal. However, out of about ten
 attempts, we have had normal communication with ATC once or twice, and in other cases, 
nothing happens. It is impossible to change the radio frequency, either from the Pilot2ATC 
interface or the simulator interface. No sentence suggestions appear, and no radio. Communication seems to be working since 
the aircraft's position on the map is correct. 
We have also enabled the 'Ignore Avionic Switch' and 'Ignore Battery Switch' options. 
I'll add the log file if it helps your analysis.
Thank you for your help.

Quote

2025-08-31 12:06:45.0001|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|Program StartedPilot 2 ATC (P2A) - version 3.0.0.0_EarlyAccess 0.2.2A  8/31/2025 12:06:44 PM
2025-08-31 12:06:45.2162|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|Pilot2ATC® starting initialization.
2025-08-31 12:06:45.2162|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|NumberDecimalSeparator: 
2025-08-31 12:06:46.0299|INFO|P2ADataLinq.WxMgr|Retrieving weather from web successful at 8/31/2025 12:06:46 PM
2025-08-31 12:06:46.0299|INFO|P2ADataLinq.WxMgr|Successfully downloaded NOAA Wx
2025-08-31 12:06:46.6386|INFO|P2ADataLinq.WxMgr|Retrieving TAF from web successful at 8/31/2025 12:06:46 PM
2025-08-31 12:06:59.1560|INFO|P2ADataLinq.Data.FltPlan|NextWpt: Alt:1500
2025-08-31 12:07:10.4843|INFO|P2ADataLinq.Controller|TransponderSettingChanged - Code: 1200 Mode:
2025-08-31 12:07:10.4843|INFO|P2ADataLinq.Controller|TransponderSettingChanged - Code: 1200 Mode:
2025-08-31 12:07:10.4873|INFO|P2ADataLinq.ComChannel|ControllerFreqChanged: - - - -.  CtlrShrtName: - - - - CtlrType: None
2025-08-31 12:07:10.5033|INFO|P2ADataLinq.ComChannel|Com1 set to - - - -          - - - -
2025-08-31 12:07:10.5033|INFO|P2ADataLinq.ComChannel|ControllerFreqChanged: 127.900.  CtlrShrtName: - - - - CtlrType: None
2025-08-31 12:07:10.5033|INFO|P2ADataLinq.ComChannel|Com2 set to - - - -          127.90
2025-08-31 12:07:10.5443|INFO|P2ADataLinq.simJoystick|Device: Souris  Souris  Mouse
2025-08-31 12:07:10.5443|INFO|P2ADataLinq.simJoystick|Device: Clavier  Clavier  Keyboard
2025-08-31 12:07:10.5443|INFO|P2ADataLinq.simJoystick|Device:  Logitech Z205     Logitech Z205    Device
2025-08-31 12:07:10.5443|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5443|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5513|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.JoystickMgr|JoystickMgr.Init
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5673|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5813|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:10.5973|INFO|P2ADataLinq.JoystickMgr|JoystickMgr.Init completed
2025-08-31 12:07:10.6433|INFO|P2ADataLinq.ATCListener|Loading Speech Recognition.  Language: en-US
2025-08-31 12:07:10.6663|ERROR|P2ADataLinq.ATCListener|Error in ATCListener LoadPilotGrammar: System.InvalidOperationException: Cannot find the requested data item, such as a data key or value.
   at System.Speech.Recognition.RecognizerBase.SetInputToDefaultAudioDevice()
   at P2ADataLinq.ATCListener.SetRecoEngineInputDevice()
2025-08-31 12:07:12.4872|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|SIM version: 
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.JoystickMgr|JoystickMgr.Init
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:12.5222|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:12.5352|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:12.5482|INFO|P2ADataLinq.simJoystick|Loading Joystick Devices - 1 devices loaded.
2025-08-31 12:07:12.5482|INFO|P2ADataLinq.simJoystick|Active GUID count: 5
2025-08-31 12:07:12.5482|INFO|P2ADataLinq.simJoystick|Unable to select device number -1
2025-08-31 12:07:12.5482|INFO|P2ADataLinq.JoystickMgr|JoystickMgr.Init completed
2025-08-31 12:07:12.5852|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|ConnectToSIM events fired.
2025-08-31 12:07:15.6822|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|ConnectToSIM complete.
2025-08-31 12:09:50.5831|INFO|Pilot2ATC_3.Panels.Settings.SettingsPanel|SettingsPanel Initializing.
2025-08-31 12:09:50.5831|INFO|Pilot2ATC_3.Panels.Settings.SettingsPanel|SettingsPanel Initialized.
2025-08-31 12:09:50.6091|INFO|Pilot2ATC_3.Panels.Settings.SettingsPanel|Settings Panel LoadPTTJoystickSettings.  PTT Joystick Name: 
2025-08-31 12:12:27.3248|INFO|P2ADataLinq.ATCListener|User Names Found: 217
2025-08-31 12:12:27.5574|INFO|P2ADataLinq.ATCListener|AddUserNames Succeeded. 
2025-08-31 12:12:27.5574|INFO|P2ADataLinq.ATCMgr|AssignedSID: BELE8W - 
2025-08-31 12:12:27.5574|INFO|P2ADataLinq.ATCMgr|AssignedSTAR: MEBA9P - 
2025-08-31 12:12:27.5574|INFO|P2ADataLinq.ATCMgr|AssignedAPPR: ILS RW18-Z - 
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed Plan: LFLC LFLB
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed SID: RW26 BELE8W : 
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed STAR: RW18 MEBA9P : MEBAK
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed APPR: ILS RW18-Z : PIRUV
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed Cruise Alt: 36000
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|File Descent Rate: 1800
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed Plan GS: 445
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Filed FP Type: IFR
2025-08-31 12:12:27.5574|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Force Dep: False
2025-08-31 12:12:27.5644|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Force Arr: False
2025-08-31 12:12:27.5644|INFO|Pilot2ATC_3.ViewModel.FltPlanVM|Force Pilot Rwy: False
2025-08-31 12:12:27.5644|INFO|P2ADataLinq.FlightStateMgr|State Changed to: FlightPlanFiled
2025-08-31 12:12:28.1503|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: A

 

The log file seems to show connecting to the SIM and filing of a flight plan from LFLC to LFLB.  However, it does not show tuning of the radio to a valid frequency of any sort, hence no possibility of communications. 

When you are on a valid frequency, you will see the frequency and controller name in the top left box of the COM area.  That is the active frequency on the Active/Transmitting radio channel.  Also, the COM 1 and COM 2 names will appear at the very top.  If they just say COM without the channel number or are blank, you are not properly connected.  Be sure you are entering frequencies from the list in the P2A Freqs window.  You can just click on them to load them into the standby frequency slot of the selected channel.

If that doesn't get you going, try running the program as administrator.  Depending on how you installed it, you may need to do that to get it to work correctly. 

If that doesn't work, start it as a normal user and try using a different aircraft.  Some 3rd party aircraft don't allow external programs to interact with their aircraft or have an option somewhere that enables/disables that interaction.  Try one of the stock P3D aircraft.

If none of that gets the radios to set properly, try installing the update.  That will replace all the code files without overwriting your P2A data files.  If some of the files have been corrupted, this should fix the issue.

Dave

 

Hello,
I'm Cheminade's brother.

Thank you for your help and answers about Pilot2atc. We use a cockpit for our flights.
https://737projectcom.wordpress.com/

Attached are some photos and questions to help us get Pilot2atc working properly.

Photo 3387: Why do we have a no entry sign?

https://737projectcom.wordpress.com/wp-content/uploads/2025/09/img_3387.jpg

Photo 3388: Why is Reims written in the frequency when the flight plan starts at lflc?

https://737projectcom.wordpress.com/wp-content/uploads/2025/09/img_3388.jpg

Photo 3392: Why are there no taxiways drawn on the plan?

https://737projectcom.wordpress.com/wp-content/uploads/2025/09/img_3392.jpg

 

Thank you for your help and answers.

Sorry for my poor English because I use Google.

Pat

Photo 3387: I'm not sure what you mean by not having an "entry sign".  I do notice that you are pulling up the phrases to speak but appear not to be pressing the Speak button.  This results in nothing being said by the copilot and no action being taken by ATC.

Photo 3388: Reims is the name of the Center controller.  Notice it says Reims Ctr.  You will need to swap frequencies before getting clearance.

Photo 3392: You have an IFR flight plan.  The "Open Flight Plan" is used in VFR flights.  For IFR, you need to get IFR Clearance.  As for Taxiways, if you get a taxi clearance with taxiways in it, you can have it display on the map by pressing the Taxi button to the left of the map.  This only works after you get your taxi clearance from ATC.  You have to zoom in to see them.

It looks like the biggest issue is that you have not started speaking to ATC.  When you do, you will see your speech (or the copilot's speech) in green and ATC speech in white.

Dave

Thank you, Dave, for this quick and precise response.

 Since we didn't want to use speech at first, we didn't program a PTT button.

 It's possible that this is our problem.

 We'll test it tomorrow and I'll keep you posted.


For photo 3389, I circled the symbol in red. What does it mean?



Thank you for your help. Have a good evening.

 

Pat

 

That's just a message that your FltPlan exported successfully.

Dave

Hello Dave, Thanks again for your help. I hope not all of your customers are like us.

We've tried several things.

The first was by installing 'Pilot2ATC' on the same PC as 'P3D', but we're having the same problem.

We followed the flight plan creation procedure step by step, which is very well explained in the video, but the same problem still occurs even when changing aircraft.

We added a microphone and declared a shortcut for the 'PTT', but without success.

 

To describe the situation, the flight plan is being created correctly. After submitting the flight plan using the 'FILe' button, we click the connect button. After a few moments, this is what we see.

 

1) In the radios window, there are no COM1 and COM2 as in the video, only COM and COM.

2) In the radios window, it is not possible to swap or change the frequency. The input window appears correctly, but after entering the information, there are no changes in the main radio window.

3) If I select a radio station from any list, there are no changes either.

4) Finally, the strangest thing is that our plane is correctly positioned at the departure airport (LFLC in the picture), but the frequencies displayed in the radio panel correspond to a different airport (REIMS in picture).

 

We are using FSUIPC 5 and, for your information, we were using PROATC before switching to P2ATC, and it worked fine. I admit I don't know what to do anymore. I hope you find a solution to our problem.

Thank you so much

The COM and COM indicate that the Connect is not fully working.  The frequencies are not being automatically set to ATIS and Clearance/Ground at the departure airport because of that.

Is the SIM paused when you connect?  It must be fully up and running and not paused before you try and connect.

If it is not paused, try an experiment to see if the problem is with the loaded aircraft.  Change to one of the stock aircraft in P3D.  Then try and connect and see if the COM windows populate properly.

Dave

Hello Dave,

Some news, but it's not good.

Today we retested with the same aircraft (Mooney) on P3D and on P2ATC with P3D fully active, but without results.

A little information, but it may not be the cause of our problem. During the installation, we received an error window at the end of the installation. 
This error only appeared during the installation and no longer appears. You will find a screenshot of this window.



So, I admit we're a little desperate. It seems we're not very far off, but we don't understand what's blocking us.


Sincerely, François.

 

 

 

Edited September 4, 2025Sep 4 by Cheminade

OK.  That might be the problem.  That error indicates the installer wanted to install the SQLLocalDB engine but failed to find the installer.

I will send you a link to the SQLLocalDB Installer in a private message.

Dave