I have started to add functions to MinimOsd code.
At first i did it for myself only. Added many functions i thought i need. Then opened this thread.
after a while, Pedro and later Miguel came, and things started to happen fast. :D
They have optimised the code and added even more things to it.
They have worked hard on CT, and it became a great tool!
Thank you Bough! :)
By now MinimOSD-Extra got a pretty advanced OSD.
Here it is in action:
- Changeable unit measurement (US, metric)
- Home alt
- Battery Percent
- Battery used mah
- Current Draw
- Time From Startup (cleared at takeoff to show exact flight time)
- OSD Menu
- Wind horizontal speed and direction, and also the average wind speed of the last few minutes.
- OSD on/off
- Switchable secound screen
- WP distance
- WP heading
- Crosstrack error
- Warning messages for Lost GPS fix, Stall, Overspeed, battery volt, battery Percent, RSSI
- Efficiency, glide distance & thermic notifier. 3 in one panel
- OSD Brightness
- HAM Call Sign
- After flight summary
- Trip distance
- Smoothened horizon
- Real heading
- Vertical speed
This functions can be turned on and off, and placed on different screens now, by the Config. tool.
Also RSSI, switching mode and channel and unit measurement, Stall speed warning, Overspeed warning, Battery warning volt, Battery percent warning, RSSI warning, can be set in new Config Tool.
We built in a new way of setting video standards. Now OSD does not guessing anymore :). You can set it fixed from CT. It is in "Video Mode" menu.
Here is how it looks: (This video is a bit outdated, sorry. I will make a new one soon.)
The MinimOSD-Extra project is here: Link
This project is the developing version of the official Arducam OSD located here: Link
The latest stable version is: 2.2
The latest version can be downloaded from here: MinimOSD-Extra R800
CT is included. (The FW for Plane, Copter, Character upload and the character file is in the "FW & Char" directory inside CT directory)
We are sharing it to see videos you make using it! :)
Hi Gàbor, thanks for your great improvement!
I've a little request, i use miniOSD-Extra with the latest APM Copter code,the percentage of the battery does not work, always at 150% i think because I'm not installing the current sensor.
My request is: a feature to set the n. of LiPo cell and calculate the % residual with a simply calc inside the minimOSD-Extra code, related to the alarm already set on the tension? :-)
Just completed another round of noise chasing on the board.
If you're running MinimOSD with a UHF system...don't forget to tie off your tx/rx lines with a toroid. I went a step further and soldered 330ohm ferrite beads inline on the tx and rx lines and that completely blocked the high frequency noise. I still have the CC3D to contend with but that's much less painful than the nearly -67db the minimosd was spewing.
I documented my scans here:
do you plan to support the jDrones MiniOSD board new pins : http://www.jdrones.com/wiki/jd-miniosd-v1-2-guide ?
I am eager of a FrSky PWM RSSI support.
I made a custom version of MinimOSD, with the following things :
- RSSI either from APM or from MISO PIN for PWM RSSI like FrSKy
- Flight Time when throttle is above 10%
- Climb rate
- Percentage of battery available with picture
- Possibility to select a parameter (STAB_KP / RATE_KP / RATE_KI / RATE_KD / RATE_YAW_P and ACRO_P) you what to remote tune (CH6) via OSD, and value is displayed while flying
- Possbility to enable / disable APM log and what log you want to enable
Because of the lake of space, I had to disable several things, and actually this version is only for Multirotor. So I can share my code if you want.
This thread has certainly started slowing down, which probably means we are getting very close to a stable release! I don't know if it is helpful for you to see anymore videos, but I've been flying a bit lately. If it helps I posted a flight over here. On that flight I took off on panel 2 which is pretty simple, and at 1:00 I realized I was missing information and switched to screen 1.
I have been very pleased with the performance of the firmware, it seems very good now. I did notice that my flight time didn't reset on one takeoff, and I'm curious what the reset trigger is.
As previously mentioned, the CT tool need some updating because the grid is off, and what you see isn't exactly what you get.
I am still hoping that the vertical speed +/- can be replaced with something more graphical like up/down arrows or chevrons. You can see by my trivial requests that this firmware is getting very mature.
Let me know if you have any new versions or features you want me to test. I am flying a beach mapping mission every monday.
Thank you for everything!
I switched to uzuhf and now the osd extra doenst show all flight modes
Only the first 2 modes shows correct. stab en althld, the other 4 shows as stab, in mission planner connected with 3dr the correct flight modes are selected in flight modes and correct pwm values
What could be the problem?
I have a very strange problem on MinimOSD. Probably not Extra specific, but since this thread is so active ... :)
I've recently installed a camera switcher, so I have 3 inputs and one output. I have 2 input cameras connected. When booting MinimOSD I can see the boot screen on both. As soon as the boot sequence is finished, the OSD disappears from the one camera and only available once I switch to the other camera input. I've switched the cameras, but the OSD only appears on the same camera - the Sony Super HAD II, while the cheap 5v BevRC camera only shows video without OSD.
I've noticed in the latest version of the CT that the grid coordinates of whichever item I'm placing don't match up to what is actually being calculated in the X and Y boxes on the left. In other words, I have to map out panel items by watching those two boxes rather than relying solely on the visual grid format for Panel 1 and 2 tabs. Has anyone seen this before? Am I just using a bad version of the CT? It is 126.96.36.199 that I'm using..
Dont know is it already fixed, but catched one more unsigned integer problem for crazy fpv people like me :D
This time distance from home.
I use MinimOSD rev 1.1 from 3DR (http://store.3drobotics.com/products/apm-minimosd-rev-1-1) and I encounter a strange thing : as soon as I arm my copter (APM 2.6), updating stops and the screen gets a fixed OSD : no more mode change, no more heading or anything else. Before arming, all is good. After disarming, nothing come back to life. The OSD has to be reset to have live data again. And this is only with Minim OSD Extra (2.2 or 2.4 prerelease). Data stay live after arming with original OSD ArduCam firmware. I tweaked update rates as specified in this thread, but nothing change : Minim OSD Extra freeze after arming. Does it tell something to someone ?