<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks, Bob.<br>
<br>
Arch, The Hitec Aurora RX module has the capability of splitting
receiver power and servo power inputs. You can run raw lipo output
up to 35 volts to power the receiver and that voltage will be used
to trigger the low voltage warning. Servo power would then be a
separate regulated input from the same battery. Just don't reverse
the inputs. :) <br>
This means that it is possible on anything up to an 8S system to
power the receiver with raw motor battery and actually trigger a low
voltage warning in the TX at a motor battery voltage of your
choosing higher than the ESC cutoff. Of course the same could be
done instead for the 2S pack driving the radio system on a 10S. If
you get the additional telemetry module you might be able to do
both.<br>
<br>
John<br>
<br>
On 11/22/2011 7:04 AM, Archie Stafford wrote:
<blockquote cite="mid:28879.1321970654@md.metrocast.net" type="cite">
<p>
<style> BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }</style>
Keep in mind on most of the telemetry I have read about and
seen the battery warning given is the measured voltage coming
into the receiver. Running a regulated system this will not
give a true battery status.</p>
<p>I do agree with John though, that listing what is acceptable is
probably much easier than what is not.</p>
<p>Arch<br>
<br>
<br>
<br>
<b>On Tue 11/22/11 8:37 AM , Bob Richards <a class="moz-txt-link-abbreviated" href="mailto:bob@toprudder.com">bob@toprudder.com</a>
sent:<br>
</b></p>
<blockquote style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px;
MARGIN-LEFT: 5px; BORDER-LEFT: #5167c6 2px solid; MARGIN-RIGHT:
0px">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="top">
<div>These are the best thoughts on this subject that I
have read.</div>
<div><br>
<br>
--- On <b>Tue, 11/22/11, John Gayer <i><jgghome@comcast.net></jgghome@comcast.net></i></b>wrote:<br>
</div>
<blockquote style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: rgb(16,16,255) 2px solid"><br>
<div id="yiv1278670611">
<div>I think you would be better off listing the
information that a pilot and his caller can
receive through telemetry during an official
flight. This information could be audible alarms
for exceeding limits of the three parameters you
listed. This is effectively the same as the low
battery alarm currently in your transmitter. This
one just happens to have an RF link added between
the sensor and the alarm. <br>
<br>
We should not be concerned about what telemetry is
being downloaded and recorded but only what
telemetry data the pilot/caller is receiving in
realtime during an official competition flight.
It doesn't make a lot of sense to enact rules that
cannot easily be enforced. It should be
permissible for the pilot to set up a download of
any info he wants but would only be allowed to
examine the telemetry data postflight as an
instructional aid. That data would have no
standing in the competition and could not be used
for any kind of protest.<br>
<br>
Of course there should be a ban on any closed loop
control systems that use the attitude, velocities
or accelerations of the model as feedback, either
directly in the model or through the transmitter.
This should not preclude the use of closed loop
systems such as those that control surface
position, system voltage or motor/engine rpm which
do not use aircraft parameters as feedback.<br>
<br>
John<br>
<br>
</div>
</div>
</blockquote>
</td>
</tr>
</tbody>
</table>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NSRCA-discussion mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NSRCA-discussion@lists.nsrca.org">NSRCA-discussion@lists.nsrca.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nsrca.org/mailman/listinfo/nsrca-discussion">http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</a></pre>
</blockquote>
</body>
</html>