@bnsgeyer, to fix the compile problem, i think you just need to download and install the latest pixhawk-toolchain. It’s linked from this page. http://ardupilot.org/dev/docs/building-px4-with-make.html. Hope that helps. If it doesn’t, maybe try uninstalling the currently installed pixhawk-toolchain and then re-install this latest one. That extra step shouldn’t be required but just in case.
@Andre-K,
Thanks for the reporting on the missing builds for Y6, Hexa. It was a mistake in our build scripts introduced recently. Tridge has fixed and hopefully the other vehicle builds will arrive shortly, thanks!
@ReadyEdi,
Looks like this log is from AC3.3.3 which is very well tested and really shouldn’t be reported in this AC3.4.4 release section.
It looks like some of the logging information is turned off (LOG_BITMASK) so it’s a bit hard to tell but I think the issue is the buzzer. I’d recommend moving it away from the flight controller or remove it completely.
By the way, if you choose to upgrade to AC3.4.4, you can disable the buzzer by setting the NTF_BUZZ_ENABLE parameter to zero.
1 Like
“Fitness” is in what place? In Mission Planner.
Thank you
@rmackay9 I am running toolchain v14. Would installing the latest toolchain affect being able to compile AC 3.3.3? Thanks for the help!
@Terry,
I think I pointed you to the correct wiki page in the other posting (Live calabration fail).
In any case, please see the image in the “Onboard Calibration” section of this wiki page. http://ardupilot.org/copter/docs/common-compass-calibration-in-mission-planner.html
@bnsgeyer, I think it should be safe to upgrade to the newer pixhawk-toolchain and still be able to compile the AC3.3 branch. I haven’t specifically tested it but it should be fine.
Many thanks to problem solved!
Hexa remains at 3.4.3, but what time will it be released in 3.4.4?
@rmackay9
What are the sounds now after a successful flashing?
Is it still the beginnings of Close Encounters or is it the basic boot sound?
That is what I got after flashing 3.4.4 - basic boot tones.
1 Like
I checked it now and it is released.
Thank you.
Randy,
The toolchain upgrade worked and was backwards compatible with AC 3.3.3. Thanks for the help!
@pmshop,
“Close Encounters” plays when it upgrade the I/O board’s firmware (the Pixhawk & Pixhawk2 actually have 2 CPUs on the flight controller). We didn’t need to make any changes to the I/O board’s firmware with this release so if you’re upgrading from AC3.4.3 I’d expect the regular boot sounds (which I guess is what you heard).
@hirochi, @bnsgeyer,
Great news on both fronts!
test motor sounds with different mot_pwm_type modes.
The best sounds in normal and oneshot modes. Oneshot125 very noisy.
FW 3.4.4 FC F4BY
50%throttle from motor test tab in Mission planner
I don’t know if that’s normal or not, but that board isn’t supported yet.
Why the copter v3.4 otca under pixhawk aux1 - aux6 no PWM, after the safety switch to unlock
It appears changes in 3.4.4 render the camera feedback function (CAM_FEEDBACK_POL) unusable, switching back to 3.3.3 fixed the issue for me.
@a123456, in copter, there should be output on the pwm channels even before arming if they’ve been setup for controlling a gimbal, landing-gear, etc. It’s configurable however using the BRD_SAFETY_MASK parameter. The easiest way to change this parameter is to use the mission planner’s Advanced Params screen.
Been trying to narrow down what might be causing error message “gyros still settling” during prearm check. I also tried to disable the prearm check but still got the message. Could I have a parameter set wrong causing this? I did try swapping out gps/compass but have not yet tried swapping Pixhawk (not P2).
For what it is worth, I reloaded default parameters and things seemed to settle down. Ran into some throttle issues but that is more straight forward to deal with (at least it seems so). Is arming now.