Rushduino OSD - Multiwii based open software osd

dramida · Post by **dramida** » Tue Jan 01, 2013 5:17 pm

I am impressed with Rushduino versatility. I have a minim OSD and i want to program it with Rushduino. As i understand, it is necessary to not only upload the Atmega328 sketch in Arduino but to upload a character set in MAX7456 video driver. I know this information is scattered around 74 pages.

Would be very useful to make a tutorial for new entry users on on how to set up Rushduino. In this way new users would participate in evolving Rushduino along with MWC.

carlonb · Post by **carlonb** » Tue Jan 01, 2013 9:53 pm

dramida wrote:...
...
Would be very useful to make a tutorial for new entry users on on how to set up Rushduino. In this way new users would participate in evolving Rushduino along with MWC.

Hi Dramida,
I attached a zip file with the arduino sketch for Rush/Minim OSD board, a PDF manual and an .mcm file that is a char set to upload in max7456.
Thanks to original developers of all above we can start up with this new adventure.
Here http://code.google.com/p/rush-osd-development/downloads/list is the code repository for the latest releases (for this thanks to Kataventos and Itain).
Bye
Carlo

carlonb · Post by **carlonb** » Thu Jan 03, 2013 10:15 pm

New fly test with Mwii Rushduino S/W and Minim OSD.

http://www.youtube.com/watch?v=pO5suA6vA3U&feature=youtu.be

I have modified the charset with new symbols and smaller numbers and letters, now the screen is much better and clean.
Cheers,
Carlo

trailblazer · Post by **trailblazer** » Fri Jan 04, 2013 12:20 am

Is your new charset already available for download? ATM I´m not that motivated to include all your improvements and bugfixes that have been done by you guys in my own version of the rushduino SW. So I´m back on main road

kataventos · Post by **kataventos** » Fri Jan 04, 2013 12:53 am

trailblazer wrote:Is your new charset already available for download? ATM I´m not that motivated to include all your improvements and bugfixes that have been done by you guys in my own version of the rushduino SW. So I´m back on main road

I´m sure that you have your own great version of this rush thing.
Just keep in mind that this is a community, sometimes there is one thing or another that make us a little disturbed, but the main thing is to develop stuff. Remember that there is a guy that wrote your SW and his name is J.Gab.

I can assure you that your CharM is not available for download on the repository, and if it was, not without your name on it.

We all appreciate your work, keep yourself close.

EDIT: We are working on KV 2.1, it will not be radically different, but we work for everyone, keeping this SW working, and the most important, BUG FREE.

MINIMOSD IS FULLY IMPLEMENTED :mrgreen:

kataventos · Post by **kataventos** » Fri Jan 04, 2013 1:03 am

@ Dramida

The WIKI is going to be edited with the help of you all, if I forgot something please report.

http://code.google.com/p/rush-osd-devel ... Map_Upload

trailblazer · Post by **trailblazer** » Fri Jan 04, 2013 1:48 am

kataventos wrote:
trailblazer wrote:Is your new charset already available for download? ATM I´m not that motivated to include all your improvements and bugfixes that have been done by you guys in my own version of the rushduino SW. So I´m back on main road

I´m sure that you have your own great version of this rush thing.
Just keep in mind that this is a community, sometimes there is one thing or another that make us a little disturbed, but the main thing is to develop stuff. Remember that there is a guy that wrote your SW and his name is J.Gab.

I can assure you that your CharM is not available for download on the repository, and if it was, not without your name on it.

We all appreciate your work, keep yourself close.

EDIT: We are working on KV 2.1, it will not be radically different, but we work for everyone, keeping this SW working, and the most important, BUG FREE.

MINIMOSD IS FULLY IMPLEMENTED

