Rushduino OSD - Multiwii based open software osd

Splashy · Post by **Splashy** » Fri Mar 30, 2012 8:30 pm

JohnyGab wrote:
Splashy wrote:Can someone at least tell me whether it works with MultiWii 2.0 and, if it does then do I have to modify the MultiWii code.

Ok, sorry of my last post.

At the end of the serial file in the Rushduino project, there is some text in comme, O, Y and Z string, you need to put them into the serial of the multiwii firmware ( replace O and add the Y and Z ) this should work well

I have made the Mods and everything works very well now. Thanks for your reply and a great product.

May I suggest that the code that needs to be inserted is put at the TOP of the main file that is opened. I did look but clearly not well enough. It is not very intuitive to look at the bottom of the serial file.

JohnyGab · Post by **JohnyGab** » Sat Mar 31, 2012 12:33 am

I totally agree, and i will modify it.
I'm really happy that you liked it !

papa_lazerous · Post by **papa_lazerous** » Sat Mar 31, 2012 3:27 pm

JohnyGab wrote:
papa_lazerous wrote: There isnt a link on your website to make contact,

Concerning that complain, you can notice that I just added the section that allow customer to contact me. Its pretty straight foward.

Please understand that i'm an honest person, and I do all the possible to make all of you happy by doing business with me.

Thanks for adding that to your site, and I am sorry to hear you where sick I hadn't read about that. I look forward to getting the OSD in the near future

JohnyGab · Post by **JohnyGab** » Sun Apr 01, 2012 4:36 am

No problem! I understand that my personal life should not affect my customer.

I already assembled 25 of these, and here 16 of them waiting for the arduino bootloader

JohnyGab · Post by **JohnyGab** » Tue Apr 03, 2012 4:05 am

All not already shipped OSD WILL be shipped out wednesday.

I'm currently waiting for a big bunch of anti-static bag that I will receive tomorow.

papa_lazerous · Post by **papa_lazerous** » Tue Apr 03, 2012 4:27 am

JohnyGab wrote:All not already shipped OSD WILL be shipped out wednesday.

I'm currently waiting for a big bunch of anti-static bag that I will receive tomorow.

Big smile

Great news, looking forward to getting mine up and running

katana · Post by **katana** » Mon Apr 16, 2012 8:12 pm

Good morning to all, I would need a pleasure.
I bought a rushduino osd v1.1.
PROBLEM: I am not able to connect the osd to the pc, in order to update it.
I do not succeed to find guides, wiki, video ecc.. only this forum and another in rcgroup. Does a guide "for dummies" exist?

Proceed step by step:

1) download Metro libraries and puti in ...\arduino-1.0\libraries (this is ok? http://arduino.cc/playground/Code/Metro)

2) connect USB UART with function FTDI (for example this one flyduino.net/USB-UART-Adapter-new-Type_1)
Schematic:

USB UART-->Rushduino OSD

VCC-->VCC
GND-->GND
RX-->TX
TX-->RX

3)download Rushduino_OSD_MCE_V8.rar, then open Rushduino_OSD_MCE_V8.ino with arduino uno

setting for Arduino one:
tools-->Board-->Arduino Pro or Pro Mini(5v 16Mhz)w ATmega328
tools-->serial port (select the corect serial port)
tools-->Programmer-->AVRISP mkII

push UPLOAD...Uploading... --> And does not happen nothing, the advancement bar remains blocked.

where is it the error?

Splashy · Post by **Splashy** » Tue Apr 17, 2012 12:11 am

Are you sending out a shipping confirmation for the V1.2 boards. I should have been one of the first.

JohnyGab · Post by **JohnyGab** » Wed Apr 18, 2012 6:29 am

Splashy, all OSD as been send last week, and typical shipping take 6-10 open days, you should get it fast

JohnyGab · Post by **JohnyGab** » Wed Apr 18, 2012 6:34 am

katana wrote:Good morning to all, I would need a pleasure.
I bought a rushduino osd v1.1.
PROBLEM: I am not able to connect the osd to the pc, in order to update it.
I do not succeed to find guides, wiki, video ecc.. only this forum and another in rcgroup. Does a guide "for dummies" exist?

Proceed step by step:

1) download Metro libraries and puti in ...\arduino-1.0\libraries (this is ok? http://arduino.cc/playground/Code/Metro)

2) connect USB UART with function FTDI (for example this one flyduino.net/USB-UART-Adapter-new-Type_1)
Schematic:

