[NSRCA-discussion] Plettenberg 30-10 evo and Jeti ESC
ehaury
ejhaury at comcast.net
Fri Mar 16 05:27:08 AKDT 2012
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nsrca.org/pipermail/nsrca-discussion/attachments/20120316/4f37f141/attachment.html>
More information about the NSRCA-discussion
mailing list