Jump to content
remzibi

A poor man's OSD

Recommended Posts

I got one of these OSD's prebuilt from remzibi and at last got to fly it today. All I can say is fantastic, it dose what it says on the box.

I did not record the flight as my recorder battery went flat before take off before anyone asks :(

I wil be after a couple more for my other planes :)

Terry

Share this post


Link to post
Share on other sites
...I did not record the flight as my recorder battery went flat before take off before anyone asks :( ..

How it possible to mist first movie on UK ? :) that really pity :( .

Next opportunity do not forget about your recoder's battery :) .

Share this post


Link to post
Share on other sites

Yep very sorry, I was also trying out a new recorder but it seems the internal battery is bad.

I had a helper pointing the aerial at the plane and the distance to home was very good for making sure I kept my flight within his eyesight.

Terry

Share this post


Link to post
Share on other sites

At last I recorded a test flight with this OSD, I was flying a new easystar which failed to trim so still had a tendency to go right and I was also testing an auto tracking aerial and an archos recorder.

The easystar and the aerial need work but the OSD was great :)

http://www.vimeo.com/4279441

Terry

Share this post


Link to post
Share on other sites

Yes I don't have anything I dont need :)

I have :

Run time

Video volts

Direction home

Distance home

Speed

Height

Terry

Share this post


Link to post
Share on other sites

You do not need clibing (faling) rate ? you can use it as graphic indicator like arrow up or down or graphic plus numeric value of climbing or falling rate . This climbing rate is working very accurate as the altidude drift is very slow and climbing rate is derivative - so accuracy almost like with air prassure sensor .

Anyway - it is absolutely your invetion how you like have screen layout done :) .

Share this post


Link to post
Share on other sites

Yes I did consider the climb rate but decided it was not needed for this aircraft, I may well switch it on just to see how usefull it is though. I have a glider that I will use it on for sure but I need to get another couple of units from you as I dont like to keep swapping it about.

Terry

Share this post


Link to post
Share on other sites

That is a nice, compact item, Remzibi - I'd love to try one! I've just finished shortening all my antenna leads, so I could do with something else to fiddle with.

Terry, I see from your Vimeo vids that you fly near electricity pylons. I've been a good boy so far and not flown anywhere near such things, for fear of stray electrons shooting me down - apart from actually flying into them, have you noticed any problems?

Share this post


Link to post
Share on other sites

NO..lol..apart from flying into one I have had no problems, BUT I fly on 459Mhz and not 35Mhz so I may be more immune.

Also no problems with them blocking the video either :)

Terry

Share this post


Link to post
Share on other sites

I didn't expected but for some users reference I must also add the GPS picture with expalnation what side is UP what is BOTTOM .

Label is always bottom side , GPS must look the UP side to the sky looking for SATs .

I know that even in opposite side it can track 8 sats but better is to keep antenna looking in to the sky

post-3818-1241864358_thumb.jpg

Edited by remzibi

Share this post


Link to post
Share on other sites

Remzibi, is there a kit, or are you selling complete OSDs?

Share this post


Link to post
Share on other sites

Terry, do you have a URL for your 459MHz Tx?

Share this post


Link to post
Share on other sites

No its a home made system with modules from Radiometrix, not cheap but it works ok.

I have sold a few of my TX and RX but it is only a amature system for my own use realy so is not top grade stuff.

Here is a link to my first system

http://myweb.tiscali.co.uk/elevated/uhf.htm

Terry

Share this post


Link to post
Share on other sites

While I wait for mine to arrive, two questions, remzibi!

1. I use 'motor current' on my IFOSD as a reassurance that the motor is on. Perhaps I'm a bit paranoid, but when the plane is so far away I can't hear it, it's a useful check.

Any suggestions how I could get a similar measure from the PMOSD (poor man's OSD)?

(For example, I could wrap a few turns around one of the (brushless) motor wires, rectify it and smooth it and measure this on the 'motor volts' input - might tell me something....)

2. A feature of the IFOSD I really like is the ability to switch the OSD off using a spare receiver channel. I note there are pads on the PCB you mark 'for future use' - would this be easy to implement on the PMOSD?

(I know the idea of the PMOSD is that it keeps everything simple, but those two are things I find useful)

Share this post


Link to post
Share on other sites
While I wait for mine to arrive, two questions, remzibi!

1. I use 'motor current' on my IFOSD as a reassurance that the motor is on. Perhaps I'm a bit paranoid, but when the plane is so far away I can't hear it, it's a useful check.

Any suggestions how I could get a similar measure from the PMOSD (poor man's OSD)?

(For example, I could wrap a few turns around one of the (brushless) motor wires, rectify it and smooth it and measure this on the 'motor volts' input - might tell me something....)

2. A feature of the IFOSD I really like is the ability to switch the OSD off using a spare receiver channel. I note there are pads on the PCB you mark 'for future use' - would this be easy to implement on the PMOSD?

(I know the idea of the PMOSD is that it keeps everything simple, but those two are things I find useful)

There is almost ready software with additional ADCchannels - also for current sensor (any current sensor - possible calibration , even two way curerent sensors) - it will work independently from engine (main battery) voltage measurment .

Read some more here http://rc-cam.info/viewtopic.php?t=178 - there will be update with files when ready .

The main goal of that OSD was not occupy any RC channel - so it be possible to use with anyone even with very cheap 4 channel TX or 3ch (car) .

I do not plane to made any turn on -off function - but never say never :) .

instead of turn-on-off dispal - it is ability to arrange custom icons and information on screen most sweetable for any user needs .

By the way here is the II FPV meeting 2009 in Poland - here are briefly showed some of our harware "inventions" :) , and crash with clear picture untill ground hit :) .

