E.T.s OMNIBUS F4 Autopilot...Which one to buy..?...AKK

English Turbines · December 22, 2017, 11:43:12 AM

Quote from: BigT on December 22, 2017, 11:33:30 AM
Well i have done it bothe ways with the same result. The acc is 270 deg out on all 3 axis. Just tried it on an F3 board and that fine as well. So it is a fault with the AKK board in iNav but not in BF.

Yes, it's very strange indeed....How can it right in BF but not in iNAV?

It almost sounds like the first calibration setting you have done is with the board the correct way up rather than upside down?

The first diagram in the Wiki is definitely upside down as I see it. Is this what you did?

:vulture:

BigT · December 22, 2017, 11:47:20 AM

No, in my view Dia 1 is right side up as the props are up, Dia 2 is upside down, Dia 3 could be flying to the right or from the right. I am going to ask on the wiki for clarification.

English Turbines · December 22, 2017, 11:53:51 AM

Quote from: BigT on December 22, 2017, 11:47:20 AM
No, in my view Dia 1 is right side up as the props are up, Dia 2 is upside down, Dia 3 could be flying to the right or from the right. I am going to ask on the wiki for clarification.

I just looked at the diagrams again, you are right the first diagram is the right way up.

It is possible they have loaded the chip on your board backwards, but it doesn't explain why it works in Betaflight does it?

They need to put an arrow on their diagrams 3,4,5,6 to clarify the direction of flight, this part is open to error, an arrow head alone looks like it's part of the copters body, and on views 1 and 2 that "Arrow Head" is not shown..

:vulture:

BigT · December 22, 2017, 12:25:22 PM

Quote from: English Turbines on December 22, 2017, 11:53:51 AM
I just looked at the diagrams again, you are right the first diagram is the right way up.

It is possible they have loaded the chip on your board backwards, but it doesn't explain why it works in Betaflight does it?

They need to put an arrow on their diagrams 3,4,5,6 to clarify the direction of flight, this part is open to error, an arrow head alone looks like it's part of the copters body, and on views 1 and 2 that "Arrow Head" is not shown..

:vulture:

So here is the answer from a developer

"Place model on all sides in sequence (positions 2 to 6): on its back, right side, nose up, left side, nose down. Press "Calibrate Accelerometer" button for in each position. The advanced calibration algorithm will record 2nd to 6th data points. There is no time limit for this calibration. the 30 secs is for the compass cal."

Seems that the pointy bit is supposed to be the nose not the tail. I am looking further into cal issues on the RC Groups iNav thread

English Turbines · December 22, 2017, 01:47:26 PM

"Place model on all sides in sequence (positions 2 to 6): on its back, right side, nose up, left side, nose down. Press "Calibrate Accelerometer" button for in each position. The advanced calibration algorithm will record 2nd to 6th data points. There is no time limit for this calibration. the 30 secs is for the compass cal."

Seems that the pointy bit is supposed to be the nose not the tail. I am looking further into cal issues on the RC Groups iNav thread
[/quote]

Hi m8,

"Seems that the pointy bit is supposed to be the nose not the tail"

I rest my case, in fact initially I thought this too, the pointy bit could be construed as part of the Copters body.

The big problem here as I see it, is that you posed the question to a Developer....Predictably, he gave the unwanted response and ignored what you were saying about the copter diagrams. Herein, lies the problem.
He's probably thinking most people get the diagrams, but he could not be more wrong. They are open to interpretation as we have just proved.

"The problem with communication, is the mistaken belief that it's actually happened"

:vulture:

BigT · December 22, 2017, 01:49:55 PM

Quote from: AdamG on December 19, 2017, 05:18:23 PM

Adam I am interested to see if your AKK board has the same issue as mine re the direction issue.

English Turbines · December 22, 2017, 01:53:08 PM

Quote from: BigT on December 22, 2017, 01:49:55 PM
Adam I am interested to see if your AKK board has the same issue as mine re the direction issue.

If the Giro Chip has text on it, you could do an orientation comparison...?

