Thread Tools
Feb 21, 2011, 05:56 AM
quadcopters & FPV padavan
Rurek's Avatar
Thread OP
New Product

OSD for MultiWii/DJi/Mikrokopter

I'd like to present a new oryginal solution developed for ArduWii-copter - OSD with datalogger and artificial horizon, dedicated to Alex's MultiWii FlightController. This equipment has its own proprietary firmware, adapted to cooperate with software MultiWii, where you can find FULL compatibility and functionality with official release of MWC, published by Alex. MultiWii code has a full support for this OSD since 1.7 MWC release.

Now Misio-OSD have full support for DJi's products like WKM or NaZa (v1 and V2)

In this first worldwide MultiWii OSD with datalogger and artificial horizon you can find:

1) Opportunities when connected to the FC without GPS module:
-Read the angle and view the "artificial horizon"
-FC angle of rotation (course) only if FC have Magnetometer installed
-Height (if on the FC is mounted pressure sensor)
-Variometer bar (only with pressure sensor)
-Battery voltage drive (data taken from FC)
-Video voltage battery
-The time from power on
-Flight Time
-Analog RSSI taken from RC receiver (works only with some models with given RSSI signal)
-Current consumption and battery consumption in mAh (required external current sensor, sell as option)
-Logger for flight data to the SD/MMC card
-Acoustic variometer
-Alarms sound configurable from the menu on the voltage, current consumption, height ect.
-Visual alarm indication (blinking of the value).

2) If the OSD connected with GPS receiver then additionally gain:
-Height with GPS
-Variometer (data taken from GPS)
-Rate of the base (arrow toward the base)
-The distance from the base
-Number of satellites visible
-Alarm to cross a given distance
-Store the "base" position at the engine arm
-Display statistics from the flight after disarming engines.

Misio-OSD has on-board filters for power video transmitter and cameras - Video output voltage has max load 0.8A (eq video transmitter with 1000mW output power can handle).
I have also offer GPS receivers, there is an extra battery retaining power in the GPS clock after disconnecting the main power. This allows you to catch sattelite FIX within 10 seconds after changing the LiPo package - if the time from disconnection to reconnection package will not exceed 30 minutes.
Connector for the GPS output is consistent with the order in the receivers used for the Remzibi's OSD and works with these receivers (small receivers ICC).
Now we develop a graphical analysis of flight data recorded in the logger. You can import data log with small provided program to graphical representation in , for example google maps.

The regular price of this OSD, only for RCG members is:
- standalone OSD (without GPS receiver) 110
- GPS receiver 20
- current probe- device that measures power consumption of LiPo 20
- CAN-interface - needed to connect OSD with DJi's products 40
- complete set (OSD+GPS+Current probe) 130
- DJi's ver set (Misio-OSD and CAN-interface) 140
In addition, I can sell a FTDI/USB interface (if you use an arduino nano or other board with interface built onboard that useless for OSD purpopse to communicate beetween OSD and PC) with price of 15 standalone.

All stuff is available thru my PM. Payment via PayPal.


Connectors on the board of the OSD.

