MultiWii

waiting for it...

All is OK (on PAL). Johnny is testing the NTSC and he release this version

YES I use PAL settings *lol

Just found this project and looks very interesting! I want to test it!
Guys, can you tell me where I can get PCB board for Rushduino?
I can quite well solder and ISP program Atmel but have limited money so I prefer either an empty board or just the basic kit. Is it available? Where?
I'm even able to make one or double side PCB (but not connecting vias .)
Thanks for any advice!
Roman

JohnyGab sells them built and tested for just $60 (+shipping) on his site.

You can make your own board design around atmega328p + max7456. I do not think you can make it much cheaper.

What's up? The Rushduino OSD have disappeared from qcrc.ca and there's no software update from JohnyGab yet. I hope everything is OK.

itain wrote:What's up? The Rushduino OSD have disappeared from qcrc.ca and there's no software update from JohnyGab yet. I hope everything is OK.

also waiting for the new 2.1 compatible version

I just brought two mobiDrone nano OSD's to repalce my Rushduino's it seems that the product is more active.
It's not much fun when you cant use your OSD while trying to stay current or even testing the lastest dev code...

Hi Gab and Bledi, please hurry up we are getting obsolete!

I can't release for him but I had send a e-mail.

Hi !

Sorry for that delay, again
I had a bad adventure last week end.

Was trying to assemble a copter to demonstrate the OSD in field....and while disabling break on an old ESC, I made the mistake of not removing the prop. The motor just go full power and hit 4 finger on my right hand, 2 finger have been hurt seriously. one have a big cut, but is ok, but the other, the prop did go about 15mm into the finger, then hit the bone ( radiography show some broken bone on the tip of my finger.) Dont have to explain how much blood there was out there....

anyways, i'm writing with one hand,

its now less than 10 days after the release of 2.1 and the osd is now working.

here is the package : http://code.google.com/p/rushduino-osd/ ... akechanges

thanks to bledi to helping me finding bugs and solving them!

there is still some little things to modify, like the artificial horizon that is differently displayed in PAL vs NTSC because of the number of line in one frame, and the menu, i have to adapt it so it match the new parameters list.

Hope you enjoy it, sorry again.

If you find bug and/or solution to them, please feel free to post them here.

Why not make it open source? that way, anyone with an interest can contribute.

I think is an excellent idea. Faster and better

here is a new update, some bug corrected, still

http://code.google.com/p/rushduino-osd/ ... akechanges

for the open source, correct me if i'm wrong, but the code is actually public....so open...no?

if there is a better way to do it, i'll be happy to listen to what you have to say

yes but you ahev to open the SVN on google for other developpers. For the moment we just can download but not upload

Bledi wrote:yes but you ahev to open the SVN on google for other developpers. For the moment we just can download but not upload

Just tell me how can I do this, it will be a pleasure

it's something link "add members" but I don't know how to admin a google repository.

Is someone can help us ?

He would first have to use some source control system.

On Goggle, he will have to select one of two source management, SVN or GIT. If you wants to be compatible with the MWC, select SVN. It is detailed on the following page. Note, the Password is not the Google Password but a generated Password from the Admin Tab.

http://code.google.com/p/support/wiki/GettingStarted

Once create, the he will have to load the source code into the trunk and grant Commit rights to selected Contributors.

JohnyGab, Thanks for the update and for releasing V9 Beta version.
Have my best wishes for getting well and flying soon!

Johnny if you want that developers can help you, you will also have to opensource the hardware meaning provide the schematic.. Get well soon.

Hi Gab,
I just now saw this last post´s since my last one. I just hope that your hand gets better quick, we can not forget that this things sometimes can bite us!

Going to give the new code a try today!

Cheers,
H

Many THANKS for the ne OSD Version !!!

works fine ... Video Source GoPro Hero HD (R5 PAL Resolution) only upload the new MCM Table .. followed by the Rushduino Code ... plug all togther an Lights On VERY NICE WORK !! There is the DONATION Button ??


