Posts: 668
Threads: 31
Likes Received: 208 in 158 posts
Likes Given: 95
Joined: Feb 2019
Reputation:
14 Make sure that you have the correct firmware flashed to your FC.
If that doesn't help, I would unninstal and reinstall betaflight software on the pc, but I'm pretty sure that I've seen some errors like that happening when the fc firmware is not the perfect match.
Posts: 5
Threads: 0
Likes Received: 3 in 3 posts
Likes Given: 0
Joined: Jan 2019
Reputation:
0 09-Sep-2019, 01:12 AM (This post was last modified: 09-Sep-2019, 07:05 PM by ielbury.) This is caused because when an early pre-release/custom version of 4.0.0 is installed on the Fight Controller and the latest version of the Betaflight Configurator does not work correctly with these unofficial releases. This is common with the various whoop style Flight Controllers as they were released with either a Oct or Dec 2018 4.0 pre-release version.
You have 2 choices:
1. Flash the controller with an officially released version of 3.5.X or 4.0.X.
2. Roll back the version of the Configurator to an older version.
This looks like a Crazybee controller so I would recommend going to the latest 3.5.X version as the 4.0.X versions can be a bit temperamental for whoops IMHO ... fine for 3" and 5" quads. The 4.0 pre-release is for the most part 3.5 as the big changes were merged in 2019 so you can use the same PID's.