~ Debug Port connector. This connects to the serial communication pins on the FC (flight controller) board using 3 wires. The Debug Port has 10 pins, for MultiWii we only use 3 of the upper pins, the lower 5 pins are unused. RXD, TXD and GND connect to the pins on the Arduino which are normally used to connect the FC to the computer (if you use an FTDI interface / USB), alternatively they can be soldered directly to the pins on the Arduino.
~ VID_TX connector. This connects the OSD to a video transmitter. The transmitter must be able to accept a 12V input. If the device requires 5V then you will need to use an additional voltage regulator (Eg LM7805)
~ Camera Connector. This port is used to connect the camera and an optional microphone. As above, if the camera requires a 5v supply then an additonal voltage regulator will be required.
~ RC_CTRL Pin. If the signal / pulse output from a spare Rx channel is
connected to this pin then it will serve as an on / mode switch to change the OSD display during flight.
~ GPS connector. Used to connect the GPS receiver. We Recommend that a "small" GPS with an MTK chipset is used. The GPS operates at a frequency of 4Hz. The connector (and whole OSD) is compatible with the GPS receiver used in Remzibi's OSD.
~ CURR_PROBE connector. Here you can connect a current sensor to monitor power consumption from the battery. The sensor output can be either positive or negative. A current sensor is optional and can be purchased separately.
~ RSSI connector. This connector has 2 inputs and is used to display RX signal strength. Normally we only use IN_1 (or IN_2), and set the appropriate input in the OSD menu. In the menu you can also select 'dual mode' which can be used if you have a dual receiver (diversity) in which case both inputs can be used. In dual mode, the OSD will display the RSSI value of the stronger signal. RSSI signal may be positive or negative, this is not important. The RSSI signal type will be recognised when it is calibrated from the menu.
~ And last but not least - Power connector. We recommend powering the OSD board from a 3S lipo. If using a 4S flight battery then either use a separate battery to power the OSD, Vtx and camera, or take 3S voltage from the 4S balance plug, or use an external 12V regulator. Current consumption of the OSD without GPS is approximately 110mA, and with GPS receiver - 160-170mA.

Calibration of signals :RX RSSI, current sensor and video tx battery voltage.

To calibrate the RSSI indication for the OSD you must first connect the RSSI signal from your RC receiver. The RSSI signal voltage from the receiver should be in the range of 0 to 5V. To start, go into the osd menu -> Service Menu -> Analog RSSI calibration. Now, as described on the screen, turn off the RC transmitter, wait until the displayed value has stabilized and press any button on the OSD. Now, follow the onscreen instructions and switch on the RC transmitter, wait for values to stabilize and then press any button on the OSD. At this point, the RSSI calibration procedure is complete and you can exit the menu.
To calibrate the current sensor connected to the current probe pin of the OSD you must first prepare some equipment. You will need a 3S LiPo (or AC power source that can manage an output current of at least 10A and voltages from 10-14V), a second 3S LiPo to use as a temporary supply to the OSD, an ampmeter/wattmeter capable of measuring at least 10A, and a load that will force a current value of 10A. As the load you can use several automotive lamps connected in parallel with a total power capacity of about 100W, or an ESC, motor and propeller that can provide a 10A load. You can also be used your whole MultiWii copter, but you will need to find a safe method of immobilising the copter to make sure that it cannot move, takeoff or cause injury during the calibration process .
During the current sensor calibration process it is recommended that the connection between the OSD and the FC is removed. First, connect the current sensor. Connect the signal (I) and GND wires from the current sensor to the current probe input on the OSD, and the wires from your main lipo to the current sensor (+ hole to positive lead from the LiPo). The "-" hole of current sensor is left disconnected, not loaded. Then supply power to the OSD from a separate, small "second LiPo". With the OSD output displayed go to MENU-> SERVICE MENU-> Current probe calibration. Firstly we calibrate zero current. You should see a stable value displayed (depending on the type of sensor the value could be near 0 or 10000), then press any button on the OSD. Now we have to connect a load to "-" hole of the output sensor. If you use an ESC and motor as a load, or the whole copter, run the motor(s) and try to obtain the exact current of 10A (watch the display of your ampmeter/wattmeter). If you cannot obtain an exact 10A, set a bit more, and wait for the current to drop as the voltage of the main battery decreases.
As soon as the ammeter/wattmeter displays exactly 10A again press the button on the OSD. Calibration of the sensor is now complete, we can exit the menu and compare the OSD ammeter indicator with the ampmeter/wattmeter. Both dispays should be identical.
Calibration of the video system voltage readings is only possible by means of the OSD configurator program and an SD card. Although all OSDs are factory calibrated before shipment, if you get false readings then you can/must do the calibration.
To calibrate the video battery voltage connect the OSD to your video FPV system, compare the OSD indication of the voltage with a voltmeter connected to the LiPo and if we find differences, then proceed as follows: put the SD card in the OSD and select the service menu option "Export settings" to transfer the settings to the card. Then insert the SD card into a card reader connected to your PC. Run the program OsdCfg.exe, select "Open" and load the "SETTINGS.BIN" file from the SD card. Then click the "Settings" button. Click the 'Settings' button and a second window will appear, the setting we are interested in is the value of "volt calibrate". The default value is "180". If the OSD shows too much voltage, this value should be increased, and if too small we can try to decrease it. An increase/decrease of the value by 2 changes the voltage indicated by about 0.1V. After entering the appropriate value click "Apply" and then "Exit". The settings window will close, and now in the main window, click "Save". Transfer the SD card back into the OSD and from the "Service Menu" select "Import Settings". The OSD's LED will blink yellow, reboot, and from that point the OSD will use the new calibration values, which should result in a proper voltage indication.
Remember that this procedure of video voltage calibration has initially been done in factory.

