Rushduino OSD - Multiwii based open software osd

[fr3d]

Hi kataventos,

thats the result with the unchanged MTK version:



Jan

I get same thing when I unpowered my camera. It was 5v on vcam rather than 12v can you check your video voltage on camera-vcam and trans-vtx ?

[kataventos]

OK here is a field test regarding my last changes to the code.

MW r1240 PH test and OSD accuracy info using Rushduino MKT1.0 (not uploaded yet, need to clean the code because it was a mess)
After I coded new Rushduino soft for Alt and Vario I decided to continue working on this software as much as I can keeping it working with new releases of MWC.
These Alt and Vario values are as much as possible close to real, always depending on MW info regarding barometric sensor/others to come (sonar, optical flow, etc).
This dev I used (r1240) is one of the last, with the altitude coded by Mahowick, excellent coder/incredible job.

In this test, I made a close to ground (5m Alt Max) PH for +- 5 minutes to test behavior of MW and to see if after the flight the ground would still be = to zero Small difference inferior to one meter was what I experienced, pretty amazing though.

On Vario you will not see any number because the altitude changes were very smooth so, no m/sec, although you´re able to see ascending and descending arrows (notice the drone shadow).

The consumed current that you see is my implementation using MW POWERMETER. You can see a big number on it on the beginning of the video because before this flight (for the video) I was flying a bunch without change batteries. This value is exactly the same shown on GUI and is not correct (yet) must be tuned on MW config.h #define PLEVELSCALE (50) with lots of patience according your setup, exactly as explained on the wiki.
In my next release of this OSD soft you will be able to define on config.h if you want to use POWERMETER_SOFT/HARD or a current sensor connected to your Rushduino (this is the best option) this way you will be able to see both amperage and consumed current much more accurate.

Regarding the GPS, I personally don´t like to see coordinates on screen (just a bunch of numbers lol). It is useful in case of an accident far way to find the drone (if you record your flights on the ground and if ou have a hand GPS to follow it ) This is something I almost never do because I record on board and for that propose I have exactly the same GPS info on my Turnigy 9X with ER9X.
I think that I´m going to put sea level relative altitude permanently on the right top of the screen under GPS velocity because it´s good to know in every flight for statistics on drone behaviour/"real" altitude.

Any questions you know what to do
Stay tuned and subsribe.

Cheers,
KV

http://youtu.be/T8ForeC7eLo

[Benzel]

Hi Kataventos,

Got most of the things working with your latest version and it is a lot faster !
But i have some trouble with the voltage messurment, I am messuring the 12 volt video voltage on Port 0, but all messurements will give me a value of 1023.
With the old rusduino software the voltage was correct.
Do you messure the voltage with the OSD or are you using the VBAT data form multiwii?

[carlonb]

OK here is a field test regarding my last changes to the code.
....
.....

Hi Kataventos,
I'm still waiting for minimosd clone board and I can't wait to test it.
Thanks for great job (thank also to modelci).
I saw your last video and all run well, but I've some detail I want discuss.

Speed: I saw very high (too much) speed related to what I can see in video looking at ground when copter moves.

Vario: I don't understand the black arrows and single/double/triple white arrow activation even if OSD show zero mt/sec. I think one arrow low vario, 2 arrows medium vario, 3 arrows very high vario rate.

All numeric info: Thats aren't left justified, always are jumping right/left if the number of digits changes.

Do you think it's possible do some corrections ?
Anyway, as soon as I receive my minimosd I can partecipate to develop this awesome OSD

Thanks and Bye
carlo

[kataventos]

Hi Kataventos,

Got most of the things working with your latest version and it is a lot faster !
But i have some trouble with the voltage messurment, I am messuring the 12 volt video voltage on Port 0, but all messurements will give me a value of 1023.
With the old rusduino software the voltage was correct.
Do you messure the voltage with the OSD or are you using the VBAT data form multiwii?

What version are you talking about, so I can take a look?

1-No, VBat is not used to display voltage.

2-For Main voltage you´l have to find your match, configure it on config.h:

Code: Select all

#define DIVIDERRATIO 25           // R1/R2 of voltagePin.

For Cam voltage I need to look at the code, maybe separate them allowing to use different batts ex:.(1s or 2s for video depending on your VTX and 3s for main or whatever)

[kataventos]

OK here is a field test regarding my last changes to the code.
....
.....

