I have the problem that I can't move the items down.
The other move functions work (Pitch: Up, Roll: Left / Right)
My remote control is set to Mode 1 (Horus, Kiss FC)
Each channel is set to +/-100.
I have installed the current version 2.3.1.

COM3 does not show up in the tools>ports tab I tried to upload using a different port: /dev/cu.Bluetooth-Incoming-Port. It says not in sync, I feel like I am missing something very obvious or I should just do this on a windows pc and save myself the headache but this is what I have at the moment.

I've tried to replicate this, but the new firmware from Flyduino does not allow access to the camera control function to work.

The video from Benjamin from Flyduino shows it does works. Take note, there is no KISS OSD hooked up, the OSD shown is the stock OSD that comes with the newer Runcam cameras.
https://www.youtube.com/watch?v=KtFwp2Ue-y8&feature=youtu.be

But in my case I have a Furious FPV Piggy OSD V2 hooked up, and it doesn't work. I'm pretty sure this would happen with a Steele PDB as well
https://www.youtube.com/watch?v=KFWMEGbBB_U

Awolf78 said this on the Flyduino Official page when I brought the issue up.
-That should not interfere with each other. The OSD and the FC operate independent from each other - the OSD just pulls the stick positions from the FC all the time. While it may be a bit annoying that the battery menu pops up - you are not going to hold yaw to the right for too long.

This is not true. The OSD does interfere with the camera control, and you cannot access the camera settings with a OSD hooked up. Why does the OSD share the same stick command as the Runcam control device? Can this not be changed in the code to bottom yaw right for the OSD battery info and center yaw right to activate the camera control function?

If this can be looked at, I would appreciate it a lot. I upgraded the FC firmware to RC36i to take advantage of this function on my racing quads. Sometimes we have to change the camera settings on the fly, and I was hopping to have this working especially when flying outside since the lighting changes a lot on us from cloudy to sun breaks, etc.

With the Steele PDB I was not able to flash the new firmware, neither on Mac or Windows. On Windows this issue was probably related to my updates being turned off. So I plugged the board in the windows machine and it recognized it as a CP2102 serial to USB adapter but it didn´t show the COM port in XLoader. So I did a quick search online and found the following drivers:

https://www.pololu.com/docs/0J7
(not sure if this is the right approach or just a lucky shot)

Installing these, it worked right away. This also worked on OSX Sierra which was my main issue.
This might be useful for other people aswell.

Cheers
ODM

There WILL garbage on the screen when BB is connected to the FC and operational. I sent fix to felix, and he supposed to put it to his git somewhere ;)))

how do you get all the icons not gook

Hello,

Thanks so much for producing this OSD, it works well! Do you have any plans to incorporate TBS SmartAudio controls? It would be awesome to manage TBS Unify Pro VTX settings with the sticks.

Cheers,
Jason

Hi,
Has this issue with the stock OSD so decided to give this one a go as it seems to be a lot more functional!
When the quad is armed and the motors spinning, the RPM on the OSD does not change, and neither does the Current or mAH.
After the quad is disarmed and the statistics are opened, none of the values read anything but the defaults. (0A, 32F, 0RPM, 0V etc.)
All of the ESCs and the FC are updated to the latest versions, and the TLM connections are soldered

Thanks in advance!

Setup: KISS V1 FC, 24A KISS ESCs, Mr. Steele PDB.

Hi, i'm creator of Digital font (betaflight).

And i want ask one question.
It this possible to add these font in KISS OSD?

https://www.dropbox.com/s/uk1u8qzswbc973r/f8.jpg?dl=0

The KISS FC will detect lipo voltage if it receives telemetry data from the KISS 24RE ESCs and prevent the setting of the PIDs and/or Rates from the OSD via serial (see SendFCSettings() in KISS_OSD.ino). Would be great if there would be a way to send the PIDs and Rates to the FC - which would then store them in the EEPROM instead of using them directly (safety issue). The user would have to reconnect the lipo to use the new values.

Hello,

I'm having issues just getting a video feed into my fatshark goggles. I can't seem to get any kind of video feed or even OSD to appear. I have flashed both the latest Steele SteelePDB.V2.5.1.zip and SteelePDB.V2.4.RC4.3.zip in hopes that maybe the older firmware would allow something to function and still nothing.

