KV Team Multiwii OSD

Batch1 · Post by **Batch1** » Tue Sep 10, 2013 6:43 pm

SkyrimDragon wrote:I know this sounds crazy, but I would start from zero. First, use a different computer. Install arduino. Install the drivers. Try to load the sketch.

The second thing I would do is to use a different FTDI programmer.

If NEITHER of these processes work, then the only remaining explanation is that it is the OSD. Then you can begin chipping away at that problem, probably by reburning the boot loader with a USP ASP programmer. Do you have one?

Start fresh and reduce your variables. It doesn't sound like you're doing anything wrong. Probably there is a glitch in your workflow.

(Sadly, I think your bootloader is corrupted, though. But deal with it when you get to that step).

I will have to order another FTDI (that time from eBay) and minimOSD and I have a USP ASP programmer.

On another computer, I load MinimOSD Extra Copter on that minimOSD board and using same FTDI and had no problems loading and configuring it

I didn't try to load the KV Team soft. on that computer, will try that.

Thanks

katana · Post by **katana** » Tue Sep 10, 2013 8:00 pm

carlonb wrote:
Point 1) I agree with the previous reply of SkyrimDragon
Point 2) Try to set min and max RSSI received values as discussed here http://www.rcgroups.com/forums/showthread.php?t=1786599&page=30 starting from post n. #438 and next page posts #451 and #452.
Carlo

Point 2) I just did as you suggested, perfect!
for those who have had the same problem:
- make sure that the value of rssi max corresponds to 1.1 Volt or less (use a Voltage divider)
- enter the OSD menu, in one of the last pages you can read the current RSSI value, that value can used for calibration.
- that is all

thank you very much Carlo!

katana · Post by **katana** » Tue Sep 10, 2013 8:08 pm

SkyrimDragon wrote:
What version of the OSD do you have? The jumper mod (5v) used to be recommended because of the power management problems. But those have been fixed and the analog side should be able to handle 12 volts. If it's getting hot, maybe you have an old version.

ALSO, the analog side doesn't NEED 12 volts. It can just USE 12 volts. It will run fine all the way down to 5 volts. So if they are separated, (no mod) you can power the analog side with a lower voltage (like a 2S battery) and it will run cooler.

The other benefit of this is that it will operate as designed and remove line noise and potentially provide a clearer signal.

Hi SkyrimDragon,
thanks for the reply.
i have this version : http://www.hobbyking.com/hobbyking/stor ... _v1_1.html (v1.1) it's ok?
now it works, but it seems to me hot... I will try to use only the 5v of flyduino mega.

SkyrimDragon · Post by **SkyrimDragon** » Tue Sep 10, 2013 8:30 pm

...................................................

SkyrimDragon · Post by **SkyrimDragon** » Wed Sep 11, 2013 5:20 pm

...................................................

katana · Post by **katana** » Thu Sep 12, 2013 10:31 am

SkyrimDragon wrote:
katana wrote:i have this version : http://www.hobbyking.com/hobbyking/stor ... _v1_1.html (v1.1) it's ok?
now it works, but it seems to me hot... I will try to use only the 5v of flyduino mega.

The picture that Hobby King has there indicates that it is A-OK. It appears to have the proper voltage regulator. Do you see the dark round thing near to the six pins on the analog side? On the older 1.0 version--or any version/copy/clone that has heat trouble, the area in the corner around the pins was very empty. It only had a couple of small components. In the fixed 1.1 version (whether 3DRobotics or the jDrones MiniOSD or any other clone), if that corner is populated by a lot of "stuff" it means that they added the proper voltage regulators.

I do highly recommend running that side off of a small 2S battery. They weigh very little, are very small, and will both keep the temperature down and keep the signal noise free. It's a good way to go.

