External compass not detected on Flywoo Goku F745 Nano

ArduCopter Copter 4.1
,
1

Hi guys,

I am having problems with the new Flywoo Goku F745 Nano FC not seeing the magnetometer on the Matek M8Q-5883 GPS/compass module. I tried beta and latest Arducopter firmware versions with the same result.

The M8Q module is working fine with a PixHawk Lite on Arducopter 3.6. The M8Q compass is detected as QMC5883 and is working fine with Flywoo Goku F745 Nano FC on Inav. The same GPS/compass with the same wiring is working fine on Inav. I just re-flashed the FC to Inav, enabled magnetometer and got it working. Flashed back to Arducopter 4.1 latest and no mag. Tried AP latest and beta.

Looks like there is a problem with Ardupliot 4.1 firmware, not being fully compatible with Goku F745 Nano FC. The internal baro is working fine.

The FC supplier is saying that the FC has two independent I2C buses. They suggest setting the following parameter for Betaflight:
set mag_i2c_device = 2.

Any help is much appreciated.

goku-f745-35a-esc
goku-f745-35a-esc2048×1317 349 KB

mp-no-mag
mp-no-mag722×553 18.2 KB

mp-hw-id
inav-mag-working
inav-mag-working1084×499 76.4 KB

2

Review the Hwdef file for the Flywoo F745 target.

-no built-in compass and no external I2C so no compass
define ALLOW_ARM_NO_COMPASS
define HAL_COMPASS_DEFAULT HAL_COMPASS_NONE
define HAL_I2C_INTERNAL_MASK 0

The board you have is different.

1 Like
3

I have this exact same issue… The Flywoo745 nano board needs a custom build.
I was just coming on here to look where to request the build.

4

1st look at who coded the existing target. The contributors are shown at the top of the Hwdef page.

5

I am using the Matek M8N5883 GPS with Compass, and the Flywoo745 build is for the AIO, not the Nano.
It works in iNav, but I prefer ArduPilot over iNav Flywoo has a build for iNav 3 on their website for the nano board, but not for ArduPilot.

6

Yes, I know that. That was the point of my post.

7

I see. Thank you for the direction.

8

Is this something I could add to the target build? I have never tried to do that before and have no idea how to go about doing it, but I am not scared to try.

1 Like
9

Let’s see if @LavaChemist can help! Cool looking board.

2 Likes
10

Yeah, the board is really looking cool, it is only 16x16 and is stuffed with features: lots of UARTs, built in baro, I2C pads for external devices. The only thing that I could wish more is a better baro chip.

11

Thank you Dave! I appreciate the effort!

with regards,

Jude Garcia

F57D61B245D64AFF9914819FBB7E6163.png
F57D61B245D64AFF9914819FBB7E6163.png708×1 82 Bytes

12

Agree. I have a few 20x20 mini boards (Matek, Holybro, Omnibus) and it’s nice to see more small hardware with the features Ardupilot needs. The stack they are selling with this board for $60 looks nice. .

1 Like
13

next board will be the MAtek H7 mini

14

I like that board. I have it flying a sub 250g 5" and it’s very nice. It run’s hot but the IMU Temperature Compensation routine really works.

15

I have ordered both Goku’s - I will do a port

3 Likes
16

That’s fantastic! Thank you Andy.

1 Like
17

@andyp1per, txs for that.

If it is OK I’m going to drop this issue from the 4.1.0 blockers list because the Goku is not currently one of our supported autopilots. Hopefully in a future point release we can add it.

1 Like
18

I’ve managed to order the Goku Hex ESC rather than the Goku Flight Controller, it’s going to take a little longer :man_facepalming:

1 Like
19

In the mean time you could get Dshot working on that BLHeli_S ESC :smiley:

20

Does it not work?

My Goku F745HD arrived today - I have to say its a very nice board

1 Like