I have test flown the drone by line of sight and the drone responds and arms to my controller inputs but its the video feed that i can't seem to get to work. Below is a link to a photo of my soldering points and to what devices i'm using for VTX and FPV Camera.

I have those listed as well:

RunCam Swift 2 Rotor Riot D-WDR 600TVL 2.5mm Lens OSD MIC DC 5-36V CCD

TBS UNIFY PRO V3 5G8

Kiss FCv1.03 Firmware: RC34c

At this point i'm going to see if soldering another VTX would work but when plugged in all LEDs lightup on both the PDB, FC, and vTX so i'm just not sure why i wouldn't get a video feed.

https://imgur.com/a/TjZpam1

After following the setup guide from the wiki here and going through the troubleshooting section(Including flipping TX and RX on Port 2, which are the two pins on port 2 closest to the outside of the board), I am still unable to see the video/osd on my goggles.

I am using Mr. Steele's setup with the following:

• KISS FC, flashed with latest firmware (V 2.1.0)
• Mr. Steele PDB, programmed with KB SteelePDB.V2.4.RC4.3.zip(using Arduino 1.8.4 on mac)
  • Currently I have programmed the CONFIG version

Some hopefully helpful notes:

• The FC shows accelerometer orientation when plugged into Cleanflight
• Motors run
• I am able to see "No connection to KISS FC" on my goggles

Hi,

I would like to know if the current sensor pin on the micro minim OSD is actually used within Kiss OSD 2.5.
My setup: AIKON 4 in1 ESC on Kiss v2 works great with the micro OSD, except of the current sensor.
Since the AIKON dose not support ESC current telemetry, I tried to connect the single current sensor to the micro OSD current pin, but it did not work. Can you please help me to solve the issue?
Thank you very much in advance!
Jan

I use a reactor PDB/OSD that I prefer to use for voltage readings. My FC is a little messed up and only reads 5v instead of battery.

Is there any configuration to change the voltage to read from my OSD instead of the FC?

Thanks

Hi,

This is not issue, but I would really appreciate if you can add support for RSSI channel up to AUX8 (channel 12). I'm using FlySky i6X radio which can provide RSSI only on channel 11 (AUX7). Since It cannot be changed in radio, It would be super cool if I could set RSSI channel to AUX7 in OSD.

Thank you,
Dominik

Would be nice to have the angle to know if we are level or not

Hi, I wonder if you can help me? I've set up a Kiss OSD exactly as shown on your page but when I connect the battery, the OSD appears in my goggles for a few seconds but then disappears as soon as the ESCs initialise (beep). I'm running with Kiss 24A ESCs. Kiss FC firmware is 1.1RC6. Logger is switched off in the Kiss configurator. Any ideas?

Getting some compile error when uploading the fw to the minim osd
I added the both libs to arduino: MAX7475 and SerialPort and still getting errors.
here is the output of the build:
http://pastebin.com/VdhEZzPp

Hi,

i use mx12, which has 6 channels. all are used. it would be fantastic, if i can hide the motor infos from the borders in the move menu.

Thx,
Michi

Thanks for your awesome work :)

I have two questions:

• Does this OSD support setting band and power of the Tramp vTx?
• Why is it necessary to use a different configuration firmware? Wouldn't it be more convenient to merge the two versions?

Hi,
I am new to KISS and I have quite a hardware problem with Steele PDB. I was flying a bit with my new quad (I have 7 batteries flown on it) and after changing battery, I ran into No connection to FC problem, which seemed like there was no power to FC. When i got home i read about this and checked if any of connection wires are broken or if any of pins are bent, but there was no problem with that. So i tried connecting FC to PC which had no problem (It was powered by USB and there was no problem to connecting it to KISS GUI). So I went back on PDB and discovered that there is no connection between any of 5V outputs and PORT pin and there was same issue with V_out. So there is probably something wrong on PDB.

The questions are, is there some option to get that working again ? Should I just solder Vbat to FC let it be (if it is safe) or should i claim PDB as faulty and send it back to seller ?

