solved [NO REPRO] BATC CPDLC - no resposne in sim?

[Donald Douglas]

When I use CPDLC for clearance request in the ini A340, I can send the request,I see it in BATC, then see the response in BATC, but it never comes to the flight deck, so there's no way to respond or acknowledge it.  This seems to work fine in the A350.

Edited October 10 by Donald Douglas

[MMAACCXX]

I had the same Problem and also I was able to see the response in BATC (with SU4 Beta). Thereafter, I flew the Fenix A320, and I got the missing CPDLC Response from the flight with the A340, so the message was definitely created, but not picked up by the A340...

[richboy2307]

Hi @Donald Douglas/ @MMAACCXX

Apologies for delay in response. For BATC, it only supports Pre-Departure Clearance (PDC) via CPDLC currently.

Key things to ensure for proper function:

• You are on BATC Experimental Branch (v1.6.75 Experimental or greater). PDC is not available on the Early Access branch at this time.
  
   
• You have set BEYONDATC as the CPDLC Source on the EFB 3RD PARTY SETTINGS Page.
  
  (Click to enlarge image)
   
• You have completed your MCDU INIT-A page with information such as FLT NBR and FROM/TO
  
   

After that, you can request PDC following the guide below: 

We and a few other testers have confirmed this working since launch, even up to v1.0.2 recently. 

 
Thanks!

[Donald Douglas]

I had already done everything you are suggesting, down to the letter--  multiple times, but would never get the response onto the DCDU.

 

I have not attempted since 1.02, but will try again now.

[Donald Douglas]

Nope. Still broken.

CPDLC source set to BATC:

 

BATC version 1.6.75 Experimental (which was just released today/last night, by the way)

INIT A completed:


Clearance Request Composed and sent to DCDU:

Sent to and received by BATC and BATC sends response:


No messages received on flight deck:

[richboy2307]

Hey @Donald Douglas

There is a slight delay (by design) between when messages are "sent" by BATC vs when they actually show up in the aircraft. In my case it was upto about 30 seconds. However trying your exact same route on 1.0.3 (latest version now), its working my end.

If you continue to have issues, perhaps check with BATC Support, along with your log to see if they have additional information. 

Thanks!

[Donald Douglas]

I left it running almost 30 minutes while I composed these responses.  

I've already reported this to BATC, they indicated it was an inibuilds issue.... and, why would this work for me for the iniA350 and not the A340?  If this was a BATC issue, or a communications issue, wouldn't it be evident globally??

I have the A340 installed locally (ie: not streamed) if that matters...Neither MSFS or BATC run with Admin rights.  What is the difference or conflict here from my system to yours?

@MMAACCXX Are you still having this issue?

 

 

 

[richboy2307]

Hi @Donald Douglas

We have attempted on both streamed vs locally downloaded copies, as well as on SU3 and SU4 Beta across different systems before reporting no-reproduction of the above. As at the moment the issue is only reproducible on your instance, can you please try the following to see what works

• Try running BATC as admin first. If that doesn't work try running both as admin. In our test instances that was not required but every system is different in its UAC settings.
• Try on the streamed version of A340 (Delete the locally installed copy from My Library).
• Ensure BATC and the sim is granted proper permissions through your firewall.

Again, we are equally curious as to the cause as the outgoing message is seemingly working, but the incoming isn't for some reason on your end. Let us know the outcome of the above.

Thanks!