USB UART-->Rushduino OSD

VCC-->VCC
GND-->GND
RX-->TX
TX-->RX

3)download Rushduino_OSD_MCE_V8.rar, then open Rushduino_OSD_MCE_V8.ino with arduino uno

setting for Arduino one:
tools-->Board-->Arduino Pro or Pro Mini(5v 16Mhz)w ATmega328
tools-->serial port (select the corect serial port)
tools-->Programmer-->AVRISP mkII

push UPLOAD...Uploading... --> And does not happen nothing, the advancement bar remains blocked.

where is it the error?

I'm sorry if you had hard time with that, a manual is almost done for that.

your board have to connector for serial a 4 pin, and a 6 pin. the 4 pin are the same that they are on the 6 pin...its just to hook up the multiwii board.

To be able to upgrade the firmware, you need an FTDI adapter, no the AVRISP MkII ( that to change the bootloader only, useless in that case, bootloader is already there ), like all other Arduino stuff. But, you also need to disconnect the serial link between the multiwii and the OSD in order to allow the FTDI to talk to the OSD.

does it sound clear said like that?

katana · Post by **katana** » Wed Apr 18, 2012 8:12 am

Dear Johny,
I use this to upload multiwii software in my flyduino mega, it's a FTDI adapter I believe (this one http://flyduino.net/USB-UART-Adapter-new-Type_1)
I have tried also with a ftdi prolific cable FTDI (from my remzibi OSB) same result

My pc is win 7 64 bit and I use arduino one.

1) I must not use AVRISP mkII, What Programmer I must use? tools-->Programmer-->???

2) I have simply removed the osd from the package and tried to connect to the PC for the update, he is not connected to nothing. Only the 4 cables to the ftdi vcc, gnd, tx, rx

Luca

JohnyGab · Post by **JohnyGab** » Wed Apr 18, 2012 1:36 pm

The 4 pin header is made so you can wire them to the multiwii ( you still need to unplug them when upgrading the multiwii or osd firmware.

The 6 pin header is made for the FTDI adapter, it have the DTR pin wich is required to upgrade firmware
I made this picture quickly, and i'll make it cleaner later

shufflez · Post by **shufflez** » Thu Apr 19, 2012 9:56 am

Hi all,
I'm back in the multicopter game again, currently building an FPV octo based on Flyduino FCP (and Multiwii of course).
With great pleasure I have received Rushduino OSD from Canada within about a week, great service from both postal services.
Luckily I saw JohnyGab's last post about where to connect the FTDI, as I was trying to connect the AVR ISP

Now I encounter a power/connection problem:
I'm using Fatshark Predator set, with (ImmersionRC) 100mW TX. This TX is directly connected to 2S (eventually 3S) battery via balancing lead.
When I connect a 5V UBEC to PWR, OSD works, but it appears my camera doesn't get power (yes, I've soldered the jumper for VCAM).
When I connect a 5V UBEC to 5V+ (ES=Extra Servo?) Rushduino OSD powers up and I get OSD in goggles, but no camera.
When I connect FTDI and 5V UBEC to 5V+ (no VTX connected because TX outputs power for cam), I get the OSD to show in goggles, but no camera power.

I figure not connecting VTX jumper will cause no voltage to go to TX pins right? Currently awaiting multimeter so I can check some more. Any suggestions?
Do you think it's advisable to let the TX's onboard 5V powerregulator power everything, or use BEC for OSD and CAM?

Thanks guys!

katana · Post by **katana** » Thu Apr 19, 2012 9:59 am

Thanks Johny!

it's work now

, the correct connection is this on rushduino osd v1.1 :

1)USB UART-->Rushduino OSD

DTR--> no label pin
RX-->TX
TX-->RX
VCC-->VCC
GND-->GND
GND--> no label pin

2) tools-->Programmer-->AVRISP mkII (it's work!)

In the next day i connect the Osd to the Multiwii and I check if everything works.

JohnyGab · Post by **JohnyGab** » Fri Apr 20, 2012 2:53 am

shufflez wrote:
Now I encounter a power/connection problem:
I'm using Fatshark Predator set, with (ImmersionRC) 100mW TX. This TX is directly connected to 2S (eventually 3S) battery via balancing lead.
When I connect a 5V UBEC to PWR, OSD works, but it appears my camera doesn't get power (yes, I've soldered the jumper for VCAM).
When I connect a 5V UBEC to 5V+ (ES=Extra Servo?) Rushduino OSD powers up and I get OSD in goggles, but no camera.
When I connect FTDI and 5V UBEC to 5V+ (no VTX connected because TX outputs power for cam), I get the OSD to show in goggles, but no camera power.

