As discussed above, I tried changing the update_interval to 0.1 seconds in the A/T Lua script and I think the A/T performance was somewhat better, so the Lua script A/T controller in my Dropbox at  

https://www.dropbox.com/s/ia0k97e823hs86r/Autothrottle Lua Script.zip?dl=0

has been updated to use this new value.

No changes were made to the XML 2D popup gauge version of the A/T.

Al

Edited May 22, 20206 yr by ark

Thanks Al - that works alot better for the lua script

For me the best way to use it in the FSM Lear - is to get close to right speed and trim in level flight at cruise and dial in the target speed - it then holds it well with little seeking and auto-throttle self adjustment

It also helps to guard against over speed when the plane gets lighter later in the trip (when you want to go as fast as you can and want to walk away for a few mins)

question - in the lear or any plane with sync - ENG sync on or off ?

Edited May 22, 20206 yr by julian46

24 minutes ago, julian46 said:

Thanks Al - that works alot better for the lua script

For me the best way to use it in the FSM Lear - is to get close to right speed and trim in level flight at cruise and dial in the target speed - it then holds it well with little seeking and auto-throttle self adjustment

It also helps to guard against over speed when the plane gets lighter later in the trip (when you want to go as fast as you can and want to walk away for a few mins)

question - in the lear or any plane with sync - ENG sync on or off ?

Yes, the closer the a/c IAS to the target A/T IAS when you turn the A/T on, the less the simple A/T will hunt.

I don't understand the context of your ENG sync question -- are you asking wrt the A/T?  I don't really know the details of what ENG sync is supposed to do. I think it just reduces that wa-wa sound you get when the two engines 'beat' against each other sound-wise. Hopefully someone more knowledgeable will respond with the correct info.

Al

 

I was just wondering if with ENG sync on it would fight against the lua AutoThrottle - no worries - it seems to work fine with it on or off

After some additional experimentation I have updated both the Lua script and XML 2D popup gauge versions of the Poor Man's Autothrottle.

Throttle movement should now be smoother with the Lua script A/T, and I added some coding protection to both forms of A/T to prevent out of range throttle values.

EDIT: BTW, when using the Lua script A/T you can grab the right side of the green bar with your mouse and resize the bar down to a small display. You can also drag and reposition the green bar to where you want it. I find that convenient.

The A/Ts are still available here:

Lua script A/T:                 https://www.dropbox.com/s/ia0k97e823hs86r/Autothrottle Lua Script.zip?dl=0

2D Popup gauge A/T:     https://www.dropbox.com/s/lcx89iqoums71bj/AutoThrottle XML.zip?dl=0 

Al  

Edited May 24, 20206 yr by ark

Good work Al - latest version is noticeably smoother - testing in the Lear - working fine (the lua script) - thanks again
(going to try the gauge next)

Edited May 24, 20206 yr by julian46

On 5/18/2020 at 3:15 PM, ark said:

 I am trying to help a fella who has the Aerosoft CRJ and apparently the Lua script form of the A/T didn't work -- I was thinking maybe Aerosoft uses some special code for engine control.

I finally figured out how AeroSoft does things wrt the CRJ throttles, so if anyone is interested in either a Lua script or XML gauge version of an AeroSoft CRJ Poor Man's Autothrottle send me a PM with your email address and I'll email you the files. The AeroSoft system for throttle control in the CRJ is quite different than you find with default FSX/P3D aircraft.  I don't have the AeroSoft CRJ myself, but I'm told even the sim standard CTRL+ R speed hold function does not work with that a/c. However, based on some of the documentation I've seen, the AeroSoft CRJ aircraft does seem like an impressive add-on.

Al

I updated the A/Ts in my Dropbox again, this time to eliminate the initial instantaneous large throttle 'jump' you sometimes get when an A/T is first turned on.

Al

Edited May 26, 20206 yr by ark

I took a shot at both Lua script and 2D popup XML gauge autothrottles for the MU2. If anyone is interested in experimenting with these PM me an email address and I'll send you the files to try along with some instructions. How well these A/Ts work may (I'm not sure) depend somewhat on computer speed.

Al

Edited May 28, 20206 yr by ark

9 hours ago, ark said:

I took a shot at both Lua script and 2D popup XML gauge autothrottles for the MU2. If anyone is interested in experimenting with these PM me an email address and I'll send you the files to try along with some instructions. How well these A/Ts work may (I'm not sure) depend somewhat on computer speed.

Al

Hi Al,

PM sent.

Roberto

1 hour ago, Ralvarez232 said:

Hi Al,

PM sent.

Roberto

Files sent. The MU2, or maybe it is just the nature of turboprop engines, seemed more difficult to work with wrt the A/Ts. I'll be interested to hear how they work on your system. As usual with these A/Ts, the bigger the change in IAS you ask for, the longer they take to settle down.

Al

Edited May 28, 20206 yr by ark

On 5/28/2020 at 10:25 AM, ark said:

Files sent. The MU2, or maybe it is just the nature of turboprop engines, seemed more difficult to work with wrt the A/Ts. I'll be interested to hear how they work on your system. As usual with these A/Ts, the bigger the change in IAS you ask for, the longer they take to settle down.

Al

Hi Al,

I tested both Lua script and 2D popup XML gauge autothrottles for the MU2. For the LUA script because of flickering in my system (Windows 10 version 2004 FSX SE) I had to change back the  update interval to 0.5 sec. That is also valid for the LUA script for other planes. Otherwise, both autothrottle utilities works great with the MU2.

Cheers,

Roberto

51 minutes ago, Ralvarez232 said:

because of flickering in my system (Windows 10 version 2004 FSX SE)

Roberto,

Thanks for the feedback.

Is the flickering a new and general problem that started with the Windows upgrade to ver 2004?

Al

Edited May 30, 20206 yr by ark

22 hours ago, ark said:

Roberto,

Thanks for the feedback.

Is the flickering a new and general problem that started with the Windows upgrade to ver 2004?

Al

No Al, I had it before ...

I was doing some AoA test approaches and realized I needed a quick and convenient way to turn off the autothrottle function. With the XML gauge it's easy, just click on the On/Off button. But with the Lua script, it was a little more involved for me since I use a key combination to activate the script, so to turn if off I have to use that key combination, then hit *, and then Enter -- a challenge at my age on short final approach!  🤕

So just in case there actually is someone else out there still living at my age, I thought I point out an easier way to turn off the autothrottle Lua script is to use the FSUIPC LuaKill option. In either the FSUIPC Key or Button assignment dropdown windows, assign a (hopefully single) key or button to LuaKill AutoThrottle. As it says, then using that key or button will immediately kill (exit) the running AutoThrottle script and return the throttles to manual control.

Al

Edited June 2, 20206 yr by ark