Buttons on the OSD.

A short press of the SW1 button can manually save the base position (instead of automatically when you start engine).
A short press of SW2 after landing will turn off the display of statistics from the flight after landing. Stats are also reset automatically one minute after landing. A long press of SW1 enters the OSD MENU. Inside the menu, pressing SW1 will cycle to the next option (a long hold will Autorepeat the key) and pressing SW2 selects an option or changes the selected parameter. Here, too, Autorepeat works, so holding SW2 causes cyclical changes in the parameter.
A long press of SW2 will change the video mode from PAL to NTSC and vice versa. If the monitor shows an image from a camera, and you do not see the OSD, press and hold the SW2 button. You should receive the appropriate message about the current video mode.
In the firmware we have also added a feature that automatically detects and switches to the correct video mode (PAL/NTSC). Immediately after powering on, the OSD checks the parameters of the signal from the camera and if the OSD mode is different from the camera, the OSD mode changes to the correct signal.

SIMULATING SW1 ad SW2 via the transmitter sticks
You can control the OSD with the sticks of the transmitter. If the copter is disarmed, and the engines turned off, the pitch/roll stick is able to emulate the OSD buttons. Tilting the pitch stick down emulates the MENU / NEXT button, moving it to the right emulates the ENTER button. For example, we can enter the menu by moving the pitch stick down for 2 seconds, the menu will then appear on the OSD. Now, by moving the pitch stick we can scroll through the menu, tilting the roll stick to the right to enter into the option. Likewise, to delete the statistics from the screen after landing we can just move the roll stick to the right.
Warning! Since the original code MultiWii motors arming function is implemented using the roll stick, to be able to operate the OSD menu with this stick, first you must change the following lines in the sketch:
if ( (rcData[YAW] < MINCHECK || rcData[ROLL] < MINCHECK) && armed == 1) {
to this one:
if ( (rcData[YAW] < MINCHECK) && armed == 1) {
and also this old one:
} else if ( (rcData[YAW] > MAXCHECK || rcData[ROLL] > MAXCHECK)
with this:
} else if ( (rcData[YAW] > MAXCHECK)
If you don't do this, be careful - roll stick movement causes arming motors if the gas stick is at minimum position! And setup OSD via stick isn't functioning.
Of course you don't have to do these changes in code but YOU MUST REMEMBER - the gas stick must be above minimum position...for security reason I prefer change in code...It's easy to forgot gas stick position

Status LEDs

The OSD is equipped with three LEDs to indicate its status.
- Green LED lights up when everything is OK and the OSD is working correctly. When you initiate the GPS receiver, the green LED starts flashing. It will blink as long as the GPS does not obtain a satelitte FIX from at least 5 satellites (this is the minimum amount that allows you to save the position of the base). So as long as the green light is blinking - we have to wait, when it stays lit permanently you can start and correctly store the position of the copter's base.
- Yellow LED flashes when receiving data from the FC, which during normal operation should be blinking. When the OSD is in "menu" mode receiving data is blocked so the LED will go out. Exceptions include - while defaults settings are loaded, when settings are read from an SD card, a new set of characters are imported, or when software is updated (in its first phase, which is to reflash OSD's CPU), and if you are operating the menu by using TX sticks.
- Red LED blinks when sending data requests from OSD to FC, and at when writing to SD card (for example, writing a LOG file to the card). So the blinking red LED is normal. If the red LED stays permanently on, it means an error, usually these errors occur when logging to an SD card (card is full, bad contacts ect.) In this case, the green LED also goes out. But If only red LED lights up - it means activate any of the alarms.

SD card operations.

The OSD board has a slot for an SD / MMC card. Cards with capacities ranging from a few MB to a maximum of 1GB are supported. The card must be formatted with the FAT16 file system. If not, then when you start the OSD the status of the card will read "NOT FAT16". If it is correct, then the status shows "OK". If you format the card with a low capacity (tens of MB) then sometimes M$ Windows will format it as FAT12 and not FAT16. There is a simple way to avoid this. You must use the command line to format the card. Click Start-> Run-> type cmd -> OK. Then in the window type: format z: /X /A:1024 Replace "z" with the drive letter of the card reader on the PC.
The main function of the card is to record flight data for later analysis. Each time the copter is armed a log file is created "LOGxx.CSV" which contains all the parameters received from the FC, plus data from the GPS (if you have a GPS receiver). Each log is saved as a CSV file which can then be opened in a spreadsheet (like Excel, etc. ..) The relevant software for Multiwii data visualization is under construction. Currently we have a cute little program called "SticksPlay" which shows us the movements of the TX sticks from a logged flight.
Files are created in the root directory of the card and have ascending numbers - from 00 to 99, which allows up to 100 flights to be stored on a card. If the card is full, an appropriate message is displayed when the copter is armed, and a new log file is not saved. This applies if the number of log files exceeds 100, or there is not enough free space on the card. If this is the case then you will need to delete some of the LOG files. The algorithm used to create the next file is simple: it checks whether the file LOG00 exists on the card, if not, it is created and stored. If it already exists then the next file is checked in turn LOG01, LOG02, and so on to LOG99. If the card already has files called LOG04 and LOG02 for example, they will not be overwritten by the next record, but omitted. If the OSD is connected to a GPS receiver and it receives satellite links then each log file will contain the date and time when the copter was armed (time is UTC, not local).
The SD card will also be needed to be able to customize the display layout to your liking, and if necessary to update the appearance of fonts (character generator in the IC MAX7456). To change your display settings you need to access the Service Menu and select "Export settings". This will save a file to the card called SETTINGS.BIN. Exit the service menu and insert the card into a reader on a PC. The SETTINGS.BIN file can then be opened with the "OsdCfg" program, the required modifications can be made, saved back to the card, and transfered back from the card into the OSD. To do this you need to access the Service Menu again and select "Import Settings". After importing the OSD will restart and should show your new settings.

Updating the Software.

To update the software on the OSD you need an FTDI/USB interface - the same type used to connect a MultiWii with a computer. However, you will need to prepare a system connector because the TX, RX, GND pins are laid out differently than an Arduino. The GND, TXD and RXD pins on the OSD debug port need to be connected to the corresponding pins on the FTDI/USB interface (GND-GND, data pins always crossed as TXD to RX and RXD to TX).
We also need the AVRFLASH21 program and the HEX file of the new software (I will send the HEX files of new firmware to any users by email).
Warning! If you want to preserve custom settings from the OSD then save them to an SD card before updating the software - use the "Export settings" option in the Service Menu.
First, download the AVRFLASH21 program and install it on your PC. Then, connect the USB interface, making sure the 3 wires are properly connected to the upper row of pins of the "debug port". Now connect a monitor and LiPo power to the OSD. Run the AVRflash program, use the "Port" Menu to set the COM port number to the one which corresponds to the USB interface, and set the 'speed' to 57600. Now in "Datei" menu select "Auswahl" and load the HEX file containing the new firmware. If when AVRFlash is loaded you receive an error relating to no library "bdertl60.bpl" then you must copy the file (from unzipped attachment) to the directory where you installed AVRFlash. In the OSD, go into the Service Menu, select "Software Update" and confirm. "Bootloader" will flash on the screen, and the LEDs on the OSD board will start flashing - red and green. Now in the program AVRFLASH click the "Flash" button to upload the software. It takes a few seconds, you will see a progress bar first - Blue (programming), then green (verification). After the update, reboot the OSD and the default configuration will be loaded and ready to work. There is an alternative way to run the update - in an emergency - it is equivalent to the method above without using the menu. Run AVRFlash, load the HEX file, then on the OSD press both keys simultaneously and while holding them pressed connect the power supply to the OSD. The screen does not display anything but the OSD LEDs will flash. Next click the "FLASH" button as above and wait for the firmware to upload, the OSD should now start normally with the new software.
Now, if we want to, we can restore our custom display settings. Loading the normal "Settings.bin" to the new firmware will not work, you will get the message "incompatible version ...". This must be done differently. Run the OSD Configurator program. Open the "settings.bin" file from your old version of the firmware. Now click on "Export" and save the exported file anywhere (on the card or on your PC). Now transfer the card into the OSD that has the new firmware and then Export the "Settings.bin" file from the OSD onto the card. This gives us the file in a format compatible with the new software. Now, insert the card into the reader on a PC, open a new file in the program, then click the "Import" button and select the exported file with our custom settings. Next, select the display settings to import from settings screen, and the main parameters (ie, alarms, calibration, ect), and we have now restored our settings. We can now check whether the new software has any new data on the screen and customise it if necessary. Then just click on "Save" which saves the new file "Settings.bin" on the card, transfer card back into the OSD and select the "Import Settings" option from the Service Menu. Now, the OSD will adopt the new settings and everything will be OK.

Audio channels in the OSD - acoustic vario and alarms.

The OSD outputs an audio signal that can be connected to the A/V transmitter. This allows the audio signal to be used as audible alarms and a variometer. Variometer has two modes of operation. The first outputs a pitch and repetition rate depedant only on the instantaneous rate of climb / descent. The greater the rate of climb the higher pitched and faster the sound, the faster the speed of descent, the lower pitched and faster the sound is. In the second mode, sound speed depends on the rate of climb / descent (the higher the speed the quicker sound), but the tone of the sound reflects the current height of the copter above the ground. With some practice this can be both two pieces of information - rising / falling, and the current height.
In the "Alarms setup" menu you can enable an audible sound for any given alarm, for example, if the copter goes beyond the prescribed distance limit, or when the battery voltage drops, then instead of the vario you will hear alarms. This is a quick high pitched sound lasting two seconds followed by a 4 second pause (in which time the vario can be heard), and then again a two second alarm sound, this continues until the source of the alarm is rectified. There may be several alarms active at once. The cause of the alarm can be identified on the OSD screen, because the parameter will start flashing on the screen. Acoustic alarms work even when the parameters are hidden on the screen - if we enable an audio alarm for an item, and it is set as invisible, it's alarm will cause that item to be dispayed on the screen. If you create your own screen settings it should be remembered that even the invisible elements can cause collisions with visible ones, because alarms can cause them to be displayed. It should help that the latest OsdConfigurator shows invisible elements in gray and collisions with them in yellow.
Use the "Alarms setup" menu to set the thresholds for each alarm, and select which of them can trigger audable alarms. If the copter is equipped with a microphone, then the sound is mixed between the MIC and VARIO and ALARMS so all these sounds can be heard.

DJi's Wookong M and NaZa support - connectors and configuration

Currently sold version 2.0 of Misio-OSD has added support for FC's DJi. For this purpose, the bootom side of the OSD include two jumpers JP1 and JP2 which must be properly configured depending on the FC which cooperates with OSD.

For each FC jumpers should be made as follows:

- MikroKopter - JP1 and JP2 open (must be!)
- MultiWii - No matter, they can be combined or not
- DJi Naza v1 or Naza Lite - open JP1, JP2 closed
- DJi Wookong M and Naza v2 - closed JP1, JP2 open

Connections for NaZa v1

To connect the OSD to the FC board is required for cable set shown in the attached picture. But it will be better to buy DJi's PMU v2 and a new interface : CAN interface to connect OSD with DJi's FC. In this combination OSD works better and has all options and features.

But if you have only NaZa v1 you can connect OSD with FC this way:
EPX plug port is put into the EXP in the Naza, and a GPS recieiver connected to the socket described as GPS. this way data is retrieved from the GPS and the magnetometer.
Insert the M1 plug into the output M1(for Motor1) in Naza and put Motor1 socket cable from the ESC of the first engine. In this way, the OSD gets info about running engines.
Insert the X3 plug into the connector Naza's X3 and connect cable marked as "PMU" to the Naza's socket PMU which originally was connected to X3. In this way, OSD gets the battery voltage which is given to the OSD board on pin next to the RSSI pin. The picture shows the location (center pin plug) where you can plug the RSSI signal from the RC receiver (marked as red arrow).
Plug F1 and F2 to the output signal pins F1 and F2 in the Naza. If you going to use gimbal with Naza, you need prepare two Y-cables (not delivered in package), one end of Y-cable will be put into the F1 and F2 Naza, doubled-paired pins of the Y-cable will connect servo of the gimbal, and plug second to F1,F2 - respectively of the OSD (for the signal pin). This way the OSD gets information about pan/tilt for visualize the artificial horizon and the corrections for magnetometer.

The rest (camera, transmitter, power supply, control of the RC, current sensor) connected in the same way as for the other FC. GPS connector on the OSD board is left unconnected. Cable connector with signals from FC to be inserted into an OSD this way: the yellow wire was on the lower side of the OSD pins, and the remaining four cables at the top row.
Now that we are all connected and secured to calibrate the readings of the OSD.

At the beginning connect Naza to your PC and activate the Naza gimbal in software.
Recommended settings in the options gimbal:
Gain: 20.00, servo travel: 1000, 0, -1000, servo refresh: 50 or 100hz.
Save setting and Turn off the power, and go to the OSD configuration stage.

Re-attach the power, will see the image on TVset/googles/monitor. Look forward to the disappearance of the start-homesscreen which should detect and display the "Naza GPS".

After proper initialization you should enter the OSD menu. Turn ON the option "Artif. Horizon" and "MotBatt. Input" and the option "Course source" set to "MAG". Exit the menu.

Magnetometer calibration you should perform step outside, away from metal objects interfering with the compass.
From the OSD menu select "SERVICE MENU" and the "Level + Compass calibration" and you should make 5 steps requested by OSD and after each one you will be asked to press any button on the OSD:
Step 1 - place copter perfectly level - for storing level horizon (confirm button on OSD)
Step 2 - copter tilted about 45 degrees to the axis ROLL, right
Step 3 - copter tilted about 45 degrees to the axis of pitch, head upwards
Step 4 - hold copter as horizontally rotate it in the yaw axis from 3 times to 360 degrees (in either direction). At OSD minima and maxima can be seen, the red LED flashes and beeps can be heard in the audio channel, and captures value (like the compass calibration in MK).
Step 5 - copter rotate vertically (horizontally holding any two opposite arms) in a north-south axis. You can swing a whole in any direction as cheerleader with tassel :-). The last time the confirm button and the calibration is completed, saved and would rather not have to repeat it anymore.

Now you can check if everything is working properly. That's all.

Connections for DJi's Wookong M or NaZa v2 (or v1 with PMU v2)
If you going to use Misio-OSD with WKM or NaZa v2 you should check this:
If the OSD is working with DJi's Wookong M or Naza v2 are practically available all the possible options (including menu- sticks support for OSD).
Connecting the Misio-OSD with DJi's FC is simple. Plug the CAN-interface with 10 pole connector to the OSD debug-port so that pin 1 of the connector is facing the buttons on the OSD. On other side of CAN-interface attach 3-wire plug to an available CAN-port in DJi's ( GPS or PMU ) or PMU v2 for NaZa. The rest ( cam , transmitter, current probe, etc) will be connect the same way as usually (described in other chapter of manual). GPS connector on the Misio-OSD is left unconnected . During operation, the red LED on the CAN-interface should indicate normal operation of double flashes . No flashing LED means no communication with the FC , and regular flashing ( not double) means that communication with the FC is establish , but the CAN-interface has not been correctly initialized by the OSD.
Using the RC receiver with PPM output or S -BUS you don't need a separate RC channel connection to control OSD "on the fly", because the OSD can use the eighth, never used RC channel via the CAN bus of the DJi's FC and in this way you can control the OSD. You should assign the eighth channel to 2 or 3-pos switch in your RC transmitter and in OSD menu control you should select "Direct" for the 3 -position switch , or "Sequ" for the 2 -position . With traditional receiver (separate PWM control of each RC channel) of course you can connect the output of the free RC channel (from RC receiver) to Misio-OSD RC- CTRL pin to be able to change the layout of the screen during the flight.
After connecting everything together OSD is ready to go.

NEW! Misio-OSD now have a hardcase - DJi-style as an option.

CAUTION!!! Absolutely hot MISIO-OSD can talk to you!!! Detailed description soon!
Now you can check youtube: in polish language.
......stay tuned for another info....
Last edited by Rurek; Feb 12, 2014 at 06:12 AM.
Sign up now
to remove ads between posts
Feb 21, 2011, 06:13 AM
Centurian's Avatar
Wow!!! I'd like to get on the list early for a pre order!!!

I just started using Remzibi's unit yesterday, guess I'll have to sell it... the data logging and artifical horizon are priceless!!
Feb 21, 2011, 06:32 AM
Registered User
Really nice! Is it possible to add an Position hold and RTH feature using the GPS sensor?
Feb 21, 2011, 06:36 AM
Build 2 Bounce!
Awsome! I've just been looking at OSD's for my quad, this one looks perfect! Look's like it uses the standard 45mm hole spacing so that it will be stackable with other boards too

Feb 21, 2011, 07:48 AM
King Thor
now accept pre-orders at a special price of 119 € for the OSD and 39 € for a GPS module with battery backup.
i'm in!
where can i pre-order?
Feb 21, 2011, 08:41 AM
quadcopters & FPV padavan
Rurek's Avatar
Thread OP
@nabazul - it is impossible without some inteligency supported by another module - navigation. In MultiWii project today there is no navigation features. Maybe in the future

@firetrappe - yes, this is mikrokopter standard 45mm hole spacing This OSD has been designed natively for Mikrokopter (if someone interested in MK version -let me know)

Special preorder offer valid to end of february or first 20 pcs. ETA: 20th March 2010
Last edited by Rurek; Feb 21, 2011 at 08:50 AM.
Feb 21, 2011, 01:40 PM
Guess Who's Back? :D
paintz2007's Avatar
cool subbed for more info as it rolls out
Feb 21, 2011, 09:25 PM
"Let's put a camera on that.."
spagoziak's Avatar
Wow that's incredible!! Wish I had $170 laying around lol.. I'm using Remzibi now on my quad, how cool would it be to have one of these?! Nice work!
Feb 22, 2011, 08:08 AM
quadcopters & FPV padavan
Rurek's Avatar
Thread OP
all pre-orders please paypal me at [email protected]. Shipping costs will be added later , it will be 8-20 depends of region of the world.
Mar 01, 2011, 02:24 AM
Centurian's Avatar

I received your PM about pre ordering. I have some questions as the definition of the project is still a bit vague.

Could you provide some photos of the complete system including GPS & data logger. What sensors are included on the board? Is this a single board with the SD card on the bottom? it's not clear to me in the pics.

Is the "artifical horizon" an inertial combination of gyro & accel data or is it just a display of accelerometer data?

I see that the fimware is proprietary, I am a bit confused about integrating your app with the open source muiltiwii firmware. Are both applications running on a single processor? What impact does your system have on the cycle times on the multiwii software? Can the multiwii software still be user configured and modified? I have seen nothing specific on the data logging yet, what data can be logged and how is it retreived and analyised? Is all GPS and other sensor (volts, rssi, etc) data available to the multiwii software?

What processor is the board based on? I thought it was the 128 with 14 pwm outputs, I was hopeing to use it on a octo. Not sure why I was thinking that.

Can you provide pinouts of the board IO external hookups please.

Sorry for all the questions, the board is relativly pricey and I want to know exactly what I'm buying.

I already have the remzibi OSD w/GPS, I have another GPS on order with a group buy and a seeduino on the way. I want to make sure your system is fully integrated.

Looking forward to your reply... Thanks,

Mar 02, 2011, 03:56 AM
quadcopters & FPV padavan
Rurek's Avatar
Thread OP
Hi, thanks for yours remarks.
About questions:
This is a single, two sided board. Datalogger sends data to *.csv file, look to attachment.
Data for artificial horizon is taken from MWC processing angle[pitch] and angle[roll] - so it is combined data taken from IMU.
The OSD use own Mega32 CPU.
The OSD request data from MultiWii every 100ms, but get less data than Alex's GUI in PC connected mode. This is not affected to cycle times because you can read these times only with GUI connected (that affects more than OSD )
The multiwii software still be user configured and modified, of course!!! There is only a few commands that sends data to OSD via serial comms. To be honest and clear - Alex aprooves these mods to sketch and plans to attach OSD functionality to official release.
About data logging - look into attachment, all info can be saved every 100ms. Analysis (and GUI for logged data) - it is only thing that now is developing. The rest of the OSD project works fine.
All GPS and other sensor (volts, rssi, etc) data CAN BE available to the multiwii software, in the future, for navi purpose, I think. But it is question for future and for more people involved to code this AI (artificial inteligence). Of course not in ardu pro mini platform, maybe for another standalone board with own proccessor and memory...
Last edited by Rurek; Mar 02, 2011 at 04:10 AM.
Mar 02, 2011, 09:12 PM
Suspended Account
Cool, looks just like EPI-OSD except for MultiWii. How did you manage to USE so many components that it requires double-sided design? I recently made a version of EPI-OSD optimized for single-sided picknplace assembly, and I had mostly empty spaces on the board. I think I even had enough space to fit a SD card there too. Thanks for giving me that idea I'm using atmega644.

What happened here?

Last edited by timecop; Mar 02, 2011 at 09:18 PM.
Mar 03, 2011, 03:40 PM
Registered User
This hardware (resistor) was used for find stupid bug in the firmware.
This photo show little old, test board. On current boards this resistor is not mounted, because it is not needed.
Mar 03, 2011, 11:14 PM
Suspended Account
So what MCU is it? Looking at pinout maybe Atmega164/324/644 or so...
How much of firmware is based on C-OSD? Pretty sure if any, their license is GPL...
Mar 04, 2011, 05:42 AM
quadcopters & FPV padavan
Rurek's Avatar
Thread OP
Look three post earlier, I described some info
About C-OSD - there is no borrowed code, similarity to the EPI is reduced to the size of plates, two setup buttons and used IC MAX 7456 , that are you asking for? I don't think so . How does the OSD to talk about MAX ICs is always possible to discern similarity to something that is already based on it. I have a different MAX connection to MCU, I have a SD card which is not in the epi, I have an audio track which is not there, I'm linking to a GPS receiver, the epi also don't have - so where's the similarity ???
Well, maybe the similarity will be always unless those two circuits, MAX and CPU (which by the way it is different than in the EPI because it has 2x more memory) will be used in this project :-).
The similarity in the code - you can always find if OSD is based on the same hardware .... BUT THIS IS NOT A COPY, no part of someone's CODE.
Moreover, what sense are your questions? I wrote in the first post about it's own, original design. And does not include the stolen ideas, much less have a copy of the code open source, even!!!
Everything clear now?

Quick Reply

Thread Tools

Similar Threads
Category Thread Thread Starter Forum Replies Last Post
Discussion FOR SALE: Black Stork OSD $95 - free shipping worldwide! Ian Davidson FPV Talk 3 Dec 01, 2010 02:39 AM
New Product New Osd Design For Fpv With Data Logger FAKHREALAM FPV Talk 20 Oct 27, 2009 05:11 AM
Discussion Newest design off the Drafting table! Ken Park Fuel Plane Talk 1 Apr 12, 2007 02:39 PM
Discussion my newest design using the plantraco system (green 2.0) RobertTHaas Scratchbuilt Indoor and Micro Models 18 Feb 12, 2006 04:28 AM
FS: NIB YS 91 STR, Free Shipping Worldwide! (New Red Head, the latest design of YS91) Jason WAI Aircraft - Fuel - Helis (FS/W) 1 Dec 06, 2004 06:08 AM