Jump to content
The simFlight Network Forums

PFC Avionics COM1 <-> COM2 switched


Recommended Posts

I'm using the PFC Cirrus II and Avionics stack with MSFS v9.1. I've installed FSUIPC v353 and PFC v1921.

Everything works well except that COM1 and COM2 are switched when controlled within MSFS. That is to say, if I change COM1 in MSFS, COM2 is changed on the avionics stack. Similarly, COM1 on the stack changes COM2 on the screen.

I've looked through the options, but can't find the reason. Any clues why?

Thank you for your kind attention.

Link to comment
Share on other sites

I'm using the PFC Cirrus II and Avionics stack with MSFS v9.1. I've installed FSUIPC v353 and PFC v1921.

PFC DLL Version 1.996 works a bit better than 1.921 -- you can get it from the "interim versions" announcement at the top of this forum.

Everything works well except that COM1 and COM2 are switched when controlled within MSFS. That is to say, if I change COM1 in MSFS, COM2 is changed on the avionics stack. Similarly, COM1 on the stack changes COM2 on the screen.

I've looked through the options, but can't find the reason. Any clues why?

There are extensive facilities in PFC.DLL for using both COM1 and COM2 interchangeably. These were first in place in the days when FS only supported COM1. They were kept for use with programs like Radar Contact and on-line services such as AVSIM which use COM1 exclusively -- it allows 4 frequencies all to be preset and switchable to the active COM1 radio.

The same facilities are used on the Jetliner console, which only sports a single COM radio, to allow use of both COM1 and COM2 in FS.

It sounds like you have enabled these facilities, and possibly inadvertently activated a swap.

I'm not sure why you've not found the details, but they are the first to be extensively described in the Avionics Options section of the manual, under the sub-heading COM radios

Please check the section in the document and come back if you still can't sort it out.

Regards

Pete

Link to comment
Share on other sites

Thanks for the hints Pete.

I've managed to pinpoint the problem.

It was as simple as pushing the ON/OFF button on COM1!

By pure chance, I've never encountered this before despite having played with the buttons many times!

Link to comment
Share on other sites

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...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.