timecop wrote:There are so many issues in mwc that need to be addressed before "waypoints" or any other useless shit is even started to talk about. Copypasting more and more tarducopter code without fixing the foundation only leads to garbage. So you should be lucky you can't fly "waypoints" in baseflight.
There will be always issues ...
Anyhow ... who did spoke about copy re-tard-U-copter code ?
I know that there are tons of copy-paste guys around ... but I'm an old, old school guy ...
Anyhow ... back to waypoint navigation ... MultiWii has already inside navigation, else RTH would not be possible.
MultiWii has 2 functions :
GPS_set_next_wp ... this allow to set the desired waypoint target (code use home location, but any location can be used here)
Then ... we have this simple line, that check if the copter is arrived:
if ((wp_distance <= GPS_wp_radius) || check_missed_wp())
Actually .. " check_missed_wp" sucks ... it make no sense to me, in fact I did disable it , else it will not work my hacked MW 2.2 with waypoint navigation.
Inside the code that make an action once the target WP is reached ... just set a next WP for the "new navigation mode" ... and ... WP navigation is done ... just few lines of code, no copy any tard-retardu stuffs ... no "gay" i2c GPS needed, not any special GPS needed ...
Hardcoded WP navigation is very simple .... make it configurable that is more "compicated" ... but you have already a CLI ... so add there a couple new commands and the game is completed ... at very very low coding cost.
The only reason why people pick re-tard-U-copter is because of navigation ... personally I think mutliwii is a better code
I hope I did clarify my point
ps: I'm having some afro32 boards and some STM32 board ready to be connected to 10DOF board ... so ... I was planing to use them on more complex copter (like double wing-quad copter) ... and I'm exploring what I can get off-shelf ... so far for quick experimenting ... I'm still on old ATmega boards