I figure not connecting VTX jumper will cause no voltage to go to TX pins right? Currently awaiting multimeter so I can check some more. Any suggestions?
Do you think it's advisable to let the TX's onboard 5V powerregulator power everything, or use BEC for OSD and CAM?

Thanks guys!

You are right, ..only one thing is missing. The +5V of the whole board will not be distributed to the Voltage-Tx and Voltage-Cam solder switch until you soldered. the BEC solder pad ( just over it ). Why that, in fact, if you dont solder it, PWR header is used, if you solder BEC, PWR pin will have the +5V signal. So in fact, you can use 2 sources of 5V if you want.

I'm currently uploading a video on Vimeo right now about those details, its about 10 minutes of HD explaination.

JohnyGab · Post by **JohnyGab** » Fri Apr 20, 2012 11:43 am

http://vimeo.com/40696974

katana · Post by **katana** » Mon Apr 23, 2012 7:45 pm

Another problem

I have updated the Caracter chart like described in the file pdf . (with Rushduino OSD CC rev Bledi 5.mcm ) (with pal setting)
Then i have re-inserted Rushduino_OSD_MCE_V8 (with pal setting).

Connect the videoTx to a monitor, conect the serial S3 on my flyduino Mega (serial S1 ppmsum, S2 Gps, I have free only the S3) and power up.

I visualise the osd but all the parametres are crazy.

I use multiwii 2.0 original, I must set up anything? I have not found any settign about rushduino osd...

papa_lazerous · Post by **papa_lazerous** » Mon Apr 23, 2012 8:18 pm

My OSD finally turned up today

. I found out it had been stopped and opened by Uk customs that's what the delay was.

Is there a proper guide on how to get the v1.2 OSD working with multiwii 2.0 ??

JohnyGab · Post by **JohnyGab** » Tue Apr 24, 2012 3:46 am

papa_lazerous wrote:My OSD finally turned up today . I found out it had been stopped and opened by Uk customs that's what the delay was.

Is there a proper guide on how to get the v1.2 OSD working with multiwii 2.0 ??

Nice to know that you had your board, in the last week, I knew that shipping was taking for ever, i'm currently looking for other way to ship, because I know some of you are not happy with shipping delay

Currently, the OSD is working with the OLD serial communication protocol, I will have to make it compatible with the new one

JohnyGab · Post by **JohnyGab** » Tue Apr 24, 2012 3:49 am

katana wrote:Another problem

I have updated the Caracter chart like described in the file pdf . (with Rushduino OSD CC rev Bledi 5.mcm ) (with pal setting)
Then i have re-inserted Rushduino_OSD_MCE_V8 (with pal setting).

Connect the videoTx to a monitor, conect the serial S3 on my flyduino Mega (serial S1 ppmsum, S2 Gps, I have free only the S3) and power up.

I visualise the osd but all the parametres are crazy.

I use multiwii 2.0 original, I must set up anything? I have not found any settign about rushduino osd...

What you are having look to be normal : Yes you do have to modify the mutlwii code a bit.
-First you have to use the OLD communication protocol MultiWii_2_0.zip is good, latter than that, i dont know.
-In the Rushduino OSD code, in the serial file, there is a section at the bottom that is commented ( Y, Z and O string ), you have to replace the actual O section of the multiwii code, by those 3 lines, and there you go, it will work better than now

papa_lazerous · Post by **papa_lazerous** » Tue Apr 24, 2012 4:53 am

JohnyGab wrote:
Currently, the OSD is working with the OLD serial communication protocol, I will have to make it compatible with the new one

That info is a little vague, can you please state if there is an instructional guide anywhere? I thought there was instructions?

1. Do I need to update the character chart?

2. Do I need to flash with latest FW or is it ready?

3. Can I use with multiwii_2_0.zip?

4. I found the commented code in your OSD FW

