The Team was a group of around 200 Hams from around the world that had a lot of experience with the Nano from the 10,000+ Bitx40 and uBitx transceivers delivered around the world. When the project started in March we were told that Florida would be out of Vents by mid April. People were literally working around the clock on hardware and software design and testing. A sprinkler valve was tested to over a million cycles. The supply chain was shutting down, but the Nano was still available in large quantity. The Bitx PCB design was easy to modify to support pressure sensors, solenoid drivers, and push buttons. It already supported an LCD display. You would not believe the difficulty in sourcing sensors and components during this time period.

There were dozens of threads discussing alternate processors among our group members and members of other international teams. Our group did not have the time to switch. All design information was open source, so other teams were encouraged to modify our design to match locally available parts(this was a prime design objective). My suggestion was to mount a pin header instead of the Nano and let others plug in whatever processor they could get. Software porting was up to these other teams.

The bottom line was that a fully functional Vent was designed and ready for manufacture by the end of May. A Nano, a PCB, a sprinkler valve, two washing machine pressure sensors, a 3D printed relief/safety valve, and the code - estimate $200USD - provided greater functionality than the $20,000 commercial Vents now on the market.

I believe several groups in Europe used higher end processors. India started with the Nano.

Thanks for your input.

James

There's never enough time to do it right, but always enough time to do it over...

In reply to Re^7: Call function no more than every 0.1 seconds by jmlynesjr
in thread Call function no more than every 0.1 seconds by zapoi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.