Tushhar’s Status Report for 04/30

For this week, I worked on our testing for the mat, poster and the box housing Arduino and the perfboard.

On Wednesday, we tested our game properly with everything working for the first time. While the game worked generally, there were many times where presses weren’t being detected. I worked on it to make it so that the Arduino calibrates the thresholds on startup. Caio helped me to get that code working properly. This seemed to help a bit but due to reasons mentioned in the team report, it still seems to be unreliable at times. A strategy we came up with to deal with this problem is to have a button that we ask the user to press before every game. This will set the thresholds according to what is measured at the time of the button press. We hope that this will make our game more reliable.

I also spent time on Friday working on laser cutting and putting together a big enough box to house our Arduino and perfboard. It has holes to let wires from the FSRsĀ  and the USB cable from the Raspberry Pi into the box. The Arduino and the perfboard will be fastened to the base of the box. It’s pictures are shown below. Big thanks to Spandan for putting in the time and effort to paint the box and make it look beautiful!

The rest of the time in the week was spent on designing and writing some of the content for the poster.

For the last week, I plan to implement the button press to let the Arduino calibrate the thresholds. Other than that, I will be working on the other submissions for our project.

Tushhar’s Status Report for 04/23

This week, I was able to complete my part of the presentation, help with making the physical mat, and gather testing data.

Collectively, we planned out our final presentation on Monday, and figured out the necessary information we needed. This helped us plan our testing for Wednesday as well. I was particularly involved with FSR error rate and coverage testing. While Spandan or Caio stepped on the mat, I took down the number of missed hits and recorded data in a table. This data will be shown in the final presentation. On Friday, I was also involved in the planning of the top layer of the mat, as well as making necessary physical measurements.

Individually, I worked on the slides for ‘use case requirements’, ‘complete solution’ and FSR testing. I also learnt how to crimp connector pins to awg wires. After watching some videos on it and practicing it on spare wire, I was able to get the hang of it. I spent a lot of time on Friday learning this and attaching male connector pins + housing to 20 wires coming out from the FSRs. This will allow us to easily connect and debug the FSRs to the female headers on the perfboard. With this the circuit layer is completely ready.

As per my plans last week, I was able to complete my goals for this week. For the upcoming week, I will be contributing to finishing whatever’s left for the physical mat. I am hoping that we are able to test the entire system after the completion of the mat.

Team’s Status Report for 04/16

This week, we made considerable progress in building the physical mat, as well as the game on Python.

All three of us spent a lot of time soldering the components this week. We soldered the FSRs to their corresponding length of wires based on their positions. We also labelled them for easy identification. We were able to successfully attach them to their corresponding plates as well. Later on in the week, we also soldered connections and female headers to the perfboard. This perfboard has all the necessary connections. We only need to plug the wires in for it to work. This way, we don’t have to worry about putting any other components under the mat and connecting them there. For rest of the mat, Spandan and Tushhar learnt how to use the sewing machine in Techspark. We consulted with the person who taught us sewing, and upon further discussion amongst the three of us, we were able to plan the proper dimensions, cuts and seams for the layers of the tarp. We even decided how the pockets for the plates will be implemented with velcro and sewing. This should help achieve one of our big goals, which is to have the entire mat ready by the end of this week.

In terms of the software, Caio was able to finish the crude game. The game should be playable, and the transitions between screens like game screen to pause screen or name input screen to menu screen should be working now. The high scores are also be saved and accessed properly now. Now, there are particularly 2 tasks remaining for the software. The first task is to add animations to make it feel more like a game. The second task is to modify the code to be able to handle more than 5 songs.

In terms of schedule, we were able to complete the crude game and the circuit layer for our mat. For the upcoming week, we aim to finish the mat and add some animations to the game. We will also be putting in a good amount of time towards making the final presentation.

Tushhar’s Status Report for 04/16

For this week, I spent most of my time working on the circuit layer of the mat. I was able to achieve all of my last week’s goals.

