BATC not Recognizing COM2
-
Apologies for how long this took to get back to you on. Life must be lived...
Anyhow, I did a test just now and the MX170Bs are the issue here. I swapped in the GTN and I was able to tune the radios and have BATC see them tuned as such.
With the MX170B, BATC doesn't see what is tuned. However, swapping back from the GTN caused the MX170B to be recognized. There is something off about having them as the default radios, I think.
I didn't test any other avionics besides these two.
-
I was using both MX170B the other day with BATC with no issues. Had radio comms on 1 and ATIS on 2
Just logged in quickly. In attached, EGHH Ground on Comm1 and EGHH ATIS on Comm2. All coming through fine.
Not sure what to say. This is what I see right now.
Default is the MX170B set. Swapped to TDS GTN set. Same message for COM2 with either set.
There are some inconsistencies here, for me. For example, in this thread I've noted that the COM1 won't see the tuned frequency without messing about with BATC's in-app tuning function and/or swapping avionics. Today, I launch the sim, load into the 114 with the MX170B as the default and it's seeing COM1 tuned correctly, but no COM2.
It's inconsistent for me.
-
Hi, it is very strange. For me every time I have used BATC and the Commander all has worked perfectly. So the hooks between the 2 are definitely there correctly.
Are you running any other apps that could be interfering with the setup somehow? I am not sure what but there must be something creating this issue for you somehow.
-
BATC currently doesn't recognize Comm 2 unless you're listening to an ATIS frequency. You cannot receive or transmit on comm 2 otherwise. Actually just read that this morning, while reading about their VFR progress. I can't for the life of me find a link to the article now, but I know that's what it said.
-
Hi, it is very strange. For me every time I have used BATC and the Commander all has worked perfectly. So the hooks between the 2 are definitely there correctly.
Are you running any other apps that could be interfering with the setup somehow? I am not sure what but there must be something creating this issue for you somehow.
I’m not running any apps. I have a very lean system with minimal add-ons, and those from highly reputable developers.
I can trim everything away and retest with just the 114 installed.
I had ATIS tuned on COM2 when I made my post today, yet it indicated COM2 was off.
I don’t know if the issue is the experimental version of BATC vs. the early access version, but I’d really doubt it since the radios aren’t what BATC are even working on within the experimental branch.
I’m also on SU6 beta, so I don’t know if that is also a differing factor.
-
I am using the experimental BATC so wouldn't seem to be an issue with that version. I am on the SU5.1. Perhaps it is SU6 related then. Didn't realise you were on the beta. I wouldn't normally expect everything to work correctly on the beta channel of MSFS.
-
I am using the experimental BATC so wouldn't seem to be an issue with that version. I am on the SU5.1. Perhaps it is SU6 related then. Didn't realise you were on the beta. I wouldn't normally expect everything to work correctly on the beta channel of MSFS.
If it's SU6 Beta, then it's still the 114. I'm flying the A2A Comanche, and its radios behave as expected.
Again, I'll look further into the 114 and do some testing when I'm in the mood for it. For now, I'd rather be flying.
