@ionas86 wrote:
Hello everyone,
we are trying to perform an autonomous flight using a custom .waypoints file. It was working like a charm but when we altered the WPNAV_SPEED from 500cm/s to 300cm/s it completely freaked out. In detail it started making unexplainable moves around the first wp. It was not responding.
Has anyone encountered any similar problems?
Thank you advance for your time.
Best,
George
Posts: 1
Participants: 1
@Gramslam wrote:
Hello,
I'm trying to setup a Pixhawk 2.1 and can not get the motors to turn. they did before I upgraded to 3.5 using the motor test in Mission planner.
They all spin fine when tested using the RPM tester on my charger, but I Cant get them going with motor test or transmitter.Cheers,
Graham
Posts: 1
Participants: 1
@Pedals2Paddles wrote:
In the near future, I am going to make a few videos for the Solo wiki on the topics of calibration. I want to make sure I don't say anything dumb or repeat rumors. Can someone sanity check me here:
After doing the 6-axis accelerometer calibration, is rebooting required, advised, or totally unnecessary? My advice to people is to start on a known level surface that is stable like a table or the floor. Place it gently on each side per the prompts, count to 5 so it settles, then press the button. It doesn't need to be at perfect 90 degree angles. Being still is what's important. Am I correct about this?
After doing the onboard compass calibration, is rebooting required, advised, or totally unnecessary? My advice to people is to do this outdoors, away from structures, vehicles, power lines and transformers, reinforced concrete slabs, and other sources of magnetic interference. Face north, and rotate the vehicle around each of it's axes a few times. Remove any magnetic jewelry or accessories from your body before before doing this. Is this correct? Any other advise?
What is the function of the calibrate level button in Mission Planner? The wiki eludes to it just making the HUD be level. Is it changing something on the autopilot, or just in mission planner? Circumstances? My understanding is calibrating vehicle level is the first stage of the accel calibration. So this button does what?
Posts: 3
Participants: 2
@ccnavio wrote:
Hi everyone!
I'm working on a script in Mission Planner that will start a loaded waypoint file. This is supposed to run autonomously. So the script starts the ARM, throttles up, etc. (plus there's a function to get control back to the pilot if necessary). But what I really want is to have the scripts arm and go to a certain height and then switch over to the loaded waypoint file.
From what I understand, when you start running the script, it needs to talk to the ground station to work properly. It's not saved onto the PIXHAWK, right?
Is there a way to run the waypoint file (or some other loaded file from the PIXHAWK) using the script which wouldn't involve writing the waypoint file into the script?
Thank you!
Posts: 1
Participants: 1
@wicked1 wrote:
I just updated my copter from 3.4 to 3.5. I flew this morning w/ 3.4 and it was smooth. After putting 3.5 on it, my copter bounces up and down in alt_hold mode. Kind of like the PID's are wrong for alt_hold. But how do I correct that?
I can get a log if you need.. But I figured maybe it's something simple so I'll start w/ this...thanks!
Posts: 6
Participants: 3
@Hugo wrote:
Hi everyone,
I'm trying to bring up to instances of sim_vehicle.sh by doing, in a first terminal:
../Tools/autotest/sim_vehicle.sh -j 4 -f gazebo -I 0and in second terminal
../Tools/autotest/sim_vehicle.sh -j 4 -f gazebo -I 0however, after I run the second command the I get the message on the xTerm window saying:
failed to bind port 9002 to receive fdm from Gazebo
over and over againI attach a picture below
Is there something obvious I'm missing?!
Thank you very much,
Hugo
Posts: 14
Participants: 2
@Chris_Hardwick wrote:
Hi all,
I've been chasing a weird oscillation problem for close to a year now. It isn't visible by line-of-sight, but makes FPV really unpleasant. The oscillation is in the pitch-axis, and appears whenever there is horizontal motion.
I've exhausted the obvious (to me) possibilities, like motor/prop vibration, PID tuning, flight mode, airframe resonances, damped mass (gimbal) resonances, bad hardware, and video sync. The aircraft has evolved considerably since I first noticed the issue, but the problem persists. The only parts that I haven't changed are the FC vibration damping, and the motors/ESCs.
The vibration damping just occurred to me today, so that will be my next test.
So I'm now forced to consider some possibilities that I hadn't before, or didn't want to. I may have to replace the ESCs and motors. I really want to be able to use the set that I have. They are KDE products and set me back quite a bit. The possibility that I want to ask the forum about is whether or not there are any FC parameter changes that might help. I'm using a 3DR Pixhawk, Rev2.1, and Copter 3.4.6.
I've included a link to a goggle DVR recording and a recent dataflash log.
I would be most grateful if there is someone out there who can look over the log for anything unusual. I've spent some time checking it out, but I'm not expert enough to spot a problem. One thing that you might notice is that my STAB gains are pretty high. I don't know why it tunes this way, but I do know that I can reduce the STAB_P gain until the aircraft is extremely mushy and the problem persists.
The aircraft is a TBS Disco Pro, with 5200mAh/4s, KDE 20A ESCs, KDE XF2315-885kV motors, minimOSD, ImmersionRC 600mW/5.8GHz VTX, DragonLink Micro RX, 3DR GPS/Compass, my own barometer mod (tried that too), Runcam Swift FPV cam.
Posts: 4
Participants: 2
@evanp18 wrote:
Hello all,
This is a repost from a different topic. Several weeks ago, while flying my Skywalker X8 Quadplane, I had a very bad wreck. This happened while attempting to land in QLoiter mode. As I was decreasing throttle, the motors cut out at approximately 50%. There were several things that I thought may have been the issue, including my parameters. I have attached my parameters below, and was wondering if anyone would be able to help me checking them? Any help at all would be greatly appreciated!
Configurations.param (12.7 KB)
Posts: 1
Participants: 1
@JohnWBlackwood wrote:
How do you mute the sound from the rpi3 connected to a navio2?
Posts: 2
Participants: 2
@Anthony_Short wrote:
I have a quadcopter with a 3DR Pixhawk 1 and dys XS20A ESCs. It was running well on 3.4.6, with the ESC protocol set to Oneshot125. Prior to upgrading to 3.5 rc8 I ran through all the calibrations including ESC calibration which completed successfully. I did the upgrade to 3.5 rc8 and when I tried to run ESC calibration on 3.5 it failed. I click the button in MP to start, then power cycle the quad. The Pixhawk just sits there with rapidly flashing red/blue/green. I tried the procedure about ten times and the same thing happened each time. I then changed the ESC protocol from Oneshot125 to Normal, and ESC calibration now works fine. I also tried Oneshot, that doesn't calibrate either.
Posts: 2
Participants: 2
@HumamHelfawiOptecks wrote:
Hi,
I am using "3.6.0-FIRMWARE_VERSION_TYPE_DEV" on Intel RTF drone. Both loiter and altitude mode does not work. When I set one of them, the drone goes down directly and crashes on the land. BTW, the simulator has the same behaviour. I have also tried the Mavproxy command and I got the same result.
Thanks
Posts: 1
Participants: 1
@nomisreltub wrote:
Finally got amp 2.8 set up and flying well. I have used this x8r in same plane for months now with no problem. Had several flights with apm connected just not tuned right. Was having a great flight, RTL worked beautifully. (the main reason i wanted pilot) then right above my head my radio loses signal. Gone, nothing. Plane went into RTL and started circling above (perfect right?) but my taranis radio had zero connection. It didn't give the "signal strength warning" it just cut off. When i realised the plane was safely circling i tried switching radio off and on again, twice but nothing. Panic was setting in. My mac was still connect with apm planner and in my panic i could not think what to do? (any tips here would be appreciated also) I got the idea to disarm plane and it then came gently down into the soft branches of a 30ft tee tree. Little damage thankfully. Once retrieved i plugged batter back in and it bound with taranis as per usual. There were no lose connections and antenna were exactly where they had been mounted. So my questions are how do i know if this x8r is to blame? Would you use it again? Could it be the taranis? Could the plane have been landed using Planner? Has anyone else had a similar failure? Thanks in advance.
Posts: 5
Participants: 4
@OlivierB wrote:
Congratulations to Ardupilot Developer Jaime Machuca and Nick Nunno of Aion Robotics for winning the "Best Contribution of the Month" award for May 2017, for their work towards and including Ardupilot's successful demonstration at the MakerFaire Bay Area in May.
Invited by Intel and sponsored by both Intel and The Cube, the project for MakerFaire was started by Ardupilot hardware lead and Cube designer Philip Rowse. Philip unfortunately faced unexpected hard traveling constraints less than a month before the event, yet Jaime volunteered to step in and manage the project both remotely and on-site, prior to and during the event.
The project idea consisted of having a copter follow a rover with both vehicles running Ardupilot on a Cube aka Pixhawk 2, while showcasing Intel Joule or Edison. The copter would fly with an Intel Edison onboard, a camera, GPS precision RTK with Here+, IR-lock for precision target following, Poxyx UWB for geofencing, and a power tether for continuous flying. If time allowed obstacle avoidance and SLAM would be performed on the rover with a Joule and Intel RealSense ZR300 camera.
As is typical with complex projects of this nature, time (surprise!) became scarce quickly and deadlines approached faster than anticipated. With just a month to go, a team was formed together by Jaime and Philip, that included Nick who provided his freshly designed high end rover, Jonathan Challinger who started working on integrating a copter provided by EnRoute, Dan Pollock hard at work on Ardupilot SLAM solutions and ROS based Edison and Joule integration, and Mission Planner's Michael Oborne for on site help an support.
It's worth noting that Nick's rover is no average one, but instead a high power and industrial grade ground vehicle. Weighing in at over 30 pounds, two feet long and one and a half foot wide, the Aion Robotics rover also uses industrial grade servo motors for propulsion, with variable duty cycle. Given this, Ardupilot developer and Rover specialist Pierre Kancir volunteered and provided crucial on-going coding support, as Tridge also stepped in to add custom and compatible support for the previously unsupported motors and its control signaling requirements.
Randy McKay as Arducopter lead also stepped in and provided support on the copter side, along with Ardupilot developers Peter Barker and Grant Morphett. Needless to say the project saw many ups and downs, yet thanks to Jaime, Nick and the coordinated teamwork of all participants ultimately an "Up!", with great execution at the MakerFaire venue.
Challenges the team overcame included shipping delays, (parts were shipped from all over the world including Japan and Australia), unavailability of the tethered leash, and the typical yet nerve wracking technical trials and tribulations always present when building, integrating and testing a new and complex robotics system under harsh time constraints. Not to mention (as Jaime made his way from Aion Robotics in Colorado to Maker faire in California, after having visited and worked with Dan in Texas for the vision part of the project), a rare and unexpected May snow storm in Colorado!
Highlights of overcoming the many challenges faced included Jonathan and Jeff Wurzbach designing and building a working powered tether in what appeared to be the blink of an eye, and Tridge remotely debugging and tuning the rover from half way across the world and a 16 hour time zone difference.
Regrettably Intel has just recently announced the end of life of the Joule and Edison. The good news however is that the cube was designed with modularity as a starting point, and as such works equally well with other companion computers like the Rasberry Pi, the powerful NVidia TX1 and TX2, and many other computers. So work done for this project is not lost at all, and instead will continue to benefit this community.
If you missed them, Jaime made several videos documenting the "Road" to MakeFaire, well worth watching! They are available on his youtube channel, and were also blogged about on this forum: Episode 1, Episode 2, Episode 3&4, and Episode 5.
Congratulations Jaime, Nick and the team!
The prize this month was $200 for the top contributor. Thanks to those who donated to ArduPilot, including our Corporate Partners. If you are a company and wish to donate a prize for an upcoming month, please email the partners email list (partners@ardupilot.org).
![]()
Posts: 4
Participants: 4
@TTGold wrote:
I have a setup that uses a PixRacer and a HERE GPS module with internal LEDs and Compasses. I have been flying successfully for a while now without any major issues except I would get a random "inconsistent compass" error upon boot. I would reboot the PixRacer and then it would boot successfully and pass. It usually would only happen on the first boot and then no trouble after that. Over the last couple of days I am now finding that the inconsistent compass comes in on every cold boot and I can not get it to clear unless I re-calibrate the compasses. Once I do this it will pass the calibration and then I can fly using Loiter and all GPS based flight modes without issue. I can even fly a couple of batteries and everything works great until I put it away and come back the next day and have to re-calibrate again because of the pre arm inconsistent compasses. I don't know if it is because of the weather getting warmer affecting something or what how to answer this issue. Any help or advice would be greatly appreciated.
Posts: 3
Participants: 2
@Kikirikiki90 wrote:
I´m using an APM 2.8 and the buzzer starts beeping too early to warn me of too low voltaje in the batterie. It starts at 11,5 V, is there any way to change this value? Someone with a similar problem?
Thanks!!
Posts: 2
Participants: 2
@Georacer wrote:
Hello everyone,
I was wondering whether it is possible to trigger a failsafe from the 2nd battery voltage measurement.
Is this possible? If yes, how can this be done?Thanks!
Posts: 1
Participants: 1
@Sunit_Pal wrote:
I was flying my heli successfully using 3.4.6. Then I upgraded it to 3.5-rc8. Now I get the message “PreArm: Motor Interlock Enabled”. I am unable to find out the reason for this. This happens only when the RSC_MODE is set to 2. When I set RSC_MODE to 1, then there is no error. Is anybody else having this issue? I searched this forum but no one seems to have reported this issue. Some one reported a similar issue ( http://discuss.ardupilot.org/t/3-5-0-rc2-on-heli-with-pixracer-cant-clear-motor-interlock-solved/15734) but that seems to be dues to missing CH8 in the transmitter.
Posts: 4
Participants: 4
@ruben1 wrote:
Hello,
Is it possible to disable the buttons 'Initial Setup' and 'Configuration/Tuning' and make sure that user cannot activate these buttons easily? I'm working on a project in which the Mission Planer is used by many different people and I want that the setup values can't be changed accidentally by someone who don't know what he is doing.
Posts: 2
Participants: 2
@Eric_Wikramanayake wrote:
This is the altitude drift from a stationary PH2.1.
What is the sensor value that VFR_HUD is showing for altitude (Baro, GPS, Mix/blended ?)
thanks.
Posts: 1
Participants: 1
@aamadeuss wrote:
Hey guys,
im thinking of converting a small electric car ( around 500kg) with ardurover.
how can i handle the problem with compass calibration?
is there a workaround, or tips?Thanks
Posts: 1
Participants: 1
