Guido

OK, I identified the problem. When I assigned presets the aircraft specific was not set and when testing it was active. Now things are OK. 🙂 Thanks for help and sorry for the issue. Rgds Guido

OK, no problem. Thanks, enjoy lunch and weekend.

Hi John, Again, thank you very much for support. Meanwhile I followed your instructions and this is the outcome: 1. Activate FSUIPC logging for Events: When activating Log Events (MSFS C172) only Event: Control 67198 Fuel_System_Valve_Open was logged. I could not find other events in the log file. Is there a filter to hide continues active events? 2. Presets: Next I assigned the presets for AS430/530 to Menu, Clear, Direct to and enter buttons. No action. Please find attached the log file for the presets and FS control buttons. 3. List available lvars: I could only find AS530_CDI_Source as a relevant variable for my panel. Range and brightness, I have not implemented. VLOC/GPS toggles at addressed VOR as it works through FSUIPC FS controls. And now? Any other tracing possibility to track the events? Note: Pity, that no commands are included in the panel.cfg file of the GNS. Rgds Guido FSUIPC7FSContrlGPS.2.log FSUIPC7_PresetsAS530.6.log

Hi John, Thank you very much for introduction and advice. I will check and come back. Nice weekend. Rgds, Guido

Hello, As in P3D I wanted to control the MSFS Garmin GNS 530 / GNS 430 (@ MSFS from Working Title) via FSUIPC button and switches assignments with my panel. Therefore, I assigned GPS direct to, enter, clear, menu and more from the FSUIPC event list to the panel buttons. Unfortunately, only GPWS switch toggle (GPS/LOC) has an effect to the sim. Are the GPS control events not supported by MSFS or are other commands/events required? Thanks for feedback

Yes I did. Some months ago when switching off cockpit tips and user tips I switched message text also off. I did not know that message text is also used by FSUIPC. Sorry. Thank you very much for the help. 😊 Rgds Guido

Hi, today I wanted to record a macro and discovered that after a "VC button" click no window is pupping up to assign a functional name to the macro. Next I tested macro recording with the default F-35 unfortunately with the same result. I discovered this after installing P3Dv4.5.13.32097 and FSUIPC 5.152. With P3Dv4.4 and (I think) FSUIPC 5.132 I had no problems. Going back to client v4.4 does not help. I checked with full screen, window mode and recorded log data but I cannot find a hint what to do next to fix the issue. Attached the FSUIPC install and macro recording logs. Thanks for support to fix my problem. Rgds Guido System info: W10x64, P3Dv.v4.5.13.32097 , FSUIPC 5.152 FSUIPC5 Install.log FSUIPC5.4.log

Hi Thomas, Thanks for the help. As proposed I deleted the old assignment and renamed the new created IDs with the former joy letters. This did the job. Rgds Guido

Hi, When transiting from FSUIPC version 4959 to 4969 I got a missing joystick issue. With this behavior my assignments are “gone” and second some joysticks are now twice listed with new IDs. I don’t understand what is creating the <<MISSING JOYSTICK>> message (except for F=737YOKE) and why the detection after. Appreciate any help to fix the issue. Guido Attached: File compare and log file FSUIPC4.log missingjoystick.pdf

Hi, I got the W10 anniversary update by surprise. And the surprise swapped the GoFlight assignments of the two GF186 (NAV<->COM) and the two GF-RP48 units. Meanwhile I understand the basics about the USB mechanism. But I don’t understand how and where the unit numbers displayed in FSUIPC (Joy# 174, 175,…) are linked with the USB HW Port/Hub number and/or USB addresses? Registry? As I am using parallel to the W10 P3D also a W7 FSX system I really would like to keep the same assignment for both sims. How can I influence W10 to change back to the former unit order (174 <-> 175) assignments? Many thanks for help

Thanks for feedback and hints. And I am sorry for the miniscule script. To answer first the question: Yes, I did read the A2A forum topic. Triggered by Paul’s comment I did the following steps which solved the problem - Replacing the RealityXP(RXPGNS.ini) with the original empty file - Deleting the lately added two A2A assignments (via input configurator) - Starting FSX. Now FSUIPC and FSX accepted key commands - Shut down FSX - Entering the same 2 assignments again using the input configurator of A2A - Renaming the RealityXP ini files to get the former status - Restarting FSX and things work Difficult to say what it was but at least I could assign ruder trim to the buttons :) Again thanks for the help. Guido

