Telemetry is still there with battery, but no sticks or buttons work Just got the new data cable in the post so I’ll try that out to see if flashing the correct firmware resets things.
Tried the new cable, same failed serial port. I get an error message on the computer that says a driver is being blocked from running, so I’m assuming this is my IT department blocking things.
Looking on the circuit board of the mob7, it says ELRS 2.2, so I’m a bit confused as to how a brand new one out of the box comes with betaflight 4.4… someone must be flashing them before they leave the shop?
Could be a ELRS version of the quad that is V2.2 of the board, not that the software is 2.2?
You’re probably bored of the updates, but the receiver and drone are now bound.
Only problem is that the throttle doesn’t work. Every other button works, but the throttle doesn’t spin any rotors. It works on speedybee (I gave up on betaflight), but doesn’t work in real life.
The FC makes a funny sound when I put throttle to max and leave it. As if it’s trying to move the rotors but can’t…
The updates are good.
I always find I get debug a problem - when trying to explain it.
What does it sound like ?
Does it spin the motors when armed ?
When armed dies yaw/roll do anything ?
Yeh so I went on a deep dive and found someone with a similar problem. They ended up realising they had the turtle mode button pressed.
So I got it out again to see if any of buttons were pressed weirdly, and after a few goes at binding it the throttle suddenly worked!
Throughout the whole process I keep getting ‘bad telemetry’ messages from the RC, so maybe the connection wasn’t strong enough?
The sound wasn’t a motor sound, more like the old sound modems used to make! Yaw, roll and pitch all worked the first time when throttle didn’t.
I’ll try again tomorrow and see whether the connection is dodgy again. Might be a temperamental antenna? Or a loose wire on the drone?
Don’t worry too much about this, it’s fairly normal when working on the bench with the transmitter and resiver close together, the signal gets swamped.
There are other causes usually the telemetry rate settings in the TX, lots of vids on YT about it