BaobobMiller

Has anyone found the offset for the tail hook? the one listed in the documentation is 3BA0 but it seems not to be accurate as it returns to a value of 0 any time the hook is not moving regardless of it being deployed or retracted. Thanks, Bao

GPSOut… over bluetooth Windows 7 64 bit Perhaps I’m just way behind in the common knowledge department, but I recently went looking for “the way” to send my FSX gps data to my Android tablet over Bluetooth so that I could use the full functionality of apps like Garmin pilot, FltPlan.com, and others and was surprised at the number of posts making reference to the fact that it could be done but lacking in the information about how to actually do it. So I am posting this as an example for anyone who is in the same situation I found myself in. I’m not going to wordy by getting into things like how to install a Bluetooth adapter and how to pair your tablet with the PC. If anyone has questions about thinks like that that they cannot find answers to on Google, feel free to shoot me an email or a PM and I’ll do my best to help out. Let’s assume that you already have your tablet paired with the computer and start there… PC Portion: Open “Bluetooth Settings” (Right click on the Bluetooth icon in your system tray and choose “Open Settings” Click on the “COM Ports” tab and if there are no incoming com ports listed, click add. Make sure that “Incoming” is chosen (there are only two choices) and click ok. Make note of the incoming COM port number that has been added to the list. (COM3 for example) and click “OK” Run FSX, start a flight, and open the FSUIPC interface (AutoSave and GPSout tab) and Enable GPSout Choose the COM port you made a note of from the drop down list (but do not check the box for “Send data via WideFS” as this is an either of function and we want the data sent via the COM port) Leave the port speed and interval timing alone for now (you will change it ONLY if you need to later) For testing purposes check all of the boxes at the bottom of the section and click ok (RMA, RMC ,VTG, etc. After you know which ones are needed by the app you want to use on the tablet you will disable the ones that are not needed) Tablet Portion: Enable “Allow Mock Locations” in the “Developer” section if the settings menu Install “Bluetooth GPS” on tablet (there are others that I have tested as well but it works and it’s free… for now at least) Open Bluetooth GPS and tell it to connect to your PC. (there is a drop down list of paired devices at the top. As long as you left your FSX flight running you should see GPS data in the boxes on the main screen of Bluetooth GPS. If the connection fails before going back through all the settings you just made try the alternative connection method in the “Bluetooth GPS” settings. Leave Bluetooth GPS running and open whatever app you want to use (FltPlan.com for example) and Bluetooth GPS will continue to feed the GPS data from your FSX to the tablet tricking most applications into thinking it’s a “real” gps connected via bluetooth. Don’t forget to research which sentences (RMA, RMC, etc. you actually need and disable the rest) Continue fiddling and tweaking in general until you get what you are after. Note: Many people, myself included, have trouble with windows randomly assigning a different COM port to the Bluetooth every time windows is restarted. I have not looked for a way to “reserve” a COM port yet and knowing Microsoft… there may not be one. If anyone does know of a work around please let me know and I’ll edit it into this post. May your Sim flights be plagued with bad weather, damaged landing gear, low oil pressure, and engine failure… and may your real flights endure none of the like. Bao

Thanks Pete It works like a charm. I wasn't sure weather or not it could be written to (SDK says untested and the corresponding "A" variable in fsx can not be written to) so I tried it both ways. funhction Prop_Sync_On () if ipc.readUD(0x2EC8) == 0 then ipc.control(66287, 1) end end Or function Prop_Sync_On () ipc.writeUD(0x2EC8, 1) end Both work great Now as for the UD on the ipc.write Which in the plethera of pdf files will I find the explinations if UD, WD, etc.?

I have been trying for a while to figure a way to read the "A" (and other) variables using a LUA script. I can read and write L variables just fine but I can't find a way to read an "A" variable. (A:PROP SYNC ACTIVE, bool) for example. Is there some reason this can't be done? The point of the excercise is to take toggle only functions and add on/off assignability to them that can be easily included in the LINDA librairies. I have managed to kluge something together but only by adding an xml gauge to the plane for the reading of the "A" variables involved. Since the point is to make this something easy for pilots who are not computer savvy... adding a guage is not a great option. What I have so far is this: LUA function Prop_Sync_On () ipc.writeLvar("L:JMH_Prop_Sync", 1) end function Prop_Sync_Off () ipc.writeLvar("L:JMH_Prop_Sync", 0) end Corresponding XML (L:JMH_Prop_Sync, bool) (A:PROP SYNC ACTIVE, bool) != if{ (>K:TOGGLE_PROPELLER_SYNC) } Any Help? Cheers, Bao

An updated version of the two scripts has been added (right next to the first one in the first post for this thread. just a few bug fixes. but they are important fixes depending on how you are using the scripts there have been no changes in functionality so just replacing the files in you modules folder will do the trick. (No need to reconfigure your hot keys and switches in other words.) Bao

Hello all- Here I have uploaded (attached) a zip file with two scripts in it. The scripts are my attempt at making all the "broken" knobs and switches in the Duke Turbine. assignable to hotkeys and buttons through FSUIPC. Please understand I had never seen lua until two nights ago when I came across another post in this forum dealing with the oil doors... or was it the ignition switches. I would really appreciate it if someone who actually knows lua could take a look at them and give me some feedback or point out mistakes. So far they work fine on my system and anyone who wants them is welcome to download them and use them... improve them... etc. I am in no way claiming any kind of copyright protection or anything. I was just frustrated that I has to use a mouse to fly the plane. Thanks Bao UPDATE I have added version 1.1 to the downloads to address some bugs that I found in a few of the "cycle" routines. I left the 1.0 versions of the files in case I accidentally messed up something else while I was editing. Incidentally Some of you may have noticed an incorrect parameter in the first release as well feel free to take a look, and as always... feel free to make changes, redistribute, etc. just please add your name to any changes you make so we can keep track of "who knows how to do what". DukeLUAs.zip DukeLUAs_V1.1.zip

Hello All - I know this post has not has not been active for a while and I'm not really sure where to start.. I recently purchased the duke turbine/piston Combo and I love/hate the plane. It flies great, Looks outstanding, sounds like sweet music when you spin the props. Now before you start thinking that All I'm here to do is talk about how great the plane is, Let me assure you I have spent the last 2 months looking for a way to get the buttons and switches in that plane to work with key-bindings. Preferably something I could send from HiDMacros because I use so many KBD input sources. I was disgusted to find that there were no real published work arounds or anything. Other than other people complaining about it I could find nothing. That's how I happened upon this thread and a similar one at avsim talking about the fuel doors. So in frustration last night I activated the script you speak of and started hacking away in a scripting language I've never looked at before. The result was two scripts. One to handle the radios and inverter switch (otherwise known as the autopilot power switch for some reason), and the other to handle the fuel valves, ignition switches, and oil doors. I tried to include a full array of use types in my scrawlings, things like toggle, Cycle through settings,activate each state independently, basic on, basic off, for each switch as well as for switch sets. For example you can assign the left switch only or both left and tight switches to work together. At any rate I'm asking for someone who knows Lua better than I to look at the scripts and see if I have made any silly mistakes or anything like that. I have uploaded them to avsim because it's the only thing I could think of to do. I would be happy to copy and paste them into this forum but they are quite long so I don't want to post them without someone giving me the go ahead first, my posts are long enough without adding code to them. When the file gets approved for download (if it has not already... or if it ever does for that matter) on avsom.com the file name is dukeluas.zip I appreciate any look see someone can give. Bao