↧
My mission with autoland
↧
Omnibus F4 pro GPS
@ardisd wrote:
On the Omnibus F4 pro running Arducopter 3.6 GPS 1 was assigned to Serial 3 in version 4 there is no Serial 3 just 0,1 and 2.
I have configured serial 2 to use GPS but it still not working. What are the new Serial Port mapping for the Omnibus F4 pro
David Ardis
Posts: 2
Participants: 2
↧
↧
RPM sensor not work because less than 5V
@jinchengde wrote:
(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)
Posts: 1
Participants: 1
↧
Rpm sensor not work because signal voltage less than 5v
@jinchengde wrote:
hi,
I used futaba rpm sensor and connect to AUX 5 to measure the rpm, but no information to get.
I connect my aileron output directly to AUX 5, it works and get 7500 rpm
then I check the signal wire of rpm sensor, when the magnetic and hall sensor matched, voltage output from signal wire is only 4V(less then 5v), and after then magnetic go away, it output only 0.2v
So I guess is that the reason why I can’t get the rpm info. How can I solve it?
Posts: 1
Participants: 1
↧
Pixhawk Crash magically
@Abdul_Qadeer wrote:
Anyone please help … i don’t know what is happening …here is the little description .
i use Mission Planner to control my quadcopter … i first created some mission ,upload it to pixhawk . then arm the copter and takeoff in guided mode . but when copter gain some altitude to about 5-6 meter approx . it suddenly desends rapidly and crash…
below is the bin file…00000044.BIN (368 KB)
Posts: 2
Participants: 2
↧
↧
Configure Airspeed Sensor on Kakute F7
@adarby wrote:
Hi
I am trying to configure an analogue airspeed sensor and a HolyBro Kakute F7 AIO running AurduPlane 4. When I go to Mission planner it gives me a choice of inputs but they are mainly referenced as APM2 pins.
Which pin/input should I use in Mission Planner and which pin should I connect to on the Kakute F7?
If this is not going to work please suggest other option. I have the compass and GPS working already with the compass on the I2C bus.
Thanks for you help.
Adam
Posts: 1
Participants: 1
↧
AutoTune on Large 1200mm Octo And unstable YAW
@smartdave wrote:
I have built a Large Octo and the Yaw is quite unstable. At one point the copter was slowly spinning on its own. I have not completed the 3 axis Auto tune yet.
I want to get the Yaw stable before I try the other two Axis.
The autotune on Yaw Only ran for about 18 minutes before I had to land because of batteries.
Can someone take a look at this logs and give me some pointers?
Thanks
Posts: 1
Participants: 1
↧
Logging failed on Kakute F7 mini
@Hugues wrote:
Hi,
I installed Release 4 RC2 on the Kakute F7 mini board. The ship flies nicely but logging is not working.*I I get these errors on the HUD:
Then trying to download logs , the following error is displayed:
The log parameters are as follows:
Any idea what I’m doing wrong or is this an issue with the F7 mini (Kakute) ?
Posts: 2
Participants: 2
↧
Does the customer parameters will change to default after upload firmware?
@xingxing wrote:
Hi,my F4050 WING is running arduplane3.9.9,i try to upload to firmware4.0 but not sure if it will change some parameters to default(such as PID,servo output etc),I also back up my parameters,but it seems don’t chang back afer I load the back up parameters file.
Posts: 1
Participants: 1
↧
↧
Pixhawk PX4 and the video transmitter
@rjriggins111 wrote:
I’m wiring up an older Pixhawk FC and was wondering if there is a built in display and how would I wire it up to my video transmitter?
Posts: 1
Participants: 1
↧
Cannot connect to CubeOrange with MissionPlanner
@rmackay9 wrote:
This is a discussion carried over from the Copter-4.0.0-rc2 testing thread in which @Jernej_Fajdiga could not connect to the autopilot (a Hex CubeOrange) using Mission Planner.
Question: when I successfully installed copter 4.00-rc4 on the cube. the cube no longer starts running. Can you help me?
Possible causes/solutions:
- The autopilot is starting up but the LEDs are not coming on because the GPS/compass unit is connected through CAN so the CAN_P1_DRIVER and NTF_LED_TYPES params must be set. We can conclude this is not the issue because you cannot connect with the MP.
- Writing the new I/O firmware (and/or bootloader) took 30sec or so but the autopilot was rebooted before this could be completed (waiting longer should resolve this problem). This is not the problem because I assume you’ve left it powered up for more than 30seconds after booting.
- Something wrong with our bootloader or a sensor is broken.
- If there is not enough power provided especially if using a USB cable. We can confirm this is the cause by disconnecting all accessories (RC receiver, telemetry radio, anything else) and then try powering it up again. This is not the problem because you’ve disconnected all accessories
- The wrong firmware has been loaded to the board somehow
- Bad USB cable
- Missing drivers on the windows PC
I’ve just received a report that there’s an issue with our CubeOrange firmware’s bootloader so I’ll respond back later.
Posts: 11
Participants: 2
↧
Overlapping Overlay's
@rjriggins111 wrote:
I’m running into a problem where the lettering on the screen and the buttons are overlapping and un-readable. Has anyone run into this or run across a fix. My new Pixhawk is proving to be a pain-in-the-A–S. I’ve been trying all day just to get the motors to turn over with no success. I did get some of the radio channels straightened out but some of the others quit working alll together. Not quite as simple as the Vector I’m used to.
Rick
Posts: 1
Participants: 1
↧
Is mission planner available for android
@sumitkrsharma01 wrote:
Hi
I just need to know if mission planner available for android?
if not what needs to be done to port it to android platform. ?
is there any chance that it could appear in android in future ?
thanks
Posts: 1
Participants: 1
↧
↧
Dual motor tailsitter
@vinod_nayak wrote:
Hi team,
Its been a long time im working on cube. I have successfully made quad plane with cube and few other projects and they were grand success. Now i am working on Dual motor tail sitters. I have already made 3 prototype models and they were running on arduplane 4.0.0 firmware.its been few weeks since i m testing and tuning up the pid’s few things i have still in confusion and strange things happens with my setup.
Confusion things:
- what mode should i let the aircraft turn on and let it initialise, is it fw mode or q hover mode?
- in which orientation should i do accel and level calibrations.
- if i place my tailsitter on its tail and takeoff in q hover mode why does it will drift in terms of yaw let say if i place tailsitter top exposing north and take off it wont hold north in terms of yaw.
strange things observed:
- in q hover mode aircraft is fine and flying good, but when i take into fbwa mode my pitch oscillates too much as both the elevons servos are oscillating too much which resulted in a crash. I have tried tuning fw pid gains and found to be good for 2 flights later on 3&4 flight they started oscillations and crashed(3&4) Test was done in little wind where in 1&2 test was done in no wind.
- auto mission takeoff in vtol mode transition to fw mode and do mission in fw mode while RTL and vtol land it is triggering from fw mode to vtol mode but not coming to land at home point.
Please help me with this problem.
Thanks indeed.
Vinod nayak
UAV development engineer India.
Posts: 1
Participants: 1
↧
Warning: Do not update bootloader if using Copter-4.0.0-rc1 to -rc4 on high powered H7 boards
@rmackay9 wrote:
Today we discovered a “byte alignment” issue with ArduPilot bootloader that is included with Copter-4.0.0-rc1 to -rc4 that can affect autopilots that use the STM H7 CPU.
Please do not attempt to upload the bootloader with Copter-4.0.0-rc1 to -rc4 on any boards with an STM H7 CPU (these are high powered boards like the CubeOrange, Durandal, CUAV V5 Nano) or you risk “bricking” your board. A fix will be released with Copter-4.0.0-rc5 tomorrow (Tue Dec 24th).
This issue does not affect the older Pixhawk boards (CubeBlack, mRo Pixhawk etc) nor any other board that ran Copter-3.6.
This issue will not cause your vehicle to crash. The worst case is it will cause H7 boards to fail to startup and fail to accept new firmwares (i.e they become bricked). Some boards (CUAV V5 Nano, Durandal) include “DFU” pins which can get them out of this state.
To provide some background, a “bootloader” is a small piece of software on the autopilot that runs for a few seconds immediately after the autopilot is powered up. It’s purpose in life is to make updating software to the autopilot easier. The reason that the ground station asks you to plug/unplug the board before a software update is so it can communicate with the bootloader.
Most flight controllers come with a bootloader already installed but ArduPilot also comes with bootloader. This new bootloader is only loaded if you connect to the flight controller with a ground station (like Mission Planner) and then specifically tell it to upgrade the bootloader. This button can be found on MP’s Install Firmware screen or the Ctrl-F screen but please don’t push it!
Posts: 1
Participants: 1
↧
Optical Flow in Loiter mode
@danielh wrote:
Is it possible to fly in LOITER with optical flow (As opposed to FLOWHOLD)?
I wish to control the velocity as opposed to the lean angles.The documentation of flow hold states that the height and velocity are estimated, even with no lidar\sonar.
Does Loiter require a distance sensor?Thank you!
Posts: 1
Participants: 1
↧
Copter-4.0.0-rc5 available for beta testing!
@rmackay9 wrote:
Copter-4.0.0-rc5 has been released for beta testing and should be available for download from the ground stations within the next few hours. If you’d like to help us with beta testing please use MP’s or QGC’s “Beta Firmwares” link to download this latest version or alternatively the binary can be downloaded directly from firmware.ardupilot.org
This release candidate’s changes are in the ReleaseNotes and also copied below.
- RM3100 compass enabled on all boards
- GCS failsafe disabled by default (see FS_GCS_ENABLE parameter)
- Bug Fixes
a) Bootloader fix for H7 boards (could brick CubeOrange, CUAV V5 Nano, etc)
b) OmnibusF4pro GPS fix
c) MatekF405-Wing missing serial ports restored
d) MatekF765-Wing RTSCTS parameter defaults set correctly
e) CUAV V5 Nano battery monitor param defaults improvedThese changes are all directly related to reports we’ve received as part of this beta testing so we greatly appreciate your feedback!
If all goes well this could be the final release candidate before Copter-4.0.0 becomes the official/default version but in any case, please help us to uncover issues by giving it a try and reporting back.
thanks very much!
Posts: 2
Participants: 1
↧
↧
Gyros Inconsistent after Boot
@alberto.munizaga wrote:
Hi
I have BlackCube, and on one of my drones, after some minutes started, the “Gyros Inconsistent” error show up. If I takeoff at the moment I have 3Dfix, no problem, but If I wait more the Gyros problem appear.
If I reboot the pix I can takeoff again, but the same, some minutes without takeoff and the Gyros Inconsistent show up again.
If I fly and land, the same, some seconds after landing the Gyros Inconsistent show up again.
I have calibrated de Accelerometers so many times, even with a electronic level, and the same.
I have been reading here to some people had the same issue, and I saw maybe could be because the temperature of the IMUS at calibration is too cold?
I will appreciate your help!
Thanks!
Posts: 1
Participants: 1
↧
BlackCube wont boot after poweron
@alberto.munizaga wrote:
Hi
Some times after connect the battery, the Cube wont boot, the Motors ESC keep beeping and safety switch doesnt do anything, and I have to disconnect and connect again the battery to boot again.
How can I identitfy why this happend?
Thanks!
Posts: 1
Participants: 1
↧
Not holding heading during flare? .bin logfiles provided
@Christopher_Milner wrote:
Arduplane 4.0, Pixhawk4, Rudder-only airplane.
Any thoughts/diagnosis/suggested tests would be much appreciated!
Logfile, bin format, here:
Stall speed in this configuration about 7 m/s (see below), so I set up TECS_LAND_ARSPD to 10 m/s.
Approach is pretty stabilized landing stage 1. Airspeed and heading look good.See 15:10:12.5. However when landing stage changes to 3 (which I think is the flare stage), throttle goes to 0 (which is correct), and rudder output suddenly goes to 0 (which doesn’t seem correct), and the plane veers off to the left, then veers to the right. I suspect something about a rudder-only control loop failing when in the flare. Why doesn’t the autopilot keep heading in the flare like it does in the approach? I think the rudder authority in the flare, with idle throttle, is sufficient (see below where I do manual landings in the same configuration and can hold heading just fine all the way to the ground).
Another attempt 15:06:41 ended in the plane rolling too far to the right at 15:06:48 (and I switch to manual to recover)
Any thoughts/diagnosis/suggested tests would be much appreciated!
Another logfile, here, https://drive.google.com/open?id=1JzCxk7imhGGGAokGrXqS7exWbD8_a4CC
has power-off stalls (to show stall speed) at
14:23:50 stalls at about 7 m/s
14:24:40 same, about 7 m/s
14:25:03 same, about 7 m/shas throttle-off manual mode landings, 7.5 m/s (to show rudder authority at idle throttle and this low speed), at
14:25:57.5 - 14:26:02
14:27:59 - 14:28:05
Posts: 1
Participants: 1
↧