SolvedFeedback & bugs

FFB-Bridge Multiple (5) Safety Stops on Specific AB9/MH16 Flightstick Binding

10 replies 1477 views started 15d ago

This topic has an accepted solution. Jump to solution.

#1

Hi all - 7950x3D/4080 using AB9 with Moza MH16 flight stick and AY210 along with FFB-Bridge. I had 5 immediate Safety Stops on my AB9 as soon as I hit Button #19 which is on the MH16 left side 4 way thumb switch with a button press. I have been flying Taog's Dauphin and Button #19 is bound to FTR - Flight Trim Release control binding. As soon as the button is pressed immediate halt.

The AB9 is then unrecoverable (as well as Spad) until I turn it on and off again, which works fine but the multiple safety stops have given me pause to continue using this until I know what's happening. Thanks for any help!

Report
#2

What an odd bug. Did it literally just go into safety stop as soon as you hit that button? No sudden forces or anything? And if you use another button for FTR? Does that work?

Could you send me a support bundle from the app after this happens - here's how to do that.

YouTube video

This preview is served by FFB-Bridge. Loading the player connects your browser to YouTube/Google.

Open on YouTube
Report
#3
In reply to FFB-Bridge's post

Will send you the info. Yep it is a really weird bug and very jolting when it happens because it is so immediate. Will try to do that today.

Also congrats on the Moza partnership - Moza is smarter than I thought! :)

Helpful 1Report
#4

Hi! Brand new user here. I get the exact same error as JPVann when pressing the FTR button. With a Cowan 206 helicopter. Only way to get going again is to cycle power to the AB6.

Report
#5

Hey can you send over a Support Bundle after this happens? I have tried reproducing on my own AB6 but not seeing this.

Report
#6
In reply to Swepri's post

I can't identify the root cause or reproduce it on my machine, so I've built a special logging build that I'd like you to install. Copy and paste this into your browser:

https://ffb-bridge.com/dl/diag/bsUW9_PlMKDHqzil1MuPT_0g5jEEwkkc_1C2qFo_cDo

  1. Note the base and grip models and the firmware version shown in MOZA Cockpit. Include a screenshot of its native trim/button settings if possible. Note whether Cockpit/Device Service and SPAD.next were running during the failure.

  2. Close FFB-Bridge, install the diagnostic build, reopen it, and check the version in About. Keep the original profile, force strength, controls and other software settings for the first test.

  3. Load the helicopter that showed the problem. With the aircraft parked and a hand on the stick, arm Bridge, hold your usual FTR button for about one second, then release it once.

  4. If Safety Stop appears, wait two seconds, then export the ZIP from Support → Diagnostics before restarting Bridge or power-cycling the base. Do not repeatedly press Arm. If it works, export the bundle anyway.

  5. Send the ZIP with the firmware version and what was felt: did resistance disappear while held, return on release, and did Safety Stop appear?

This bundle will capture more data to help me narrow down the root cause.

Report
#7Accepted solution

Thanks for sending in the support bundle. The issue is now resolved. This is caused by a conflict between Moza Cockpit and FFB-Bridge.

You need to disable Hardware Trim. You currently have it enabled as follows -

Now, to make it work, you need to disable it so it looks like this

Once turned off, it should work. This is also a bug in FFB-Bridge, it missed this setting and thus it was going nuts. I will correct it in the upcoming 1.5.1 update so this wont' affect anyone in the future.

Thanks for helping track this down, it was tricky!

Helpful 1Report
#8
In reply to FFB-Bridge's post

Disabling HW trim in Cockpit did help with the triggering of the Safety Stop.

But now I can not get the FTR button to do anything. The On/Off button works as expected if mapped, but if I map to the push-and-release there is no hold, just relatively free movement.

I will do som more testing tomorrow, perhaps.

Report
#9
In reply to Swepri's post

Question - where are you binding your FTR button? Are you doing this in the sim, or in Moza Cockpit, or in FFB-Bridge.

You need to bind the button in FFB-Bridge, not in Moza or in the sim.

Tell me some more about how exactly you're setting all this up, and I'll let you know if something needs to be changed.

Report
#10
In reply to FFB-Bridge's post

The FTR button is only bound in ffb-bridge. It used to be bound in Moza Cockpit, but the hardware trim is disabled there, as recommended earlier in this thread.

Report
#11
In reply to Swepri's post

Yes, it should be unbound in Moza even though the latest version of FFB-Bridge beta removes that limitation - it sorts this automatically. Still, that's why it's in beta, to work through issues.

I can't replicate your issue, could you send over another support bundle when you have a moment? From the 1.5.1 beta.

Report