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.

[DrewR1]

I will say, DANG it's good when it's on :) :) :)

[DrewR1]

Will do and thank you graciously for the assist.

[DrewR1]

Okay, it is working, not overheating and no red led. My guess is that the red led is broken or burned out....

[swoopyfpv]

i have a problem with my wolfpdb v1. i've flashed the newest kiss version (kiss v2 - 1.3-RC40o) and the newest impulse osd version(68.20). osd won't recognize my kiss v2 (tried 2 different fc's). ( OSD show's - No Connection to FC 1 - No Settings Received )

if i connect my kiss v1 ( 1.3-RC34c) it work's without problems.

tried flashing V24.11 onto the osd, didn't change anything when connecting my kiss v2.

(i'm on 4s, 24a kiss esc's, connected a vtx via smartaudio to the pdb)

any ideas or maybe version suggestions? thanks in advanced

[awolf78]

How did you connect the Wolf to the KISS V2? Did you use the wiring harness that came with the Wolf? Did you plug it into the correct ports? Are any of the pins bent on the KISS V2 plugs?

[swoopyfpv]

thanks for the quick answer! i used the wiring harness. plugs are connected correct & pin's are not bend.

edit: i have now updated all components to the latest firmeware (pdb - 68.20 / kiss v1 RC40o / kiss v2 RC40o ) - tried two different pdb's (both v1) & also tried two different wiring harness.

ESC's (Kiss 24a) LED's light up blue, I'm able to test the motors via the kiss gui, OSD is working, but in all cases i won't get a connection to the FC...

now to the weird part: as mentioned above with kiss v1 it worked. as i flashed the kiss v1 (RC40o) the pdb didn't recognize the FC. After restoring a dump from a old kiss v1 it works... maybe i have some wrong settings at the kiss v2 and therefore it won't recognize the fc?

---

here is the dump i restored: { "G_P": [ 3, 3, 8 ], "G_I": [ 0.035, 0.035, 0.05 ], "G_D": [ 10, 10, 5 ], "ACCtrim": [ 0, -1.6 ], "RC_Rate": [ 0.93, 0.93, 0.93 ], "RPY_Expo": [ 0.76, 0.76, 0.76 ], "RPY_Curve": [ 0.29, 0.29, 0.29 ], "ACCZero": [ 0, 0, 0 ], "TPA": [ 0.4, 0.2, 0.4 ], "RGB": [ 0, 0, 0 ], "CBO": [ 0, 0, 0 ], "AUX": [ 21, 0, 53, 0, 0, 0, 0, 0, 37, 0, 0, 0 ], "DB": [ 0, 0, 0 ], "NFE": [ 0, 0 ], "NFCF": [ 200, 200 ], "NFCO": [ 100, 100 ], "ver": 110, "reverseMotors": 0, "launchMode": 0, "A_P": 4, "A_I": 0.04, "A_D": 10, "RXType": 8, "PPMchanOrder": 0, "CopterType": 2, "Active3DMode": 0, "ESConeshot125": 5, "MinCommand16": 1000, "MidCommand16": 1500, "MinThrottle16": 1070, "MaxThrottle16": 2000, "TYmid16": 1500, "TYinv8": 0, "maxAng": 50, "LPF": 1, "ESConeshot42": 0, "failsaveseconds": 10, "BoardRotation": 0, "CustomTPAInfluence": 0, "TPABP1": 30, "TPABP2": 50, "TPABPI1": 30, "TPABPI2": 0, "TPABPI3": 0, "TPABPI4": 100, "BatteryInfluence": 0, "voltage1": 12.8, "voltage2": 14.8, "voltage3": 16.8, "voltgePercent1": 130, "voltgePercent2": 100, "voltgePercent3": 70, "loggerConfig": 0, "vtxChannel": 32, "vbatAlarm": 0, "debugVariables": 0, "mahAlarm": 0, "lipoConnected": 0, "lapTimerTypeAndInterface": 0, "lapTimerTransponderId": 0, "loggerDebugVariables": 0, "YawCfilter": 35, "vtxType": 0, "vtxPowerLow": 25, "vtxPowerHigh": 25, "motorBuzzer": 1, "loopTimeDivider": 1, "yawLpF": 1, "DLpF": 1, "adaptiveFilter": 1, "ledBrightness": 100, "setpointIntoD": 100 }

[DefiniteDisorder]

Hi. I'm having trouble too. Fettec fc and esc, apex reg and osd. Connected with apex wire harness. (disconnected the vcc and gnd cable that goes to fc, as shown in Philip seidels wiring diagram, it gets vcc from esc instead to reduce load on the regulator) Latest firmware on fettec, latest firmware on osd. Same as others I have osd working for about 30 seconds but then it goes away and no connection to fc comes up. Any suggestions?

