"your" osd is probably counting lines erroneously, check this out and adjust in the software...

Originally Posted by jalves

"your" osd is probably counting lines erroneously, check this out and adjust in the software...

I've understood from the beginning this was most likely a code issue but I'm not a seasoned programmer, so would you mind being somewhat helpful and possibly telling me what variable needs to be changed or at least which section of code to look in? I can handle the hardware side fine, I've only just begun to learn how to read and write code, none of which has had anything to do with imaging.

if you do a video of the problem and put it online I could be of more help.

I just launched a hypothesis, try to change the line "line =0" in detectframe() to line =1...5...10 .

Check if this change something.

I have increased the variable to 35 where it now sits, this has shifted the entire image in the upward direction on my monitor but does not fully solve my problem.

The LOS, speed, and alt "section" of the image is now mostly cut off up top, it seems what I need to do is somehow decrease the amount of (vertical I think) lines or rather remove some of the open space from above and below the center line.

Surely I can't be the first to have experienced this issue.

Tw34k,

Do a video or at least show us more images of the problem.

I can't be more helpful with the information you gave so far.

Default "line" setting - cuts off bottom portion of overlay





With adjusted "line" variable, at 40.





As you can hopefully finally see, changing this variable just shifts the entire overlay up causing the top portion to now be cut off. I don't know how to be any more clear about this than I have been.

Simply put, the overlay (OSD) image needs to be shrunken down vertically, It's to tall to fit the screen

If you have anything specific you need from me, please do tell.

Originally Posted by Tw34k

Simply put, the overlay (OSD) image needs to be shrunken down vertically, It's to tall to fit the screen

Config.h what is your VIDEO_SYSTEM?

//===========================
// Video system: PAL or NTSC
//===========================
// Pal = 0, NTSC = 1
#define VIDEO_SYSTEM 0

Are you trying to overlay a PAL OSD on NTSC signal?

The config is set to 1 (NTSC)

The camera out is also set to NTSC @ 4:3 aspect ratio.

I briefly came across a post last night where someone else had similar issues, said it had something to do with the latest version of code not working well. All of the previous versions are in .doc format for some reason so until I get the chance to sit down at one of my other computers I'm at a stand still.

Originally Posted by Tw34k

All of the previous versions are in .doc format for some reason so until I get the chance to sit down at one of my other computers I'm at a stand still.

No, the file ends in .doc ( probably because the attachment system here is screwy ) but the files themselves are just .cpp/plain text.

from the first post:

The code can be opened with notepad++ or Arduino IDE. Please rename to .pde instead of .txt when using with Arduino.

Version 17 seems to work so far, the screen fitment issue looks to be gone.

Originally Posted by Tw34k

Default "line" setting - cuts off bottom portion of overlay





With adjusted "line" variable, at 40.





As you can hopefully finally see, changing this variable just shifts the entire overlay up causing the top portion to now be cut off. I don't know how to be any more clear about this than I have been.

Simply put, the overlay (OSD) image needs to be shrunken down vertically, It's to tall to fit the screen

If you have anything specific you need from me, please do tell.

Your cam output is 4/3 but the screen is 16/9 (I think). Perhaps the screen is streching the picture to fit the wider format. Look at Your screen setup.

No, I had already tried changing aspect ratio, it only cuts off the sides when changed. It seems it is in fact a version 18 issue, solved by using version 17 instead. I'll try and post some follow up pictures tomorrow.

There is a little bug in the NTSC settings in software version 0.18 mentioned before. As far as I rememer, it was a simple mistake with some capital-letters that makes NTSC-setting faulty.

If you can please check the #if VIDEO_SYSTEM routine

Line 154 in config. If you can please try to change "#if (video_system == 0)" to:
#if (VIDEO_SYSTEM == 0)


This is the code-part where it's used:
#if (video_system == 0)
// PAL
#define toplinetext 41
#define toplinenumbers 51
#define butlinenumbers 271
#define timer_line 252
#define gps_nmea_line 32
#define summaryline 102
#define current_calc_line 292
#else
//NTSC
#define toplinetext 24
#define toplinenumbers 34
#define butlinenumbers 229
#define timer_line 210
#define gps_nmea_line 15
#define summaryline 100
#define current_calc_line 260
#endif

Hi
I would like to thanks Dennis Frie and other contributors for such great project!
I realized DIYOSD with LM1881 on breadboard from bare components (no stupid arduino pro mini), recycled GPS module from remzibi and it simply works!

Next time I would design proper PCB, probably cheap single sided without mask, as breadboard is too laborious and not pretty at all.

Can't wait to try it in air.
Thanks!

nice

Originally Posted by kolin

Hi
I would like to thanks Dennis Frie and other contributors for such great project!
I realized DIYOSD with LM1881 on breadboard from bare components (no stupid arduino pro mini), recycled GPS module from remzibi and it simply works!

Next time I would design proper PCB, probably cheap single sided without mask, as breadboard is too laborious and not pretty at all.

Can't wait to try it in air.
Thanks!

Great Job kolin, there is no shame in bread boarding providing we only want a limited number of systems.

Here is my LM1881 bread boarding project based upon Dennis' design, it sits on top of an Arduino ATMEGA1280 and run MultiWii Firmware. The OSD is mobiDroneOSD.

