This are the 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, but are now no longer available.
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 MSFS2020 PMDG FSUIPC
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..).
Posted by: @driver738The 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: @driver738I’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: @driver738Any 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 / RAIf 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
Many thanks John, it's tricky for me to type this issue to explain, but see if this is better:
I'm using FSUIPC 7 (it auto loads), MSFS 2020 and the PMDG 737-700.
The ATC Transponder hardware Module from OpenCockpits has 2 enccoders and 1 rotary switch. (I think we can ignore the XPNDR 1/2, ALT SOURCE 1/2 and IDENT switches for the moment)
As you know. On my hardware module, the 2 encoders and 1 rotary switch are used as follows:
Left encoder - Function normaly is to advance the 'selection' of the Squawk code digit, moving 1 digit left or right. This is the way it's always worked and is currently working fine with FSUIPC removed link When phsically rotated, it selects the next digit correctly, in the PMDG Sim Transponder digit window.
Right encoder - Function normaly is to change the numeric value up/down of the Squawk code digit as selected using above. Again, this is the correct action I'd expect and currently it works fine visually, changing correctly inside the Sim Transponder digit window.
Top right Rotary Selector switch - Function normaly is used to select STBY/ALT RPTG OFF removed link This is the selector switch I have the issue with. Physically turning it on the hardware doesn't show the same or any response on the Transponsder inside the PMDG sim, mounted in the virtual cockpit removed link Visually inside the sim it remains static. Therefor in the PMDG sim I'm unable to select through STBY removed link using this hardware switch. The switch can only be rotated correctly in the sim using the mouse.
I'm not using SIOC nor have assigned anything. I've not programmed anything. I'm just in the process of bringing this Transponder module back to life 'straight out the box' plugging it in to the USB, runing FSUIP/PMDG and seeing what happens.
I'm not familar with the deep workings of FSUIPC, so all I've done is grab that (previous post) log line in the log cosole, among a stack of others. When running the sim, I can move that hardware rotary switch for selecting STBY removed link etc. I can then see lines generated in the Cosole log. Seems to indicate to me that FSUPIC is at leat 'seeing' something as the switch is rotated around the positions. Hope I've been a bit better at explaing here!
Posted by: @driver738Top right Rotary Selector switch – Function normaly is used to select STBY/ALT RPTG OFF removed link This is the selector switch I have the issue with. Physically turning it on the hardware doesn’t show the same or any response on the Transponsder inside the PMDG sim, mounted in the virtual cockpit removed link Visually inside the sim it remains static. Therefor in the PMDG sim I’m unable to select through STBY removed link using this hardware switch. The switch can only be rotated correctly in the sim using the mouse.
How have you assigned this rotary? As I said, for this you need to use the PMDG custom control. See the FAQ entries on using PMDG custom controls.
Posted by: @driver738I’m not using SIOC nor have assigned anything. I’ve not programmed anything. I’m just in the process of bringing this Transponder module back to life ‘straight out the box’ plugging it in to the USB, runing FSUIP/PMDG and seeing what happens.
But the transponder module does seem to be working, in that when you turn the rotaries they are updating the values in the VC displays. So is this device being detected and assigned automatically in MSFS? Does FSUIPC see this device? i.e. when you turn the selector switch, does FSUIPC recognise the buttons? If so, you can try unassigning in MSFS and assigning in FSUIPC.
Posted by: @driver738When running the sim, I can move that hardware rotary switch for selecting STBY removed link etc. I can then see lines generated in the Cosole log. Seems to indicate to me that FSUPIC is at leat ‘seeing’ something as the switch is rotated around the positions. Hope I’ve been a bit better at explaing here!
FSUIPC is just logging the events seen in the FS - I do not know where this event is originating. Can you attach a log and ini file so that I can see what is happening please. Activate logging for Buttons & Keys and Events.
Not sure why you post has so many removed links...
John
Every time I put in a "/then text" its saying 'removed link'. Very annoying. I also edited the post but the forum engine didn't change it. Thx! Stand by.