rstory1 / cardinal-ems Goto Github PK

If we obtain the route from the GPS and we have a fuel flow input, let's show the fuel remaining once arriving at the waypoint and the leg fuel.

Reach out to me, I want to discuss merging my PFD project (Backlfip) with this EMS + MFD, full EFIS. My latest version uses the same exact NHD-7 BB cape display and an off-the-shelf 10DOF controller as ADHRS + autopilot. Let's talk

Right now the gaugeSettings.ini file is relatively specific to the Rotax 912 engine. Issues could arise when there are multiple caution/warning ranges for particular gauges.

The gaugeSettings.ini file and the code should be changed so that we define each range separately. i.e. range1-rangeN with corresponding data for the specific range.

This will allow us to let the user define gauge ranges easier.

Add engine interface selection to Settings page. We will define what is supported and then save it to the settings.ini file which already includes something for this. The majority of the work is to create a class that handles the interface communication and then separate the interface specific ode into their one class to be included in the main interface class.

Using data from an Aviation NMEA source, build the current route and display it.

The engine monitor shall record and store total aircraft engine time.

We need extra power to let the beaglebone shutdown gracefully when the main power is lost.

Right now I'm working on a supercapacitor solution since it would be cheap and keep lithium ion batteries out of the project.

• Calculate parameter rate of change

• Using a user defined prediction period, calculate where the value will be at the end of that period for the given parameter

• If the predicted value is in a caution or warning range, let the user know

Example for prediction period is 20 seconds. We get the rate of change as parameter change per second. Multiply by the prediction period and then check the value against the ranges.

Need to create definitions for sensors. This includes the name or type of sensor and the equation used to convert the raw value into a readable value.

I think this is related to poor signal/slot design in the RPM gauge class.

Add a page to graphically configure EMS options and enable dev/testing features.

Break up the wind vector into headwind/tailwind and crosswind components.

WindVector already gets the direction and magnitude, so we just need to add in some trig functions if we want to display the components.

Need to process incoming data from Garmin G5

Add control over backlight when using a PWM capable backlight screen. Current iteration is based on NHD 7" Beaglebone cape.