<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Those are good points and context Chad. I wasn’t aware of the Hacker unit. The regulation I presented was from the AMA, which only applies to our events in the US. I don’t know what the FAI regulation says/reads, but it could be different. <div><br><div>To comply here, we only need to answer the question of whether this device is a “<span style="background-color: rgba(255, 255, 255, 0);">Power plant management system that adjust(s) power with regards to model performance, position or attitude”. </span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">In my thinking, the esc is changing it’s power output to maintain rpm, which is an aspect or consequence (regard) of performance. But an interesting consideration for sure!</span><div><br><div id="AppleMailSignature">Sent from my iPhone</div><div><br>On Jun 7, 2020, at 3:08 PM, Chad Northeast <<a href="mailto:chadnortheast@gmail.com">chadnortheast@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="content-type" content="text/html; charset=utf-8">So many of us (myself included) flew these at the WC in 2019, and there were many events in Europe that allowed their use. As well the Hacker Sensitrol (similar function, however it uses direct rpm measurement I believe) was also in use at the WC in 2019, so there is some good precedent for legal use at least internationally. They were known to the event organizers/jury/judges etc. that they were being used, and no one was disqualified or asked to remove them that I am aware of. Personally I did bring along a full batch of other esc’s in case this happened as there was definitely “chatter” about them being illegal, however it turned out that was not an issue. <div><br></div><div>My understanding is it would become illegal if you say used it to maintain airspeed, which would then in turn auto adjust the throttle input from the rx, essentially taking the pilot out of the “control loop”. What I understand in simple terms is that as long as the pilot is part of the control loop then its most likely legal.</div><div><br></div><div>Maybe Mark or Derek, or someone more in the loop on the inner workings of the rules with the FAI can give more info.</div><div><br></div><div>It would be a great shame to make these sorts of innovations illegal as ultimately it will stifle creativity and has zero bearing on the results. Everyone has access to them, so its a level playing field, the best pilot will rise to the top as usual.</div><div><br></div><div>Chad</div><div><br><div dir="ltr">Sent from my iPad</div><div dir="ltr"><br><blockquote type="cite">On Jun 7, 2020, at 12:34 PM, Tjpritchett <<a href="mailto:tjpritchett@aol.com">tjpritchett@aol.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8">As I was reading this thread, I was wondering how a self regulating speed control might fit within the current competition regulations. We’ve considered the gyro/ stabilization debate before, and that issue is pretty clear, since the relevant rule was written after gyro control was already available. <div>This capability, prop rpm, was not really around until now, and may need to be evaluated more carefully against existing rules. The most relevant I could find is copied and posted below, from the 2020-2021 AMA Competition Regulations, 4.4.2. Point number 3 seems particularly relevant. </div><div>What do you think?</div><div><div><br></div><div><div>Examples of control functions not allowed:</div><div>1. Preprogramming that will automatically perform a series of commands based on a timeline.</div><div>2. Automatic leveling or electronic stabilization in any axis.</div><div>3. Power plant management systems that adjust power with regards to model performance, position or attitude.</div><div>4. Positioning systems utilizing any sensors such as air data, GPS, distance, etc.</div><div>5. Learning functions involving maneuver-to-maneuver or flight-to-flight analysis.</div><br><div id="AppleMailSignature">Sent from my iPhone</div><div><br>On Jun 7, 2020, at 1:11 PM, flyintexanmark via NSRCA-discussion <<a href="mailto:nsrca-discussion@lists.nsrca.org">nsrca-discussion@lists.nsrca.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">A slight tweak in kv and a d3 should allow use of a ys200 prop. The right throttle curve and it may be possible to get Bryan Hebert to fly electric :)<div dir="auto"><br></div><div dir="auto">Seriously it seems more possible now than ever to emulate a YS.<br><div dir="auto"><br></div><div dir="auto"><br></div></div><div><br></div><div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Chad Northeast via NSRCA-discussion <<a href="mailto:nsrca-discussion@lists.nsrca.org">nsrca-discussion@lists.nsrca.org</a>> </div><div>Date: 6/7/20 9:27 AM (GMT-06:00) </div><div>To: <a href="mailto:nsrca-discussion@lists.nsrca.org">nsrca-discussion@lists.nsrca.org</a> </div><div>Subject: Re: [NSRCA-discussion] Plettenberg Advance 30-10 ESC - Questions </div><div><br></div></div>I will chime in my 2 cents on the Pletty. I have used the Jeti Spin 99 and the Futaba 9100 (same as OS 1100) and the D3, all of them without issues so I think you are safe with those for sure. I have not used the CC or the Jeti Mezon, but I imagine the Mezon is like the Spin. There is no issue taking a Pletty Advance to 90A, and no issues for big props, in fact the bigger the better. I use a 22-13, which hits around 85A and 6300 RPM on the ground, any prop made you can run on the motor depending on what you like.<div class=""><br class=""></div><div class="">Braking has always been an issue, even with the Jeti/Futaba ESC braking set I have never been able to get it “perfect” where its good in downlines and in 45’s etc, there always seemed to be a compromise. Propellor selection had some impact, I found APC’s brake better than a Falcon on their own so that helped to get the balance better at least for my style.</div><div class=""><br class=""></div><div class="">This is where the D3 shines (braking/constant speed), I think blows the doors off every other controller made. It is a total re-learn of how you fly, but once you get it I don't think you would want to go back. For those that don't know, the D3 is produced just for pattern and is custom to every motor, so you order for the motor you want. There is no programming, no telemetry, nothing really, you just put it in the model setup your tx and fly. It is a governor controller so setting up your RPM is absolutely critical, if you get it wrong you will not have great results and likely struggle with it. However the ability to get constant speed is very good, it really turned the Pletty into a setup that has braking as good as anything else IMO. It manages power for you in a lot of cases, for instance as you pull vertical and the models starts to slow down and load the prop the esc will apply power to maintain rpm, so you don't need to throttle up much, maybe 2 clicks on the stick.</div><div class=""><br class=""></div><div class="">Some of the adjustments you need to get used to, generally you want to start throttling up prior to pulling the exit radius, as the esc is always maintaining rpm of the motor you dont have that freewheel to help carry speed out of an exit. So if you don't throttle up early you will really lose airspeed. Mostly in looping elements you actually never need to really come to a full idle, as the esc is essentially braking all the time to maintain the rpm based on your stick position.</div><div class=""><br class=""></div><div class="">I have also found it very efficient consumption wise, as good or better than the Futaba/Jeti’s that I have used prior. Some really nice side benefits, it is light ~70g and inexpensive.</div><div class=""><br class=""></div><div class="">Below is a chart of rx output and motor rpm for the Pletty, personally I use 950 rpm for landing, 1950 rpm for normal flight (downline idle), and 5600 rpm at my midstick position. In case it doesn’t show up properly, one column is % of output, one column is us output of rx (0 - 2000 us) and last is motor rpm.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">
<table border="0" cellpadding="0" cellspacing="0" width="276" style="border-collapse:
collapse;width:207pt" class="">
<!--StartFragment-->
<colgroup class=""><col width="92" span="3" style="width:69pt" class="">
</colgroup><tbody class=""><tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" width="92" style="height:13.0pt;
width:69pt">100.00%</td>
<td align="right" width="92" style="width:69pt" class="">2000</td>
<td align="right" width="92" style="width:69pt" class="">6700</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">90.00%</td>
<td align="right" class="">1800</td>
<td align="right" class="">6030</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">80.00%</td>
<td align="right" class="">1600</td>
<td align="right" class="">5360</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">70.00%</td>
<td align="right" class="">1400</td>
<td align="right" class="">4690</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">60.00%</td>
<td align="right" class="">1200</td>
<td align="right" class="">4020</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">50.00%</td>
<td align="right" class="">1000</td>
<td align="right" class="">3350</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">40.00%</td>
<td align="right" class="">800</td>
<td align="right" class="">2680</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">30.00%</td>
<td align="right" class="">600</td>
<td align="right" class="">2010</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">20.00%</td>
<td align="right" class="">400</td>
<td align="right" class="">1340</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">10.00%</td>
<td align="right" class="">200</td>
<td align="right" class="">670</td>
</tr>
<tr height="17" style="height:13.0pt" class="">
<td height="17" class="xl63" align="right" style="height:13.0pt">0.00%</td>
<td align="right" class="">0</td>
<td align="right" class="">0</td>
</tr>
<!--EndFragment-->
</tbody></table></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>NSRCA-discussion mailing list</span><br><span><a href="mailto:NSRCA-discussion@lists.nsrca.org">NSRCA-discussion@lists.nsrca.org</a></span><br><span><a href="http://lists.nsrca.org/mailman/listinfo/nsrca-discussion">http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</a></span></div></blockquote></div></div></div></blockquote></div></div></blockquote></div></div></div></body></html>