Wishlist for v1.10 - closed

Hamburger · Post by **Hamburger** » Thu Nov 10, 2011 12:04 am

well. v1.9 is out, some minor kinks are being addressed. So it is about time to rally up a list of features to come.
If you add an entry here, please mark whether you intend to implement it yourself or if it is a pure wish.
One item per post would allow to edit the post and update on status more easily.

Hamburger · Post by **Hamburger** » Thu Nov 10, 2011 12:07 am

Summary of wishlist items and implementation status.

integrated in Alex' dev version

LED code
Simple mode like the Pirates or Carefree from Microcopter
turn passthrough mode into a checkboxes item
add checkboxes option to gui and multiwii to unconditionally turn on the buzzer via aux1/aux2 as a model-lost-and-found
preset the debug variables for GUI with more helpful info
have stick combo for magneto calibration
have servo midpoints (default 1500) user configurable via LCD (like subtrim on computer TX) for Flying Wing and TRI
flying wing code is stable, feature complete
Automatic inflight ACC calibration
GUI: visual feedback on state of all of the auxN options
alternate GUI to any (vt-100 aware) terminal program (optionally over BT), works for most tablets, smartphones, etc.
Extended motor range (for use with wii-ESC; resolution 250 steps vs. 125 steps std.)

implementation submitted to *_shared

cleanup internal misleading use of characters to address telemetry pages.
build multiwii with full cpp and compiler warnings and cleanup code (partially done only)
GUI so it reports the full MWC firmware version number, INCLUDING the patch level

ideas MCU

Add the VTAIL configuration as new selection type
RC rate adjustment for stable mode
Sport flying mode with stabilisation
Tricopter servo; consider not moving the servo until after armed and control returned to center
Dual EEprom settings
Something to show the stable trim
Repeat the Gyrocalibration if the copter is moved in the process of calibration
perfected Acro & Level modes
uM-FPU - i2c floating point co-processor
uM-PWM1 - i2c 16 bit, 8 channels PPM decoder/generator
Timecop's i2c to PWM converter
autodetect sensors
Autopilot with GPS waypoint and Return to home support.
Altitude Hold perfected (over 10 cm)
improve Acc calibration without any procedure (plug and play and store in memory)
port to other architectures (stm32) boards
replace low/mid/high for auxN switches with ranges (for those with n-way (multi)switches (n>3)
turn vbat alarm levels into configurable items
split M-command data transfer into two for separate commands; one for live (graph) data (continually sent @50Hz as before), other for tunable parameters (sent only on explicit request)

ideas GUI

pretty GUI graphics
GUI -Able to backup/save/load settings
Gui reset when lost signal with bluetooth
GU remembers serial port
GUI so it reports the full MWC firmware version number, INCLUDING the patch level
GUI->Start includes intial ->Read
GUI baudrate as configurable setting
GUI advanced tab / convert some #defines to user configurable items
Record flight data and replay for analyzing arter flying
sliders for some more values
port to android
visual feedback on all states (same way it is done for existent sensors now)
emulator for TX/RX input via GUI for testing

Hamburger · Post by **Hamburger** » Thu Nov 10, 2011 12:09 am

add checkboxes option to gui and multiwii to unconditionally turn on the buzzer via aux1/aux2 as a model-lost-and-found [will implement]
Update: done.

copterrichie · Post by **copterrichie** » Thu Nov 10, 2011 1:47 am

I suggest moving to 2.0 for the next release.

Bledi · Post by **Bledi** » Thu Nov 10, 2011 9:15 am

Add the VTAIL configuration as new selection type

shikra · Post by **shikra** » Thu Nov 10, 2011 12:09 pm

RC rate adjustment for stable mode
Ability to adjust the RC rate used when in stable mode - as a #define would be fine.
For those flyers who like to fly with stabilisation on. I know many would like to. I do sometimes when in tight spots.

shikra · Post by **shikra** » Thu Nov 10, 2011 12:10 pm

Sport flying mode with stabilisation
Improved code for "sport" flying with stabilisation mode. i.e. stabilisation permanently on
Maybe as stick are moved further from midpoint, stabilisation is reduced. Could even loop/roll with stab on !!

shikra · Post by **shikra** » Thu Nov 10, 2011 12:10 pm

LED code
Many of the guys are using LED's. I'm not one, but may soon.
Maybe some code to generate navigation lighting / effects etc. etc.

shikra · Post by **shikra** » Thu Nov 10, 2011 12:10 pm

Tricopter servo
consider not moving the servo until after armed and control returned to center.
I think that may also help with gyro calibration as my frame moves a lot when the servo tilts with prop spinning.
Plus prop hitting the ground (yes I know alternative exists)

shikra · Post by **shikra** » Thu Nov 10, 2011 12:11 pm

Gui - graphiocs
Pretty graphics like Openpilot for Pitch/roll/compass etc
Doen't really do anything, but looks cool

shikra · Post by **shikra** » Thu Nov 10, 2011 12:11 pm

GUI -settings options
Able to backup/save/load settings

shikra · Post by **shikra** » Thu Nov 10, 2011 12:11 pm

Dual EEprom settings
Selectable options for different PID/RC rate etc
For those who like to swap between gentle flying and crazy flying.
Different PID settings for acro / stable flying.
Maybe linked to aux control
Also useful for testing different settings and not destroying the main ones

shikra · Post by **shikra** » Thu Nov 10, 2011 12:38 pm

But maybe Alex will need a holiday first

timecop · Post by **timecop** » Thu Nov 10, 2011 3:38 pm

shikra wrote:Dual EEprom settings
Selectable options for different PID/RC rate etc
For those who like to swap between gentle flying and crazy flying.
Different PID settings for acro / stable flying.
Maybe linked to aux control
Also useful for testing different settings and not destroying the main ones

+1 on this. at least a couple fixed "profiles" would be super nice.
AND ability to choose them on power-up, maybe by stick position.

tovrin · Post by **tovrin** » Thu Nov 10, 2011 6:25 pm

code for beer servo tilt, i want this thing to pour a perfect beer without spilling it!

actually just kidding, I want to +1 the dual PID settings, and the LED code please!!

jevermeister · Post by **jevermeister** » Thu Nov 10, 2011 7:50 pm

Autamitc inflight ACC calibration.

I will supply you with the code next week.

nils

KeesvR · Post by **KeesvR** » Thu Nov 10, 2011 8:28 pm

Something to show the stable trim, i've got it now in the Debug 3 and 4 thanks to Patrik.

But with Jevermeisters idea it's not necessary , a very good idea.

KeesvR · Post by **KeesvR** » Thu Nov 10, 2011 8:38 pm

A way to store all the settings in the Gui to your hard disk.
Now i need to make a screen-view and set all my settings i wish again and again, while testing other code versions.

jevermeister · Post by **jevermeister** » Thu Nov 10, 2011 8:53 pm

Repeat the Gyrocalibration if the copter is moved in the process of calibration ;-)

