Jump to content

Recommended Posts

Posted

Hello !

First of all, thank you for the 1.0.7 update, performances are much better and I can finally fly the plane on Vatsim !

But now I'm having issues with the CPDLC, everything seems to be fine, except for the WILCO messages, which make it impossible to use 😕 I had multiple issues on VATSIM because of that : 
- The other day a controller gave me a DIRECT TO, and I responded with "WILCO", but then he called me 5min later on the radio saying that he didn't saw my response (even though I could see it on the Hoppie log page)
- Today I tried to request a PDC clearance to the ground controller, I responded to it with WILCO, but then it was rejected, saying that I didn't acknowledgeo it
- Then I again with the en-route controller, requesting a direct and a FL change, but it was again rejected because the WILCO was never received on their end.

Below you can see the Hoppie logs for the last 2 cases reported above : 


image.thumb.png.c921581e41c38c9ef8b431c15dd996fa.png

 

Am I doing something wrong, or is there an issue with the plane ? Below there is a video of how I am sending wilco to ATC instructions : 
 

 

 

Posted

Hi,

Thank you for adding the footage as well as the Hoppie logs, that really helps alot, I will push this along to the team as I know how important and helpful CPDLC is on Vatsim especially in busy airspaces

  • Thanks 1
  • 2 weeks later...
Posted

Hi,

FYI I did more tests and I think I found the problem :

I tried to send some messages on the Hoppie network as you can see below

image.png.1d496a70079ab45632f579d90219faf2.png

The format seems to be :
- ATC message : /data2/<act_message_id>/...
- Plane response message :  /data2/<plane_message_id>/<atc_message_id>/...

The A300 is incrementing the plane_message_id like the other planes, but will always put 0 instead of the atc_message_id, so that's why the controllers are not seeing my response I guess.

As you can see below, other planes are responding with the correct atc_message_id : 

image.png.7225eac2a59c3f2ca05c84920ea2508f.png

 

image.png.0181ff64869003e182b53735f96c437f.png

 

image.png.d68254dc928860a06f66c0b6be4f4f11.png

 

Thank you for investigating this issue and have a nice day !

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
×
×
  • Create New...