Ups - I think you got me completely wrong! I´m a lousy programmer and just wanted to test out some stuff on the great codebasis that has been developed here. I shared all the stuff that I have done, even the custom charset, here in the thread. Nothing more happens to my SW so far. The big problem is the incompatability of the charsets and the fixed screenlayout (that I didn´t liked). It is not that easy to get this in line with all the "official" developments going on here. I haven´t done any community based programming project yet and have no experience with that, so sorry if I acted a little bit too "closed" for some of you.
I really appreciate all the work of you guys, so thats what I meant when I said " on the main road again".

kataventos · Post by **kataventos** » Fri Jan 04, 2013 2:08 am

@ Trailblazer

your lousy programming got us a real time AH! it´s not so lousy after all :roll:

Carlonb is working hard to get things different, I also don´t think that this new screen layout or char map is going to make the difference, but I will work with him to make some real difference on 2.2 dev.

You are welcome if you want to make part, you have edited a char map before

with the right tools is easy as a few hours around it.

power67 · Post by **power67** » Fri Jan 04, 2013 11:18 am

Ok guys, while I sort out an issue with the direction home and such I thought I would offer another function to the OSD.

I have seen some OSD that show the current throttle position so I added that in. I am not sure if anyone wants this function but it may be good for planes and wings to keep at a good cruise setting.

anyway, it is not great coding but it works. the ugly part is that I would like to create a right justify function but have not got there yet so I just did the best I could to right justify it. I am new to Arduino coding so dont bash me too hard. Perhalps if there is interest in this function, someone can write it better and add it to the next rev. I did not assisn a #define for it yet.

it "turns on" when the system is armed and it also automaticly calibrates to your throttle settings.

Thanks
Ross

Place this in the Screen.ino

Code: Select all

void displayCurrentThrottle(void)
{
  // CurentThrottlePosition is set in Config.h to line 11 above flyTimePosition
  // Calibrate high and low throttle settings  --defaults set in GlobalVariables.h 1100-1900
  if (MwRcData[THROTTLESTICK] > HighT) HighT = MwRcData[THROTTLESTICK] -5;
  if (MwRcData[THROTTLESTICK] < LowT) LowT = MwRcData[THROTTLESTICK];
  
  //insert symbol for throttle 
  screenBuffer[0]=0xC9;
  MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]);
  //map current throttle to 0 -100 scale
  if(!armed) {
    screenBuffer[0]='-';
    screenBuffer[1]='-';
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+2);
  }
  else
  {
    int CurThrottle = map(MwRcData[THROTTLESTICK],LowT,HighT,0,100);
    //begin right justify
    int Digit = CurThrottle;
    int CTDigit = CurThrottle % 10;
    itoa(CurThrottle % 10,screenBuffer,10);
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+3);
    CurThrottle /= 10;    // Shift by one digit
    CTDigit = CurThrottle % 10;
    if (Digit < 10){ screenBuffer[0] = 0;  }
    else { itoa(CurThrottle % 10,screenBuffer,10);}
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+2);
    CurThrottle /= 10;    // Shift by one digit
    CTDigit = CurThrottle % 10;
    if (Digit < 100){ screenBuffer[0] = 0;}
    else { itoa(1,screenBuffer,10);}
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+1);
    // add % to end 
    screenBuffer[0]='%';
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+4);
  }
  
}

Place this in the Config.h under the Middle of the screen section

Code: Select all

const int CurentThrottlePosition[2][2]=            {
  LINE11+22  ,LINE11+21  ,LINE11+23+60  ,LINE11+21+60  };

Place this in the GlobalVariable.h

Code: Select all

//For Current Throttle
int LowT = 1100;
int HighT = 1900;

kataventos · Post by **kataventos** » Fri Jan 04, 2013 12:20 pm

power67 wrote:Ok guys, while I sort out an issue with the direction home and such I thought I would offer another function to the OSD.

I have seen some OSD that show the current throttle position so I added that in. I am not sure if anyone wants this function but it may be good for planes and wings to keep at a good cruise setting.

anyway, it is not great coding but it works. the ugly part is that I would like to create a right justify function but have not got there yet so I just did the best I could to right justify it. I am new to Arduino coding so dont bash me too hard. Perhalps if there is interest in this function, someone can write it better and add it to the next rev. I did not assisn a #define for it yet.

