@rmackay9 EKF3 allocation failed with EK3_IMU_MASK=3.
Thanks for the report.
If you have time could you test if the same failure is seen with 4.1.5? This will more quickly help us determine if it is a new or existing limitation. There are certainly configurations where there simply isnāt enough memory available for all the enabled features.
If it is new could you provide a log file and/or parameter file so we can try and reproduce?
Hey @rmackay9
Tested on AC4.1.5. There was no issue with 15 reboots.
Getting MAVFTP is failing to initialize with AC4.2beta. Happens only when both CAN drivers are enabled by CAN_P1_DRIVER=1, CAN_P2_DRIVER=2. After reboot it shifts to EKF3 not enough memory or MAVFTP failing. Have attached the param file below. Is it because of moving baseline feature enabled?
AC4.2beta test.param (17.0 KB)
Free memory with CAN_P2_Driver=2

Free memory after CAN_P2_DRIVER=1 (Difference is now thereās no MAVFTP or EKF3 initialization problem.

Do you have any news about changing altitude during mission? I am quite puzzled as why we have tons of boutique things almost nobody uses, support 80+ different boards but we donāt have a basic feature as change altitude during a mission. We even support vtol landing on a boat, maybe altitude change in mission could be done with lua too?
Iām afraid thereās no update on providing the ability to add an altitude offset during a mission.
Different developers work on various things so adding support for new boards actually has no impact on this item. AP is fully open source, if thereās a dev who has the skills and wants to implement it we very much welcome their PR⦠until then, itās on the to-do list but weāre going to do it properly⦠no bodged solutions.
Ok great will wait and hope
Corrado
p.s. we have been using a ābodgedā solution for 3 years now and never a prob, maybe a bodged solution would have been better than nothing waiting for the āproperly doneā
curious enough, i was wandering about presence of such feature (change alt while auto) just recently, asking myself if it was there already and iāve could miss it among everything ardupilot offers. So itās not there, all right, got it
PS just to be clear, iām everyday grateful for the work all devs do!
I am not sure whether it is properly done or not but I did some implementation about it here, @rmackay9 FYI. @Corrado_Steri wait some time for it to become stable. Stay TUNE
d
Great to see something is moving, hopefully will be good enough to have it merged soon
Thanks
Did you apply an offset to the waypoints altitude?
Actually not to the waypoint but to the position controller, so you can even change the current altitude between waypoints based on TUNE settings and current TUNE channel value.
Great, we tried changing waypoint altitude because it was less dangerous to test but if waypoints are far away it takes ages to change. Working with position control is way better.
I saw that the TUNE channel read is rated at 3.3Hz so altitude changes will be really fast
Really looking forward to test it if itāll pass the merge
Yes, ready to test also! I see your PR is in units of cm. Thatās great after I learned my lesson with the WP speed Tune units
@rmackay9 Been watching all the dev conference, very nice job. Do you think the ability to change altitude during a mission can be sneaked in before the fix for the navigation near the magnetic poles??? Maybe even before they fix EKF in th proximity of north and South Pole, which, in my poor man opinion not many people will miss much
Looks like your PR didnāt have much luck yet.
Txs! I think 4.2.0 is almost fully baked so there wonāt be any further enhancements included. We are trying to do releases more regularly though so maybe it will make it for 4.3. We havenāt even got a PR for it yet though so weāre still a ways off from getting the enhancement request resolved. Iām sure it will be done before the magnetic poles issue is fixed though.
Dev conference is very interesting, it s a shame not many people take the time to watch it on the youtube channel. Maybe it should be advertised a bit more.
PR from @Mustafa_Gokce has been sitting there for 2 weeks, not much attention to it, seems.