Hi, i cant make it flying, no i/o thread heartbeat(),it works fine with 3.5.7, did anyone had/solved this problem?
Yes, and I use it that way on both Helis and it works only with Nuttx on both. I fly the newest 3.6.rc11 and I am happy so far. New Loiter is not that solid hovering anymore what I am used to with the old one.
I also changed to the Chibios even with my Quad copter. All good but my Lidar lite - PMW do not work in Chibios.
Hello, I had also this problem but only with my pixhack v3 and was able to solve the issue with using a different sd card (SanDisk ultra class 10) . With pixhawk 2.1 never saw this warning massage.
Randy,
Thank you for planning to incorporate.
I am concerned about the following case:
- Suppose drone is on the ground, and EKF origin altitude is 21.92m.
- On arming, HOME altitude is automatically set to 21.00m, not 21.92m due to this bug.
- The relative altitude on the ground will be calculated as 0.92m, so the takeoff altitude is 0.92m lower than expected, and following WPs will be handled similary.
1 Like
Thank you for your reply , i tried at first with a Kingston class 10, same problem , then i put the Sandisk, i had in my Mobius, and its working…very sensitive!
1 Like
Fred,
I’ve investigated the LidarLite PWM driver not working under ChibiOS. I’m afraid to say that this is a known missing feature of ChibiOS. It’s on the to-do list to add support for RangeFinders that output PWM but it’s unlikely to be done for the 3.6.0 release. It’s possible we will resolve this in a later point release (i.e. 3.6.1, 3.6.2, etc). Until then I’m afraid the NuttX build is the one to stick with if the LidarLite PWM range finder is a required.
1 Like
Sergey,
Thanks for the report. The Pixracer safety button issue is also on the list to investigate.
Sergey,
I’ve tested the safety switch on a Pixracer with ChibiOS and I’m not seeing any real issues. Perhaps I don’t know exactly what to look for. Can you be more specific about the issue that you’re seeing? What are the symptoms? If you have a dataflash log that might also be helpful.
@rmackay9 sure I will retest today evening.
Maybe it is related to the exact BRD_SAFETY_OPTION value. For me it is configured in a way to require a button press to arm; Then any further press cannot disarm. I don’t recall the exact value but I will report.
1 Like
Thank you for the reply. I will wait until it is fixed in Chibios.
Hey all,im flying since first beta and i can say its awsome. I really like new loiter… Im testing it on my F450 with pixhawk fmu4. The only issue i saw in this beta’s was when i first time take off and back the throttle to mid the quad continiue to raise alt to about 4-5 meter then stop. This was fixed i think in rc9 and now is fine. Also i see as some other people here that new loiter is not lock in position in hover like PosHold. I tryed to reduce LOIT_ACC_MAX to 150 and i got less wobling around. Keep this good work up!
1 Like
Randy,
On safety button doesn’t work on Pixracer. Still repro for me.
I’ve done a further testing:
With BRD_SAFETY_OPTION = 3 - works well on both ChibiOs and NuttX
With BRD_SAFETY_OPTION = 1 - works well on NuttX, does not work on ChibiOs.
Do you want me to create an issue? Also there are bin logs exists but I believe there nothing interesting except details I’ve provided above.
Thanks!
Tested today Rc-11 and it seems fine in general flight and GPS loiter mode is cool. My small quad has some jerks but smooths out about 50% in flight. I noticed smart return to land was missing error checking told me about the missing flight mode so that’s nice. some pre flight logging messages. Running Pixhawk.
" https://www.dropbox.com/s/9jfi19lmnsrvb36/IMG_1929.MOV?dl=0 "
" https://www.dropbox.com/s/82g3f9aksptfn4d/IMG_1927.MOV?dl=0 "
1 Like
Sergey,
Great, thanks for the detailed info. We’ve reproduced and fixed the issue and this will go out with -rc12 in the next day or two. txs!
2 Likes
Tested 3.6 RC 11 nutx on Pixfalcon, (fmuv2), no issues.
Upgrade from 3.5.7 was seamless, all parameters carried over to the newversion.
Flight was all OK, we’re just toying with the new loiter settings.
The OLED display shows a couple more messages than before.
Battery failsafe worked as planned.
SmartRTL worked as planned
2 Likes
I think, there might be an issue with DShot:
On my quadcopter, I am using a servo for camera-tilt on PWM6.
It works fine as long as I keep MOT_PWM_TYPE to 0.
If I set this parameter to 4, the four motors run on DShot150, but the servo doesn’t work any more.
I checked with a logic analyzer and found out, the PWM pin of the servo runs DShot as well.
It seems like MOT_PWM_TYPE does not only affect the channels which are used for motors but all PWM channels.
Not sure if I am doing something wrong with configuration or it’s a bug. Any advice is highly appreciated.
1 Like
Solved/ flight mode issue that I reported was that I was not using MP beta…
What flight controller are you using? Can you please provide a full set of parameters, or a log file.
I took the risk to fly a comprehensive Mission of 10 minutes with my TR600 Heli today.
The FC is the Pixhawk 2.1, Arducopter 3.6.0 rc11 chibios, (No Lidar Lite) HERE normal GPS and Sony X3000 camera.
ROI with different altitude up to 75m high. Flying sideways, was very smooth. After a big lop with different altitude a full RTL with Auto land. One of my best Missions so far. 3.6.rc11 worked great.
Thank you all.
3 Likes