If you were logged in and working on this process, you would log your work on this page.
Outputs
Scheduled:
Unplanned Production:
Work
Planned Work: (Requirements are ordered by due date)
Unplanned Work:
Did some programming in LabView.
I am developing LabView code to interact with all the sensors used in this project.
This LabView code is used to perform tests and analysis on different sensing systems and to analyse data. LabView is a powerful data analysis software, and it can be used to monitor plants for a long time in the lab, save the data and analyse data on the fly. I also comes with user friendly UI.
https://docs.google.com/document/d/1Z_WF2GNPBqH7gQYdY7Hodu92x9w-DHx_zkvDuh6ZgOk/edit#heading=h.lu5ghaw7ye5s
We can also use these programs, which can display data in real time in a nice graphical way, during events.
This was done in the context of an event around sensing in agriculture, organized by Bruce and myself. The goal of this project is to attract more participation in the project.
http://www.meetup.com/SENSORICA-Fridays/events/220483925/
Worked with Tibi on prototyping the hanging smart pot , during the hackathon Dec 18-19, 2014.
See doc.
https://docs.google.com/document/d/1S9lUbVN7cP3QRd8f7BuGdhHnlvHpysxtVEDOMKmF4rE/edit
We tried thermoplastic forming. Failed.
Worked with Abran on prototyping the hanging smart pot , during the hackathon Dec 18-19, 2014.
See doc.
https://docs.google.com/document/d/1S9lUbVN7cP3QRd8f7BuGdhHnlvHpysxtVEDOMKmF4rE/edit
We tried thermoplastic forming. Failed.
Organized,coordinated and participated in the eCG hackathon
https://sites.google.com/site/sensoricahome/home/working-space/events/past-sensorica-fridays/ecghackathon-hackforequity
Also did documentation.
Helped Abran with the prototyping of the smart pot prototype
https://sites.google.com/site/sensoricahome/home/what-we-do/projects/microgarden-control-systems/microgarden-control-systems---announcements/thesmartpotprototype
Setting up experimental eCG website, with forum, and populating it with data
Updating and debugging code to allow switching relay to work
Fixing delay in displaying large amounts of data on the web application, and debugging it
Planning modular system, writing doc, creating schematics
Worked with Tibi on the Garden Manager, installation in the SENSORICA lab in Montreal. I solved some software and driver issues to run a webcam on the GM server.
Worked alone and with Jérémy on the prototype in the SENSORICA lab. Essentially, I installed the system on a vertical shelf, put a webcam on it to test the concept. Later during the day we also had some problems with the Arduino. It turns out that the USB wire was too long. I solved that with John.
During the day there was some emails exchange with John and Guillaume about webcam.
Updating web application, making RTC module optional, deploying the updates to the Sensorica server, and making it run live on the web with data from the newly replicated electronics
Adding light control circuit and code
Remotely configuring server and RPi, installing software, testing remote programming of arduino, setting up web application, and posting info about the progress to Sensorica group
Creating, editing, and posting survey form
Preparing for presentation, providing photos and info, setting up live system and monitoring it during presentation
Helped Guillaume to install a Linux server in the lab. This is needed to put the garden Manager online. The idea was first proposed by John, Tibi tested with John a raspberry pi. After, John plugged his Garden Manager to the network and shared live data with project members. the idea was to reproduce that at SENSORICA lab.
Updating GM web application interface (start data capture button and info)
Figuring out how to set up remote access via the web to control RPi and arduino remotely (almost there)
Discussing/planning the future of the project (ie. merging the two prototypes) and wiring doing diagrams
Taking photos, testing minimum components required, and sharing info to replicate
Updating pin config and pushing source update to github
Reorganizing sketch code (and then making it work again)
Updating web application and adding flow chart
Reorganising sketch code and turning it into a library
Integrating flow meter and debugging code
Researching, assembling, and testing irrigation system
Set up and debugged irrigation test (successful)
Creating and publishing irrigation breadboard diagram
Researching and prototyping flow meter to arduino setup
Adding 12v power control resources (links to tutorials/examples) to main doc
Updating pin config doc
Updating parts list
Wiring up and testing solenoid water valve
Documenting bill of materials. Adding notes, ideas, comments, etc. to main document. Updating pin configuration.
Prototype development
Process context:
Pattern:
Generic R&D
Context: eCommunity Garden
Order:
Work order 139 for Garden Manager R&D Report due: 2014-11-02
Previous processes:
Product design stage to Garden Manager R&D Report starting 2014-10-22 ending 2014-10-25
Next processes:
Manufacturing stage to Garden Manager R&D Report starting 2014-11-03 ending 2014-11-10
Process notes:
Prototyping stage of an R&D process. This stage is about making something tangible, in the physical world, that uses a design and that works to a satisfactory level.
During the R&D process there is a cycle between Prototyping and Design, meaning that the prototyping process might unravel problems with the design, which will trigger changes of the design.
Prototyping produces a detailed description of a tangible thing, how it is made, how it functions, how well it functions. This description is based on empirical data or physical experimentation.
This process is also known as Testing and Refinement: Construction and evaluation of multiple pre production versions of the product. Early (alpha) prototypes are usually built with production intent-parts-same geometry and material properties as intended for the production version of the product but not necessarily fabricated with the actual processes to be used in production. Alpha prototypes are tested to determine whether the product will work as designed and whether the product will satisfy the key customer needs. Later (beta) prototypes are usually built with parts supplied by the intended production process. Beta prototypes are extensively evaluated internally and are also typically tested by customer in their own use environment. The goal here is to answer questions about performance and reliability in order to identify necessary engineering changes for the final product.
INPUT: a product design
OUTPUT: a detailed description placed in the main document
More than one prototype can be made, tested and documented during this process.