:vulture:

English Turbines · December 22, 2017, 02:35:21 PM

This would help take some of the doubt out of it....

Its saved as a jpg....so they should be able to update the Wiki..

:vulture:

BigT · December 22, 2017, 08:05:45 PM

I agree so why dont you update the wiki?

Further to the issues. I have just flashed the board with Betaflight and set the configuaration mixer type to airplane and the board is spot on with no changes or adjustments.
Gin Time

English Turbines · December 22, 2017, 09:54:39 PM

Quote from: BigT on December 22, 2017, 08:05:45 PM
I agree so why dont you update the wiki?

Further to the issues. I have just flashed the board with Betaflight and set the configuaration mixer type to airplane and the board is spot on with no changes or adjustments.
Gin Time

Hi m8,
I updated the Wiki page, but I screwed up a bit....I have the url there...but not the image...heeeeelp.

:vulture:

English Turbines · December 23, 2017, 10:50:11 PM

Github Wiki page has been amended with clarified accelerometer calibration diagram.....:)

Got my son to do it...

https://github.com/iNavFlight/inav/wiki/Sensor-calibration

:vulture:

BigT · December 27, 2017, 01:13:13 PM

Just had input from an experienced iNavver saying that iNav " iNav and Betaflight use different default values for board orientation in the target definition source files.". Cannot see this but it may be true. Anyhow I have AKK on the case now and maybe can get a replacement. Incidentally they are looking for testers and reviewers for their boards. You might apply?
http://www.fpvhub.com/index.php/topic,52383.msg274978/topicseen.html#new see post #19

BigT · December 27, 2017, 04:36:31 PM

So update: I have decided to just wire it up and see what happens. This was prompted by the arrival of the ublox today. I have wired it and now can smugly report that the gps is configured and getting 14 sats indoors. Happy Days. Next job is deciding how to power the board. I think I am going with the 10 amp sbec Siamese wired from the ESC to flight pack plug and then to the ground and positive on pwm1 with the red wire from the esc removed. However I would like to have the battery voltage and current monitored so any ideas on how I should do that would be most welcome.

English Turbines · December 27, 2017, 05:10:33 PM

Quote from: BigT on December 27, 2017, 04:36:31 PM
So update: I have decided to just wire it up and see what happens. This was prompted by the arrival of the ublox today. I have wired it and now can smugly report that the gps is configured and getting 14 sats indoors. Happy Days. Next job is deciding how to power the board. I think I am going with the 10 amp sbec Siamese wired from the ESC to flight pack plug and then to the ground and positive on pwm1 with the red wire from the esc removed. However I would like to have the battery voltage and current monitored so any ideas on how I should do that would be most welcome.

Hi m8,
You have to apply Vbatt to your FC to get the Lipo pack condition. On all FCs the Vbatt input point is marked on the schematic circuit diagram. I always use an inline LC filter for this to ensure the board gets a clean supply. Using RAM jumpers also ensures your VTX and Camera shares the same clean main pack supply and ground and eliminates messy wiring.
Your onboard 5v reg will provide a clean supply for the FC, RX and GPS....and you can measure its voltage at the SBUS input rail. The last one I measured was only about 4.75v.
You will note at this point that there is no 5 volts present on the Servo rail output pins.
You can provide your (clean) 5v or higher servo supply on the FC rail..(Or make a separate one for +/- supply). If using a BEC, ensure it has a ferrite on the supply cable, a lot of ESC are missing these.

:vulture:

BigT · December 27, 2017, 05:26:03 PM

So let's see if have this now. On the top off the board I have bat+ and moto_vcc (see pic 1) so do I take lipo plus to bat and lipo neg to moto_vcc? Or in pic 2 which is bottom of the board I have vcc ram 5v. Do I take lipo +- to that? I don't want to power the board via the lipo as we know this will try to power the servo rail.

Of course the big issue is now I am going to power servos connected to pwm 5 and 6 unless I go back to my bus bar idea as others have done.

Sent from my iPad using Tapatalk