KeesvR · Post by **KeesvR** » Thu Nov 10, 2011 8:54 pm

Simple mode like the Pirates or Carefree from Microcopter.

Hamburger · Post by **Hamburger** » Fri Nov 11, 2011 10:03 am

preset the debug variables for GUI with helpful info like i2c-error-count, failsafe-events-count etc. The data is already available, some data gets transferred already (mainly default zeros), so no overhead induced here. [will implement]
update: done.for i2c-error-count and armed-status

Tifani · Post by **Tifani** » Fri Nov 11, 2011 2:07 pm

Back to the basics.
WMP/NK only setup but with perfected Acro & Level modes, easy/fast calibration (maybe BlueTooth integrated).
+1 on graphics

KeesvR · Post by **KeesvR** » Fri Nov 11, 2011 5:27 pm

Gui reset when lost signal with bluetooth.
Now i have to restart the Gui when i loose signal or change the lipo.

captaingeek · Post by **captaingeek** » Fri Nov 11, 2011 7:33 pm

a way to quickly import / export PID settings from the model. That way instead of asking people to post a pic of their pids you can press a button in the GUI that will export the PID settings to a CSV or TXT file.

mr.rc-cam · Post by **mr.rc-cam** » Fri Nov 11, 2011 7:45 pm

Low on the list, but here's some to consider:
(1) When GUI is launched it remembers the last COM port used as the default.
(2) GUI releases the USB port when the GUI has been stopped. This will make debugging sessions more pleasant since the GUI can be present without interfering with sketch uploads.
(3) Add a I2C error counter in the GUI. Useful for confirming good sensor communication.

jevermeister · Post by **jevermeister** » Fri Nov 11, 2011 8:40 pm

Hi,
I just uploaded the inflight ACC Calibration into:

svn/ branches/ jevermeister/ 1.9_inflight_acc_calibration/

I would be happy if someone tests it, I did some flights indoor with it and the results were good.
Just be careful not to crash your bird. Do a ground test first.

I included a HowTo.

Nils

KeesvR · Post by **KeesvR** » Sat Nov 12, 2011 3:48 pm

Hi Nils, I've tested this but i don't know if it worked right.
The description of the stick combination is a little bit confusing for me.
Do you mean for the right stick, first left then down and then right and hold it there and do the left stick up and left.
This is what I've tried, but i don't have a buzzer or led for control, so I'm not sure.