it "turns on" when the system is armed and it also automaticly calibrates to your throttle settings.

Thanks
Ross

Hi Ross,

this software is what we all can do with it

I will test your contribution and report, I´m sure that many will like it!

Cheers,
KV

kataventos · Post by **kataventos** » Fri Jan 04, 2013 4:32 pm

@ Power67

THROTTLESTICK indicator not working, please verify using last developments from repository.
I´m working on debugging what we have now for 2.1 and testing Minim.

Thanks,
KV

power67 · Post by **power67** » Fri Jan 04, 2013 4:47 pm

Just checked the repository

28 minutes ago, you did some cleaning in the config.h file and removed the THROTTLESTICK #define

it was

Code: Select all

// RX CHANEL IN MwRcData table
#define ROLLSTICK        0
#define PITCHSTICK       1
#define YAWSTICK         2
#define THROTTLESTICK    3

you removed that section.

nevermind..... just checked again and it is back. 1 min ago
Try it again it should work.

Thanks

power67 · Post by **power67** » Fri Jan 04, 2013 5:26 pm

boy do I feel like an amateur.

Found the right justify code that you guys have got in place...... its much cleaner

change the screen.ino part to

Code: Select all

void displayCurrentThrottle(void)
{
  // CurentThrottlePosition is set in Config.h to line 11 above flyTimePosition
  // Calibrate high and low throttle settings  --defaults set in GlobalVariables.h 1100-1900
  if (MwRcData[THROTTLESTICK] > HighT) HighT = MwRcData[THROTTLESTICK] -5;
  if (MwRcData[THROTTLESTICK] < LowT) LowT = MwRcData[THROTTLESTICK];
  
  //insert symbol for throttle 
  screenBuffer[0]=0xC9;
  MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]);
  //map current throttle to 0 -100 scale
  if(!armed) {
    screenBuffer[0]='-';
    screenBuffer[1]='-';
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+2);
  }
  else
  {
    int CurThrottle = map(MwRcData[THROTTLESTICK],LowT,HighT,0,100);
    //begin right justify
    ItoaPadded(CurThrottle,screenBuffer,3,0);
    screenBuffer[3]='%';
    MAX7456_WriteString(screenBuffer,CurentThrottlePosition[videoSignalType][screenType]+1);
  }
  
}

kataventos · Post by **kataventos** » Sat Jan 05, 2013 3:07 am

Power67 implementation is working great and it will be on next release

Like many are saying, we need a new Char Map, we are going to work on that.
This Implementation will be available without symbol for now.

rortega · Post by **rortega** » Sat Jan 05, 2013 2:30 pm

dynai wrote:Hi rortega,

best way to do this with minimOSD is to use the voltage monitor of multiwii, use a voltage divider konsisting of 2 resistrors like here http://www.rcgroups.com/forums/showthread.php?t=1340771

Mis wrote:BTW for more than 3S battery we can different divider because 51k/33k can measure only up to 12.5V battery voltage. With 100k/33k we can monitor up to 6S packs. For 100k/33k divider, the VBATSCALE should be about 86.

then enable the "VBAT" option in the multiwii code
and in the rushduino osd software by kataventos select

#define MAINVOLTAGE_VBAT // Uncomment to change from MAIN VLOTAGE Analog Pin to MwVbat (must be defined on MWcode)

after youve loaded the software maybee you need to go to the config screen (page 3) of the OSD which you acces via max-throttle max yaw and max pitch (took me a while to find this, had no yaw on my multiwii-wing )

kind regards Chris

I've build the divider with 100k/33k and I've seted up VBATSCALE to differents values (including 86), but I get on screen arround 4.7 v.
I thought that the problem could be the analog input pin, so I've tried defining in config.h A3 and also A0, but i can't see the correct voltage.
Do any body know the correct pin for the CRIUS AIO pro?

