Current Status of Project:
This week we researched many alternative design options based on conversations with Dr. Klaesner and Patricia Widder, including using an alternative form of force transducer. Options that have been brought back into consideration include load cells (con: expensive) and larger Force Sensing Resistors (FSR) (con: hard to get appropriate force range for our purposes, but if designed and then mass produced as per our project scope, where this device would be placed in all clinics country-wide, it is feasible).
Additionally, we have begun the purchasing process of the arduino (hopefully obtaining one with built-in bluetooth or obtaining a bluetooth module) and a standalone accelerometer. We are still doing research to see if buying an Arduino BT is better than an Arduino Due (or similar model) + bluetooth module. In addition, there is a phone app that is designed to communicate with the arduino bluetooth signal, which greatly simplifies our task. Some online research has shown that developing an app from scratch will be a significant amount of work, something that may not be able to be accomplished in full in the timescale of our project, so the phone app provides a good alternative if we can configure it to work.
Work Planned for Next Week:
Since we have just purchased an arduino microcontroller and a standalone accelerometer, we plan to focus on programming the microcontroller so that the data from the accelerometer can be stored on a computer. This also applies to the force sensing resistor, which we will order soon. We also plan to call several companies and ask about what the cost might be to implement the FSR on the large scale that we hope for.
Additionally, we will look into the bluetooth module (which see to only cost ~$7) and see if it is feasible for our project. A lot of learning will need to be done regarding programming the Arduino, since none of our group has any knowledge about that. We have been talking to Patricia about some of the details and nuances of that, since she has had a little bit of experience in that area before.
Anything needed from Client or TA before work can progress:
We are hoping to discuss these design alternatives with our client before moving forward with making the physical prototype. However, we are able to move forward with the programming of the device during this time.
This week we researched many alternative design options based on conversations with Dr. Klaesner and Patricia Widder, including using an alternative form of force transducer. Options that have been brought back into consideration include load cells (con: expensive) and larger Force Sensing Resistors (FSR) (con: hard to get appropriate force range for our purposes, but if designed and then mass produced as per our project scope, where this device would be placed in all clinics country-wide, it is feasible).
Additionally, we have begun the purchasing process of the arduino (hopefully obtaining one with built-in bluetooth or obtaining a bluetooth module) and a standalone accelerometer. We are still doing research to see if buying an Arduino BT is better than an Arduino Due (or similar model) + bluetooth module. In addition, there is a phone app that is designed to communicate with the arduino bluetooth signal, which greatly simplifies our task. Some online research has shown that developing an app from scratch will be a significant amount of work, something that may not be able to be accomplished in full in the timescale of our project, so the phone app provides a good alternative if we can configure it to work.
Work Planned for Next Week:
Since we have just purchased an arduino microcontroller and a standalone accelerometer, we plan to focus on programming the microcontroller so that the data from the accelerometer can be stored on a computer. This also applies to the force sensing resistor, which we will order soon. We also plan to call several companies and ask about what the cost might be to implement the FSR on the large scale that we hope for.
Additionally, we will look into the bluetooth module (which see to only cost ~$7) and see if it is feasible for our project. A lot of learning will need to be done regarding programming the Arduino, since none of our group has any knowledge about that. We have been talking to Patricia about some of the details and nuances of that, since she has had a little bit of experience in that area before.
Anything needed from Client or TA before work can progress:
We are hoping to discuss these design alternatives with our client before moving forward with making the physical prototype. However, we are able to move forward with the programming of the device during this time.