aronax meinte

Also communication via BT module should be now a little better.
Best Regards - Irek

Hello Irek,
For my part, it still does not with BT module.
I tried all options, I receive packets but I can not send with Smart OSD Manager.
Mktools does not connect with FC/NC.
When we are on the field, the most important is to communicate with MK (FC / NC). Is it not possible to have a version to communicate only with MK without the Smart OSD ?
thank you
65oliver65

65oliver65 meinte

aronax meinte

Also communication via BT module should be now a little better.
Best Regards - Irek

Hello Irek,
For my part, it still does not with BT module.
I tried all options, I receive packets but I can not send with Smart OSD Manager.
Mktools does not connect with FC/NC.
When we are on the field, the most important is to communicate with MK (FC / NC). Is it not possible to have a version to communicate only with MK without the Smart OSD ?
thank you
65oliver65

I had this issue with only receiving packets and not able to send, BEFORE soldering the resistor to get BT working in both directions.

You have already done that and re-checked don't you?



@anorax: Geat!!!! Thank you for this update, will test asap and report if I find any issues
p.s. have you seen my brand new MK GPXTool ?

DRAGNET meinte

I had this issue with only receiving packets and not able to send, BEFORE soldering the resistor to get BT working in both directions.
You have already done that and re-checked don't you?

hello,
yes I did at first, but it did not work, and I'm not alone in France

thank you Dragnet

Thanks Irek

I'm going to test now and will report back.

DRAGNET meinte

p.s. have you seen my brand new MK GPXTool ?

From the screen shots that looks pretty cool, do you have that info in english?

Thanks
Craig

No english description yet, - its still in beta, as long as its not in a release state I have only published it in german section of this forum (less hassle for me) but this can change anytime soon.... google translator users and experienced pc users will not have much problems using the app

the app itself is completly in english

Can someone please tell me what bootloader version they have on their OSD, mine is saying 0.0. Is this correct?

Edit: I just noticed that it depends on the OSD firmware version. 2.23 had bootloader: 1.6 and 2.27 has bootloader 0.0. So I guess it must be ok?

Thanks
Craig

Hello,

65oliver65 - we have BT module from MK shop, we tested it again
with additional 1.2kohm resistor (it can be any resistor about 1kohm) on osd board, and after that we removed it
and also we removed resistor from BT module. In both cases we had communication
with OSD, but in orginal setup we didnt have. So it is impossible to say why it doesnt work in your setup.
If it is possible please try to remove that resistor from your BT.
We also thought about selling own BT module, which will work with osd without problems.

DRAGNET - very cool tool

crcr - bootloader in you board is 1.6 - sometimes Manager doesnt catch identification packet from bootloader, and then it will display 0.0.

Best Regards - Irek

thanks irek for the text boxes and the camera frame ;-)). great!

Hi aronax!

I am having the same problem with Bluetooth connection as 65oliver65. I tried the 1.2K resistor as suggested but without success. I could not see any communication wave forms on pin 9 of the UART port in the OSD card. There must be a software glitch some where. How to upgrade the boot loader?

Other wise SOSD is great in all aspects.

PB

GREX meinte

thanks irek for the text boxes and the camera frame ;-)). great!

Can someone please tell me what the user defined text and camera frame boxes are designed to do?

Thanks
Craig

Hello everyone!

I am interested to use the Smartosd on the GROUND together with the MK WI232-Module and a Fatshark.

Irek answered to Wizprod:

Zitat

wizprod - just make sure, that proper pins on MK port in osd i powered with +5V.
In ground setup connect the wi module to MK port in osd, and connect osd via usb to your computer,
then you will not need MKusb.

Is my opinion correct:
I dont need more components on the ground than Smartosd and WI232.
The Computer is just needed for updates etc.... and not for asking the data from the fc via the WI232.
And no more cables to buy, they are all included???


Do i have to make any updates on the smartosd, when the FC or NC firmware changes? So far i know i'dont..?
Correct??

Thanks for your reply!!!
Reinle

aronax meinte

Hello,

65oliver65 - we have BT module from MK shop, we tested it again
with additional 1.2kohm resistor (it can be any resistor about 1kohm) on osd board

Hello, please it is possible to have a photo ?

Hello,

prabinbardoloi - well, we wasn't able to communicate with osd via BT without hardware modification. But we could communicate with OSD with additional resistor, without any change in software. So it is very unlikely, that this is software issue. Tomorrow we will do additional test. maybe there are different versions of BT module

Craig Please take a look at picture.
I think, that it will be the best answer for your question

Reinle - You just need something to power OSD and wi232 module.

65oliver65 I will have it toomorow.

Best Regards - Irek

Hi All, anyone having issues with Gopro Hero 2 camera? I'm trying to use it with SmartOSD, but the OSD characters and graphics are very fuzzy.
I've tried both PAL and NTSC with Gopro and get the same results. I've also tried with 3S and 4S batteries and no changes.