Setup:
Mr Steele PDB V2.5.1
KISS FC v2 v1.3RC34c
KISS 32A regulators

Thanks for any help,

ok guys so after finish building the mr steele alien everything works great on the first flight voltage was working perfectly.(no crash) so to the second battery mah and amp start reading 0 and half way though the pack voltage was stuck on 15.6v so i came back put new battery in and now it only read the starting voltage can any one please help?? the voltage on my taranis is reading out fine

steele osd pdb with all kiss hardware

i try to upload the setup tool and have uno (A Tmeg328) selected along with the hexfile configtool. com 2 port is unplugged.
i hit upload and it says uploading but never finishes. even left it for several minutes and never finished.
thank you for your help!

Hi,
I don't have connection to FC with the KISS_OSD but I do have a connection with the KISS_OSD_CONFIG tool, so RX and TX wires are correctly installed.
What should I change or is this a bug?
Best Regards, Nils

hi
i use KISS_OSD V2.3.1 there is no tune menu like in the youtube video how can i turn this on?
if i disarm , the menu is always visible is this normal ?
i see on youtube yaw 3 sec to the right it opens the battery menu ,its not working for me.

I have an aikon ak32 and I was thinking it would work with my kiss FC but it's not.... Does blheli32 work with your OSD? Any other thoughts?

While disarmed, move yaw to the right. Now you can select the batteries with roll and change the values with pitch.

How does it work for people with ARM-ON-YAW ?

Hello,

I come back with another config, and another issue...
With Kiss FC (1.3 RC30), i want to connect a runcam split (latest fw, 1.1.0) on tx pad. This part run fine, i can start and stop the recording via my radio.

But, when i connect osd (tx/rx) and split (tx) on FC, the OSD runs fine while the split does not answer.
OSD is a piggyOSD with v2.4 RC4.3 fw.

Thanks

Oliv

I got error ( no connection to FC ) maybe because i flashed betafligth?

Hi,
This is my second build with Steele PDB, Kiss FC V2 & Kiss 32A ESCs.
First one worked flawlessly.
Now i'm having a constant red blinking led on the Steele PDB and i don't know why.
I have ignored the blinking led now and just proceeded with flashing the Kiss FC V2 and the Kiss 32A ESCs and that worked just fine.
But now i still have that red blinking led (next to the continuous green led) and i still don't know what it's about.... Do you? Any hints??
I then decided maybe i should try and RE-flash the Steele PDB?
So as i don't have the initial Windows PC anymore (moved to Mac) i installed bootcamp on MacOS and the latest version of Windows 10.
When using Xloader, the COM port is not showing. So it's impossible to upload a hex file...
I have now tried to install the FTDI drivers (Polulu) but i get an error messages everytime saying:
"The current language is not supported by the Device Driver Installation Wizzard."
I'm running out of ideas... Anything else you have in mind? Any hints or tips?
Any advice would be much appreciated. Thank you.

Hello,

I have 2.4 version and i would like to correct the mah consuption at screen.
As told in wiki, i go to BATTERY in KISS OSD but i don't find MAH CORRECTION.
Did i make a mistake? or this setup is available somewhere else?...

How can i do to correct the mah?

Thanks for your help

Olivier

Its possible to have the GPS function with mr Steele pdb?

When I select icon off, the icon of the esc that are on the right and throttle are still visible.

Setup:
KISSFCV2F7-1.3RC32e
Kiss 32A 32-bit ESCs, full telemetry
KISS_OSD 2.5
Micro MinimOSD+470uF cap

I am unable to get spinning prop icons only - I now realize this could be due to the telemetry I have hooked up to the FC (if OSD detects rotation telemetry from ESC, I am guessing it displays this information instead of spinning prop icon); however, it would be nice to see only the spinning props, as I prefer this display to the rotation telemetry. Or even better, if the props could be an additional item in the order, so we could turn the spinning icons on/off based on our set order...

Amazing OSD!

Would it be possible to have a cross hair ✛ in the middle of the screen :)

Hi there,

I got a problem with the Kiss OSD of my Kiss FC V2 + Mr. Steele PDB + TBS Unify Pro V2!

In my OSD I've displayed the Volts, Amps, mAmps, Throttle % and a Timer.

