Team Status Report for 04/29/23

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

The biggest risk right now is making sure the whole system works. There were a couple of bugs in the HID driver that require fixing. For example, the compute module was successfully able to classify the input sensor data and attempted to dispatch it to the computer, but sometimes the host computer was not able to receive it. We also experimented with debouncing times so that random gestures aren’t picked up but the action isn’t too slow.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

None since last week.

Provide an updated schedule if changes have occurred

No changes.

Team work adjustments

No teamwork adjustments have been made. We are currently on track to accomplish our tasks and are currently all just working on them.

List all unit tests and overall system test carried out for experimentation of the system. List any findings and design changes made from your analysis of test results and other data obtained from the experimentation.

  1. Latency tests – averaged over 20 trials. The finding we found is that using a time-series-based approach is pretty speedy compared to neural networks, which was stated in the presentation.
Measurement Actual Value
Oscilloscope measurement of Pi 4 GPIO pin and sensor detection output 

(overall measurement)

~ 112ms
Sensor data collection ~ 100ms
Model classification time ~ 5ms
Wi-Fi transmission delay with ping tests ~ 5ms
Dispatch time TBD

2. User experience tests. The finding we found is that our initial goals were overestimates as we were able to significantly exceed the target metrics we had, with the exception of the range. This is because we felt like for the best user experience, the configuration should be as hands-free as possible, which is why we switched the communication protocol from local wifi to using the Raspberry Pi as a hotspot. That way, we would not need to reconfigure both the glove and Pi when the user uses the glove in a different location. Even though this came with a trade-off of lesser range, we decided it was alright considering that it still worked at least 10 meters away, which is far enough in a classroom setting.

Requirement Measurement Procedure Target Metric Actual Value
Usability Ease-of-use: User study measuring comfort, setup time, and responsiveness 90% user satisfaction based on survey

Setup time < 5 mins

~4 minutes
Portability Measure weight with a scale.  < 500 g 57g + 34g battery
= 91g
Range Test wireless communication across measured distances Up to 50 m between glove and compute 10 m
Battery Life Run glove module with all sensors and communication running and measure total power consumption up to 1 hour of continuous use ~40 hours

3. Accuracy tests – We tested the zoom-in and out gestures, however, the zoom-in wasn’t as accurate as we had hoped. We found out that the sensor of the index finger wasn’t that responsive to flex, which is particularly important for our zoom-in gesture. Xuan will replace the sensor in hopes that the algorithm will achieve higher accuracy.

Train/test split evaluation

Accuracy of dispatched HID controls

> 90% gesture recognition accuracy 95% for rotation/pan

Zoom in – 65%

Zoom out – 90%

Enable-disable – TBD

Dispatch accuracy TBD

Xuan’s Status Report for 4/29/2023

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

We started working on the final deadlines such as the poster. I also am in the middle of repairing and strengthening the glove since the wire of the middle finger’s flex sensor apparently broke off. I’m also assisting Gram and David in their testing and calibration of the glove so that it is as accurate as possible.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

We should be on track as we’re continuing our testing phase.

What deliverables do you hope to complete in the next week?

This week, I hope to finish all the testing as well as the final deadlines

Xuan’s Status Report for 4/22/2023

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I didn’t anticipate having to resolder most of the flex sensors because it was too short. I initially soldered so the sensors would fit exactly on each finger of the glove, but it turns out that extra room was needed. I also switched from using a hard wire to a more flexible one. These were setbacks that occurred but fortunately were resolved in time. I was supposed to work on the battery circuit this week but this took a large amount of time.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Progress is slightly behind schedule due to this setback, but we should be on track as we’re continuing our testing phase.

What deliverables do you hope to complete in the next week?

This week, I finish integrating the battery into the glove and also plan to continue integration and run the tests that require an assembled glove.

Team Status Report for 04/08/2023

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

Much like last week, the most significant risk right now is still just the integration between the individual subsystems. We did finish basic system integration as we showed in the interim demo, as we got a full dataflow working from sensor reading to HID dispatch command. However, we still need to work on continuing this integration, but it should be going along as the glove itself was finished this week. We’re also conducting tests in our individual subsystems during the integration process, and more tests are to follow.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

None since last week.

Provide an updated schedule if changes have occurred

No changes.

Team work adjustments

No teamwork adjustments have been made. We are currently on track to accomplish our tasks and are currently all just working on them.

Now that you are entering into the verification and validation phase of your project, provide a comprehensive update on what tests you have you run or are planning to run. In particular, how will you analyze the anticipated measured results to verify your contribution to the project meets the engineering design requirements or the use case requirements?

Accuracy will be measured by collecting data from different runs of gestures and comparing the number of samples that are correctly classified.

Performance will be measured in the classification layer by measuring (in Python) how long it takes to classify each window of data that comes in from the glove module.

Xuan’s Status Report for 4/8/2023

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I finished soldering the glove, and Gram will help me in sewing the glove since I, unfortunately, have no sewing experience. I also ran some tests outlined below. I cleaned up the circuit so that it’s actually neat when used.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Progress is on schedule.

