Firmware update on one of my working drones yesterday, on prompt from Mission Planner from 4.5.7 to 4.6.0, disabled arming with persistent message to check frame type and style. Full parameter list shows both settings correct. Double checking with QGroundControl reports a bug in the new firmware. Now I’m having a bit of trouble trying to re-install 4.5.7, can anyone help? I won’t upgrade the other drones until I sort this out, I need them flying. Thanks in anticipation. Gil.
1 Like
I’ve successfully upgraded, so not exactly sure what happened for your upgrade.
I would go back to the last good .bin log, save params to a file so you have a good copy.
You could load the 4.6.0 firmware, do a “reset to defaults”, then load you params from the saved file. There are params that are “read only” and shouldnt be changed, so they will fail every time - that’s OK.
Be aware some params could have changed names, so you will need to manually go through your parameter list and match them up with the new parameters in MissionPlanner full param list and make any suitable adjustments.
Cleaner method:
The hardware checker will be able to distill your original param file down into just the ones you need but you will need to do the mandatory calibrations again (first).
Hi @gilbo211_25,
Thanks for the report. Which autopilot are you using and do you have an onboard log file and/or parameter list?
It sounds like your parameters were wiped as part of the upgrade and we have seen a similar issue with the TBS boards that store their parameters in flash but we thought it was resolved.
The downgrade back to 4.5.7 can be done using MP’s firmware install screen’s “All options”. Could you clarify what problems you’re seeing as part of the backout?
Thanks guys, apologies for any delay in getting back, it’s been raining here and I like to work outside so I receive good clear GPS. I have printed your replies and will run through them once I’m set up again. Onto it this afternoon.
1 Like
I use Pixhawk 2.4.8 controllers, they’ve proven steady and reliable and I like them. Only on the odd occasion I get one of these hiccups usually resolved fairly quickly.
Hi @gilbo211_25,
OK, the Pixhawk boards have separate eeprom for storing the parameters so it seems unlikely that the parameters would have been wiped as part of the upgrade. I think the two more likely causes are:
- the wrong vehicle firmware was loaded (e.g. plane was loaded instead of copter)
- an eeprom hardware failure that lead to an error
It would be good if you could check if all parameters were set back to their default or if only the FRAME_TYPE and/or FRAME_CLASS parameters were set. If it’s only these two parameters that were changed then it is more likely to have been a user fat-fingering the parameter list or a GCS issue.
TBH, this is not my area of expertise so we will discuss at the developer’s call tomorrow
OK, here are the two parameters lists, the one V4.5.7 arming and starting normally, and the other V4.6.0 that fails to arm, telling me to check frame class and type. Thanks again for your help, great forum very professional, much appreciated.
G3 Copter 4.5.7 parametr list.param (17.4 KB)
G3 Copter 4.6.0 parametr list.param (17.8 KB)
1 Like
Those param files have same frame settings.
Probably best to load 4.6.0 and set LOG_DISARMED,1 and try arming - upload that .bin log file somewhere and send us the link.
The only difference of any importance is
< LOG_BITMASK,176126
---
> LOG_BITMASK,180222
and even that is nothing critical.
1 Like
Hi @gilbo211_25,
Thanks for the parameter file, I don’t see anything immediately wrong. The parameters have not been wiped.
My guess is that the autopilot is running out of memory but there aren’t many features actually enabled… still, this could be the issue.
Could you load 4.6 onto the board, set LOG_DISARMED = 1, reboot the autopilot, wait a few minutes and then download the onboard log and then post it somewhere? Feel free to set LOG_DISARMED back to zero.
If you’re worried about revealing your location you could send it to me privately.
1 Like
I’m having the same problem. SpeedyBee F405 Wing. Two things:
-
I keep getting warning message to check frame class and type, but they are set correctly (X8).
-
When I click on frame type in Mission Planner, nothing changes on the servos tab - is that normal? Aren’t there supposed to be motor assignments as a person changes frame types? My servos tab is blank, except sometimes it will show a quad - 4 green bars - but still no servo assignments (motor 1, 2, 3…etc).
All quite strange.
Hi @wsalopek,
This sounds like the firmware was built without the X8 mixer. Did you use the custom build server to create the firmware or was the official/stable 4.6.0 installed?
If possible we’d like to see an onboard log file.
Official/stable. Thanks…
A regular Octo 8 work (as well as other frame types) to populate the servos (but still not assigning motors - are motors supposed to be auto-assigned?) - but if I click on X8, I get nothing.
Pardon my slowness - been using MP for a dozen years but not much in the last couple - by “onboard log file”, do you mean the Tlog? It’s attached - hopefully that’s the one you want.
2025-06-19 18-29-58.tlog (198.0 KB)
Can’t do a motor test on X8 (I can on octocopter) - Mission Planner verbally says:
“Motor test - check frame class and type”.
And a dialog pops up saying “Command was denied by the autopilot”
And of course when I check the frame class and type, I see that I have the X8 highlighted in frame class, and “X” is selected in frame type.
I have rebooted etc, a hundred times, cycled thru frame types, etc etc.
Another odd (and related?) thing - when I go to the servo tab, I have zero green “bars” (might be yellow, I’m colorblind) - but I do have Motor 1 thru 8 selected under “function”.
I recently posted much the same query here recently, after receiving the same message following firmware update to 4.6 on one of my hexacopters. I finally reloaded 4.5.7 and resolved the issue as I needed to keep flying. Q Ground Control reports possibility of a bug in 4.6 but fails to specify what it might be. Good luck with it.
Did you have a Speedybee F405 flight controller also?
Yes I do Dave, SpeedyBee F405 Wing.
Yes, I saw you mention that, I was wondering if @gilbo211_25 also had one to narrow it down to the hardware which I would guess is where the problem lies.
Looks like OCTA QUAD was removed from the enabled feature set on (some or all) F405 boards:
!AP_MOTORS_FRAME_OCTAQUAD_ENABLED
https://firmware.ardupilot.org/Copter/stable-4.6.1/SpeedyBeeF405Mini/features.txt
1 Like
Thank you Yuri - and I can confirm it’s the same on 4.6.0 as well as 4.5.7 - haven’t looked farther back than that.
What does it take to get that exclamation point removed?
Thanks again…