Servers by jDrones


Hi Guys,

I’m after a little help setting up my flight controller for singlecopter.

My flight controller is pointing straight up AND it’s at 45 degrees to the flaps… So I essentially have an x flap configuration instead of +
I assumed that I’d pick a number from the list on AHRS_ORIENTATION but I don’t see my combo on there… I need pitch 90(although the guide says 270), and yaw 45. Is that correct?

Any help here would be really appreciated.


Try and mount it 0deg x y and z if you can. Otherwise there are individual parameters for x,y,z offset of ahrs

you can use a custom rotation, just be sure to check the hud is moving as expected

Thank you guys. I’ve found the three custom sliders and am currently trying to get it set right.

On some of the older systems, the compass has needed to be less than a few degrees of level to work correctly.

I have the GPS/GNSS antenna MCX, does that also have a compass as I can mount that in any direction and orientation.
I’m worried that any onboard compass won’t work correctly with the board pointing up and the belly of it facing N/W.

I have found an issue with Custom AHRS.

If I set AHRS_ORIENTATION to 34, that is Roll 180 and Pitch 270(-90) then it sits perfectly with the board pointing downwards and the artificial horizon level.

However… If I set AHRS_ORIENTATION to 100 and AHRS_CUSTOM_PIT to -90 and AHRS_CUSTOM_ROLL to 180 with the board in exactly the same and un-move position, pitch is about +27 degrees and the roll is out by about 30.

AHRS_ORIENTATION set back to 34 (which is the same as above) and it goes back level.

It’s as if the custom settings don’t work. Which is a real pain because I need my board to be pointing down and at 45 degrees on the Y axis as it’s mounted on a hexagonal frame with a plus single copter fin configuration.

Anyone else have this issue?

Have you had success calibrating this hardware in normal orientation just as a test?
I found the compass data output values on a ulbox m8n knock off, were incorrect. And the sensor outputs are as if the sensor was upside down, even when it was right way up.
Just an idea, if this isnt proven hardware that youve previously had running

I’ve disconnected the external GPS so it should just be using the Navio2 onboard stuff.

I’m trying to set AHRS_CUSTOM_PIT to 90… It goes +30 on the Hud… I deduct 30 from the -90 to -60 and it goes -30 on the Hud… I can’t even compensate for the offset that shouldn’t even be there in the first place.

My Pi3 B / Navio2 is point down to the floor, it’s sat on my desk strapped to a cube for easy accurate rotation yet I can not seem to get even the pitch and roll custom to work correctly.

I had real trouble understanding the outputs of the magnetometers, i ended up using qgc which gives more info. Then once i knew what the issue was i went back to mp

This is with

With AHRS_ORIENTATION = 34 it’s level???

Surely, that is an issue with MP?

I used this info, and qgc which gives the live raw output data for each mag, (possibly mp does too, but i couldn’t find it) to work out what was going on.

For my dodgy external gps / mag i need roll 180 on the external mag when it is phisically mounted inline and the same way up as the fc

Board is level (default)

There is no way that is 10 degrees pitch and roll

Yes i see, so it doesnt look correct with board level and 0,0,0 in the offsets?
Even after a compass cal?

I always get Accelerometer Calibration failed, I’ve just noticed this.

Every single preset AHRS_ORIENTATION is correct. It is only when I try to use the CUSTOM settings that it is incorrect.

Perhaps this is a bug with MP?

Perhaps, i have only used some of the presets, never a custom. Sorry

Servers by jDrones