kolaf

Sorrry, my bad. Was indeed writing UD instead of UW.

Hi, I'm wiring up a rotation switch to act as a magneto switch on my panel. It sends the values 0 through 4 to offset 0x0892, and most of the sequence works. The trouble is, when I moved from stage four to stage three for piston engines, or stage 2 to stage 3 for turbine engines, the mixture resets itself. This means that it is very difficult to use this to fire the engines correctly. I have tried to set the mixture to full through the appropriate offset right after I change the magneto, but this only causes the magneto change to reset itself instead. Is there some kind of coupling here that I am not aware of? Is it possible to prevent it from changing the mixture? Thanks for your great support.

The reason is that that the panel I am designing does not get recognised as an input device. It simply communicates with FSUIPC and LUA through a serial interface. It does therefore not present any axis to which I can map the flaps control. On another note, from the options dialogue it appears that FSUIPC knows nothing about the flaps of the Mustang. I just have to learn to live with it, I guess ;)

I just tried it, only offset reports 1820. This gives nine detentes, which is inconsistent with the five positions I observe when running the flaps manually. Any suggestions?

By this I guess that reading the ranges for the flaps from the appropriate offset 3BFAwill not be possible either? I haven't tried, so I guess it is worth a shot. Is there any other way of achieving flaps control from a proportional lever if this is unsuccessful?

Thank you for your awesome help. I now got flaps, spoilers, and gear working for the 737 NGX :smile:. The flaps are accessed through axis flap set. The weird thing, though, is that this does not control the flaps on the A2A p-51 Mustang. I think the gear works, but the flaps do definitely not work. You said that this was the most generic way of controlling things? It is not a big deal, but still...

Thanks, if it is as easy as that, then I will manage :-) Just one more quick question. There are several controls for the flaps and the spoilers. I'm curious about the function of the control "flaps set". Does this take the same values as the flaps offset I talked about above? Could I then just input a number between zero and 16,000 and have the flaps change accordingly (similar for spoilers)? Or do I have to calculate the number of detentes myself based on input from the other offsets...

Thanks for the clarification. Looking at offset 3110 I'm not entirely sure of how to use it. Could you be so kind as to give me a simple example for how I would control the flaps given a number available in a variable? Do I have to assign some kind of dummy axis in fsuipc? I would prefer to keep the code as generic as possible, so I would like to avoid addon specific modules. Doing this through axis as you suggest seems like a better way of doing it for me, assuming I can figure out how :)

Hi guys, I am building my own panel based on arduino, and I am interfacing it with FSX/P3D through the latest version of FSUIPC. Most of the controls work, but there are a few key controls that do not work for all aircraft, like PMDG 737NGX, A2A P-51, Vans RV-7. The offsets I am talking about are 0x0bdc for flaps, 0x0bd0 for spoilers, and 0x0be8 for gear. All of these work for default aircraft, and also some add-on aircraft such as RealAir Scout, C90B, Carenado 208, and so on, but not for the aircraft listed above. Is this because they use some other means of control? Is there perhaps some other offsets I should use instead? Do I have to go to work more manually and emulate the actual key presses in some way? A simple example from my lua script is included below. Any help is appreciated. if string.match(str, "flaps:(%d+)") then state = tonumber(string.match(str, "flaps:(%d+)")) ipc.writeUD(0x0bdc, state) end if string.match(str, "spoilers:(%d+)") then state = tonumber(string.match(str, "spoilers:(%d+)")) ipc.writeUD(0x0bd0, state) end table.insert(commands, {0x0be8, "gear", ipc.writeUD, ipc.readUD, 0, 16383}) for i,v in ipairs(commands) do if string.match (name,v[2]) then ipc.log(v[1]) if string.match (action, "on") then v[3](v[1],v[5]) states [v[1]] =v[5] elseif string.match (action, "off") then v[3](v[1],v[6]) states [v[1]] =v[6] elseif string.match (action, "toggle") then current_value =v[4](v[1]) if current_value ~=v[5] then v[3](v[1],v[5]) elseif current_value ~=v[6] then v[3](v[1],v[6]) end else v[3](v[1], tonumber (action)) states [v[1]] = tonumber (action) end break end end [/CODE]