[DefiniteDisorder]

Tried to move the cables between fc and osd away from the esc. No difference. Note I said that it works for 30 seconds, it is more like 3 minutes.

[sblakemore]

@DefiniteDisorder Think I just replied to you on Facebook, but will copy the same text here in case it helps anyone else.

"This is a grounding issue. For the MCU on the OSD and the MCU on the FC to be be able to make sense of the serial data going between them, they need a solid noise free ground reference. I would recommend to power the FC via the reg board as intended with VCC and GND. Then remove just the VCC wire from the FC to OSD, but keep that GND signal there.

Doing it this way is exactly how the harness was designed to work with the KISS v2 which was never able to get VCC from the 4in1 anyway."

[DefiniteDisorder]

Yes you did 😋 I will try it as soon I find the time. 👍

Den mån 23 mars 2020 02:39sblakemore notifications@github.com skrev:

@DefiniteDisorder https://github.com/DefiniteDisorder Think I just replied to you on Facebook, but will copy the same text here in case it helps anyone else.

"This is a grounding issue. For the MCU on the OSD and the MCU on the FC to be be able to make sense of the serial data going between them, they need a solid noise free ground reference. I would recommend to power the FC via the reg board as intended with VCC and GND. Then remove just the VCC wire from the FC to OSD, but keep that GND signal there.

Doing it this way is exactly how the harness was designed to work with the KISS v2 which was never able to get VCC from the 4in1 anyway."

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ImpulseRC/OSD/issues/25#issuecomment-602318525, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO427MH7DWKGSBYKCHKMYRTRI24UFANCNFSM4HCRDBNA .

[shneakypete]

Having a similar issue with the osd going out, if it even shows up at all. Tried the vtx, 2 different fc and vcc ground pads… I understand their not “clean” but I don’t have or can fit the pdb. I even tried a small lc filter but when the osd does show I can’t get it to stay for more than 30sec. Suggestions?

Edit: found the answer… camera sync

[oyvindp]

I also have this issue on and off on two quads with same setup. Usually goes away after replugging the lipo, so minor annoyance unless it gets more persistent. Fettec 45a, KissV2, Apex OSD, Apex regulator board. All connections are as recommended.

[awolf78]

Try setting camera sync to 200.

[shneakypete]

Try setting camera sync to 200.

Thanks it worked, it still disappears after a sharp high amp draw but it’s rare… are there different sync settings for different cameras? I’m running a turtle v2.

Also, for some reason I’m not able to control my vtx to change channel or mw… running tramp. Everything else seems to be working fine.

[awolf78]

Need to play around with camera sync. Try increasing it further, like 250. If it gets worse, try 150. A bit of trial and error. We know it for a few cameras, but not turtle v2.

Did you solder Tramp "T" wire to the VTX control pad? Can you post a picture how you wired it up?

[shneakypete]

Need to play around with camera sync. Try increasing it further, like 250. If it gets worse, try 150. A bit of trial and error. We know it for a few cameras, but not turtle v2.

Did you solder Tramp "T" wire to the VTX control pad? Can you post a picture how you wired it up?

Sry, just looked at it again and realized the vtx has an audio pad and tlm pad… I had it running from audio… for the camera sync, it is working at 200, just if I clip a branch it disappears… I’ll play with the numbers

[shneakypete]

Need to play around with camera sync. Try increasing it further, like 250. If it gets worse, try 150. A bit of trial and error. We know it for a few cameras, but not turtle v2.

Did you solder Tramp "T" wire to the VTX control pad? Can you post a picture how you wired it up?

Tested the turtle v2 with camera sync at 250 and it appears to be better than 200. sharp stick inputs was getting osd flickers vertically. changing it to 250 did not show these. Bench test only at the moment.

[darkjedi15486]

Hi I'm having this issue. Iv updated to newest firmware on osd and kissv2 fc. After a few mins of flying I get the warning "no telemetry " and "no connection to fc4" can anyone help

[awolf78]

Try running the wires above the FC

[darkjedi15486]

I actually asked mr steele about this and he said he has no issues with running the wires between the stack i will try it though. What is it cause by awolf78?

[awolf78]

Moving the wires may not fix it - it is an attempt to eliminate a possible cause of error (EMI from the ESC). Can also be a mechanical connection issue.

[darkjedi15486]

So if I do that and the issue remains. What would u suggest. A new kiss wiring harness. Or something else?

[shneakypete]

Had this issue… for me the harness on the pdb had come loose from the solder joints and was getting intermittent connection. Ended up replacing the pdb cause when I tried to resolder the traces came off

