MatzeH84

I somehow cured the problem. In the log I only could see 504922 3172 WRITE0[13976] 3110, 8 bytes: 1F 02 01 00 00 00 00 00 ........ 508687 3172 WRITE0[13976] 3110, 8 bytes: 20 02 01 00 00 00 00 00 ....... when actuating the switch. But I deleted some general assignments to macros (maybe ported in from P3D config) which were not found anymore, and the problem is gone. SO once again, while not knowing the solution, you pointed me in the right direction to find the issue myself. Many thanks, your great support is very much appreciated! All the best.

Thanks John for coming back to me. It happens either way, both when in the taskbar or in the system tray. It will always move to the task bar and blink/highlight, bringing up the hidden taskbar. Until now I couldn't figure it out- when I open the console by clicking on the icon in the task bar, only the console comes up in its usual state. WIll try with the console already open.

As said in the title, when I actuate the Vrinsight M Panel's gear switch (up or down doesn't matter), it works perfectly function wise, but always brings up the Taskbar with the FSUIPC icon blinking. When I click on it, FSUIPC comes up as it usually would, nothing more. It's a bit distracting however, when you always have to click the icon to make the Taskbar disappear again. FSUIPC redownloaded yesterday, but it had been this way since release of the MSFS version. In P3D it was OK. The M panel is not configured in FSUIPC in any way. It there a simple solution? Best Matthias

Thank you, I will try that. As this is an older unit (black color, not the current Grey) it could also mean they were used so extensively that buttons are triggered that shouldn't.. I'll check that as well, maybe it's more a mechanical problem rather than a software issue.

Thanks John for your quick reply. Sorry, work kept me from answering until now. I already tried to use direct keybinds like to suggested, as it seemed the obvious and easiest option. However, this does not really work well. Let's take the 4th dial for example. I turn it clockwise slowly. FSUIPC registers buttons 22 and 23, but also 20 and 21 in between. Counterclockwise it registers mainly 20 and 21, but also 22 and 23 in between. Similar for every other dial. The faster I turn the knob, the more apparent becomes the error. This means, my values/ dials in the sim are jumping back and forth instead of counting straight up or down. I hoped the LUA would help to rectify the issue, that's why I wanted to test it.

