OSD doesn't work with kiss V2 F7

Question

OSD doesn't work with kiss V2 F7

S-T-A opened this issue 7 years ago · 24 comments

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!

Answer 1 · 2018-02-01T18:53:22.000Z

You need to yaw left and hold it for more than 2 seconds for the menu to pop up. Quad must be disarmed of course.

Answer 2 · 2018-02-02T22:57:59.000Z

Ok you have a valid point but my if my FC when I plug it into the kiss GUI it tells me it's disarmed and as soon as I plug in a battery it says armed when it's not I know for a fact it's not so what would the next step?

…

On Feb 1, 2018 1:53 PM, "awolf78" ***@***.***> wrote: You need to yaw left and hold it for more than 2 seconds for the menu to pop up. Quad must be disarmed of course. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH48ydE2eU0jQid6KpXq4Ycj2vN9Zks5tQggjgaJpZM4R2GUD> .

Answer 3 · 2018-02-07T20:15:31.000Z

is there a problem with the kiss V2 FC and and your steels OSD when it says armed when it is in fact disarmed?

…

On Fri, Feb 2, 2018 at 5:57 PM, steve allam ***@***.***> wrote: Ok you have a valid point but my if my FC when I plug it into the kiss GUI it tells me it's disarmed and as soon as I plug in a battery it says armed when it's not I know for a fact it's not so what would the next step? On Feb 1, 2018 1:53 PM, "awolf78" ***@***.***> wrote: > You need to yaw left and hold it for more than 2 seconds for the menu to > pop up. Quad must be disarmed of course. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#38 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ASdzH48ydE2eU0jQid6KpXq4Ycj2vN9Zks5tQggjgaJpZM4R2GUD> > . >

Answer 4 · 2018-03-04T01:12:06.000Z

Ok on v2.5 and kiss v2 installing OSD configuration works. I used my transmitter it worked fine, saved the configuration. I then loaded the OSD that took plugged back in the port 2. When it starts up it shows the FC is armed when the arm switch isn't In arm position and says FC connection??? I checked all the wires have continuity I even tried switcing the tx and Rx wires and nothing I'm stumped I don't get it? It should of worked since I could program it just before I flashed the OSD hex.

Answer 5 · 2018-03-04T03:55:04.000Z

Unplug both ports from the PDB and try flashing it again.

Answer 6 · 2018-03-05T11:06:37.000Z

I tried 4 times there is either something in compatible on the v2 or the pdb firmware. I think there is an issue it gets input from FC to do the configuration that works no problem just when you go to load the OSD firmware on to it it would say no connection to FC or nothing. I'm swamped the port 1 and 2 wires with each other to eliminate the wires being a problem and the their not it arms and flys the OSD works! But when you first plug in it after impulse logo it says armed!!!! Now in the FC, I have armed on aux 1. Min command is 1075 I tried making it 1000 no difference I can't get it to start up with out saying arm so I can never get into the OSD firmware to make any changes is there a problem with the kiss v2 or the pdb??? I have another v2 with 32amp kiss esc's and a Steel's pdb which I was going to use in a reverb. I'm extremely frustrated and would really like to get it working should I buy a older kiss 1.03 v1? I'm pretty sure is should work with an older one no???

…

On Mar 3, 2018 10:55 PM, "awolf78" ***@***.***> wrote: Unplug both ports from the PDB and try flashing it again. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH2535m8BuFwkZqNWGD-lc2r6gYwUks5ta2WZgaJpZM4R2GUD> .

Answer 7 · 2018-03-05T12:11:41.000Z

The SteelePDB does work with the V2, there are many users that are running that combination. Did you check in the KISS GUI if you have ESC telemetry? Connect USB to FC, run KISS GUI, connect a Lipo (props off) and go in the advanced tab. On the drop down you can display the various ESC telemetry items such as mah, rpm, etc. Please double check that is working properly.

Answer 8 · 2018-03-06T01:23:50.000Z

Just checked in the GUI the telemetry is not working in the final OSD firmware but when it's the test I can set it up and every thing else I switched the cables and checked them for continuity and tried switching the tx and Rx and nothing so is it the kiss v2 maybe I have everything selected correcty? I just don't get how come I can flash the configuration file it works and responds to my radio and does what it's so pose to do when I flash the final OSD bam I get kicked in the nuts! :(

