I have just now checked the manual of my DragonOSD 2.0+ OSD/Autopilot:

On the display I have two elements and the manual says:

Zitat

Group F
This group consists of two elements, the upper one being the ground distance while the lower one is the absolute or line-of-sight (LOS) distance.

Here you can see an example of it (lower right corner)
externer Link:


LOS element in this case does include height as one can see

So I say why discuss about this or that, lets have them both

@ghaynes754 MK has not built or sold SOSD, the comany that built it is smart-electronics from poland http://smart-electronics.eu

is there an update or so planned? irek, do you still add things on your sosd? my sosd is working great, however, lines and text would be really great.

best, grex

Just FYI:
Today I have tested MK FC/NC latest firmware 0.88m/0.28m update via Smart-OSD->MK Bluetooth 2.0->MK Tool

Result:
Did not work. Update failed (I tried NC first).

After that I could update it via MK USB with no problem.

Greetings
Franco

Franco I don't think that it is suggested to do firmware updates via wireless. Remember reading that somewhere in the wiki.

Gary

ghaynes754 meinte

Franco I don't think that it is suggested to do firmware updates via wireless. Remember reading that somewhere in the wiki.

Gary

Sure it's better via cable... but someone has to test it so we know if it would work or not

Hi guys,

Grex - recently I was focused mostly on finding that strange error, which sometimes is causing reboots of OSD,
after uploading settings via Bluetooth.
Unfortunately I was still unable to reproduce this error (even after twenty - thirty tests) - damn I hate such bugs
But I can confirm that reading 'all screens', sometimes reads screen contents in wrong 'screen slots'.
This will be fixed soon. I'm also going to add few 'label' elements with user defined text.

Gary, Yves , Franco
About LOS - we don't need to keep military or any other meaning of LOS
So I was thinking that I could modify a LOS a bit, so that it could show any of following values:
- "ground distance" (this is current LOS)
- "absoulte distance" - distance from vehicle to home - this is sqrt( ground distance^2 + altitude^2)
- "angle from ground" - angle between vehicle, home and ground.
So everyone could set it up, as he likes it

Franco - I am glad that you are happy with our OSD Thanks for your tests and observations
I will fix that battery, so it will have constant width.
As for visual styles - I will check what I can do


Best Regards - Irek

aronax meinte

...which sometimes is causing reboots of OSD, after uploading settings via Bluetooth.

I also had that once, after connecting via USB cable and reflashing it worked again.

aronax meinte

Gary, Yves , Franco
- "ground distance" (this is current LOS)
- "absoulte distance" - distance from vehicle to home - this is sqrt( ground distance^2 + altitude^2)
- "angle from ground" - angle between vehicle, home and ground.
So everyone could set it up, as he likes it

And the option to have more than 1 element or only 1 element but with 2 lines of text each showing a different distance value? That would be perfect.

aronax meinte

Franco - I am glad that you are happy with our OSD Thanks for your tests and observations
I will fix that battery, so it will have constant width.
As for visual styles - I will check what I can do

Best regs
Franco

wep800 meinte

wep800 meinte

Irek, another request:

Is it possible to show one of the Br-Ctrl temperatures?
For example the hottest one or
one or two you can choose.

Would be great

Hi Irek,

Have you seen new firmware (0.8 showing all Br-temps in OSD?
I assume it's easy for your now to have it the same like that?! (With the Amps)
Would be niceee!

http://www.mikrokopter.de/ucwiki/en/Firmware-0.88#Temperature-_and_Power_indicator_of_the_BL-Ctrl_in_the_OSD


Thanks !

Irek, have you looked at this already? thanks

Hello,

wep800 - yes, I have looked through the FC source code. I found the part responsible for querying the temperature of the BL,
I found a code that transmits temperature data to the Jeti, but I still could not find the part in which data is sent to mktools
As soon as I find the way in which BL data is sent to MKtools, I'll add tempertaure control for OSD.

Best Regards - Irek

is most recent firmware 2.25?

yvesOttawa meinte

is most recent firmware 2.25?

Yes

http://www.smart-electronics.eu/downloads/

aronax meinte

Hello,

wep800 - yes, I have looked through the FC source code. I found the part responsible for querying the temperature of the BL,
I found a code that transmits temperature data to the Jeti, but I still could not find the part in which data is sent to mktools
As soon as I find the way in which BL data is sent to MKtools, I'll add tempertaure control for OSD.

Best Regards - Irek

Thanks and good luck with that.


Just one more question, did you already find the sollution/cause for the flikkering of the OSD when connected to a 4S lipo yet?
Or did I miss that part?

Mine is still not very solid when flying on 4S

wep800 meinte

Just one more question, did you already find the sollution/cause for the flikkering of the OSD when connected to a 4S lipo yet?
Or did I miss that part?

Mine is still not very solid when flying on 4S

hmm... I fly with 4S and have no problem with flickering...

see: http://www.youtube.com/watch?v=vrE-sVVsv1g

aronax meinte

65oliver65 - you need to wait few more days

it is now one month

I don't have a flicker problem but I don't run my FPV cameras from the main battery. I got image problems doing that before the OSD so use a small 3S 2200mah battery for FPV.

Gary

Can someone please help.
I have the OSD connected up in my ground station but when I turn it on I see the video display with the words Smart OSD on it for about 1 sec then it goes blank. If I unplug the USB from the laptop then plug it in again it does the same thing.
I also can't get it to open any of the COM ports and says "COM1" does not exist, could this be something to do with windows 7 on my Eeepc? Are there drives you need to run this?

Does anyone have any ideas on what may be causing this to happen?

Because the OSD is directly connected to the laptop, do I still need the 5v external power connected to pins JP11?

Thanks
Craig

Craig

It won't work without a camera connected and powered up. Give that a try and see if it works. I remember having the same issue.

Gary

Hi Gary

I had the camera powered up and could see the subject on the monitor for a slit second before it disappeared.

Craig

Ok I've found that it was a dodgy USB cable and I can now connect to the OSD but the text is still all black and I and can't connect to the MK via the Xbee.

With the Kopter going and OSD showing I rotated the Kopter around moved it this way and that and it's not showing any data from the MK.

Is there anyone else using this OSD on the ground that can please help?

Thanks
Craig

Have you calibrated gyros? (Left UP)

Yep I had the motors running (props off)

Have you tried playing with the settings in Options->Global Parameters->Transparent uart port?

Does it work without xbee?

DRAGNET meinte

Have you tried playing with the settings in Options->Global Parameters->Transparent uart port?

Does it work without xbee?

Yep have played with the Transparent uart settings, currently have on USB port and Buffered.

As far as working with xbee, I'm having problems sending my own screens to the OSD with or without the xbee plugged in.

And its also not getting any data from the MK with the xbee plugged in.

Thanks,
Craig

Does anyone know how to reset the board back to original/default settings?

I loaded all the font files onto the OSD thinking it would solve my text issue but it just buggered things up. Now the monitor is displaying differently to the OSD manager.

Thanks

Hello,

I prepared new firmware 2.27 for OSD
I added new features requested on this forum:
- Camera frame (or just a rectangle for any purpose)
- User defined text (3 textboxes 48 chars max)
- LOS is now more configurable and can display any of following values:
-- Line of site
-- Line of sight
-- Angle of sight

Also communication via BT module should be now a little better.

Craig - you can also try this firmware.

Best Regards - Irek