Welcome to Cockpitbuilders.com. Please login or sign up.

October 15, 2025, 07:19:23 AM

Login with username, password and session length

PROUDLY ENDORSING


Fly Elise-ng
535 Guests, 0 Users
Members
Stats
  • Total Posts: 59,756
  • Total Topics: 7,887
  • Online today: 580
  • Online ever: 1,343
  • (October 08, 2025, 07:40:38 AM)
Users Online
Users: 0
Guests: 535
Total: 535

COUNTDOWN TO WF2024


WORLDFLIGHT TEAM USA

Will Depart in...

Recent

Welcome

Need help Fs2Phidget : AT moving forward smooth / backwards zig zagging

Started by GSalden, January 20, 2014, 10:54:32 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

GSalden

My throttle quadrant : Simulatory with a Leo Bodnar joystick card and motorized by Phidget hardware .

Software : FSX , Fsuipc, Fs2Phidget, Ifly Cockpit Builders Edition.

The throttles are assigned and calibrated in Fsuipc only and not through the FSX controller menu.
Fs2Phidget v 4.2.9
Assigning the throttles in Fs2Phidget was straight forward.
Min / max positions are good.

When using the AT and increasing the speed the throttles move forward. A bit jerky but together.
When decreasing the speed a bit always one of the throttles goes first and the other one follows with a zig zagging movement.

When decreasing the speed a lot one goes immediately to idle and the other is first zig zagging rapidly and after a few seconds going to idle.

In the Fs2Phidget Manage Fs Variables menu :
- FsVariable File : FsVariables4364.ini
- Fs Variable Type : Range of Values
- Source : Fsuipc

I was wondering if it was possible to include some kind of dead zone / sensitivity like in the Fs menu  and  a acceleration control like in the Phidget Control Panel.


All advice and help  to achieve more smooth moving throttles and no zig zagging  is very much appriciated.

GSalden

In the mean time I figured out that there are no issues with default 737.
So it has something to do with the Ifly 737.

That aircraft uses lots of Fsuipc offsets , like the throttles.
And for anything that isn't directly compatible with it there is Ifly to Fsuipc.

Still all help is very welcome.

GSalden

The moment I disconnect the joystick card ( Leo Bodnar ) which is connected to the throttles potmeters, the Fs value in Fs2Phidgets drops to 0.
So Fs2Phidgets needs the the  values from the hardware throttles or needs to see a joystick card where the hardware throttles are assigned to.

Then I did a test :

I unplugged the power to the phidgets hardware and then by hand moved the throttles.
Immediately the throttles onscreen started jumping up and down.

The same test I did with the default 737.
When moving the throttles by hand nothing happened to the throttles on the screen.

That leads me to the conclusion that the Ifly AT has been programmed differently than the default aircraft..
When the hardware throttles are not moving ( doesnt matter at what position they are ) then no issue.
When they are being moved the jumping issue occurs.

So Fs2Phidgets needs the joystick card to work and the Ifly AT reacts on moving the hardware throttles, where the FSX default AT does not care if the hardware throttles are being moved.

So what I would need when flying the Ifly with the AT on , is blocking the changing hardware throttles values to the Ifly AT , but not to Fs2Phidgets.

Anyone has an idea ?

KyleH

Do you have 'Inhibit manual Throttle when using A/T' in the iFly setup  checked?
Kyle

Chief Pilot
Worldflight Team USA
http://www.worldflightusa.com

GSalden

Yes, Inhibit  manual throttle when uysing AT has been enabled.

It doesn't even matter if it is enabled or disabled ....
When I push my hardware throttles a little they override the AT and I can see the Ifly onscreen throttles move , better said zigzagging.

I even reinstalled the Ifly from scratch, let FSUIPC make a new ini file but no difference.

I disabled the throttles in FSUIPC and enabled them in FSX , as I read that Inhibit ....   only works in the FSX controller menu and not when calibrated in FSUIPC.

Also the Ifly onscreen throttles move too fast : idle to 70% in 1,5 seconds...
In reality when using the AT it takes almost 4 seconds.
If only I could let them move slower...
 

Like the Website ?
Support Cockpitbuilders.com and Click Below to Donate