Code: Select all

  /* MULTIWII CODE 
    case 'Y':  // RUSHDUINO OSD TO Arduino - contribution from JohnyGab (rushduino.com)
      serialize8('Y');
      for(i=0;i<8;i++) 
      {
        serialize8(P8[i]);
        serialize8(I8[i]);
        serialize8(D8[i]);
      }
      serialize8(rcRate8);
      serialize8(rcExpo8);
      serialize8(rollPitchRate);
      serialize8(yawRate);
      serialize8(dynThrPID);
      serialize8('Y');
      UartSendData();
      break;

      case 'Z':  // arduino to OSD data - contribution from JohnyGab (rushduino.com)
      while (SerialAvailable(0)<30) {}
      for(i=0;i<8;i++) 
      {
        P8[i]=SerialRead(0);
        I8[i]=SerialRead(0);
        D8[i]=SerialRead(0);
      }
      rcRate8 = SerialRead(0);
      rcExpo8 = SerialRead(0); //20
      rollPitchRate = SerialRead(0);
      yawRate = SerialRead(0); //22
      dynThrPID = SerialRead(0); //23
      writeParams();
      break;
    case 'O':  // OSD to arduino data - contribution from JohnyGab (rushduino.com)
      serialize8('O');
      for(i=0;i<3;i++) serialize16(accSmooth[i]);
      serialize16(EstAlt*10.0);
      serialize16(heading); // compass - 16 bytes
      for(i=0;i<2;i++) serialize16(angle[i]); //20
      for(i=0;i<6;i++) serialize16(motor[i]); //32
      for(i=0;i<6;i++) {serialize16(rcData[i]);} //44
      serialize8(nunchuk|ACC<<1|BARO<<2|MAG<<3|GPS<<4);
      serialize8(accMode|baroMode<<1|magMode<<2|GPSModeHome<<3|GPSModeHold<<4);     
      serialize16(VERSION);  // MultiWii Firmware version    
      serialize8(armed);
      serialize16(GPS_distanceToHome);
      serialize16(GPS_directionToHome);
      serialize8(GPS_numSat);
      serialize8(GPS_fix);
      serialize8(GPS_update); 
      serialize16(i2c_errors_count);
      serialize16(cycleTime);
      serialize16(intPowerMeterSum);
      serialize8('O'); //49
      UartSendData();
      break;

*/

Can you please state EXACTLY where it needs pasting in multiwii please.

katana · Post by **katana** » Tue Apr 24, 2012 8:52 am

Papa_lazerous you have anticipated me,
johny, multiwii 2.0 it's ok? I don't have to modify nothing? corrected?
I must only modify the Rushduino_OSD_MCE_V8?
it is simpler for all to post the version V9 compatible with multiwii 2.0?

or I have understood badly...

and it is to be modified only multiwii 2.0 , in this case you can post a file .zip with multiwii 2.0 modified to use the osd?

without a detailed guide it is complex...
Thank you Johny.

JohnyGab · Post by **JohnyGab** » Wed Apr 25, 2012 5:41 am

its a little late today to work on that, but, i'll post more details really fast

Bledi · Post by **Bledi** » Wed Apr 25, 2012 9:17 am

The multiwii 2.0, in serial.ino you have to change :
line 119 :

Code: Select all

case 'O':  // arduino to OSD data - contribution from MIS
      serialize8('O');
      for(i=0;i<3;i++) serialize16(accSmooth[i]);
      for(i=0;i<3;i++) serialize16(gyroData[i]);
      serialize16(EstAlt*10.0f);
      serialize16(heading); // compass - 16 bytes
      for(i=0;i<2;i++) serialize16(angle[i]); //20
      for(i=0;i<6;i++) serialize16(motor[i]); //32
      for(i=0;i<6;i++) {serialize16(rcData[i]);} //44
      serialize8(nunchuk|ACC<<1|BARO<<2|MAG<<3|GPS<<4);    // added GPS info
      serialize8(accMode|baroMode<<1|magMode<<2|GPSModeHome<<3|GPSModeHold<<4|armed<<5);  // added GPS modes
      serialize8(vbat);     // Vbatt 47
      serialize8(VERSION);  // MultiWii Firmware version
      // new fields for using arduino GPS for OSD (OSD f/w >= 0.66)
      #if defined(GPS_FROM_OSD)
        serialize8(0x04);                 // Signalisation for OSD that MWC want GPS data from OSD
      #else   
        serialize8(GPS_fix);              // Fix indicator for OSD
      #endif
      serialize8(GPS_numSat);
      serialize16(GPS_latitude);
      serialize16(GPS_latitude >> 16);
      serialize16(GPS_longitude);
      serialize16(GPS_longitude >> 16);
      serialize16(GPS_altitude);
      serialize16(GPS_speed);            // Speed for OSD
      serialize8('O');
      UartSendData();
      break;

