Restarted the program while at cruise, revalidated and refiled. Tried initial contact. ATC keeps responding "Aircraft calling Jacksonville center say again with your call sign".

ATC was perfect with this flight plan up until climb when I had to terminate the program.

Log only shows my ATC messages but never the ATC response above:

2024-10-06 10:37:52.0099|INFO|P2ADataLinq.ATCListener|Initial Recognized Speech: Center BLUE STREAK five six five eight At Flight Level Three Six Zero
2024-10-06 10:37:52.0414|INFO|P2ADataLinq.ATCListener|Handled Recognized Speech: Center BLUE STREAK five six five eight At Flight Level Three Six Zero
2024-10-06 10:37:52.0414|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 1 in InterruptAudio 
2024-10-06 10:37:52.0414|INFO|P2ADataLinq.Speech.SpeechMgr| WaveOutPlayer Paused in InterruptAudio 
2024-10-06 10:37:52.0414|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter Paused in SpeakPhrase
2024-10-06 10:37:52.1537|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter UnPaused in OnTTSWavePlaybackStopped
2024-10-06 10:37:56.9536|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 0 in UnInterruptAudio 
2024-10-06 10:37:56.9536|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter UnPaused in OnTTSWavePlaybackStopped
2024-10-06 10:38:30.6083|INFO|P2ADataLinq.AsyncTCPClient|Socket connected to 127.0.0.1:48007
2024-10-06 10:38:57.2681|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E1
2024-10-06 10:38:57.2681|INFO|P2ADataLinq.Data.FltPlan|NextWpt: ROYCO
2024-10-06 10:38:57.2681|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E1
2024-10-06 10:38:57.2681|INFO|P2ADataLinq.Data.FltPlan|NextWpt: ROYCO
 

Logs shows waypoints, but I can't make contact to get a squawk code etc...

I opened the aircraft profile and pressed save without making changes and ATC recognized my call sign afterwards.

I was already descending and couldn't get ATC to properly control the arrival/approach.

Saving the Profile is key to updating the things like Call Sign so they will work with ATC.  If you had made a change and not pressed the save button, that likely is the cause of the controller not responding.  

Dave

I never set the callsign, it is set by the simbrief import.

The sequence was:

1. start p2atc

2. import flight plan from simbrief - which sets the callsign

3. connect to xplane

4. validate and file

5. initial contact while at cruise - callsign not recognized

6. open aircraft profile and save without changes

7. initial contact - callsign recognized.

 

For a normal flight, when step 5 is a call for IFR clearance from the ground, there is no callsign issue.

 

 

 

36 minutes ago, Dave-Pilot2ATC said:

Saving the Profile is key to updating the things like Call Sign so they will work with ATC.  If you had made a change and not pressed the save button, that likely is the cause of the controller not responding.  

Dave

just to be clear - I never use voice. The callsign that is not being understood always comes from the copilot.

p2atc generated this initial contact speech: Center BLUE STREAK five six five eight At Flight Level Three Six Zero

Thanks for the additional detail.  It seems the imported call sign is not being saved to the Grammar when it is imported, but only when you press the Save button on the Profile.

I'll have a look and try to fix so it is automatically saved if you import CallSign from Simbrief.

Dave

Problem fixed.

thanks