For many of the components I soldered, Caio and Spandan helped with gathering, planning and holding the components. Having an extra pair of hands really helped speed up the process. On Monday, we were able to solder and label the FSRs to appropriate length of wires based on where they are to be positioned. We also tested them individually to make sure they worked after soldering. On Wednesday, I was able to design the layout for the circuit. Its picture is shown below.

  • A5 to A1 refer to the analog pins that they will connected to on the Arduino.
  • The letters represent the following
    • U: Up FSRs
    • L: Left FSRs
    • R: Right FSRs
    • D: Down FSRs
    • P: Pause FSRs
  • The number 1 corresponds to the first pins for both FSRs in parallel (for corresponding arrow) and the number 2 corresponds to the second pins.

On Friday, we soldered female headers to the perfboard according to the layout above. The reason we decided on female headers instead of direct soldering is because the connections to the FSRs won’t be permanent and can be debugged/replaced more simply if need be. The perfboard was tested with buttons and works properly (similar to how it was tested on breadboard). Here is the picture of how the connections look.

I also learnt how to use the sewing machine in Techspark alongside Spandan from a nice person there. For the upcoming week, I am planning to attach male headers to the ends of FSR wires so they can be put into the female headers easily. With this the circuit layer of the mat should be good to go. I will also be working with Spandan to cut and sew the tarp for the mat. Rest of my effort will be put towards the final presentation.

 

Tushhar’s Status Report for 04/09

This week, I was able to properly demonstrate the Arduino and plate working in unison with the game in action for the Interim Demo. Before the demo, we made sure the plate replacing the button from last week worked properly. The following picture is taken from a video in action.

Rest of the work mentioned below has mostly been in conjunction with Caio. Upon moving on to the next step of soldering, we found that the Z shape FSR was unresponsive for the sections after the fold. This also resulted in many foot orientations not working. We decided to thoroughly test other possible options for the FSRs. Ultimately, we came to the choice of using the FSRs in parallel (both in arrangement and the circuit). In terms of response, this worked the best. The FSRs can also be cut from the 2ft length and still work properly. For the best results, the plates will be placed such that the FSRs are perpendicular to the the up arrows.

After this issue was dealt with, we soldered some of the FSRs to properly measured length of stranded wires. We also used heat shrinks to prevent the two open ends of soldered wires to touch each other and short circuit. After doing so, we tested the FSRs again to make sure that the heat from the soldering iron did not damage it.

For the next week, I aim to finish soldering rest of the FSRs. I will also try to secure a perfboard from IDeATe. If unable to do so, we will order some. I will design the layout for the perfboard connections and solder the circuit accordingly. With this, the circuit layer of the mat should be mostly complete.

Team Status Report for 04/02

For this week, we were each able to work on our individual tasks and then combine some subsystems to have it ready for our Interim demo.

Spandan worked on the menu screen and is almost finished with it. She also layered the Masonite plates with evafoam and worked with Tushhar to integrate a FSR to one of the plates. The Z-shape now has their corners cut off to let the FSR fold properly. The Z-shape also sandwiches the FSRs and is still responsive to footsteps. The plate is nice and firm to step on as well. This will be further demonstrated in the Interim demo.

On the other hand, Caio and Tushhar worked together to test and connect the plate to the game. The Arduino file was tested and modified to work properly with the game. One of the important issues we took care of was the button held down being read as several inputs together. This often messed up with the combo as even brief steps would register as multiple hits of the arrow button. This has been accounted for now. However, it may change if we consider adding holding down arrows as one of the game features.

According to our schedule, we will likely need at least 1 more week in the buffer period to construct the mat and make the pause screen + high score input screen. Caio and Spandan will also work on integrating their menu screen and game screen together.

Tushhar’s Status Report for 04/02

For this week, I was able to work further on the plates of the mat and have the Arduino communicate with the python program. This was especially the focus as it also allowed to have something ready to show for the interim demo.

I was able to laser cut the files from last week. We have decided to use Masonite as the material for our plate and Z shape. Furthermore, our discussion with the professor and TA helped me realize that ends of the Z-shape could be left open to allow the sensor to fold. The files for laser cutting will be adjusted accordingly.

Fortunately, the Arduino Leonardo with headers arrived at the start of the week. Not only did that allow me to test the Arduino program but also integrate it to Python programs with the help of Caio. The testing was first done with lever switches replicating the different arrows.

This testing helped me find out errors and fix my Arduino file. Once it was working on the Arduino Serial Monitor, we tried it out with Caio’s game screen and made further changes to the Arduino file including accounting for holding down the button and setting thresholds. The new file and picture of our testing is down below.

