jfjoubert

Thanks for the info Tom... no wonder my neck hurts after a rejected takeoff.

I just tried this... got mixed results. But there is definitely brake input from RTO with AT activated. I think you should be well over 80 knots before pulling the throttles back. Strange thing is that the parking brake engages whenever you do an RTO. Is this normal Jan?

Thanks for the info...

Thanks for the info. I managed to drive my steppers via Arduino and ArdsimX and I'm using the virtual throttle handle angle and comparing it to the value of the actual throttle axis value. My Arduino has a potentiometer which is mapped as the throttle axis so just checking whether there's a difference and then running the stepper to catch up works like a charm. Now I just need to figure out a homemade slip clutch...

May I ask what "system" you're using? Maybe there is a way to emulate "holding down" a button.

Hi Rob, Could you please explain to me how you use this dataref to determine when to apply power to the autothrottle motors? Thanks Jean

Hi, I was just wondering why there's no STAB OUT OF TRIM indicator on the left forward panel of the IXEG 737. Also, shouldn't there be a "QTY TEST" placard above the fuel quantity test button? (like the ENG OIL QTY TEST on the steam gauge instruments) Out of curiosity... how would one test the engine oil qty on the non-steam gauge instruments? Jean

Hi, not by default but you can create your own command in FlyWithLUA and then map your hardware button to this via the menus in Xplane. You have to use the "ixeg/733/fuel/fuel_qty_test_act" dataref and map it to a custom command. Remember to use the second parameter of the create_command function which is the code for holding the button down. The test only happens after holding the button for about 2 seconds. This is one of those "weird" datarefs... the initial value is 0. As you hold down the test button in the VC the value wil go up until it reaches 1. After this the value will stay on 1, but as long as you hold the button down for approx. 2 seconds the test will still work. So in your FlyWithLua code you can simply set the dataref value to 0 or 1 or 2... it doesn't matter. As long as you hold down your physical "mapped" button for approx. 2 seconds it will work. Shout if you need help... Jean

Hi Rob, Thanks for the info... could you please provide me with the datarefs for the ghost throttles? Thanks Jean

Haha, I thought it was just my plane that had a double cockpit door...

Hi, would it be possible to add some datarefs for A/T logic in the not too distant future? I've got some stepper motors and microcontrollers to build my own motorised throttle quadrant. All I need is to know when the A/T servos are engaged or not so that I can enable/disable my stepper motors. Currently I'm just checking the "ixeg/733/MCP/mcp_at_arm_ann" dataref to determine whether my steppers should be enabled or not, but this is a bit crude. I think the servo disengage (whilst A/T is on) should really only happen when A/T mode goes into ARM, but there might be other modes I'm not aware of. Jan, your thoughts on this? So maybe an "at_servos_engaged" dataref? Thanks. Jean

No probs... glad I could assist. Have a nice weekend as well.

Hi, You didn't specify which version of X-Plane you're running... I'm guessing 11. This is a known issue with this plane in XP11 as it is not officially (currently) supported in XP11. You can try the quick fix in planemaker... Note that you only need to tick the first checkbox...

Hi Andrey, As far as I know there is some documentation under the FlyWithLUA folder under Resources\plugins... not 100% sure as I'm not at my home pc right now. You can also get it from Github... https://github.com/X-Friese/FlyWithLua In short here are the paramaters required for create_command() function... create_command(string unique_command_name, string command_description, string lua_code_to_execute_once_when_command_starts, string lua_code_to_execute_when_button_key_is_held_down, string lua_code_to_execute_when_command_ends) So paramaters 3, 4 and 5 will execute LUA code when button pressed initially (3), then when button is held down(4), and lastly when button is released(5). Note that all paramaters must be text surrounded by quotes... I think this is the reason why the function call is inside double brackets... it must be a string but it's still a LUA function which needs to be called so in theory it's not just a plain string. This is just a way that LUA handles strings. PS: I'm no LUA expert by any stretch of the imagination. Hope this helps.

Here's a very simple LUA script which will create a custom command which can be mapped to a single hardware switch/button to toggle the APU switch from off to start and back to off.If you have a 3 position switch then you'll have to modify the script to have 3 commands instead of one... one command for each APU switch position. Have a look at the attached script... it's really easy once you know how to use it. I did add some comments in the script to explain what I'm doing. Ask if you need help. ixeg_apu.lua

