whiggy Posted February 2, 2012 Report Posted February 2, 2012 Hello! I made the experience, that the option "multiple throttle synchronising" is not working for every aircraft. For example: On Airbus X and Eaglesoft Citation X it doesen't work. Is there a solution or a lua script for that?
Pete Dowson Posted February 2, 2012 Report Posted February 2, 2012 I made the experience, that the option "multiple throttle synchronising" is not working for every aircraft. Which option, the hot key one or the calibration one? All the hot key one does is ignore all throttle axis inputs except #1 and copies the value from that to all the others. For example: On Airbus X and Eaglesoft Citation X it doesen't work.Is there a solution or a lua script for that? Without knowing what you are doing and how the aircraft are using the controls or whatever, I couldn't really say. Regards Pete
whiggy Posted February 2, 2012 Author Report Posted February 2, 2012 I mean the the Hotkey on the hotkey page. NOT the function on the callibration page! All aircrafts are working (PMDG NGX, CS757 etc..) But not Airbus X and Citation X. Booth are a simmilar type of fadec throttle. I can press the hotkey, but nothing happens. All I want is a function to "couple" the throttle for normal flight. I't to difficult to move the throttle precise enought.
Pete Dowson Posted February 2, 2012 Report Posted February 2, 2012 I mean the the Hotkey on the hotkey page. NOT the function on the callibration page! All aircrafts are working (PMDG NGX, CS757 etc..) But not Airbus X and Citation X. Booth are a simmilar type of fadec throttle. I need to know exactly how you are assigning and calibrating for these aircraft. All I want is a function to "couple" the throttle for normal flight. I't to difficult to move the throttle precise enought. Well calibrated throttles will normally still have slight differences in postion for the same thrust. But I thought FADEC type thorttles had only certain detente ranges or positions which selected a particular thrust mode, so accuracy of position is far less important, surely? Pete
whiggy Posted February 2, 2012 Author Report Posted February 2, 2012 I need to know exactly how you are assigning and calibrating for these aircraft. Well calibrated throttles will normally still have slight differences in postion for the same thrust. But I thought FADEC type thorttles had only certain detente ranges or positions which selected a particular thrust mode, so accuracy of position is far less important, surely? Pete Citation X: - assigned via FSUIPC "send direct to fsuipc callibration" Airbus X: - assigned via FSUIPC to "use fsx normal axis" and select the lua script, callibrated in fsuipc. That's all. The goal is: move one physically throttle to move booth virtually throttles. BUT with the option to also select seperate throttles. Your "Multiple Throttle Synchronisation" Hotkey is very good and it working well with PMDG NGX etc. As in my other topic (gerneral throttle callibration for ch throttle quadrant) the solution was the LUA script to bring the throttle to work. Your tip (using of axis_throttle) doesent work. Maybe, is there also a lua script for the throttle couple avialable?
Pete Dowson Posted February 2, 2012 Report Posted February 2, 2012 Citation X: - assigned via FSUIPC "send direct to fsuipc callibration" Airbus X: - assigned via FSUIPC to "use fsx normal axis" and select the lua script, callibrated in fsuipc. Both calibrated then? Have you thought of using the calibration sync facility so you still use both throttle levers but they calibrate at several points to give the same values lined up? wuld be more realistic I think. The old hot key facility merely tries to copy what's happeing on throttle 1 to the others and ignores your throttle levers. If you want to stick to the hot key method, please make a brief lof for each aircraft where you engage the sync and move just throttle 1. Enable axis logging. Keep the test short or the log will be unmanageable. Regards Pete
whiggy Posted February 2, 2012 Author Report Posted February 2, 2012 Both calibrated then? Have you thought of using the calibration sync facility so you still use both throttle levers but they calibrate at several points to give the same values lined up? wuld be more realistic I think. The old hot key facility merely tries to copy what's happeing on throttle 1 to the others and ignores your throttle levers. If you want to stick to the hot key method, please make a brief lof for each aircraft where you engage the sync and move just throttle 1. Enable axis logging. Keep the test short or the log will be unmanageable. Regards Pete The problem is not, that the throttles are not synchron. The problem is, I cannot move the levelers with my hand synchron enough. I will check to make the loggin of the axis. I use the "AirbusX_Thr1.lua" and "AirbusX_Thr12.lua" scripts for Airbus X with "send to FS as normal axis" is selected. So, when I try to calibrate the throttles in FSUIPC, it is not possible, the values are not changing when I move the throttles during calibration. I tested with and without reversezone, but it will not work.
Pete Dowson Posted February 2, 2012 Report Posted February 2, 2012 I use the "AirbusX_Thr1.lua" and "AirbusX_Thr12.lua" scripts for Airbus X with "send to FS as normal axis" is selected. So how are the Lua programs working? Sorry, I don't know them. So, when I try to calibrate the throttles in FSUIPC, it is not possible, the values are not changing when I move the throttles during calibration. So they aren't really being driven via a normal FS axis control. Sorry, I don't understand at all at present. Regards Pete
whiggy Posted February 3, 2012 Author Report Posted February 3, 2012 Hello Pete! I'm wondering that you are not knowing this scripts, cause you are posted this: scroll down to post #6 It is from you :)
Pete Dowson Posted February 3, 2012 Report Posted February 3, 2012 Hello Pete! I'm wondering that you are not knowing this scripts, cause you are posted this: http://forum.simflig...-throttle-quad/ scroll down to post #6 It is from you :) Ah, that was nearly 18 months ago! I can't even remember things two months ago, let alone 18. I am getting old and memory seems to be the first thing to go. Or maybe it's the wine and beer. ;-). Since those little Lua programs are sending thorttle values ONLY to internal Local Variables specific to that aircraft, it is not at all surprising that no facilities applicable to axes or calibration can be used. For synchronising them you would need to test the throttle sync flag in the functions. In the throttle1 function, if the flag is set send the value to both throttles. In the throttle2 function, if the flag is set, send to neither. As listed in the list of FSUIPC offsets, the throttle sync falg (set and cleared by the hot key) is offset 0x330C bit 4 (2^4 = 16). So: Throttle1 lua then looks like ipc.writeLvar("L:AS_FADEC_0", 4096 - (9 * ipcPARAM / 4))if logic.And(ipc.readUB(0x330C), 16) ~= 0 then ipc.writeLvar("L:AS_FADEC_1", 4096 - (9 * ipcPARAM / 4))end[/CODE]Throttle2 lua then looks like[CODE]if logic.And(ipc.readUB(0x330C), 16) == 0 then ipc.writeLvar("L:AS_FADEC_1", 4096 - (9 * ipcPARAM / 4))end[/CODE]RegardsPete
whiggy Posted February 3, 2012 Author Report Posted February 3, 2012 Thank you pete! I will try it out.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now