If you're interested in even more redundancy, get a battery to run both the analog side AND the video transmitter. After all, they need a common ground between them anyway. Then even in the worst case scenario of a lost and wrecked model, it will keep broadcasting a signal from the debris field (even if it's a black screen with dead OSD overlay). Because the range while in the weeds is severely reduced, it will tighten up and localize the signal. In theory it could provide you with a secondary way to track it down, even if the main receiver and battery are no longer working. That VTX and OSD will keep going for the life of the battery. Several hours.

This is all off topic, but it's a thought. It would solve your heat issue and do so much more in the process!

Interesting advice, I always tried to have a layout with a single battery, I will think about. thanks again

jphelirc · Post by **jphelirc** » Fri Sep 13, 2013 10:13 am

SkyrimDragon wrote:
katana wrote:i have this version : http://www.hobbyking.com/hobbyking/stor ... _v1_1.html (v1.1) it's ok?
now it works, but it seems to me hot... I will try to use only the 5v of flyduino mega.

The picture that Hobby King has there indicates that it is A-OK. It appears to have the proper voltage regulator. Do you see the dark round thing near to the six pins on the analog side? On the older 1.0 version--or any version/copy/clone that has heat trouble, the area in the corner around the pins was very empty. It only had a couple of small components. In the fixed 1.1 version (whether 3DRobotics or the jDrones MiniOSD or any other clone), if that corner is populated by a lot of "stuff" it means that they added the proper voltage regulators.

Actually it's was Mr.jDrones who released original MiniOSD v1.1 with switching regulator. And it was Mr. jDrones + Mr. Sandro who made original software for it. So I would not call them as clones. Designs are based anyways on our work that Sandro and me made. Now Mr. jDrones made another release of it and it's called v1.2.

kataventos wrote:Mr. JDrones would have to send for free one OSD for each team member/developer if he wants to sell it to the Multiwii user´s if you get my point, we are always open to suggestions... the current hardware fulfill the needs at the moment, and a new dedicated hardware will rise in future...
SkyrimDragon wrote:
kataventos wrote:
This is just for receivers with PWM RSSI because we are using digital pins on this...

