No Connection to FC

[dawiddi]

Hello there, I just build my first wolf pdb setup with a brand new board and a Kiss FC V1. After updating all firmwares (Kiss on 1.3RC36 Stable and the latest OSD firmware) and do all settings (Dummy VTX, No Logger/OSD) I have the following issue. After booting up every time the message "Detecting FC Type" shows up. Sometimes after a while, the message just disappears, other times it follows "No connection to FC" and the OSD hides. I already checked the port cable, it seems to be everything ok. I resoldered the cables to the VTX and the cam aswell. The Kiss and the PDB are brand new.

I've read all the issues related to my problem, but could not find a solution. Can you help me?

Thanks a lot.

[Hydromaster1]

I am having the same issue. Kiss FC V2, tramp vtx, & crossfire. The problem goes away when GPS is disconnected. Using an RDQ M8N GPS. GPS data appears and disappears. Thanks for all the hard work and awesome firmware!!!

[awolf78]

I just released a fix for this issue, please connect GUI and update

[Hydromaster1]

Update complete and the issue is gone. Only thing I noticed was the home arrow spins continuously. Could this be due to close proximity to the home point. I only did one test flight about 300 meters out. Hope to get another flight in tomorrow. Many Thanks!!

[awolf78]

If the home arrow keeps spinning then the GPS has not been able to establish a fix yet. You can turn the satellites label on which will show you how many satellites the GPS has found. For a first fix it can take several minutes...

[Hydromaster1]

Got it. Many thanks!!

On Thu, Apr 4, 2019 at 5:51 PM awolf78 notifications@github.com wrote:

If the home arrow keeps spinning then the GPS has not been able to establish a fix yet. You can turn the satellites label on which will show you how many satellites the GPS has found. For a first fix it can take several minutes...

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ImpulseRC/OSD/issues/25#issuecomment-480112845, or mute the thread https://github.com/notifications/unsubscribe-auth/AWU1wKV6qnJCFaAAccMiNZzKGVkQX_FIks5vdp4DgaJpZM4cURha .

[dawiddi]

Many thanks. I couldn‘t try flying yet, but the message disappeared in standby.

[dawiddi]

So I got the time to test it today. But unfortunately the voltage, power and mah values were way too high (330 V, 150 A etc.) and after a short while it lost the connection to the FC. What should I do?

[awolf78]

Can you revert to V24.11 and see if you still have the same issue?

[dawiddi]

Hello, I just got the chance to test it today. The wrong voltage values are gone, but instead the "Detecting FC Type" and "No connection to FC" comes back after a few seconds of flight. Any further suggestions?

[awolf78]

If you reverted to V24.11 and you get a "Detecting FC Type" then there is definitely something wrong with your board or wiring. Do any of the chips or regulators get very hot shortly after you plug in? Can you post some pictures of your wiring?

[dawiddi]

I already measured the wiring to the Kiss FC, all cables are okay. When I touch the PDB after powering, it stays cool. It seems good. But my Kiss FC gets very hot near the USB port. I thought, that would be normal because it is a new one.

I attached some pictures of my wiring.

[awolf78]

Wiring seems OK. What type battery are you running? 4S, 5S, 6S? VTX is connected to HV power - not sure which VTX you are using. Did you change anything in your serial configuration of your KISS FC. Check in the KISS GUI Advanced tab. Please post a screenshot of that.

[dawiddi]

Battery is 4S, I use a Unify Pro HV, that works great. I attached a screenshot of the advanced tab.

[awolf78]

Strange that your Yaw Filter is at 92 - should be at 35 or 40. But that should not matter for the FC communication. Do you have another FC you can try?

[awolf78]

Did you read https://github.com/ImpulseRC/OSD/wiki/Betaflight-WolfPDB:-Please-read!!!? Configured MSP for the UART you are using for FC communication to the PDB?

[AiroFpv]

So i have also been having this same issue, new board, connect to gui and flash newest fw. When i first plug in, osd is fine and i can access menus for a bit then "no connection to fc" shows up. Same if i go for a fly, after a few seconds, osd goes away and no connection to fc. Any tips?

