Hardware support
-
We don't natively support any external FMS hardware at this time; however, software such as SPAD.neXt can be used to control buttons via Lvars.
We do recognise that FMS hardware has become more accessible to larger parts of the community in recent years, and supporting that hardware in our products is something that we have logged on our internal feature request trackers for evaluation.
Mark - Just Flight
-
That's great to hear. I hope this feature makes it onto the implementation roadmap. Affordable CDUs are no longer niche products among the audience interested in this aircraft, but quite common.
@esaahonen Agreed. More and more people will be asking for this -- and just binding the buttons isn't very satisfying compared to utilizing the entire unit.
-
S storemaster referenced this topic
-
I'm going to hold off buying this until full functionality with hardware CDU is added. It's been something that has frustrated me with the RJ Professional and I hardly fly it currently as it's the only 3rd party aircraft I own that doesn't have this functionality. I consider it a must have feature now.
-
We don't natively support any external FMS hardware at this time; however, software such as SPAD.neXt can be used to control buttons via Lvars.
We do recognise that FMS hardware has become more accessible to larger parts of the community in recent years, and supporting that hardware in our products is something that we have logged on our internal feature request trackers for evaluation.
Mark - Just Flight
@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.
-
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
-
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
@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.
-
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...
