Of the 2 Flywoo Goku GN 745 AIO V3, one of which is BLHeli32 based gets GPS recognized not the compass, whereby the compass does not get the HW ID and therefore does not show in Compass window in AP for calibration. This same GPS/compass gets recognized on the AM32 based Flywoo GN745 AIO. Same issue was reported earlier here . Here a new hwdef was created by @andyp1per to fix this issue. I am on AP 4.6.3.
.
Please try on 4.7.0 to see if its fixed
I am not sure that there are hwdef issues, if you have the same firmware on two boards whose only difference is BlHeli32 vs AM32 (which I believe are otherwise identical pin to pin, trace to trace, chip to chip).
(Flywoo F745 Nano is a different board, you should not need testing that firmware on an AIO, this will not help)
Have you checked your wiring?
Have you tried to swap the compasses and see what happens?
Hi @MaxBuzz - I have numerous GPS of the same kind that work flwlessly. I swapped them without success. Both FC and GPS/Compass have JST connectors.
My feeling is that it is the I2C (SDA/SCL) bus on the FC is defective. Thoughts?
It can be that. To test that out, you may try to connect a different I2C device (a compass by a different manufacturer, or an airspeed device, or something else you have available) and see if it is recognised by a “good” board and a “bad” one. It may indeed be that you are unlucky with the I2C bus on that board, in which case you may try to contact your reseller or Flywoo themselves.
I did exactly that as well, and I forgot to mention it. I did test with this working Mateksys GPS with the same results.
Then, likely, condolences for your hardware. I had to scrap a similar board (v1.2) after I destroyed the barometer with a drop of conformal coating, and then destroyed the USB interface when attempting to reflow the barometer.
Maybe it still makes sense to shelve it in the hope that it’s not hardware fault and someone finds the reason, but my impression it will be for parts.
Thanks @MaxBuzz . I was thinking of still using it with compass-less navigation. Seems other community members have been using it.
Thanks @MaxBuzz . I was thinking of still using it with compass-less navigation. Any thoghts or experince with that navigation? I have seen othe community membesr using this mode.
Ah, surely, I was too quick, sorry. Was still reflecting on my barometer-less and now USB-less board.
I often go compass-less too, in particular, my current Flywoo F745-based 5" quad does not have a reliable place for a compass. Though this is somewhat rectifiable via compassmot, I found out that the overall performance with the Gaussian Sum Filter is more than enough for an RTL, and that particular machine is mostly about acro flights anyway.
Thanks for giving me hope 
. I will give compass less naviagation a shot. So the only 3 parameters to be changed are as follows?
COMPASS_ENABLE = 0
EK3_SRC1_YAW = 8 (GSF)
Arming_Check = 1048058
Usually it’s all about setting all COMPASS_USE variants to zero. Without a compass, it will fall back to GSF even without setting yaw source in EKF. And you don’t have to alter arming checks.
COMPASS_ENABLE to zero should also work. Sometimes you may want to enable compass, see it in the logs, but not to use it - this is when COMPASS_ENABLE should still be 1. Right now I am flying that machine with a compass attached, enabled, logged, but not used. (It is also rotated 180 degrees compared to the previous installation and not recalibrated, better fix that eventually).
P.S.: GSF will require you to converge on direction before going to any yaw-managed mode, and will not let you arm in e.g. Loiter on the ground. In my 5" quad use case it’s not a problem, I’m starting off in a manual mode anyway. In the past, however, I attempted compass-less loitering with a machine that cannot fly fast horizontally. With a questionable GPS signal, vertical lift-off and a bit of wind it learned a wrong direction and started flying away in an attempt to hold position. I had to rebuild that machine to fly with a compass.
Thanks! Changed Comapss_enable and Arming_check to default and comapss_use to 0. Left EK3_SRC1_YAW = 8 just to be safe. I will ensure that I take off in Satbilize mode for direction convergence and then “safely” try loiter. I will start a new thred on compass-less navigaiton on my findings as needed.
Thanks once again @MaxBuzz . Happy Flying!!
I looked at the hwdef - its all correct on 4.7. Probing is enabled and there are pullups on i2c
Thanks @andyp1per !