Hi Kataventos,
I'm still waiting for minimosd clone board and I can't wait to test it.
Thanks for great job (thank also to modelci).
I saw your last video and all run well, but I've some detail I want discuss.

Speed: I saw very high (too much) speed related to what I can see in video looking at ground when copter moves.

Vario: I don't understand the black arrows and single/double/triple white arrow activation even if OSD show zero mt/sec. I think one arrow low vario, 2 arrows medium vario, 3 arrows very high vario rate.

All numeric info: Thats aren't left justified, always are jumping right/left if the number of digits changes.

Do you think it's possible do some corrections ?
Anyway, as soon as I receive my minimosd I can partecipate to develop this awesome OSD

Thanks and Bye
carlo

Modelci is working on Minim not me but I´m sure we can implement same stuff.

1- Speed- It´s given by MWC and is average speed from GPS not the real drone speed ( I can try to use some sort of filter for that I will take a look...)
2-Vario - the arrows ascending/descending are very sensitive. When you move "slowly" they can go to 3 white depending on how slow. when you see 3 black arrows you´r almost at 1m/sec then if you raise your speed you´l be seeing 2,3,4, etc m/sec that´s when you are going to start calculations (m/sec to km/h) and consequently making the necessary arrangements to buy faster motors
3- Numeric info... Near the litlle house you have distance from home, the remaining scary info it´s the GPS coordinates. I have explained that on the video post. (you can disable that on OSD config (NOT ON THE SOFTWARE on your googles)

EDIT: 1m/ Sec = to 3,61 Km/h

[carlonb]

Modelci is working on Minim not me but I´m sure we can implement same stuff.
1- Speed- It´s given by MWC and is average speed from GPS not the real drone speed ( I can try to use some sort of filter for that I will take a look...)
2-Vario - the arrows ascending/descending are very sensitive. When you move "slowly" they can go to 3 white depending on how slow. when you see 3 black arrows you´r almost at 1m/sec then if you raise your speed you´l be seeing 2,3,4, etc m/sec that´s when you are going to start calculations (m/sec to km/h) and consequently making the necessary arrangements to buy faster motors
3- Numeric info... are you talking about GPS coordinates? I have explained that on the video post. (you can disable that on OSD config (NOT ON THE SOFTWARE on your googles)

Thanks for reply,
Yes I know Modelci is working on this, you too.

1- Speed: Yes I know the speed is real speed calculated with GPS coordinates from MWii, I'm now using mobidrone OSD and speed in Km/h is perfect, in your video seems too hight.
2-OK
3- Numeric info: No, I'm talking about speed, the speed data is jumping left and right if the speed is one or two digits (8 km/h...12Km/h...9Km/h).

Carlo

[carlonb]

Modelci is working on Minim not me but I´m sure we can implement same stuff.
1- Speed- It´s given by MWC and is average speed from GPS not the real drone speed ( I can try to use some sort of filter for that I will take a look...)
2-Vario - the arrows ascending/descending are very sensitive. When you move "slowly" they can go to 3 white depending on how slow. when you see 3 black arrows you´r almost at 1m/sec then if you raise your speed you´l be seeing 2,3,4, etc m/sec that´s when you are going to start calculations (m/sec to km/h) and consequently making the necessary arrangements to buy faster motors
3- Numeric info... are you talking about GPS coordinates? I have explained that on the video post. (you can disable that on OSD config (NOT ON THE SOFTWARE on your googles)

Thanks for reply,
Yes I know Modelci is working on this, you too.

1- Speed: Yes I know the speed is real speed calculated with GPS coordinates from MWii, I'm now using mobidrone OSD and speed in Km/h is perfect, in your video seems too hight.
2-OK
3- Numeric info: No, I'm talking about speed, the speed data is jumping left and right if the speed is one or two digits (8 km/h...12Km/h...9Km/h).

Carlo

ummm...

about the very high speed, may be now are printed on oSD as is from Mwii serial protocol ?
May be is in cm/sec ? Try to divide the speed from MWii by 27,8 (cm/sec ---> Km/h)
???
Carlo

[kataventos]

Try to divide the speed from MWii by 27,8 (cm/sec ---> Km/h)
???
Carlo

That´s exactly what I was doing when saw this post!

[Benzel]

Hi Kataventos,

Got most of the things working with your latest version and it is a lot faster !
But i have some trouble with the voltage messurment, I am messuring the 12 volt video voltage on Port 0, but all messurements will give me a value of 1023.
With the old rusduino software the voltage was correct.
Do you messure the voltage with the OSD or are you using the VBAT data form multiwii?

What version are you talking about, so I can take a look?

1-No, VBat is not used to display voltage.

2-For Main voltage you´l have to find your match, configure it on config.h:

Code: Select all

#define DIVIDERRATIO 25           // R1/R2 of voltagePin.

For Cam voltage I need to look at the code, maybe separate them allowing to use different batts ex:.(1s or 2s for video depending on your VTX and 3s for main or whatever)

Thanks for your reply,

I understand the Dividerratio setting to finetune the actual voltage, the problem is that port 0 is now always showing a value of 1023.
We are using Multiwii dev1240 on a modified minimosd, we rerouted the hardwarepins so that it's basicly the same as the origional Rusduino board.

On Port 0 we measure the video transmitter voltage, about 10-11 volt with the normal resistors in place, on the V9 Rusduino version this was working OK.
I looked at the differences between V9 and Modelci version but i am not a programmer .

[kataventos]

Hi Kataventos,

Got most of the things working with your latest version and it is a lot faster !
But i have some trouble with the voltage messurment, I am messuring the 12 volt video voltage on Port 0, but all messurements will give me a value of 1023.
With the old rusduino software the voltage was correct.
Do you messure the voltage with the OSD or are you using the VBAT data form multiwii?

What version are you talking about, so I can take a look?

1-No, VBat is not used to display voltage.

2-For Main voltage you´l have to find your match, configure it on config.h:

Code: Select all

#define DIVIDERRATIO 25           // R1/R2 of voltagePin.

For Cam voltage I need to look at the code, maybe separate them allowing to use different batts ex:.(1s or 2s for video depending on your VTX and 3s for main or whatever)

Thanks for your reply,

I understand the Dividerratio setting to finetune the actual voltage, the problem is that port 0 is now always showing a value of 1023.
We are using Multiwii dev1240 on a modified minimosd, we rerouted the hardwarepins so that it's basicly the same as the origional Rusduino board.

On Port 0 we measure the video transmitter voltage, about 10-11 volt with the normal resistors in place, on the V9 Rusduino version this was working OK.
I looked at the differences between V9 and Modelci version but i am not a programmer .

OK, I will take a look at that as soon as I get GPS with correct speed readings.
First thing first, by the way... I´m no coder either !

Code: Select all

 // Process AI
  temperature=(analogRead(temperaturePin)*1.1)/10.23;  
  voltage=(analogRead(voltagePin)*1.1*DIVIDERRATIO)/102.3; 
  rssiADC = (analogRead(rssiPin)*1.1)/1023;
  amperage = (analogRead(amperagePin)*1.1)/10.23;
///////////////////////////////////////////////
aa =  analogRead(rssiPin)/4; 

These are the actual analogue pin´s defined.

Code: Select all

const uint8_t voltagePin=0;
const uint8_t amperagePin=1;
const uint8_t temperaturePin=6;   // Temperature pin 6 for original Rushduino Board
const uint8_t rssiPin=3;
const uint8_t rssiSample=30;
const uint8_t lowrssiAlarm=75;    // This will make blink the Rssi if lower then this value

EDIT: Are you running without problems MTK on a MINIMOSD?

[kataventos]

GPS speed now = to GUI values!

If you pay attention, when you are stopped with +- stable reception (tested with between 6 and 8 Sat´s inside my garage) the GUI show´s you values between 0 and 30km/h. the Rushduino now is equally wrong because we are stopped. I think that this is normal because I tested CRIUS GPS CN6 with Ucenter on my car and the speed starts to flow correct once you are really moving.

[kataventos]

Here is the code, enjoy.

http://code.google.com/p/rush-osd-development/downloads/detail?name=Rush_KV_0_1.zip&can=2&q=

[carlonb]

GPS speed now = to GUI values!

If you pay attention, when you are stopped with +- stable reception (tested with between 6 and 8 Sat´s inside my garage) the GUI show´s you values between 0 and 30km/h. the Rushduino now is equally wrong because we are stopped. I think that this is normal because I tested CRIUS GPS CN6 with Ucenter on my car and the speed starts to flow correct once you are really moving.

Strange that with copter stopped the gps reception change the coordinates, the coord must be stable, so the calculated speed=0.
In GUI and in my mobidrone OSD, if copter is stopped with 8 sats, the speed is stable=0 km/h.

[kataventos]

Strange that with copter stopped the gps reception change the coordinates, the coord must be stable, so the calculated speed=0.
In GUI and in my mobidrone OSD, if copter is stopped with 8 sats, the speed is stable=0 km/h.

Yes, you are correct... The only good thing on this is that the stuff I coded is finally accurate, see for your self.
I have my OSD on SERIAL1 so, I´m able to see in gui at the same time and they are exactly the same but with different refresh rates (OSD is slower refreshing) that is something that I´m going to look next.


So... an out of topic question what did I missed? 115200Baud 10hz for both... 0+1 output... do you have the same GPS as I? (CRIUS CN06 with EEPROM)

[carlonb]

So... an out of topic question what did I missed? 115200Baud 10hz for both... 0+1 output... do you have the same GPS as I? (CRIUS CN06 with EEPROM)

I have Flytron MTK3329 serial GPS set at 115200baud 10Hz connected on ATMega on serial 1.

??? So... an out of topic question what did I missed? 115200Baud 10hz for both... 0+1 output... ???? Sorry I don't understand this statement


Regarding the other stuff you managed...very well done !!!

I can't wait for my minimosd

Bye

[copterrichie]

Hey, not trying to undercut the outstanding product here but I am very curious if this MiniOSD will work with the Fushduino firmware?

http://dx.com/p/minimosd-ardupilot-mega ... col-149351

[vpb]

And this one two (maybe the same)? http://www.goodluckbuy.com/on-screen-di ... apm-2.html

I think we must wait for modelci , Kataventos is working on original rushduino board

I'm glad, developments continues with the highly assistances.
This is last and final for Rushduino board. Then only will continue for Minim-osd. Because, I need to empty place for new improvements in the flash.
http://osd-max7456-multiwii.googlecode.com/files/osd_max7456_multiwii_V1_2_alfa5.zip

viewtopic.php?f=8&t=922&start=540#p27005

[carlonb]

Hey, not trying to undercut the outstanding product here but I am very curious if this MiniOSD will work with the Fushduino firmware?

http://dx.com/p/minimosd-ardupilot-mega ... col-149351

As soon as I receive minimosd clone I will try.
Here in this German forum these guys are working on monimosd with rushduino/modelci firmware.
http://fpv-community.de/showthread.php?10404-Minim-OSD-und-MultiWii
I used google for translation
Carlo

[copterrichie]

Awesome, seems to me that Rushduino is about to go viral.

[carlonb]

@ kataventos

I looked at your sketch rush_kv_01 and I saw this part of code displaying the GPS speed:

Code: Select all

void displaySpeed(void)
{
  if(!GPS_fix){
    GPS_speed = 0;
  } 
  //if(GPS_speed > speedMAX) speedMAX = GPS_speed;
  itoa(GPS_speed,screenBuffer,10);     
  FindNull();   // find the NULL
  if(unitSystem)  GPS_speed = GPS_speed / 27.8;        // 27.8 (cm/sec ---> Km/h)
  screenBuffer[xx++]=speedUnitAdd[unitSystem];    
  screenBuffer[xx]=0;                   // Restore the NULL
  MAX7456_WriteString(screenBuffer,speedPosition[videoSignalType][screenType]);
}

Seems you convert cm/sec--->Km/h dividing by 27.8 after asci conversion with itoa(....)
I think must be:

//if(GPS_speed > speedMAX) speedMAX = GPS_speed;
if(unitSystem) GPS_speed = GPS_speed / 27.8; // 27.8 (cm/sec ---> Km/h)
itoa(GPS_speed,screenBuffer,10);
FindNull(); // find the NULL
screenBuffer[xx++]=speedUnitAdd[unitSystem];
screenBuffer[xx]=0; // Restore the NULL
MAX7456_WriteString(screenBuffer,speedPosition[videoSignalType][screenType]);

Correct me if I'm wrong.
Bye

[shikra]

Hey, not trying to undercut the outstanding product here but I am very curious if this MiniOSD will work with the Fushduino firmware?

http://dx.com/p/minimosd-ardupilot-mega ... col-149351

I have one of those and can confirm that the recently amended version loads up and displays on the screen now. I haven't tested on a copter with Multiwii - but no reason it wouldn't work.

I bought one to develop my own OSD - but I will probably use Rushduino now its progressing again

Be aware that pins are not broken out onto the pcb - you can only read data via the serial port from multiwii.
With some fine soldering and some resistors, this could be done - so you can get other functions like bat/rssi

[copterrichie]

Hey, not trying to undercut the outstanding product here but I am very curious if this MiniOSD will work with the Fushduino firmware?

http://dx.com/p/minimosd-ardupilot-mega ... col-149351

I have one of those and can confirm that the recently amended version loads up and displays on the screen now. I haven't tested on a copter with Multiwii - but no reason it wouldn't work.

I bought one to develop my own OSD - but I will probably use Rushduino now its progressing again

Be aware that pins are not broken out onto the pcb - you can only read data via the serial port from multiwii.
With some fine soldering and some resistors, this could be done - so you can get other functions like bat/rssi

Interesting and thanks for the feed back. As for the RSSI and current, I would love to see these read by the MWC as it does now with the voltage. Thanks again, not that I was in the market for this device, I was just curious.

[kataventos]

@ kataventos

I looked at your sketch rush_kv_01 and I saw this part of code displaying the GPS speed:

Code: Select all

void displaySpeed(void)
{
  if(!GPS_fix){
    GPS_speed = 0;
  } 
  //if(GPS_speed > speedMAX) speedMAX = GPS_speed;
  itoa(GPS_speed,screenBuffer,10);     
  FindNull();   // find the NULL
  if(unitSystem)  GPS_speed = GPS_speed / 27.8;        // 27.8 (cm/sec ---> Km/h)
  screenBuffer[xx++]=speedUnitAdd[unitSystem];    
  screenBuffer[xx]=0;                   // Restore the NULL
  MAX7456_WriteString(screenBuffer,speedPosition[videoSignalType][screenType]);
}

Seems you convert cm/sec--->Km/h dividing by 27.8 after asci conversion with itoa(....)
I think must be:

//if(GPS_speed > speedMAX) speedMAX = GPS_speed;
if(unitSystem) GPS_speed = GPS_speed / 27.8; // 27.8 (cm/sec ---> Km/h)
itoa(GPS_speed,screenBuffer,10);
FindNull(); // find the NULL
screenBuffer[xx++]=speedUnitAdd[unitSystem];
screenBuffer[xx]=0; // Restore the NULL
MAX7456_WriteString(screenBuffer,speedPosition[videoSignalType][screenType]);

Correct me if I'm wrong.
Bye

Yes, that´s what happens when you want to go for it in bad time but not the only problem here.
The formula needs to be diferent because the number you have from MW is in cm, when you read in GUI 28 is actually 28cm/sec = 0.028km/h so I need to take a look into that again!
I think that we have to use before point and after point but I need some time.

EDIT: If anyone could help on this!

EDIT: I found this for trip: ((0*1000)/3600)*0.01

[kataventos]

I have one of those and can confirm that the recently amended version loads up and displays on the screen now. I haven't tested on a copter with Multiwii - but no reason it wouldn't work.

I bought one to develop my own OSD - but I will probably use Rushduino now its progressing again

What dev are you talking, and which hardware did you use? Thanks.

PS: please confirm POWERMETER readings according your setup, can you get it working? I can confirm equal readings in GUI and OSD but still not accurate.
I think that in future we can have good readings if some more time is dedicated to this matter.
This for example is another interesting Idea :http://www.multiwii.com/forum/viewtopic.php?f=7&t=2769#p27002

[kataventos]

As for the RSSI and current, I would love to see these read by the MWC as it does now with the voltage.

I implemented VBAT and POWEMETER 1/2 done.
I will need to flash my D8RII to have PWMSum. Aftter that we need to wait for MWc implementation!

[shikra]

Clone minimosd i bought off ebay real cheap. Think it was less than $20!

osd_max7456_multiwii_V1_2_alfa5
But I didn't fly - just had the chars on screen. I haven't opprtunity to do much else at the moment because of work...

For me actually I don't really use OSD much on a copter. I only want volts and a fly timer!! But I'll take whatever you guys deliver!
What I really wanted is some debug info which is why minim appealed. Quick and easy compared to my mobidrone.

[carlonb]

.......
Yes, that´s what happens when you want to go for it in bad time but not the only problem here.
The formula needs to be diferent because the number you have from MW is in cm, when you read in GUI 28 is actually 28cm/sec = 0.028km/h so I need to take a look into that again!
I think that we have to use before point and after point but I need some time.
.....

I know, when we want do the things quickly, the error is behind the corner
I hope not boring you but as said I'm waiting my miniosd and I can't test it.
When in GUI we have 28 I have not investigate if that means 28 cm/sec, anyway 28cm/sec is not equal to 0,028Km/h.
If we have 28cm/sec to convert in Km/h:
28*60*60=100800 cm/h
100800/100=1008 mt/h
1008/1000=1.008 Km/h

So, 60*60/100/1000=0.036
Then 28*0.036=1.008 Km/h. This means that if we multiply the value received from MWii by 0.036 we have the speed in Km/h.

Or...1/0.036=27.77777=27.8 rounded
Then it's the same if we divide 28/27.777=1.008

Please verify this.
Bye, Carlo

[kataventos]

yes, yes, you are so right, I forgot hours... Thanks.

Anyway, it´s 5:00Am and I saw your message around 1:00Am, got so embarrassed with my mathematics that I did not stopped until I get it working.

Yes, it´s working perfectly!

I will upload KV_ 1.0 tomorrow.

With this dev, I can say that my work is done for now. All works as it should
Cheers,
KV

PS: Take a look at the old GPS c and compare it with the new one!

[kataventos]

Hi to all,

Here is KV_1.0
http://code.google.com/p/rush-osd-development/downloads/detail?name=Rush_KV_1_0.zip&can=2&q=
If you find any bug, fix it

1- Final implementation of Powermeter and Vbat;
2- Altitude and Vario debuged;
3- GPS_Speed debugged;
4- Statistics debugged;
5- New options on config.h

I promised my wife that when I got it all working I would sleep, so... all done.
Hope Rushduino users like it as much as I.

Cheers,
KV

[vpb]

I still cannot find max7456 here to build rushduino board, hunger to try it but I need to wait the chips to arrive

[carlonb]

Hi to all,

Here is KV_1.0
http://code.google.com/p/rush-osd-development/downloads/detail?name=Rush_KV_1_0.zip&can=2&q=
If you find any bug, fix it

1- Final implementation of Powermeter and Vbat;
2- Altitude and Vario debuged;
3- GPS_Speed debugged;
4- Statistics debugged;
5- New options on config.h

I promised my wife that when I got it all working I would sleep, so... all done.
Hope Rushduino users like it as much as I.

Cheers,
KV

Thanks so much for your effort
I can't wait for my clone minimosd!!!
I will let you my news as soon as possible.
Carlo

[RITON B]

Hello mister kataventos
The last firm KV.1.0 seems to be OK thank you very much The only thing that is not OK is "when i armed the motors on the screen Disarmed don't change to armed and the timer stray to 0" why????
thank you for yur replay
RITON B

[kataventos]

Thanks so much for your effort
I can't wait for my clone minimosd!!!
I will let you my news as soon as possible.
Carlo[/quote]

It´s nothing but a pleasure to me if everybody get it working like I have it now!
I just hope that you get it working with MINIMOsd, I think it is easy to remap it, I will buy one just to see what´s going on with that! I think that Shikra is correct, few micro soldering with some resistors and capacitors and you have al Rush. Let´s wait until you get it.

Cheers,
KV

[kataventos]

Hello mister kataventos
The last firm KV.1.0 seems to be OK thank you very much The only thing that is not OK is "when i armed the motors on the screen Disarmed don't change to armed and the timer stray to 0" why????
thank you for yur replay
RITON B

Thank you and welcome, I think that you are not with dev r1240! if not, tell me what dev do you have. It´s simple to fix. If you have everything else working, the problem is in mode active.

[copterrichie]

You guys should get together on this project: http://www.rcgroups.com/forums/showthread.php?t=1776186

I believe everyone would benefit.

[RITON B]

Hello mister K
I have r1240 all is OK except no motors on and the timer
here it is 11 pm bye
RITON B

[vpb]

You guys should get together on this project: http://www.rcgroups.com/forums/showthread.php?t=1776186

I believe everyone would benefit.

It's standalone osd (with dedicated gps...), I still like the way rushduino gets data directly from multiwii here .

Dennis Frie on rcgroups also has a DIY head-tracker project with less than 30$ hardwares http://www.rcgroups.com/forums/showthread.php?t=1677559

[copterrichie]

It's standalone osd (with dedicated gps...), I still like the way rushduino gets data directly from multiwii here .

Dennis Frie on rcgroups also has a DIY head-tracker project with less than 30$ hardwares http://www.rcgroups.com/forums/showthread.php?t=1677559

Every hear of DEFINE statements? Hmmm LOL

But both firmware versions would use the same hardware.

[kataventos]

Hello mister K
I have r1240 all is OK except no motors on and the timer
here it is 11 pm bye
RITON B

Sorry, but I do not experience that issue with the same dev! I don´t know...

[kataventos]

Sorry, forgot something on the Uploaded file and I deleted it.
Here is the new link for Rush_KV_1.0:


http://code.google.com/p/rush-osd-development/downloads/detail?name=Rush_KV_1_0_1.zip&can=2&q=#makechanges


Cheers,
KV

[kataventos]

Hello mister K
I have r1240 all is OK except no motors on and the timer
RITON B

Hi RITON B, your problem is definitely on mode active.

Please change according your MWc on config.h:

Code: Select all

#define STABLEMODE     1    // OK
#define BAROMODE       4    // OK
#define MAGMODE        8    // OK
//#define BOXCAMSTAB     16   // not used
//#define BOXCAMTRIG     256  // not used
#define ARMEDMODE      32   // OK
#define GPSHOMEMODE    64   // OK
#define GPSHOLDMODE    128  // OK

Where you see #define ARMEDMODE 32 use 16 for example. IF everything ELSE works as expected try the missing one like 256. ( you to test Aux channels and see if they mach)

I do not experience this like I said before, but I have one configuration on multiwii that could be diferent then your´s.
I did not look into that MWc, but please for the record, tell me what sensors, board etc you have working with your Rush.
With that I will find you the answer.

[RITON B]

Hello mr K
I will try your modifications to morrow.
my board is 'AMOURDURISK' board (french board ) Amourdurisk is a member of"MIKROKOPTER.fr"
ITG 3200
BMA 180
BMP 085
HMC 58983
à demain.
RITON B

[kataventos]

Hello mr K
I will try your modifications to morrow.
my board is 'AMOURDURISK' board (french board ) Amourdurisk is a member of"MIKROKOPTER.fr"
ITG 3200
BMA 180
BMP 085
HMC 58983
à demain.
RITON B

OK, if you do not have GPS on it try that ones to (one at a time), PH and RH. You will be fine.

PS: forgot to say that when you get the motors on the counter will start obviously !

[itain]

@kataventos
I suggest:

Code: Select all

#define STABLEMODE    ((1 << 0)|(1 << 1))   // HORIZON or ANGLE
#define BAROMODE      (1 << 2)
#define MAGMODE       (1 << 3)
...

1. it would show STABLE both for HORIZON and ANGLE modes (as there is no separate graphics).
2. Using (1 << XX) may be easier than calculating powers of 2.

Ultimately there should be a way to receive the correct bit assignment from MultiWii.

[RITON B]

Hello Mr K
good news,ARMEDMODE at 20 = on the screen "ARMED" and the timer start.
Thank you
next challenge :the GPS
bye
RITON B

[kataventos]

Hello Mr K
good news,ARMEDMODE at 20 = on the screen "ARMED" and the timer start.
Thank you
next challenge :the GPS
bye
RITON B

thank you, it´s good to know that you get it working.
Wish you great FPV flights, don´t go to far

[kataventos]

@kataventos
I suggest:

Code: Select all

#define STABLEMODE    ((1 << 0)|(1 << 1))   // HORIZON or ANGLE
#define BAROMODE      (1 << 2)
#define MAGMODE       (1 << 3)
...

1. it would show STABLE both for HORIZON and ANGLE modes (as there is no separate graphics).
2. Using (1 << XX) may be easier than calculating powers of 2.

Ultimately there should be a way to receive the correct bit assignment from MultiWii.

Yes thanks you are right, but this issue makes everybody think, and trying a little bit of the experience of someone who write and test the code.
One year ago I could not done this
Now, I´m working mostly on getting all the screen data perfect, principally the statistics, they were a mess, the best way I found was to create some defines that adjust most necessary things for every kind of setup.
For example statistics are perfect, every values now are real except trip (I´m on that now).
About the new defines, I wanted to comment the most so that everyone could understand and use them correctly.

For example:
I am using Powermeter and I should say that is amazing, after fine tuning it I made 3x10min flights with an error of between 50 and 100mah

Take a look

Code: Select all

                                      /**********************************************************************************/
                                       /*    RUSH KV 1.1               Configurable parameters        RUSH KV 1.1 */
                                        /**********************************************************************************/

// ____________________________________________________________________General configuration________________________________________________________________________//

#define VideoSignalType_PAL
const char videoSignalType=1;
//#define VideoSignalType_NTSC
//const char videoSignalType=0;

/**********************       Serial speed      ************************/

#define SERIAL_SPEED 115200 

/*******************************************      Mode Active (you MUST define according your MWC options)      *****************************/

#define STABLEMODE     1            // OK
#define BAROMODE       4            // OK
#define MAGMODE        8            // OK
//#define BOXCAMSTAB     16         // not used
#define ARMEDMODE      32           // OK
#define GPSHOMEMODE    64           // OK
#define GPSHOLDMODE    128          // OK
//#define BOXCAMTRIG     256        // not used

/**********    Here you can define time out for Mag calibration and EEProm write (mostly useful for mag calibration)    ***********/

#define CALIBRATION_DELAY 10
#define EEPROM_WRITE_DELAY 5

/***************************************        Voltage and Amperage        ********************************************/
 /*                                                                                                                     */
  /**************** Voltage match multimeter (you can change this options to match your requirements) ********************/
                             
#define DIVIDERRATIO 25             // Main voltagePin ratio 
//#define VBAT                      // Uncomment to change from Analog Pin to MwVbat (must define it on MWcode)

#define EST_PMSum 2.6                 /****  NOTE  **** If you use hardware CURRENT sensor on OSD use (#define EST_PMSum 1) BEFORE ANY ADJUSTMENT OR CALIBRATION 
                                                      this value is empirical and you can find "yours" after some flights using the same instructions as for VBAT adjustment
                                                      on Mwc (first you have to MWC fine tune your voltage (VBat))                                                            ****/

//#define HARDSENSOR                // Uncomment to change from MW_POWERMETER to Hard current sensor on analogue Pin (MW_POWERMETER is DEFAULT and must be defined on MWCode)
#define AMPDIVISION 3600               // DO NOT UNCOMMENT. If you use hardware current sensor define ( 3600 ) as division ratio
#define AMPERAGE_CAL 1.1            // Amperage calibration
#define AMPRERAGE_OFFSET 512        // Amperage = AMPRERAGE_OFFSET - analogRead * AMPERAGE_CAL / 10.23


/*****************************      Climb rate adjust      **********************************/

#define ESTCLIMB 60                 // Here you can adjust Climb rate (60 is empirical value and it was the best I could find) 

/**********************************         Display Settings         ************************/

#define DISPLAY_HORIZON_BR
#define DISPLAY_GPSPOSITION
//#define COORDINATES               // Uncomment to display coordinates (use with display GPS ON, on OSD page 3)
#define WITHDECORATION
#define SHOWHEADING
#define SHOWBATLEVELEVOLUTION

/********************       For Sensors presence      *********************/
 
#define ACCELEROMETER  1//0b00000001
#define BAROMETER      2//0b00000010  
#define MAGNETOMETER   4//0b00000100  
#define GPSSENSOR      8//0b00001000
//#define SONAR         16//0b00010000

/*********************      Led output      *******************************/

#define BST 7 // pin 7 for original Rushduino Board
#define BST_OFF digitalWrite(BST,LOW);
#define BST_ON digitalWrite(BST,HIGH);


/********************      Analog input defines     ***********************/

const uint8_t voltagePin=0;
const uint8_t amperagePin=1;
const uint8_t rssiPin=3;
const uint8_t temperaturePin=6;    // Temperature pin 6 for original Rushduino Board
const uint8_t rssiSample=30;
const uint8_t lowrssiAlarm=75;     // This will make blink the Rssi if lower then this value



/*----------------------------------------------       End of configurable parameters      ----------------------------------------------------*/

[vpb]

It's standalone osd (with dedicated gps...), I still like the way rushduino gets data directly from multiwii here .

Dennis Frie on rcgroups also has a DIY head-tracker project with less than 30$ hardwares http://www.rcgroups.com/forums/showthread.php?t=1677559

Every hear of DEFINE statements? Hmmm LOL

But both firmware versions would use the same hardware.

Dont talk like that man, I'm a developer for more than 15 years, and dont try to mis-understand what other means . I didn't say that osd wont work here or wont work with different sensor-components, it's how the main-board communicates with those components. You see rushduino here do that via multiwii-core, not directly.

But I just bookmark that topic as a "DIY cheap osd",still not dig into, and do I miss something such as "support multiwii, just plug in and type some DEFINE statement somewhere?"

[staroman]

Hi kataventos,
i think i will give up. I loaded the 2.11 1240 on my FC and your 1.01 in the OSD. It doesnt work. No chance. I see only the horizon. Do you have really an original Rushduino Board V1.2? I dont understand where there a problem is...

Jan