MultiWii

in config.h and also noted in the user guide...
WITESPY V2 - Enable to use the WITESPY V2 with different hardware

I have selected the witespy board in config.h

Display voltage should be on (blue switch on right)
Use mwii should be off
Voltage adjust suggest start around 200

suggest try battery on bat 1 or 2 and see if either work.

Should see something other than 0

Tried the switch on left and right, both video voltage and main voltage. And both just show 0.0 :/

If applying 12v on the video in/out pins would this cause a conflict? I've seen it wired both with and without and still working.

Ok, got the voltage working. Yay.

Now the font is messed up once hooked up to the fc.
uploaded several times and still no luck.

The boot screen is fine.

Any ideas?

From memory if you don't have the solder pads bridged you will need to have the overlay board side powered by a 12 feed.

If the pad is bridged then the ftdi should upload absolutely fine.

https://code.google.com/p/rush-osd-development/wiki/MinimOSD_Basic_Setup

Pads soldered. Everything seems to work fine however just the font is off :/

#1 output stage must be powered when programming fonts - n/a if using 5v like sounds you do
#2 programmer needs to be 5v - some are not - and some have the 5v/3.3v selector labelled wrong

So how many are using the 1.2 + gui ? Interested in the screen editor . Can I just modify the 0 screen or do I have to enable switch for multiple screens ?

Ok this one has been stumping me for hours, and I have tried all I can think of. My last resort is to ask here for the advice of others.

I have taken a break from MWOSD and Baseflight/MultiWii and have been using APM, with the MinimOSD-extra firmware... fonts... etc. Im getting ready to put a OSD and Baseflight in a setup, and ive been banging my head trying to get MWOSD to work... but seem to be getting stuck at the same spot no matter what. Setting up in the GUI.

I am able to flash the arduino code to my OSD board no problem, but then when I connect to the COM port with the MWOSD GUI, None of the settings will stick. If I change a switch, seconds later the switch reverts back to the original location. No matter what I do, writing does not actually write, and reading will always refresh the default settings. If I disable OSD simulation in the GUI, i can move switches... but clicking write does nothing, and no settings are ever saved. This is using the latest MWOSD v1.2, however the same results with v1.1 and v1.0. My hardware is the Witespy board.

I have tried this using two different FTDI programmers (verified 5V), and i have five OSD boards here, all do the exact same thing. No matter what, the GUI doesnt communicate. As a test, I loaded the MinimOSD-Extra Config Tool for APM, and it is able to communicate with the OSD no problem, configure screens, upload fonts.... The APM firmware and GUI have absolutely no issues at all.

Im at my wits end here. Im hoping its something simple I am overlooking. I can't imagine what.

My latest is a kv witespy mimimosd w/ 1.2 mwosd ,,,everything's working great....But I cant access the stick programing...What obvious thing did I miss....

Debogus wrote:My latest is a kv witespy mimimosd w/ 1.2 mwosd ,,,everything's working great....But I cant access the stick programing...What obvious thing did I miss....

Check and make sure you dont have low rates programmed on your transmitter. MWOSD needs to see full stick movement.

after more than two dozen attempts to get these font correctly working I have officially given up. I have tried several different firmware always clearing the eeprom and using a good ftdi adapter. Tried several good font files and still nothing.

Good news is voltage is working and the timer works. Nothing else is usable

subaru4wd wrote:

Debogus wrote:My latest is a kv witespy mimimosd w/ 1.2 mwosd ,,,everything's working great....But I cant access the stick programing...What obvious thing did I miss....

Check and make sure you dont have low rates programmed on your transmitter. MWOSD needs to see full stick movement.

Have d/r and know from my rctimer minim that has to be switched to 100%
The only thing on this one different, is I used the futaba offset of 1520 on center ,the other is tuned out manual....could that be it ?
Will treat it like it is and retune the transmitter...

1095, 1500, 1905 are the radio settings you need

Dam Im retarded ,reset the center, reset the endpoints ,doh ,found out I set the pitch 60 on both of the D/Rs ....Grrrr all I had to do was fix that .
done works anyway.

Shikra the screen edit in plus is awesome..dont really need a drag and drop..cant wait for 1.3 ...Youda man

subaru4wd wrote:Ok this one has been stumping me for hours, and I have tried all I can think of. My last resort is to ask here for the advice of others.

