Greetings,
Did the update to 4.5.6 on my drones, and on one of them (hex, Matek F405-miniTE, using F405TE firmware) got a weird glitch: after reboot, motors keep jerking and beeping in sequence.
ESC calibration from MissionPlanner doesn’t work (i.e. when I unplug and plug battery, no calibration tune is played).
Tried both 4.5.6 and 4.5.6blheli variants…
The drone was fine flying on 4.4.3 previously. (though haven’t had a chance to try to roll back a version or two).
Post a parameter file from 4.5.6
My guess is that you have the wrong value of SERVO_DSHOT_ESC
Here are the parameters when it was glitchy, however today I tried to roll back to 4.4.4, it popped some error message (i didn’t capture), I re-run loading of 4.5.6, now drone boots up normally, arms as requested, spins up and does its normal actions. So … beats me what happened before… 
Must be one of the arducopter weird things… like when I spent 2 days fighting with SiK telemetry radio on another drone, only to find out that it doesn’t work on SERIAL6 (labelled on FC as Tx2/Rx2), but works perfectly fine on SERIAL1 (Tx1/Rx1 on FC board)
hex_4.5.6_glitchy_motors.param (19.1 KB)
Thanks everyone for help.
FRAME_CLASS,2 FRAME_TYPE,1, double check your motor ordering. DShot digital ESC no calibration needed.
MOT_PWM_TYPE,5 # DShot300
SERVO1_FUNCTION,33 # Cubepilot digital ESC started from 9,10,11,12,13,14, now (BRD_IO_DSHOT) I think I can use MAIN out too.
SERVO2_FUNCTION,37
SERVO3_FUNCTION,34
SERVO4_FUNCTION,35
SERVO5_FUNCTION,38
SERVO6_FUNCTION,36
Did you do anything tuning previously? your current parameters are initial before any tune. by right, should be able to copy and paste if the frame size did not change only a firmware upgrade.
by the way, one of your good friends is located here.
Motor ordering is how they are wired, using two 4in1 Mamba ESC units.
Otherwise i didn’t really do any tuning, apart from GPS.
You don’t wire it to suit your pattern, you wire it to suit the frame class, type selected, and flight controller stack understandable pattern.
If you and they confirm it is correct during the motor test produce the right order and rotation, that’s fine.
they are wired to go in ‘test motors’ order A B C D E F in a clockwise direction from front left, as per MissionPlanner’s expectations. Took me ages to pick correct mappings, as there are so many conflicting numbering settings! Motor 1 ≠ Motor A. insanely frustrating, but i guess we’re stuck with it now.
(Attachment m_02_01_hexa_x.svg is missing)
It’s from the Front Right. But if you got this wrong it would likely flip on take-off.
So, there is no problem?
yes, front right, sorry 
long day…
The jerking problem seems to have gone. I’ll take it for a test flight once the weather is good.
Thank you