Author: chunglee

 

Risks

We’re currently assembling the board by taping the sensors to the acrylic board. We had to take out the wires so hopefully rewiring everything won’t result in anything that affects the sensors. We had some issues powering the LED’s so we were unable to test them thoroughly. The LED’s are currently under the power limit but we are trying to be as careful as possible. We also haven’t tested everything together so there may be issues with full integration, but we have tested everything in isolation carefully so we don’t expect any major problems.

Changes to System

None.

Changes to Schedule

None.

Personal Progress

I was able to get the smart timer working. It runs a separate thread that can be triggered and stopped by the main chess program. I am looking at how to integrate it in the chess logic. I have also started looking at networked play. I have a plan on how to implement it, but we are limited on time so I’m not sure how far we’ll get.

Schedule

I am on schedule to finish everything on time for the demo, except for networked play.

Deliverable

I’m working on whatever I can so that we can be ready for the Monday demo. I think we will have a single board ready for gameplay on demo.

Personal Progress

Austin and I were able to finish the sensor circuitry and test it. We were able to get it working for the demo. We are currently trying to help finish the gui software by learning python chess.

Schedule

We are behind schedule but I think if we work hard all week, we should have a finished board and software before the demo.

Deliverable

The main focus is definitely the software. We are trying to get it to a state where we can link the sensor input to the gui for basic gameplay.

Risks

The biggest risk is that integration doesn’t go well. We are making very good progress on all our major components. The squares are ready and being assembled on the board, the gui is coming along well, and the led’s are very close to being set up. There might be issues that we might not be aware of because we were working on components in isolation. Luckily, we have a clear division of responsibilities for all the components, so we should be able to isolate issues and resolve them quickly.

Changes to System

None

Changes to Schedule

None

Personal Progress

I’ve been working on the led’s and the smart clock. I was able to run some simple test programs on both devices. We will have the led’s working for the demo but the smart clock might still be a work in progress. This is ok because the smart clock isn’t essential to the game overall. It will be ready for the final demo. I also finished the code for reading the data from the sensors and passed it off to David so that he can integrate into the gui for gameplay.

Schedule

I am on track to be ready for our demo next week. The sensor code is ready, as well as the led’s so we should be good.

Deliverable

By next week I hope to have the smart clock working and a solid plan for how to network the two pi’s.

Personal Progress

I’ve been looking at how we want to use the 7-segment display for the smart clock portion of the project. I have a good idea of how to connect the display to pi, and run a basic clock program. However, the complexity in the functionality comes mainly from how the clock will be triggered and stopped based on the game play. We want the clock to start as soon as the other player sets down their piece and stops their turn, and for it to stop when the player puts down their piece, signaling the end of their turn. There are still some design decisions that need to be finalized on the core game logic, and this will determine how and when the smart clock will be called. I am currently working with David on integrating the sensor software with the core game logic, and I will also be working on getting the 7-segment display connected to the pi to run basic programs so that we can integrate it quickly when the core game logic is finalized.

Schedule

We will have the integration of core game logic and sensor software done by this Friday, and the smart clock functionality done by the weekend. I hope to start looking at the connected pi feature for remote play over the weekend as well.

Deliverable

We will complete integration of core game logic and sensor software, and the smart clock done by the end of the week. We will have a solid plan for connecting the pi’s as well.

Risks

The biggest risk is the software. David is a little more behind schedule than we thought, and it will take time for him to translate his ideas into code. Chris has been helping David prioritize his tasks so that we can have some tasks accomplished by the end of the weekend. These include finishing a basic gui, and getting the basic game logic as move validation working. We are working hard to make sure that the software gets completed on time, but the lack of progress on the software side is definitely the main risk to the project.

Changes to System

None.

Changes to Schedule

We are behind schedule mostly due to software. We were supposed to begin testing of the software this week, but that will have to be pushed back.

Personal Progress

I was able to get the pi to sweep across several sensors with a mux for the demo. Professor Mai asked us to figure out how fast the pi can sweep through the sensors so I will work on that next week. We did encounter some inconsistency in how the mux worked during testing before the demo. Sometimes it would work and other times it would just read garbage from the sensor. I will try to solve this problem by figuring out how fast the pi can read from the sensors and make sure that we are giving the system enough time to switch between inputs and read correct values so that we don’t run into this issue in the future.

We ordered the 7 segment display and a new pi, so I will also being working on the smart clock and connecting the other pi for remote play as well.

Schedule

I was hoping to start looking at connecting the two pi’s right now but as long as I start next week, we will be able to stay on track.

Deliverable

I hope to have the time measurements for reading from the sensor done by next week. I also hope to have the code from reading from the full array of sensors done because I only wrote code for the smaller array of sensors for the demo. I will also start looking at the smart clock and connecting the two pi’s.

 

Personal Progress

I’m currently working mostly on the demo for next week. We received feedback that an appropriate demo would be a small grid and moving pieces that could be detected by the sensors. This past week, we were able to sense inputs from several sensors and determine the threshold that represented if the piece was present or not, along with which side the piece belonged to based on the polarity of the magnet. I’m still working on modifying my code to interpret the changes on the board in an array form and output a string that displays which piece was moved. A stretch goal for the demo would be to integrate my software with the gui, so we are working on that as well.

I have also started looking at methods for connecting the two pi’s. I’ve been running into issues configuring static ip addresses so I will continue looking at this over the next few weeks.

Schedule

Our demo is scheduled for Wednesday, so I am trying to get the pi code to translate the sensor inputs to a readable output by then.

Deliverable

For the demo code,  I want to make sure that it can be scaled for the final demo. So I want to create a standard method of switching inputs that can be modified for an increased number of inputs.