67 replies to this topic

[FredericG]

I consider the support for the EagleTree OSD module complete for the moment.

I wrote a wiki for it: http://wiki.openpilo...ree_OSD_Support

The code Sambas ans I used to reverse-engineer the protocol and config blobs is stripped from the code, but it is still in SVN of course.

Frederoc

[Matthias Badaire]

FredericG, on 23 August 2010 - 09:32 AM, said:

I consider the support for the EagleTree OSD module complete for the moment.

I wrote a wiki for it: http://wiki.openpilo...ree_OSD_Support

The code Sambas ans I used to reverse-engineer the protocol and config blobs is stripped from the code, but it is still in SVN of course.

Frederoc

Hi,
Do you know if the OSD Pro uses the same protocol ?
I could be interesting to have Artificial Horizon and more graphic element than the only text based display.
Thx

[FredericG]

Matthias Badaire, on 29 August 2010 - 02:07 PM, said:

Hi,
Do you know if the OSD Pro uses the same protocol ?

No, I do not know. Perhaps somebody who owns a pro-version can try if it works. Or, if somebody feels like lending me a pro for a few weeks, I could test.

I am unsure how much time I would be willing to put into supporting the pro-version As you might know, there are a few projects going on to make powerful OSD solutions.  The main reason for us to support the pro version, would be to support people who own such an OSD. I suppose, supporting the standard version made more sense than the pro version...

Frederic

[Matthias Badaire]

I am aware for Tom's effort from UK :http://www.rcgroups.com/forums/showthread.php?t=1290963
I just hope that he will go to the bottom of this project.
It seems that most effort for a graphic OSD opensource failed so far.
Using the ET OSD pro looks like a bad solution (not opensource) but at least it is available now.

[dankers]

The ET OSD was a simply solution that is very cheap, I've flown loads of FPV and honestly all the flashy OSD are just annoying and get in the way, I am very sure they are created by people who simply don't fly FPV much but instead want to over-engineer something. The ones with horizons etc all use dated thermopile technology and are also closed source as stated by Matthias, its not really what we are about.

If there is interest we can create our own, maybe we can start with the C-OSD code and port it to an STM32, there are loads of option but we have a autopilot to finish first! The ET OSD is the cheapest out there at $40, works well enough (does not get in the way and tells you where home is) and was way less work than creating our own.

[henrik04]

I bought the PRO version and the GPS expansion.. What a stupid I am! I didn't realize that I needed the e-logger as well!

I just discovered this forum! Ah well at least I'll be able to check protocols with (from GPS) to e-logger and to the OSD pro..

I write in C (not original) but in Verilog for CPLD and FPGA. So multitasking on hard level..

I am trying to find an e-logger locally but none seems available (cable version 150 Amps)    

Anyway.. going to browse this excellent forum..

Henri

[Coptaire.com]

Welcome on board Henri!

[IceWind]

This thread is a bit stalled but here it goes.
Does any of the OSD Pro owner ended up trying to use the same/similar used by the OSD from ET?
I have a OSD Pro and of course I'd  like to use it with the CC board.