sim-
Turnigy Multistar 30A
I'd flashed the Turnigy Multistar 30A (http://hobbyking.com/hobbyking/store/__25365__Turnigy_Multistar_30_Amp_Multi_rotor_Brushless_ESC_2_4S.html) with kda.hex and it's getting very hot after a few seconds. One of my ESC burned down and after it my Motor, too.
I'd tried different versions since 2012 and they all have the same problem.
Thank you for fixing this issue.
This seems rather serious. There are a number of posts regarding this issue. Of course, I went and flashed mine before seeing there were problems. Now I'm afraid to fly until either this is resolved, or I have to order new ESCs :-(
http://www.rcgroups.com/forums/showthread.php?t=1762953&page=3#post27472839 http://www.rcgroups.com/forums/showthread.php?t=2188024 http://fritzw.com/2014/07/02/turnigy-multistar-30amp-simonk-overheating-like-on-fire/
Maybe there is a fuse-Bit Problem or something like this.
To specify the Issue: If I'm connecting the Motor with a flashed ESC and let it free-wheeled at lowest throttel, the ESC is getting hand-warm after approx. 30sec. With more throttle, it's getting more then hand-warm.
With a mounted prop, the Motor needs a lot ore current and the ESC is getting boiling hot. It's okay with an stabilized current-source (okay means, that the ESC doesn't burn after 1 minute testing). Unfortunately I'd tested one ESC directly with my Lipo and one phase burned down after approx. 40sec. with medium throttle. I'd got a sudden Motor stop, it wobbled around and released magic smoke. (*I'd tested the motor today and it's still okay hopefully. Maybe only some plastic smoked)
If you need more informations, please ask, so I can help you.
Okay, I can confirm that I have this exact problem. I ran on low throttle (on the ground) and the Multistar 30A SBEC ESC got noticeably warm in less than 30 seconds. The others (3 * Multistar 30A OPTO) were still icy cool. I flashed all of them with the latest kda.hex yesterday.
Another data point... since flashing, the ESC in question tries to drive the motor even when the only power is from the flight board via USB. This is new behaviour, and very suspicious.
Hi,Floyer007 I am a player not for a long time ,I also got the same problem in my ESC,but now I solve this problem from my friend,he advise this ESC have two version,the old one and the new one ,so there are also have two software,these two version ESC need match the different software version.I guess maybe you brought the new ESC but flashed with the old software.I brought three new ESC and flashed with the new software,this ESC boasting high efficiency,all N-channel design,I am very like it .Here I uploading the two version ESC and the software ,hope this can help all of you.
@Goodplayervivian, where would I find the updated code? There are no recent commits here, you have no repositories, and none of the forks seem relevant.
I also use this ESC, I think you flashed a wrong software and get this problem, pls try to download the correct files and select the right version file to flash, wish you will be success! http://www.divshare.com/download/25795440-a95
I also solve this problem by flashing the software, here I upload the two different version ESC with two different files,hope this can help your guys http://www.mediafire.com/download/njog23wt8o5ree7/Turnigy+Multistar30A.zip
@Goodplayervivian, thanks for the file. I won't get a chance to reflash until tomorrow at the earliest.
How did you generate the modified firmware? What options?
What would be really useful is if you could actually document the code differences from the existing kda.inc, and/or issue a pull request to get them in here. There seem to be a lot of people burning up these ESCs for no good reason, if the solution is already understood.
@Goodplayervivian what changes did you make for them to work? could you create a pull request?
@JimKuhn do you know what git commit started this overheating, so I can clone it and roll back the changes(I really need the firmware, the official one that shipped with it is horrible. I cant fly with it as the motors won't spin at the right speeds so the quad twirls on the ground and rips it's props. I know its the official firmware as I swapped out everything with spares. I also tested the esc with different motors and the same problem).
@thehurley3 I have no idea what commit started the problem. I was using the stock firmware (successfully). Upon flashing with SimonK, 3 of the ESCs (OPTO) seem fine, the 4th (SBEC) does heat up dramatically.
@Goodplayervivian I definitely have the old version of the ESC (if the pictures you enclosed are accurate). Flashing with your enclosed Old.hex does not seem to fix the problem, the ESC is blistering hot in short order...
This is a refresh rate problem. The multistar ESCs are using a p-channel FET that has a really high turn-off time according to the datasheet. What that means is that the body diode in the FET is still conducting current when PWM is turned on. The easy way to fix this is to reduce the PWM rate to 8kHz, which will allow the body diode in the FET to turn off between each cycle of commutation.
I've made an edit to the code that seems to fix the problem. The downside is that the PWM rate is now into the audible range, which is kind of annoying. But at least your aircraft won't catch on fire now - they're nice and cool to the touch after extended full-throttle operation, even without any airflow over them.
Either way it's a simple fix and I'm going to submit a patch. If it's accepted, you'll be flashing 'multistar.hex' to these instead of 'kda.hex'.
Stay tuned.
For those of you capable of compiling this yourselves: http://meat.damnit.us/tgy/multistar.patch should do nicely.
For those of you not capable of compiling this yourselves: http://meat.damnit.us/tgy/multistar.hex will do the job.
@khudson, fantastic... this patch looks plausible :-) I'll apply and build tomorrow.
On Sat, Jul 19, 2014 at 4:53 PM, khudson [email protected] wrote:
For those of you capable of compiling this yourselves: http://meat.damnit.us/tgy/multistar.patch should do nicely.
— Reply to this email directly or view it on GitHub https://github.com/sim-/tgy/issues/52#issuecomment-49529294.
Hello! I was actually just testing this myself with a Multistar 30A that arrived yesterday. Mine is all N-channel, no P-channel. I've posted pictures here: http://0x.ca/sim/esc/HK_9351000004/ ...and renamed the old ones to _old: http://0x.ca/sim/esc/HK_9351000004_old/ . khudson, do yours look different? It will need more than adjusting the PWM frequency, if so..
When I take a look at your pictures, I have the Problems, with the "old" version.
Are there any differences at all with your board vs the pictures in the "old" directory? Like which FETs they used? Possibly there is an intermediate revision where they tried to do something cheaper (my assumption :)) and then figured that was a bad idea and redesigned it to be all-N-channel.
So, it turns out mine was just kda.inc modified to have an inverted high side. I've pushed a new kda_nfet board type and fixed the voltage sense values for this and the original board (normally not used).
@khudson, any reason why this problem doesn't affect the OPTO version of this ESC? Perhaps they are using the "old" p-channel FET that doesn't have the lower refresh rate requirement.
@sim- I wish I had the new version :-(
sim-: mine look like the '_old' type. I ordered them about a week ago from the HK US warehouse. An all n-FET design makes these far better than they were, especially at that price point. Anyways, I'll verify the FETs are the same on your "old" one and mine, and follow up to this message.
Jim: I'm not sure - I don't own the "opto" version (opto in quotes here because it's probably not actually optoisolated - I haven't seen any of them that are). If you cut the shrink off and take some photos that show the FET model number I can dissect the datasheets and let you know what I think is going on.
Looks like your old one has Toshiba TPC8020 n-channel FETs and Alpha/Omega AO4407A p-channel FETs. I do believe we've found the culprit - there is an intermediate (likely indeed "cost savings") version that uses instead Toshiba TPC8123 p-channel FETs and retains the TPC8020 n-channel FETs.
From the datasheets for the AO4407A and TPC8123:
TPC8123: Turn-off fall time: 80 ns, no specific body diode recovery time AO4407A: Turn-off fall time: 12 ns, body diode recovery typ. 30 ns
Either way the two parts are such a different spec it's kind of amazing they don't fry themselves with the stock firmware.
@khudson - I can confirm that both the "opto"/BEC version both use the TPC8020-H. The "opto" uses the AO4407A, whereas the BEC version uses the TPC8123
@khudson I'd tested your multistar.hex and it works fine. (No overheating) But I have no Quad currently to test it.
@khudson @Floyer007 I'll be flashing and flying hopefully tomorrow (too much came up today). Thanks for the work on figuring out this mystery.
But test it carefully, maybe there is an unexpected behavior at full speed or something like that. (I didn't test the motors with props)
@sim- I'd forgot to check the name of my mosfets. Also I forgot them at my laboratoy and will give more informations about them the next days. But I think they're the same like khudsons, cause I'd bought them at the UK Warehouse two weeks ago.
I just got back from a session at the park. Aside from having to free one of my quads from a tree (heh) all my ESCs performed flawlessly, as did the batch of 4 that my friend had on his quad. We fly pretty aggressively, so if something was going to burst into flames it probably would have.
Ok, I pushed a kha_8khz target for this case (done with just an include), since this probably also affects compatible boards.
When I was originally testing with the HK-SS30A (non-HW) boards (http://0x.ca/sim/esc/HK_HK-SS20A/), the issue seemed to be related to the slew rate (and maybe miller effect?) and the drive of the high side. The high side FETs briefly turn on while the low side was turning on (swinging down) if the current was still flowing through the PWM'd phase. Depending on the motor and load of the motor, it would be fine or would get very hot in seconds.
This happens even at low speeds, so I found that I could drag a motor by hand without causing much heating, but then if I dragged a little more, it would rapidly heat the high-side FETs (because they were all turning on-ish, for a brief period). On the 'scope, you could see that the difference was if the current had collapsed or not yet by the time PWM turns on (pulls down) again.
For example, with this (old, unrelated) 'scope trace, you can see that the current has stopped before the PWM (on ch1) turns on again: http://0x.ca/sim/esc/timing_loss_fix/zc_debug_unloaded_390kv_zoom.png ...but dragging/loading the motor elongate the time it takes to collapse back to the floating range, and, with enough load, meets the part where it turns back on again, leaving a trace of just high and low on the PWM'd phase.
I suspect the problem here could be fixed by adjusting the gate resistors on one side (low or high), or by changing the drive strength through the NPNs that they use to drive the P-channels. Lower PWM will help, but the shoot-through problem will still happen if the motor is loaded enough.
Hello, i have also bought 3 weeks ago 6 Multistar 30A BEC at Hobbking in European Warehouse. Before flashing i have read about the heating Problems. So now i opened the heat shrink and found a old Design, but with TPC8123 and TPC8020H http://postimg.org/image/426ie5maz/ http://postimg.org/image/sheqf7l7v/ So i can confirm the FET change too. I have not flashed any firmware yet, but I also will use the kha_8khz in future.
hello i buy the same esc like sim : http://0x.ca/sim/esc/HK_9351000004/ whit "tcpa 8012 h" so n channel i flashed them whit kda.hex and they burn immediatly so who have tested kda_8khz whit this version? and who know make a correct firmware for this esc. i dont buy more multistar for sure. And thanks for the work of the community if anyone make a firmware for this version im ok for test on my esc i just wish they not catch fire^^
Those need to be flashed with kda_nfet.hex as simon outlined above. Then they won't burn.