If I arm/disarm the Quad the OSD shows "armed" and "disarmed" instantly, just like Throttle % and the Timer working fine with no delay!

But the Volts, Amps and mAmps have a delay of about 10 seconds till they start counting and measuring correctly...

I got the newest firmware on the FC V2 and the Steele PDB and i flashed the FC first, then the PDB via the GUI and did this two times but nothing fixed the problem yet...

I also flashed a older Firmware on the PDB but the same problem.

Please help me!

the props icon that are on the right are not aligned to the right of the screen

Would it be possible to display if we are in acro or level mode?

I uploaded the configuration FW it worked but the OSD fiction to access the pid and vtx doesn't work off the sticks with the Steel's pdb OSD and the latest kiss V2 FC when Tring to enter the set up screen!

I'm encountering a strange issue where the minimOSD is adding a strange character as shown in the attached image.

It happens after the font has been loaded and persistents on both the config and standard hex firmware. It doesn't change position or disappear when the menus are accessed either.

I've loaded multiple times using both XLoader and the firmware tool on mwosd.
I've also tried clearing the eeprom via the mwosd tool.

This is all regarding KISS_OSD V2.5

Any ideas?

Thanks for your great work!
Dan.

Hi

Just set up a new quad and flashed Steele V2.5 OSD everything is working fine apart from the fact that the OSD thinks that the quad is armed when its isn't and vice versa, do you know what's going on and how to correct this issue???

Hello,

I have (now) V2.4 RC4.3 and i meet issue when i want to make voltage correction.
When i apply positive correction, it seems to be good
However, when i apply negative one, it's run at first, but at next lipo, it's show me 42V at screen! (i run 4S)
So, i go to VOLTAGE CORRECTION and the value has move to 25V (approwimately, denpending of negative value i apply on previous lipo)
This issue occurs with kiss FC and CC.

Thanks for your job!

Olivier

Betaflight 3.1+ has a MSP_DisplayPort command which lets it show its own OSD runes via an external device.

I know this software already supports most of the betaflight features, but I think it would be really cool to have this nonetheless!

FWIW, MW_OSD has support for this via the #define CANVAS_SUPPORT.

Maybe I'm blind, but I couldn't find a hyphen when entering my Call sign.
May you can add some some special chars?

I tried to search for a while now but nothing found.

All the documentation states "1.2 and higher", but I'm getting the no connection to FC with latests KISS FW: 1.3RC30.

Are there planes to update to support 1.3?

FYI: I'm using the Steele PDB and trying to load the Config Tool on MacOSX (via the Other Platforms method).

Hello,

I flashed this software to my micro minimOSD.
The left side off the OSD is not on my screen.

What can I do ?

Hi,
I have set up the osd according to this link here:
https://github.com/awolf78/KISS_OSD/wiki
I have followed the instructions the only difference is that I have put it to Aux 4 in the taranis following the link where Oscar describes how to do it for frsky.

When I plug in the kiss fc to the computer I can see the rqly signal in the aux 4 signal so I know its working correctly but it jumps between 1300 and 1995 when off/on. In the osd configurator I put those numbers in and set it to aux 4, but don't get anything other than 0 db in the osd.

Also I've noticed that Arduino says the firmware is very large for the chipset it takes like 98% of it. Any clues as to what is going on here. I purchased this one: https://www.flyduino.net/en_US/shop/product/pr1865-micro-minimosd-kissfc-osd-fw-preflashed-pal-2683?search=Osd

Unfortunately it didn't come with the newest firmware on it and it's been a pain updating it.

Hi,
in advance: Nice work, many thanks.
My problem with 2.3:
After starting the osd_config tool, the menu will appear for 2 seconds and then disappears completely.
The osd tool does not run at all, no menu, no response.
Version 2.2. works for me as expected.

Greetings Frank

Hello,

https://youtu.be/gSINJNPbjSk

voltage is wrong, if i throttle a bit, the voltage is rising up.
If throttle 0% the voltage is 0.1V

Setup:
TBS Silk
Full KISS,
Lumenier PDB
TBS Unify Pro
Runcam RotorRiot Edition
Piggy OSD Furious