Hi After installing A2A's C182 and assigning via FSUIPC some buttons and keys to GoFlight HW some days later I could not add new key codes to buttons. Even rolling back to the older FSUIPC.ini file version does not help. All buttons are inactive or blanked (attachment) independent if specific is tagged or not. Also changing to other airplanes has no effect. Compared to the FSX.cfg version without C182 the differences are the following lines: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.rbcratezqkteollihqcneubobuntnccbtbnelcnc=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\A2A_Accusim.DLL.ihanbthaiabztoluzunklboizqttkazwciqrlbhh=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182.DLL.hekhcekicobbeznctihozwrunzwtilhoiqqazlho=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182_Illumination.DLL.aiqzikzhoanearrwbqerwwarlkanihahzitwkilw=2 C:\Program Files (x86)\GoFlight\GFDevFSX.exe.uzbqceeqtnqokbittcwwtlzrzahhanzkkkqqnhuw=1 I wonder what could block FSUIPC to accept new key/button inputs. Many thanks for the help. Rgds Guido FSUIPCBS.pdf

Hi Pete Thank you for the feedback. I will check and inform the supplier of the add-on. Rgds Guido

Hi "Every" time updating FSUIPC I run in to the issue to edit the dll.xml. As the FSUIPC update installs always at the end but before <simbase.document> <rwyadv> is not behind FSUIPC a). In this case I get a R6025 error when ending fsx. If I move FSUIPC before rwyadv the problem is solved b ). It is easy to fix when you know what to do but the reason is not clear to me. Thanks for your feedback. File: dll.xml a) </Launch.Addon> <Launch.Addon> <Name>RwyAdv</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\RwyAdv.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </SimBase.Document> b ) </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>RwyAdv</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\RwyAdv.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </SimBase.Document>

Hi The problem is solved. I deleted FSUIPC.ini, rebuild and copy-past it. Now it works as expected. Thanks Guido

Hi I am new to LUA and below is my first simple program. It should test several 737NGX annunciation flags to control the LEDs of the second RP48. A simple RP48 LED flash test program did work. But I fight with the offsets. I did set the EnableDataBroadcast=1 and tested the Re-simconnect trick but nothing flashs. I am getting out of ideas what to do next. I appreciate your support very much. My LUA script: --Begin model = GFRP48 -- GoFlight model number unit = 1 -- Sets the Variable Device "unit" to GFRP48 174: 0; 175: 1? MCLED = 0 -- Init LED Numbers APLED = 1 ATLED = 2 FMCLED = 3 -- Function Master Cautionto light on/off function MasterCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,MCLED) -- Turn RP48 2 MCLED ON else gfd.ClearLight(model,unit,MCLED) -- Turn RP48 2 MCLED OFF end end -- Function AP Cautionto light on/off function APCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,APLED) -- Turn RP48 2 APLED ON else gfd.ClearLight(model,unit,APLED) -- Turn RP48 2 APLED OFF end end -- Function AT Cautionto light on/off function ATCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,ATLED) -- Turn RP48 3 ATLED ON else gfd.ClearLight(model,unit,ATLED) -- Turn RP48 3 ATLED OFF end end -- Function FMC Cautionto light on/off function FMCCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,FMCLED) -- Turn RP48 2 FMCLED ON else gfd.ClearLight(model,unit,FMCLED) -- Turn RP48 2 FMCLED OFF end end -- Main program gfd.SetBright(model, unit, 15) -- Sets the Brightness of Unit#1 on the GFP8 to 15 (full). event.offset(0x6506, "UW","MasterCaution") event.offset(0x6550, "UW","APCaution") event.offset(0x6552, "UW","ATCaution") event.offset(0x6554, "UW","FMCCaution") --END Thank you for help and bregards Guido

