Hardware support

fabo.sk

@Mark That's good to hear.

Would you be able to make the screen data available, for 3rd party tools to be abe to display them on the MCDU?

Text and formatting instructions would be necessary, so it could just be a single read-only var, or a a var per line, containing text.

If you'd like, I can forward you the spec of MobiFlight driver input, though of course community can build a translation layer as long as you are able to export the output.

rodmg

I created an account on this forum for the purpose of making it clear that display output for external hardware like the WW MCDU is an essential feature missing in this wonderful product. PLEASE! Make it happen!

rodmg

Please @Mark, make it happen. We really need the external display output for hardware integration. It is a huge missing feature in this wonderful product.

ScotchMist

There is a post here on how to get the display variables with SPAD.Next - it will need a little conversion to other tools however the variables will remain the same:

https://community.justflight.com/post/51540

esaahonen

The MCDU display export feature would add significant value to this aircraft and would likely attract new customers as well, as many users who rely heavily on this hardware simply won't buy the aircraft unless it supports it.

micstatic

@ScotchMist correct me if I'm wrong. I'm a spad user also. We could always code our MCP type devices to display. The problem is with the MCDU/CDU displays. That's the one we are unable to use on all just flight aircraft.

ScotchMist

You're correct in regards the MCDU however there was FCU mention earlier so thought I'd cross reference as that post slips down the list very quickly...

jutacphg

I was really hoping that the F100 would have it considering it has a reasonably modern FMS. This was already requested for the RJ and I can understand that with that plane already released it was not going to be developed, but for the Fokker it would be really nice to get. With a couple of hundred Australian Dollars for a Winwing FMS it’s definitely not just for the cockpit builder and even planes like the CRJ support it even though they are not considered top tear. Anyway, I am not sure what is involved, but I am sure you can sort it out if it would get the focus and priority on the list. In the end if people spend a lot of money for hardware, they will check what planes can support it especially with so many great addons coming to the community

OverSpeed

I have the winwing FCU displays working fine in spad, albeit with a lot more work than most planes require.

Jamie G

So, not sure if this is of use, but the first Mobiflight profile for Winctrl hardware has been released on flightsim.to:

https://flightsim.to/addon/111120/mobiflight-winctrl-fcu-efis-throttle-profile-for-justflight-fokker-70-100

Also, they're asking in the Winctrl dc for feedback re them adding support for the Fokkers:

Maybe jump in there and let them know you want it:

https://discord.com/channels/1444993890355511326/1521266758462210069

IanB2469

I’ve commented on the thread on discord.

This is the problem with things like winctrl. The deeper you get into hardware the more limited (potentially) your range of aircraft becomes!