[awolf78]

Can you describe the setup you are running? FC type, lipo voltage, etc.

[AiroFpv]

Sorry, i deleted the link comment cause i am running kiss v1 fc and 32a escs, 5v unify, 4s with caps on esc's in preparation for 6s transition.

[awolf78]

What FW are you running on the KISS FC? Not sure if you have tried to run 6S on your rig, but the KISS V1 cannot handle 6S lipo voltage. Most of the time the voltage regulator gets damaged if you try to run 6S and although it still flies you get these connection issue. Not 100% sure that is the issue, just one possibility.

[StevenFpv]

ciao ragazzi, ho lo stesso problema appena collego la lipo mi rimane il logo impulse con la scritta DETECTING FC TYPE. una build che funzionava, ho sostituito con una nuova kissv2 e nuova ricevente r9 slim plus, ho aggiornato con l 'ultimo fw di impulse e l ultimo su gui, aggiungendo il GPS. ho staccato il gps e provato fw precedenti ma non sono riuscito a risolvere il problema.

[vladsubbotin44]

pdb wolf writes in OSD Detecting FC Type. flight controller mamba f405 mk2. whats problem ?

[sblakemore]

@vladsubbotin44 please ensure that you have updated to the latest version of ImpulseOSD. Can you also check that you have MSP enabled for the correct serial port in BF and that you have soldered RX to TX and TX to RX.

[AiroFpv]

So, something really weird just happened, went to update the osd, run impulseosd plug in, says do you want to update, click yes then error message saying lost connection try power cycling and re run gui. Now when i plug in the computer it says that device isnt working correctly, impulseosd gui just sits there and doesn't see it and impulserc driver fixer doesnt see it either. No flashing heartbeat, should i try to solder sda and gnd or did it fry?

On Fri, May 10, 2019, 9:49 PM awolf78 notifications@github.com wrote:

Please read https://github.com/ImpulseRC/OSD/wiki/Betaflight-WolfPDB:-Please-read!!!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ImpulseRC/OSD/issues/25#issuecomment-491469797, or mute the thread https://github.com/notifications/unsubscribe-auth/AMBKOZKGI6MG4MABHIHPVILPUYQZ3ANCNFSM4HCRDBNA .

[awolf78]

https://github.com/ImpulseRC/OSD/wiki/Rescue-flash

[blackdrone911]

If you reverted to V24.11 and you get a "Detecting FC Type" then there is definitely something wrong with your board or wiring. Do any of the chips or regulators get very hot shortly after you plug in? Can you post some pictures of your wiring?

I have the issue with my PDB v2. The small voltage regulator is getting hot shortly after plug-in the LiPo. Also it is not possible to connect the board via USB. Is the board defect?

[awolf78]

