September 28, 20214 yr Hi. I've followed every training steps to train my speech. First I did the full windows training speech recognition. After I did all the full Pilot2ATC language trainer beginning on clr delivery until approach. This I did twice. After I did the personal grammar training phrases with sentences I wrote myself simulating a full flight. I've listend to what I said and it was recognized. My english is not so bad... But in a flight ATC keeps saying for me to call with a proper call sign. The call sign I use is accepted in the config and is EASY 1715. I do not know what do next. Any ideas to help me? Thank you. HB
September 29, 20214 yr Commercial Member Is the call sign an Airline call sign with the Airline option checked? Is EASY in the Call Sign box and 1715 in the Flt Number/Tail Number box? Try changing EASY to Easy. It may be seeing the all CAPs as Echo Alpha Sierra Yankee. Edited September 29, 20214 yr by Dave-Pilot2ATC
September 29, 20214 yr Author Hi Dave "Is EASY in the Call Sign box and 1715 in the Flt Number/Tail Number box?" Yes. I've also tried another call sign and the result is the same. Regards HB
September 30, 20214 yr Commercial Member Email the log file for a flight where you get the call sign problem to [email protected] and I'll have a look. Also, send a screenshot of the main Config screen with the call sign setting so I can see it. P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab. A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one. Regards, Dave
September 30, 20214 yr Commercial Member HB, I think I figured out what is wrong. When flying in the US and Canada as an Airliner, you must pronounce 1715 as Seventeen Fifteen. In the rest of the world, it must be One Seven One Five. So if you have been using One Seven One Five in the US, that would cause the problem. This will be fixed in the next update so that you can use either form worldwide. Dave
Archived
This topic is now archived and is closed to further replies.