Support for MOZA AY210 on MacOS

To do that, I have to get the AY210 myself so I can write the code for it. I've ordered it so when it arrives I'll take a look and see what's what.

That's a good news. Thanks a lot!

I have the AY210 and use it on my Windows and hopefully Linux once it will be supported with your tool. If you want me to send you some Wireshark + USB probe output let me know how to gather the info for you.

Thanks for the offer to help! I just got my AY210 delivered (the base is here, the yoke apparently shows up later today), so I'm all set now. I should be able to add first class Linux and MacOs support soon.

Good news, everyone! (GN, E!...)

AY210 is validated and fully working on macOS and Linux now. The next beta update will let you use this. Just a little while more...

Thanks for the great news. Hope to test it soon.

Beta 13 is out with full support for AY210 on Linux and Mac. Let me know how it goes.

You can download it from https://ffb-bridge.com/beta

I tested the Beta 13 on my CachyOS Linux distro. * The Yoke was detected with no issues. * When I tried to test it using the "Flight Check" screen, there was no FF from the Yoke itself. It did not move, nor rumble. * In the "Dashboard" screen, after I started X-Plane 12, the sim was recognised. I used the default Cessna 172 G1000 plane, and I started it with "Engines" on.

The "elevator" and "aileron" movements were recognised by "ff-bridge". The telemetry data was also depicted by the application, and I think its values are between 0.0 and 1.0, so 0.2 should reflect ~20% force.

Unfortunately, there was no FF, and no rumble from the Yoke itself.

Here are few screenshots:

[Image 01](https://drive.proton.me/urls/G7ZSMQ8YH8#aQbb74NMBqz0)

[Image 02](https://drive.proton.me/urls/DQ1P5AZ7FR#NGkm9hnNlkIo)

Cheers

You set it in Moza cockpit to DirectInput mode and all the rest?

Awesome! FFB is now active on my Mac with AY210.

At first while doing stick test, push/pull was doing aileron control and left/right was doing elevator control. After I swapped pitch / roll in hardware page, everything was good.

I just made few closed traffics on xplane, and this is just amazing. Thanks a lot.

Great, glad it worked with no issues. Odd that it flipped your axis like that. I tested on mine. Maybe just a minor difference , and that’s what the hardware page is for so no big deal.

Let me know if you run into any issues

Nope, I did not think I had to change the Windows settings to affect the Linux one. I'll check this.

After setting the yoke in the "Moza cockpit" it started functioning as expected. From first observation: 1. there is an issue when we toggle between the "setup" window and the "loaded scenery". Every time I do that, there is a small rumble in the yoke. 2. When I move the flap, I do not expect a strong rumble, instead I expect a continues vibrations that indicate flap movement. Instead I get a specific "rumble" length in the yoke, even though the flaps are still in transition.

I'll try to tune the profile for the Cessna. Do you read the data using specific "datarefs" ? If so, where can we find this list ?

Hey, you can find the X-Plane datarefs in the docs here

https://ffb-bridge.com/docs/xplane

MSFS Simvars

https://ffb-bridge.com/docs/msfs

These are a bit out of date, the beta is looking at a couple more things. I will update all the documentation and the website when I release 1.3, so just wait a few days.

There are various improvements to this coming in the next build later today.

The latest build (beta35) should fix a lot of this and provide a much nicer experience with Moza hardware. let me know how it goes.

And now you no longer have to! It should just work seamlessly in Mac and Linux, regardless of what Moza Cockpit settings you may or may not have on the base.

That is great. Thanks for the great work and effort.

I did a quick test with the "FfbBridge-1.3.0-beta.39-x8664.AppImage" version. Unfortunately it stop detecting the AY210 and even X-Plane 12 when it is running. It shows: "device disconnected" in the dashboard. Once I re-installed version: "FfbBridge-1.3.0-beta.17-x8664.AppImage" everything was detected correctly.

Hope for a quick fix. Cheers.

I think it would be beneficial to have an access to all beta version builds, so we could downgrade and test since when an issue occurs.

At the moment this isn't possible.

I have a custom CMS/CRM/backend that I'm using to make it possible to track everything and actually run this product and there's only so much I want to add.

But... if it makes sense, I will think about it - maybe beta testers have a private page where they can get custom builds or the like? Not for this beta cycle, perhaps in the next round. I'm close to releasing 1.3 final already.

However, even now, nothing stops you from installing an older version if you have the exe/appimage/dmg - the app doesn't care, it will just install. So if you want to do that kind of A/B, save the installer.

Regarding your issue on Mac - I'm not able to reproduce it. Could you send in a support bundle? For me on my M4 Mac Mini and my M1 Macbook Pro 14, it just works. X-Plane is detected, the bases work, everything. The support bundle will help me analyze what's going on.

Thanks!

I am on a Linux OS. CachyOS. I will send the support bundle tomorrow. Could you explain how to generate it?

Ah yes, sorry. Been hopping between OSs all day today and got mixed up.

To solve your issue, run the Health Check. There's a new udev rule that needs to be installed. Go to Support -> Health Check and click run. It should tell you what to do, and offer a single-click fix.

https://ffb-bridge.com/docs/doctor tells you more, but note that this page is out of date so ignore the screenshots. Just press Run and see what happens.

If this works, great. The docs haven't been updated yet so I'll add it in there. If it doesn't work, send me a support bundle

https://ffb-bridge.com/docs/support-bundles

The RC1 update now detects the missing udev rules on startup and provides you the option to fix it. That should help sort this out.