Im at my wits end here. Im hoping its something simple I am overlooking. I can't imagine what.

Okay, scratch all that. Somebody pointed me to the new GUI for v1.2+ with the layout editor. I gave that a try, and I am able to fully configure my MWOSD 1.2 boards now I am uploading fonts.... re positioning items... I am in love with this OSD all over again!!!

Thsi one is posted quiet frequently. So far every one (I think has been down to the voltage needed by the max chip.

I would recommend:
#1 verify the voltage supplied by the programmer is 5v. Best place is on the actual pins of the OSD 6 pin header. It needs a full 5v and there have been quite a few reports of this being an issue
#2 If you are powering the output stage separately, this absolutely has to be powered during programming for fonts
#3 Checking that the common ground link on the OSD is bridged during any programming

acessford wrote:after more than two dozen attempts to get these font correctly working I have officially given up. I have tried several different firmware always clearing the eeprom and using a good ftdi adapter. Tried several good font files and still nothing.

Good news is voltage is working and the timer works. Nothing else is usable

No worries - thanks for the feedback.
When your done, post layout. Be good to see all the creative options out there.

1.3 will not be a massive change compared to 1.2 - starting to get pretty full of features and memory

So far:
Customisable layout. Also addresses following requests:
- "Disarmed" enable / disable option to GUI
- Callsign - GUI to support location
Alarms in for max current, amperage, distance, altitude, speed, timer. All tested and working
OSD switch - 3 way switch middle position to turn OSD overlay off. Tested and working
Pal/ntsc autodetect - disabled by default
GUI - switches green for on / red for off
GUI - selectable baud rate

Debogus wrote:Dam Im retarded ,reset the center, reset the endpoints ,doh ,found out I set the pitch 60 on both of the D/Rs ....Grrrr all I had to do was fix that .
done works anyway.

Shikra the screen edit in plus is awesome..dont really need a drag and drop..cant wait for 1.3 ...Youda man

I've been reading info from everywhere about the witespy/minimosd, and it seems like this thread has some of the best info so far

I recently purchased the witespy minim osd w/ kv mod. I plan to use the OSD without a flight controller just so I can get basic rssi/voltage/current information on a fpv plane. My question is this - would I be better off using the latest multiwii OSD r1.2 and trying to configure it for standalone operation (is that even possible?) or just using the "standalone" firmware posted on the witespy minim osd product page? Thanks for any info in advance.

This will run fine standalone...

Use 1.2 with the 1.2+ gui and just enable the bits you need and where you want using switches and layout editor.

It also makes a great groundstation OSD...

Sounds good to me, thanks for confirming

Altitude in OSD does not reset to zero on a dragonfly/Flip 32 ?
Is this a OSD thing or a flight controler thing ?
Reads accurate just always starts off 30 40 foot up and doesnt change when its disarmed or armed

Hello,

Juste a small question about the font editor :

Is there a way to simply edit the font by convert the font file (default.mcm) or I must use the GUI editor ?

Thanks

Im having all kinds of trouble getting this OSD up and running. I've successfully got minim's up and running before using extra firmware and config tool. But with MWii and Rush/ KV team i'm having difficulty.

I suspect its to do with my operating system being 64bit and the GUI program being a 32bit Java app.

To begin with i was getting a java path error that would prevent me even loading the program. I replaced those files with ones from the 32 bit java install directory (java.exe, javaw.exe and javaws.exe) and now i can get the program to load up.

It even acts like it's loading the character set.

When it comes to writing the params i get a flash on the TX icon. i then disconnect and reconnect and try to read the params, none of my changes are saved. Anyone had this issue before and can give me some pointers???

Turns out i've been caught out by the old Tx Rx switcharoony. it's always after you post that you figure it out

Should it be tx to tx rx to rx, or tx to rx and rx to tx?

Debogus wrote:Altitude in OSD does not reset to zero on a dragonfly/Flip 32 ?
Is this a OSD thing or a flight controler thing ?
Reads accurate just always starts off 30 40 foot up and doesnt change when its disarmed or armed

Bump..... So nobody else has this issue ?

acessford wrote:Should it be tx to tx rx to rx, or tx to rx and rx to tx?

The convention is rx to tx and tx to rx, however my programmer has labelled where the pins go to not what pins it breaks out.

so the moral of this story is try both

This is controller..

All OSD does is display what controller sends.
Pretty sure mine is close to zero at take off. I would expect controller to set it to zero reference upon arm, but no idea what it actually does. Mainly use multiwii

Debogus wrote:Altitude in OSD does not reset to zero on a dragonfly/Flip 32 ?
Is this a OSD thing or a flight controler thing ?
Reads accurate just always starts off 30 40 foot up and doesnt change when its disarmed or armed

shikra wrote:This is controller..

All OSD does is display what controller sends.
Pretty sure mine is close to zero at take off. I would expect controller to set it to zero reference upon arm, but no idea what it actually does. Mainly use multiwii

Debogus wrote:Altitude in OSD does not reset to zero on a dragonfly/Flip 32 ?
Is this a OSD thing or a flight controler thing ?
Reads accurate just always starts off 30 40 foot up and doesnt change when its disarmed or armed

Thanks
At least I know where to look now

hello, first cut of the next release of MWOSD - R1.3 is here:

https://drive.google.com/uc?export=down ... HNxVkVlWE0

This is a pre- release. Please test carefully. There have been a lot of changes and maybe a few bugs, but it should be pretty close to final.
Include a a mac compiled version

Changes from 1.2 are:
+ OSD - alarms for distance, altitude, speed, mAh, amps and flytime
+ OSD - large font option
+ OSD - additional MAP mode for advanced pilots
+ OSD - added alarms adjust page for Distance / Altitude / Speed / mah / Current
+ OSD - Increase trip maximum


+ GUI - OSD layouts can be edited from GUI
+ GUI - 256 OSD layouts can be created / stored on GUI
+ GUI - 10 preset and new layouts - ground station and standalone
+ GUI - Alarm adjustment options
+ GUI - added callsign to simulator
+ GUI - call sign position can be edited via GUI
+ GUI - added read & write to OSD verification check.
+ GUI - significantly improved GUI simulator response time for OSD display.
+ GUI - added names to GUI layouts
+ GUI - optional Auto PAL/NTSC detect
+ GUI - tidy up layout editor group
+ GUI - added GUI layout name to editor group bar
+ GUI - map modes selectable in GUI instead of config
+ GUI - implementation or URL links for support/ faq / guides etc.
+ GUI - support for different baud rates
+ GUI - relayout to increase screen space
+ GUI - option for OEM name rebranding
+ GUI - GUI / OSD version check
+ GUI - version / name moved to window title
+ GUI - switches turn green when enabled


+ config.h - option for OSD switch 3 position
+ config.h - option for prominent "low voltage" text warning
+ config.h - option for displaying low voltage in blank screens
+ config.h - option in config to define callsign display frequency and duration
+ config.h - option to amend blackbrightness for TX/CAM with compatability issues

R1.2 release defines Witespy board as:

#define WITESPYV2 // If using Witespy V2 OSD, select this to use alternative resistors / pinouts

1.3pre1 it is back to the old 1.2pre2 value (with the ".", which I think is incompatible ?):

#define WITESPYV1.1 // Choose this if using Witespy V1.1 OSD, select this to use alternative resistors / pinouts

Which is correct ?

-=dave

tungsten2k wrote:Okay, it seems this Mac GUI doesn't work at all (similar to previous reports from others).
I'll mess with the Mac version more tonight but it seems to not be working with my CP2102 TTL USB bridge.

For those having difficulties with CP2102 driver not working on Yosemite, you can download the RC signed driver here:
http://community.silabs.com/t5/Interfac ... 72#U138472

-=dave

For this beta release use:
#define WITESPYV1.1

All it is is a rename to try to better match WItespy's naming conventions rather than my made up one

Dunno why he changed. All its done is called a a whole load of hassle and confusion......

Will load it later today and let you know any issues I find Shikra

Will load it later today and let you know any issues I find Shikra

Dear Shikra,

I have tried your 1.3 pre release on my workbench computer (Windows 64, AMD processor) and get the following error when I try to start it:

---
The class controlP5.ControlWindow is incompatible with Processing 2.0.
A library (or other code) is using registerMouseEvent() which is no longer avail
able.
The class controlP5.ControlWindowKeyListener is incompatible with Processing 2.0
.
A library (or other code) is using registerKeyEvent() which is no longer availab
le.
ControlP5 1.5.2 infos, comments, questions at http://www.sojamo.de/libraries/con
trolP5
Jan 04, 2015 9:47:52 AM controlP5.ControlBroadcaster printMethodError
SEVERE: An error occured while forwarding a Controller event, please check your
code at controlEvent
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at controlP5.ControlBroadcaster.invokeMethod(Unknown Source)
at controlP5.ControlBroadcaster.broadcast(Unknown Source)
at controlP5.ListBox.controlEvent(Unknown Source)
at controlP5.Controller.broadcast(Unknown Source)
at controlP5.Button.setValue(Unknown Source)
at controlP5.Button.update(Unknown Source)
at controlP5.Button.update(Unknown Source)
at controlP5.ListBox.setValue(Unknown Source)
at MW_OSD_GUI.setup(MW_OSD_GUI.java:754)
at processing.core.PApplet.handleDraw(PApplet.java:2280)
at processing.core.PGraphicsJava2D.requestDraw(PGraphicsJava2D.java:243)

at processing.core.PApplet.run(PApplet.java:2176)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at MW_OSD_GUI.controlEvent(MW_OSD_GUI.java:1474)
... 17 more
java.lang.UnsatisfiedLinkError: C:\FPV250\MW OSD R1.3 pre1\MW_OSD_GUI\applicatio
n.windows64\lib\rxtxSerial.dll: Can't load AMD 64-bit .dll on a IA 32-bit platfo
rm thrown while loading gnu.io.RXTXCommDriver
java.lang.UnsatisfiedLinkError: C:\FPV250\MW OSD R1.3 pre1\MW_OSD_GUI\applicatio
n.windows64\lib\rxtxSerial.dll: Can't load AMD 64-bit .dll on a IA 32-bit platfo
rm
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at gnu.io.CommPortIdentifier.<clinit>(CommPortIdentifier.java:123)
at processing.serial.Serial.list(Unknown Source)
at MW_OSD_GUI.setup(MW_OSD_GUI.java:766)
at processing.core.PApplet.handleDraw(PApplet.java:2280)
at processing.core.PGraphicsJava2D.requestDraw(PGraphicsJava2D.java:243)

at processing.core.PApplet.run(PApplet.java:2176)
at java.lang.Thread.run(Unknown Source)
Exception in thread "Animation Thread" java.lang.RuntimeException: Error inside
Serial.ports()
at processing.serial.Serial.errorMessage(Unknown Source)
at processing.serial.Serial.list(Unknown Source)
at MW_OSD_GUI.setup(MW_OSD_GUI.java:766)
at processing.core.PApplet.handleDraw(PApplet.java:2280)
at processing.core.PGraphicsJava2D.requestDraw(PGraphicsJava2D.java:243)

at processing.core.PApplet.run(PApplet.java:2176)
at java.lang.Thread.run(Unknown Source)

---

I'll tried the 32 bit version on another machine and it seems to start correctly.

I guess that there is some library (or reference to library) missing in the Windows64 version when using AMD processor?

Thank you for your great work!

...I've also got some problem when compiling 1.3 pre release in Arduino:
(Compiling 1.2 works fine on the same machine)
---
Using library EEPROM in folder: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\EEPROM

C:\Program Files (x86)\Arduino/hardware/tools/avr/bin/avr-g++ -c -g -Os -w -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -MMD -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=158 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR -IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino -IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs -IC:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\EEPROM C:\Users\Eilert\AppData\Local\Temp\build7736110991464551577.tmp\MW_OSD.cpp -o C:\Users\Eilert\AppData\Local\Temp\build7736110991464551577.tmp\MW_OSD.cpp.o
In file included from MW_OSD.ino:73:0:
C:\Users\Eilert\AppData\Local\Temp\build7736110991464551577.tmp\GlobalVariables.h:610:1: error: 'prog_char' does not name a type
prog_char configMsgMWII[] PROGMEM = "USE MWII";
^
C:\Users\Eilert\AppData\Local\Temp\build7736110991464551577.tmp\GlobalVariables.h:614:1: error: 'prog_char' does not name a type
prog_char configMsg00[] PROGMEM = "STATISTICS";
^
C:\Users\Eilert\AppData\Local\Temp\build7736110991464551577.tmp\GlobalVariables.h:615:1: error: 'prog_char' does not name a type
prog_char configMsg01[] PROGMEM = "FLY TIME";

---

Is there a library missing?

Best regards,

Eijo - I'll take a look at this in the week.
I can run the 64 bit on mine OK (hadron processor), but it does show errors in the cmd window. I don't see some of the ones you advise so maybe its machine specific.
WIll update a bit later in the week.

Suggest try using the 32 bit for now. I always use that one myself....

I'm running Arduino 1.5.8 and the error seems to be an issue with later version of GCC in Arduino environment from 1.5.0. When I googled it I found this post describing the issue: http://forum.arduino.cc/index.php?topic=272313.0

I'll tried to make the proposed changes in the link above and there are less errors now, but some still remains. I'll go for 1.2 in my current Quadracopter build and update later when you have a stable 1.3 release.

ah - came back to update and see you posted too - I think if use standard arduino then fine.

For those who wish to remove compiler / system events:
Remove this line in MW_OSD_GUI
// baudListbox.setValue(1);


For those few who do use avrc compiler instead of old arduino new versions this may work as a temp fix...
put this at top of gloabalvariables.h
#define prog_char char PROGMEM

If see this message in system console - ignore.. its not used. For info only
"A library (or other code) is using registerMouseEvent() which is no longer available"

Tested 1.3 pre.
Looks OK so far. Good thing that you added large fonts ;-)
(btw, my hornet font mod still working - tested).