…

On Mar 5, 2018 7:11 AM, "awolf78" ***@***.***> wrote: The SteelePDB does work with the V2, there are many users that are running that combination. Did you check in the KISS GUI if you have ESC telemetry? Connect USB to FC, run KISS GUI, connect a Lipo (props off) and go in the advanced tab. On the drop down you can display the various ESC telemetry items such as mah, rpm, etc. Please double check that is working properly. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH1OUy7ESCzR8q1LeL74yfRB1oOUMks5tbSt9gaJpZM4R2GUD> .

Answer 9 · 2018-03-06T01:29:49.000Z

If you do not have any telemetry in the KISS GUI, then you might have a short somewhere on your ESC telemetry. Disconnect the telemetry wire for each ESC one by one and keep checking in the KISS GUI if you get ESC telemetry for the ESCs that are still connected. That might help to narrow down the culprit.

Answer 10 · 2018-03-06T02:11:42.000Z

Aren't the telemetry wires all a common signal going to the OSD then the fc? In beta flight4f with beta flight esc's on my reverb the telemetry wires on the pdb all go to a common wire exiting the pdb going to the fc.

…

On Mar 5, 2018 8:29 PM, "awolf78" ***@***.***> wrote: If you do not have any telemetry in the KISS GUI, then you might have a short somewhere on your ESC telemetry. Disconnect the telemetry wire for each ESC one by one and keep checking in the KISS GUI if you get ESC telemetry for the ESCs that are still connected. That might help to narrow down the culprit. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH9khjrVNZP0QZUJF8hqm6RQyK96Gks5tbeaOgaJpZM4R2GUD> .

Answer 11 · 2018-03-06T04:07:00.000Z

No, the telemetry wires are connected to the FC. FC reads ESC telemetry. OSD reads telemetry (stick input, etc.) from FC.

Answer 12 · 2018-03-07T03:26:25.000Z

Do you have a electrical schematic of the OSD pdb?

…

On Mar 5, 2018 11:07 PM, "awolf78" ***@***.***> wrote: No, the telemetry wires are connected to the FC. FC reads ESC telemetry. OSD reads telemetry (stick input, etc.) from FC. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH4SIn177foj2y6C7UAbFktDzFUjCks5tbgtpgaJpZM4R2GUD> .

Answer 13 · 2018-03-07T12:44:28.000Z

I don't. You can ask ImpulseRC, but I highly doubt they will give you the board design showing all the traces. All you should need is the pictures on their website:
https://impulserc.com/collections/pdbs/products/mr-steele-alien-pdb-kit-for-kiss-with-osd-and-mic

Answer 14 · 2018-03-25T04:12:06.000Z

ok this is my second PDB and it's exactly the same as the first i flashed and connected my KISS V2 and steels PDB in my reverb and kiss 32A esc's no shorts nothing of the sort. When the KISS OSD is flashed when first pluging in it says armed!!! when it's not and the Kiss GUI 2.0.6 says its disarmed and serial is set to OSD! and there is no telemetry feed back through the PDB To The FC in the GUI. yet it arms and responds just can't access the main menu and the stick doesn't respond the final firm ware flash... So what the next step???????

…

On Mon, Mar 5, 2018 at 8:29 PM, awolf78 ***@***.***> wrote: If you do not have any telemetry in the KISS GUI, then you might have a short somewhere on your ESC telemetry. Disconnect the telemetry wire for each ESC one by one and keep checking in the KISS GUI if you get ESC telemetry for the ESCs that are still connected. That might help to narrow down the culprit. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH9khjrVNZP0QZUJF8hqm6RQyK96Gks5tbeaOgaJpZM4R2GUD> .

Answer 15 · 2018-03-25T13:56:54.000Z

Try changing arm to AUX1 or AUX2 - that has helped some other users

Answer 16 · 2018-03-25T14:42:15.000Z

I will try that thanks wolf 😎

…

On Sun, Mar 25, 2018, 9:56 AM awolf78, ***@***.***> wrote: Try changing arm to AUX1 or AUX2 - that has helped some other users — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH0aUdhVSBWj7GnRxlMe2hn4Te56Dks5th6IngaJpZM4R2GUD> .

