qq190 quit recognizing receiver

2.47K viewstroubleshooting
0

Brand new qq190. Had it flying 30 minutes out of the box on SBUS with X4R-SB. First flight 5 minute hover LOS no issues except the stock camera went completely out of focus after the 5 minute hover. The goggles were on during the flight and then I picked them up after I landed.

Installed the upgraded camera and that one works fine. Second flight hovered about 2 minutes after landing and disarming noticed that the LED strip had quit working. Tried to arm with no luck. Looked through the googles and it said “looking for Spektrum1024”. Every since then it will not recognize a receiver input. Even tried switching over to PPM with a DR4-II via PPM.

Back to SBUS now. Sticks are centered at exactly 1500.

Connecting with Betaflight all receiver inputs are grey and zero.

I never flashed it or changed any settings so symptoms are:

  1. will not sense SBUS receiver with sticks centered at 1500 even though it did that successfully on first try out of the box and yes the bind is good. Green light on receiver and good RSSI telemetry.
  2. LED strip doesn’t work anymore. Gives a quick white flash on power up.

Ready to go back to Libre and CC3D. The Colibri just won’t comm with a receiver on PPM or SBUS. This is my first round the TBS stuff. been doing open pilot, Libre and Ardupilot for 5 years.

Support said I might reset with TBS agent. Tried that on Win7, Win8, Win10 and TBS agent says “none connected”. I tried all the different drivers your supposed to use and also tried on a virgin Win10 without the drivers like some have said. Betaflight will talk but TBS Agent will not.

Any suggestions?

0
Mark Prince (anonymous) 0 Comments

camera is not dirty. There was no crash just a 5 min hover. I’ll send a screen capture from the goggles.

Yes I”m plugging into the top port using the same cable I am using Betaflight with.

So I stayed up all night, read the BF wiki, the power cube manual, etc. etc. and figured everything out. Configured everything from scratch and have everything working. Took about 6 hours. Obviously a lot of trial and error involved in that process since I am new to colibri and Betaflight but that is what I do in my day job.

I am now versed enough with the TBS stuff for scratch configs. Just hope it doesn’t revert again while flying. Actually when it originally reverted to a receiver config that doesn’t work I was doing a disarm/arm, LED goes out and it starts looking for a Spektrum1024 when I was doing serial sbus.

I’m using the tune from the qq link dated 12/2016. Don’t know if that’s what it shipped with. Dont’ think it is cuz the rates are different than when I took it out of the box.

Haven’t gotten to fly it yet cuz I gotta work on my day job.

0
Mark Prince (anonymous) 0 Comments

camera is not dirty. There was no crash just a 5 min hover. I’ll send a screen capture from the goggles.

Yes I”m plugging into the top port using the same cable I am using Betaflight with.

So I stayed up all night, read the BF wiki, the power cube manual, etc. etc. and figured everything out. Configured everything from scratch and have everything working. Took about 6 hours. Obviously a lot of trial and error involved in that process since I am new to colibri and Betaflight but that is what I do in my day job.

I am now versed enough with the TBS stuff for scratch configs. Just hope it doesn’t revert again while flying. Actually when it originally reverted to a receiver config that doesn’t work I was doing a disarm/arm, LED goes out and it starts looking for a Spektrum1024 when I was doing serial sbus.

I’m using the tune from the qq link dated 12/2016. Don’t know if that’s what it shipped with. Dont’ think it is cuz the rates are different than when I took it out of the box.

Haven’t gotten to fly it yet cuz I gotta work on my day job.

0
Anonymous 0 Comments

Hi, strange issue with the stock camera- they are glued in place- it sounds like maybe something else is going on.  It’s possible the lens is dirty, or, in some cases during a hard crash, the IR filter can come dislodged causing a blurred reddish effect.  If this has happened to you, you can re-glue the filter if needed.

Installed the upgraded camera and that one works fine. Second flight hovered about 2 minutes after landing and disarming noticed that the LED strip had quit working. Tried to arm with no luck. Looked through the googles and it said “looking for Spektrum1024”. Every since then it will not recognize a receiver input. Even tried switching over to PPM with a DR4-II via PPM.

-interesting issue- it sounds as though the FPVision layer reset.  I recommend running the calibration again.   Did you do any software updates?

it said “looking for Spektrum1024”. Every since then it will not recognize a receiver input. Even tried switching over to PPM with a DR4-II via PPM.

-Did you try switching it to SBUS? It should say “waiting for Sbus” and should go through the calibration once you center your sticks.

Connecting with Betaflight all receiver inputs are grey and zero.

-This will happen if the OSD is in calibration mode.  You can skip it to configure manually in Betaflight if needed by entering the OSD menu with the button on the side of the powercube.  Hold it for 3 seconds and it should get you into the menu (recommended for advanced users only)

Can you verify that your receiver is plugged in properly?  Sometimes they can be installed backwards which can lead to a signal not making it to the powercube.

Support said I might reset with TBS agent. Tried that on Win7, Win8, Win10 and TBS agent says “none connected”. I tried all the different drivers your supposed to use and also tried on a virgin Win10 without the drivers like some have said. Betaflight will talk but TBS Agent will not.

Is it possible for you to try a different USB cable when connecting to your computer?

Can you verify that you are plugged into the top USB port on the powercube?

 

Hopefully this gets you on the right track.

Question stats

  • Active
  • Views2469 times
  • Answers3 answers