Process: Prototyping stage to Ramy's project planning and contribution accounting starting 2016-03-09 ending 2016-03-16

If you were logged in and working on this process, you would log your work on this page.

Outputs

Scheduled:

R&D report @Prototyping stage 1.00 Idea due March 16, 2016

Work

Planned Work: (Requirements are ordered by due date)

Work - Engineering: 23.00 Time - Hours due March 9, 2016

Assembling and testing of prototype.

Taken by Tibi
Work events:
April 28, 2016 2.50 Time - Hours Done by Jim

Software debugging with Tibi and Ramy.
We had some problems for the run and stop of the motors.
We understood that in digital read mode there was some signal bouncing that was miss triggering the motors or skip stopping the motors.
We forked the code to analog read with a bandgap, and Ramy found another problem. We think we fixed it at the and.
https://github.com/Sensorica/I-feel-like-a-potato-in-the-mist

April 28, 2016 3.50 Time - Hours Done by Tibi

Software debugging with Jim and Ramy.
We had some problems for the run and stop of the motors.
We understood that in digital read mode there was some signal bouncing that was miss triggering the motors or skip stopping the motors.
We forked the code to analog read with a bandgap, and Ramy found another problem. We think we fixed it at the and.
https://github.com/Sensorica/I-feel-like-a-potato-in-the-mist

I also rearranged a few sensors and replaced a paper guide.

April 22, 2016 2.00 Time - Hours Done by Tibi

Helped Ramy with mechanics. built another paper guide from an aluminum plate, installed the sensor on it, provided assistance with fixing the rollers to the structure.

April 15, 2016 3.00 Time - Hours Done by Tibi

testing the entire system, with Jim and Ramy, some software adjustments, all saved in Github.
https://github.com/Sensorica/I-feel-like-a-potato-in-the-mist

April 14, 2016 3.50 Time - Hours Done by Tibi

Worked with Ramy and Jim on setting up the motors and the sensors. We tested them with the Arduino board. Everything works, we stopped short of testing the entire Arduino program.

April 14, 2016 2.50 Time - Hours Done by Jim

Worked with Ramy and Tibi on setting up the motors and the sensors. We tested them with the Arduino board. Everything works, we stopped short of testing the entire Arduino program.

April 9, 2016 4.00 Time - Hours Done by Tibi

More mechanical work, added the sensor to the tray that I installed on the second roller. Ramy was there with me.

April 7, 2016 4.00 Time - Hours Done by Tibi

Mechanics : sensor attachment to rollers, built tray for guiding paper into one roller.
A bot of electronics: soldered connectors to the motor shield, tested the sensors.

March 30, 2016 0.25 Time - Hours Done by Jim

Debug the Arduino motor shield - helped Ramy and Tibi to figure out how to drive a DC motor, we found that there was a jumper that was missing on the board.

March 30, 2016 1.50 Time - Hours Done by Tibi

Creation of a mini board for the sensors, and mounting of this board on top of the Arduino motor shield.
Soldering of pin connectors on the Arduino motor shield.
Worked with Ramy.

March 30, 2016 1.50 Time - Hours Done by Tibi

Mechanical assembly of paper guides and optical sensors.

March 22, 2016 1.00 Time - Hours Done by Tibi

Mechanical mount of the roller on a 2x4 wood structure

March 17, 2016 3.00 Time - Hours Done by Tibi

Worked on integrating the IR limit switches into the design, we did some physical tests with the Arduino to see if they can support long wires.
Also produced a pseudo code for the entire system.

March 17, 2016 1.00 Time - Hours Done by Jim

Worked with Tibi and Ramy online, gave input on the pseudo code and some design considerations.

March 11, 2016 3.50 Time - Hours Done by Jim

Worked on a H-bridge to drive a DC motor in both directions. If we get this working fast, we can test the rollers with the sensors, before Ramy orders a motor driver or shield.

March 10, 2016 3.50 Time - Hours Done by Tibi

Worked mostly on mechanics. Replaced a broshless motor with a DC motor on the second roller, and tested it.

March 9, 2016 1.50 Time - Hours Done by Tibi

Implemented the MOSFET unidirectional and variable speed option, tested, works, communicated results and some recommendations.

[double time from Sensor Networks]

Work - Programming software: 1.50 Time - Hours due March 16, 2016

Write the Arduino code.

Taken by Tibi
Work events:
March 23, 2016 1.50 Time - Hours Done by Tibi

Arduino programming

Process context:

Pattern: Change
Context: Ramy project
Order: Work order 196 for Ramy's project planning and contribution accounting due: 2016-03-24

Previous processes:

Product design stage to Ramy's project planning and contribution accounting starting 2016-03-07 ending 2016-03-10

Next processes:

Experimentation stage to Ramy's project planning and contribution accounting starting 2016-03-16 ending 2016-04-11


Process notes:

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 the user 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.