Minor issues:
- There's blinking letter "S" near disarmed string - blinks together with alarms (so it becomes "DISARMEDS"). I commented "FORCE_DISP_LOW_VOLTS" and it disappeared - that's probably part of warning text?
- FULLAHI option does nothing IMO. I commented SBDIRECTION and uncommented FULLAHI define, AHI width remained the same. +2 dashes to AHI (from each side, so +4 in total) would be nice.

Not tested in air... But will do ;-)

Thanks ABL

for disarmed/low volts I figured in flight that as the "disarmed" is unused it would be ideal utilisation of screen space. I didn't really pick up on the scenario on the ground in testing.
If I add a check to display only if armed, I think that will look cleaner.

for AHI - surprised as I don't think any changes in that area. WIll recheck and see if can add the extra..

For fonts -
its aimed at guys like you so let me know what bits you think could do with fattening up a little. I don't think font file is likely to change much in future so now is good time to do it.

I think for your hornet font, its liekly one of map modes will no longer dispaly.

@ABL

for #FULLAHI - This is working OK for me so a little puzzled with this.
I have extended a little further as requested. 5 "bars" either side of center instead of default 3

For optional low volts warning, I checked with low volts and see what you mean about the flashing "S". This now only displays when the "armed/disarmed" indicator is cleared.
Much nicer - thanks for pointing that out.