Do I have to do this in stable or acro mode?
I've done this in stable mode, but i think i must do this in acro, other wise i have to do a lot of trim on the TX and acro mode is a way of trim.

jevermeister · Post by **jevermeister** » Sat Nov 12, 2011 6:15 pm

Hi,
my Bad, maybe I am a little too deep in the code.

Okay you need to hold both sticks like described in the same moment.

You should watch what is happening in the gui without a lipo, you can calibrate the acc via gui while the copter is tilted and then follow the procedure.
It works in Acro and Hover Mode.
Nils
btw.: you should really install a buzzer - maybe I should use the LED that is on the arduino... any one has a hint for me how?

timecop · Post by **timecop** » Sun Nov 13, 2011 4:42 am

I'm a bit confused why any further "calibration" of acc is needed besides the one where the craft is leveled and any potential acc offsets from '0' are saved and used for further calculations. What does additional calibration achieve, and why is it necessary?

jevermeister · Post by **jevermeister** » Sun Nov 13, 2011 10:07 am

It is easier and dependable.

On the ground calibratiin does not work.you nearly always need to do some trimming via trial and error.

It is my personal opinion,that this function is needful. In theory,this should be the best way to finetune the levelmode to perfection.

Nils

KeesvR · Post by **KeesvR** » Sun Nov 13, 2011 1:50 pm

Hi Nils, Right now i use pin8 for aux2 (arming motors) i have to chance some wires to make this free for the buzzer.

I've done the test again I see in the Gui Acc-Z drop to zero, so calibration is starting but this is only for 2 seconds.
I think this should be at zero till i switch of the motors.
Then fly, trim, switch of motors and land, again the stick movement.
After this there is nothing changed and i need to trim ACC as much as before.
So for me it's not working, or i do something wrong.

May bee we need a new topic for this.

Kees.

jevermeister · Post by **jevermeister** » Sun Nov 13, 2011 5:52 pm

You are right with the new topic.

dont forget to take back the trimming? ;-)

i need to talki to alex about that, I take 50 values for calibration, while alex takes 400, maybe it is not enough.

+1 on PID Parameter saving in GUI for import/export (already possible on Android Tool)
+1 on different paramter sets:
I fly some FPV and remove my camera infield, so I need another Parameter set infield.

Nils

jevermeister · Post by **jevermeister** » Sun Nov 13, 2011 6:10 pm

About the usefulnes of the autocalibration: I was in the hills today and had no flat surface to do the calibration, so my new function was very handy ;-)

KeesvR · Post by **KeesvR** » Sun Nov 13, 2011 7:15 pm

I've done this in acro mode, then i don't need some trimming on TX.

jevermeister · Post by **jevermeister** » Sun Nov 13, 2011 7:32 pm

Kees:

About the channel layout:

left stick: throttle and yaw, right stick: Pitch and roll?

So to activate the function throttle down and full yaw left and pitch forward and roll right.

I wil review the code and see where the problem is, maybe it is too specific for my setup :-(

sorry for stealing your time with that.

KeesvR · Post by **KeesvR** » Sun Nov 13, 2011 7:46 pm

This exactly opposite to what you described in the text file to my understanding.
This is clear and i give it another try.
Yes Mode-2.

I like to test new things, so no stealing time.

jevermeister · Post by **jevermeister** » Sun Nov 13, 2011 8:26 pm

shoot me!!!

bad, VERY BAD Typo!!!!!

KeesvR · Post by **KeesvR** » Sun Nov 13, 2011 8:51 pm

Never mind.

Did the test again, but a bad result, not working.
What i see in the Gui is, when i switch off the motors and land the pitch and roll signs are at an angle, but when i do the stick movements to end the calibration they go back to level.

Hamburger · Post by **Hamburger** » Tue Nov 15, 2011 10:49 pm

turn passthrough mode into a checkboxes item so user can asign to preferred aux1/aux2 low/mid/high state(s).
Currently in use for Flying Wing. Aiplane should adapt easily. Status: done.

Example: Wing with gyro and acc
checkboxes on for Level - high and PassThru - low, both for aux1
This yields ->
aux1=low : no multiwii sensors interference, only delta mixing
aux1=mid: gyro only acro mode
aux1=high: gyro+acc level mode
Please test and enjoy.
Hamburger

ziss_dm · Post by **ziss_dm** » Thu Nov 17, 2011 3:22 am

Hi,

There are couple of projects, which can be integrated to WMC:
1) BlinkM - i2c RGB smart LED
http://thingm.com/fileadmin/thingm/down ... asheet.pdf
2) uM-FPU - i2c floating point co-processor
http://www.micromegacorp.com/umfpu-v3.html
3) uM-PWM1 - i2c 16 bit, 8 channels PPM decoder/generator
http://www.micromegacorp.com/umpwm1.html
4) Timecop's i2c to PWM converter
http://www.rcgroups.com/forums/showthread.php?t=1399162

