Ok, Got two quads - one on 3.0.0 and one on 3.0.1rc1.Both had excellent loiter on 2.9.1, and both worked perfectly in MP on .53.Now both toilet bowl badly within a minute of engaging loiter. Stabilise and alt hold are ok.I have performed the following on for both:- ESC cal- Compass live cal- Radio cal- Accel calI have *not* done compassmot. Two questions follow...1. Do I need to?2. Isn't the compassmot procedure quite onerous and even dangerous? Even I'm worried about it, given the CF 14"'s, 6S power and 3508's spinning at near full power...Are we expecting new users on APM 2.6 (assuming these come with 3.0.0) to be able to perform this? I'm not really sure compassmot is a step in the right direction, is all, if we hope to attract more users to the platform.My second problem...Both quads on 2.9.1 and MP on .53 and same hardware had no problem using USB and the CLI to download logs, setups etc.Now...on .56...I just get garbage on the screen!It's like when you connect via flight data, then switch to CLI. Except I've been nowhere near it, and my log download procedure is the same as before?
You need to be a member of diydrones to add comments!
The compassmot is almost mandatory now, had the same sort of toilet bowl issue, until I bit the bullet and did the compassmot.
My large hex is also a frightening beast but if you use the method of moving the props around by one place you can set it up and do it via radio link with the copter at a safe distance. Just be aware of FOD! and make sure the surface is clean and nothing will get sucked into the blades and all should be well.
The garbage is the MavLink binary you are seeing, which will happen if the copter has sat for enough time powered up before you connect. Usually just hitting the reset button and then the Terminal will do it, even over a radio link now, unless you want to do logs, then you will need USB.
Replies
The compassmot is almost mandatory now, had the same sort of toilet bowl issue, until I bit the bullet and did the compassmot.
My large hex is also a frightening beast but if you use the method of moving the props around by one place you can set it up and do it via radio link with the copter at a safe distance. Just be aware of FOD! and make sure the surface is clean and nothing will get sucked into the blades and all should be well.
The garbage is the MavLink binary you are seeing, which will happen if the copter has sat for enough time powered up before you connect. Usually just hitting the reset button and then the Terminal will do it, even over a radio link now, unless you want to do logs, then you will need USB.