Jump to content
Sign in to follow this  
stems

ATC will not respond

Recommended Posts

I am trying to use Pilot2Atc as trial version on FS2020 and I noted the following:-

1. I am starting flight from runway on A320 I select request departure runway and press say it but no answer. Frequencies do change in FS when changed then on P2A , I tired calling ground, centre and tower but there is no answer. I have an input device as microphone although I am not sure if it is working correctly but initially I intend to use the sayit button to get accustomed. 

 

2. This could be related,  as I fly the tower will not give any instructions I am just flying on my own could be that nobody is hearing me 🙂

I appreciate any idea of what could be the problem. I have an input device 

Thanks

Edited by stems

Share this post


Link to post
Share on other sites

First, I assume you are connected to the SIM with the Connect button turned Green and the last line in the Speech Text Window (bottom right of P2A) says Grammars Loaded.  If not, then you need to Disconnect and try Connecting again.  Once Connected fully, check the following:

1.    SWITCH SETTINGS: Check to be sure the Power indicator in the bottom left of the main P2A screen is  green.  If not, then you need to turn on the battery switch and avionics switch in the aircraft, or if that doesn’t turn it green, check the 2 options “Ignore Battery Switch” and “Ignore Avionics Switch” in the Config P2A Setup panel.
2.    VALID CALL SIGN: Make sure you are using a valid call sign by changing it to the default Mfg: Beech; Tail Number: N431VB and pressing the Save Button.  You can send me a screenshot of this page and I will let you know if there is a problem with the call sign.
3.    VALID FREQUENCY: Be sure you have a valid frequency showing in the Active frequency display.  Open the Radio Panel and check that the frequency selected has a valid controller assigned.  Try swapping the active and standby frequencies a couple of times.
4.    PTT BUTTON: Use the PTT button on the main screen to eliminate the possibility of it being the Joystick button setup as the issue
5.    VALID PHRASES: Make sure the phrase you are using is appropriate for the controller.  “Say Altimeter” should work with all controllers, so use it.
6.    VOLUME SETTINGS: Check the Windows Volume Mixer and be sure Pilot2ATC volume is turned up. (While P2A is running, right click on the speaker icon in the task bar and select Volume Mixer).  Also check the volume of the voices in P2A Config.  On the Communications tab of the Sound dialog, be sure "Do Nothing" is checked for when Windows detects Communications activity.
7.    GRAMMAR HELP SCREEN AND DIAGNOSTICS: Try using the Grammar Help screen.  
⦁    Press the Grmr Help button to the right of the Flight Plan
⦁    Press the Practice button 
⦁    Take a screenshot of the resulting Message box with the connection information and email to me 
⦁    Try saying "Say Altimeter" with no other words.  It should be recognized.  Let me know the result.

Dave
⦁    If not being recognized, press the "Replay" button and see what your voice sounds like.  If no sound, then your voice is not getting through to Pilot2ATC.
 

Share this post


Link to post
Share on other sites

Thanks I am away and cannot try, I will try to replace headset. I am flying Airbus A320 using callsign T7660 but when I press sayit it shows ~T7660 six six zero.

I will try the options tomorrow but thanks for your prompt reply.

Edited by stems

Share this post


Link to post
Share on other sites

That call sign seems incorrect.

If you are flying as an airline, you need to enter the airline callsign, like Delta, American, or Air New Zealand in the Mfg/Airline box and the flight number, like 660 in the Tail/Flight number box.

If flying as GA, then you could put Airbus in the MFG box and T7660 in the Tail number box, for example.

Dave

Share this post


Link to post
Share on other sites

I managed, it was the headphones not working well. I completed one test flight and all seems very well, could speak to the tower and get response without any issue. Actually I put in Airbus in the MFG box and   7660 but it is saying it 660 but that is fine with me, even better as it is shorter.

I will do some more test flights but if everything goes is it was today then I am sure you will hear from me in a positive way.

 

Thanks

 

Share this post


Link to post
Share on other sites

Glad you got it working.

GA Call Signs are either the full Tail Number, or the Mfg and the last 3 characters of the tail number.

There are a couple of other combinations, but those are the most widely used.

Dave

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...