Start by removing all 3rd-party addons in XP11 like JARDesign etc... except of course Gizmo which is required for the IXEG. This looks most likely to be a plugin conflict.

Have a look here...

Best is probably to disengage both AP and AT... I think this is how most RL pilots fly the 737. Also keep in mind that the VNAV is not 100% accurate... yet.

Mine had too many bugs... and whenever I wanted to beta test her she kept on crashing.

I think it is because the "ixeg/733/radios/radios_com1_right_mhz" is a manipulator dataref, so you have to take the current value of the dataref and either add or subtract 1 for the dial to turn. There isn't really any meaningful value contained in this dataref... it goes from 0 to 19 but it's just an arbitrary value. You might be able to use the following as well... XPDref("ixeg/733/radios/radios_com1_right_mhz", GetData(190) + 1) The GetData(190) will retrieve the current value of the #190 dataref from your config file. Theoretically it should do the same as the SimInput(190) solution... (I'm once again just guessing)

You're welcome... Yes, I know that... but you still need to map it as a custom command to be able to bind it to a joystick button etc. Can be a bit confusing at times... Thanks for your input.

I just had a quick look at the ArdSim interface... Have you tried using the "datarefs for custom input configuration" as explained on this page http://svglobe.com/ardsim/ardsim_input.html ? So I would code something like this in the config file... C1 ixeg/733/radios/radios_com1_left_khz 1+ C2 ixeg/733/radios/radios_com1_left_mhz 1+ C3 ixeg/733/radios/radios_com1_right_khz 1+ C4 ixeg/733/radios/radios_com1_right_mhz 1+ C5 ixeg/733/radios/radios_com1_left_khz 1- C6 ixeg/733/radios/radios_com1_left_mhz 1- C7 ixeg/733/radios/radios_com1_right_khz 1- C8 ixeg/733/radios/radios_com1_right_mhz 1- In your Arduino code you'll call SimInput(3) for example to increment com1 right khz or SimInput(8) to decrease com1 right mhz whenever your encoder turns. As to the values being sent by FlyWithLua... as far as I know the commands in FlyWithLua is simply mapped to the custom dataref manipulators which will actually turn the virtual dials in the cockpit. The IXEG code behind the scenes will then set the actual radio frequencies... it is similar to you using the mouse to manipulate the dials. But this is just my guess... I'm no expert on this whatsoever. Let me know if this works...

Unfortunately I haven't used ArdSim yet... are your rotary encoders etc. visible as buttons inside the x-plane Joystick & Equipment menu?

Maybe I should have asked before... what are you using to interface your Arduino with the sim? Do you run FlyWithLua?

Hi Syl20, I just had a quick look and here are my findings: (I don't have any Arduino hardware so I'm simply using FlyWithLua with my Saitek Yoke to do the tests.) First of all you have to keep in mind that the "ixeg/733/radios/radios_com1_left_khz" etc. are not standard datarefs, they are custom manipulator datarefs. So you cannot "write" a value to them. You "code" them as a command which can then be mapped via the Joystick & Equipment - Buttons: Adv menu and then using the "custom cmnds from plugins" option. I have just done a test in FlyWithLua and I'm able to increase and decrease the mhz and khz of both com radios, active and inactive without having to know which one is currently active. For Com1 left mhz : Use "ixeg/733/radios/radios_com1_left_mhz" as a command where you increase the value by 1 every time the command is executed. For Com1 left khz : Use "ixeg/733/radios/radios_com1_left_khz" as a command where you increase the value by 1 every time the command is executed. For Com1 right mhz : Use "ixeg/733/radios/radios_com1_right_mhz" as a command where you increase the value by 1 every time the command is executed. For Com1 right khz : Use "ixeg/733/radios/radios_com1_right_khz" as a command where you increase the value by 1 every time the command is executed. Then you do the same for all 4 above but decrease the value by 1 every time. Then do the same as above for Com2 if needed. Let me know if you would like to see some code or if you have any other questions. Regards, Jean