Questions & Next Steps

[gracelower]

Opening this issue to document questions I come across and potential NEXT STEPS for the Open Water Level Sensor project.

• [x] PVC end caps
• [x] Parts spreadsheets
• [x] Solar system assembly
• [x] Metal vs. cellular antenna
• [x] Returning zeros (Log.info)
• [x] Get-Involved
• [ ] Polycase design
• [ ] Getting-Started instructions
• [ ] Close issues that have been completed

[gracelower]

PVC END CAPS PVC-End-Caps-GitHub

• [x] Upload datasheets + BOMs
• [x] Oatey red gripper (upper end cap)
• [x] Pipe bushing (bottom end cap)
• [x] Update descriptions in readme.md file
• [x] Add to parts spreadsheet + BOM

[gracelower]

PARTS SPREADSHEETS I have built two separate spreadsheets (one for Polycase enclosure, another for PVC enclosure), located in my Student Projects folder in the SharePoint

• [x] Update these spreadsheets & BOMs once all parts are finalized & upload .pdf or .csv to BOM folders

Specifically:

• [x] Pipe tape
• [x] Marine epoxy vs. superglue
• [x] Cable glands
• [x] Pipe bushing
• [x] Pipe gripper
• [x] Screws
• [x] Hex nuts

[gracelower]

ASSEMBLY INSTRUCTIONS I wrote new instructions for assembling the two sensor models, but more updates are needed to ensure a comprehensive and accurate assembly guide

• [x] Specifically, SOLAR SYSTEM ASSEMBLY in both models needs work
• [x] Solar system cable head does not fit through cable glands that would be able to seal the red cable itself
• [x] Need to take more photos of assembly process
• [x] Fabrication / PVC-Enclosure / readme.md ("How to assemble ...")
• [x] Fabrication / Polycase-Enclosure / readme.md ("How to assemble ...")

[gracelower]

METAL VS. CELLULAR ANTENNA (Polycase)

• This may not be an issue, but is something to watch out for!
• To enhance cell reception of the antenna, it should be no less than 10mm from metal objects ... while this was considered in the Polycase chassis design, it's not perfect (especially because of screws in the Polycase and chassis).
• Keep this in mind when deploying the sensor & assessing resulting data! Could potentially be an area for improvement.

[gracelower]

RETURNING ZEROS

• Previously, the code+sensor was returning too many zeros in testing. I adjusted the code to transition Serial.print statements to Log.info statements, which seems to have resolved this problem. I am opening this issue just as a reminder to look out for zeros moving forward.
• NOTE: When using the "Getting-Started" instructional guide, the sensor is powered by a PC, not a battery or solar system, so "battery level" WILL return zeros.
• Watch out for zeros in future testing & deployment; they shouldn't arise, but if they do, another factor may be at play.

[gracelower]

GET INVOLVED As the project progresses, expanding the contents of the Get Involved folder may be a nice touch! Not pertinent to the mechanics of the project, but important nonetheless.

• [x] I have started a spreadsheet of potential partners in my Student Projects folder in the SharePoint; if the sensor eventually gets to a distribution stage, feel free to use this resource as a starting point for deployment and educational partnerships!
• [x] Add links to the IO Rodeo Blog features, too! (Not sure whether this would be better in "Get Involved" or the main page readme.md file)

[gracelower]

POLYCASE DESIGN

• [ ] Potential project: collaborate with IO Rodeo to improve Polycase enclosure
• [ ] Use product with case knockouts?

[gracelower]

GETTING-STARTED INSTRUCTIONS

• [ ] A few photos in the Getting-Started Instructions markdown code are embedded but no longer exist; I believe these were photos included in previous versions of the repo, but are no longer present and therefore have 404/nonexistent pathways. Photos that no longer exist are marked in bold within the .md file.
• [x] Photograph missing photo Boron + Adalogger + Pins stack; embed.
• [x] The last section of instructions ("practice full code") has been simplified in the number of steps by changing the sample code itself; not sure if this is something we want to do for the other sections of the instructions, too.
• [ ] None of the other instruction sections are incorrect per se, but may benefit from simplifying.