Jump to content
The simFlight Network Forums

Build Throttle - Axes have spikes via FSUIPC


Recommended Posts

Hello Pete,

I just finished up building my Throttle. Iam using 10k potentiometers for the Levelers (Engine 1, Eingine 2, Spoiler and Flaps)

The potentiometers are connected to a BU0836X Interface Card from Leo Bodnar.

Via FSUIPC Axis Calibration & Assignment I have assigned the correct axes. Thats working great.

But as you can see in the video I have some spikes in there.

Video

How can I eliminate those? Because when I want to arm the spoilers the spiking disabled the spoilers again...

Is there any solution available within FSUIPC ??

Thanks for your help and best regards,

Mark

Edit: Iam using FS9 and FSUIPC 3.999

Link to comment
Share on other sites

But as you can see in the video I have some spikes in there.

Why is it spiking? Are they cheap pots, or just dirty? I use those same Leo Bodnar boards for analogue controls and they are as smooth as a baby's bottom!

Video

They are all changing together! That looks more like a conflict with a dual assignment to me. Have you disabled controllers in FS? If not, that's your reason.

Pete

Link to comment
Share on other sites

Hi Pete,

I have now doublechecked. The Joystick settings are disabled in FS and no axes are assigned in the FS menue.

Would it help if i post the FSUIPC.ini, that you might take a look and maybe see something?

Is there any way to chek for a dual assignment?

Thanks again for you help.

Mark

Link to comment
Share on other sites

I have now doublechecked. The Joystick settings are disabled in FS and no axes are assigned in the FS menu

Nevertheless, all the axes are "springing" back to a fixed value, by the look of it. And all at the same time. something is clearly doing it. It doesn't look like spiking or jitter at all.

Would it help if i post the FSUIPC.ini, that you might take a look and maybe see something?

I can do, by all means post it. But also, before that, go into FSUIPC's Logging tab, enable both event logging choices on the left hand side., Then reproduce the error (don't spend too long in FS -- the log will get too big!), and show me the FSUIPC log file too.

Is there any way to chek for a dual assignment?

If you temporarily clear one of the assignments you've made in FSUIPC and move the contorlsd, if the cleared one still moves, then there's another assignment, or try moving it with the mouse and see if it leaps back to the "spike" position.

Regards

Pete

Link to comment
Share on other sites

here is the ini

Okay, that's a good start:

You have a generic throttle AND separate throttle 1 and 2 axes calibrated:

Throttle=-16123,16383 Throttle1=0,656,1016,3803 Throttle2=6,457,714,3601

If there are axes attached to all then those will obviously conflict.

Worse, these are your axis assignments in FSUIPC:

[Axes]

0=0X,256,F,65763,0,0,0

1=0Y,256,F,65762,0,0,0

2=1X,256,D,1,0,0,0

3=1Y,256,D,2,0,0,0

4=1Z,256,D,4,0,0,0

5=2Y,256,D,3,36,0,0

6=3X,R1,D,23,0,0,0

7=3Y,R1,D,22,0,0,0

8=3R,R112,D,9,0,0,0

9=3U,R77,D,10,0,0,0

65763 is the FS Axis ailerons set control, and 65762 is the FS Axis elevator set control. They are from your "CH 3-Axis 10-Button+POV USB Yoke". You've assigned those via FS, not direct, so they don't get arbitrated with your dual assignments

2=1X,256,D,1,0,0,0

3=1Y,256,D,2,0,0,0

which are for the same controls, yet direct, on one of your Bodnar boards:

1=BU0836X Interface

1.GUID={BBB523E0-6A76-11DF-8008-444553540000}

Then your throttles:

4=1Z,256,D,4,0,0,0

8=3R,R112,D,9,0,0,0

9=3U,R77,D,10,0,0,0

The generic throttle on 1Z (the CH yoke, again), and throttles 1 and 2 on a Bodnar board. These will also conflict.

But, to the main problem. Looking at the log:


5328136 *** AXIS: Cntrl= 66534 (0x000103e6), Param= -4230 (0xffffef7a) AXIS_FLAPS_SET
5328136 *** AXIS: Cntrl= 66382 (0x0001034e), Param= -2546 (0xfffff60e) AXIS_SPOILER_SET
5328136 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 6060 (0x000017ac) THROTTLE1_SET
5328136 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 7564 (0x00001d8c) THROTTLE2_SET
5328136 *** AXIS: Cntrl= 66534 (0x000103e6), Param= -16383 (0xffffc001) AXIS_FLAPS_SET
5328136 *** AXIS: Cntrl= 66382 (0x0001034e), Param= -16384 (0xffffc000) AXIS_SPOILER_SET
5328136 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET
5328136 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET[/CODE]

This sequence repeats throughout. Whatever one of your controllers sets, another is setting the minimum (-16383 or -16384) for the AXIS controls and 0 for both throttles.

Since there are NO such duplicate axis assignments in FSUIPC, I think you must be mistaken about the FS settings. Are you sure joystick controls are DISABLED in FS -- not simply not assigned -- FS makes automatic assignments, and in any case you have to select every one of your attached controls in turn to see what is assigned. You cannot see them in one glance, you select one controller at a time. Have you done that?

Pete

Link to comment
Share on other sites

Hi Pete,

I have now checked the above things.

I really hab the throttles and throttle 1 and 2 assigned. I deleted them, but it doesn't show any better effect.

I have uploaded the new log file as well as the .ini file.

Joy.jpg

All the 6 cards as well as the CH Yoke and my pedals were checked. No assignment

joy2.jpg

Link to comment
Share on other sites

Hi Pete,

one more question. Is there an option available to ignore a complete joystick in FSUIPC?

When I want to assign some key presses via FSUIPC some other joystick keepresses are takin g the focus. Those cards (all BU0836X) are configured via Prosim and therefore no config via FSUIPC is required.

Thanks again,

Mark

Link to comment
Share on other sites

one more question. Is there an option available to ignore a complete joystick in FSUIPC?

When I want to assign some key presses via FSUIPC some other joystick keepresses are takin g the focus.

Key presses? FSUIPC won't know whether key presses are coming from the keyboard or from a joystick driver. There's no way to distinguish them.

If you mean buttons and switches, there is an "IgnoreThese" option -- see the Advanced Users guide, search for "ignorethese". Of course ideally you shouldn't have any buttons which are continuously signalling -- that's normally the sign of a fault.

Pete

Link to comment
Share on other sites

  • 1 month later...

it took a while, but I got a replacement card and installed the card into my cockpit. And all is working very fine now.

No spikes and no multiple buttonpresses anymore.

Good. It's unusual to have faults in those cards, but I'm pleased the fix was relatively easy in the end!

Pete

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.