power67 · Post by **power67** » Sat Jan 05, 2013 7:02 pm

rortega,

have you played with the VBATSCALE in the multiwii code? I had to adjust my quite a bit in order to get it work. For some reason, I too did not get the values that I calculated so just adjusted to match a known voltage on the best charged battery I had.
Try to use A3 as that is the standard AD pin and you will not have to reassign it in the code.

--(EDIT)-- I also found that when adjusting the VBATSCALE value, I offten had to run the clear EEPROM arduino example to get the new value to go in.

Hope this helps

Ross

dynai · Post by **dynai** » Sat Jan 05, 2013 8:52 pm

Hi,

the Crius Pro is Fitted with an Atmega 2560 as is the Flyduino Mega

A0 is the correct Voltage Pin for that board

-> (http://multiwii.googlecode.com/svn/trun ... 20Mega.png)
you wont need to change the pin in the code as the Arduino MEGA as Target-Board defines this pin in the multiwii software

you should see the correct voltage when you connect the multiwii-conf and connect gnd of your flight pack to gnd of the controller and plus of your flightpackt to the voltage divider

i allways get 4.7v when there is no battery connected to my board

kind regards Chris

sisco211 · Post by **sisco211** » Sun Jan 06, 2013 1:20 pm

Hello and great job.

I ve got flyduino board and i want to know where i could find a rushduino osd board for France. And how to wire this board. Could i used serial port 3 for exemple.

Thx Sisco

itain · Post by **itain** » Sun Jan 06, 2013 2:13 pm

sisco211 wrote:Hello and great job.

I ve got flyduino board and i want to know where i could find a rushduino osd board for France. And how to wire this board. Could i used serial port 3 for exemple.

Thx Sisco

I do not know if an original Rushduino osd board is still available. New versions of the software are compatible with MinimOSD and compatible boards. The limitation is that these boards do not have analog inputs so you need to get voltage and current reading from the main board.

If you are using any of the recent development versions of MultiWii you can connect to any serial port available. If you are on the official 2.1 or older that will work only on serial port 0.

-- Itai

Bledi · Post by **Bledi** » Sun Jan 06, 2013 7:08 pm

OK I had some news of Jean Gab. I can't explain you but for the moment he can't continu developpement and other.
I whish him to be better rapidly.

Thanks for all that are working on this OSD !

carlonb · Post by **carlonb** » Sun Jan 06, 2013 7:14 pm

I wish Jean to be better soon and thanks to him that startet this project.
Bye
Carlo

kataventos · Post by **kataventos** » Sun Jan 06, 2013 11:54 pm

Bledi wrote:OK I had some news of Jean Gab. I can't explain you but for the moment he can't continu developpement and other.
I whish him to be better rapidly.

Thanks for all that are working on this OSD !

Hi Bledi,

you know... this is good news because I was imagining the worse
Give him a hug from me.

Cheers,
KV

kataventos · Post by **kataventos** » Mon Jan 07, 2013 12:16 am

OK, Wise Man´s Day Dev as promised.

I speak in the name of this team, and I´m proud to say that Rush 2.1 is out and ready for download :mrgreen:

These are the changes since 2.0:

-Full Implementation of MinimOSD;
-Hide GPS related info when there is no fix;
-More realistic Climb rate arrows;
-Heading bug fixed;
-Configuration active help on config.h;
-Option to show heading as 0..359;
-Conversion of numbers and coordinates to a text string;
-Define for decimal point character;
-Auto statistics page after flight when disarmed;
-Throttle usage percentage.

In name of the Team ( KV _ ITAIN _ CARLONB _ POWER67 ) please enjoy.

Cheers

http://code.google.com/p/rush-osd-development/

NOTE: To exit statistics page at the end of flight you have to: throttle middle and down again.

trailblazer · Post by **trailblazer** » Mon Jan 07, 2013 6:55 pm

kataventos wrote:OK, Wise Man´s Day Dev as promised.

I speak in the name of this team, and I´m proud to say that Rush 2.1 is out and ready for download

These are the changes since 2.0:

-Full Implementation of MinimOSD;
-Hide GPS related info when there is no fix;
-More realistic Climb rate arrows;
-Heading bug fixed;
-Configuration active help on config.h;
-Option to show heading as 0..359;
-Conversion of numbers and coordinates to a text string;
-Define for decimal point character;
-Auto statistics page after flight when disarmed;
-Throttle usage percentage.

In name of the Team ( KV _ ITAIN _ CARLONB _ POWER67 ) please enjoy.

Cheers

http://code.google.com/p/rush-osd-development/

NOTE: To exit statistics page at the end of flight you have to: throttle middle and down again.

Great news :mrgreen:

My TBS discovery quad build is nearly completed, so I will check out this fresh release. I´m really happy about the heading bugfix

kataventos · Post by **kataventos** » Wed Jan 09, 2013 3:26 pm

Hi,

to generate less confusion with the implementation of the Minim OSD, I started a new topic for Minim related stuff here: viewtopic.php?f=8&t=2918
so, if you are a Minim OSD user please subscribe and use the new topic from now on.

Cheers,
KV

kataventos · Post by **kataventos** » Thu Jan 10, 2013 3:48 am

Last OSD recorded flight with KV_2.0, next will be with 2.1 showing bug fixes and new features.

Thanks for watching, don´t forget to subscribe.
The most important is to download the SW and have fun :mrgreen:

http://youtu.be/lkAXFUaCtMc

olex · Post by **olex** » Fri Jan 11, 2013 2:35 am

This seems to be exactly what I was looking for! And at a great price, too, much better than most standalone OSDs. Will definitely order a MinimOSD once I actually learn to fly my quad properly and start getting the FPV gear together.

A few questions: will this work without a GPS sensor? How much information will I lose, if it does? Obviously the speed and distance readouts, but will it be able to show altitude and climb rate from the BAR, and heading from MAG? And last but not least, what connections do I need on the FC - I currently use a Crius SE v0.2, it has a 6-pin FTDI and 4-pin TTL connectors, will those be enough?

kataventos · Post by **kataventos** » Fri Jan 11, 2013 10:28 pm

olex wrote:This seems to be exactly what I was looking for! And at a great price, too, much better than most standalone OSDs. Will definitely order a MinimOSD once I actually learn to fly my quad properly and start getting the FPV gear together.

A few questions: will this work without a GPS sensor? How much information will I lose, if it does? Obviously the speed and distance readouts, but will it be able to show altitude and climb rate from the BAR, and heading from MAG? And last but not least, what connections do I need on the FC - I currently use a Crius SE v0.2, it has a 6-pin FTDI and 4-pin TTL connectors, will those be enough?

Hi Olex,

-Every information is MWC dependent, If you don´t have Gps you will only lose related information.
-Absolutely, serial connection is what you need.

Count · Post by **Count** » Wed Jan 23, 2013 5:47 pm

Hi,

perhaps someone can help me.
I flashed my Rushduino OSD V1.2 with the Rush_KV_2.1 firmware.
Everything went fine and I installed it on my copter.
After a short indoor testflight the video went blank and the LED on the Rushduino was dark.
I suspected a problem with the power supply.
The only connection to and from the rushduino were the serial cable from the Crius AIO Pro and camera/video TX. Camera is selfpowered, Video TX too.
The Rushduino was powered through the 5V line of the serial connection.
I connected the FTDI, no LED.
I connected the BEC of the Video TX to the 5V Pin of the ES connector and the LED lit up again.
The video link was working, but no OSD overlay was there.
After about 2min the Multiwii Logo came up, but nothing else happened for the next 5min and then I cut power.
Now there is only a video picture for a second after connecting the lipo and then darkness.
Any idea what is wrong here?

Thanks,

Count

kataventos · Post by **kataventos** » Thu Jan 24, 2013 1:56 am

Hi Count,

sorry to hear that, I presume you have second version of that board! I think you have to change your capacitors... please search this topic (because I do not have time for that at this moment) some pages behind and look for people who had the same problem. They changed capacitors and everything went normal again.

Cheers,
KV

Count · Post by **Count** » Fri Jan 25, 2013 1:13 pm

I thought the capacitor problem only caused a noisy image. Is this still the problem with the 1.2 version of the board?
Right now I have an OSD overlay again (changed nothing) and crystal clear, the OSD just seems to freeze now and then. Not something I would go flying with.
If I can salvage some capacitors anywhere I´ll try and change them.

Thanks

Count

krystal · Post by **krystal** » Fri Feb 08, 2013 10:39 pm

Any one know how to calibrate barometer altitude from 137 meters on the ground to 0 ?

kataventos · Post by **kataventos** » Sat Feb 09, 2013 1:46 am

krystal wrote:Any one know how to calibrate barometer altitude from 137 meters on the ground to 0 ?

Hi,

what altitude are you talking about and what firmware are you running on both, Multicopter and OSD?
There is no calibration, OSD will display only what FC sends if you are running KV Team firmware!

krystal · Post by **krystal** » Sat Feb 09, 2013 2:25 am

kataventos wrote:
krystal wrote:Any one know how to calibrate barometer altitude from 137 meters on the ground to 0 ?

Hi,

what altitude are you talking about and what firmware are you running on both, Multicopter and OSD?
There is no calibration, OSD will display only what FC sends if you are running KV Team firmware!

Im talking about altitude from Multiwii board. I've got 137m on the ground. I saw your video: http://www.youtube.com/watch?v=V4JkmixV ... e=youtu.be
You have 0 meters on the ground. How you do that? Changes in multiwii code? How?
I've got Multiwii 2.1 minim OSD and newest software Rush_KV_2_1

kataventos · Post by **kataventos** » Sat Feb 09, 2013 12:11 pm

Hi,

you will not be able to have the same results you see on that video with MWc 2.1.
As you can see on main ino Created for Multiwii r1240 or higher, you need to update your MW version.

If you have a Minim OSD use this topic instead: viewtopic.php?f=8&t=2918#p28940

Cheers,
KV

kataventos · Post by **kataventos** » Sun Feb 10, 2013 9:03 pm

Hi all,

just had this idea and posted it on MINIMOSD topic, so, posting it here too.

I will send to Liam (that take care of the wiki and documentation) all the information on how to edit properly the entire character map.

This way, everyone who want´s to spend some time around it, and creat new Logo will know what to do, and of course to help us to improve some chars.

Everyone that have a good work on that matter can send me the mcm file, and we will eventually pack it with new releases

Good work to all.

Cheers,
KV

dramida · Post by **dramida** » Mon Feb 11, 2013 7:53 am

Hi, i saw a new OSD with a better Artificial Horizon and Home arrow. http://www.youtube.com/watch?v=PnqsGFCA8mU

How can we get such goodies?

kataventos · Post by **kataventos** » Mon Feb 11, 2013 11:57 am

dramida wrote:Hi, i saw a new OSD with a better Artificial Horizon and Home arrow. http://www.youtube.com/watch?v=PnqsGFCA8mU

How can we get such goodies?

Hi Dramida, I know you saw that Video because when I commented it you received that information!

This "new OSD" software is KV Team next dev without propper information of software source on it.

Like I said before you all need to wait a little more for official, stable and properly tested release, as soon as the entire Team agree that it is ready

But as you know, this software is open source ( that is the thing I like more on this) and you can already use it at your own risc! And please do not ask for detailed instructions, that is being prepared at this moment by the Team member responsable for writing the most complete and understandable tutorials.

Anyway, for the most anxious ones 8-)