regards,
ziss_dm

Hamburger · Post by **Hamburger** » Sat Nov 19, 2011 10:25 am

sidestep current arduino IDE limitation, build multiwii with full cpp and compiler warnings and cleanup code.
Status: partially done - list of warnings available, some causes for warnings fixed or cleared.

mr.rc-cam · Post by **mr.rc-cam** » Wed Nov 23, 2011 5:47 pm

1. Revise the GUI so it reports the full MWC firmware version number, INCLUDING the patch level.
2. Add a GUI feature that reports the chip numbers to the sensors that are installed. It would also show the #define activated features that have been chosen. To save GUI screen room the info could be listed by selecting a menu item. This feature would allow newbies to confirm that they have correctly selected the sensors and options.

Hamburger · Post by **Hamburger** » Sat Nov 26, 2011 1:05 am

have stick combo for magneto calibration. [done]

mr.rc-cam · Post by **mr.rc-cam** » Sun Nov 27, 2011 7:18 am

1. When the GUI's START button is pressed, have the PID and BOX values automatically populate.
2. When launched, have the GUI remember the last COM Port that was used.

Hamburger · Post by **Hamburger** » Sun Nov 27, 2011 10:56 am

mr.rc-cam wrote:1. When the GUI's START button is pressed, have the PID and BOX values automatically populate.
2. When launched, have the GUI remember the last COM Port that was used.

1.: should be fairly easy.
2.: not sure. a) where and how to store this default, b) what on launch the saved default is not the port where MWii is connected.

On a similar note, the idea to have information like complete parameter sets available for save and restore into GUI has sprung up several times.

EOSBandi · Post by **EOSBandi** » Sun Nov 27, 2011 1:31 pm

Hamburger wrote:
mr.rc-cam wrote:1. When the GUI's START button is pressed, have the PID and BOX values automatically populate.
2. When launched, have the GUI remember the last COM Port that was used.

1.: should be fairly easy.
2.: not sure. a) where and how to store this default, b) what on launch the saved default is not the port where MWii is connected.

On a similar note, the idea to have information like complete parameter sets available for save and restore into GUI has sprung up several times.

It could be a good idea to be able to select the baudrate when connecting to a com port. For examle I use bluetooth for one of my copters and xbee for another. one needs 57600 baud, other 115200. currenty i need two compilled versions from the control tool,

Hamburger · Post by **Hamburger** » Mon Dec 05, 2011 1:12 am

update: second post of this thread now has a rundown of wishlist items summary and implementation status for easier reading and avoiding duplicates.

jevermeister · Post by **jevermeister** » Mon Dec 05, 2011 7:50 am

Hi,

inflight ACC calibration is done, I tested it and it is working and I have several positive feedbacks from the community.

About the buzzer, I implemented an Idea using the failsafe mode as buzzer condition:
If the failsafe landed the copter after you loose signal the buzzer starts to beep 1 hz. I alwas implemented this if I turn off the tx while the engines are off, so you can land savely in high grass and switch off the tx to find the copter.

This way you do not need a switch.

See the code in my branch "jevermeister"

Nils

Hamburger · Post by **Hamburger** » Mon Dec 05, 2011 10:10 am

Nils,
interesting about your buzzer implementation.
I use the buzzer (with LED for alarm instead of buzzer) beyond battery&powermeter warnings to signal non-level mode. I fly in level mode mostly with most of my copters so this reminds me of acro mode.
Besides, when copter is landed in high grass on a night flight activating the alarm (blinking LED) somewhat helps locating the copter.
Turning off the TX with Spektrum does not toggle the failsafe for me.

shikra · Post by **shikra** » Mon Dec 05, 2011 1:02 pm

Perhaps it is time to consider a second GUI window / advanced tab?
There is a lot of unused space in the EEPROM -
Some things are clearly hardware related and should always be in #define, but some of the more frequently changed items could be accessed easier wit ha GUI -
Also not everyone finds it easy to compile sketches etc and rely upon the board suppliers a lot.

These are what I'd like to see in there most...

GUI/EEprom value
Tricopter - reverse YAW direction. This is good for guys who provide pre-compiled boards. And me when swapping servos away from home....
ITG filter settings- is a pain to recompile each time to test new values
Cam TILT/PITCH PROP - again, real pain to recompile and test each value until correct!!
Battery tuning

That 3rd/fourth aux channel is looking really necessary now with all the options of mag/baro/stab modes