The one thing you forgot, was if a pilot does an incorrect CLI dump, and is actually able to save and execute the dump, then the quad will load up, show that you have telemetry, and even lose telemetry when you unplug the quad. But not arm. And you notice in the modes tab, that when you go to arm, the little ChickLit moves into the slider range, but arm is not highlighted. Nor are some or all of the different things like air mode, horizon, crash flip, etc.. So the solution obviously is to find the correct CLI dump. It happened to me, I found this video, and then later was lucky enough to grab the correct CLI dump for a GEPRC phantom analog. Hit me up if you need it.
@@midge9740 my first thought says check your channel mapping. And also go back to the receiver tab and make sure that the arm switch (and all others in correct order) is actually popping up when you engage it. If it isn’t/they aren’t popping up in the right order…then check your channel mapping on the radio versus Betaflight. Off memory, that’s my best idea.
I have Many qwads now that i have bound (BetaFPV TX module and HM EP2 RX's) and BF gives RXloss in cli tab, and still do not arm. what else could be holding ALL my qwads from arming? I only have one qwad, using ELRS that is bound, able to get into BF and running great. My other 8 get nowhere.
$M>âtARM;FAILSAFE;BEEPER;OSD DISABLE SW;BLACKBOX;AIR MODE;FPV ANGLE MIX;BLACKBOX ERASE (>30s);CAMERA CONTROL 1;CAMERA CONTROL 2;CAMERA CONTROL 3;FLIP OVER AFTER CRASH;PREARM;VTX PIT MODE;PARALYZE;DISABLE VTX CONTROL;LAUNCH CONTROL;¬$M> ¼$M> ng Entering CLI Mode, type 'exit' to return, or 'help' help me plase
