Status Report for Mukundh Balajee on 04/29

This week, I focused on ensuring our PCBs were fabricated correctly and properly connected to the 9th MUX.  I also helped ensure we can have our PCB neatly placed and positioned within our encasing, to provide minimal clutter and easily accessible. I was also able to run a number of tests on our software systems, to ensure that the move and board legality checker has minimal latency (<25ms) and the sub-system was able to catch all illegal board states and moves. I was able to test the board components for accessibility (braille, piece identification, ease of understanding the board), and decided to modify our braille tiles to be larger to ensure clear comprehension by our blind users. I was also able to provide that our button and speaker circuit work accurately and ensure that they can be powered by our RPi/Arduino, without affecting the performance of our system. I was also able to run some power tests on our button and speaker circuit while keeping in mind the voltage requirements of our PCBs. Finally, I was able to determine the latency for communication between the Arduino and RPi (<80ms), and also the vocalization system(~<500ms). I was able to ensure that our sub-systems were within their individual latency requirements for MVP and plan to reduce latency post-MVP.

We are slightly behind schedule because of a delay in the arrival of our magnets and PCBs, however, we plan to finish the integration by this weekend and start our system tests and integration tests next week, before our final demo.

By next week, we hope to have our project completely done and ready to be used!

Mukundh Balajee’s Status Report for 04/22

This week, I was able to help Edison solder the PCB. I focused the majority of my time on the piece detection logic, by choosing accurate magnets and magnetic strengths for each piece. After that, I was able to write Arduino code to generate a move based on the number of sensors we had (one fabricated row). This way I was able to generate a move and send the move over to be validated and sent to lichess.org.

We are currently slightly behind schedule because of delays in our orders for PCBs and magnets. However, we have been able to make significant progress with fabricating our PCBs and have at least a semi-functional board by this weekend.

This next week, I hope to be able to integrate the MUX logic with our existing software logic and connect the PCBs. I also hope to be able to attach the speaker to the board and help complete the board to make it a functional product. This week, I also hope to be able to perform as much testing as possible to ensure the integrity of the product.

Mukundh Balajee’s Status Report for 04/08

This week, I ensured communication between different systems worked as expected. This includes connecting our Arduino, and RPi to communicate with each other and information flowed accurately between the two systems. I was also able to manufacture our pieces and print all pour components required for blind users to play physical chess.

Currently, we are slightly behind on our schedule as our PCBs had to be re-fabricated and re-ordered. This delay could potentially affect us, however, I have been able to simulate the testing script to ensure that our current system works correctly, so that we would only have to establish communication between the physical board and the online platform.

Regarding testing and validation, I have been able to add error logs in my software scripts to ensure I can catch any error by monitoring the errors.log file. Since we do not have our hardware components yet, we decided to simulate inputs like it would be made by a user, to play a game of chess with an online player. We also have been measuring our latency goals as we develop, to ensure we stay within our target. We have been user-testing our pieces to ensure our blind users can recognize pieces correctly, and identify the coordinates with the braille notation.

For next week, I plan on finishing the fabrication of our PCB and having our PCB powered, and connected to our software system. I also plan to ensure we have a fully functional button system for starting a game and performing other functions required for the game of chess, and also make sure we have our speaker embedded in our board.

Mukundh Balajee’s Status Report for 04/01

This week, I was able to finish up our software module, upload our code onto the RPi and enable communication between arduino and RPi. Apart from this, I was also able to write arduino code, to help facilitate some sensor measurements and voltage checks for our hardware, before we pass data over to out software component. Apart from this, I was also able to write testing scripts for some of our scripts to help ensure optimal performance.

At the current rate, we are slightly behind schedule, however, we have our physical product in manufacturing, which would put us back on track to complete our project well ahead of time.

By next week, we hope to have a functional gameplay on the software side, and a proof of concept with at least 3-4 rows working, with the ability to detect different pieces and types of actions.

Mukundh Balajee’s Status Report for 03/25

This week, I was able to finish modeling all our pieces and print a couple out to test that their behavior with the magnet and sensor is as expected. I was also able to determine the magnetic strength required for each unique piece and have our order ready to be placed on Tuesday. I was also able to work on the Software side with Edison to help ensure our code functions as expected. I was able to make a script to validate a user’s move made on the board and pass the information along through various other checks and finally over to lichess.org. I was also able to work on our arduino code, to help read the output of the Hall Effect Sensor.

Currently, we have been able to stick to our schedule, by making progress over spring break, and are a little behind on manufacturing the board.

I hope to complete the manufacturing of the board by next week, and also upload our code into the RPi. We hope to have full connectivity barring our hardware. This will enable full gameplay from a software application.

Mukundh Balajee’s Status Report for 3/18

This week, I was able to test our Hall Effect Sensors, which arrived late.  I designed the circuit needed for each tile and tested out our magnets. I was also able to place the order for the magnets, on my own, to ensure it arrives on time, and we can decide our magnetic strength range for each unique piece. On the software side, I was able to help make our code modular, and separate it into different scripts. I was able to make major progress on the move validation, and integration with lichess.org. Our code currently has endpoints that can be connected to for full functionality. Once our PCB arrives and we can connect the hardware portion.