KV, no need to be sarcastic.. we are not developing these just because of huge amount of $$$ (which there isn't), we do these because of love to electronics and avionics. Sure we are happy if people want to buy those too. So Mr. jDrones just might send few boards if someone needs them for development. But we are not going to send them to all developers as many times they just end up on collecting dust on someones shelfs. So if there is someone who really want's to develop software on those, I am happy to send few boards to those individuals. Just PM me here or where ever, I think it's easy to find me around net.

And btw. mostlike without Mr.jDrones and few others there would not be even multiwii and many other nice things... Just like OSD, It was us who originally started to create and use Wii based controllers on AeroQuad development team back at early 2010, which is +1 year before multiwii.com was even registered.

Anyways back to v1.2. I just updated few diagrams for it so if someone needs and want's to take a look at those, you can find them from my document site in here http://www.jdrones.com/wiki/jd-miniosd-v1-2-guide

We are going to make one more revision in next few months of it but nothing major changes.

Here are basic digram of it:

And for fun: Early multiwii/wiiquad and aeroquad development boards from early 2010.. Things has changed a lot since then but these should still fly

With best Regards,
Jani aka Mr.jDrones

Fly hard but fly safe...

jphelirc · Post by **jphelirc** » Fri Sep 13, 2013 1:50 pm

OT: I am looking to make several adapter boards for MiniOSD. Adapter boards will allow easier cabling and will have smaller type connectors. Would be great to hear what type cabling you all have been using on your installations. If we can figure several mainstream installation methods, making simple daughterboard for OSD will be easy.

--jp

timecop · Post by **timecop** » Fri Sep 13, 2013 2:38 pm

I'm curious why time + effort was spent to make NEW hardware with MAX7456? It's been FINALLY EOL'd by Maxim.
It's time to fucking move on.

jphelirc · Post by **jphelirc** » Fri Sep 13, 2013 2:52 pm

tc, yeah they EOLed those but those are still on market at least about year or so. There are several works going on already for new hardwares but it will take time before those are done. 7456 just were one great and simple chip to work with.

Batch1 · Post by **Batch1** » Fri Sep 13, 2013 3:08 pm

SkyrimDragon wrote:I know this sounds crazy, but I would start from zero. First, use a different computer. Install arduino. Install the drivers. Try to load the sketch.

The second thing I would do is to use a different FTDI programmer

If NEITHER of these processes work, then the only remaining explanation is that it is the OSD. Then you can begin chipping away at that problem, probably by reburning the boot loader with a USP ASP programmer. Do you have one?

Start fresh and reduce your variables. It doesn't sound like you're doing anything wrong. Probably there is a glitch in your workflow.

(Sadly, I think your bootloader is corrupted, though. But deal with it when you get to that step).

I did what you suggest, on a different computer using same minimosd board and same FTDI

I download a fresh copy of Arduino, KV_TEAM_DEV r370, and I use another USB cable.

I am able now to load the KV_Team r370 on the minimosd and do the configuration with the KV_Team GUI

Thank you very much my friend, you can't imagine how hard I work on that. I never thaught to try on another computer

Thanks again

Robert

SkyrimDragon · Post by **SkyrimDragon** » Fri Sep 13, 2013 3:17 pm

...................................................

shikra · Post by **shikra** » Fri Sep 13, 2013 4:37 pm

Suggestion... in this bit

if(!armed) {
flyTime=0;
}
else {
flyTime++;
flyingTime++;
configMode=0;
setMspRequests();
}

remove flytime=0 totally - or put it into reset statistics?

Personally I like to have the the total flight time whilst battery connected - not resetting it each time I arm. When I'm filming I know I have say 8 mins, but might fly 4 or 5 scenes and stop inbetween with possibly a long wait so don't know the true total fly time. And on time is not usefull with long waits between flights.

SkyrimDragon · Post by **SkyrimDragon** » Fri Sep 13, 2013 11:02 pm

...................................................

kataventos · Post by **kataventos** » Sat Sep 14, 2013 11:59 pm

jphelirc wrote:KV, no need to be sarcastic...

With best Regards,
Jani aka Mr.jDrones
Fly hard but fly safe...

I was not being sarcastic... just calling for some attention here...
We never let our hardware on the shelf, we use and explore it to exhaustion by flying.

PM will be sent.

shikra wrote:Suggestion... in this bit

if(!armed) {
flyTime=0;
}
else {
flyTime++;
flyingTime++;
configMode=0;
setMspRequests();
}

remove flytime=0 totally - or put it into reset statistics?

Personally I like to have the the total flight time whilst battery connected - not resetting it each time I arm. When I'm filming I know I have say 8 mins, but might fly 4 or 5 scenes and stop inbetween with possibly a long wait so don't know the true total fly time. And on time is not usefull with long waits between flights.

Hey Shikra,

Yep that´s a good point, also noted and on the list

SkyrimDragon wrote:Now that we have the official schematics and pinouts on the new MiniOSD 1.2 from jDrones, can someone tell me which analog pin can be used to measure voltage? I believe RSSI is the A3 pin (or MISO)...which is voltage?

Thanks!

Yes we have the schematic :geek:

...
We will develop and publish as soon as we have it in our hands :ugeek:

But, ADC3 (PC3) is an analogue input and MISO (PB4) a digital one (PWM), which kind of signal are you trying to get on screen?

Cheers,
-KV

kataventos · Post by **kataventos** » Sun Sep 15, 2013 12:11 am

SkyrimDragon wrote:...Often with Windows based computers, you must do what doesn't makes sense.

kataventos · Post by **kataventos** » Sun Sep 15, 2013 12:29 am

timecop wrote:I'm curious why time + effort was spent to make NEW hardware with MAX7456? It's been FINALLY EOL'd by Maxim.
It's time to fucking move on.

This is 100% correct.
Anyway, we will keep developing for MAX7456 with our modest OSD until the real "future" telemetry comes. I predict something a lot different as I said before, but that´s just me speaking

until then let´s keep the screen populated with most needed data for Multiwii FPV fun.

-KV

SkyrimDragon · Post by **SkyrimDragon** » Sun Sep 15, 2013 12:47 am

...................................................

carlonb · Post by **carlonb** » Sun Sep 15, 2013 9:55 am

kataventos wrote:Yes we have the schematic ...
We will develop and publish as soon as we have it in our hands

But, ADC3 (PC3) is an analogue input and MISO (PB4) a digital one (PWM), which kind of signal are you trying to get on screen?
-KV

Hi Henrique,
Agree about first point, it's time that someone send to us developers the new hardware to make easy the job. :ugeek:

About PB4 (MISO), are we sure we can use it? MISO is actually communicating with MAX7456 :?:

Bye, Carlo

SkyrimDragon · Post by **SkyrimDragon** » Tue Sep 17, 2013 2:02 am

...................................................

carlonb · Post by **carlonb** » Tue Sep 17, 2013 8:44 am

SkyrimDragon wrote:Now I have confused myself.

I have a FrSky receiver. I believe that has a PWM output for RSSI. So I cannot use the analog input A3? Is there an answer for Carlo on whether MISO actually works? I have a board set up to test it, but Icannot for another few days and wwould rather know for sure before soldering pins and such.

You can use A3 input to read an analogic input or a PWM input.
If you are reading a pure PWM signal (not filtered with an RC nor a resistor devider as per analogic reading) you use A3 pin and modify the Config.h file of OSD sketch as follow:

ORIGINAL
/******************** PWM RSSI *********************/

#define PwmRssiPin 12 // Miso Pin

MOD
/******************** PWM RSSI *********************/

#define PwmRssiPin A3 // A3 analog Pin

after that, in GUI enable PWM reading and disable the ADC reading

Please try as I've not a PWM RX and let me know any news
Cheers

rbirdie001 · Post by **rbirdie001** » Wed Sep 18, 2013 10:37 pm

Hi guys,
I just intalled Minim R370 and connected with MWC R1555. Everything seems to work well, except RSSI readout.
I have configured Multiwi to measure RSSI as analog voltage on the pin A7 and Minim to get RSSI from Multiwii. OSD shows RSSI percentage and it's somehow dependent on voltage at MW pin A7, but I can't set correct range.

My RX gives RSSI as DC voltage 1V at no signal and 1.6V at 100% signal. If I look into OSD menu at page where is RSSI displayed, it says that actual RSSI (at maximum signal) is value 340 and minimum about 210. If I try set these "borders" from GUI, I can't set MAX to 340 but only up to 255. When I try to do this from the OSD config page via stick, I'm unable to set correct value - number doesn't react correctly to stick movement. I move triangel cursor to the correcponding line by PITCH stick (Mode 1) and then try to adjust it by YAW stick, but value almost doesn't change, just sometimes randomly +-1 but I can't reach numbers above 80. At PID settings page everything including values adjustment works just fine.
What is wrong :?:

Thanks for any advice!
Roman

carlonb · Post by **carlonb** » Thu Sep 19, 2013 1:30 pm

Hi rbirdie,
try to set the RSSI min and max as linked here that I suggested in some previous post.

Set min and max RSSI received values as discussed here http://www.rcgroups.com/forums/showthread.php?t=1786599&page=31 in post n. #451 and #452

Carlo

rbirdie001 · Post by **rbirdie001** » Thu Sep 19, 2013 5:30 pm

carlonb wrote:Hi rbirdie,
try to set the RSSI min and max as linked here that I suggested in some previous post.

Set min and max RSSI received values as discussed here http://www.rcgroups.com/forums/showthread.php?t=1786599&page=31 in post n. #451 and #452

Carlo

Thanks Carlo,
I tested this procedure and it works perfectly for MIN value (after 15s countown the actual value 210 is copied to RSSI MIN), but for setting MAX value it sets only 88 or 89 and not more while actual RSSI is ~340! Is there another trick? Why just 88 or 89? Isn't it a problem of variable type?
Thanks for any other ideas!
Roman

carlonb · Post by **carlonb** » Thu Sep 19, 2013 9:31 pm

rbirdie001 wrote:I tested this procedure and it works perfectly for MIN value (after 15s countown the actual value 210 is copied to RSSI MIN), but for setting MAX value it sets only 88 or 89 and not more while actual RSSI is ~340! Is there another trick? Why just 88 or 89? Isn't it a problem of variable type?
Thanks for any other ideas!
Roman

I think understand the issue,
from MWii, the RSSI serial data is two byte long, in OSD we read two byte, but the calcs use one byte only.
R370 dev of KV OSD has a bug, the next dev will be correct, anyway try this workaround doing this mod:

In OSD sketch the KV_team_OSD.ino file at row 165-166 you see:

Code: Select all

if (Settings[S_MWRSSI]) {
      rssiADC = MwRssi;

Modify with:

Code: Select all

if (Settings[S_MWRSSI]) {
      rssiADC = MwRssi/4;

Please verify and let us know.
Cheers
Carlo

rbirdie001 · Post by **rbirdie001** » Thu Sep 19, 2013 10:19 pm

Carlo,
again thanks for prompt support but unfortunately still not work well.
I added /4 to line 166 so now RSSI shows values between 51-86 and adjusting MIN and MAX values works also perfectly, but final RSSI percent value is now ALWAYS 100%. I guess that original undivided value is used somewhere again. Sorry, I'm not programmer so I'm afraid to dig into code.
I'll appreciate if you can look at it once more, I'll immediately test it.
(As I'm more confident in circuit electronic, my emergency solution would be a resistive voltage dividier

)
Thanks!
Roman

carlonb · Post by **carlonb** » Fri Sep 20, 2013 3:40 pm

rbirdie001 wrote:Carlo,
again thanks for prompt support but unfortunately still not work well.
I added /4 to line 166 so now RSSI shows values between 51-86 and adjusting MIN and MAX values works also perfectly, but final RSSI percent value is now ALWAYS 100%. I guess that original undivided value is used somewhere again. Sorry, I'm not programmer so I'm afraid to dig into code.
I'll appreciate if you can look at it once more, I'll immediately test it.
(As I'm more confident in circuit electronic, my emergency solution would be a resistive voltage dividier )
Thanks!
Roman

Hi Roman,
I've tried (simulated) some time ago and to me seems working well....
I've noted that changing the RSSI signal received this take some second ( one or two or tree) to update the screen percent due to calculation of the average of the last 30 received values, so wait a little....
Have you saved the min and max values after min/max setup ?

Bye
Carlo

rbirdie001 · Post by **rbirdie001** » Fri Sep 20, 2013 10:02 pm

carlonb wrote:Hi Roman,
I've tried (simulated) some time ago and to me seems working well....
I've noted that changing the RSSI signal received this take some second ( one or two or tree) to update the screen percent due to calculation of the average of the last 30 received values, so wait a little....
Have you saved the min and max values after min/max setup ?
Bye
Carlo

Carlo,
I tested it once more and I believe I really don't do anything wrong.
I captured two short videos to demonstrate the behaviour. Both are taken with r370 with added "/4" at the line 166.
First video shows RSSI measurement with saved MIN and MAX values and then rebooted. I folded my TX antenna (35MHz radio) and passed behind some walls. You can see that actual RSSI value goes down but the interpreted percentage remains 100%.
http://www.youtube.com/watch?v=-isOHa9uC9c

Second video shows how I did the calibration. After save and exit (at the main page) I again reduced transmitter signal but percentage remained 100%.
http://www.youtube.com/watch?v=ULBooILP2Po
Do you have any ideas?
Thanks!
Roman

carlonb · Post by **carlonb** » Fri Sep 20, 2013 10:41 pm

Hi Roman,
I can not simulate RSSI issue, but I look into code:

At line 406 of KV_Team_OSD.ino file you have

Code: Select all

  else { 
      if (Settings[S_MWRSSI]) {
        aa =  MwRssi;
      }

Please try to mod with

Code: Select all

  else { 
      if (Settings[S_MWRSSI]) {
        aa =  rssiADC;
      }

Ciao
Carlo

rbirdie001 · Post by **rbirdie001** » Sat Sep 21, 2013 3:43 pm

carlonb wrote:Hi Roman,
I can not simulate RSSI issue, but I look into code:

At line 406 of KV_Team_OSD.ino file you have
Code: Select all
  else { 
      if (Settings[S_MWRSSI]) {
        aa =  MwRssi;
      }
Please try to mod with
Code: Select all
  else { 
      if (Settings[S_MWRSSI]) {
        aa =  rssiADC;
      }
Ciao
Carlo

Carlo,
now with both mods it works perfectly!
I think that whole condition on lines 407-412 could be replaced just with aa = rssiADC; but once it works, I don't dare touch it.

Really nice project!
Thanks!
Roman

carlonb · Post by **carlonb** » Sat Sep 21, 2013 4:50 pm

rbirdie001 wrote:now with both mods it works perfectly!
I think that whole condition on lines 407-412 could be replaced just with aa = rssiADC; but once it works, I don't dare touch it.
Really nice project!
Thanks!
Roman

Great to hear you happy,
About the MWii RSSI issue this will be solved in the next release where you can find new nice stuffs. Stay tuned with KV-Team_OSD
Ciao
Carlo

SkyrimDragon · Post by **SkyrimDragon** » Sat Sep 21, 2013 4:53 pm

...................................................

carlonb · Post by **carlonb** » Sat Sep 21, 2013 8:43 pm

SkyrimDragon wrote:Hello Carlo,

Speaking of the next release, I know you can't say exactly, but can you say if it will be in days, weeks, or months?

Hi Skyrimdragon,
I think it's a matter of a few weeks.
The sketch for MinimOSD is almost ready, and Kataventos is working on the GUI (the most 'difficult).
Bye
Carlo

kataventos · Post by **kataventos** » Tue Sep 24, 2013 6:09 pm

I must say that I am crashing with Java on GUI to make the moveable items by dragging them with the mouse...

probably more time needed because this is very hard work for me alone...
We have the OSD sketch almost ready, just little stuff need to be implemented like for example some of the ideas posted here by the users. Other than that the sketch is working just fine on mine and Carlo OSD´s

Be patient please... after all the current code r370 is working fine for everybody

keep it flying and trusting us your flights.

-KV

rbirdie001 · Post by **rbirdie001** » Thu Sep 26, 2013 9:39 pm

Hi kataventos,
I really marvel that you all are spendig so much time for us!

Just because I'm reading that you are working on completely new GUI,
please let me say one experience:
When I work again with Minim GUI after some weeks, I'm always confused
about the meaning of dark/light blue switches for configuration. I always
have to look at reference what position is ON and what is OFF. What do
you think about replacing them with something really explicit like
button which is GRAY for OFF and GREEN for ON?
Thanks!
Roman

witespy1 · Post by **witespy1** » Sun Sep 29, 2013 2:07 am

Ditto.

thank you for everything you have done. I like your firmware. I have modded the hardware to working with the current code r370 and makes all the "mod" hardware pins available. It will be able to offer it at an good price. Please, how can I contact you to send you this hardware, and anyone else on the team .. .

subaru4wd · Post by **subaru4wd** » Sun Sep 29, 2013 4:53 am

That OSD board looks brilliant! Can we get a pin diagram for all the exposed pins?? Can't wait to see that on your site witespy!

SkyrimDragon · Post by **SkyrimDragon** » Tue Oct 01, 2013 4:59 pm

...................................................

kataventos · Post by **kataventos** » Wed Oct 02, 2013 1:51 pm

@WiteSpy

Great, that seems really made for this code inclusive voltage dividers, I presume you have it for max 5v to RSSI and up to 4S on both main and video voltages.

Thanks for the offer, already sent you an email with developers addresses

@SkyrimDragon

I presume that you are talking about using the PWM RSSI.
As I said before at this time on that release you need to inject PWM before change the option otherwise it will hang.
What PIN are you using, MISO?

Cheers,
-KV

SkyrimDragon · Post by **SkyrimDragon** » Wed Oct 02, 2013 5:36 pm

...................................................

disq · Post by **disq** » Sun Oct 06, 2013 5:48 pm

Any plans to make it compatible with FrSky telemetry data? ie. connect a single wire from a flight controller (MultiWii with frsky patch, Baseflight, etc) to both the RX and OSD and get the data on both using a single serial connection on the FC side.

Of course that would mean removing all the MSP code and fitting in a FrSky parser there instead. (FrSky's inverted serial requirement (which sucks) could be ignored, as there are usually places to get the not-inverted signal from the FC, or maybe just before the ttl inverter)

rbirdie001 · Post by **rbirdie001** » Sun Oct 06, 2013 11:05 pm

Hi guys,
first I want to thank to all developers because this OSD is really GREAT! Today I practised FPV flying (I'm just beginner in it) and OSD worked perfectly!
OK, almost perfectly, because speed measurement was obviously incorrect - I guess that OSD was displaying just 10% of real speed. You can look at this video: http://www.youtube.com/watch?v=zYCRTDU-kUM
At about 0:50 I'm passing tractor which is going about 10km/h but OSD shows speed 1-2km/h and at about 2:17 I'm flying at about 40km/h (90m in 8 secs) but OSD shows just 4km/h. I'm using unmodified MWC 2.2 and OSD r370 with just this modification for correct RSSI readout: viewtopic.php?f=8&t=2918&start=600#p41493 but nothing else touched.
For me it looks like just missing *10 in calcualtion.
Is it known problem, or I'm again first?

Thanks!
Roman
Edit: Maybe important info: I'm using external I2C GPS on Promini board so in case it works OK for other people who use Mega boards and serial GPS and not for me, then it could be problem of MW 2.2 interpretation of speed from I2C GPS. I'll test it over GUI...
Roman

jevermeister · Post by **jevermeister** » Mon Oct 07, 2013 9:47 am

Hi,
last year I bought a Mobidrone OSD but the develepment seems dead, I managed to keep it working by hacking into the Multiwii MSP after each update but this and the hardware is a real pain.

Would you guys recommend to switch to MinimOSD or is it possible to run this software on a mobidrone OSD?
I like the layout of the Mobidrone OSD but configuring is like solving a puzzle and flashing is really complicated and dangerous.

Additionally: I read out Current sensor and Height via Multwii ist this possible via this OSD too? I cannot get a clue from the FAQs and guides.

ps.: I like that GUI - nice work!

Nils

carlonb · Post by **carlonb** » Mon Oct 07, 2013 10:09 am

@ rbirdie001,
I'm using Mega board and a serial GPS unit, so I've no issues wirh the speed indication. I saw your vid and I can confirm you have a problem may be with I2c GPS.
Pls verify and let' us know.

@ jevermeister,
Mobidrone H/W is not compatible with MinimOSD H/W. Mobidrone do not use the MAX video chip.
KV_Team_OSD with MinimOSD H/W is perfectly compatible with MWii

Bye
Carlo

jevermeister · Post by **jevermeister** » Mon Oct 07, 2013 12:32 pm

Hi,
just ordered a minim 1.1.

Is there a guide for the newest OSD dev, the guide provided in the Wiki seems to be outdated.
I just played around with the newest GUI but some items are not displayed in the example screen even if I activate them (note: no hardware attached yet)

Last Question: Is baro altitude used via MW Protocol If there is no GPS data present? I believe I saw a part in the code where Baro Altitude is used (mwaltitude).

I am looking forward to test this OSD. I loved my Mobidrone with my customizations like mAh Counter and stuff but it is time to upgrade to better software I believe.

Nils

carlonb · Post by **carlonb** » Mon Oct 07, 2013 1:23 pm

@jevermeister,

Hi Nils,
About Baro, yes I can confirm that baro altitude is coming from FC also if no GPS is available.

Almost all data on OSD display are coming from MWii FC, but a dedicated video cam battery volt level (if used) is managed by OSD H/W and S/W.
Optionally it's forseen to manage RSSI or Main Vbatt or mAh consumed also directly from OSD H/W but at this momento MinimOSD has not exposed these pins and you need to solder on the AT chip pins directly (not so easy).
I know in the very near future there wil be available a new OSD H/W (JDrones and Witespy) where we can found more new input pin/connector and this will make the life easy

Bye, Carlo

jevermeister · Post by **jevermeister** » Mon Oct 07, 2013 1:56 pm

Hi,
thank you for that clear statement, now I am even more looking forward because I have all features I needed to hack into that mobidrone!

As I power Cam and FPV TX with same 12V 3s Lipo as my FC I do not have to do the 12V mod, right?

I only need to power the FPV TX with 12V and the OSD routes 12V and GND to the cam (The TX has 12 Supplied to the cam Pinout if you connect a cam directly)?
Nils

rbirdie001 · Post by **rbirdie001** » Mon Oct 07, 2013 6:43 pm

rbirdie001 wrote:Hi guys,
first I want to thank to all developers because this OSD is really GREAT! Today I practised FPV flying (I'm just beginner in it) and OSD worked perfectly!
OK, almost perfectly, because speed measurement was obviously incorrect - I guess that OSD was displaying just 10% of real speed. You can look at this video: http://www.youtube.com/watch?v=zYCRTDU-kUM
At about 0:50 I'm passing tractor which is going about 10km/h but OSD shows speed 1-2km/h and at about 2:17 I'm flying at about 40km/h (90m in 8 secs) but OSD shows just 4km/h. I'm using unmodified MWC 2.2 and OSD r370 with just this modification for correct RSSI readout: viewtopic.php?f=8&t=2918&start=600#p41493 but nothing else touched.
For me it looks like just missing *10 in calcualtion.
Is it known problem, or I'm again first?
Thanks!
Roman
Edit: Maybe important info: I'm using external I2C GPS on Promini board so in case it works OK for other people who use Mega boards and serial GPS and not for me, then it could be problem of MW 2.2 interpretation of speed from I2C GPS. I'll test it over GUI...
Roman

Hi!
I looked closer at the problem and it's even more funny:
When I connect my tricopter to laptop and try to read speed in GUI, it measures also wrong, but not 10 times less (like OSD) but approx 2.5 times more!

than the real speed in km/h is.
(I took it into the car and measured during driving.)
I don't know which units should GUI show (km/h, m/s, mph, knots...), but I can't see any logic in it. More it looks like mistake between I2C NAV module and MWC (probably) or MWC and GUI.
I also found probable reason of my bad speed measurement on Minim OSD: in I2C_GPS_NAV_v2_2 on the line 724 there is:

Code: Select all

case 7: i2c_dataset.ground_speed = (atof(string)*0.5144444)*10;      //convert to m/s*100

This is obviously conversion from knots to cm/s but if there isn't something special I missed, it seems to be wrong because 1kt is 51.44444 cm/s.
I'll try to modify it and test tomorrow with OSD but still I wonder what value GUI should show...
Regards
Roman

ezio · Post by **ezio** » Mon Oct 07, 2013 8:28 pm

Speed that comes from multiwii protocol is in cm/s

IceWind · Post by **IceWind** » Mon Oct 07, 2013 8:37 pm

Hi,

is there an option to disable the AHI?
I looked in the config file as well as in the GUI but I can't find it.

Thanks.