by

Code: Select all

case 'Y':  // RUSHDUINO OSD TO Arduino - contribution from JohnyGab (rushduino.com)
      serialize8('Y');
      for(i=0;i<8;i++) 
      {
        serialize8(P8[i]);
        serialize8(I8[i]);
        serialize8(D8[i]);
      }
      serialize8(rcRate8);
      serialize8(rcExpo8);
      serialize8(rollPitchRate);
      serialize8(yawRate);
      serialize8(dynThrPID);
      serialize8('Y');
      UartSendData();
      break;

      case 'Z':  // arduino to OSD data - contribution from JohnyGab (rushduino.com)
      while (SerialAvailable(0)<30) {}
      for(i=0;i<8;i++) 
      {
        P8[i]=SerialRead(0);
        I8[i]=SerialRead(0);
        D8[i]=SerialRead(0);
      }
      rcRate8 = SerialRead(0);
      rcExpo8 = SerialRead(0); //20
      rollPitchRate = SerialRead(0);
      yawRate = SerialRead(0); //22
      dynThrPID = SerialRead(0); //23
      writeParams();
      break;
    case 'O':  // OSD to arduino data - contribution from JohnyGab (rushduino.com)
      serialize8('O');
      for(i=0;i<3;i++) serialize16(accSmooth[i]);
      serialize16(EstAlt*10.0);
      serialize16(heading); // compass - 16 bytes
      for(i=0;i<2;i++) serialize16(angle[i]); //20
      for(i=0;i<6;i++) serialize16(motor[i]); //32
      for(i=0;i<6;i++) {serialize16(rcData[i]);} //44
      serialize8(nunchuk|ACC<<1|BARO<<2|MAG<<3|GPS<<4);
      serialize8(accMode|baroMode<<1|magMode<<2|GPSModeHome<<3|GPSModeHold<<4);     
      serialize16(VERSION);  // MultiWii Firmware version    
      serialize8(armed);
      serialize16(GPS_distanceToHome);
      serialize16(GPS_directionToHome);
      serialize8(GPS_numSat);
      serialize8(GPS_fix);
      serialize8(GPS_update); 
      serialize16(i2c_errors_count);
      serialize16(cycleTime);
      serialize16(intPowerMeterSum);
      serialize8('O'); //49
      UartSendData();
      break;

shufflez · Post by **shufflez** » Thu Apr 26, 2012 1:02 am

I'm sorry, but in my serial.ino (dev20120414) there isn't any case 'O' anymore.
Little bit more help please?

EDIT: Has been removed with r670 of serial.pde.

Bledi · Post by **Bledi** » Thu Apr 26, 2012 8:25 am

it's normal, the serial protocol had change in the last dev.
We are working on this new version but we wait an official realase.

The modification of the 'case' section is for multiwii 2.0

katana · Post by **katana** » Thu Apr 26, 2012 6:09 pm

I executed the modification to the serial.ino file.
Now the situation is this: whatch Untitled 1.jpg in attached
Anything I do, the screen remain the same, i arm the motors or begin to fly, it never changes... where is the problem now?

shufflez · Post by **shufflez** » Fri Apr 27, 2012 9:06 am

Hi Rushduino maestro's,

Quick question, I've wired everything up, reverted back to MW2.0 stable release, did Blendi's Serial.ino modifications and when I connect 5V BEC to PWR or 5V+ input the board powers up (as does my Flyduino, via the serial-port).
And I can see the OSD in my goggles. But when I connect my BAT1 (used for VCAM), I get picture from the cam, but don't see the OSD anymore!
BEC jumper is soldered BTW.

I believe the serial.ino (or serial.pde) mod Blendi wrote up hasn't worked for me, because I get the same as @Katana.
BTW Rushduino OSD is connected to RX3/TX3 (RX1 = Spektrum, RX2 = GPS).

Thanks a lot guys!

