DakeFpv h743 INS error

Hardware
1

Bought a new Dakefpv h743
Connecting to misson planner after flashing Arducopter an error is seen in the data tab.
”Config Error: INS: unable to initialise driver”
”Config Error: fix problem then reboot”

Reflashing or rebooting does not help & the error is constantly seen.

Loading betaflight, the configurator shows correct imu data.

Note: No other external hw connections were made, just usb plugged into the controller.

2

Just some guesses here…

  1. Are you sure you have the correct firmware for your FC? I see there is a “Pro” and non-pro version.

  2. Have you tried other USB ports?

3

Thanks for the reply Mike!
I have loaded the correct fw (not the pro), as a check I tried the pro version too but no luck..

There’s only one usb port on the fc.

4

Interestingly, I reached out to the aliexpress seller & they provided me a firmware.
DAKEFPVH743-Copter-V4.8.0-dev
This seems to work fine.

5

Glad they got you going, but I do find it a little odd that the seller provided a firmware.

If the same thing were to happen on the next firmware release, I may begin to wonder if I got a FAKEFPVH743.

1 Like
6

I would suggest trying the dev version from the official download site and see if that works then report back
Dakefpv H743 4.8 Dev

If it doesn’t the board probably isn’t legit.

7

Thanks Dave.
That’s what I exactly tried & it doesn’t work. Highly likely that the board is not legit.
Time to return it back :slight_smile:

Thanks for the help here. Cheers!

1 Like
8

That’s good info for the forum. Thanks for following thru on that! Out of curiosity did they just send you a .apj file?

1 Like
9

No they sent all the files we have on the arducopter downloads i.e. the hex with bl etc.

I’m new to arducopter (only a day now :D) and therefore still just learning this stuff.

Once I learn to build the code & flash, I’d be intrested to attach via debuggers to see where this fails during the init routines (if my return is not accepted), I suspect they’re claiming a certain imu but really use a cheaper one/clone which probably has different driver requirements

1 Like
10

That’s almost certainly what’s happening. They’re using an IMU that doesn’t match the hwdef. It’s technically possible to do some forensics and find out what they’ve changed, but it’s not worth the time. Thanks for the due diligence to discover the likely counterfeit.

1 Like