<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Thanks Rud.<div>I will keep that in mind.</div><div><br></div><div>Regards.</div><div>- Kumar<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Oct 29, 2021, at 11:22 AM, Rud Merriam <rudmerriam@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I wouldn't invoke ballistic behavior for more than a few seconds,
at most. You have to keep the robot reactive to dangerous
conditions. For instance, a ballistic behavior with backing move
could run into something since there usually are no backwards
looking sensors. That could damage the robot or environment if
maintained for a long period.<br>
</p>
<div class="moz-signature"><font face="Comic Sans MS" color="#000080"> <br>
-73 - <br>
<b>Rud Merriam K5RUD</b> <br>
<a href="http://mysticlakesoftware.com/"> <i>Mystic Lake
Software</i> </a> <br>
<br>
</font>
</div>
<div class="moz-cite-prefix">On 10/28/21 11:22 PM, Thalanayar
Muthukumar wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAAwP+LZoReOSedB48xZx_ZafwXdp92wX72g+ivZ6u4Kiuw45aQ@mail.gmail.com">-
Ballistic behavior is high priority and invoked for example, for a
period of time (say 30 seconds)</blockquote>
</div></blockquote></div></body></html>