With my standard small FPV camera it works great.
Appreciate if someone has any tips.

Thanks,
Leonardo

Leonardo

Several other have had the same problem. You get an image that looks fuzzy and somewhat like a weird negative. FPV cam is fine. I think it is the GP overdriving the video signal. You might be able to adjust it with the two potentiometers (white and black) but then the FPV camera would probably be messed up.

Gary

Now after upgrading to version 2.27 I have a problem. The OSD screen shows only the big OSD opening logo along with firmware version 2.27_ etc. There is no any other text/data overlay from the NC. I have repeated the upgrades several times but it remains same. On OSD manager I can see that boot loader version is 1.6 and fw version is 2.27. When I try to send any 1 or all it announces Boot loader is Ready. Some times it shows failure with the message " Is the OSD powered? ". In an attempt to down grade to earlier versions e.g. 2.23/2.25 the situation remains same.

Can any body help out? Is there a way to reset the ATMEL processor AT91 and loading the boot loader afresh. It looks like a corrupted software.

PB

Hi Gary,

Thank you for the response. The aim is to use Gopro for FPV, so setting up the OSD pots should be ok if it works fine. When you mean potentiometers it's via software, right? It doesn't seem to have any potentiometer in my board.

Thanks,
Leonardo

Leonardo

I have the older board that has the pots. If you have the new one then it is with the software.

Gary

congrats aronax!
looks really promising. keep the good work.
I'll be monitoring this and back on time.
Take care!

aronax meinte

65oliver65 I will have it toomorow.

??

My problem resolved. I have to go slow in sending the screens one by one with each update of parameters. But I used to send ALL in earlier versions without problem.

PB

Hi guys,

Sorry for the long absence, but I was really really really busy

First thing - I've prepared new firmware for OSD 2.28 which allows to change the appearance of altitude, speed and heading indicators.
The apperance of home direction indicator (integrated with artifical horizon) can now be modified.
Also I've fixed small bug with LOS "line of sight" value.
Important : you need to refresh third font file, with one of the following files : OSDsymbols or OSDsmallsymbols.
Quick preview
Appearance of mentioned indicators can be changed by modifying "Visual Appearance" property in PC manager.



Second Thing - BlueTooth - the best way to make MK BT module work with OSD, is to remove resistor from TX line and solder that connection, or to replace it with resistor of small value (such as 10-20 ohm).

Here is foto of our module.
externer Link:


Third thing - video signal - some cameras (such as GO PRO HD2) have high constant voltage of video signal, this can result in "jumpy" or very dark image.
This can be simply eliminated by inserting small capacitor into "video in" cable connector to block any constant voltage.
We tested it with 47uF (but it can be something in range 47uf - 330uf) and in future we will add such capacitor on OSD board.

Fourth thing - "ground mode" - this may be important for Craig and Reinle, but also for others trying to use OSD on the ground. We did test with Xbee 900 (but it should work with Xbee 2400 and wi232) and we were able to connect to with MK tools if transparent port is set to "USB direct", with "buffered" the delay was too big for MK tool (which is quite sensitive for that).
Xbee can be powered from separate source or via OSD - but in this case you need to remove diode located just 1mm from MK data port, and solder that connection.
Here is image of that diode
externer Link:



Uff - I hope I didn't forgot about anything

Best Regards - Irek

Hi Guys!

Zitat

We did test with Xbee 900 (but it should work with Xbee 2400 and wi232) and we were able to connect to with MK tools if transparent port is set to "USB direct", with "buffered" the delay was too big for MK tool (which is quite sensitive for that).
Xbee can be powered from separate source or via OSD - but in this case you need to remove diode located just 1mm from MK data port, and solder that connection.

Is it correct:
The diode has to be removed only when i want to connect the OSD on the ground, together with the MK Tool (connected with the laptop by USB) ???? In all other cases there is no need to remove it?!

"solder" means connect both solder points of the diode together?

Thank you
Reinle

PS: Irek: what a fast delivery service: order-delivery about 5 days!!!! Thank you very much!

Thanks Irek, I was having issues connecting to MKTools in both direct and buffered modes, are you saying that by removing the diode this will improve?

Also, is there any way to power the OSD on the ground without the laptop?

Thanks
Craig

Hello

Reinle - yes that diode protects OSD from powering anything via MK data port., so you will want to remove that diode only in ground setup and when you want to power ground xbee via OSD from PC USB or other source. After removing diode you will need to connect diode points by soldering them together.

Craig - if you are powering your xbee from another source then you dont need to touch that diode. We
tested the wireless connection between the OSD and MK and had no problems in use MK tools when OSD was working in 'direct' mode. MK tool is sensitive to delays in communication , and direct mode only adds just 1 byte delay (0,14ms) buffered mode adds more delay, but it will work without wireless connection.

Best Regards - Irek