I was having a quick look at the AutoQuad ESC32 wiki yesterday and their fancy ESCs actually have a current limiter that might prevent this kind of thing:
http://autoquad.org/wiki/wiki/esc32/esc32-calibrations/esc32-current-limiter-calibration/
These ESCs look far more advanced than SimonK…but the downside is:
1. much more expensive
2. require soldering before you can actually put them on your quad
-Randy
--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I tried autotune today with a similar setup.
Sunnysky 4108 480kv motors
15x5 CF props
10000mah 4S
Tarot 650 CF quad frame
30amp Quattro ESC
I had similar results. During first roll measurement a motor seemed to cog. Quad flipped and fell. I started playing with throttle to force cogging and was able to repeat cogging with extreme throttle movements. I then tried some 30A Turnigy Multistar ESCs flashed with SimonK. Less cogging but it is there occasionally on rapid throttle changes. I've read that Wii-esc had better sync than SimonK so I ordered some HK F30s that I can put Wii-esc on. I wished I'd seen those ESC32s before!
Phillip
Those must be clones of the ESC32 hardware. Good to see that they *can* be made cheaply at least.
I totally agree that smart ESCs will very quickly pay for themselves even if they are more expensive than normal ones.
-Randy
I'm sorry Holger, i've read well, "this macro limits the throttle to double of its previous value", but during AutoTune do not think that from the point of hovering on the amount of throttle that is given to tilt the multicopter can not be double the previous value here, should ask Leonard what value of throttle is used in the procedure.
Randy,
Good find. Looks like the shop may be state side also. I will give them a shot.
Jesus,
I've been able to test and recreate the problem on the bench by repeatedly and rapidly moving the throttle from to to bottom. It's obvious when the ESC and motor loses sync. You have to test with prop attached, though.
Phillip
Sorry, Pablo, you get credit for the good find.
Marco,
If 3DR were to make smart ESCs, what’s the maximum voltage and current that you would need for your copter?
I think it’s 6S batteries (i.e. 25V) but how many amps do you need per ESC? 40Amp? 30Amp? Any idea how much current your hexacopter draws when hovering and at full throttle?
-Randy
From: drones-...@googlegroups.com [mailto:drones-...@googlegroups.com] On Behalf Of Brendan O'Reilly
Sent: January 15, 2014 9:09 AM
To: drones-...@googlegroups.com
Subject: [drones-discuss] Re: APM Copter V3.1: Autotune with reflashed ESC... warning!
...so SimonK loaded ESCs are of no advantage (or worse) for "bigger" copters? Randy suggested that the ESC32's might be a good option for the higher pole count motors and larger props. If "slower" firmware is all that is required then that sounds great.
--
I have two machines running 22-pole pancake motors:
A photo-quad with an APM 2.0, AX-4008Q / 620kV turning 12x3.8 SF props, and Skywalker Quattro 20A ESC with BLHeli firmware on 4S. This one flies like a champ, went through
--
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
Para,
Re the comment about getting the hall sensor working. Does that sensor produce a voltage between 0 ~ 5V (or 3.3V) to indicate the current it’s sensing? If it does then it should be possible to get it working without any code changes. The wiring diagrams are on this wiki page:
http://copter.ardupilot.com/wiki/common-using-a-current-sensor/
and then to get it to produce an accurate number you might need to calibrate it as shown on this page (including a video!):
No pressure of course, it’s your copter, but just wanted to provide the info in case.
-Randy
Yesterday I run Autotune on two of my heavy hexa, installing powerful motors with large carbon propellers 15x5, F40A ESC flashed with SimonK firmware (the latest version), working with 6s LiPo.
During the automatic tuning of the "pitch" two motors have completely lost sync and miraculously i recover the multicopter and land without damage.
Thinking it was a case I repeated the procedure with another multicopter, always very heavy (same propellers) and the problem occurred again (always during variations on the pitch), this time only one motor lost sync during one of the fast throttle inputs that Autotune produces, the quad is tilted diagonal, not to the right side.
This was always done during the step on the pitch because the multicopter is much more reactive on that side for obvious reasons of weight (battery, landing gear, etc.).
I try to find the logs and post them here as soon as possible, but the problem in my opinion is that Autotune produces too fast throttle change input during the procedure, from the "hovering" (quad in a horizontal position) to the max location where it's tilted, these too rapid accelerations, that only the code can produce but our thumbs would be almost impossible, causing possible out of sync with the SimonK firmware.
Now, I don't know how Leonard can solve the problem because this thing could never happen even on some setups, but I did it three times and honestly do not intend to try again because I risked crashing quad very large and expensive.
On DIY Drones I've read of someone who has had the same problem, and had not realized what had happened, the probable cause is one that I wrote, as long as the code of Autotune there is something wrong (do not think).
The problem in my opinion is certainly not attributable only to Autotune (i hope), but of course this procedure can cause crashes with fast ESC reflashed with SimonK or BlHeli firmware for out of sync, our have been warned.
Bests, Marco
--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
Lorenz,
--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
Hi, where did you get the clones? I am unable to find them
--
Just remember that as with clones of 3dr products, buying these does not support the original creators who obviously put a lot of work into them.
-Randy
From: drones-...@googlegroups.com [mailto:drones-...@googlegroups.com] On Behalf Of Phillip Smith
Sent: January 23, 2014 11:33 AM
To: drones-...@googlegroups.com
Excellent news. Hopes are climbing that these smart ESCs are really going to help with the mechanical failures.
--
The dc feel parameter doesn't fix the problem, it does make it hard or even impossible for the pilot to cause the problem. However the problem could still be caused by flying in turbulence.
The basic truth here is if auto tune can cause the problem, the you can repeat the problem in normal flight, provided you are using the same PID gains.
The only way to prevent this problem is to keep all the gains low enough to make the esc throttle response too slow to ever cause the problem for that esc/motor/prop combination. Anything less is just flying arround the problem.
The basic problem is people are using Simon K on big copters where it isn't needed because the're is a perception it is better. For large copters Simon K like not using lock tight on your motor mounts.
Where Simon K has real value is small copters using small props. Here the reduced latency can really improve performance.
--
You received this message because you are subscribed to a topic in the Google Groups "drones-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/drones-discuss/tq8l52cwGXg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to drones-discus...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
Yes it would. But all that is doing is reversing what the Simon K firmware does.
Simon K basicly removes the input filter from the esc. What you are suggesting is to add that back into the arducopter code.
Yes I agree with you. I just don't like adding tuning parameters and complexity to the arducopter code because people are purchasing and using hardware that is not appropriate to the task and a safety hazard.
As an example there would be equal cause to limit the maximum throttle response because people wanted to drive motor/prop combinations that can draw 30 amps with 10 amp esc's. I use this example because this is what we are doing.
I personally like that Auto tune causes these problems because I would prefer to see the copter crash during tuning in an isolated field from a known issue than while flying over a wedding reception.
Heh.. nice call Leonard.
In case no one gets the reference… https://www.youtube.com/watch?v=ocqB6_y71xE
Don’t be that guy.
From: drones-...@googlegroups.com [mailto:drones-...@googlegroups.com] On Behalf Of Leonard Hall
Sent: Wednesday, March 5, 2014 10:14 PM
To: drones-...@googlegroups.com
Found a possible fix for the low KV Motor problem!!!!!!Im running a similar setup and had a motor stall from the APM asking too much of the ESC's and in the end, the motor stalled.Ends up there is a function in the full parameter list called RC_FEEL_RP - You can set this for a softer response to stick input commands.On the Throttle side, I set the radio for a small throttle delay incase I throw all the power in at some point. Its barely noticeable to me, but the motors don't knock at all anymore.Besides having to tune by hand and NOT using Auto Tune.... That seems to have fixed the issue.
On Saturday, January 11, 2014 10:11:53 PM UTC-10, Marco Robustini wrote:Yesterday I run Autotune on two of my heavy hexa, installing powerful motors with large carbon propellers 15x5, F40A ESC flashed with SimonK firmware (the latest version), working with 6s LiPo.
During the automatic tuning of the "pitch" two motors have completely lost sync and miraculously i recover the multicopter and land without damage.
Thinking it was a case I repeated the procedure with another multicopter, always very heavy (same propellers) and the problem occurred again (always during variations on the pitch), this time only one motor lost sync during one of the fast throttle inputs that Autotune produces, the quad is tilted diagonal, not to the right side.
This was always done during the step on the pitch because the multicopter is much more reactive on that side for obvious reasons of weight (battery, landing gear, etc.).
I try to find the logs and post them here as soon as possible, but the problem in my opinion is that Autotune produces too fast throttle change input during the procedure, from the "hovering" (quad in a horizontal position) to the max location where it's tilted, these too rapid accelerations, that only the code can produce but our thumbs would be almost impossible, causing possible out of sync with the SimonK firmware.
Now, I don't know how Leonard can solve the problem
...
--