here is the how to use it today :mrgreen:

1- Go to the official KV Team repository;
2- Download a zip file;
3- Upload the KV Team software as before;
4- Open GUI pde with Processing / read;
5- "Reset" EEPROM
6- Configure the OSD according your needs;
7- Write to EEPROM / enjoy

Remember work is in progress!

Cheers,
KV

RITON B · Post by **RITON B** » Mon Feb 11, 2013 5:03 pm

Hello
i have the 3d robotic minim osd (pink) to read the battery voltage on the screen do i have to solder the resistances as on the hobby king minomosd or the is an other way
thank you
RITON B

kataventos · Post by **kataventos** » Mon Feb 11, 2013 5:58 pm

RITON B wrote:Hello
i have the 3d robotic minim osd (pink) to read the battery voltage on the screen do i have to solder the resistances as on the hobby king minomosd or the is an other way
thank you
RITON B

See this and use that topic for Minim OSD:

viewtopic.php?f=8&t=2918&p=30950#p30950

KasparsL · Post by **KasparsL** » Mon Feb 11, 2013 6:35 pm

Do I need some other files to run KV_Team_OSD_GUI.pde with Processing? I need controlp5 library for sure, what else?

kataventos · Post by **kataventos** » Mon Feb 11, 2013 6:58 pm