[darkjedi15486]

I'm not using a pdb. Im using the kiss 4 in 1 and the kiss v2 with apex irc osd and regulator board

[awolf78]

First I would re-seat the connectors and make sure the pins inside the connectors are not bent in a weird way. I would still route the cables above the FC to eliminate any possible EMI issues (not every ESC is the same even if it is the same brand). If all of that doesn't help you can try a new Apex OSD harness.

[darkjedi15486]

Well thats how I have mine wired up. I moved the wires away from the motor solder joints and reflashed the osd board and had a 4 min flight with no issue so hopefully its a problem thats gone for good.

[LocNgu]

I am having the same "no connection to Fc" Problem. I am running Fettec Fc, Fettec 4in1, Apex Regulator, Apex Osd Board, all wired up using the Kiss Harness, 6s, low esr cap, and fettec spike absorber. I tried running the wire over the fc and powering the Fc from the regulator board instead of the esc. Reflashed everything to most recent updates as of today. I can reproduce the issue pretty consistently. Every time the amp draw goes over aprox 5A the issue occurs and go away when amps falls back.

[awolf78]

1. Remove the GND wire from the ApexOSD harness between Apex Regulator and Fettec FC
2. Remove the extra Lipo wire between Fettec ESC and FC
3. Add a GND wire between ApexOSD (can use e.g. GPS GND) and Fettec FC (use any GND that is convenient)

[LocNgu]

1. Remove the GND wire from the ApexOSD harness between Apex Regulator and Fettec FC

2. Remove the extra Lipo wire between Fettec ESC and FC

3. Add a GND wire between ApexOSD (can use e.g. GPS GND) and Fettec FC (use any GND that is convenient)

Did all the steps above and they do help. Issue doesn't appear that often, but still does from time to time. Still not quite what one would expect from a pretty expensive osd board.

[awolf78]

There are also some firmware fixes, not only on our side, also on KISS. What KISS FW are you using?

[darkjedi15486]

I'm using rc40i on my v2.

[awolf78]

Consider upgrading to 40o. Alexander Fedorov has also made some changes (we worked closely together on the communication issues). You can find his latest FW on Patreon.

[darkjedi15486]

Is 40o available on the kiss gui

[awolf78]

Yes

[LocNgu]

There are also some firmware fixes, not only on our side, also on KISS. What KISS FW are you using?

FETTEC_KISSFC-1.3-RC40o

[ebeez]

Hi, Can anyone post a picture of how they have used the Apex regualtor/OSD wiring harness to the FC? I am still getting the "connection lost to FC" on my build: Fettec 45 ESC, Fettec FC (both flashed to most current version), apex regulator board/OSD

[awolf78]

1. Route OSD wires above FC, not between FC and ESC (or below ESC)
2. Remove GND wire between FC and Apex Regulator
3. Remove Lipo+ between FC and ESC
4. Add GND wire between FC and ApexOSD (any GND pad on either side will do).

[ebeez]

1. Route OSD wires above FC, not between FC and ESC (or below ESC)
2. Remove GND wire between FC and Apex Regulator
3. Remove Lipo+ between FC and ESC
4. Add GND wire between FC and ApexOSD (any GND pad on either side will do).

Thank you for the quick response! Will give it a shot.

[ebeez]

Thank you!!! Worked like a charm!

[blackdrone911]

Hello again, now I have two v3 PDBs where the red LED is constantly on. The trick with SDA and Ground doesn’t work. Some questions:

1. Why this happened the second time?
2. How could it be solved, detected the broken part?
3. Is the problem known from the manufacture?

I am really tired with this PDB after spending so much time to find the problem :(

[awolf78]

Did you select "Full chip erase" when you forced the bootloader by bridging SDA and GND?

[blackdrone911]

I can’t select anything. The software doesn’t detect the PDB. I tried with windows and also with MacOS. Than I removed all solderings (cam, ESCs, FC and so on) and tried again. Same result.

[awolf78]

When you bridge SDA and GND and plug a Lipo in - does the red LED start blinking then?

[blackdrone911]

No

[awolf78]

OK, I suggest you open a support ticket with the dealer you bought the PDBs from - it is up to them to decide how to handle this.

[tommymcnab]

Having an issue with my gen one mr Steele Alien setup had it saying no connection to fc and then I hooked it up last night al of the sudden started working was micking around with it and the video started becoming grainy when I shook the unit and then it just dropped out back to no connection to fc I updated the fc and have also taken it apart and found two of the esc had loose wires still no fix though have resoldered connections to cam video transmitter am quite baffled with what to do so anything will help thank you in advance!!!!!!!