copterrichie wrote:Awesome, orded a MinimOSD a few days ago, hope to have it in hand soon.
Great Job BTW!
shackfu wrote:Hi,
is there a way to connect an external current sensor to the MinimOSD?
vpb wrote:Thanks for your great job, Kata!
I guessed this sw will come and ordered minim 3 weeks ago, but still not arrives yet, cant wait...
monkey wrote:...
...
Marc with RCHacker.com just put up a great video on the minimOSD clone and goes over a lot, great info well worth the 21 min watch.
http://www.youtube.com/watch?v=hMUvrjivOQM
He talkes a little about the overheating issues with the clone version (first version of minimOSD) and show how to put it into 5volt mode, this is a common issue with the first version of minimOSD and you can read about the overheating issue all of the web.
kataventos wrote:Hi,
1-in Multiwii software you don´t need to do anything unless you want to see amperage consumed;
2-you can not use Arducam config software;
3-Everything you need, according your needs and MWC config (sensors, etc) are on config.h. Folow the instructions/comment or uncomment;
4-Nice build and diary
I will work on a wiki (on the repository) to new arrived pilots to MWc cosmos![]()
Please check this link from time to time, there will be that information soon!
http://code.google.com/p/rush-osd-development/w/list
rortega wrote:I know that MinimOSD with your conde can show rssi info from Multiwii serial stream, but how can I read and measure the rssi signal from the DR8-II. I have got a CRIUS AIO PRO and MinimOSD working together thanks to your code and I see ON screen the vbat voltage, GPS data ... But want to see also the rssi info. Is it posible? Do I need some sensor or can I connect directly the ch2 ouput signal pin form the FrSky module to one of the analog input of the CRIUS AIO PRO? Need I to do some mod in the Multiwii code? I'm using multiwii dev r1240...
rortega wrote:I know that MinimOSD with your conde can show rssi info from Multiwii serial stream, but how can I read and measure the rssi signal from the DR8-II. I have got a CRIUS AIO PRO and MinimOSD working together thanks to your code and I see ON screen the vbat voltage, GPS data ... But want to see also the rssi info. Is it posible? Do I need some sensor or can I connect directly the ch2 ouput signal pin form the FrSky module to one of the analog input of the CRIUS AIO PRO? Need I to do some mod in the Multiwii code? I'm using multiwii dev r1240...
dramida wrote:...
...
FrSky delivers PWM signal on channel 2 as RSSI. It could be "read" either as PWM or through an integrator as linear voltage. I observed that most of minimOSD's has atmega chips with exposed terminals so an analog read would be easy to implement...
Last edit: could be used a pin from ISP witch has already pads (MISO-MOSI-SCK-RST) or they are already used for comunicating with MAX7456 ?
copterrichie wrote:Why not create code within the WMC to read the RSSI signal and pass that information to the OSD via the protocol?
KasparsL wrote:Today tried the OSD. I received the minimOSD v0.1, updated fonts and programmed with Rushduino 2.1. Overall i like it! It is my firs OSD ever also =].
Thank You!
Only I have noticed that menu browsing sometimes jumps several items not one. Can it be made like - do command (go left, right, up, down or sellect) if detected do it once, and if it is still present after 2 sec - then start to repeat it 1 or 2 times per sec. If released before 2sec - reset counter and wait for command again. Just an idea =]
Nice job for us Multiwii fans!
Hers is the video of test flight http://youtu.be/ayxhRc5IrsE I still need to sort the Video RX part - change antenna and add secont RX for diversity. I need tripod for the RX and monitor also! =]
KasparsL wrote:I am saying that I like the OSDonly the menu control response is quite "sensitive". And video was the first flight to check it how everything is working. People like reading posts with pictures and videos
KasparsL wrote:I am saying that I like the OSDonly the menu control response is quite "sensitive". And video was the first flight to check it how everything is working. People like reading posts with pictures and videos
kataventos wrote:KasparsL wrote:I am saying that I like the OSDonly the menu control response is quite "sensitive". And video was the first flight to check it how everything is working. People like reading posts with pictures and videos
You did not answer my question/suggestion, important stuff. (posted on your video)
Almost no-one use narrow screen (OSD Page configurable)and we were thinking in taking it off permanently to save some bytes for other features.
I know you have a 4:3 LCD but, I think you should have 16:9 option on it.
And:
-did you just flagged my youtube comment as spam?![]()
Take that off immediately or I will kick your ass...
kataventos wrote:I know what went wrong... I posted one first comment but I forgot something, deleted it making copy and paste of what I have wrote before... that´s it, for youtube is a spam.
About what I said... yes, displayed information places are different in narrow and wide, every one of them have a different code (place where stuff are displayed) the same for pal and ntsc because of TVlines number)
Just try to use it wide even with 4:3 stuff (camera and monitor) and report back. This is useful information for development.
Anyway, for the moment I can say that are big surprises to come from Power67 on this part of the code.
Cheers,
KV
KasparsL wrote:kataventos wrote:I know what went wrong... I posted one first comment but I forgot something, deleted it making copy and paste of what I have wrote before... that´s it, for youtube is a spam.
About what I said... yes, displayed information places are different in narrow and wide, every one of them have a different code (place where stuff are displayed) the same for pal and ntsc because of TVlines number)
Just try to use it wide even with 4:3 stuff (camera and monitor) and report back. This is useful information for development.
Anyway, for the moment I can say that are big surprises to come from Power67 on this part of the code.
Cheers,
KV
Hi, tried the "wide" setting, and actually it looks better positioned.
KasparsL wrote:Just saw this video - plain flying with OSD. http://youtu.be/n3gq8fZpUhM or this one http://youtu.be/4t_d4AonTXY
Does this OSD in video has better resolution than minimosd with MAX7456? I like the way the pitch and roll are displayed! Any chance to program it to look like that on minimOSD?
Peter wrote:I just uploaded the fonts and it showed the percentage and the ready message, but it gives strange characters and icons when using the osd.
Do you have any tips?
EDIT: Got it working. When using the OSD with 5V and 12V, you also need to power the 12V side when uploading the font.
dramida wrote:I saw some original arducopter minimOSD artificial Horizon videos and i observed that the horizon line works smoother on Y axis with more intermediary steps between on tilt.
http://www.youtube.com/watch?v=k3CN4hFHEMg
realpastaman wrote:1. How to change to wide mode? Or is it set already?
2. When I arm the quadcopter, its not showing on the display as armed. Any ideas? I'm using R1316 btw and NTSC camera
Thanks again for all your great work
itain wrote:realpastaman wrote:1. How to change to wide mode? Or is it set already?
2. When I arm the quadcopter, its not showing on the display as armed. Any ideas? I'm using R1316 btw and NTSC camera
Thanks again for all your great work
Start with 2. You need to edit Config.h and set the mode bits that would match your copter settings.
My best suggestion is to start MultiWiiConf, connect your quadcopter and see what boxes you have configured. Now assign each box with the next power of 2 and and use the results to replace the values in the Mode Active area of Config.h
For example, I have (see attached image):
ANGLE = 1 ==> #define STABLEMODE 1
HORIZON = 2 (not used)
BARO = 4 ==> #define BAROMODE 4
MAG = 8 ==> #define MAGMODE 8
ARM = 16 ==> #define ARMEDMODE 16
GPS HOME = 32 ==> #define GPSHOMEMODE 32
GPS HOLD = 64 ==> #define GPSHOLDMODE 64
(other values are not used by the OSD).
Upload the firmware to the OSD. Armed as well as other flight modes should be recognised.
Now to question 1. With the OSD connected to the quad you shooud ecter config mode and change the settings from NARROW to WIDE. Disarm the motors, then apply middle throttle, full right yaw and full forward pitch and wait a second. The OSD should go into config mode. The selection of WIDE or NARROW screen in in config page 5.
analogReference(INTERNAL);
vpb wrote:But I accidently plugged in the VideoIn (+) wire to MinimVideoOut (-) port, no more blue led, the board is now malfunctioning I think, cannot flash anymore (arduino error: programmer not respond). Another 2-3 weeks waiting...
Anyway, thanks Kata & his team's job, it's awesome osd!
#define MAX7456SELECT 6//10-ss
#define MAX7456RESET 10//10-ss
dramida wrote:Later on the day...
So i figure out the upload!
Firstly i uploaded font_update.ino with changes :
- Code: Select all
#define MAX7456SELECT 6//10-ss
#define MAX7456RESET 10//10-ss
Then i used TeraTerm, i selected the serial protocol with the right port, then File- Send command @ 19200baud.
BUT
The OSD shows wired characters. What am i doing wrong?
Return to Software development
Users browsing this forum: No registered users and 2 guests