This are the (new) Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, and are still available (until the end of the year) for read-only here.

At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Opencockpits MSFS20…
 
Notifications
Clear all

Opencockpits MSFS2020 PMDG FSUIPC

Posts: 1
Registered
Topic starter
(@driver738)
Joined: 16 hours ago

Hi Guys. I have managed to bring back to life 3 (ancient!) pedestal OC modules, COMM, NAV, and ATC Transponder. With FSUIPC, COMM and NAV work great, no tweaking required. The ATC module works fine on any adjust of the main rotary encoder, to change the squawk code. However when physically changing the other Encoder for Stby/Off/Xpndr/Ta/Ta/Ra the change is not reflected in the sim, on the PMDG pedestal, it does not move. I’m no expert but FSUIPC logging sees some kind of event when the hardware encoder is turned:

8098641 *** EVENT: Cntrl= 65715 (0x000100b3), Param= 512 (0x00000200) XPNDR_SET

Any ideas if we can get this encoder working? Apologies if this turns out to be an Opencockpits issue. ( I know before I rebuilt the sim, this did work ok previously, a few moons back..).

 

 

 

 


1 Reply
Posts: 114
Admin
(@fsuipc)
Joined: 6 months ago

Posted by: @driver738

The ATC module works fine on any adjust of the main rotary encoder, to change the squawk code. However when physically changing the other Encoder for Stby/Off/Xpndr/Ta/Ta/Ra the change is not reflected in the sim, on the PMDG pedestal, it does not move.

So the ‘selector’ encoder doesn’t change the selection, and the ‘main’ encoder always acts as if the ‘selector’ encoder is in the ‘Xpndr’ position?

Posted by: @driver738

I’m no expert but FSUIPC logging sees some kind of event when the hardware encoder is turned:

8098641 *** EVENT: Cntrl= 65715 (0x000100b3), Param= 512 (0x00000200) XPNDR_SET

That is setting the transponder/squawk code to 0200 (or maybe 1200, if the leading 0 is assumed). So it looks like the main rotary is always controlling the Xpndr.

Posted by: @driver738

Any ideas if we can get this encoder working?

This depends on how and where you have assigned the rotary encoders. To control the selector/mode switch/rotary in the PMDG 737, you would use the following PMDG custom control:

#define EVT_TCAS_MODE (THIRD_PARTY_EVENT_ID_MIN + 800)

As for the other rotary, I am not sure about this as there is no such knob on the TCAS – there are only rotaries to control the ATC code left/right, so I am not sure what this should control when the selector/mode switch is in each position. However, the standard way of using an inc/dec rotary where the value being changed depends on a selector switch is to overload the assignments on the rotary (i.e. assign to every inc/dec function needed) and then add a conditional on the assignments so that only one is sent depending on the position of the selector/mode switch. For the PMDG 737, this would be a conditional on the value held in the PMDG-specific offset for XPDR_ModeSel:

6C64 1 BYTE XPDR_ModeSel:  0: STBY
                                                    1: ALT RPTG OFF
                                                     ...
                                                    4: TA / RA

If you are assigning in FSUIPC, I can help further if you provide more information on what you expect the rotary to control (depending on the mode), but if using SIOC I cannot help with this.

John


Reply