Mateksys H7A3 Slim issues

Dear Forum,
I try to use Mateksys H7A3 Slim together with my FPV glasses for distance indication and artificial horizon, nothing fancy.

Unfortunately the distance is resetting periodically ~20sec…

On top of this the artificial horizon behaves badly: I keep the plane leveled, indication is ok. I lift the nose slowly, the indication is showing that I put the nose down for 2-3 seconds, after a while it goes the correct way, in 10 sec I have correct indication ..???

I use mission planner to configure, and different version of arduplane hex.

There is a secret configuration I need to tune to get it work right ?

Thank you

Andrei

Do you have a .bin log file with log_disarmed set to 1?

No just following the documented configuration process.

Thank you for your answer. I just found out that I was supposed to have a bin file. Apparently I can not download it, or I do not have it.

I tried to do all sort of setting, increase filter cut-off frequencies, different EKF or even off … behavior does not change at all!!!

Should I send back my Mateck for reimbursement ?

Reflash the firmware. Go here and download the arduplane.apj file: Matek H7A3
Then use Mission Planners “load custom firmware” option and select it.

Thank you for the input, I got: no need to update hex already on board.. or something.

I just realized a big limitation of my board: it only works if the PCB has the bottom up ( components down) WHO designs a board to be used only like this ??? I tried to recalibrate the accelerometer to use it nomaly ( for me ) but then the symptoms from my first post show up… this is NOT ok Matek!!!

Is there a setting to fix this ?

I did not tested the distance reset issue yet

That’s nonsense.

Of course there is. Some details here Board orientation

I don’t think that is the problem. User error.

I do not see any potential problem as the manufacturer provides quite sufficient information on using their product.

“Sufficient info” is very relative. They still did not answered to my message .. but everyone sees the world differently

Is no doubt that is user error @dkemxr

Still i count on the good samariteam to point me where is the setting that configures this unit to work properly with the pcb botton down.

If you look in the description shown linked by @Jai.GAY you clearly can notice that the standard us is with Components on downside. You was able to get the information before ordering the FC. So this is not a fault.
You are able to configure ardupilot in nearly any rotation as linked by @dkemxr
You didn’t send a log file as requested by @LupusTheCanine
You didn’t show how your FC is mounted to the aiframe
So what you need more from the the good samariteam?

1 Like

All you need to know is in the link I posted under “alternative orientations”. How do we know how you have mounted the board? Just saying it’s component side down doesn’t define it sufficiently. After you have configured the AHRS_ORIENTATION Parameter correctly use Mission planners HUD to determine if it’s right.

1 Like

Kudos Dave : Roll 180 deg

Nice! That would have been my 1st guess but you could have also rotated it in another plane so no way to know.

This only shows your setting but how should someone can check if it is correct if you don’t show also how your FC is mounted.
So show ALL DETAILS

1 Like