There is STILL Life in the LM1881 design.

I've been testing DIYOSD on a breadboard with an Arduino UNO and an old TV. I had to adjust the line settings pretty dramatically for it to all show up on the screen. I thought I would post this for those having trouble with the top/bottom being cut off.

Here are my NTSC settings:

  //NTSC
  #define toplinetext 54
  #define toplinenumbers 64
  #define butlinenumbers 214
  #define timer_line 195
  #define gps_nmea_line 45
  #define summaryline 90
  #define current_calc_line 260

Here's what it looks like:



Cheers,

- Jason

Old TVs cut a lot but Goggles and recorders don't so no adjustments needed unless you are taking your old TV to field

I cann't get it to work with baud rate 115200. Is it even possible? I cann't change my baudrate because I need it to use with multiwii, my general purpose for this was to have one gps for multi wii and osd.. now it is not working with that rate.. :/

Originally Posted by walkmanz

I cann't get it to work with baud rate 115200. Is it even possible? I cann't change my baudrate because I need it to use with multiwii, my general purpose for this was to have one gps for multi wii and osd.. now it is not working with that rate.. :/

I'm not sure a baud rate of 115200 is possible. The serial data is read with polling and not interrupt. As the pixel-output will have highest priority (it's running in an interrupt), the data-transfer must be slow enough, to make sure no character is "missed". You can do a quick calculation, to see if it´s possible. Try to compare the "line-time" (the maximum length of the an interrupt) and the serial-speed. Just to get an idea

I'm not so into the code, I'm not a programmer.. well with 38400 baud rate osd works but for multiwii I need 115200 baudrate.. maybe there is the way to read the serial data at 115200 baudrate and still do the pixel generation?

Wanted to share my DIY OSD board with GPS, Current, V1, V2, and RSSI inputs

Please tell me your going to sell a few of these ??

Originally Posted by kristaps_r

Wanted to share my DIY OSD board with GPS, Current, V1, V2, and RSSI inputs

C'mon dude, you just keep making my builds look ugly as hell

On a more serious note - it's awesome to see the projects be used like that. Really nice and clean setup with a PCB.
Can't really say anything but great work

You should give the version with MAX7456 a shot if you solder PCB anyway

Originally Posted by kristaps_r

Wanted to share my DIY OSD board with GPS, Current, V1, V2, and RSSI inputs

want that!

That's awesome, hope to see some to buy!

Originally Posted by Dennis Frie

C'mon dude, you just keep making my builds look ugly as hell

On a more serious note - it's awesome to see the projects be used like that. Really nice and clean setup with a PCB.
Can't really say anything but great work

You should give the version with MAX7456 a shot if you solder PCB anyway

I will ...

Originally Posted by kristaps_r

I will ...

Sounds good
- and as always, feel free to sell whatever you want from all of these projects. They are uploaded with no strings attached at all.

Originally Posted by sarky1

Please tell me your going to sell a few of these ??

I was not going to sell them. I made this just because I wanted (liked). I don't have time even to test it.
I am also going to make one 25x25mm powered from RX 5v without USB with Bat, Current and RSSI inputs

When I will test them I will think about expenses and maybe sell some.

Originally Posted by Dennis Frie

Sounds good
- and as always, feel free to sell whatever you want from all of these projects. They are uploaded with no strings attached at all.

Thanks You give me real inspiration Dennis. I have more ideas in my head but don't have as much time as I want.

OK
I will solder some more of these after I will successfully test it. My friend also asked.
I summed components, board, soldering... and seems I could give away these for 29$ shipped worldwide with tracking. (I wish i could get components as cheap as Chinese and some Chinese to solder this )

If someone interested I will count people and solder that quantity.
Can't give any date but hope this would not take long (count people interested + order components + solder)

Please don't be angry if I will find out that something is not OK with resign. USB and OSD works fine, need to test all ADCs and serial port

hello,

I would like to join this thread and enjoy this great OSD, but my OSD does not work properly.

Attached pictures of my circuit, the only thing that shows the screen output is a snapshot that lasts a few milliseconds, and appears in different horizontal position every 10 or 15 seconds.

I've tried with the following changes in the code:

# define CONTROLLER 0 or 1

# define VIDEO_SYSTEM 0 or 1 (do not know the camera system as it is reused)

# define align_text_ 1 to 22 (I tested all intermediate values​​)

And the result is always the same. I can not find the error.

Thanks and sorry for my English

hello,

After many hours and testing, the result is that multiple cirtuitos not fail, but fails to VGA Adaptor AV:

http://www.ebay.es/itm/290694941022?...ht_4555wt_1397

Connecting the circuit to capture it works correctly.

Now the problem is that this model does not detect GPS:

http://www.ebay.es/itm/271079582518?...ht_1886wt_1163

I do not know how to set it from the code, and how they connect BACKUP and 1PPS signals.

Thank you.

The ebay site shows it requires a 115200 baud rate for the GPS. Make sure to update the code to that baudrate, although I'm not sure the Arduino will be able to handle that high of a serial rate. Worth a try, though.

A better option would be to replace this part of the code:

