Quantcast
Channel: ArduPilot Discourse - Latest posts
Viewing all 251372 articles
Browse latest View live

Very weird problem acceleration

$
0
0

The system should have enough headroom for full throttle.
Full transmitter stick up does not equal full output to the motors. And you can tune this behavior. I am not somewhere I can look things up at the moment, but I believe it is the atc_mix_man parameter. (but I could be completely wrong about that… sorry) And there’s another similar parameter having to do w/ Yaw, and I don’t remember the name of it at all… But look through the full parameter list online and you’ll find which to adjust.

I fly full throttle flights every day :).

I do have an issue w/ some of my copters leaning. If I fly at high speeds, the vibrations cause the system to lean more and more to one side (always seems to be the left for me, on several copters). I can land, re-level the copter and it’s OK for a while. But then after I reboot, it will be pulling to the right until I do a high speed run to cause the problem I am already correcting, and then it is level again. On these copters w/out ideal vibrations, I basically make a compromise so it leans a little to the right when I take off, and if I do a lot of full throttle runs, it’s leaning a bit to the left by the time I land.

Not sure if that matches the symptoms you’re seeing… My vibrations are quite low in the logs, but this is on tiny copters, and the FC reacts differently to the frequency of vibrations on the little microcopters I’ve been using lately.


Pixhawk with jumper R8 and FrSky telemetry passthroug not work

$
0
0

Thanks for your answer,
I will try to alternate the tx / rx lines.

I don’t know how to move the question to another topic. If any admin can move it, Thanks

Connection of two LiPos

$
0
0

yeah you’re overthinking it a bit. Just make sure theyre both the same i.e: same cell count(1s,2s,3s, etc) or mah capacity.

Connection of two LiPos

Pixhawk 4 Mini with the Hereflow

$
0
0

I’m trying to get the HereFlow working with the Pixhawk 4 Mini. I can get it working on a regular Pixhawk 4 using CAN1, and changing the parameters as mentioned in the documentation for the HereFlow. However, whenever I change the parameters on the Pixhawk 4 mini, it does not work at all. Has anyone been able to get this working on the Pixhawk 4 Mini? If so, what parameters were used, and how are they different from those used in a Pixhawk 4. I followed the instructions from the link below to get it working on the PIxhawk 4.

Heli Setup page and Helicopter 4.0.0 fw

Pixhawk with jumper R8 and FrSky telemetry passthroug not work

$
0
0

I have configured firmware serial2_options 0.
I tried to exchange the tx / rx lines.
It does not work,
The transmitter don’t discover sensors, I follow the manual, leaving the sensor search active and displaying the yaapu page.

A little more help.

Thank you.

Digging into 3dr radio power


Unwanted Yaw during auto missions

$
0
0

Hey, thanks for your reply.

Unfortunately plane firmware 4.0.2 does not contain any such parameter. I had already looked it up.

Weird situation i am finding myself in.

Heli Setup page and Helicopter 4.0.0 fw

$
0
0

@danielhellin and @Webillo Yes, we are working on getting a heli page working again. I am considering removing the old page altogether (the first image in @Webillo post) and replacing it with the 2nd image in @Webillo post. This is consistent with the page in QGround Control and hopefully will be more easily maintained as there is no special graphics. Also there are many outdated options on the old heli page. For instance, it shows only two swashplate types which is no longer true with 4.0 It also shows the old V curve for the throttle curve. That has been replaced by a 5 point spline throttle curve.

So unless I hear a compelling reason that the old page must be kept, I am recommending that it be removed and the new page be the only heli page option in Mission Planner.

Regards,
Bill Geyer
TradHeli Maintainer

AP_Periph 1.0.0 stable released

Several errors using HereFlow

$
0
0

Thanks for the log, I’ll see if @priseborough can have a peek because I’m pretty sure it’s an EKF issue.

Unwanted Yaw during auto missions

$
0
0

My bad. Apparently I can’t read. I assumed copter :roll_eyes:

Let me do a bit more digging.

Oneshot125/42 blhelis

$
0
0

I’m still check on this (this area of the code is not my expertise) but I think AP’s RCOU onboard log messages and the values sent to the GCS (i.e. chXout on MP’s status screen) will be scaled to the 1000 to 2000 range when non PWM outputs are used. So besides DShot we have various versions of CAN and so I think for consistency we should always log and send values in the same range (1000 to 2000).

Users need to be able to check that DShot is working though so hopefully we can think of a way to do this. My first thought is a text message sent soon after startup similar to what AP sends for the input decoding.
image

Lidar in AltHold

$
0
0

@anbello,

Thanks for the info and testing. Here is the parameter file for using the rangefinder is SITL and it seems to have some slightly different values (the scaling in particular). I don’t know if the parameter values are relevant but I thought I should point this out.

The wiki page linked above (here it is again) is for the EKF1 which we don’t use anymore. Perhaps we should update the page but for now I recommend users look at this EKF wiki page which I know is maintained although it has much less information on it.

By the way, my PR removed the ability to use the rangefinder at low altitudes and the barometer at higher altitudes. This wasn’t completely intentional (at the time I didn’t know the EKF2 even had this feature) but the change was the result of countless support calls from users who had set one of the two parameters (EK2_ALT_SOURCE and/or EK2_RNG_USE_HGT) and had horrible experiences often resulting in crashes. I don’t remember ever seeing a positive report regarding these parameters. Perhaps there are more issues in the EKF in this area, I’m not sure… but disabling the rangefinder + baro mixing has definitely reduced the support calls. I guess my point is I’m not willing to re-enable this behaviour unless it’s proven to be reliable in a wide variety of situations (baro or rangefinder failures, uneven surfaces under the vehicle, rapid climbs and descents, flights right at the threshold of the switch, etc).


Lidar in AltHold

$
0
0

@Frankendrone,

Thanks for the feedback on testing and good to hear that it’s basically working.

One thing that seems odd is the EKF appears to be consuming the rangefinder altitude even when it’s clearly bad. The EKF’s altitude is in red, the sonar’s range is in green. The EKF should really only be consuming the altitude when the rangefinder status is “Good” (4).

The rangefinder’s actual status can be seen in the RFND message’s Stat field

I’ve created an issue in the issues list and hopefully we can find someone to fix it. I suspect it’s actually not that hard to make the EKF only consume the rangefinder when it’s status is Good.

Very weird problem acceleration

$
0
0

I agree with @wicked1 that it’s probably not a control issue (it’s impossible to be sure without an onboard log though). I’m pretty sure that the controllers will always prioritise attitude over altitude. So even if the pilot commands full throttle, if the vehicle starts losing attitude control, the overall average output to the motors will be reduced in order to give more room for the attitude controllers to operate.

I also agree that the most likely culprit is actually high vibration leading to an attitude estimation problem.

Oneshot125/42 blhelis

$
0
0

Something like that would be great.

Pixhawk with jumper R8 and FrSky telemetry passthroug not work

$
0
0

I have the same problem now,
Four weeks ago I had it working , but with a previous version of Mission Planer, Arduplane 3.9.9 firmware and the yaapu script version 1.7.x .
Now the new 1.8 version and the copter ( heli) firmware 4.0 does not work together anymore
Sorry, tomorrow I must search for the correct version of this script . …a little too late now

Integration of ArduPilot and VIO tracking camera (Part 3): Indoor autonomous flights and performance tests

Viewing all 251372 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>