What deliverables do you hope to complete in the next week?

This week, I plan to continue integration and run the tests that require an assembled glove. I also will begin integrating the battery into the glove.

Now that you are entering into the verification and validation phase of your project, provide a comprehensive update on what tests you have you run or are planning to run. In particular, how will you analyze the anticipated measured results to verify your contribution to the project meets the engineering design requirements or the use case requirements?

The tests I have run include network latency tests with the MQTT, the range test, and making sure the flex sensors values are actually being read. I was able to verify that the connection to the Raspberry Pi hotspot was sufficiently quick, as packets were received properly every 10ms. Moving the Arduino 50 meters away from the Pi also didn’t affect the latency that much which passed the other test. Tests I will run include the battery test and the oscilloscope test mentioned in our design requirements. I will also assist my other group members in the accuracy tests since we will have the glove ready.

I will analyze my measured results by directly comparing them against the initial test goal metrics that we outlined in our design presentation and paper. For example, I’ll make sure that the battery test lasts at least one hour as stated in our requirements. This way, I’ll be sure that my contribution meets the design requirements.

Xuan’s Status Report for 04/01/23

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

For this week, I mostly focused on soldering the circuit; I’m almost finished with soldering the circuit (will finish tomorrow). I also made a couple of minor optimization changes to the Arduino code. Specifically, the Arduino ADC reads from an integer 0-1024 range, however, the voltage that I ended up getting varied between 1-2.1 V, so I had to do some fine-tuning.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Progress is on schedule.

What deliverables do you hope to complete in the next week?

This week, I plan to begin assembling the actual glove with the soldered circuit and start integration with the other components.

Xuan’s Status Report for 03/25/23

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I finished assembling the breadboard circuit and testing it to see if it actually worked. The way how Arduino detects the inputs is via a voltage divider circuit, so when the flex sensor was being bent, there would be a different voltage drop. I had to test the other resistor I was using to ensure that the change in the ADC reading from the Arduino had sufficient range; if the other resistor was too small or large, there wouldn’t really be a noticeable change in resistance. I ended up asking for permission from a 220 TA to use the resistors they had in their lab as I asked Professor Tamal if there were available resistors around.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Progress is on schedule.

What deliverables do you hope to complete in the next week?

This week, I plan to begin soldering the sensors.

Xuan’s Status Report for 03/18/23

What did you personally accomplish this week on the project? Give files orphotos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I finished the MQTT portion for the code of the microcontroller. There was a decision made to hold 10 data packets on the glove side before transmission in order to reduce network traffic, as the minimum time interval in reading the IMU data is around 10ms. This might change with further testing though. I also started with the desktop application that we’re using for the configuration and calibration, which would be written using the Qt library.

Currently, it has the option to switch between left and right-hand mode, but the calibration process isn’t written yet as I think the compute module would need to be done before that. I’m also finishing up breadboarding the glove circuit.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

I think we’re on track.

What deliverables do you hope to complete in the next week?

I hope to further test using the breadboard circuit and integrate it with the MQTT portion of the compute module to see if there is a need to further optimize the network latency.

As you’ve now established a set of sub-systems necessary to implement your project, what new tools have your team determined will be necessary for you to learn to be able to accomplish these tasks?

I’m not necessarily learning anything new, but probably would need to sharpen up my soldering skills. I also probably would need to sharpen my skills in Qt.

Xuan’s Status Report for 03/11/23

What did you personally accomplish this week on the project? Give files orphotos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

A large portion of the week was spent working on the design report. It actually was easier than I initially expected due to the preparation we did from the entire design iteration process, as we had most of our ideas down when we did the slides.

I also started writing the system code for the microcontroller of the glove module. Specifically, I started writing code that would read sensor data from the various pins and started implementing an MQTT client that would pack and transmit this packet over a network.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

I think we’re on track as we adjusted our schedule last week.

What deliverables do you hope to complete in the next week?

I hope to finish the main code of this glove microcontroller and assemble a basic breadboard representation of the glove module. This is to ensure everything will be working before soldering any component onto the glove.

As you’ve now established a set of sub-systems necessary to implement your project, what new tools have your team determined will be necessary for you to learn to be able to accomplish these tasks?

I’m not necessarily learning anything new, but probably would need to sharpen up my soldering skills.

Xuan’s Status Report for 2/25/2023

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

We prepared the slides for the design presentation. We also started with the design report, although we didn’t make significant progress yet because the feedback came yesterday.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

We are slightly behind because our Gantt chart didn’t take into account the significance of the design review process and spring break. We updated the Gantt chart in response. Also, one of our parts was missing because the wrong part was shipped, so we put in a request for that. I think the original chart also had extra time that could be shortened, so we edited that part too.

What deliverables do you hope to complete in the next week?

I hope to finish the design report and start assembling the hardware glove module when the missing part arrives.