I emailed FrSky about it and they replied saying an engineer would take a look. Note, this incorrect telemetry is only visible on the Tx. When I converted the one to 2.4Gz (because of the RSSI problem), the random current spike telemetry went away as well. It appears to be totally random like the RSSI issue. The Power value is also thrown of by the phantom current spike. This is caused from an incorrect Current telemetry value which I can see in the Max Amps recorded for the flight. I have it happen quite often where the tx suddenly displays over a million mAh used in the consumption telemetry value.
#Tbs discovery pro rssi software
This receiver also has RSSI level output indication and its software can be.
#Tbs discovery pro rssi upgrade
Now they just need to fix the random high Current telemetry values being sent back to the Tx over S.Port/F.Port. Damper upgrade set for your TBS gimbal on your TBS DISCOVERY PRO frame. Apparently the randomly incorrect RSSI is what was tripping the flight controller into failsafe. I haven't had a single dropout since switching to this version. I've flown about a dozen packs so far on the new 181228 production firmware. Pretty much ready to give up and go Crossfire at this point.except that I have a Hours x10s.which leads to more issues to be able to use CF. The latest versions also have a glitch where the current telemetry will suddenly have an impossible value (like a million amps) which throws off the Power and mah used values as well. Any ideas?īTW, I've tried the last stable firmware for the R9Slim+ as well as the Flex, and latest FCC beta firmwares. So, I wired a Furious 2.4 Ghz receiver instead. I was starting to lean towards a HW/SW incompatibility of some kind with BF the the R9slim+ specifically. txt extension from the end.I'm surprised log files aren't supported here?Īny suggestions of what is going on would be appreciated.
Here is a Blackbox log with a cutout right at the end. GoPro and FPV camera mounts Power Distribution Board (PDB) Traces and pads for clean RC receiver to Flight Control wiring RSSI trace to the TBS CORE. I've tried 3 different R9 Slim+ receivers, two different wire harnesses, and multiple antenna layouts. Sometimes the signal received flag goes to 0 but comes back soon enough that the "valid" flag doesn't trip.
Everything is going fine when out of the blue, the RX Signal Received goes to 0 (from 1) and a short while later the RX Flight CH. I'm trying to use an R9 Slim+ receiver with a Matek F711 / Spedix GS40 4in1 ESC / Tramp HV Vtx / Matek GPS-Compass module. Valid" flags? (from the Blackbox logs) I have a new quad that won't make more than 10 minutes of flight before just dropping out of the air.usually while the RSSI is in the 90 range. Could one of the developers tell me where BF gets the data to determine "RX Signal Received" and "RX Flight Ch. Here based on UWB RSSI Data Analysis, a fine-tuned trilateration algorithm is designed to get the indoor coordinates with enhanced and improved accuracy by 20-30.
0 kommentar(er)
