Just managed to get my first Clearance Delivery via CPDLC! Thank you so much Roland, finally I get to use P2ATC in VR!! 🙂 I can already say this is going to be a game changer for me, since I refuse to take my headset once in the cockpit and I can't possibly remember the entire delivery clearance without pen and paper. 

A few comments so far:

1. The instructions are very clear, thank you for putting in the time 👍 I managed to set it up by myself just by following along.
2. I was unable to set it up at first because my hoppie user was set to network "None". Once I noticed the P2A  hoppie user (the one derived from the SimBrief ID) was listed in the hoppie logs under VATSIM, I changed mine too and I was able to connect. Just to keep in mind and maybe add to the readme file.
3. I disconnected using the MCUD and then was unable to reconnect, however I noticed there were no LOGON requests sent to hoppie, so I assumed this was some kind of spam protection built in the network. Changing the P2A ID (simbrief) to a new number fixed this. Again, just for awareness as there's probably nothing you can do about it here.
4. I assume this goes well beyond the scope of the integration, since you are reading the P2ATC output via the .txt file, but it would be a great addition to be able to request pre-dep clearances, directs, and such (http://www.hoppie.nl/acars/system/message.html?msgid=9119906). Not sure P2ATC would even support that, just a random thought.

Thanks again, going for a first full test flight tonight. Happy landings! ✈️

Nicew one Roland.. message sent! 🤓

Looks like I may have "fallen at the first" as they say 😊
set up was going well but the notification page in the FBWA32nx only has space for 4 characters and my personal atc code is 9. 
Now it could be that I'm doing it wildly wrong or it could be the FBW isn't compatible...either or both is possible.

I should add that all the "chat" between pilot and ATC from P2ATC has been recorded succefully in the P2Aconversation file. So I it seems to just be the connection to the FBWA32NX.

Edited May 7, 20233 yr by BrianT

do you plan to publish your software?

According to this FBW screen, the ATC CENTER accept up to 8 chars

My Simbrief ID has 5 digits, so the whole name has 8 chars like: P2A12345 and match the available length. You should try to omit the last digit if your Simbrief has 6.

20 hours ago, Commander_K said:

do you plan to publish your software?

I did not yet because very few people seem interested

About the ATC Center max length, I can reduce the fixed chars to "PA" to keep 8 chars with a 6 digits Simbrief ID. 

24 minutes ago, roland_lfor said:

According to this FBW screen, the ATC CENTER accept up to 8 chars

My Simbrief ID has 5 digits, so the whole name has 8 chars like: P2A12345 and match the available length. You should try to omit the last digit if your Simbrief has 6.

Where did you find that? in the most recent FBWA32NX (experimental) it looks like this. (ignore the red messsage)

there is only space for 4 my Simbrief id is 6 so even with your suggestion of reducing the max length I'm still over. I'm sure they should be able to increase the number of characters
I have asked on their discord and am awaiting a reply, unfortunatley I have to go out today so not going to be able to do much.
 

My screenshot is from an old standard version. But even for a classic ATC use, 4 chars is not enough. You should open a ticket I guess.

In the meantime to be able to test, you can try to fill your ID as "3" to get "P2A3" as ATC position.

44 minutes ago, roland_lfor said:

My screenshot is from an old standard version. But even for a classic ATC use, 4 chars is not enough. You should open a ticket I guess.

This was the response I got.....Maybe tiome for me to buy the fenix.

"What does SimBrief id have to do with the atc logon code? The restriction is there because they are only 4 letters in real life as well"

"the ACARS is modelled after a specific version of the Honeywell FMS, which supports 4 characters"

"We might support software revisions in the future provided we have appropriate documentation but atm it’s H3. Something may be possible through the EFB"

Might just be easier for me to buy the Fenix 😁

Edited May 8, 20233 yr by BrianT

It's strange because for online flying with Vatsim or Ivao, ATC position in the past were usually like <ICAO>_<type> which is always above 4 chars.

I.e. LFPO_TWR or LFPO_APP

I think a little bit on this issue. If we are limited to 4 chars then I can generate a random 4 digits ATC name.

The goal is to have a unique ATC name over the Hoppie network for each user. I can use the computer system tic last 4 digits for that.

I have a new Beta with this mechanism.

For users who are using Beta, I've just changed my Hoppie profile network to "none" (previously set to VATSIM which is default). 

>>> As P2Acars currently uses my Hoppie logon, you have to do the same with your personal Hoppie account <<<

You can access your Hoppie account here.

Before public release I will modify P2Acars so each Hoppie user will set its own logon.

Edited May 9, 20233 yr by roland_lfor

16 hours ago, roland_lfor said:

I think a little bit on this issue. If we are limited to 4 chars then I can generate a random 4 digits ATC name.

The goal is to have a unique ATC name over the Hoppie network for each user. I can use the computer system tic last 4 digits for that.

I have a new Beta with this mechanism.

Good morning Roland, do you have a link to the nerw version I can try?