KasparsL wrote:Do I need some other files to run KV_Team_OSD_GUI.pde with Processing? I need controlp5 library for sure, what else?

And the mcm file that is on MAX7456 update folder, copy it to the GUI Data folder.

power67 · Post by **power67** » Tue Feb 12, 2013 3:41 am

When the "Official Release" that contains the GUI is published, it will also contain an application of the GUI, much like what you are used to with mwconfig. This will be much easier to use then having to install processing and all the Dependant libraries.

kataventos · Post by **kataventos** » Tue Feb 12, 2013 12:48 pm

power67 wrote:When the "Official Release" that contains the GUI is published, it will also contain an application of the GUI, much like what you are used to with mwconfig. This will be much easier to use then having to install processing and all the Dependant libraries.

Of course Ross, forgot to say that!

The process posted before is for the most anxious ones that know what they are dealing with at this moment!
Do not expect it to work for everybody in every OS, and we will not give detailed instructions at this time like I said before!

kataventos · Post by **kataventos** » Wed Feb 13, 2013 8:11 pm

Hi all,

please check this link, you are welcome to participate!

https://groups.google.com/forum/?fromgr ... v-team-osd

Cheers,
KV

kataventos · Post by **kataventos** » Sat Feb 16, 2013 10:24 am

Hi all Rushduino users,