Hi there! I got myself a used GoFlight RP48. Goal is to be able to assign functions to the rotary knobs via the button/switches function in FSUIPC. Example: Turn knob 1, turn dial (altimeter, heading, whatever) in the sim via the heading bug inc/Dec command. I'm not someone with huge programming skills. I spend about one day researching here and elsewhere for a "simple" solution, thinking I can't be the only one using this unit and FSUIPC. Currently when I turn the knob, up to 3 buttons are recognized by FSUIPC per direction, however they are mixing up so the dial is not dialing up, but jumping back and forth. I used the rotaries.lua file, made it automatically load and recognize the unit (I guess). But FSUIPC is still recognizing the "real" buttons instead of virtual ones I aim for. HID scanner log: Device at "\\?\hid#vid_09f3&pid_0028#9&34a1e11e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=09F3, Product=0028 (Version 1.1) Manufacturer= GoFlight Product= GoFlight GF-RP48 Serial Number= GoFlight GF-RP48 Usage Page: 2 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 2 Number of Link Collection Nodes: 4 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 9 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 1 Number of Feature Value Caps: 2 Number of Feature Data Indices: 3 Buttons range 1 -> 8 at indices 1 -> 8 Value Dial at index 0, range -128 -> 127, using 8 bits ********* FSUIPC7, Version 7.0.5a (12th January 2021) by John Dowson ********* Checking for FS path in 'C:\Users\(deleted)\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt' FS path found = D:\MSFS\ WebSocket server found: D:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0) Reading options from "D:\FSUIPC7\FSUIPC7.ini" Checking the Registrations now ... User Name="(deleted)" User Addr="(deleted)" FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 109 System time = 19/01/2021 22:44:32 109 FLT path = "C:\Users\\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 125 ------------------------------------------------------------------- 203 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 219 FS path = "D:\MSFS\" 219 ---------------------- Joystick Device Scan ----------------------- 234 Product= Saitek Pro Flight Yoke 250 Manufacturer= Saitek 250 Vendor=06A3, Product=0BAC (Version 3.1) 265 GUIDs returned for product: VID_06A3&PID_0BAC: 265 GUID= {5F23DDB0-62FF-11EA-8002-444553540000} 265 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255 265 Product= Alpha Flight Controls 265 Manufacturer= Honeycomb Aeronautical 265 Serial Number= 6D323C0C192C3B00 265 Vendor=294B, Product=1900 (Version 2.32) 265 GUIDs returned for product: VID_294B&PID_1900: 265 GUID= {E9B5DA70-0348-11EB-8001-444553540000} 265 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0 265 Product= T.A320 Pilot 281 Manufacturer= Thrustmaster 281 Serial Number= 1 281 Vendor=044F, Product=0405 (Version 2.0) 281 GUIDs returned for product: VID_044F&PID_0405: 281 GUID= {904D9F70-F2B5-11EA-8001-444553540000} 281 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 281 Product= Saitek Pro Flight Rudder Pedals 281 Manufacturer= Saitek 281 Vendor=06A3, Product=0763 (Version 1.0) 281 GUIDs returned for product: VID_06A3&PID_0763: 281 GUID= {E53EFA00-6373-11EA-8002-444553540000} 281 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 297 Product= Saitek Pro Flight Quadrant 297 Manufacturer= Saitek 297 Vendor=06A3, Product=0C2D (Version 2.0) 297 GUIDs returned for product: VID_06A3&PID_0C2D: 297 GUID= {E53EFA00-6373-11EA-8003-444553540000} 297 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 312 Product= GF-TPM Throttle/Prop/Mixture Control 312 Manufacturer= GoFlight 328 Vendor=09F3, Product=0210 (Version 1.1) 328 GUIDs returned for product: VID_09F3&PID_0210: 328 GUID= {E53D4C50-6373-11EA-8001-444553540000} 328 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 328 ------------------------------------------------------------------- 328 Device acquired for use: 328 Joystick ID = 0 (Registry okay) 328 0=Saitek Pro Flight Yoke 328 0.GUID={5F23DDB0-62FF-11EA-8002-444553540000} 328 Device acquired for use: 328 Joystick ID = 5 (Registry okay) 328 5=Alpha Flight Controls 328 5.GUID={E9B5DA70-0348-11EB-8001-444553540000} 328 Device acquired for use: 328 Joystick ID = 4 (Registry okay) 328 4=T.A320 Pilot 328 4.GUID={904D9F70-F2B5-11EA-8001-444553540000} 328 Device acquired for use: 328 Joystick ID = 2 (Registry okay) 328 2=Saitek Pro Flight Rudder Pedals 328 2.GUID={E53EFA00-6373-11EA-8002-444553540000} 328 Device acquired for use: 328 Joystick ID = 3 (Registry okay) 328 3=Saitek Pro Flight Quadrant 328 3.GUID={E53EFA00-6373-11EA-8003-444553540000} 328 Device acquired for use: 328 Joystick ID = 1 (Registry okay) 328 1=GoFlight GF-TPM Throttle/Pitch/Mixture control 344 1.GUID={E53D4C50-6373-11EA-8001-444553540000} 344 ------------------------------------------------------------------- 359 LogOptions=00000000 00000005 375 Using "D:\FSUIPC7\GFDEV64.DLL", version 2.2.8.0 375 GoFlight GFRP48 detected: 1 device 375 GoFlight GFSECM detected: 1 device 3203 Simulator detected 8297 SimConnect_Open succeeded 8297 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 8297 MSFS version = 11.0.282174.999 8297 Initialising SimConnect data requests now 8359 C:\Users\MHane\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 8359 SimObjects\Airplanes\Asobo_DA40_NG\aircraft.CFG 8359 User Aircraft ID 1 supplied, now being used 8422 Aircraft loaded: running normally now ... 8906 Aircraft="DA40-NG Asobo" 8937 System time = 19/01/2021 22:44:41, Simulator time = 22:44:36 (21:44Z) 14859 -------------------- Starting everything now ---------------------- 14937 LUA.1: beginning "D:\FSUIPC7\rotaries.lua" 14937 LUA.1: D:\FSUIPC7\rotaries.lua:1 14953 LUA.1: Global: ipcPARAM = 0 14969 LUA.1: D:\FSUIPC7\rotaries.lua:2 14984 LUA.1: Global: Vendor = GoFlight 15000 LUA.1: D:\FSUIPC7\rotaries.lua:3 15015 LUA.1: Global: Product = GF-RP48 15031 LUA.1: D:\FSUIPC7\rotaries.lua:10 15047 LUA.1: Global: Device = 0 15062 LUA.1: D:\FSUIPC7\rotaries.lua:16 15078 LUA.1: Global: Rotaries = table: 0000022D3416FC50 15219 LUA.1: D:\FSUIPC7\rotaries.lua:18 15234 LUA.1: Global: wr = 0 15250 LUA.1: Global: wrf = 2 15265 LUA.1: Global: dev = 1 15281 LUA.1: Global: rd = 6 15297 LUA.1: D:\FSUIPC7\rotaries.lua:26 15312 LUA.1: D:\FSUIPC7\rotaries.lua:31 15328 LUA.1: Global: FastTimeLimit = 60 15344 LUA.1: D:\FSUIPC7\rotaries.lua:34 15359 LUA.1: Global: Pollrate = 20 15375 LUA.1: D:\FSUIPC7\rotaries.lua:35 15390 LUA.1: Global: LastTimes = table: 0000022D34170A10 15406 LUA.1: D:\FSUIPC7\rotaries.lua:36 15422 LUA.1: Global: Buttons = 0 15437 LUA.1: D:\FSUIPC7\rotaries.lua:37 15453 LUA.1: Global: PrevButtons = 0 15469 LUA.1: D:\FSUIPC7\rotaries.lua:81 15484 LUA.1: Global: Diff = 0 15500 LUA.1: D:\FSUIPC7\rotaries.lua:40 15515 LUA.1: D:\FSUIPC7\rotaries.lua:83 15547 LUA.1: Waiting for an event in "D:\FSUIPC7\rotaries.lua" 15578 LUA.1: Timer event: calling "poll" in "D:\FSUIPC7\rotaries.lua" 15578 LUA.1: D:\FSUIPC7\rotaries.lua:42 15594 LUA.1: Local: Time = 281927484 15609 LUA.1: D:\FSUIPC7\rotaries.lua:44 15625 LUA.1: Global: data = 15640 LUA.1: Global: n = 0 15656 LUA.1: D:\FSUIPC7\rotaries.lua:81 15687 LUA.1: Waiting for an event in "D:\FSUIPC7\rotaries.lua" 15687 LUA.1: Timer event: calling "poll" in "D:\FSUIPC7\rotaries.lua" 15687 LUA.1: D:\FSUIPC7\rotaries.lua:42 15703 LUA.1: Local: Time = 281927593 15719 LUA.1: D:\FSUIPC7\rotaries.lua:44 15734 LUA.1: D:\FSUIPC7\rotaries.lua:81 15765 LUA.1: Waiting for an event in "D:\FSUIPC7\rotaries.lua" 15765 LUA.1: Timer event: calling "poll" in "D:\FSUIPC7\rotaries.lua" 15765 LUA.1: D:\FSUIPC7\rotaries.lua:42 15765 LUA.1: Local: Time = 281927671 15797 LUA.1: D:\FSUIPC7\rotaries.lua:44 15812 LUA.1: D:\FSUIPC7\rotaries.lua:81 15828 LUA.1: Waiting for an event in "D:\FSUIPC7\rotaries.lua" 15828 LUA.1: Timer event: calling "poll" in "D:\FSUIPC7\rotaries.lua" (it keeps on going like that) The LUA file: Vendor = "GoFlight" Product = "GF-RP48" Device = 0 -- Multiple devices of the same name need increasing Device numbers -- Use separate Lua plug-ins for separate cards! -- NOTE: this can handle up to 16 rotaries only, using the first 64 "virtual buttons" -- List the pairs here: Rotaries = { 1,2,3,4,5,6,7,8} -- Example { 31, 30, 25, 22 } would be 31+30 for one, 25+22 for the next, and so on -- Which is clockwise and which counterclockwise doesn't matter -- you'll get -- fast and slow of each in any case dev, rd, wrf, wr, init = com.openhid(Vendor, Product, Device, Report) if dev == 0 then ipc.log("Could not open HID") ipc.exit() end -- Set the boundary time in milliseconds between -- "fast" (shorter) and "slow" (longer) signalling FastTimeLimit = 60 -- Adjust to taste -- Polling time in milliseconds: should be much shorter than -- the boundary time Pollrate = 20 -- same as 50 times per second -- Initialise variables used to keep track of things LastTimes = {} Buttons = 0 PrevButtons = 0 Diff = 0 -- This function will be called by a time event, set at the end of the program before exit. function poll(Time) -- read any data available from the device (only need most recent report) data, n = com.readlast(dev, rd) if n ~= 0 then -- Data was returned, so get the status of all the possible "buttons" we are using -- one value of 32 bits Buttons = com.gethidbuttons(dev, data) -- See if any changes occurred: Diff = logic.Xor(Buttons, PrevButtons) PrevButtons = Buttons if Diff ~= 0 then offset = 0x3340 buttonbit = 1 j = 1 while Rotaries[j] ~= nil do mask = logic.Shl(1, Rotaries[j]-1) if logic.And(Diff,mask) ~= 0 then -- This one changed -- See if changed in less than the "boundary" time thisbutton = buttonbit if (LastTimes[j] ~= nil) and ((Time - LastTimes[j]) < FastTimeLimit) then thisbutton = buttonbit + buttonbit -- Use next higher button for fast end LastTimes[j] = Time -- Toggle a virtual button accordingly ipc.togglebitsUD(offset, thisbutton) end j = j + 1 buttonbit = 4 * buttonbit if logic.And(j,15) == 0 then buttonbit = 1 offset = offset + 4 end end end end end event.timer(Pollrate, "poll") I don't know how to proceed from here.. some input-for-dummies would be well appreciated. Best Matthias

