Guido

OK. The important click is heading and this works. Thanks for support.

Yes, it is the case. But as this does not reflect the real behavior I opted for an improved method to synch with the current altitude. But failed. GFC 500 Manual: 2) Select Altitude and use the Selection Knob to change the Selected Altitude. Syncing to the current altitude: Press the ALT SEL Knob on the GMC 507

Why not use the included preset XCub Ap Alt Push which uses INDICATED ALTITUDE instead of PLANE ALTITUDE? XCub Ap Alt Push: It has the same issue therefore I tested a different option. (Issue: With each push one 100ft step down/up until reaching the actual Alt by +/- 100ft)

Outcome of today’s tests: The following two LUA and Preset implementations work: -- LUA implementation 1 ipc.execCalcCode(" (A:PLANE HEADING DEGREES GYRO, degrees) (>K:HEADING_BUG_SET) ") -- LUA implementation 2 bearing = ipc.readUW(0x2FA8) ipc.control(66042, bearing); And Presets: SYNC_HDG_BUG_TO_HSI_HDG1#(A:PLANE HEADING DEGREES GYRO, degrees) (>K:HEADING_BUG_SET) SYNC_HDG_BUG_TO_HSI_HDG2#(A:PLANE HEADING DEGREES MAGNETIC, degrees) (>K:HEADING_BUG_SET) However, I struggle with the ALT command: SYNC_AP_ALT_TO_ACT_ALT0#(A:PLANE ALTITUDE, feet) (>K:AP_ALT_VAR_SET_ENGLISH) (real alt) As the Preset XCub Ap Alt Push (altimeter alt) Both work as strange as the mouse click implementation: Step down/up by 100ft until reaching the actual Alt by +/- 100ft.

Thank you very much for help. I appreciate it very much. AP GFC 500: The AP is part of the MSFS X Cub delivery (VC). About the source I think it is Asobo. Together with the G3x (Working Title Sim) and external GTN 650 (TDS Sim) it is an easy-to-use AP offering amazing system functionality. The APs two rotary knobs push functions synch the heading bug with the current heading and AP alt preset with current alt. Fast and less dialing. I will check the proposed two ways by adding it to myevents.txt by second half of next week (after 7th). Meanwhile I study the proposed implementations.

As I could not find an event/preset for synching the HSI heading bug to current heading, for use with the GFC 500 AP, I traced the event. It looks like this: 0000174861 Event: 066042 Event Data: 000263 Event Name: HEADING_BUG_SET I wonder if something like this is possible with a FSUIPC Macro: //Read actual heading const HSIDegree = SimVar.GetSimVarValue('HSI BEARING', 'degree'); //Set heading bug to actual heading SimVar.SetSimVarValue('HEADING_BUG_SET', ' HSIDegree ', '0'); Or how this could be implemented for us in FSUIPC. Appreciate advice how to or if the event already exists the link to the event. Rgds, 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