http://vimeo.com/4675558

New LINK

Edited by remzibi

Share this post


Link to post
Share on other sites

I like the fact that it dossent use any radio channels as I like not having my video TX connected to my R/C RX. Then if I connected the OSD to my power system to give volt or amps it would also connect the power system to my RX too.

I dont even like my speed controller connected to my RX unless its opto :)

Terry

Share this post


Link to post
Share on other sites
I like the fact that it dossent use any radio channels as I like not having my video TX connected to my R/C RX. Then if I connected the OSD to my power system to give volt or amps it would also connect the power system to my RX too.

I dont even like my speed controller connected to my RX unless its opto :)

Terry

You right - RC RX is very sensitive for any external glitches and his range can decrease dramtically with bad connections or mess in cables .

Share this post


Link to post
Share on other sites
By the way here is the II FPV meeting 2009 in Poland - here are briefly showed some of our harware "inventions" :) , and crash with clear picture untill ground hit :) .

http://vimeo.com/4643750

That was a very entertaining video, but sad too (I never like to see lawn dart landings). What was the reason for the crash?

Share this post


Link to post
Share on other sites
That was a very entertaining video, but sad too (I never like to see lawn dart landings). What was the reason for the crash?

2.4GHz TX was covered by trees and lose range . 1.2GHz video downlik was working perfect till last moment .

Edited by remzibi

Share this post


Link to post
Share on other sites

Thanks - I guess I can always use a small relay to switch it in & out if I'm that bothered. The future firmware updates sound interesting!

Another question - the supplied USB-RS232 adapter +5v pin isn't connected, so I have to power the PMOSD up with a separate battery. Would it harm the PMOSD if I connected up the +5v RS232 pin, so the PMOSD is powered by the USB cable, for programming? i.e. will the onboard regulator get unhappy if it has no power input, and +5v is put across it's output? (Which regulator does it use?)

I still hanker after 'poor man's autopilot' (= loss of signal causes the 'return to base' indicator value to control the rudder). I guess something like that breaks the 'no connection to the Rx' rule...

Share this post


Link to post
Share on other sites
Another question - the supplied USB-RS232 adapter +5v pin isn't connected, so I have to power the PMOSD up with a separate battery. Would it harm the PMOSD if I connected up the +5v RS232 pin, so the PMOSD is powered by the USB cable, for programming? i.e. will the onboard regulator get unhappy if it has no power input, and +5v is put across it's output? (Which regulator does it use?)

Better NOT . At first units was 5V provided but this done more problems than advantages - simply connect USB cable and connect to external battery OSD for supply , as the supply input(12V) is protected against opposite connection . 5V is not protected by any way , so any accident will cause of burned OSD unit - and this is what we do not want to experience .

So always use external battery for power-up OSD - USB cable use only for communication , not for supply .

Edited by remzibi

Share this post


Link to post
Share on other sites

New software is realsed :

button function

- save home position (short click)

- video mode change (NTSC or PAL) press and hold button for about 1 second

- cofiguration mode (pressed when conecting to power)

show information DONE :

- latitude

- longitude

- speed

- altitude

- to-home course

- to-home distance

- satelite quantity

- video battery voltage

- main battery voltage

- flight timer

- variometer

- UTC Time

- UTC Date

- alarms for distance , ADC , atitude , batterys voltages

- 32 static displayed independent graphical-character symbols configurable

- 6 additional sensors on ADC channels , each individually calibrated and alarm set

- after detection 0 speed for cinfigurable X seconds , shows maximal values for altitude , distance , speed

OSD board after face-lifting looks like that :

s6300953.th.jpg

http://img19.imageshack.us/img19/7995/s6300953.jpg

s6300970.th.jpg

http://img32.imageshack.us/img32/4643/s6300970.jpg

Small video tutorials

Firmware update if newer version avaliable

http://vimeo.com/4698791

Update of BIN file (as well as Font file)

http://vimeo.com/4698755

Example of using ADC channel for external sensor - here RSSI information

http://vimeo.com/4698633

and for play and funny F-16 HUD screen layout captured

uvs090523_001_500.jpg

All avaliable for downloads - so every one can update his unit

http://rc-cam.info/viewtopic.php?p=1734#1734