please follow this link: viewtopic.php?f=8&t=2918&start=160#p31153

Cheers,
KV

kataventos · Post by **kataventos** » Sat Feb 16, 2013 3:59 pm

Hi all,

If you would like to give us the pleasure to try our work :arrow:

http://www.kvteamosd.com

Have fun!

1- upload the new Char map like before (do not use the one on GUI for now);
2- upload the Team dev (look at config.h, still are a few options left);
3- open GUI and your port, make a RESET;
4- configure it according your needs and save;
5- close port, done.

The Wiki already have crucial information about the GUI, to make possible for you to understand what to do once you´r there!

copterrichie · Post by **copterrichie** » Sat Feb 16, 2013 6:47 pm

Outstanding Work, Great Job.

kataventos · Post by **kataventos** » Wed Feb 20, 2013 3:34 pm

Hi all,

this may help http://www.youtube.com/watch?v=egStpPl9 ... e=youtu.be thanks for watching!

Cheers,
KV

soko · Post by **soko** » Sat Feb 23, 2013 2:16 am

Hi all!

I am new to this interesting forum and I have a basic question.

I have successfully updated my software Minimosd with KV Team and works well.

But I have doubts about how I should connect the three components that make up my FPV system, GPS, Crius se and minimOSD.

I have this GPS and I do not know if it is compatible:

http://www.ebay.es/itm/Very-Small-MT3339-PA6C-GPS-multiwii-multirotor-arduino-flight-controller-/271079582518?pt=FR_YO_MaisonJardin_Bricolage_ElectroniqueComposants&hash=item3f1d9a2b36

Greetings and thanks.