https://github.com/CaioA1516/Capstone/blob/main/ardToRaspPi.ino

Lastly, Spandan and I were able to make one plate integrated with the FSR. We have tested it with Caio’s game screen and will have it ready for the Interim Demo. In terms of progress, a good amount of work was done this week. Since I wasn’t able to make the circuit layout this week, I plan to make it next week. I will also laser cut pieces for rest of the mat, as well as get started on soldering some FSRs.

Tushhar’s Status Report for 03/26

For this week, I was unable to continue to test the Arduino program with the Python minigame as the Arduino Leonardo board we ordered has still not arrived. However, the materials for the mat arrived. Therefore, I was able to work on some of the things we need for that.

Upon discussing some points on what we need to do for the mat, one of the first steps that we need to get done is laser cutting the correct plate shape and size, as well as a Z shape for the FSR. I was able to take measurements and model it on Solidworks. The pictures below shows what I have been able to make so far.

The second picture is the Z shape. The following 3 pictures is the Z shape broken down into pieces so that it can be laser cut more easily without waste. This was an informed decision. Using a whole 1 ft by 1 ft board per Z shape would not only waste a lot of materials but also be expensive. Breaking it down eliminates this issue. Since this is a busy week for me, I wasn’t able to do more. However, I can make much more progress now with the mat materials here.

Next week, I am aim to laser cut the pieces in the picture above and test the configuration of the mat with the necessary layers just for one square. I will also make a layout for the wires in the circuit layer. Furthermore, I am hoping to test the Arduino file when the Arduino Leonardo arrives. Any other things I will do will depend on further discussions about building the mat with my team.

Tushhar’s Status Report for 03/19

Since the last report, I was able to further test the sensors and work on Arduino communicating with Python.

In class, I was able to take some measurements with the help of my teammates. We tested the viability of bending the FSR into a Z shape. The circuit we used was similar to the one in the last status report.

The above image is a screenshot of the Serial Plotter from the Arduino during the measurements. The peaks represent taps by the foot on the FSR, while the plateau represents keeping the foot there for a period of time. The results seemed to be quite reliable. More details about the results are discussed in the team’s status report.

The next thing I worked on was the Arduino file which would relay the values from the FSR to the Python file. Caio showed me a really good resource which showed how analog values could be mapped on to keyboard buttons. Registering FSR hits as keyboard buttons would make integrating the game much easier. Using that file as a reference, I was able to write Arduino code that should work for our purposes. The code is in the following link.

https://github.com/CaioA1516/Capstone/blob/main/ardToRaspPi.ino

We were going to test it with 4 simple buttons and the minigame that Caio developed. However, we found out that Arduino Uno doesn’t use the Keyboard library. We have taken steps to solve that issue which is described in the team’s status report. Once the Arduino Leonardo with headers arrive, this code can be tested and modified accordingly.

The next week, I should be able to further work on this once the Arduino arrives. Furthermore, I will get very involved with the construction of our mat once the parts arrive. I believe I am one week behind schedule due to not having ordered materials for the mat earlier. However, there should still be time to make progress on that in the upcoming weeks.

Team Status Report for 02/26

This week, we divided up the Design Report into sections amongst the 3 of us. We also made sure that we know and have all the content we need respectively to work on the report. We have been and will continue to work on our sections individually. Our aim is to finish it by Tuesday night. Then, we will combine and format the report on Wednesday in order to submit it before the midnight deadline.

We also are close to keeping up with the schedule, both individually and as a group. While working on the design review presentation, we made some changes to the schedule. While the majority of it still remains the same, we accounted for Spring Break and the tasks we have completed so far. Furthermore, the new Gantt Chart is much more readable and easy to understand. Of course, the tasks delve much deeper in contrast to the few words shown in the Gantt Chart.

Some important changes may come to our system in terms of what and how many FSRs we use. Based on our talk with the professor and TA as well as results reflected in Tushhar’s testing, our initial plan of using 2ft long FSR in a circle or Z-shape may fail. We do have a mitigation strategy for it where we use smaller but more numerous sensors per square. Further details will be discussed and flushed out in the week to come.

We also plan to finish our tentative Bill of Materials by next week, and so we will order parts for the construction of our mat within the next two weeks.