fly video follows on weekend
regards thorsten

yes for donation you can send I at my adress
Can you test the arrow of direction to home, I am not sure it's ok and I can't test this week

Bledi wrote:yes for donation you can send I at my adress
Can you test the arrow of direction to home, I am not sure it's ok and I can't test this week

1.) youre Adress -> PN to me

2.) Arrow testing -> may be today ... or this weekend .. no problem

Hi everyone!
Johny I'm sorry for what happened to your hand.

I tested the latest version, unfortunately, the problem of video noise remains unchanged (https://vimeo.com/42752848)
Until now I had to fly with my old osb remzibi, no video noise. Rushduino osd have a hardware problem? on equal condition and hardware remzibi= perfect, rushduino osd = noise
Also I no longer go into the menu of the pid, the procedure has been changed?( so it does not interfere with the trim of multiwii).

Hi @ALL

in preparation for the testflight tomorrow ... i found some problems

1.) amperage sensor all tIme show -80A (solved) -> #define AMPRERAGE_OFFSET -> first it produced an
compile error ( solved ) -> second time by compiling it a message apears the parameter always written (also
soved) -> i thing it was some rest from your debug working ....

2.) bring the second batt monitor on screen (solved)

@Bledi ... my """new""" codepices comes tomorrow by mail

@katana .... GoPro Hero HD (all resulutions) works fine

regards thorsten


regards thorsten

testflight today ...

bad news ... the Arrow (way to home) works .. let me say 99% ... in the down position (on screen) is not an arrow .. i see the number 11 and not the arrow .. .. the other direktions i see the correct symbol ... the rest of the ""flight mode"" works ..

regards Thorsten

What is the required settings (config.h) to get LCD style PID config working?
,
I upgraded my board to latest code, to give it a shot again with the new code. Serial data is flowing and updating OSD (tx and rx correct between MWC (MW 2,1) and OSD board), but I don't get PID config menu via OSD working (it used to work before upgrade). Can't get the configuration menu to appear via stick input. I might have missed something that might be altered in config.h, or I don't get it right with stick combo. I can't think of something else.

When trying to enable config menu, I start with middle stick on pitch, then full yaw to the right and then full pitch (moving stick forward, forward flight), no repsons at all, no config menu. As I undertstand this is the current stick combo for enabling config menu?

The copter works as it should and all channels have correct directions (no inverses on any channel).

BUG LIST :
- PID menu, impossible to go in - confirmed
- Home arrow, down position we see niumber 11 - to confirm
- Amperage sensor, to test (skytor code)
- Sencond batt - to implement (skytor code)

For PID menu I can't test but I purhaps find the problem.
in config.h :


change to



to activate menu :
- PITCH FULL
- YAW FULL
- TROTTLE at middle

is someone can test ?

Those settings didn't change anything for me, still no config menu.

Any settings in MW, like enabling LCD telemetry or any specific LCD config that is required in MW?

Bledi wrote:BUG LIST :
- PID menu, impossible to go in - confirmed
- Home arrow, down position we see niumber 11 - to confirm
- Amperage sensor, to test (skytor code)
- Sencond batt - to implement (skytor code)

Hi

- PID Menu (after Update config.h) impossible to go (SORRY i used normaly my android phone)
- Home arrow -> "" in test/debug ""
- Amperage sensor works ... it ""flickers"" on Screen but it Works
- Second batt - tested an Work

Code inklusive all open ""Bugs"" is in ""Upload"" -> PN to Bledi for double check

EDIT ->
Screenshot -> https://dl.dropbox.com/u/90162497/2012-07-30%2018.18.07.jpg
Screenshot2 ->https://dl.dropbox.com/u/90162497/2012-07-30%2018.38.10.jpg

palton wrote:Any settings in MW, like enabling LCD telemetry or any specific LCD config that is required in MW?

no it's a bug, I have to find where is

Hi @ ALL

for some one who want to see how it works (inklusiv HomeArrow ""BUG"" )