Hi Pete Sorry I did not catch it the first time. The advanced users guide was not part ot the initial down load package and I mixed it with the users & programmers guide. Again sorry about that. Now things are clear. Rgds Guido

Hi Pete I am one of the 3D cockpit users and therefore I think mouse macros will not work. Until now I did not study LUA and I guess I would need a variable list. Do you know a good link to learn and start with LUA? For Wilco’s A320 is an interface available called exporter to control A320 specific commands. I am using it already to manage the altitude information. I read through FSUIPC the commanded altitude in FSX (coming from my MCP-Pro) and write it through the exporter to the A320s virtual FCU. What I want to do now is to detect some MCP-Pro button event via FSUIPC “inside” FSX (I am not using the MCP-Pro development kit) and then write the event into the exporter interface. The trouble is that I do not know how to detect the MCP-Pro button event (#158/11,12,13) via FSUIPC and FSX. The rest is no problem as I did test it with a joystick button event (offsets 32FF, 2910 and joystick #0/button 2). I hope there is a way to detect the event via FSUIPC. I am not sure what I can do with offset 66C0 as it is for general use. Can I use it to detect “joystick” number 158 button 11? I guess not. I am sorry for my not so usual “miss use” of FSUIPC. I am also happy if another easier method exist to do the same. Many thanks for your help. Rgds Guido

Hi Pete I want to emulate the Airbus FCU’s push/pull button functions with MCP-Pro’s rotary knops push button event to switch between managed and unmanaged mode. In the pilots guide I could not find a key code for this function. But by using Eric’s exporter interface it would be easy to implement it. The “only” problem is that I cannot detect the “key” event. As FSUIPC does detect it in the button assignment window I hope to have a chance to detect it somehow through it. But how is the question! Can you help? Thanks for your support. It is really excellent. Rgds Guido

Hi Pete Maybe I don’t understand the access or numbering method. Reading the description for offset 2910: Byte 0 (bits 0-7): Joystick number (0-15) + 128. In other words 128 for Joystick 0, 129 for joystick 1, etc. Byte 1 (bits 8-15): Button number (0-39) The FSUIPCs Joystick assignment window shows joy# 158 and the button window 11, 12, 13 when pushing the MCP-Pro buttons. If the "joystick" number is already > 128 (like # 158) then the sum is out of range for Byte 0. What I don't understand is how to calculate the right "joystick" number for byte 0 of offset 2910. What I want to do is to assign Wilco A320 specific commands to 3 push buttons on my MCP-Pro. Thank you for your help. Rgds Guido

Hi Pete After my difficulties controlling throttle I wanted to do something easy! I wanted to read keys from MCP-Pro and assign a new function (for Airbus use). The tests with my Joystick was no problem. FSUIPC button asignment window shows Joy# 0 and button 2. The button is detected at (32FF) and which one selected via (2910). But the MCP-Pro shows in FSUIPC Joy# 158 buttons 11,12,13. The joystick number is out of range! How should I handle this correctly? Any idea? Sorry for bother you again but this is the “last” thing I wanted to do for now. Rgds

Hi Pete I am sorry to bother you again! After several attempts to make my throttle HW working with WA320 I realized that it is “not possible” to do this via FSUIPC. As written the WA320 uses throttle information compatible to DirectX and uses the AXIS_THROTTLE1(+2)_SET. The Serial USB TQ737 joystick driver does not support DirectX. Therefore I wanted to: Read 88C Engine1AxisValue Write to 3114 Engine1AxisValue and 3110 (66420) to AXIS_THROTTLE1_SET Write to 88C Engine1AxisValue The last write to 88C is to overwrite the FSX throttle increase from the write to 3310. If the engines are off levers move more or less on the 2D/3D display. But as soon as the engines are on the thing gets unstable and wild. I think by writing back to the 88C register, to remove the unwanted additional throttle increase, interferes with the FSX throttle loop. I did the same exercise using F1..F4 keys. The behavior is the same. Every F3 key write to (3200) increases the value at 88C and is then different to AXIS_THROTTLE1_SET. The attempt to overwrite the changed value at 88C makes the system unstable (levers jump up and down if engines are on)! So I think it is not possible to do make my joystick work with the WA320 via FSUIPC L. Rgds Guido

Hi Pete Yes, I have a solution for now. But I also think it is a bit complicated for the little I wanted to do. In deed I need to study what the Lua plug-in can do. About your lever movement question: I referred to the WA320 levers displayed at the monitor. Again thank you for your support and patient Guido

You are trying to use an axis control from a Client PC, not on the FS PC? A: The throttle axis is on the FS PC. At this very moment I use the wide client as "programming station" and for further developments or better further challengesJ. Er, sorry. Now I am really confused. Where is this USB connection< then? Surely not on the WideClient PC? How does it get its value into FS? A: Yes the Serial-USB-HW is connected to the FS PC. The client only reads and writes the values from/to the FS PC. These levers, are they motor controlled by any chance? If so, the software used with them might be READING the value from 088C, moving the lever according, which is then giving you a new position which you are feeding back -- result positive feedback, completely unwanted. A: I had the option with or without motor. For “time” reasons and for Airbus simulation compatibility I decided to skip the motor option. Writes to 089A are either ignored (except for a copy placed at 3330) if the thorttles are currently disconnected for AutoThrottle control, or result in a write to 088C, so I'm not at all surprised. 089A is realy simply a disconnectable 088C intended for autothrottle motor control applications where the feed through has to stop when A/T is engaged. A: OK, now I understand why the lever position did not change when I copied the position value to 089A only (I hoped to simulate a direct x axis input to FSX). I guess the unwanted move from the commanded lever position to full throttle could come from the motor option of my throttle. This seems to stop when “closing” the feedback loop from “KEY_AXIS_THROTTLE1_SET via 0x3110” to 089A (read 088C, write 089A and 03110). Sorry, you'll need to explain what you mean there. Since copying to 089A shouldn't do anything, isn't this the same as doing "copy the read value from 0x88C “calibrated” to 0x3114 addressing KEY_AXIS_THROTTLE1_SET via 0x3110", which would certainly make more sense. What exactly do you mean by "calibrated" in this context? A Calibration: The values delivered at 088C are from 0 to +16k. To move the throttles over the full range on the displayed WA320 I have to send -16k to +16k. Sorry, what do you mean? I wish I knew a bit more about this weird throttle device of yours. Did you build it yourself? Why is it so unorthodox? 1. A: Maybe this helps: B737 TQ from Poland Videos zu B737 TQ poland Throttle maker feedback: The FeelThere Airbus probably uses out of standard ways to manage thrusts, as FSX itself doesn't have specific commands for this type of throttle. In our TQ throttle driver, we use only Microsoft's directives, as from Simconnect SDK, that is writing throttles values from -4096 to +16368 into throttle offsets, depending on lever positions on the TQ. My problem is that no direct x commands are used and my guess is that the Wilco Bus does not handle the Simconnect SDK inputs. Regards Pete Thank you for the smart feedback. Rgds Guido

Hi Pete Over the weekend I did quite an exercise in the attempt to make my TQ throttle work with Wilco’s A320 “misusing” FSUIPC (actually Wide Client). My steps: A: Read lever position in FSUIPC: The serial USB driver throttle input is available at “offset” 0x88C. B: The next thing was to copy the 0x88C value as proposed to 0x3114 addressing KEY_AXIS_THROTTLE1_SET via 0x3110 and wow the levers did move but move and move to max without any further lever movement. C: Next was to check what will happen when I copy the 0x88C value simply to 0x89A. No lever movement. D: When I copy the read value from 0x88C to 0x89A and “calibrated” to 0x3114 addressing KEY_AXIS_THROTTLE1_SET via 0x3110 did make it. But I am not sure if this is a clever implementation. I think my Logitech and CH-Throttle use the standard USB driver/gaming interface. FSX reads it from there and stores the values at the "right" locations that the Airbus can use it. I wonder if this can be emulated by using FSUIPC easier or if the current implementation is reasonable. By the way which document gives a good insight about the FSX and FSUIPC for me? Rgds Guido