Bledi · Post by **Bledi** » Fri Apr 27, 2012 9:20 am

shufflez wrote:I believe the serial.ino (or serial.pde) mod Blendi wrote up hasn't worked for me, because I get the same as @Katana.
BTW Rushduino OSD is connected to RX3/TX3 (RX1 = Spektrum, RX2 = GPS).

What FC are you using ? For me the OSD must be connect to the same serial port as GUI.

katana · Post by **katana** » Fri Apr 27, 2012 10:18 am

My connections flyduino mega - rushduino osd

Bledi · Post by **Bledi** » Fri Apr 27, 2012 10:49 am

I think you have ton connect the OSD on serial 0 (like FTDI)
I just look at the code, all data are exchange on serial 0 not on another port

katana · Post by **katana** » Fri Apr 27, 2012 2:23 pm

Thanks you Bledi!

it works only with serial 0

shufflez · Post by **shufflez** » Fri Apr 27, 2012 3:22 pm

Bledi wrote:What FC are you using ? For me the OSD must be connect to the same serial port as GUI.

I'm using Flyduino V2.1 (ATMEGA 2560) flightcontroller.

Bledi · Post by **Bledi** » Fri Apr 27, 2012 3:27 pm

shufflez wrote:
Bledi wrote:What FC are you using ? For me the OSD must be connect to the same serial port as GUI.

I'm using Flyduino V2.1 (ATMEGA 2560) flightcontroller.

I think it's the same, connect the OSD to serial 0

shufflez · Post by **shufflez** » Sat Apr 28, 2012 12:53 pm

Problem is, when I connect 5V power to my Flyduino board, it doesn't give power on the FTDI port!
And when I power the Rushduino (on 5V or PWR), it turns off as soon as I connect the serial cable (no power on Flyduino!)

I'm feeling quite stupid right now...

EDIT: I'm still feeling quite stupid, I forgot to connect GND from Rushduino to CTS on FTDI (Serial 0) port. I should really listen better

Bledi · Post by **Bledi** » Sat Apr 28, 2012 1:41 pm

shufflez wrote:Problem is, when I connect 5V power to my Flyduino board, it doesn't give power on the FTDI port!
And when I power the Rushduino (on 5V or PWR), it turns off as soon as I connect the serial cable (no power on Flyduino!)

I'm feeling quite stupid right now...

So you find a solution or you need help ?
I you need help can you post a picture and a connection diagram ?

shufflez · Post by **shufflez** » Sat Apr 28, 2012 3:16 pm

Hi Bledi,

I've found solution on connecting the power and serial port, that is working.
Except for some issues with magnetometer, but that's a Flyduino/Multiwii issue.

Other issue I have is: as soon as I plug-in my BAT1, I only get camera signal on my goggles. Otherwise (no power to cam) i get the OSD!
I've soldered the VCAM jumper to BAT1 (middle and left pad) and the cam does get power, except I don't get video overlay.
I'll try to get a picture or diagram for you!

EDIT: Turns out my NTSC advertised camera is actually PAL. I think connecting the PAL camera to the Rushduino that was still on NTSC caused a config with the overlay.
Changed the Rushduino settings to PAL and now it works, great!

I'm one happy camper!

Bledi · Post by **Bledi** » Sat Apr 28, 2012 4:29 pm

yesss great !!!
I just speak with Johnny, we will try to give you a new release next week including the new serial protocol

shufflez · Post by **shufflez** » Sun Apr 29, 2012 11:51 am

Thanks Bledi and Johny! You guys rock, I always encourage (b)leeding edge products from guys with a passion for what they're doing.
Would implementation of this new serial protocol mean that we can also use TX/RX3 port? Would be great to have Bluetooth on RX0/FTDI, Spektrum PPM on RX1, GPS on RX2 and Rushduino OSD on RX3!

Keep up the good work!

Bledi · Post by **Bledi** » Sun Apr 29, 2012 12:10 pm

yes RX3 is on the new multiwii ! so we have nothing to do it will working.

Bledi · Post by **Bledi** » Sun Apr 29, 2012 7:47 pm

So good news. I had finish to code the new serial link.
You start tests tomorrow. The release is confirmed for the end of the week

Matt. · Post by **Matt.** » Tue May 01, 2012 11:14 am

To whom this may help,

