Im having some troubles setting the above-mentioned bit mask how I (think) I want it to be.
First, could someone please briefly outline "inhibit IMU_bias" for me?
Second, I would like to select "2", "5" and "7" (imu_bias, drag-fusion and gps-yaw-fusion) but my selection doesn't stick and it always resets to bit-value "7", meaning other options are selected too, again.
Also, do we set "0" (use GPS) additionally or would that be not needed when point number 7 (gps-yaw-fusion) is active?
What would be the necessary bit-value to enter into the mask for reaching my preferred selection?
@m4v3r hey there,
I'm really stuck herr still and can now confirm that this is a VOXL problem since I've tried several different FC's now an with each of them the settings for any bitmask are sticking, no problems... except for the VOXL.
Bitmask will always switch to "7" with all options except first and last ticked.
Won't save any kind if selection at all.
I noticed the same on a couple of other bitmask selections as well, for instance declination handling and some others.
We kinda need this working correctly and considering the price of a VOXL-Flight you guys might at least give us half-a-hand here?
Chad Sweet last edited by
Flight Core is where the EKF2_AID_MASK is being set. Flight Core runs stock PX4, so EKF2_AID_MASK should not behave differently than other flight controllers using stock PX4. Which version of software are you running on Flight Core?
You can find details on Flight Core firmware here: https://docs.modalai.com/flight-core-firmware/ There are a few custom builds for flying without magnetometer indoors.
We have reference EKF settings here: https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/helpers
If you are trying to fly with VIO, you can look at the instructions here: https://docs.modalai.com/flying-with-vio/
We do not have any experience with "Inhibit IMU Bias", the PX4 forum might be a good place for that.
In general, it might help to share what you are trying to achieve.
Also, can you please try saving your parameters twice? Sometimes QGC gets messed up if not all of the parameters are there the first time.
m4v3r last edited by m4v3r
@Chad-Sweet Hi Chad.
First sorry but this issue is just making me so furious since I've tried so much already (different Firmwares, entering manually etc.) and it can be so infuriating if that one little thing just won't work, you know...
Anyways, Flight Core software is PX4 1.12.1 right now but I've also tried the custom ModalAI firmware (1.11.1-0.0.5) and others to no avail.
Using .params files is of no use since the problem is with saving the values not with entering them.
As far as I understand it the multirotor-drag thing would use ballistics to calculate like the wind so I regard it as something I would want for a MC.
No vision whatsoever for navigation so I would like to turn these off (should save CPU cycles if not checking, right?).
Also my Logs are filled with
"Estimator Source (8) not supported"
errors and it would be nice to clear those up.
Don't get me wrong please, the VOXL-flight is a great piece of hardware and I love working with it, it's just there's a couple smaller issues here and there and sometimes your documentation is dodgy in the important places but of course I realize you guys are also humans likely trying your best and can't be omniscient etc. so yeah,
I hope we'll get this resolved together.
I'm in "weekend" flight-mode for now so I'll report back on saving twice next week.
m4v3r last edited by m4v3r
hey, I know it's Tuesday ;D but saving twice did nothing and
the only two bitmask-values I can reliably reproduce are 1 and 7 (meaning the Parameter is set to "1" or "7" with a corresponding selection), neither of them are of much help.
The thing is, the quad is flying fine autonomously but I can't really have the unreliability of a somewhat important parameter chosing its own setting, you know...
So it would be nice if we'd be able to find some way to set them reliably to what one actually chooses.
Only thing I can think of the top of my head is that we're using no PX4-flow or any kind of optical sensors whatsoever.
For reference this constant string of errors is a consequence of this parameter not being set right:
Just an aside I got to fly your guys' new firmware today and can confirm it's doing good so far.
I still had to include my own fix to make J1009 (TELEM/SERIAL4) work for now but that's already been merged into master so should be included with whatever next version you guys put out as well.