Category: Arthur’s Status Reports

This week I worked on our final presentation, poster, and demo. We met several times this week to finalize our project.

We are on schedule

Next week is the demo itself, and also the final report that is due Thursday

This week I worked on:

• haptic feedback code is complete
• able to do a sequence of vibrations based on game state input
• we all met on campus to finally collect metrics for our tracking

We are on schedule

Next week

• final presentation, Ishaan is giving this one
• fine-tune some details for the final demo

This week I worked on the following:

• haptic feedback
  • being able to control 3 different microcontrollers with multiplexer
  • receiving input from FLORA via bluetooth module
    • so that the game is able to communicate with the glove
  • based on the input above (game state), different vibrations
    • fruit being cut: buzz 1 (effect 47)
    • bomb being cut: long buzz (effect 118)
    • fruit being missed (lose 1 life): long double sharp click strong (effect 37)
    • more vibrations to be added as needed

still on schedule

next week

• instead of just one vibration per game state, maybe have a sequence of vibrations per game state
  • this is so that the vibrations are felt longer by the player
• help Ishaan with Fruit Ninja game

This week I worked on the following:

• finished soldering the parts on the glove
  • FLORA arduino
  • Arduino Bluetooth Module
  • Breadboard
  • Mux
  • 3 motor controllers
  • 3 vibrating mini motor discs
  • Infrared LED & 330 Ohm Resistor
• haptic feedback arduino scripts
  • the arduino is able to control each of the 3 motor controllers on the glove through the Multiplexer
  • just using 1 type of vibration for now

Still on schedule

Next week:

• demo
• start adding more complexity for the haptic feedback
  • different vibrations
  • based on Fruit Ninja game state
    • this requires connecting the RaspPi to the Arduino via bluetooth
    • so that Unity can send data to the Pi, which then transmits it to the arduino

We met several times this week on campus in HH 1307.  We unfortunately hit an obstacle in our positional tracking of the glove. We discovered that doing background substitution in OpenCV with IR LEDs adds way too much latency. We saw that moving an IR LED across the screen with gray-scaling and background substitution has a 1 second delay on screen.

We’ve almost completed soldering the parts for the glove (FLORA, mux, microcontrollers, battery holder). Still need to solder the bluetooth module and IMU (not arrived yet).

Still on schedule for the demo

Next week, we will finish soldering all the parts on the glove, finalize the positional tracking, and write the haptic feedback Arduino code.

We met several times this week on campus in 1307 HH to work on our project. We are currently testing out positional tracking with our Raspberry Pi NoIR Camera module and Infrared LEDs. We are all currently working on the python scripts that will go on our RaspberryPi to control the Camera module, to filter for Infrared LEDs using frequency/wavelengths, and to contour the LEDs that the camera detects in order to track them.

We are still on schedule

We want to finalize the positional tracking by the end of the week and also start the assembly of the glove (right after we figure out the tracking). For the Interim Demo on April 12th, we want to have the glove fully built, and we want to be able to showcase how accurate our positional tracking is and how fast the response time is.

This week, I gave the Design Presentation for our project. We received lots of very helpful feedback which we will use to revise certain aspects and details of our design. All of the parts for the glove have arrived except for the IMU, (the positional tracking unit). I will also need to go to campus this week to retrieve some wires, a breadboard, and a Mux.

We are still on schedule.

For next week, we have the Design Report due on the 17th and for our schedule, we would like to have the glove assembly finished by EOW.

This week, we ordered all of the parts that we need for our glove. A lot of these have already been received, but I am still waiting on a few that have not yet arrived. I will begin assembling the glove as soon as I have all of the parts. I worked on the Application Area and Project Management slides for the Design Presentation which we have next week.

We are still on schedule.

As I said above, next week we have our second presentation of the semester concerning the design details and implementation of our project. I will be giving this presentation. Furthermore, I hope that by some time next week I will have at least received all of the parts for the glove so that I can begin the assembling process.

This week, after Logan gave the presentation on wednesday, I started making some research on what parts we are going to need for our glove controller. We will meet early next week to finalize this list and start ordering our parts.

We are still on schedule

Deliverables for next week: The design presentation as well as we should at least order all of the parts so that we can start assembling the glove.

This week, our team focused on our Proposal Presentation and making sure that all required elements are present. I was tasked with the Requirements section as well as making the Gantt chart for our initial schedule. We did however finalize the tasks, starting dates, and end dates together. This chart can be seen in our team status report as well as in our Proposal Presentation.

We are on schedule for this project and next week we will order all of the parts that we need for our glove controller. As soon as those parts arrive, we can start assembling the glove. Since the glove is one of our main risks, we want to make sure that the glove works or doesn’t as soon as possible.

If the glove is assembled by next week, then we will be able to post a picture. Once the glove has been built, I will turn all of my attention towards testing this glove to make sure that all the parts work correctly. This will be helpful once we code the game environment in order to identify where the errors come from.