I have 2x Here4 units and looks like one of them has bad compass. I thought it was bad setup this is why i started this thread: Here4 Compass DevID
but after switching to the other unit i realized it is not the param setup.
Comparing the here4 params on both working and not working the only diff is that the unit that is not work has “CAN_FDBAUDRATE,8000000” and the working unit don’t have this one at all.
I guess it is not related since it also have “CAN_FDMODE,0” but correct me if wrong here…
@guyzoler please set FORMAT_VERSION 0 on Here4 modules and retry. To verify id Compass data is being published, Goto DroneCAN tab in Setup, can click Inspector. Check if you see MagneticFieldStrength message show up. Also make sure you calibrate Compass after swapping Here4 modules.
Ok… what do you need me to do? I also updated the firmware on the here4 and I flew it and was auto tuning and everything was going good for about 4 mins and she went off the rails again. Although it was long than before update.
Hi, I have the same problem as Thomas. Is it possible that this is software, not hardware problem? UAVCAN Inspector didn’t show any MagneticFieldStrength report, thanks
@palma if you are running the latest firmware updated through mission planner and not seeing Magnetic Field Strength please contact your reseller for support.
I have the same issue. No MagneticFieldStrength in the CAN inspector, and no COMPASS_DEV_ID in the param list. Interestingly there is a BARO1_DEVID that doesn’t appear on another Here4 I’ve got with a functioning compass?
What are my options if I wasn’t the original purchaser of the Here4, so have no knowledge of the original seller? Any more detailed debugging I can try to diagnose the issue? Any findings from the above RMAs?