[NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC

James Oddino joddino at socal.rr.com
Fri Mar 16 13:26:14 AKDT 2012 

Derek, Earl, John,

We're getting close to understanding the system but not understanding the cause of the original problem.  Sounds like the Spin ESCs do work in high speed and it is not an amplitude problem.  I just looked at the 18MZ manual and I see no mention of high speed for that receiver.  Earl has to figure out if it does have a high speed mode.  If it doesn't, then John is correct that it does seem like the wrong direction.  Someone will eventually figure out what the rep rate is on the S.Bus but it would be so much easier if Futaba would tell us what the interface specs are.

Jim O


On Mar 16, 2012, at 2:06 PM, Derek Koopowitz wrote:

> Jim,
> 
> My Jeti SPIN worked fine running on the HS channel - only the programming box wouldn't work when plugging into CH6.  When I changed it to "normal" mode it worked just fine.
> 
> -Derek
> 
> On Fri, Mar 16, 2012 at 1:57 PM, James Oddino <joddino at socal.rr.com> wrote:
> I know the Jeti Box does not measure the pulse width on the high speed channels and I would guess the ESC wouldn't work either.  I run my throttle (Spin 99 ESC) on channel 7 and I suspect that was because it didn't work on high speed but I truly can't remember if I actually tried it on a HS channel.  I told you I was getting old.  Does the 18MZ receiver have any low rep rate channels?
> 
> Jim O
> 
> 
> On Mar 16, 2012, at 1:31 PM, ehaury wrote:
> 
>> Jon
>>  
>> Possibly, as Derek mentioned - setting the RX from HS to standard is worth trying.
>>  
>> Earl
>> ----- Original Message -----
>> From: Jon Lowe
>> To: nsrca-discussion at lists.nsrca.org
>> Sent: Friday, March 16, 2012 3:29 PM
>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>> 
>> Can average volts cause problems like Robert is seeing?  Could the speed control be looking for both a voltage peak and duration?
>> 
>> Jon
>> 
>> 
>> -----Original Message-----
>> From: ehaury <ejhaury at comcast.net>
>> To: General pattern discussion <nsrca-discussion at lists.nsrca.org>
>> Sent: Fri, Mar 16, 2012 3:24 pm
>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>> 
>> Well, Jim caught me. So much for quick & dirty!
>>  
>> I made the servo signal measurements using a high impedance meter with a scope mode. It displays a voltage at the top of the scope screen, as well as a freq. Without thinking, that voltage is the number I reported, and it's 50% different between the RX's because one was operating at 2X the freq of the other, but it's not pulse amplitude but average volts.
>>  
>> I took another look and the actual pulse amplitude is the same for both, and is 3v as Jim observed. Pretty obvious upon thinking about it. So - Futaba didn't change anything and Robert's problem isn't with pulse amplitude.
>>  
>> Jim, thanks for questioning me - sorry for the confusion.
>>  
>> Earl
>>  
>> ----- Original Message -----
>> From: James Oddino
>> To: General pattern discussion
>> Sent: Friday, March 16, 2012 1:55 PM
>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>> 
>> Earl, something doesn't look right.  How did you measure the pulse amplitude?  Did you have a servo connected?  I measure 3.0 volts peak unloaded on a 6108SB.
>> 
>> Jim O
>> 
>> 
>> On Mar 16, 2012, at 8:18 AM, ehaury wrote:
>> 
>>> I compared the servo pulse amplitude of the 6008HS (0.64v) and the 7008SB (0.32v) RXs. That's a significant difference, while Futaba servos are designed to work at that level, other stuff isn't. That's likely the issue with your ESC.
>>>  
>>> Earl
>>> ----- Original Message -----
>>> From: Robert Green
>>> To: 'General pattern discussion'
>>> Sent: Friday, March 16, 2012 8:44 AM
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> 
>>> Thanks Earl i was told that someone else in Europe was experiencing similar problems with theirs as well.  Hope they can get it resloved.
>>> From: nsrca-discussion-bounces at lists.nsrca.org [mailto:nsrca-discussion-bounces at lists.nsrca.org] On Behalf Of ehaury
>>> Sent: Friday, March 16, 2012 8:27 AM
>>> To: General pattern discussion
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> Suggest you give Futaba service / Steve Kaluf a call. It may be that the RX pulse rise is a little low for the ESC. Futaba have, in the past at least, used a lower pulse amplitude than some others which resulted in strange results when mixing servos on occasion. If this is the case, the problem is more compatibility with the ESC than RX defect, still annoying though.
>>> Earl
>>> ----- Original Message -----
>>> From: Robert Green
>>> To: 'General pattern discussion'
>>> Sent: Friday, March 16, 2012 7:42 AM
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> Ed, I don't like it either I mat try a ferrite ring, as I like the telemetry feature on the tx from the rx.  Anyone else using the 18MZ receiver seeing any issues with the motor cutting out?
>>> From: nsrca-discussion-bounces at lists.nsrca.org [mailto:nsrca-discussion-bounces at lists.nsrca.org] On Behalf Of Ed White
>>> Sent: Friday, March 16, 2012 6:56 AM
>>> To: General pattern discussion
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> Robert,
>>> 
>>> The only way I can think of that this is a receiver problem is that motor or ESC noise is being picked up on the ESC lines (any or all) and the 8 channel Rx is somehow more tolerant of the noise or better able to filter it than the other Rx.  I would be uncomfortable at leaving this at - I have to use my old receiver.   
>>> 
>>> Ed
>>> From: Ronald Van Putte <vanputte at cox.net>
>>> To: General pattern discussion <nsrca-discussion at lists.nsrca.org>
>>> Sent: Thu, March 15, 2012 10:14:28 PM
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> 
>>> Wait a minute. "The problem was with the receiver." doesn't quite cut it.  What was the problem?  
>>> I'm glad you got the problem "solved", but you can't trust that receiver until you identify the problem.  BTW, "I don't know" is a perfectly valid answer, but you could save somebody else a lot of grief if you know what was wrong with the receiver.
>>> Ron
>>> On Mar 15, 2012, at 8:26 PM, Robert Green wrote:
>>> Well I think I found the issue with the Jeti and the Plettenberg.  The problem was with the receiver.  I recently got a new radio, and installed the new rx in the plane, and then the issue started showing up.  I even went and borrowed a Jeti99Spin, to see if this would resolve the issue, but it did not, so I started to think of everything that I had changed, and decided to go back to my 8 channel receiver and voila, everything is back to normal.  Thanks to everyone for there input.  Feels good to have the problem behind me
>>> From: nsrca-discussion-bounces at lists.nsrca.org [mailto:nsrca-discussion-bounces at lists.nsrca.org] On Behalf Of Robert Campbell
>>> Sent: Thursday, March 15, 2012 8:38 AM
>>> To: General pattern discussion
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> My suggestion to limit throttle isn't to limit current draw.  It's to limit the motor RPM's so the ESC can remain synchronized with the motor.  If the motor turns faster than the ESC can handle, the motor will begin screeching.  I've only seen this on outrunners, never inrunners.
>>> Rob
>>> ----- Original Message -----
>>> From: Bob Richards
>>> To: General pattern discussion
>>> Sent: Thursday, March 15, 2012 7:55 AM
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> That was my thought. I don't understand why one would want to limit the throttle to something less than full. Why not install a prop that loads the motor less?
>>> Bob R.
>>> 
>>> 
>>> --- On Thu, 3/15/12, Peter Vogel <vogel.peter at gmail.com> wrote:
>>> 
>>> From: Peter Vogel <vogel.peter at gmail.com>
>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> To: " General pattern discussion " <nsrca-discussion at lists.nsrca.org>
>>> Cc: "General patterndiscussion" <nsrca-discussion at lists.nsrca.org>
>>> Date: Thursday, March 15, 2012, 12:15 AM
>>> Limiting throttle does NOT limit current to the motor, in fact, it can cause higher current draw.  All throttle does is vary the on vs off cycle during which voltage is sent to the motor. 
>>> Peter+
>>> 
>>> Sent from my iPhone4S
>>> 
>>> On Mar 14, 2012, at 7:29 PM, "Robert Green" <robcase1 at cox.net> wrote:
>>>> Hi Rob, the Static amps on the ground is 81 amps.  My throttle is limited to 85 percent.  Even changed out the speed controller and the same thing happened.   Really wish i knew what was going on?
>>>> From: nsrca-discussion-bounces at lists.nsrca.org [mailto:nsrca-discussion-bounces at lists.nsrca.org] On Behalf Of Robert Campbell
>>>> Sent: Wednesday, March 14, 2012 9:18 PM
>>>> To: General pattern discussion
>>>> Subject: Re: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> 
>>> Robert,
>>> Which Jeti are you running?  Advance or Spin?  Just a guess, but all the outrunners I've run require low timing advance and some require fixed end points and the throttle to be limited to 70 percent or so.  Also, have your checked your set-up on a watt meter?  Sometimes our set-ups pull more current than we were expecting and the ESC over current protection kicks in.
>>> Hope this helps.
>>> Rob
>>> ----- Original Message -----
>>> From: Robert Green
>>> To: 'General pattern discussion'
>>> Sent: Wednesday, March 14, 2012 8:19 PM
>>> Subject: [NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
>>> Is anyone out there running this combo.  Went flying today, and had some issue with the speed controller cutting out when i was setting up for my approach into the pattern.  I was pulling up and advanced the throttle to do an reverse cuban eight to get into my pattern, when the motor suddenly quit.  I pulled the throttle back and advanced it once again and the motor came back it did this on every flight except the first flight where i had no issues whatsoever.  my setting are high timing for the motor, low cut off voltage, acceleration high,
>>>  
>>>  
>>> thnaks in advance
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>>> _______________________________________________
>>>> NSRCA-discussion mailing list
>>>> NSRCA-discussion at lists.nsrca.org
>>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>> 
>>> -----Inline Attachment Follows-----
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2012.0.1913 / Virus Database: 2114/4873 - Release Date: 03/15/12
>>> 
>>> 
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>> 
>>> 
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2012.0.1913 / Virus Database: 2114/4873 - Release Date: 03/15/12
>>> _______________________________________________
>>> NSRCA-discussion mailing list
>>> NSRCA-discussion at lists.nsrca.org
>>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>> 
>> _______________________________________________
>> NSRCA-discussion mailing list
>> NSRCA-discussion at lists.nsrca.org
>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2012.0.1913 / Virus Database: 2114/4874 - Release Date: 03/16/12
>> _______________________________________________
>> NSRCA-discussion mailing list
>> NSRCA-discussion at lists.nsrca.org
>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>> 
>> 
>> _______________________________________________
>> NSRCA-discussion mailing list
>> NSRCA-discussion at lists.nsrca.org
>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>> 
>> 
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2012.0.1913 / Virus Database: 2114/4874 - Release Date: 03/16/12
>> 
>> _______________________________________________
>> NSRCA-discussion mailing list
>> NSRCA-discussion at lists.nsrca.org
>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
> 
> 
> _______________________________________________
> NSRCA-discussion mailing list
> NSRCA-discussion at lists.nsrca.org
> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
> 
> _______________________________________________
> NSRCA-discussion mailing list
> NSRCA-discussion at lists.nsrca.org
> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nsrca.org/pipermail/nsrca-discussion/attachments/20120316/5b0de3d6/attachment.html>

More information about the NSRCA-discussion mailing list