I am using Win10 MFS 2020 .  With a trial version of P2ATC.

I am connected to P2ATC with FSUIPC 7 with Simulator Connected and com1 nav2 and power button green (although Im using a320 neo FBW which didnt recognise the buttons so assume that just an indication of the checkboxes in p2atc)

I have US English installed  as the default language (I assume no need to change region etc for the PC itself)

I have run P2ATC in administrative mode

I have used call sign beech and no. N431VB, as an airline and as GA,  I have tried the call sign EZY 255 

However only seeing Simulator Connected line in right hand box.

Error message when selecting freq.. Aircraft position not found.

Successfully filed a flight plan. 

 

Not sure what to try next other than a reinstall of p2atc.

 

tks

You are not fully connected to the SIM.

Here are the most common reasons for not being fully connected:

1. Be sure the SIM is fully up and running and not paused.  The cockpit must be showing.
2. Be sure you are connected to the internet. It must be a reliable connection.
3. English-US Language installed and set as Primary Language, English Speech Recognition installed also.
4. Working Microphone installed and set as Default Sound Input device in Windows
5. Valid Call Sign – Try using the default call sign of Mfg: Beech; Tail Number: N431VB.  Press the Save button.
6.  Try running the program in Administrator mode by right clicking on the Pilot2ATC.exe file and selecting “Run as Administrator”
7.  If connected but the radios aren’t working, check the Battery and Avionics switches on or the “Ignore battery” and “Ignore Avionics” options are checked in P2A Config
8. If it seems to partially connect but the Connect button does not turn Green, set the Weather option to a different source such as NOAA Real Time Weather and try again

Dave

19 hours ago, Dave-Pilot2ATC said:

You are not fully connected to the SIM.

Here are the most common reasons for not being fully connected:

1. Be sure the SIM is fully up and running and not paused.  The cockpit must be showing.
2. Be sure you are connected to the internet. It must be a reliable connection.
3. English-US Language installed and set as Primary Language, English Speech Recognition installed also.
4. Working Microphone installed and set as Default Sound Input device in Windows
5. Valid Call Sign – Try using the default call sign of Mfg: Beech; Tail Number: N431VB.  Press the Save button.
6.  Try running the program in Administrator mode by right clicking on the Pilot2ATC.exe file and selecting “Run as Administrator”
7.  If connected but the radios aren’t working, check the Battery and Avionics switches on or the “Ignore battery” and “Ignore Avionics” options are checked in P2A Config
8. If it seems to partially connect but the Connect button does not turn Green, set the Weather option to a different source such as NOAA Real Time Weather and try again

Dave

Thanks for the message,  1 - 7 everything as suggested.. it actually connected once last night and I was able to use it  ... weather was set to NOAA yesterday and tried different today.  I launched this morning and again would not connect.. however I restarted FSUIPC 7 and it connected right away so it appears that there may be some disconnect for me depending on the order I start the various programmes.  Will update accordingly, thanks for help.

On 11/5/2020 at 10:01 AM, targetpractice2 said:

Thanks for the message,  1 - 7 everything as suggested.. it actually connected once last night and I was able to use it  ... weather was set to NOAA yesterday and tried different today.  I launched this morning and again would not connect.. however I restarted FSUIPC 7 and it connected right away so it appears that there may be some disconnect for me depending on the order I start the various programmes.  Will update accordingly, thanks for help.

just update on this, for me its fsuipc / p2atc order of loading that impacts it.. so just have to load fsupic a couple of times for it to connect after I load p2atc, it doesnt see it if I load it first.