I'm exactly after the same issue. I found that under engine systems (I have the German version, so don't know if that's the term used in the English one) there is 'toggle engine main switch' and 'set engine main switch', for engines 1-2 and this will operate the ECU master Switch at least on the 62. However it seems there should be a keyboard button assigned, and then configured via FSUIPC, because using a hardware switch will cause the variable (VC switch) to flicker up and down.

Sorry, I have been busy work-wise.. yep, I can press skip, but then I cannot access the assignments for buttons and axis.

Same here. De-installed the old version, installed the new version, fresh download- cannot register. Tried both links.

You sometimes feel pretty dumb when you were trying to solve a problem for a longer period of time, and find out you overlooked the obvious. I logged the keypresses, and the sent command stayed the same. I then opened the FSUIPC.ini to see if I could see anything there, and discovered that, although no spoiler axis was assigned, I still had the spoiler in the joystick configuration configured. Pressed reset, e voila, spoilers work as intended. So after all your tips helped to find the error in the end- many thanks John for your support! Best, Matthias

Hi there! I guess this issue is not FSUIPC related directly, but I am trying to understand what's behind. With the earlier version of the Lear everything was fine. Events were mapped through FSUIPC and worked fine. The spoiler on this aircraft is on /off type using a switch, which uses a G1000 PFD softkey event to operate (or direct operation via clickspot of course). Since the latest update of the Lear I can only operate the spoiler exactly one cycle, means, extend once, retract once, and then it's stuck. After that, the switch is still operated, but has no effect (also clicking the switch in the VC does nothing, so it's clearly an issue with the aircraft). But, and here FSUIPC comes into play, if I start FSUIPC and close it by just clicking OK, the spoiler again works for exactly one cycle. This procedure works every time. So my question is, what happens when you just start FSUIPC and close it again right after? How could this affect an event like this spoiler operation? Best Matthias

Thanks for your advice, I will forward your informations.. have a nice weekend!

Hi, the company I work for is specialized on industrial automation. We, together with another well established company, would like to build a flightsim with a cockpit attached to an industrial robot, similar to the DLR DA40/42 system, but limited to entertaining and showcasing purposes on exhibitions. While I have good knowledge on the users side of FSX, I have very little knowlege of programming and what's going on deeply under the hood. Therefore I'd like to establish the contact between you and one of our programming partners in order to exchange some technical details on what data can be extracted out of the FS, and how it's done, before the project may start at all. Could you send me an email adress as PM so I can forward it to our partner? Best regards, Matthias Hanel