// Used to set the GPS update-rate to 5 hz, and GPGGA and GPRMC gps-strings (Only for MKT-GPS).

  Serial.print("$PMTK220,100*2F\r\n");
  Serial.write(13);
  Serial.write(10);

  Serial.print("$PMTK314,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*28 ");
  Serial.write(13);
  Serial.write(10);

with this:

// Used to set the GPS update-rate to 5 hz, and GPGGA and GPRMC gps-strings, as well as setting a baudrate of 57600 (O nly for MKT-GPS).

  Serial.print("$PMTK251,57600*2C\r\n") //to change go to http://www.hhhh.org/wiml/proj/nmeaxor.html and create a valid checksum.
  Serial.write(13);
  Serial.write(10); //57600 baud
  
  Serial.print("$PMTK220,200*2C\r\n");
  Serial.write(13);
  Serial.write(10); //5Hz refresh rate

  Serial.print("$PMTK314,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*28 ");
  Serial.write(13);
  Serial.write(10); //Sets GPGGA and GPRMC to update once every fix

It sets the baudrate 57600, which should always work (as opposed to using the gps' stock 115200 baud, which can be flaky with this OSD).

It would be a good improvement to put this into the shipping version of the code, just to remove some of the issues with the occasional stock GPS incompatibility.

It sets the baudrate 57600, which should always work (as opposed to using the gps' stock 115200 baud, which can be flaky with this OSD).

It would be a good improvement to put this into the shipping version of the code, just to remove some of the issues with the occasional stock GPS incompatibility.

thanks for the replies.

I've changed the lines indicated in the file DIY_OSD_v0_18.ino

But the result is the same.

SAT: 00
NO GPS FIX

The GPS blue LED flashes every second. I have checked the connections:

Tx GPS >>>>> Rx OSD (with transistors to increase voltage to 5V)
Tx OSD >>>>> Rx GPS (with diodes 3.3v)

thanks again for your time and help

Are you indoors? For me, even though I'm on the highest floor of my house, I don't get gps lock at all. Try the same thing you're doing, but go outside.

Some things that you may want to consider. The arduino doesn't need transistors to increase the voltage to 5v, because the logic high threshold of the Atmega is 3v; if the GPS is supplied with a solid 3.3v, there will be no problem with that.

Another thing is that you should really use a regulator to get the 3.3v for the GPS, its just a more stable voltage. It should never require more than 50ma, so for GPS regulators I like to use the TI TPS77033, but any 3.3v regulator will work well.

And I have to say, that's a really expensive GPS module.

Thanks Legot.

I've been testing for more than an hour on the outside with the new code, but not working.

I tested with a 3.3 V regulator with a diode in series and removing the transistors, but no way.

I tried on the computer with the program MiniGPS_v1.7.1 and everything works fine. I do not know what else I can try.

I'd appreciate if you show me where to buy some GPS economic model that works well with this OSD.

Regards

I'm using the Locosys LS20031, it's a MediaTek MT3329-based setup. It's not the cheapest ($50 at polulu.com), but it works well with the OSD. It's 3.3V, so you either have to change the settings external to the OSD (I used my PC with a usb->serial adapter) or have a logic level converter so that you don't write to the GPS serial channel at 5V. It's very sensitive, I get good lock inside my house, and it has a battery backup to keep the ephemeris for quicker acquisition. It's slightly power hungry, but I think most GPS chips are during acquisition.

hello again,

After many changes in the code I can not find the solution, because with the code mentioned in the line:

  Serial.print ("$ PMTK314, 0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 * 28");

Crack! and the execution does not continue.

I'll try to set Handmade gps with miniGPS program, but has too many values ​​I do not know how to fill, I have tried many options but not working.

I put a screenshot of my gps with possible options.

Thank you.

That is so strange. I use a 3329 based module as well, but the 3339 is supposed to be functionally identical. There's no reason to change modules if yours works with the MiniGPS program, I was just making a comment.

Try setting up the module for 57600 baudrate, GGA: 1, RMC:1 (all others:0), DGPS doesn't matter, and 5hz fix update rate through the Mini GPS program. Another possibility, is it at all possible that your RX and TX wires to the GPS are swapped? (I have problems with this all the time.)

That's the best I can come up with at the moment, sorry and best of luck.


Ooohh! something else that may or may not be worth a try is changing that line of code to:

  Serial.print("$PMTK314,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*28 \r\n");

hello,

First of all, I forgot to mention that the module is cheaper, this is the actual link:
http://www.ebay.es/itm/Very-Small-MT...#ht_1905wt_917

item code, after much reading in various forums, attached what I think would be a correct settings, but for some strange reason, if I put more than two sentences, execution stops and the program crashes.

  Serial.print("$PMTK251,57600*2C\r\n"); //  // Set NMEA port baud rate 57600 baud
  delay(100);
  Serial.write(13);
  Serial.write(10); //57600 baud

 Serial.print("$PMTK314,0,1,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0*29\r\n");
  delay(100);
  Serial.write(13);
  Serial.write(10); //Sets GPGGA and GPRMC to update once every fix
  
  Serial.print("$PMTK220,200*2C\r\n");  // //5Hz refresh rate = 200(millisecond) = 0.2(sec) 1/0.2 = 5 Hz
  delay(100);
  Serial.write(13);
  Serial.write(10); //5Hz refresh rate
  
  Serial.print("$PMTK300,200,0,0,0,0*2F\r\n");
  delay(100);
  Serial.write(13);
  Serial.write(10); 
  
  Serial.print("$PMTK313,0*2F\r\n");     // Disable to search a SBAS satellite. 
  delay(100);
  Serial.write(13);
  Serial.write(10);
 
  Serial.print("$PMTK301,0*2C\r\n");     // Disable to search a SBAS satellite. 
  delay(100);
  Serial.write(13);
  Serial.write(10);

I have put a battery to GPS to save the settings, and I've programmed from MiniGPS as attached image, omitting all configuration lines in the program, but does not work either.

If I set it to hand, how I can I remove the connection that goes from Tx OSD to Rx GPS?

The output signal of the GPS module working properly measured with an oscilloscope. This is the output:

$GPRMC,183242.000,A,4138.0757,N,00445.6716,W,0.38, 246.22,010213,,,A*70
$GPGGA,183243.000,4138.0758,N,00445.6712,W,1,6,1.1 7,748.1,M,51.6,M,,*4B
$GPRMC,183243.000,A,4138.0758,N,00445.6712,W,0.43, 246.22,010213,,,A*76
$GPGGA,183244.000,4138.0758,N,00445.6710,W,1,6,1.1 7,748.1,M,51.6,M,,*4E
$GPRMC,183244.000,A,4138.0758,N,00445.6710,W,0.45, 246.22,010213,,,A*75
$GPGGA,183245.000,4138.0759,N,00445.6708,W,1,6,1.1 7,748.1,M,51.6,M,,*47
$GPRMC,183245.000,A,4138.0759,N,00445.6708,W,0.53, 246.22,010213,,,A*7B
$GPGGA,183246.000,4138.0759,N,00445.6706,W,1,6,1.1 7,748.1,M,51.6,M,,*4A
$GPRMC,183246.000,A,4138.0759,N,00445.6706,W,0.69, 89.76,010213,,,A*4F
$GPGGA,183247.000,4138.0758,N,00445.6702,W,1,6,1.1 7,748.1,M,51.6,M,,*4E
$GPRMC,183247.000,A,4138.0758,N,00445.6702,W,0.68, 103.24,010213,,,A*7E
$GPGGA,183248.000,4138.0755,N,00445.6697,W,1,6,1.1 7,748.1,M,51.6,M,,*41
$GPRMC,183248.000,A,4138.0755,N,00445.6697,W,0.73, 104.27,010213,,,A*7F


This can not be so complicated ....

Wait wait wait... Is that the exact code your uploading to the OSD?
Because the entire setup routine for the GPS is commented out...

Before and after the serial.print section that you've been working with, erase the /* and the */

Maybe that's the problem? If it isn't, then I have absolutely nothing left to try.

hello Legot

Thanks for your time to check my code, actually, all code to configure the GPS is commented. If I do not comment, program execution stops and the OSD stops working.

So I manually configure the program MiniGPS GPS (attached image above) and battery backup saved settings.

I have also flashed the GPS to the latest version, but still not working.

I ordered some optocouplers to connect GPS and OSD, I do not know what else to try.

Too bad it does not work, it is a good and cheap GPS ideal for an interesting project like this. : (: (: (

Thank you very much to all for your time

Sorry I couldn't be more help.

Just know that in your case there is an issue somewhere with the OSD, the GPS seems to be working perfectly.

Good luck my friend.

Hey guys i have a problem here.

I want to use this one without any gps module like one of those "Simple OSDs" showing only time and voltage. So i stripped the "output.ccp" to only show voltage and time. So far so good works as expected. Now the problems starts. As time is calculated my the gps in need to find another way to calculate the time. I guess the best way to do this is using the Arduinos millis() command. So i added this to the calculation part of the output.ccp.

      flight_timer2[0]=((flight_time2/1000)/600)+3;     
      flight_timer2[1]=(((flight_time2/1000)%600)/60)+3;      
      flight_timer2[2]=(((flight_time2/1000)%600)%60)/10+3; 
      flight_timer2[3]=(((flight_time2/1000)%600)%60)%10+3;

If i declare for testing

flight_time2 = 1415000;

it shows me the correct time of 23:35 on the osd. Big Problem is i just cant get the time to start.

flight_time2 = millis();

just does not wok time always shows 00:00. I am quite new to arduino programming so anyone can give me a hind how to fix this ?

Here is what i have done so far

Hi all!

I've got some more time to try to solve my problems with gps.

First I changed the setup code for this:

 #define MTK_SET_NMEA            "$PGCMD,16,1,1,1,1,1*6B\r\n"
 #define MTK_SET_NMEA_SENTENCES  "$PMTK314,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*28\r\n"
 #define MTK_OUTPUT_4HZ          "$PMTK220,250*29\r\n"
 #define MTK_OUTPUT_5HZ          "$PMTK220,200*2C\r\n"
 #define MTK_OUTPUT_10HZ         "$PMTK220,100*2F\r\n"
 #define MTK_NAVTHRES_OFF        "$PMTK397,0*23\r\n" // Set Nav Threshold (the minimum speed the GPS must be moving to update the position) to 0 m/s  
 #define SBAS_ON                 "$PMTK313,1*2E\r\n"
 #define WAAS_ON                 "$PMTK301,2*2E\r\n"
 #define SBAS_OFF                "$PMTK313,0*2F\r\n"  
 #define WAAS_OFF                "$PMTK301,0*2C\r\n"
 #define SBAS_TEST_MODE_1        "$PMTK319,0*25\r\n"	//Enable test use of sbas satelite in test mode (usually PRN124 is in test mode)
 #define SBAS_TEST_MODE_0        "$PMTK319,1*24\r\n"

  #define GPS_SERIAL_SPEED 57600
  uint32_t init_speed[5] = {9600,19200,38400,57600,115200};

      for(uint8_t i=0;i<5;i++){
        
        Serial.begin(init_speed[i]);					   // switch UART speed for sending SET BAUDRATE command
        #if (GPS_SERIAL_SPEED==19200)
          Serial.write("$PMTK251,19200*22\r\n");     // 19200 baud - minimal speed for 5Hz update rate
        #endif  
        #if (GPS_SERIAL_SPEED==38400)
          Serial.write("$PMTK251,38400*27\r\n");     // 38400 baud
        #endif  
        #if (GPS_SERIAL_SPEED==57600)
          Serial.write("$PMTK251,57600*2C\r\n");     // 57600 baud
        #endif  
        #if (GPS_SERIAL_SPEED==115200)
          Serial.write("$PMTK251,115200*1F\r\n");    // 115200 baud
        #endif  
        delay(300);
      }
      
          
      // at this point we have GPS working at selected (via #define GPS_BAUD) baudrate
      Serial.begin(GPS_SERIAL_SPEED);
            
      Serial.write(MTK_NAVTHRES_OFF);
      while (Serial.available() != 0) {Serial.read();}
      
      Serial.write(SBAS_OFF);
      while (Serial.available() != 0) {Serial.read();}

      Serial.write(WAAS_OFF);
      while (Serial.available() != 0) {Serial.read();}
      
      Serial.write(SBAS_TEST_MODE_0);
      while (Serial.available() != 0) {Serial.read();}
      
      Serial.write(MTK_OUTPUT_5HZ);           // 5 Hz update rate
      while (Serial.available() != 0) {Serial.read();}  

      Serial.write(MTK_SET_NMEA_SENTENCES); // only GGA and RMC sentence
      while (Serial.available() != 0) {Serial.read();}   

      Serial.write(MTK_SET_NMEA); // Si no lo pongo no continua

And finally the execution is not stopped.

Now looking at the code, I have a couple of questions, I would like to see on screen data received by arduino, but I can not find this function in your code, there is no (Serial.read)

On the other hand I have doubts with external button, there are several lines of code like this:

  if (CONTROLLER ==1 | Usebutton == 1) {
  if (digitalRead(Buttonpin)==LOW) {

that use an external button, I would like some information on this subject.

Thank you very much.

Hey,

thanks to a tip from Dennis i could fix my problem. I did myself a power distribution board for small quads with an onboard diy osd which shows only time and voltage. The OSD is also able to control the quads leds to make them blink when battery is low:

DIY OSD Power Distribution Board (0 min 57 sec)

@kristaps_r
I am interested please let me know if you have one for sale.
Thx
Peter

Originally Posted by daito

@kristaps_r
I am interested please let me know if you have one for sale.
Thx
Peter

I'll let you know but that would be at least after week or two. Have a lot to do on other projects.

Hi!

This is my 1st post on rcgroups, i try the code and works perfect.

A video of my first test using diy-osd:

First test of diy-osd from rcgroups (0 min 45 sec)

My next test must include: more light, a better camera, a more portatile tv, and then i try gps first and then current/voltage sensors.

Thanks a lot!!

regards from chile,

Hello Everyone,

A good news about SimpleOSD Open.
As you know, we didn't produce it since few months because of new design and production. My plan was making it smaller, lighter and cheaper
After few PCB design problem and reproduction now I did it.

This is new SimpleOSD X2






It is coming with useful features for opensource programmers.

And best news it is only 39.90$
The product page: http://www.flytron.com/osd-headtrack...l-edition.html
Schematic: http://www.flytron.com/pdf/SimpleOSD_X2.pdf

Features:

• Working with both DIY-OSD(open source) and SimpleOSD XL(close code) firmwares. (compatible SimpleOSD XL firmware coming soon)
• 16Mhz Atmega328 Processor with Arduino Boot
• Standard 6 Pin FTDI Port for PC connection and other Serial sensors as GPS
• 100% compatible with DIY-OSD Project.
• I2C pins ready to solder for all sensors.
• 4 extra Analog input pins
• 6 extra Digital input/output pins
• On-Board Voltage Sensor
• One current sensor input
• Simple 3 pin (video,+,-) connection to video system.
• 5V regulated output for other sensors (120mA max)
• Build-in LM1881 video signal seperator
• PAL & NTSC compatible
• Only 1.95gr

You can use a standard FTDI cable to programming it.



I just add some lines into the DIY-OSD 0.18 firmware for compatibility. You can download it from the attachments.

@Dennis:
You can track the differences into the code with "X2" keyword.
Can you update your original for the future updates?

Here is the list:

config.h

Replaced line

//Arduino = 0, SimpleOSD OPEN = 1, SimpleOSD X2 = 2
#define CONTROLLER 2

Added this line because of different dim, voltage and current pins

 // SimpleOSD XL OPEN 16 mhz
#elseif (CONTROLLER==1)
         
  // Input from current-sensor and voltage-divider
  #define voltage_divider_input 7
  #define current_sensor_input 4
  
#if (dim_on == 1)
// This is used for dimming. can be changed to another pin if you want. 
 //define SimpleOSD OPEN's dim pin C5 
 //SimpleOSD OPEN XL
 #define DimOn  DDRC |= 0b00100000;
 #define DimOff DDRC &= 0b11011111;

#else
  #define DimOn  DDRB |= 0b00000000;
  #define DimOff DDRB &= 0b11111111;
#endif    
  
  #define little_delay _delay_loop_1(13);
 
 // SimpleOSD X2 16 mhz
#else
         
  // Input from current-sensor and voltage-divider
  #define voltage_divider_input 0
  #define current_sensor_input 1
  
#if (dim_on == 1)
// This is used for dimming. can be changed to another pin if you want. 
 //define SimpleOSD X2's dim pin B1
  #define DimOn  DDRB |= 0b00000010;
  #define DimOff DDRB &= 0b11111101;
#else
  #define DimOn  DDRB |= 0b00000000;
  #define DimOff DDRB &= 0b11111111;
#endif    
  
  #define little_delay _delay_loop_1(13);
  
#endif

Main Sketch

Replaced Line into SETUP section

//Define SimpleOSD X2 dim pin
#if (CONTROLLER == 2)
pinMode(9,OUTPUT);
#else
pinMode(9,INPUT);
#endif

Added into the SETUP section

// If SimpleOSD X2/LM1881
if (CONTROLLER ==2) {
attachInterrupt(0,detectline,FALLING);
attachInterrupt(1,detectframe,RISING);
pinMode(13,OUTPUT);
digitalWrite(13,HIGH); // Turn on the led

// Button with internal pull-up.
pinMode(6,INPUT);
digitalWrite(6,HIGH);

}

Please feel free to any question.
Cheers
Melih

Hi Melih
It looks good

I've been busy with the MAX7456 OSD project lately and not been around much here (you have probably noticed, that I have bought a few GPS-units and current-sensors).

I will try to get some time and update the software sooner or later.

By the way, send you an e-mail long time ago regarding the MAX7456 version. You are also welcome to use that for anything you like.

Hi Dennis,

Yes i noticed your GPS+Current sensor orders and I tried to making a surprise to you and put few units SimpleOSD X2 into your pack but didn't finish it in time :/ Anyway, now they are ready to shipping

Personally i don't like complicated electronics like MAX based OSD devices but of course i will glad to subscribe you.
Have you got any group for MAX based OSD project?

Originally Posted by MelihK

Hi Dennis,

Yes i noticed your GPS+Current sensor orders and I tried to making a surprise to you and put few units SimpleOSD X2 into your pack but didn't finish it in time :/ Anyway, now they are ready to shipping

Personally i don't like complicated electronics like MAX based OSD devices but of course i will glad to subscribe you.
Have you got any group for MAX based OSD project?

I would have been a bit surprised, to see a "random" piece of electronic

The extra components needed on the MAX7456 version is not exactly an advantage, but the overlay looks better and there is a lot more processing-time left. But the simple design here is really nice.

I will test the OSD ASAP and report back and have an updated software-version compatible

Question: As I didn't find the word(s) "air-speed" in this thread, I wonder whether air-speed data (instead of GPS speed) can be processed or is on the todo list?

Please, can some point me to a C Bitmap editor to create fonts and other items? I have Tobis ODS Charter Maker however, I would like to have something a little more robust.

Thank you.

Originally Posted by vipix

New WMC copter controler have GPS possibility.
Because i have using yours OSD, i want to ask if it is possible to connect this OSD as slave to I2C and provide all info for another arduino?

By now is required seperate arduino to make Serial GPS work with WMC I2C ports. I want to make simplier and use your OSD to display info and use as RTH in WMC.

I know it's an old post but I just stumbled on it and realized that I'm working on exactly the same thing!!! Did you ever get it to work with second Arduino and GPS going to DIY OSD via I2C? For me RTH is a MUST and second Arduino running RTH autopilot is a perfect solution. BTW - I went with LM1881 setup for DIY OSD as it's much easier and better looking too. I cleaned DIY OSD code as well (fixed few bugs in the process too )

Technical question here... please help meee! I'm killing myself trying to figure out whats right...
You say there is a negative part in the pal signal, which is backed up here:
http://en.wikipedia.org/wiki/File:PAL_2_lines.png

But then this guy is generating PAL with just 0-1v:
http://www.rickard.gunee.com/project.../pic/howto.php

How does it work if the Sync level is suppossed to be -1.5v ?!?!?!?!

I'd really appreaciate it if you could help me... I live in a NTSC country but I'm thinking about developing a PAL OSD that's plug and play with Multiwii and can get the Gyro-Accel-Magnetometer-altimeter data straight through serial... Of course it would be open source

Any help appreciated! I need this confirmed so that I can start developing while the PAL gear I ordered is on its way.

Originally Posted by alejoal07

Technical question here... please help meee! I'm killing myself trying to figure out whats right...
You say there is a negative part in the pal signal, which is backed up here:
http://en.wikipedia.org/wiki/File:PAL_2_lines.png

But then this guy is generating PAL with just 0-1v:
http://www.rickard.gunee.com/project.../pic/howto.php

How does it work if the Sync level is suppossed to be -1.5v ?!?!?!?!

I'd really appreaciate it if you could help me... I live in a NTSC country but I'm thinking about developing a PAL OSD that's plug and play with Multiwii and can get the Gyro-Accel-Magnetometer-altimeter data straight through serial... Of course it would be open source

Any help appreciated! I need this confirmed so that I can start developing while the PAL gear I ordered is on its way.

One OSD that takes serial data from MultiWii and draws AHI ... is called Mobidrone. It has same schematic as DIY OSD so nothing to invent, it is allready done and opensource: http://www.toptel.sk/multicopter/ind...&products_id=1

I think I saw also MinimODS code for MultiWii somewhere.

Hello all!

Have anyone of you added code for the BMP085 sensor in this project that we can use for accurate altitude? Yes I know that you Melih have done that..

Regards,
Carl

Originally Posted by alejoal07

Technical question here... please help meee! I'm killing myself trying to figure out whats right...
You say there is a negative part in the pal signal, which is backed up here:
http://en.wikipedia.org/wiki/File:PAL_2_lines.png

But then this guy is generating PAL with just 0-1v:
http://www.rickard.gunee.com/project.../pic/howto.php

How does it work if the Sync level is suppossed to be -1.5v ?!?!?!?!

I'd really appreaciate it if you could help me... I live in a NTSC country but I'm thinking about developing a PAL OSD that's plug and play with Multiwii and can get the Gyro-Accel-Magnetometer-altimeter data straight through serial... Of course it would be open source

Any help appreciated! I need this confirmed so that I can start developing while the PAL gear I ordered is on its way.

If everything was ideal and it was all DC coupled, the video signal would go negative. Higher quality but it makes things a lot more complicated to keep all parts working and interconnectable.

The simple solution is to AC couple the video signal; which just means feeding it through a large value capacitor. This passes the high frequency video signal to the next stage but blocks DC. The signal reference level is shifted positive or set above 0V by the next stage . Now it can operate from a simple single supply.

There are some minor problems introduced by the AC coupling. Quality is reduced and the average DC level is all over the place, which can affect the ability of the next stage to lock onto and track the video signal when it's less than idea; which is often the case with FPV.

I had this problem a while back and added a DC correcting amplifier to the groughd station. This made previously crappy cameras look quite good.

Paul

Originally Posted by RFnoise

Hello all!

Have anyone of you added code for the BMP085 sensor in this project that we can use for accurate altitude? Yes I know that you Melih have done that..

Regards,
Carl

Hi Carl,

Yes I did. But it is not an open product.
You can also do that with DIY-OSD, I can only show the way to you. Just download the ArduPilot project and isolate the altitude calculation code. Or maybe you can find BMP085 library with temperature compensated altitude calculation code on the net. Then you can integrate it into the DIYOSD code.

Sorry for this close code things but HobbyKing copying our all projects and we have to do this for surviving and supporting future projects
thank you for your understanding.

Melih

Originally Posted by MelihK

Hi Carl,

Yes I did. But it is not an open product.
You can also do that with DIY-OSD, I can only show the way to you. Just download the ArduPilot project and isolate the altitude calculation code. Or maybe you can find BMP085 library with temperature compensated altitude calculation code on the net. Then you can integrate it into the DIYOSD code.

Sorry for this close code things but HobbyKing copying our all projects and we have to do this for surviving and supporting future projects
thank you for your understanding.

Melih

No problem! I support you! Thanks for pointing me at the right direction.

Regards,
Carl

Here's some arduino code and detailed explanations on using bpm085 here :

http://www.sparkfun.com/tutorials/253

Otherwise, feel free to copy-paste from the MAX7456 OSD project where BMP085 is implemented and OpenSource.

The altitude calculation is a linear approximation atm

Hi i tried your scheme with arduino mega 2560, but there is mosi in pin 51 not 11, where i must make change in code ? i make change in pinMode(11,OUTPUT); to pinMode(51,OUTPUT); it's everything ? Thanks...
i tried non changed code, but display nothing show.

I tried now in this scheme


Thanks for any idea.

Ok, i tried on iduino nano http://www.ebay.com/itm/190746782529...84.m1439.l2649
but nothing show i tried turn slowly left or right with potenciometer but nothing happend.

Any idea ? Thanks for reply

I use version 0,18 without changes...

Ok, now works. but no readable text same as this picture
i use 50k potenciometer(try 100k but nothing), diode 1N4148, i use scheme on page 1. firmware 0.18

NOOOO, I bread boarded it. worked perfectly, made a protoboard to fit onto my mini pro and nothing haha, back to the drawing board.

Has anyone made a protoboard like the Denis did, if so is there any chance I can see your design? with some close up pics of the front and back ?

Yew got it, now I need to work out powering a 3.3v gps, sigh!

Originally Posted by sarky1

NOOOO, I bread boarded it. worked perfectly, made a protoboard to fit onto my mini pro and nothing haha, back to the drawing board.

Has anyone made a protoboard like the Denis did, if so is there any chance I can see your design? with some close up pics of the front and back ?

Originally Posted by njosef

Ok, now works. but no readable text same as this picture
i use 50k potenciometer(try 100k but nothing), diode 1N4148, i use scheme on page 1. firmware 0.18

I did not try again, but I just set up a new quadcopter and I really want an osd!! did you fix this?
I am going to rebuild the project again and use an oscilloscope to find out what's wrong..

Originally Posted by emerge

I did not try again, but I just set up a new quadcopter and I really want an osd!! did you fix this?
I am going to rebuild the project again and use an oscilloscope to find out what's wrong..

Hey Emerge.

What Arduino are you using? I had a very similar issue with the UNO but got it working just fine with a Mini Pro

no i havent time yet

wow nice project! Just saw it!
I was wondering if it's possible to change the view with something similar at the image i posted..maybe modding the script of the ascii..
(only an example)

Hello,

I know this project is old,

but is it possible to get the altitude by a BMP 085 Sensor instead of a GPS ?

I just need the alt for my OSD, nothing special.


-ironman

I tried again and now working. But i dont know where was problem.

The Arduino Micro is another very small board and is conveniently available at Radio Shack. I tried building the code for it, but for the Micro (essentially the same as the Leonardo) a number of constants used had to be changed because the Serial IO and timer are different from other boards. Also, the Micro has only about 28K available because the boot loader steals about 4K from flash memory and the compiled program is a bit too large to fit. (Maybe there are some tricks that can be done to reduce the memory taken up by the ASCII file.)

Has anybody else tried building this project for the Arduino Micro board?

--Van

I decided to try the Arduino Uno board and got better results with the compiler. The version 18 code compiled as-is but I cannot seem to get the sync to stabilize. The camera is a Sony 600TVL Super HAD that outputs NTSC video. The OSD display looks very similar to that in post #2271. I've tried 10K, 50K and 100K pots with similar results. The USB is being used for power source (5V).

TIA for suggestions,

--Van

Hey guys is there any simple way in the code to remove\disable the GPS and related text? Just point me in the right direction so I don't have to reverse engineer all the code here. I'm looking to just show pack v and mah at this time and add the GPS later if needed.

I just received the inexpensive NEO-6M module from Hobbyking- $21.99. I had the OSD working with an Adafruit breakout board, but when I attached the NEO-6M instead, I got nothing. The LED on the GPS flashes at about 1 second intervals. Testing with a simple Arduino Adafruit program shows the GPS putting out something, but not intelligible. The unit comes pre-set to 38400 baud. Can someone tell me how to make this GPS work?

Thanks

Dick

Originally Posted by joesa3rd

Hey guys is there any simple way in the code to remove\disable the GPS and related text? Just point me in the right direction so I don't have to reverse engineer all the code here. I'm looking to just show pack v and mah at this time and add the GPS later if needed.

Hi

This is not a pro solution but it worked for me (until someone tells me how to do it properly)

I just moved the text away from the visible area. In the config tab. Change the values as follows (maybe other values for NTSC).

#if (video_system == 0)
// PAL
#define toplinetext -100
#define toplinenumbers -100
#define butlinenumbers 271
#define timer_line -100
#define gps_nmea_line -100
#define summaryline -100
#define current_calc_line 292

Now I only see volts, amp and mah.

//Antonov
www.fpvteamsweden.com

Anyone add Sonar to this?
For Multicopter low level flying, baro or altitude is not very useful I think, but Sonar should be very useful and fun!

Originally Posted by NHmoose

Anyone add Sonar to this?
For Multicopter low level flying, baro or altitude is not very useful I think, but Sonar should be very useful and fun!

Thats hard.

Well, maybe it's because i'm just a noob in electronic and µC programming (actually, i wrote my first blink sketch on arduino 1 month ago ), but i tried to write my own OSD prog based on the atmega328/LM1881, and it's really a pain in the ass ! All what i can do is some flickering lines. I tried with timers, SPI and asm delay (i used your delayX functions Dennis, as i don't know asm), and i can't make a single clean lettre that doesn't flicker like hell !
So Dennis, please allow me to express my respect for your work and my thanking to share it (even if i still don't understand half of your code). u rox.

I've been thinking, and I don't think its possible with this particular hardware just because of the limits on timing that were mentioned.

On the implementation end of it you would need a gyro stabilized gimbal that's capable of 360 degree continuous motion (with continuously varying speeds) so that you can have an ultrasonic sensor or the like spinning at a constant speed on a level plane.

In software you would have to take the continuously changing range data from the Ultrasonic sensor and plot it as polar coordinates around a little stationary image of the multirotor. This polar graph would then have to spin in relation to the multirotor's orientation (from a magnetometer, which would also determine the speed of rotation for the sensor).

Overall, the hardware is a little tricky but pretty simple. The software is where it gets difficult, you would definitely need allot of power and speed to make it useable. Maybe in some other graphical OSD designed by a legend?