https://www.dropbox.com/s/e7awp68mxbngjx1/2012-07-30%2021.22.16.mp4 smal part of the FIRST !! flight off Iain from Irland

really strange !!! you never have the arrow ????
I don't have this bug.

Try to reload the mcm file

Bledi wrote:really strange !!! you never have the arrow ????
I don't have this bug.

Try to reload the mcm file

Hi

I have arrows in all direction BUT NOT backwards (i see 11) an in 5 a clock postion (i see 12)

and (is it a bug ?) the altitude show when not armed show 23865 meter

today i found an update for my GPS .. i think i test this one first befor i touch the Rushduino / MWC Code

maybe the update fixed more then the GPSfix LED

Hi ..

... update for the GPS Modul (10 Hz 115kBaud Typ FMP04/Media TEk MT3329 WAAS enabled Firmware)... noting diffrents for the OSD .. only diffrent number ... befor 11 an 12 ... now 8 and 5 (testet NOT at the same place maybe only diffrent position) ... ich think i musst search on the code to look whats happend

MCM file reload / eprom clear is next step for tomorrow

by good night

Hi ,

have upload the RushOSD_CP_v1_0.pde to my RushOSD to upload a new mcm file to the MAX7456 .
But how i have to send the mcm file to the RushOSD ?

First you reprogram your OSD to be able to be able to reprogram the MAX max 7456 circuit. Replacing the OSD fw with this special edition of code for upgrading the MAX 7456 circuit. That is what you have done, as I understand.

When you connect with a terminal program the OSD is waiting for a you to send the MCM file, you have to start terminal program, set serial parameters and download the MCM file.

This is well described in the pdf document found at the same place as the code is located. Read it, it describes very well how it is done.

http://code.google.com/p/rushduino-osd/downloads/detail?name=Caracter%20Map%20Update%20v1.pdf&can=2&q=

thanks
The PDF Manuell is what i looking for

What is status regarding bugs atm?

Edit:

btw, DiplayPIDConfigScreen(); will never run due to ConfigMode is never set to 1. ConfigMode is commented out where stickinputs are checked.

//ConfigMode = 1;

After uncommenting ConfigMode = 1 the PID menu is possible to enable with stick input.

I didn't follow for a while.
But is there compatibility with Multiwii 2.1 now ?

Version 9 does...

http://www.youtube.com/watch?v=CNouIFwaM3Q

greetz from vienna,
christian

cant open the website to look at the product.. it is just me or?

Hi @all

ill be back in germany ... sorry for my delay to debug the osd soft !!


AND the youtube link works fine on my samsung s3 cellphone via umts

regards thorsten

i'm really looking forward to using this osd for my fpv rig.. But im totally confused with the components and features that it provides and I need...
there are info all around the places. a neat PDF might help out a lot

my req:
1. basic osd stuff..
2. gps (it seems possible to pull gps data from fc now?)
3. current sensor(already have)
4. battery cell volt monitoring
5. power consumption recording(such as how much mah has consumed)

thanks

jy0933 wrote:i'm really looking forward to using this osd for my fpv rig.. But im totally confused with the components and features that it provides and I need...
there are info all around the places. a neat PDF might help out a lot

my req:
1. basic osd stuff..
2. gps (it seems possible to pull gps data from fc now?)
3. current sensor(already have)
4. battery cell volt monitoring
5. power consumption recording(such as how much mah has consumed)

thanks

Hi jy0933

1.) the BASIC OSD stuff works fine (with MultiWii 2.1)
2.) no .. now on MultiWii 2.1 is easy
3. an 5.) monitoring consumed mAh with external current sensor works on MW2.1 (tested with pololu ACS715)
4.) for volt monitoring you have 2 (3) lines to display different voltages


and .. maybe my picture (inklusiv bad calibratet current sensor) works for you
https://dl.dropbox.com/u/90162497/2012-07-30%2018.38.10.jpg

The only problem I found so far, is that the configuration menu (PID & stuff) does not work for me...