Share this post


Link to post
Share on other sites

Fortunate community of this OSD owners are growing and growing , including FPV flyers but not only , even some universitys and high schools for experimental use and other projects adaptations as well as some home designers .

So lastly I have many additional questions similat to like that :

I like to use OSD in another use -

on combant plane (with graphics and sigt to aim enemy) ,

on boat ,

on U-boat ,

on RC-car ,

on real car with recording ,

on bicykle ,

on motorbike as parameter monitor ,

on my Video monitoring system cooperate with PC ,

on my personal Videos information stamp ,

on Video as frames counter (whatever it means),

on my own top secret project , so can not tell you about ,

etc. etc. and many more .

I do not need to use GPS - I do not need it , I like the analog inputs use only - like Voltages , external sensors and possibly RPM meter .

OSD is cheapper without GPS .

So that is OK - here is the firmware for beta testing for everyones want it to test - working without GPS module at all .

All other advantages are remain without change .

Button work only as Video mode changer and save (something like save home) function saving Video mode and reseting timer at any moment .

Iviting logo will gone after 5 seconds so not any save needed for proper work .

So after firmware update all information regarding GPS data are not displayed .

Other like Timer , GMT date (will be zero so made it invisible) , GMT time (will be zero so made it invisible) , Frequency meter(RPM meter) , ADC , and graphical object are displayed without changes - all can be configurable (scaling , alarms etc.) in usual way using PC configuration program . Character editor and all rest - works in usual way .

Free UART(COM) port is set to default 38400 baud rate receiving and can be used to display on OSD layout absolutely everything we want or need to display at any location using external device - if we want to connect any .

Now for those programerrs who want to display anything using that port and their device .

So we can deliver information to display at location x,y looks like that :

[leading character][text message][ending character][ending space]

ending space is displayed always after mesasage.

String to OSD shoult look like that :

"$MXXYYLLEEabcd"

must be end by enter character CR LF linefeed and carriage return .

$M - means that it is meassage to display (M must be uppercase)

XX - is a x coordinate on screen , must be hex value

YY - is a y coordinate on screen

LL - is leading character hex value from font table

EE - is ending character hex value from font table

abcd - is a "text message" to dispalay

when LL or EE is Hx00 - then will be not displayed at all

when text message is "" [empty] then also will be not displayed

So string to OSD can belike that in C aduino sample


serial.println("$M050a4a4bI like that")

so at location x=05 y=10 will be displaed this :

<I like that>
as you see LL is 4a it means [<] char and EE is 4b it means [>] char . or can be done like this way:

serial.print("$M")      //header for message

serial.print("050a")   //x and y coordinates 

serial.print("4a4b")   // leading and ending characters(graphics)

serial.println("I like that")  //message with LR CR ends string  

This is exactly how is working this function in OSD now . As advantage of this system when we define most significant bit of XX coordinate for 1 then we choose small fonts for text message display (only capital letters) - when is 0 then default big letters are displayed from characters table capital and small letters .

XX |= (1<<7) // set 7 bit for small characters 

XX &= ~(1<<7) //reset 7 bit for big characters

To be possible custom screen configuration , need of understanding how it is work . The screen is divided on net where the charcters are writen .The grid is 30x16 with PAL mode nad 30x12 in NTSC mode . Looks like that:

.  X------>

Y 1 2 3 4 5 6 7 8 ... 29 30

: 2

: 3

: 4

v 5

. .

. 15

. 16 

So when we made configuration we just teel the program where on the screen we want first character(or graphic) of our information - up left corner is coordinates X,Y (1,1) , bottom right corner is X ,Y (30,16) - remembre that NTSC mode Y must be no more than 12 .

How do we know what mode are currently in use ? - we will see after OSD init logo .

I hope that this firmware will help for many peaples doing his own project and will made poor man's OSD more open to world , also be more universal to variouse usage in many other project , not only flying platform .

-------

I foloowed of mmormota idea about add to OSD firmware ability to display any custom information delivered by RX input at the same baud rate with GPS module .

So if anyone have external device with GPS and retransmitiing GPRMC GPGGA messages , OSD can be used in usuall way - inluding autodetecting baud rate .

But also in middle of NMEA messages is possible to put custoom dispaly instruction - all described detaily in post above .

So here is the beta version of firmaware 1_60 - mostly for mmormota to test with ardupilot software .

It is working exactly as remzibi OSD (including GPS configuration commands sent at begining by TX line after baud rate detection) plus ability to display any custom oinformation delivered by UART(com port) in the middel of NMEA messages , format described in post above :

"$MXXYYLLEEabc"

So with this solution there are a bit solved problem of insufficient space in OSD's chip . maybe will be possible also displaynig artifical horizon and pitch using characters E0 to E7 from character-font table .

Here are some pictures of possible GPS connection with external device and OSD .

osd_your_device_766.jpg

osd_your_device1_150.jpg

osd_your_device2_277.jpg

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...