MultiWii

For some years I have been working on a better and updated version for a flight controller, based on multiwii and mahowii, here are the github links for those interested in seeing.

Code:
https://github.com/JCFLIGHT/JCFLIGHT

Configurator:
https://github.com/JCFLIGHT/JCLFIGHTGCS

Photos:
https://github.com/JuliooCesarMDM/JCFLIGHT_FOTOS

Interesting.
Is there any info what changes you did to functionality?
Is the 2560 board available for purchase somewhere?

Hello,I have not yet manufactured the PCB with the ATmega2560, I will do it when I get a more stable version possible for all users, I have always worked alone on the algorithm, and I am very overwhelmed, I have already published it in groups here in Brazil, but no one was interested .

JCFLIGHT has an AHRS more robust than the old MultiWii with complementary filter.
A new float-based PID with kCD and FeedForward.
Biquad filter, PT1 and average.
Uses Mahowii's INS (In the future I want to reconstruct the vertical position control).
Support for PPM, SBUS and IBUS.
Support for Quad, Hexa, Model Airplane and Fixed Wing.
Automatic launch for model aircraft and fixed wing.
Contains a Crash system with parachute.
Arm safety button for model airplanes, fixed wing and multi-engines.
Task systems.
Advanced and robust math library.
Buzzer with several different ringtones.
Better RPM compensation of engines based on drop in battery voltage.
Better fail-safe.
And much more...
Contains the GCS (similar to the mission planner) so that the user can do all the configuration without having an IDE to edit directly in the algorithm and compile (Here in Brazil many people do not use multiwii because of that, they were not patient in building the same with the arduino ide).
JCFLIGHT is developed in the VSCode environment with the PlatformIO extension,And GCS is built on the Visual Studio community.

Hamburger wrote: ↑

Thu Mar 11, 2021 11:08 am

Interesting.
Is there any info what changes you did to functionality?
Is the 2560 board available for purchase somewhere?

you can use the boards made in the past of multiwii, such as crius aio pro, flyduino, any based on mega2560.But, you should note that the orientation of the imu was made to accommodate the JCFLIGHT, that is, it must be changed. PPM read pin has been switched to Analog 14 (PK6).
UART1: GPS only (M7, M8 or DJI-Naza GPS).
UART2: SBUS and IBUS.
UART3: Future OSD, MATEK3901L0X and SD Card.
The PWM control pins of the motors / servos were changed, placed in the correct order (2,3,5,6,7 and 8) for JCFLIGHT.
Gimbal Tilt: Pin 46 (PL3 ~ OC5A).
Parachute Servo: Pin 45 (PL4 ~ OC5B).
Buzzer: Pin 9 (PH6 ~ OC2B).
RGB Led: Pins 10 (PB4 ~ OC2A), 11 (PB5 ~ OC1A) and 12 (PB6 ~ OC1B).

Hi JC i have some updates sensor implementation here perhaps you can help add on to it

https://github.com/synersignart/Multiwii-2020-update

Julio Cesar wrote: ↑

Thu Mar 11, 2021 4:13 pm

JCFLIGHT has an AHRS more robust than the old MultiWii with complementary filter.
A new float-based PID with kCD and FeedForward.
Biquad filter, PT1 and average.
Uses Mahowii's INS (In the future I want to reconstruct the vertical position control).
Support for PPM, SBUS and IBUS.
Support for Quad, Hexa, Model Airplane and Fixed Wing.
Automatic launch for model aircraft and fixed wing.
Contains a Crash system with parachute.
Arm safety button for model airplanes, fixed wing and multi-engines.
Task systems.
Advanced and robust math library.
Buzzer with several different ringtones.
Better RPM compensation of engines based on drop in battery voltage.
Better fail-safe.
And much more...
Contains the GCS (similar to the mission planner) so that the user can do all the configuration without having an IDE to edit directly in the algorithm and compile (Here in Brazil many people do not use multiwii because of that, they were not patient in building the same with the arduino ide).
JCFLIGHT is developed in the VSCode environment with the PlatformIO extension,And GCS is built on the Visual Studio community.

(sorry for the late reply - work has kept me busy)

Reason for me asking is Alex had originally experimented with various forms of code structuring and found linear code to execute much faster than structured code with lots of function calls, so I am curious:
with all these additions, what is the loop time on 2560 hardware for a quad with 6050 sensor and the new filters and libraries, please?