<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[BATC not Recognizing COM2]]></title><description><![CDATA[<p dir="auto">Hey,</p>
<p dir="auto">BATC shows that COM2 is "off" when it is clearly on.</p>
<p dir="auto">I contacted BATC and they say "The radio controls are done through standard commands through simconnect." They indicated that the issue is probably the aircraft developer's to look into.</p>
<p dir="auto">Could you give this a look?</p>
<p dir="auto">Thanks!</p>
<p dir="auto">(I can't wait to get the 114 into the air!)</p>
]]></description><link>https://community.justflight.com/topic/11065/batc-not-recognizing-com2</link><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Jul 2026 21:34:55 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/11065.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 29 Jul 2026 16:31:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Thu, 30 Jul 2026 14:22:54 GMT]]></title><description><![CDATA[<p dir="auto">Yes. I was using the MX170Bs.</p>
<p dir="auto">There is a planned power is outage here most of the day, so I will get to this when it come back on this afternoon (Pacific Time).</p>
<p dir="auto">As I’m thinking on this, I wonder if any of my troubles were due to after effects of “hot swapping” the avionics. On initial load, it had the TDS unit, and I switched it to the MX. However, my initial load of the aircraft was in a different flight session (same sim session, though) than when I actually flew the aircraft. On that second flight session, the MX units were already enabled, so you’d think there would have been no after effects, as such. It will be interesting to see how it behaves with a fresh load cycle of the sim itself.</p>
<p dir="auto">I just know that Matt at Working Title had mentioned that hot swapping wasn’t a clean solution in 2020. I’m unsure if that continues to be so with 2024.</p>
<p dir="auto">Anyhow, I’ll get back when I can.</p>
]]></description><link>https://community.justflight.com/post/52935</link><guid isPermaLink="true">https://community.justflight.com/post/52935</guid><dc:creator><![CDATA[NixonRedgrave]]></dc:creator><pubDate>Thu, 30 Jul 2026 14:22:54 GMT</pubDate></item><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Thu, 30 Jul 2026 08:11:41 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for getting that information.  I checked all those variables, including CIRCUIT NAVCOM1 ON, CIRCUIT NAVCOM2 ON, CIRCUIT AVIONICS ON, COM AVAILABLE:1, and COM AVAILABLE:2.  All of them appear to be working correctly.  The frequencies seem to be populated correctly, as well.</p>
<p dir="auto">I assume we're talking about the MX170B's, btw?  I'm sure you know what you're doing, but do you think you could send some screenshots of the radios, and whatever interface you're looking at with BATC?  Sometimes I can see things that lead to a solution, even if they might go unnoticed to anyone who didn't program the aircraft.</p>
]]></description><link>https://community.justflight.com/post/52921</link><guid isPermaLink="true">https://community.justflight.com/post/52921</guid><dc:creator><![CDATA[Black Square]]></dc:creator><pubDate>Thu, 30 Jul 2026 08:11:41 GMT</pubDate></item><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Thu, 30 Jul 2026 05:42:41 GMT]]></title><description><![CDATA[<p dir="auto">Here it is:</p>
<p dir="auto"><code>COM STATUS:index</code><br />
<code>COM VOLUME:index</code><br />
<code>COM TRANSMIT:index</code><br />
<code>COM RECEIVE:index</code><br />
<code>COM ACTIVE FREQUENCY:index</code></p>
<p dir="auto">“These are what BATC is looking at in an aircraft to enable the functionality. These are default sim variables - if an aircraft is not writing/updating these then BeyondATC won't know about what is entered or happening on the radio panel. The index is the COM number effectively. 1 for COM1, 2 for COM2 etc.<br />
More info in the <a href="https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_RadioNavigation_Variables.htm#COM" rel="nofollow ugc">MSFS SDK </a> but I would think an aircraft dev would be using most of these already.”</p>
<p dir="auto">Thanks for looking into this!</p>
]]></description><link>https://community.justflight.com/post/52908</link><guid isPermaLink="true">https://community.justflight.com/post/52908</guid><dc:creator><![CDATA[NixonRedgrave]]></dc:creator><pubDate>Thu, 30 Jul 2026 05:42:41 GMT</pubDate></item><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Thu, 30 Jul 2026 00:28:07 GMT]]></title><description><![CDATA[<p dir="auto">I suppose I ought to add that there’s another issue I’ve never seen with an aircraft until the 114.</p>
<p dir="auto">I can tune COM1 to ATIS (again, via BATC). When I tune COM1 to Tower or Ground, and switch it to active, BATC doesn’t see the frequency — it acts like it’s an unknown frequency. This is extra odd given it <em>can</em> see and recognize the ATIS frequency.</p>
<p dir="auto">Ok, so I can go into BATC and click the frequency for ground or tower there and it’s able to automatically tune the in-sim radio to that frequency. When I do this, BATC tunes the <em>standby</em> frequency. Upon doing this, suddenly the ground or tower frequency is recognized. I can even retune standby to ATIS and the active, still tuned to ground or tower, will continue to be recognized by BATC. I can even swap between ATIS and ground/tower with no issue.</p>
<p dir="auto">I saw this today at both my departing and arrival airports.</p>
<p dir="auto">I’m unsure why this would be, but perhaps a glance at the incoming VARs that are able to tune the radios from external apps might be in order?</p>
]]></description><link>https://community.justflight.com/post/52902</link><guid isPermaLink="true">https://community.justflight.com/post/52902</guid><dc:creator><![CDATA[NixonRedgrave]]></dc:creator><pubDate>Thu, 30 Jul 2026 00:28:07 GMT</pubDate></item><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Thu, 30 Jul 2026 00:20:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nixonredgrave">@<bdi>NixonRedgrave</bdi></a> Thank you!!</p>
]]></description><link>https://community.justflight.com/post/52901</link><guid isPermaLink="true">https://community.justflight.com/post/52901</guid><dc:creator><![CDATA[Black Square]]></dc:creator><pubDate>Thu, 30 Jul 2026 00:20:18 GMT</pubDate></item><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Thu, 30 Jul 2026 00:19:33 GMT]]></title><description><![CDATA[<p dir="auto">I’ve posed the question. When I receive an answer, I’ll get back to you,</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://community.justflight.com/post/52900</link><guid isPermaLink="true">https://community.justflight.com/post/52900</guid><dc:creator><![CDATA[NixonRedgrave]]></dc:creator><pubDate>Thu, 30 Jul 2026 00:19:33 GMT</pubDate></item><item><title><![CDATA[Reply to BATC not Recognizing COM2 on Wed, 29 Jul 2026 20:30:52 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nixonredgrave">@<bdi>NixonRedgrave</bdi></a> I recall this coming up not too long ago in another of my aircraft, though I'm not sure it was BATC.  I haven't seen wide ranging reports of this, though.  Do you think you could get BATC to say what variable they are looking for, if not <code>CIRCUIT NAVCOM2 ON</code>?</p>
]]></description><link>https://community.justflight.com/post/52858</link><guid isPermaLink="true">https://community.justflight.com/post/52858</guid><dc:creator><![CDATA[Black Square]]></dc:creator><pubDate>Wed, 29 Jul 2026 20:30:52 GMT</pubDate></item></channel></rss>