1. The software for the OSD is compiled in Version 1.0 of the Arduino IDE.
2. The "Metro" library must be downloaded and imported into the IDE before it will compile. http://arduino.cc/playground/Code/Metro
3. Watch the video on hooking up the board. For the Cirus SE board users the markings on the PCB for the FTDI header have the TX and RX around the wrong way. Use the legend on the OSD board as a guide.
4. add and replace the serial case statements commented in the bottom of the serial.ino in the OSD software with the serial.ino of the Multiwii_2_0 software.
5. If you are getting the camera picture passing through the board but no overlay, config the OSD software for your camera type PAL/NTSC in the Config.h of the OSD software.

I hope this helps someone.

Matt

JohnyGab · Post by **JohnyGab** » Fri May 04, 2012 2:52 am

Hi everybody, i'm not dead!

Bledi and me are working on implementing the new serial protocol, so future will be easyer for all of us.

Its also the end of my fiscal year.....

, I need to know how much I have to give away to Stephen Harper and Jean Charest....lol

katana · Post by **katana** » Thu May 10, 2012 8:07 am

After a few hours of use I can say potentially he is an excellent product.
But...
it is some things that probably depend on my setup, the problems are:

1) Every time one enters in the modification menu the multirotor comes trim to dx, Every time! (and consequently it is impossible to trim to dx without entering in the menu…)

2)The modification menu freezing often, 1 time every 3 acces, the only way to solve is to disconnect power

3)The values of the pid, are not the real value read through GUI (exceeded certain values, for example 11 for the P).
ES: (only indicative)
Gui PID --->OSD PID
ROLL P: 8 ---> ROLL P: 8 OK
ROLL P: 11.5 ---> ROLL P: -13.4 :?:

For now I use the osd for the pid tuning , the problems listed are making much difficult to me the work...

M.Force · Post by **M.Force** » Fri May 11, 2012 12:25 pm

Great Project!

Is out there any possibility to get one of these Boards? All Shops that i found are out of stock an d on rushduino.com it is completely gone.
Will it be restocked at the near future?

katana · Post by **katana** » Wed May 16, 2012 7:45 am

I have a problem very more serious of the precedence, after pid tunig (with a lot of patience) it's time to fly!
and instead no :cry:

I have important problems of video noise, is not possible to fly in these conditions.

The strange thing is that, I use similar fpv setups in many models without problems.
I have made a simple test, can be seen in the attached image.
bypass the osd and the problem disappears. Ok the problem is the Osd.
I have one battery setup, in hovering 40-45 Amp.
I have noticed that the greatest Noise are presented when the motors are in motion and when the servo move.
in attached the scheme of my setup.

Bledi · Post by **Bledi** » Wed May 16, 2012 9:00 am

With hight power, you have more electronic noise.
When you use an OSD board the video signal cross the board and componants so it can be easyer impact by noise.
If you can, an easy solution is to put a aluminum plate between the OSD and other board. Don't forget to connect this board to the ground

LenzGr · Post by **LenzGr** » Wed May 16, 2012 9:22 am

katana wrote:I have a problem very more serious of the precedence, after pid tunig (with a lot of patience) it's time to fly!
and instead no
I have important problems of video noise, is not possible to fly in these conditions.

The strange thing is that, I use similar fpv setups in many models without problems.
I have made a simple test, can be seen in the attached image.
bypass the osd and the problem disappears. Ok the problem is the Osd.
I have one battery setup, in hovering 40-45 Amp.
I have noticed that the greatest Noise are presented when the motors are in motion and when the servo move.
in attached the scheme of my setup.

You have created a ground loop. Have you tried disconnecting the GND connection from the TX video connector to the OSD board?

Bledi · Post by **Bledi** » Wed May 16, 2012 9:42 am

yes you are true !

katana · Post by **katana** » Wed May 16, 2012 6:46 pm

Today I have had very a little time to test.
I have tried to remove the ground from the tx video. no change

Don't forget to connect this board to the ground

exactly what should I connect?

the osd have this connection:

OSD Serial 4 pin connector--> ftdi flyduino (ground connect to bec 5V)
OSD 3 pin tx video---> tx video (ground connect to bec 12V)
OSD 3 pin cam---> cam ground (ground connect to bec 12V) or if i disconnect ground video tx: ground?(ground connect to bec 5V)??

I suppose the ground loop is the problem, the osd board is quite distant to power distribution board and servo..

thanks for help!