<html><head></head><body><div class="ydp50c36274yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">Michelle, all - </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">My initial reactions reminds me, </div><div dir="ltr" data-setdir="false">I was once involved with a commercial RFID link, written by a standards committee of Architects (and no designers / implementer ), that had:</div><div dir="ltr" data-setdir="false">5 different forward link BW. (separate filters, switches, gains, cost, size, etc.)</div><div dir="ltr" data-setdir="false">8+ different Reverse link data Rates, multiple M Codes, etc.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I learned:</div><div dir="ltr" data-setdir="false">a) Architects LOVE features that grow with binary weights. And really LOVE even more binary options that multiple with other binary weighted features.</div><div dir="ltr" data-setdir="false">(and why wouldn't they? It naturally falls out of the thought process. Very cool and exciting!)</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">b) It took enormous time and energy to implement and verify each mode.</div><div dir="ltr" data-setdir="false">c) Adaption algorithms take extra energy above and beyond to implement and verify.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">d) no one really wants to be adapt to the edge of a link budget. The apple religion of "it just works" (always!) is successful for a reason.</div><div dir="ltr" data-setdir="false">{---- even record breakers and EME experimenters will tell you how much extra link margin they had!}</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">and the kicker ---></div><div dir="ltr" data-setdir="false">e) *Really 3 buckets solve the large majority of trade-off needs. small/medium/large; slow/average/fast. (you get the idea).</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">f) When implemented, even the architect on staff (coauthor of said voluminous standards doc), who had to support and make recommendations to customers </div><div dir="ltr" data-setdir="false">--- ONLY used the edge cases to make his own life simple. If you look at the math, he only used a small subset of the A*B*C*D*E available options.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">My $0.02</div><div dir="ltr" data-setdir="false">KI6CLA</div><div dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="ydpb49838e8yahoo_quoted_2983913611" class="ydpb49838e8yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, June 17, 2020, 11:13:55 AM PDT, Michelle Thompson via Ground-Station <ground-station@lists.openresearch.institute> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpb49838e8yiv8995645327"><div dir="ltr">Attached is today's cut of the System Architecture document for AREx. This is also our baseline design. <br><br>We have a significant milestone coming up in the 25 June 2020 hardware meeting for AREx. <br><br>I need this document to be as good as it can be by then. <br><br>Please review. All comment and critique welcome and encouraged. <br><br clear="all"><div><div dir="ltr" class="ydpb49838e8yiv8995645327gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr">-Michelle W5NYV<br><br><div dir="ltr"><br></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
</div></body></html>