Putting the Community back in to Radio Control
Are the esc's in the motor nacells or in the fus?...I've put the esc's in the nacells on my Cat so if I do decide to fly it off water, they should be well out of the way and benefit from additional forced cooling from the props..... I'm using 2.4g, so interference that could be potentially induced in the long leads won't be a problem...It might be if you're using 35mHz though, a ground range test at full throttle would be well advised.
Just a point of clarification here. The reason for maintaining short leads between ESC and battery isn't primarily due to risk of radio interference, it's due to inducing high voltage spikes in those long leads which may damage the ESC, especially if running this near it's limits.
Leccy flierIn my post, I impressed, stressed the importance of having a suitably rated ESC...Running them on the edge ( as you intimated to be acceptable) is the reason most esc's get damaged. If you're in any doubt speak to the guy at Giant Cod and ask him what the biggest single cause of esc failure is besides connecting them up the wrong way around...
Over the years the idea that long battery leads can cause damage, keeps rearing its head...In the very early days of electric flight ( over 20 years ago) this was a potential problem, mainly due to the fact that the semiconductor technolgy and circuit design available at the time was nowhere near as robust as modern day esc's, I know, I used to build them.I can only speak from experience of flying electric flight for over 25 years..it's never happened. Theory is fine but practical experience, to prove for, or against ,wins out every time....
Regarding 2.4 v 35mHz interference point, again, I have flown multi engine, multi edf, high power ( 2Kw ) set ups and since converting to 2.4g , I have never had a single glitch ( the flight log on my Spektrum Rx's proves this), I used to get fed up trying to optimise RX, esc, extension lead positions etc to minimise interference issues when on 35mHz ( even using multiplex IPD's, percieved to be the best for interference rejection).
Also the interference problem is more likely to be induced in the extended esc Rx lead ( hence the reason of optically coupled versions for higher power versions.
Also the migration from Brushed ( spark generating) motors to Brushless ( sparkless) motors has solved a large percentage of interference issues now.
Another issue for interference is also the use of cheap linear becs in esc's not superior switch model devices which produce more electrical noise...( can of worms..... I know poorly designed, poorly screened, switched mode models can be problematic)
Also just to add to the discussion pot.... I have never had a problem in multi's, using both esc's becs ,without disconnecting one and also I have used a small capacity rx battery to top up the bec's current delivery, again with no issues ( 2nd can of worms)..... [Theory may say no.. many , many years and hundreds of hours of use proves otherwise. ( New bigger can, bigger worms) Shaun
Would it be grossly exaggerated manufacturer's ratings, such that they recommend using an 80Amp ESC for a 50 amp current draw? Or a 40 amp controller for a 25 amp current draw?So, on that basis, any incidence where that has happened would be evidence that there can be an actual problem? There have been reports of such and a flying pal has had exactly that problem. The manufacturer's instructions refer to the problem and offer the appropriate advice.It's a bit like those anti-Tiger tablets that people might take in deepest Surbiton. If you take the tablets and don't have a problem does it mean that the tigers were deterred, or were there never any Tigers there in the first place? I haven't had a problem either, but I do tend to follow the manufacturer's installation instructions with regards to lead length and so lack any contrary direct data. I'm also happy to run my Jeti controllers a little below their rated limits,with a bit of headroom, whilst recognising that other manufacturer's kit simply couldn't handle that, having seen the results of Tornado 40 amp controllers letting out the blue smoke at just over 20 amps. The Jeti's have run for years at ca 40 amps for a 45 amp controller, with no problems, but I personally wouldn't dream of running an OEM or one of the cheapy 40 amp controllers at 35 amps.
So, on that basis, any incidence where that has happened would be evidence that there can be an actual problem? There have been reports of such and a flying pal has had exactly that problem. The manufacturer's instructions refer to the problem and offer the appropriate advice.
Hi Brian,There is always confusion over this issue... The advice given ( as was the case for early Jeti Advance controllers, to not extend battery leads by more than 20cms ) was basically because the longer leads potentially could act as an aerial that could transmit interference to the esc Rx lead...That was the issue,( and the reason why it is always preferable and good practice to use twisted as opposed to ribbon type extension wiring), not, I believe that the controller would be damaged by a pulse flying down the battery lead....Your mate with the problem, was it interference or did the esc get damaged by using long leads ?..Had the esc been run at its max rated value or was there plenty of headroom?Was it an esc of older design or a newer one and was it as you correctly mentioned , a cheap over egged chinese esc or a more expensive, but higher quality one. Was it adequately cooled...There are many, many reasons why esc's go west!!
Again, I can only offer my actual experience of running long battery lead esc's. The info I posted was that, not, what I have been told or heard or a personal theory or belief .It's there as I said for people to agree with or not.....but over 25 years experience of flying electric models and I've never damaged one by using long leads....( I always used the multiplex extension leads with a ferrite ring on though and in many cases had a seperate Rx battery to the servo / esc supply pre 2.4g on the bigger set ups)
It's also interesting that many moden esc's don't have that caveat re lead length in the instructions any more.....I used to be an avid Jeti User, but have been using Turnigy ( hobbywing) ones now for the last 2 years from the minute 1g 3A single cell one up to 100A versions with no problems at all...If you've not tried one have a go...Easy programming , with lots of options, very well constructed and the quality is repeatable...i.e. a common problem with 2 same manufacture and spec esc's in twins is the start at different throttle stick positions, usually meaning a bit of clever programming using 2 Rx outputs to sync them.....The Turnigy ones are virtually identical in performance, in my experience, to date, confirming a high level of quality control and design...At about half the price of a similar Jeti, there worth a look.
Not trying to be dictatorial here, just offering a view Shaun
Over-rating esc's? No My Jeti 40A have been running fine for years at 44A peak, very well cooled, and the peak is for 5 secs or so only. Likewise Kontronic JAZZ esc's, happy to run at or just over rating. But they ain't cheap. Nowadays I buy 60A Emax/HWing etc, but run them at 40-45A and not had a problem. I might do at 60A though Ref lead length, not yet smoked an esc due to extending battery-esc leads, but then I never extend more than 8" as per manufacturer recommendations.
Hang on a mo, are we talking about the leads plugged into the receiver here? Only in my post I was referrring to the main battery to ESC leads, rather than the signal, positive+negative lead plugged in on extension leads.
... Over the years the idea that long battery leads can cause damage, keeps rearing its head ...
... make sure they are amply rated ...
... have a suficiently large heatsink on to dissipate any heat ...
Nice analysis and testing programme Peter and very interesting results.
So Peter, twisting or twinning the power leads would have an adverse effect?
OOOPS..Leccy, PDR, Alex, mark, etc ...we've been edited...We've over stepped the mark...
Page created in 1.368 seconds with 32 queries.