Issues to be aware of

Changes in 0.19.13

Issues addressed in 19.13

1 - Fixed a critical error in Windows that was causing FPP to crash on many machines when accessing the registration server.

2 - Updated the logic to use the new CFMU validation syntax and addresses (note, old versions of FPP are likely to stop validating correctly on 18 March due to this change at CFMU)

3 - Fixed a range of minor issues in processing CFMU messages

IMPORTANT NOTE - FlightPlanPro uses web services from, and Some people’s antivirus/web security systems are blocking these service calls.  The symptoms are FlightPlanPro being unable to contact the registration server, validation requests timing out or being unable to obtain weather/winds information.  The solution is to whitelist the three URLs above.

  1. Recently some restrictions have been added by CFMU that are not included in the Electronic RAD.  To the extent these involve a level cap or a mandatory routing, FlightPlanPro will not be able to resolve these.

  2. If you get a No Route message, check that the minimum and maximum altitudes are sensible. 

  3. FlightPlanPro should be able to process all Mandatory Route messages.  However, the logic has required extensive testing and reports of any failures to correctly resolve these restrictions will help develop the product

  4. Note, the altitude optimisation uses too much memory and can cause a programme crash on longer routes.

  5. The cloud profile doesn’t always work correctly for routes over 1000 miles.

  6. If you are flying a circular route (same departure/destination), the Notam brief will give an error.

An interesting site Arduino Projects for RC drones

The list of known issues that are being worked on is here

FPP0.19.13 Zero FootPrint

A zip file with the Mac, Windows, Linux programmes and data files ready to be loaded on to a Memory Stick.