<html><head></head><body><div class="ydp28cc17b3yahoo-style-wrap" style="font-family:times new roman, new york, times, serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Thanks for the update Jon. Good to have options. Sounds like your HMI and coding to drive it are coming along nicely.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Cliff</div><div><br></div>
</div><div id="ydp4b9ab885yahoo_quoted_6888117126" class="ydp4b9ab885yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, November 12, 2021, 09:53:42 AM CST, Jon Wallace via Personal_Submersibles <personal_submersibles@psubs.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp4b9ab885yiv2065101270"><div><div style="font-family:times new roman, new york, times, serif;font-size:16px;" class="ydp4b9ab885yiv2065101270yahoo-style-wrap"><div dir="ltr">FYI, I received a GPS unit from Adafruit yesterday and was able to interface it into my Arduino-type microprocessor package seamlessly. Like the ONWA model that Cliff tested, this one also outputs data in NMEA sentences over Serial interface. It provides location, heading, speed, date, and time when on the surface. Under water I will rely on my compass for general directional awareness.</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://www.adafruit.com/product/746" class="ydp4b9ab885yiv2065101270" rel="nofollow" target="_blank">https://www.adafruit.com/product/746</a></div><div><br></div><div dir="ltr">Current sensors are O2, CO2, Cabin Pressure, Cabin Temp, Cabin Humidity, 36 and 12 volt state of charge, HP-Air psi for ballast control, depth, water pressure, and water temperature. The final major sensor to be integrated will be the CruzPro water depth transducer which outputs in NMEA sentences and should be as seamless as the GPS was.</div><div dir="ltr"><br></div><div dir="ltr">For those interested in such things; performance of the graphics rendering software (Processing) has been less than I anticipated using Raspberry Pi 2 Model B. On average I'm measuring an 8 hz data refresh rate, which is more than enough for basic life support sensors but can make things like the compass display look a little "choppy" when turning in a tight circle quickly. The biggest performance buster is graphical rendering of the compass rose which requires a lot of calculations and image manipulation to display correctly based upon the heading. This can be alleviated somewhat by simplifying the Rose design and/or displaying a static image of a Rose and overlaying information on top of it, but I found there was a point of diminishing returns in taking this approach and 8hz was the best I could acheive. Removing the compass rose rendering completely and simply displaying a text box with the heading increases display speed significantly to about 20 hz which easily handles any compass movement without a hint of choppiness.</div><div dir="ltr"><br></div><div dir="ltr">Pi 2 B has 900mhz cpu and 1gb memory. OS performance is showing 36% cpu utilization, 525gb memory free, and no swap usage. So the hardware is handling things fine which builds confidence that the bottleneck is the graphical rendering by the Processing graphical software. The new Pi 4 is advertising native OpenGL so that may make a difference since Processing uses OpenGL.</div><div dir="ltr"><br></div><div dir="ltr">In any event, since fast tight circles are not a selling point for PSUBS vessels the graphical performance is not likely to have a real world impact in field usage.</div><div dir="ltr"><br></div><div dir="ltr"><br></div></div></div></div>_______________________________________________<br>Personal_Submersibles mailing list<br><a href="mailto:Personal_Submersibles@psubs.org" rel="nofollow" target="_blank">Personal_Submersibles@psubs.org</a><br><a href="http://www.psubs.org/mailman/listinfo.cgi/personal_submersibles" rel="nofollow" target="_blank">http://www.psubs.org/mailman/listinfo.cgi/personal_submersibles</a><br></div>
</div>
</div></body></html>