There is numbers that looks strange, but no "NaN" this time....The cruiseControl should stop motors after some angle: default is 105°, here set to 80°Did you set the motor neutrals ? > motor starts at 1030 ?Be sure the motor don't stop completely to still have some control over rotation.The min motor is 5, maybe it really stop because wrong neutral ?Try with quad in hand, without props and try to reproduce without fly and take attention to board reboot (monitor flighttime) or something weirdCan you give details for template you used ? CPU alarm is caused by all options enabled: TPS, board rotation and Gimbal... maybe too much for CC3D
Quote from: f5soh on February 13, 2016, 09:26:57 pmSorry about that, maybe a CC3D related to Gimbal module.It could be interesting see if a Revo has the same issue.An update. I disabled the gimbal function and went out again, sure in rattitude mode with cruise control the freaky my thing rolls, motors stop and don't come up again....faling brick. I went up in rate mode again with manual throttle and I could flip and roll just fine switched back to rattitude and first roll was ok, second too third one....yep, again faling brick. Something is wrong with the cruise control execution. Sure the motors "stop" after a certain extent angle but they don't spool up again. I can tell you it is t nice to see your quad telling so much abuse and damage because you can't control it anymore. Broke already 6 props, one fpv cam, 3 arms, one VTx antenna....The only way to flip or roll on this board is apparently in full rate mode.
Sorry about that, maybe a CC3D related to Gimbal module.It could be interesting see if a Revo has the same issue.