Jump to content

PFC Cirrus 2 Pro not recognized


Recommended Posts

16 hours ago, jimbooo said:

Now all the input changes seem to be active BUT the stack is still dark ?

All the displays are backlit digital numerals and the entire stack is unlit.

I was afraid that might be the case. The decoding of the switches is, as PFC told me, the same as for the original Avionics -- just arriving from different devices which I needed to open in my code.

The output to the displays is, however, obviously another matter. They probably need explicitly directing to the correct device. That is not so easy (especially, for instance, for the 4 comm radios which look identical to the software at present.

16 hours ago, jimbooo said:

seems like we are close to success here  -  any ideas ?

I don't know. I'd need to delve into the code much more deeply. I may pluck up courage and look at that, but not this week. One thing may help me: please try again but first set the LogTxData parameter in the PFChid64.ini file to "Yes". This might show me where and what is actually being sent to the displays and indicators -- probably mis-addressed.

Unfortunately the code was written many years ago and I don't remember it. (Old age wrecks memory). 😞

So, sorry, no guarantees. I'll let you know if I find something for you to try. Meanwhile, do the switches and dials do what you expect on the model within MSFS? I see that the FSUIPC log shows the appropriate commands being sent.

Pete

 

 

Link to comment
Share on other sites

yes    the commands sent that register in the live log have the correct effect in the MSFS cockpit.   the radio knobs change the frequencies, the swap button operates properly ,the transponder codes change correctly.  i  think that part of the code is amazingly correct.

only the backlighting is off....

even though PFC is adamant about not supporting MSFS i think they keep a lid on that so they dont have to do any support for any interfaces like FSUIPC.     Your program works so well that it really increases their potential market.    Funny that they dont acknowledge that much...   It even worked many years ago with the PFC Serial console. (I had one in the MSFS2004 era)

Just for fun I will call my support guy at PFC.  maybe there is an easy way to simply light up the stack.  should be an easy one bit command.    If we can just light it up all should be working great...

Ill let  you know what i can find out.

Im getting older tooooooo.

Happy New Year...

 

Link to comment
Share on other sites

per your instructions:

Set LogTxData to Yes in PFChid64.ini

Loaded Beech Baron and got to runway.

Exercised buttons on Radio Stack in the following order:

Com1 / Com2 /Nav1 / Nav2 /Transponder /Audio Panel / Autopilot VS and Target Altitude.

All work as they should in the MSFS cockpit panel and, of course, register in real time on the FSUIPC log.

Checked to make sure all the Avionics Master switches are "On"

Closed program.

Attached are the 2 log files for you to see.

Hopefully they help.

 

FSUIPC7.log PFChid64.log

Link to comment
Share on other sites

19 hours ago, jimbooo said:

Attached are the 2 log files for you to see.

Hopefully they help.

Well, there's lots of information for me to analyse. I'll dig out the original specs from PFC which I worked from and see if I can make sense of it all. There are certainly lots of Writes to the various devices, but there must be something simple missing to get them to actually light up.

One thing I'm definitely going to ask PFC about -- how to distinguish between the 4 COMM devices when displaying the frequencies. Obviously the input details identify themselves as you turn the knobs (the data commands received will say COM1, COM2, NAV1 or NAV2), but initially, before you turn one, the driver needs to know which one to send each of the MSFS/P2D frequencies to.

I'll not get to this now till next week -- probably Tuesday or after.

Meanwhile, Happy New Year!

Pete

 

Link to comment
Share on other sites

thanks Pete

when the Main Console is being energized there is a point where it lights up..  Theres likely something like that with the Radio Stack.  Even in the MSFS calibration screen they just have 4 separate entries for radios - rather than Com1, Com2, Nav1, Nav2 etc..

Sorry to make you revisit OLD programming - its a big mountain.....

Happy New Year

Link to comment
Share on other sites

ps      on the subject of the radios -

when i exercise the radio knobs on my Radio Stack your programming does connect the correct knobs to the correct radio.

So you somehow, at the time you programmed those radios, could differentiate them.

Its odd that MSFS doesnt list them as Com1, Nav1 etc - but just 4 separate entries titled "radio"

Link to comment
Share on other sites

17 hours ago, jimbooo said:

So you somehow, at the time you programmed those radios, could differentiate them.

No, the commands cominmg from the knobs or switches identify themselves.

I could deduce which one is which from that, but the radios need to display their current FS-set values on switch on, without expecting you to press a switch or turn a knob. If all else fails I can certainly do that -- once identified their device numbers would not change during that session.

Pete

 

Link to comment
Share on other sites

  • 4 weeks later...

Hi there,

At last I got some hints regarding commands to try to get your radio stack lighting up.  There were three others apart from the "ILLUMINATOR_POWER" one I was already using, and which worked fully on the earlier integrated radio stack. The other three are ILLUMINATOR_BACKLIGHT, ILLUMINATOR_AVI_MASTER and ILLUMINATOR_SIMULATOR_POWER.

I probably don't need to use all of those, but I've added them all in any case. The ones not really needed won't do any harm.

I attach the revised DLL below. Please try this and let me know.

Pete

PFChid64.dll

 

  • Like 1
Link to comment
Share on other sites

WOW     you got it  !!!!

with the new .dll the entire stack is lit and all knobs and buttons work perfectly.

should i just leave all 3 of the new commands in the .dll or should i experiment with which one is the critical one ????

 

thanks for your long term commitment to help me make this work.....

Happy New Year

Link to comment
Share on other sites

13 hours ago, jimbooo said:

should i just leave all 3 of the new commands in the .dll or should i experiment with which one is the critical one ????

I'd leave well alone.

As this update works I shall make it the current release.

Pete

 

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
 Share

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