MARSfarm Mini Version 0.2 (V0.21 and V0.23)

Documentation for MM.V0.23 — Most Recently Updated

Labs - Hydroponic Deep Water Culture

Labs - Wicking Tray

Hardware

Software

Software Architecture Overview:

  1. MARSfarm Device (Local Device Hardware/Software)
  • Each MARSfarm growth chamber has a Raspberry Pi with an SD card in it that has software pre-installed on it that is provisioned specifically for that device.
  • The Raspberry Pi connects to the internet using either Wi-Fi or ethernet, we recommend ethernet in most situations due to its reliability from year-to-year.
  • Once an hour, data from Co2/Temp/Humidity sensors and a camera in the growth chamber will be sent to three locations in the MARSfarm cloud using Python scripts executed by Cron.
  1. MARSfarm Device Connection to MARSfarm Cloud (Hosted Data Storage)
  • Camera - Images from the camera are sent to an independent S3 bucket hosted in Amazon Web Services (AWS), using a Python library called Boto.
  • Temperature/Humidity/Co2 - Sensor data is sent to a CouchDB database (http://data.marsfarm.io:5984/), hosted in AWS on an EC2 server, using a Python library called couchdb.
  • Temperature/Humidity/Co2 - Sensor data is sent to a shared Google Sheet, created by MARSfarm, using a Python library called gspread.
  1. User Access to Data in the MARSfarm Cloud (MARSfarm Web Application)
  • Raw data for each device should be accessible via each of the devices Google Sheets’s, provided along with the device-specific domains, in this spreadsheet: Links to Data for 6 MARSfarms - WHS (Regina Smart) - 01.07.22
  • The domain “http://app.marsfarm.io/reception/{devicename}” redirects to the MARSfarm web application, hosted in AWS on an EC2 server.
  • The web application uses the device name, which is provided by the user in the last part of the URL they enter (example: westlake1) to then determine what data to pull from CouchDB or S3.emphasized text