Currently, my progress is on schedule. I was able to catch up over spring break and keep our progress on schedule till this week. We have been behind on our hardware side, however, Edison and I have been able to catch up on a lot of the work on the software side of our project.

By next week, we hope to have our board laser cut, and PCB tested and ready for use. e also plan to have our pieces made (with magnets inside the piece and pegs placed at the bottom), and 3D print all the pieces. We plan to have some form of established communication between our board and RPi.

Team Report for 03/11

Currently, the delay in the arrival of our Hall Effect sensors, adds an extra time crunch to send our PCB out for fabrication as soon as possible, which would involve testing the sensors as soon as they arrive. Mukundh and Juan are currently learning how to use Autodesk and Eagle to help with PCB Fabrication, and they have also gone over their circuits to check for any theoretical flaws they were able to identify. We have moved our schedule around and worked on future tasks to help keep us somewhat on track.

We decided to get rid of an Arduino Uno, and instead just use an 8-channel ADC, as we realized that this was a cheaper option and did exactly what an Arduino Uno would do. This helps us use our budget for other purposes and be economically wise.

As highlighted in our individual Status Reports, for this week, we have identified some technical challenges which we would haveto overcome. For instance, Juan and Mukundh are learning how to use AutoDesk and Eagle, Edison and Mukundh are learning how to use an RPI as this is their first time using it, and also how to connect the RPito a web app and to the Physical Board.

Below is our updated gantt chart which takes into consideration the delays we’ve experienced with the delivery of our sensors. Due to these set backs, we’ve had to readjust the dates for sensor testing, as well as PCB fabrication – since our PCB will be based on the results of our testing.

Schedule

Mukundh Balajee’s Status Report for 03/11

For this week, I was mainly focused on assessing the different sections of our design report, to ensure we tackle every portion of our project with careful consideration. Apart from that, we were able to finalize our pieces and have them 3D printed for our first prototype. Our sensors are still stuck with the vendor, which has pushed our sensor testing off by one more week. We have been in touch with Quinn and our TA about this.

Currently, we followed a similar strategy to last week and moved our schedule around to account for the delay of the sensors. We got a head start on our web app, scripts that will run on the RPi, and also communication between the RPi and lichess.org. This has helped us stay somewhat on track with our schedule and get some future work out of the way.

Next week, we hope to receive our sensors, test them and send the PCB for fabrication. We also plan to finalize our board and the components we will be attaching to it. Apart from this, we plan to work on integrating the sensors and the RPi to ensure we have proper data collection.

After this week’s design report, we were able to come up with different subsystems required for our system, and we realized that we have some extra learning to do for PCB Fabrication, using an RPi and uploading scripts to it, communicating between RPi and web app and RPi and physical board. We plan on reading through datasheets for different components in our circuitry and on our board, to help us get an efficient circuitry and have correct connections and functionality.

Juan Mejia’s Status Report for 2/25/23

This week was mostly focused on the fabrication of the physical board tiles and pieces. I started designing the pieces from scratch, however Mukundh found existing 3D models and took over the work on Rhino. I designed a test board that has a 2×2 tile design to represent the black and white tiles( see attached picture). There was delay in the arrival of the hall effect sensors because we had to order new ones, so the unit testing that I wanted to do this week, didn’t get done. I have begun setting up the circuit for the PCB, need to call AutoDesk to ask for the correct library for the hall effect sensor.

This coming week I hope to finish 3D printing all the pieces for the board that we need for testing and finalizing the dimensions and design for the tiles and chess pieces. Once the hall effect sensors arrive, I plan on working with Mukundh to do the unit testing and finish designing the row PCB, in order to send it for fabrication. I also hope to get the micro SD for the Raspberry Pi, in order to set up the OS and connect it to our WebApp.

Team Report for 2/25

We currently do not have the parts for our circuit, so this has set us back and affected our timeline. We are currently looking at different circuit options to help finalize our circuit. We hope to be able to have our circuit done and ready for fabrication by the end of this week (the beginning of Spring Break) in order to fix any possible mistakes on the PCB as soon as we return from Spring Break.

We have updated our team work assignments to take into account the delay of our hall effect sensors and PCB fabrication. We also had a few miscommunications that lead to the board design and pieces not being printed on time. In order to account for our schedule changes we have moved things around in our gantt chart and prioritized specific tasks. The top priority for this coming week is PCB fabrication, the reasoning behind this was to match delivery time with Spring Break and begin testing as soon as we return. This coming week we have divided up the work as follows:

Edison: Finalize move legality script and  its respective testing script, finish web application board and lichess.org live game communication.

Mukundh: Unit testing for the hall effect sensors, adding braille notation to 3D designs, begin and finalize autodesk design for PCB

Juan: Finish the 3D printing of two board and piece design in order to test for the best configuration. PCB design. Also work on piece vocalization using Raspberry Pi/Arduino

We had no major design changes this week. We had to order new hall effect sensors in order to test on a breadboard, prior to fabricating our PCB. This lead to an increase cost of $16 for the unit testing. The vocalization change cost has not been determined as we might be able to get a free speaker for the Arduino in a kit that Juan has.

We updated our schedule to account for certain issues that came up. We ordered the wrong part, so we had to push our circuit testing by a week, and move certain tasks earlier to account for the delay. The updated schedule has been attached here.