@wjaxxx wrote:
We have been using 3.3 in our copters for a while now and we see a lot of issues with compass variance.
We are quite sure there some be something in the code that is triggering these errors as it happens with a bare pixhawk on the table.
In our particular case we sit a standalone pixhawk in a table and connect with usb. We connect thru mission planner and elf is OK. We take it and give 180deg yaw turn and elf is red.
Why?Same happens in flight with external compasses etc. I have even seen a small toilet bowl one of the times .
We know it is not interference as it happens with no motors running and as mentioned with a standalone pixhawk.
If we install 3.2.1. everything goes smooth.
So any ideas?
Thanks !!
Posts: 1
Participants: 1