Answer 17 · 2018-03-27T21:55:11.000Z

Hi, same problem here. Kiss V2, and mr Steel PDB. Arming on AUX1 or AUX2 didnt work for me. Also dont have telemetry for ESC on KISS GUI, but i can see telemetry of ESC on OSD.
Same as S-T-A, i cant access the OSD menu by holding yaw on left.
I think there is some kind of incompatibility. Hope you can find and solve it quickly :-)
Meanwhile... any other ideas or workarounds?

Answer 18 · 2018-03-27T21:58:56.000Z

Disable level mode

Answer 19 · 2018-04-05T06:54:54.000Z

thanks! worked for me!

Answer 20 · 2018-04-05T10:07:58.000Z

I set up arm from aux 1 to 2 and it worked but either aux 1 or 2 when moving the switches it showed the disarmed/armed only when I changed the armed from aux 1 to 2. But the ESC telemetry doesn't work in the kiss GUI on two of my Mr. Steel's pdb OSD??? Could that be changed in it the next firmware update? Also would it be possible to change the size of the font so if we wanted the ESC telemetry it would be smaller then the rest not to take up the whole screen I was thinking 1/3 of the current size? So we could put it on the side of the screen even when I do it's still too big. Kick ass OSD wolf!!!

…

On Thu, Apr 5, 2018, 2:54 AM Alephnull27, ***@***.***> wrote: thanks! worked for me! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH_JtNkIOpCsTfkLwXMB7lkgsEmAGks5tlb-_gaJpZM4R2GUD> .

Answer 21 · 2018-04-07T00:51:37.000Z

If the ESC telemetry does not work in the KISS GUI you most probably have a short on one of the ESC telemetry wires (they are internally connected together on the KISS FC). As I suggested before, try disconnecting the telemetry wires one by one to find the issue.

I would recommend you to use a switch or better a knob on your radio to control how many OSD items are displayed - especially useful for the ESC telemetry which you do not need to see all the time. In my wiki check out the section "Making your OSD more or less busy", link is below.
https://github.com/awolf78/KISS_OSD/wiki#setup-of-kiss-osd

Answer 22 · 2018-04-07T06:08:59.000Z

Two separate builds and trust me when I say there are no shorts 100% quite simplely it doesn't work! On the kiss v2 kiss 32amp ESC

…

On Fri, Apr 6, 2018, 8:51 PM awolf78, ***@***.***> wrote: If the ESC telemetry does not work in the KISS GUI you most probably have a short on one of the ESC telemetry wires (they are internally connected together on the KISS FC). As I suggested before, try disconnecting the telemetry wires one by one to find the issue. I would recommend you to use a switch or better a knob on your radio to control how many OSD items are displayed - especially useful for the ESC telemetry which you do not need to see all the time. In my wiki check out the section "Making your OSD more or less busy", link is below. https://github.com/awolf78/KISS_OSD/wiki#setup-of-kiss-osd — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH-4YJV8ChWwctDt4wChnwKRJjunlks5tmA2agaJpZM4R2GUD> .

Answer 23 · 2018-04-07T12:36:22.000Z

Did you check the pins on the KISS FC and PDB? If those are not bent either, then I would talk to your dealer about it. It has nothing to do with the OSD FW - if the FC does not receive telemetry from the ESCs it cannot send it to the OSD and the OSD cannot display it. And since you cannot see the ESC telemetry in the KISS GUI the issue is on the ESC<>FC side.

Answer 24 · 2018-04-07T15:04:06.000Z

There not bent bit 2 different kiss v2 FC's and ft so different Mr. Steel's pdb's? Really odd?

…

On Sat, Apr 7, 2018, 8:36 AM awolf78, ***@***.***> wrote: Did you check the pins on the KISS FC and PDB? If those are not bent either, then I would talk to your dealer about it. It has nothing to do with the OSD FW - if the FC does not receive telemetry from the ESCs it cannot send it to the OSD and the OSD cannot display it. And since you cannot see the ESC telemetry in the KISS GUI the issue is on the ESC<>FC side. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASdzH0tm7ZQY-QZ6zG_sl4NByI7EjBP3ks5tmLLGgaJpZM4R2GUD> .