I see a new tiny Micro MinimOSD has now been released, absolutely no excuse for not having a full OSD on even a 250 quad or smaller now even if it is only to show voltage, current and mah used. If you haven't tried one of these and you are flying a Naze32 or MultiWii of some form I highly recommend it, nowhere near as hard to set-up as people often think these days with the Naze at least handling more of the work meaning much less in the way of wiring needed.
WiteSpy Micro MinimOSD (http://www.readytoflyquads.com/micro-minimosd)
(http://s17.postimg.org/empmtyk8r/1_15_2015_6_43_12_am.jpg) (http://www.readytoflyquads.com/micro-minimosd)
My excuse is I have no need for an OSD. :D
That`s a good find :) As small as it gets really and Naze32 / baseflight / cleanflight compatible :)
got one on the way to test out.
"osdoge" is also an interesting alternative for naze32
looks pretty good!
i have been looking at getting a OSD just to show my mAh used so this might be good for me ;D
Hi Shikra, I'll be interested to hear how your testing goes as I swear by your software and wouldn't use anything else, keep up the good work!
That OSDoge looks very nice if a bit expensive...
The hard part is finding a small current sensor.
Cheers!
Sure - I'll post back here when get it.
Quote from: Grant Smith on February 01, 2015, 09:06:10 PM
Hi Shikra, I'll be interested to hear how your testing goes as I swear by your software and wouldn't use anything else, keep up the good work!
That OSDoge looks very nice if a bit expensive...
For the record, this micro MinimOSD works perfectly with Shikra's MWOSD (I'm on r1.3 now) and it makes for a very neat OSD installation indeed. here's the proof... ;D
(http://s16.postimg.org/chy3t4t0x/Capture.jpg) (http://postimg.org/image/chy3t4t0x/)
Mr.Witespy is famous for dodging with the orders, sometimes extremely slow shipments, sometimes giving the fake tracking numbers, so, I was avoiding ordering from him. Seeing this little beauty, I have decided to give it a go, and well, my order was shipped within 12 hours, it looks authentic too. Fair play to him ;)
Was also tempted with this two days after ordering two 'regular' sized minimosd' soft a pair of 250's. Saw it was listed over on hobbyrc.co.uk, never dealt with them before tho.
My only other thought was, shame it didn't have mounting holes to match the naze, guess you'd could make mounting board up.
Chris
What is also important, the mini osd from witespy have 2 inputs for voltage detection, with no modification needed. With the regular minimosd.. it's not that easy.
This is handy, for example, with cc3d controllers, which do not have vbat input.
I have had nothing but good service from Witespy (http://www.readytoflyquads.com/ (http://www.readytoflyquads.com/))
2 of my 4 Micro MinimOSD'd died on the bench - he sent out 2 replacement straight away.
Sometimes his shipping is slower but I always get me gear.
The OSD's are awesome - can fit them anywhere!
Just bought Three, 1 for 250, 1 for Tricopter, and a spare.
save a few grams :)
Quote from: Badlands on April 06, 2015, 11:41:00 AM
I have had nothing but good service from Witespy (http://www.readytoflyquads.com/ (http://www.readytoflyquads.com/))
2 of my 4 Micro MinimOSD'd died on the bench - he sent out 2 replacement straight away.
Sometimes his shipping is slower but I always get me gear.
The OSD's are awesome - can fit them anywhere!
Speaks well for the service, not so well of the OSD's if two packed up so quick.
Mine got delivered yesterday running MW OSD R1.3 firmware, and in the Emax 250 Pro in no time with Naze32, lovely little well tiny board, just got to sort out what i want to see in me gogs now.
(http://i152.photobucket.com/albums/s195/PrInCeUKER/RC/Emax%20250%20Pro/20150423_100849_zpsf5yeatk8.jpg) (http://s152.photobucket.com/user/PrInCeUKER/media/RC/Emax%20250%20Pro/20150423_100849_zpsf5yeatk8.jpg.html)
(http://i152.photobucket.com/albums/s195/PrInCeUKER/RC/Emax%20250%20Pro/20150423_100835_zpsyvnwntp2.jpg) (http://s152.photobucket.com/user/PrInCeUKER/media/RC/Emax%20250%20Pro/20150423_100835_zpsyvnwntp2.jpg.html)
Looking good, be very careful with those pins soldered straight to the PCB for the video in/out, mine ripped off the board with the tiniest of knocks, I would suggest either soldering direct and relieving strain somehow or use a load of hot glue to secure the pins too!
Thanks for the tip. will get some hot glue on it.
Was going to solder direct, but then thought get it up and running first make sure alls ok, find a tidy placement and then shorten leads and solder.
Got my 2 boards today , had a problem connecting the FTDI and getting it working .
Only when i plugged it directly to the board did I clear the eeprom and load up MWOSD 1.4 .
So my next step is to try it with the afromini 32 in plane mode .
Any other tips and ideas will be helpful.
Graham
I believe home is set upon arming the naze, so just make sure you have a decent lock before arming.
In normal operation, all altitude / distance/ direction / GPS position etc is as sent from the flight controller to the OSD. All it does is take the info and displays it. Quite dumb in some ways.
The home button on the larger minimosd board just resets it ! You don't lose any functionality.
For awareness, you can also connect a GPS chip to it as well and use it as a very cheap normal OSD without the naze or other controller. More for the plane guys...
Oh that last bit is interesting, so just osd and gas, no need for an apm etc?
@brucey - yes the later version will run pretty nicely with just a gps chip connected. Get almost all of the functionality except the horizon indicator. Even looks the same on the display.
Can still be configured from the GUI
But not the Menu - although that said, this will be available via the tx sticks soon!
Can also be run standalone without gps of course - even for a groundstation for rssi and voltage :)
Vid from some testing...
! No longer available (http://www.youtube.com/watch?v=crF1-5H9Vc4#)
Cool, can you post some details up of what to buy and how to hook it up. .. lazy I know ;D
I got mine from here http://www.ebay.co.uk/itm/MICRO-MiniOSD-Mini-OSD-for-APM-Flight-Controller-MWC-KV-Team-Mod-/252031366202? (http://www.ebay.co.uk/itm/MICRO-MiniOSD-Mini-OSD-for-APM-Flight-Controller-MWC-KV-Team-Mod-/252031366202?)
took about 10 days and works a treat - using mine with minimosd-extra for a new mini pro apm
Ok thanks, and a compatible gps for the osd?
Just ordered a couple of these to try stand alone with a gps
Quote from: Brucey on July 29, 2015, 07:50:43 AM
Just ordered a couple of these to try stand alone with a gps
Excellent, that means your Skyfun will get a satellite lock in less than an hour!
Step 1 Load mwosd onto the minim.
In config.h, select one of the following:
//#define GPSOSD_UBLOX // Uncomment this if you are using a UBLOX GPS module for a GPS based OSD
//#define GPSOSD_NMEA // Uncomment this if you are using a NMEA compatible GPS module for a GPS based OSD
//#define GPSOSD_MTK // Uncomment this if you are using a MTK module for a GPS based OSD
Set up your volts, amps etc etc.
If not using RSSI and have a spare rx channel, can also use this...
//#define OSD_SWITCH_RSSI // Enables 3 way screen switch using a TX channel via a RX channel connected to the OSD RSSI pin. Typically used for GPSOSD.
Step 2 connect up to gps – rx/tx/gnd/5v to the programming port.
Auto sets home once it gets 5 sats
It says disarmed until >20m from launch point then it arms, starts flight timer etc.
When it lands it displays summary screen for x seconds. I think needs to be within 50m of launch and zero groundspeed or something
Still consider in development, but there are a number of guys out there using it.
Any issues let me know. Always looking to improve it.
Just to add, i have done a lot of testing with GPS chips. Most of cheap ebay ones are crap...
This one is the mutts nuts. Nothing else touches it...
I regularly get 20 sats in the air. Why so good - it uses combination of Russian and US sats.
http://www.supremefpv.com/naze32-naze32-full-apm-flight-controllers/mini-m8n-gps (http://www.supremefpv.com/naze32-naze32-full-apm-flight-controllers/mini-m8n-gps)
Worth the money. If you get one, make sure it says mini 8 on the module - an cirocomm on the antenna. Not all ebayers send the module in the picture. Annoying
for a stand alone mAH meter, what current sensor would i need? and would it work "plug and play", or would i need to do some programming?
Quote from: iPeel on July 29, 2015, 08:45:59 AM
Excellent, that means your Skyfun will get a satellite lock in less than an hour!
Ha! Well at the moment I'm using your ezosd, but it's doing an odd thing with the speed, the distance from home is fine. You can see on my last vid.
Thanks shacks, I'll have a go once they arrive.
Ched - Cleanflight is supported today. Need the latest dev for CF 1.9 release When ready drop me a mail.
ynot - almost all are supported. Suggest getting one of the APM ones.
This helps for configuring. There is a drop down list click on cell "c10"
https://docs.google.com/spreadsheets/d/1-NRiG__0Ym1Sw__0UR1on3XKo4--my3V4uDAUEjcMrk/edit#gid=0
You can also try the virtual one - its pretty good for multicopters....
next dumb question, can the minim "talk to" the eagle eyes to use the tracking function?
Unfortunately not possible.
shame that.
Mine have just arrived. .. bloody tiny! Better not sneeze around them!
I can always solder it up for you :) - just ask Neil :laugh:
Think I'll manage! Thanks!
Got it all flashed and configured from the gui, just need to find my gps and get that hooked up.
Can't get over how tiny this thing is!
Yeah
they are tiny!
Not sure what version you put on but first 1.5 pre-release is out.
Only one issue raised for legacy support of Harikiri - so its looking like I will release it as full R1.5 end of the week.
https://github.com/ShikOfTheRa/scarab-osd/releases
and feature s/ changes to see if its worth updating are here:
https://github.com/ShikOfTheRa/scarab-osd/blob/master/OTHER/DOCUMENTATION/Features.md
Just put 1.4 on there, I'll do 1.5 later, thanks for the heads up.
Shikra can your code be used on the minimosd , but with an APM ?
rather than using minimosd extra which looks a bit chunky and clunky in comparison
Currently supports:
MULTIWII
BASEFLIGHT
CLEANFLIGHT
HARIKIRI
NAZA
+STANDALONE GPS only
APM planned for later in year - sorry!
OpenPilot - uncertain
Just ordered one of these.. anyone got a link to a suitably tiny current sensor? or I have one kicking about somewhere from my old feiyutech hornet. will that work? And I bought it preflashed to work as a standalone OSD. how do I calibrate whatever current sensor I buy.. the hornet one never read right when it was in use but the hornet had no way to calibrate or offset it..
Oops, after much setup and anticipation, I managed to fry mine today by cocking up my power connection from my Naze - reversed the gnd/5v and it popped. So, er - don't do that :)
Just ordered another one, so it'll hopefully be here by the time MadDogs rolls around
Arse, can anyone help - I can't understand what I've done wrong. I've got a new OSD through after blowing the first one, so connected this one a bit more carefully. The result is - absolutely no text at all, but it's passing through the video, and will happily connect in the MW_OSD GUI.
The order of stuff was that I compiled the MW_OSD 1.5 software in Arduino, just changing a few things in config.h like
#define WITESPYMICRO
#define CLEANFLIGHT
This uploaded ok, then I connected it on the GUI and set out what I wanted to do. Very simple showing the flight mode, voltage, timer and RSSI
My wiring on the board looks like -
(https://farm1.staticflickr.com/757/20855338143_798e9e42fa_c.jpg)
Obviously the outside connections on the servo plugs are redundant, but it's obviously getting in the power ok, and even is tx/rx was reversed on my Naze32 board, it should still get something (and I did try it both ways)
The white cable soldered on is the video in from my camera), the black is the ground to the vtx and the red (weird colour choice I know) is the video out. The reason the ground is connected is that I read that some people reported losing the picture on throttle up and this could help. I've tried it without the ground as well. The yellow cable is my RSSI connection.
Have I missed something in the setup steps, or can anyone see something wrong ?
this is the reason I will NEVER attempt anything with APM ever again lol, I like things that "just work" :)
Quote from: CurryKitten on September 17, 2015, 12:30:41 AM
Arse, can anyone help - I can't understand what I've done wrong. I've got a new OSD through after blowing the first one, so connected this one a bit more carefully. The result is - absolutely no text at all, but it's passing through the video, and will happily connect in the MW_OSD GUI.
The order of stuff was that I compiled the MW_OSD 1.5 software in Arduino, just changing a few things in config.h like
#define WITESPYMICRO
#define CLEANFLIGHT
This uploaded ok, then I connected it on the GUI and set out what I wanted to do. Very simple showing the flight mode, voltage, timer and RSSI
My wiring on the board looks like -
(http://farm1.staticflickr.com/757/20855338143_798e9e42fa_c.jpg)
Obviously the outside connections on the servo plugs are redundant, but it's obviously getting in the power ok, and even is tx/rx was reversed on my Naze32 board, it should still get something (and I did try it both ways)
The white cable soldered on is the video in from my camera), the black is the ground to the vtx and the red (weird colour choice I know) is the video out. The reason the ground is connected is that I read that some people reported losing the picture on throttle up and this could help. I've tried it without the ground as well. The yellow cable is my RSSI connection.
Have I missed something in the setup steps, or can anyone see something wrong ?
Have the fonts definitely installed correctly?
Ok, that's potentially useful, as my initial response to that is "what fonts". I followed the stuff from here https://github.com/ShikOfTheRa/scarab-osd/blob/master/OTHER/DOCUMENTATION/FirmwareFlashing.md
Do I need to go and flash fonts over from the GUI before anything will happen ?
Yes fonts need uploading from the GUI and they don't always upload proper even though the display shows it uploading. I have to power the board with 12v as well as being connected to usb to get them to upload right everytime
Quote from: SupremeFPV on September 17, 2015, 01:29:06 PM
Yes fonts need uploading from the GUI and they don't always upload proper even though the display shows it uploading. I have to power the board with 12v as well as being connected to usb to get them to upload right everytime
12v on this microminim ?? That would generally make it go pop, i know you need to do this on the regular minim osd, but that actually has a 12v side to it. i don't believe this micorminim does ?
I ordered two of these from banggood.... as they look awesome and small footprint...
Turns out I accidentally ordered 22!!!!! Damn keyboard!
They are great and now my go to OSD. 22, I'll buy one off you!
Quote from: Brucey on September 17, 2015, 02:05:45 PM
They are great and now my go to OSD. 22, I'll buy one off you!
Yeah when they arrive I'll be sticking them up on here.
Quote from: CurryKitten on September 17, 2015, 01:34:39 PM
12v on this microminim ?? That would generally make it go pop, i know you need to do this on the regular minim osd, but that actually has a 12v side to it. i don't believe this micorminim does ?
sorry I meant I put power to the battery monitor pin as well connect usb
Try this - FAQ #2 - I have nothing on my display?
Ensure your cabling is correct
Ensure your PAL/NTSC OSD setting matches your camera setting. (try the other - don't always believe camera label !)
If using MinimOSD board make sure your output stage is properly powered.
Ensure you do not have blank screen layout selected
If using 3 way switch try different position
If using FRSKY or other high frequency RSSI, unplug until resolved.
Quote from: CurryKitten on September 17, 2015, 12:30:41 AM
Arse, can anyone help - I can't understand what I've done wrong. I've got a new OSD through after blowing the first one, so connected this one a bit more carefully. The result is - absolutely no text at all, but it's passing through the video, and will happily connect in the MW_OSD GUI.
The order of stuff was that I compiled the MW_OSD 1.5 software in Arduino, just changing a few things in config.h like
#define WITESPYMICRO
#define CLEANFLIGHT
This uploaded ok, then I connected it on the GUI and set out what I wanted to do. Very simple showing the flight mode, voltage, timer and RSSI
My wiring on the board looks like -
(http://farm1.staticflickr.com/757/20855338143_798e9e42fa_c.jpg)
Obviously the outside connections on the servo plugs are redundant, but it's obviously getting in the power ok, and even is tx/rx was reversed on my Naze32 board, it should still get something (and I did try it both ways)
The white cable soldered on is the video in from my camera), the black is the ground to the vtx and the red (weird colour choice I know) is the video out. The reason the ground is connected is that I read that some people reported losing the picture on throttle up and this could help. I've tried it without the ground as well. The yellow cable is my RSSI connection.
Have I missed something in the setup steps, or can anyone see something wrong ?
Well that's a real RTFM job - sorry, I was looking in the main documentation part and didn't notice the FAQ, I unplugged the FrSky PWM RSSI and I had text. Messed up text, so I uploaded the font from the GUI and all was well.
So thanks very much Shikra. I wasn't too fussed about the RSSI anyway, I mostly wanted the ability to be able to tune the pids easily on the go, and that works nicely.
Haven't flown it yet, but I was getting the lipo power via the FC, does that work ok... I could certainly take a ground/power from my PDB, but didn't want to add extra bits of soldering in if I didn't have to
No worries - it got me too once. That's why I put it in the FAQ ! Going to amend the code to stop this at some point.
Anyway - RSSI - best to make an lc filter to turn it into analogue. FRSKY is non std PWM - too fast for the Minim hardware.
Not sure if the NAZE can read it as PWM - might be an option
For power, I often run my OSD from the FC 5v
Cheers, That would explain why I couldn't get a nice normal RSSI PWM looking display on my little scope (I just figured I'd put it together wrong)
The power thing, what I meant is that I set it to get the battery voltage from my FC. So my lipo is connected into the voltage connection on my Naze so it beeps when it hits 3.5v per cell. So I'm letting that get passed into the OSD to read... which certainly appears to get a reading, although I haven't flight tested it yet. Just checking to see if there were any gotchas from doing that
Nope - dead easy. Just enable the "use FC" option. Note it will use the warning voltage set on the OSD - not in the FC
It's like a sickness, if I'm not making a video for YouTube, then what's the point :) Anyhoo, a few teething troubles for me, but this is bloody excellent
! No longer available (http://www.youtube.com/watch?v=-I_H-TgwIX0#)
Ive been using these OSD's for a while but with a different firmware.
(http://s23.postimg.org/s1jkuc0uv/DIY_osd.jpg) (http://postimg.org/image/s1jkuc0uv/)
This firmware is by Dennis Frie.
Very configurable.
http://www.rcgroups.com/forums/showthread.php?t=1776186 (http://www.rcgroups.com/forums/showthread.php?t=1776186)
Its more of a stand-alone OSD which looks a lot like EZosd but for around £5 + a GPS unit it gives me speed & a home arrow.
I've been using Denis osd as well, it seems to work well :-)
Probably a bit cheeky, but MWOSD has a number of predefined screen layouts. One of which is same as EZOSD!
Even better with ha vid CK!
Anyone got any ideas what might be wrong if I'm get no video at all being passed through the board?
This was my own stupid fault, just got some connections reversed. Got it all hooked up and working now, however one small issue I have is that I can't seem to connect the Naze board to the Cleanflight configurator if it's also connected to the OSD, very strange.
both can't use same serial port at same time. Either have to unplug, configure another serial port or use soft serial.
Basically CF settings and right pin connections!
Personally I just unplug....
Cool, ta. I'll just unplug it then, I'll hardly ever be doing now that I can tweak PIDs through the OSD anyway.
Hey I just flash my minim micro OSD with MWOSD 1.4
I know it talks nicely with NAZE32 (not full) but I can't turn ON side bars and artifical horizon at all.
Everything else like voltage,naze modes,timers are working OK.
Any tips what I do wrong and what I should change.
Try turning ON/OFF in MWOSD GUI with no luck ..
Have you selected a layout where they are disabled?
In brief -
Select layout you prefer
Go into layout editor
Run through and enable / disable the display options you want.
BTW, Upgrade to 1.5 it has support for later versions of CF/BF etc.
Quote from: Shikra on October 23, 2015, 10:29:02 PM
Have you selected a layout where they are disabled?
In brief -
Select layout you prefer
Go into layout editor
Run through and enable / disable the display options you want.
BTW, Upgrade to 1.5 it has support for later versions of CF/BF etc.
Thanks Shikra.
I just upload MWOSD 1.5 , but was only able to do this with Arduino 1.0.5.
Not working when using 1.6.5 latest version arduino.
Got nice artifical horizon working now :) , new bold fonts are great !!!
I suppose that side bars need full naze32 with baro ?
Brill ! Glad you like. There is also a 1.5.1 beta test release available with a few extras. Anticipate R1.6 will be out in 6-8 weeks.
I'll take a look at the latest arduino - frankly it's a pain keeping it so it will compile across all versions. grrrr
for sidebars - they can be enabled with any FC type
If there is baro or gps then get scrolling for altitude change
If there is GPS, can get the other side scrolling for speed change
Cheers!
Try to upload 1.5.1 ,all goes nice, then I can use MWOSD GUI but trying to upload Layout stop them at 30% and does no go further.
It's reading from OSD board...
Still using 1.0.5 Arduino :)
got one of mine to update mwosd 1.5 and using ftdi with arduino 1.6.6. but i get no osd overlay cam says pal and set osd to pal in gui. with no joy. even set to ntsc just incase. vid perfect no osd?
had a major prob with older versions just could not flash it via ftdi or uno. so gave up for few months
one of the 3 i bought is dead for sure.
fc is naze 32 acro , with frsky 4channel with rssi on pin 2 ppm.
Have you got the RSSI connected from the FrSky rx to the board - if you have a look at the last page, you'll see I posted a picture of mine and it turned out that the RSSi connection was messing things up. I removed it and got the OSD to display
Quote from: Pr][nCe on January 30, 2016, 08:43:16 PM
got one of mine to update mwosd 1.5 and using ftdi with arduino 1.6.6. but i get no osd overlay cam says pal and set osd to pal in gui. with no joy. even set to ntsc just incase. vid perfect no osd?
had a major prob with older versions just could not flash it via ftdi or uno. so gave up for few months
one of the 3 i bought is dead for sure.
fc is naze 32 acro , with frsky 4channel with rssi on pin 2 ppm.
yes same setup.
removed from pin 2 but still no osd.
Just ordered a MinimOSD to add to my 250 and stumbled upon CurryKittens video which will be a great help.
I have never used FTDI before so I am going to have to learn from scratch, but bought one of these which I think is right:
http://www.ebay.co.uk/itm/281769976434?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT (http://www.ebay.co.uk/itm/281769976434?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT)
But I have a question.. At 5:20, the video starts talking about "config" but there is no mention of how to connect the PC to the MinimOSD..
Is this done using the FTDI programmer? Or do you now connect via the NAZE?
Obviously the FTDI adaptor is used to flash the firmware.. But do you use it to "configure" the OSD too?
Jon
This is all done using the FTDI adapter plugged into the OSD board. When you download the MW_OSD firmware to upload to the board via the arduino software you'll see the source for the firmware and a folder called MW_OSD_GUI which will contain a bunch of launchers depending on what OS you are running on.
I didn't go into detail about connecting up the FTDI for this one as it's going to depend on OS and I'm on OSX (whilst most people are probably on windows) but basically, as long as you have all your appropriate drivers you should plug the FTDI card in the OSD board and the USB end into you PC and a com port will appear. UIn the GUI try connecting to that COM port and you should then be able to READ the config of the OSD (see OSD controls bottom left). It's then a case of using the gui to turn things on/off and then writing the config back again
Quote from: jweaver on March 11, 2016, 05:32:44 PM
Just ordered a MinimOSD to add to my 250 and stumbled upon CurryKittens video which will be a great help.
I have never used FTDI before so I am going to have to learn from scratch, but bought one of these which I think is right:
http://www.ebay.co.uk/itm/281769976434?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT (http://www.ebay.co.uk/itm/281769976434?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT)
But I have a question.. At 5:20, the video starts talking about "config" but there is no mention of how to connect the PC to the MinimOSD..
Is this done using the FTDI programmer? Or do you now connect via the NAZE?
Obviously the FTDI adaptor is used to flash the firmware.. But do you use it to "configure" the OSD too?
Jon
yes connect ftdi to the minimosd to flash and configure the osd - use the gui programm that comes with the firmware if using mwosd
Quote from: CurryKitten on March 11, 2016, 05:49:41 PM
This is all done using the FTDI adapter plugged into the OSD board. When you download the MW_OSD firmware to upload to the board via the arduino software you'll see the source for the firmware and a folder called MW_OSD_GUI which will contain a bunch of launchers depending on what OS you are running on.
I didn't go into detail about connecting up the FTDI for this one as it's going to depend on OS and I'm on OSX (whilst most people are probably on windows) but basically, as long as you have all your appropriate drivers you should plug the FTDI card in the OSD board and the USB end into you PC and a com port will appear. UIn the GUI try connecting to that COM port and you should then be able to READ the config of the OSD (see OSD controls bottom left). It's then a case of using the gui to turn things on/off and then writing the config back again
Cheers.. That was quick :)
i was only thrown as you said that you simply "touched" the FTDI connectors onto the MinimOSD which I can see working when flashing, but not when you want to do a bunch of configs.
So, clearly the header pins are going to be quite important such that you can connect a PC for a decent amount of time.
THanks for that.. I am sure I will work it out when it comes...
Jon
Quote from: jweaver on March 11, 2016, 06:03:28 PM
i was only thrown as you said that you simply "touched" the FTDI connectors onto the MinimOSD which I can see working when flashing, but not when you want to do a bunch of configs.
So, clearly the header pins are going to be quite important such that you can connect a PC for a decent amount of time.
Yeah - sorry if that was confusing. I was going to bypass the header pins and solder straight on. But after finding I needed to mess with the config several times, I soldered the headers on so I can easily unplug/replug the whole OSD to the naze32 and/or the computer
Quote from: CurryKitten on March 11, 2016, 06:12:28 PM
Yeah - sorry if that was confusing. I was going to bypass the header pins and solder straight on. But after finding I needed to mess with the config several times, I soldered the headers on so I can easily unplug/replug the whole OSD to the naze32 and/or the computer
No need to appologise.. I am overthinking it (Again)... . I think the headers are the way to go, but sad that it almost doubles its size/volume..
I am still struggling to understand the spec of the MinimOSD.. According to the seller, they state:
- Onboard 5V and 12V switching power supplies.
- Direct connections to naze when stacked.
- Cam and vtx 3pin headers with selectable 12v or 5v power from onboard regs.
- Can power naze and anything else attached to naze, so you can disconnect the red power wire from all escs.
- Onboard micro-USB plug for flashing/configuring your favourite OSD software. Anything that works on MinimOSD will also work on this.
- Voltage dividers for both battery sources (main batt/video batt voltage sensors).
- Series protection resistors for RSSI and current sensor connections. RSSI can be filtered from high-frequency PWM into an analogue signal by enabling the RSSI filter solderjumper.
- Extremely bright, blinding LEDs
"Onboard Micro-USB"? Thats not my understanding.
"Onboard 5v and 12v PSU"? I thought it had to be fed with 5V
And thne there is this whole business of it being "stackable" with the NAZE via direct connections.. I can't see how, as the layout does not match the Naze does it??
I wonder if they are mixing these details with another products?
The sounds very much like the description of the regular sized minimOSD, but not the micro -5v as you mention, and certainly no onboard USB.
You could technically solder a header onto the tx/rx pins on the naze and then onto the osd which would make it a little kind-of-stackable daughter board, but not very useful if you need to fiddle with it again.
Quote from: CurryKitten on March 11, 2016, 07:32:24 PM
The sounds very much like the description of the regular sized minimOSD, but not the micro -5v as you mention, and certainly no onboard USB.
You could technically solder a header onto the tx/rx pins on the naze and then onto the osd which would make it a little kind-of-stackable daughter board, but not very useful if you need to fiddle with it again.
Indeed.. Last question (for now), am i right in thinking that the pins used to flash/configure it, are the the same as used to get power and data from the Naze?
Yes - although there's a DTR pin as well for ftdi (which I haven't really thought of since ye olde serial modem days), but yeah, the Tx/Rx and 5v are the same
Just wonder there is mag cal option in MWOSD is that really for compas calibration in full naze for example ?
A question about powering the MinimOSD... All of the drawings I have seen, say to take power from the ESC connection on the NAZE.
See here:
http://www.unmannedtechshop.co.uk/micro-minimosd/ (http://www.unmannedtechshop.co.uk/micro-minimosd/)
But considering the Minim allegedly draws 500mA, is there really enough power to do this?
I believe the Naze gets its power from ONE of the ESCs in my setup.. So this means that the Naze AND Minim will be powered from the ESC and considering its only a 15A version, the ESC/UBEC is tiny and probably not up to the job.
That said, according to the spec, it says it provides 1A.
Would it not be better to get a separate 5v UBEC for the job?
Also.. Is this really the best place on the Naze to get 5v power? I already have header pins on the ESC connections, which plug into a "distribution board" on my 250 chassis.. So to connect it this way, I would have to solder wires to the top of the board.. Which is easily done, but not very neat.
Jon
My MinimOSD turned up today and I need to think about how to integrate it but I am still a little concerned by the power requirements... It clearly says here that it needs a 500mA supply:
http://www.hobbyrc.co.uk/micro-minimosd-for-naze32-with-multiwii-osd-kv-team-mod (http://www.hobbyrc.co.uk/micro-minimosd-for-naze32-with-multiwii-osd-kv-team-mod)
The suggestions I have read say to power it from the Naze.. But in my case, the Naze is powered from one of my ESCs which only provides 1A.
Does anyone know if the MinimOSD really takes 0.5A (Looking at its size, I find that hard to believe) and whether the combination of the Naze and MinimOSD is OK for a 1A ESC.
In my case, I have 3 other ESCs whos BECS arn't being used.. I am wondering whether its worth taking a feed from one of those instead? Thinking about it, I could do that I quite easily.. SInce the 5v output on the other 3 arn't even used, I could simply pull out the centre pin of the Servo connector and use that. Is there a problem powering different bits of kit from multiple 5v supplies?
Jon
when you've got many components that require 5v in your aircraft, it's a whole lot better to have a dedicated 5v supply from a standalone BEC or voltage regulator and not use any of the ESC BECs to power anything.
Also, it isn't a good idea to have different 5v sources powering the gear that all needs to be part of the same electrical circuit.
Quote from: BlueFlyer on March 29, 2016, 02:27:56 PM
when you've got many components that require 5v in your aircraft, it's a whole lot better to have a dedicated 5v supply from a standalone BEC or voltage regulator and not use any of the ESC BECs to power anything.
Also, it isn't a good idea to have different 5v sources powering the gear that all needs to be part of the same electrical circuit.
Thats what I was afraid of.. With hindsight, I would have built the quad with a dedicated BEC.. But its too late now.
I have 2 choices.. Run it from the same BEC in the same ESC and hope for the best (will do some measurements later to see how much current it draws).. But I need to bear in mind that the RX, Naze and MinimOSD will be powered by a single ESC which is only 1A
Or I might just see how I get on, by taking a feed from another ESCs BEC, and just try it....
Jon
Why is it too late to install a dedicated BEC? They're cheap and small. OK, it might mean some disassembly of your quad but surely that's worth it if it means avoiding a potential crash or failure of one of your 5v dependent systems.
I think you're looking for an easy way rather than the proper way.
Quote from: BlueFlyer on March 29, 2016, 03:04:20 PM
Why is it too late to install a dedicated BEC? They're cheap and small. OK, it might mean some disassembly of your quad but surely that's worth it if it means avoiding a potential crash or failure of one of your 5v dependent systems.
I think you're looking for an easy way rather than the proper way.
I am indeed looking for an easy way.. Its only a little 250.. if it were my Discovery, I would be willing to do a lot more.
The reason it would be difficult for me is that I am using a PDU:
http://www.banggood.com/NAZE32-Integrate-PCB-Board-Power-Distribution-Board-For-QAV250-ZMR250-Quadcopter-p-989404.html (http://www.banggood.com/NAZE32-Integrate-PCB-Board-Power-Distribution-Board-For-QAV250-ZMR250-Quadcopter-p-989404.html)
So all of my connections are done via headers, connected to the PDU.
To change the power, I would have to completely strip the quad and either cut some tracks on the PDU, or remove headers.. And its a lot of work.. I would rather not fit the MinimOSD if this was my only option.
I am still not sure I understand why its a bad idea.. I get the idea that it is bad, but the more I think about it, I don't know why.
Thinking about an old school AV setup, with composite video.. You didn't think twice about connecting a Sky box, to a VCR to a TV, all of which are powered by separate PSUs.. Or even connecting a Video Camera to a VCR, one powered off a PSU, the other batteries.
Other than potential interference, none of the devices blew up, or caught on fire.
So why exactly is there a problem, having different devices all running off different supplies.. I guess one concern is if the various 5v circuits touched, I can see that being a problem. But if the OSDs power was insulated and isolated from other 5v feeds, I am not sure I understand the issues.
At the end of the day, my camera and TX are powered from the battery.. And the Naze and RX are powered by an ESC BEC.. So thats 2 sources already..
Jon
Micro minimosd is very voltage sensitive I have powered it from the flight controller which was powered from a 2amp ESC bec and it would drop the OSD if I want above half throttle due to voltage sag,plus powering from a ESC bec can put noise into video.
Micro needs a regulated 5v I would power from a small bec.
I have done this with a separate bec powering flight controller GPS rx and OSD, all good no drop off OSD and no noise in video
Quote from: Hawkview on March 29, 2016, 03:50:40 PM
Micro minimosd is very voltage sensitive I have powered it from the flight controller which was powered from a 2amp ESC bec and it would drop the OSD if I want above half throttle due to voltage sag,plus powering from a ESC bec can put noise into video.
Micro needs a regulated 5v I would power from a small bec.
I have done this with a separate bec powering flight controller GPS rx and OSD, all good no drop off OSD and no noise in video
Cheers.. So just leave everything else as is.. And get a small BEC to power the MiniOSD?
What sort of current? 1A? Or 2A? Had a quick scan and the "mini" ones are more expensive than the MiniOSD.. Any recommendations as to what you used?
Jon
Edit: Actually, this looks OK.
http://www.banggood.com/DC-DC-Converter-Step-Down-Module-3A-5V12V-Mini-BEC-For-RC-Plane-FPV-p-936792.html (http://www.banggood.com/DC-DC-Converter-Step-Down-Module-3A-5V12V-Mini-BEC-For-RC-Plane-FPV-p-936792.html)
Quote from: jweaver on March 29, 2016, 04:32:28 PM
Edit: Actually, this looks OK.
http://www.banggood.com/DC-DC-Converter-Step-Down-Module-3A-5V12V-Mini-BEC-For-RC-Plane-FPV-p-936792.html (http://www.banggood.com/DC-DC-Converter-Step-Down-Module-3A-5V12V-Mini-BEC-For-RC-Plane-FPV-p-936792.html)
Search eBay for "MP1584" and you can probably buy one or a pack of 5 from the UK much quicker, just without the wires and the heatshrink. You'll need to set the voltage using a volt meter and the little potentiometer. I guarantee that's what's lurking beneath that heatshrink.
Quote from: iPeel on March 29, 2016, 05:22:36 PM
Search eBay for "MP1584" and you can probably buy one or a pack of 5 from the UK much quicker, just without the wires and the heatshrink. You'll need to set the voltage using a volt meter and the little potentiometer. I guarantee that's what's lurking beneath that heatshrink.
Cheers.. I didn't think to search "DC-DC".. I never really like the idea of the ones with pots, as they could get knocked out of adjustment.. All of the ones i have used before have been set with fixed resistors.
But I don't really want to wait and will have a crack with one of those.
Thanks.
Quote from: jweaver on March 29, 2016, 05:30:38 PM
Cheers.. I didn't think to search "DC-DC".. I never really like the idea of the ones with pots, as they could get knocked out of adjustment.. All of the ones i have used before have been set with fixed resistors.
But I don't really want to wait and will have a crack with one of those.
Thanks.
I always use a dab of hot glue on the pot once it's been set, but I bet those ones on BangGood plus a whole lot more have the pots on them with nothing but heatshrink holding them in place.
I've got my MicroMinimosd powered off one of the unused ESC Bec outputs on my 250 and it seems fine just as long as the grounds are all the same. As mentioned a seperate Bec would probably be better as there's less risk of noise on the video.
Does that PDB frame thingy not have a 5v to power everything through instead of using the ESC's BEC ?
On mine original 3s based 250, everything is running off the BEC on a single ESC, but I'm very much in the try-it-and-see-if-it-explodes camp. My 4s quad (which is still in build after a long time) does use a seperate PDB with a 12v/5v BEC on board to power the rx/naze/osd - but that's mainly because the ESC's are opto's
Quote from: CurryKitten on March 29, 2016, 11:32:38 PM
Does that PDB frame thingy not have a 5v to power everything through instead of using the ESC's BEC ?
On mine original 3s based 250, everything is running off the BEC on a single ESC, but I'm very much in the try-it-and-see-if-it-explodes camp. My 4s quad (which is still in build after a long time) does use a seperate PDB with a 12v/5v BEC on board to power the rx/naze/osd - but that's mainly because the ESC's are opto's
Yes and no.. The PDB doesnt have a BEC onboard. Instead it simply takes 5v ONE of the ESCs and uses that to power the entire quad.
This means that the 5v output of the other 3 ESCs go nowhere and are not used.
One thing i am considering. I could install a BEC and connect it to the PDB on the ESC input which is currently used for power..
This way, none of the ESCs would be used for power and a more poweful BEC could provide more power than i need.
I am going to do a few experiments to see how that goes...
Jon