Last rescue attempt would be to attempt a rescue flash. You would have to temporarily bridge the SDA and GND pads. If the red LED doesn't blink though and you cannot connect with USB it doesn't look good :( Instructions for rescue flash are here: https://github.com/ImpulseRC/OSD/wiki/Rescue-flash

[StevenFpv]

Solved

Ottieni Outlook per Androidhttps://aka.ms/ghei36

---

From: awolf78 notifications@github.com Sent: Monday, January 13, 2020 3:42:32 PM To: ImpulseRC/OSD OSD@noreply.github.com Cc: StevenFpv stefanopre@outlook.it; Comment comment@noreply.github.com Subject: Re: [ImpulseRC/OSD] No Connection to FC (#25)

Last rescue attempt would be to attempt a rescue flash. You would have to temporarily bridge the SDA and GND pads. If the red LED doesn't blink though and you cannot connect with USB it doesn't look good :( Instructions for rescue flash are here: https://github.com/ImpulseRC/OSD/wiki/Rescue-flash

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/ImpulseRC/OSD/issues/25?email_source=notifications&email_token=ANJOVT3RFEKGOISFYHOWVTTQ5R4VRA5CNFSM4HCRDBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIY6OJA#issuecomment-573695780, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANJOVT4PR4F5ZJG5SRXBUMLQ5R4VRANCNFSM4HCRDBNA.

[blackdrone911]

In my case, unfortunately not. Thanks for the instruction awolf78. But now I am sure that I can only keep the board alive, if I change the voltage regulator. Today I ordered some of them. I hope the replacement will be the solution. Today I tried an experiment. I put some ice in a plastic bag on the “hotspot” and voila, there was connection via USB until the regulator got too hot again. But, the question is, how it can get damaged? The board is nearly brand new. Only flown 6-8 lipos with it.

[awolf78]

Unfortunately these failures can happen even though we tested the board. We do not make the voltage regulators ourselves. As an alternative you can contact your dealer and request a replacement if you do not want to replace the regulator yourself.

[Frakovich]

Hello same problem here with pdb V3. "No connection to FC" and the OSD hides. I already checked the port cable, it seems to be everything ok. I resoldered the cables to the VTX and the cam aswell. The Kiss and the PDB are brand new. I tried to bridge the SDA and GND pads, but the red LED doesn't blink though and I cant connect with USB... Even after desolder everything ...

[awolf78]

Can you post a picture how you have it wired up?

[Frakovich]

Thx for your fast answer :) Shame on me... Im actually at work lol (my setup is at home). I take a picture after my job... But even after unwire all ... I have still the problem

[awolf78]

With everything but Lipo power disconnected: Does the red light blink at all? With or without SDA-GND bridge?

[Frakovich]

With everything but Lipo power disconnected: Does the red light blink at all? With or without SDA-GND bridge?

Nope only green led :( ... Here is a pic

[awolf78]

Do you have a multi-meter? Can you check for continuity between Lipo +-?

[Frakovich]

Do you have a multi-meter? Can you check for continuity between Lipo +-?

Multimeter show 15.2 (4s for test)

[Frakovich]

Kiss fcV2 is ok (brand new) (usb recognise and version is KISSFCV2F7-1.3-RC40o ) esc ok (brand new too) Crossfire ok (brand new) Blue caps 330uf 50V are ok (old but still good)

No red blink at all :(

[awolf78]

I was trying to determine if there is a short on the PDB somewhere - if there is not it will help your warranty claim even further. The KISS FC receives direct Lipo power, so that is not affected. Anyhow, please contact your dealer for a replacment. I'm sorry this happened to you.

[awolf78]

Multimeter show 15.2 (4s for test) I did not mean voltage, but continuity.

[Frakovich]

I was trying to determine if there is a short on the PDB somewhere - if there is not it will help your warranty claim even further. The KISS FC receives direct Lipo power, so that is not affected. Anyhow, please contact your dealer for a replacment. I'm sorry this happened to you.

Thx for your help !

[Frakovich]

Hello, my dealer is ok to replace my pdb. they will check our discussion. I already order a new one ...

[blackdrone911]

Glad to hear it. In my case, unfortunately, I should have to send in the PDB to the USA. This is of course associated with immense circumstances here in Germany.

[DrewR1]

I've had the same problem and spent 3 evenings this week connecting it in every way under the sun to a matek f722 because I use Crossfire so the SPI will not work for my setup. Just using the OSD alone and not the WolfPDB. Anyhow, I give up on this product as the red blink has stopped at this point even though it still boots up and searches for an FC only to say "no settings received from FC 1." Has anyone in this thread found resolution?

[awolf78]

Did you read this: link

[DrewR1]

Yes, and I just did it again to be sure and still get "No connection to FC."

[awolf78]

What version BF are you using?

[DrewR1]

Using 3.5.6 (what the Matek F7 comes flashed with).

But that image is incorrect as the labeling of "FC RX" and "FC TX" are reversed. Now the OSD showed up for about 8 minutes and then just vanished? Rebooting or different battery do not bring it back. Is this a special feature? How do you get it to stay on?

Okay, sometimes it comes back with a different battery or maybe it was time (assuming overheat but the osd was not hot as I could hold it all day). Maybe a DOA?

[awolf78]

Does the red LED still blink?

[DrewR1]

NO, not blinking

[awolf78]

:( Rescue flash