I tan into same issue on Arduino 1.5.8 which resolved after moving to 1.0.6. On Whitespy board, cell count adjustment via stick movement is non-functional (instead it adjusts the line below).

-=dave

Loaded and looking good so far, really like teh layout editor

One thing thats unclear is the 3 position OSD switch, is there a trick to getting this enabled?

I assumed the centre would turn the OSD off, but that doesn't appear to be the case, I get the two selected views at hi and low, but mid position results in no change to the OSD

Hey Deet

Step1 - Basically uncomment this line...
//#define OSD_SWITCH_3WAY 5 // Enables midpoint on specified channel (range 0-7 def=5) to turn off OSD. For 3 way OSD switch

Step 2 - Change the "5" to match channel you want mid stick = blank screen to be activated. It doesn't need to be the OSD switch, but kinda makes sense.
I believe aux1=4, aux2=5 and so on

I just carried out a quick test here against the throttle channel which is "3" and it seems to work OK. midrc is 1400-1600 on multiwii gui

All sorted

I was using AUX4 as the OSD switch channel, so once I set #define OSD_SWITCH_3WAY 7 it worked perfectly (its logical channel not physical channel)

The Screen editor works nicely, Once I get to do some test flights the next thing I want to test is if my "saved" screens copy onto my other OSDs

Great work Skikra, this has now got to be the best OSD around

Thanks for testing and feedback Deet.