Posted on

Group Status Update for 10/24

Risks

  • Currently, one of our members has been MIA for weeks. He is tasked with the piece movement subsystem of the project and we are not entirely apprised of his progress, we only know he has been attempting to keep track of the linear actuators he ordered, but no further details on his progress. As time passes, the risk that the piece movement subsystem will not be complete becomes higher, and thus, to mitigate this risk, we will soon have to decide whether to cut this part from the project and proceed without him or not. If we were to do this, we would devise some way of informing the user where they need to manually move the opponent’s pieces to.

Changes

  • Our design is mostly the same, with the changes detailed in our Design Review. The overall design remains the same, but the details of implementation for some parts have changed. In summary, they are:
    • Now modifying existing chess pieces instead of 3D-printing our own
    • Using magnets to orient the pieces on the board correctly
    • Smaller board size to accommodate the length of affordable linear actuators.

Schedule

  • A snapshot of our schedule can be viewed here.

Progress Pictures

  • Multiplexer Testing Circuit:

Posted on

Danié’s Status Update for 10/24

This week I have been working on the detection circuit since the multiplexer arrived. I am able to loop through the inputs and will soon scale it to use all 16 inputs, adjusting the resolution as needed. Once the 16-piece detection circuit is working on the breadboard, I will begin construction of the board top or construction of the pieces, depending on when the pieces ordered from Amazon arrived. I mention wooden pieces because, as of our design revision, we will now be modifying wooden chess pieces instead of 3D printing our own.

Below is an image of the arduino console detecting input from 3 “pieces”, where 14 and 15 were set to GND and 16 was set to an arbitrary voltage <5V:

I am behind our original schedule but proceeding well into the adjusted schedule.

Posted on

Brandon’s Status Update for 10/17

This week, I mostly worked on getting the socket.io library to work with the webapp and preparing for the Design Review. While the sockets are not completely functional at the moment, I am hoping to get it working by early next week, and then working on SerialPort for the remainder of the week.

Posted on

Group status update for 10/10

Current risks:
  • Unforeseen delays due to the state of the world right now (re:pandemic) and due to us all being apart from each other have caused some shifts in the order we tackle the tasks we scheduled out, and there may be other delays to come that we cannot predict. We’re managing this by making better efforts to stay coordinated and in-sync as a team, so that if something happens to one of us, we can quickly adjust the project in response.
Changes:
  • We’ve switched from the actuator we initially were going to procure to a cheaper one. This one does not come assembled, so that is added time spent on the project, but it should be simple to build and saves us around $200. This actuator, however, has a smaller travel distance, and will result in a smaller board. As a result, the pieces will have to be made smaller than usual chess pieces, but having normal-sized pieces was a preference we had, not a strict requirement. We chose to have more freedom and flexibility in our budget over having bigger pieces.

 

Posted on

Danié’s Status Update for 10/10

This week, I’ve procured everything necessary for the detector circuit minus a multiplexer. While I wait for that to arrive through the mail, I’ve been learning how to use the Dremel DigiLab 3D Slicer software to model our own pieces and print them in TechSpark. This is a simple circuit diagram of the detector circuit:

So far I’m still on schedule, and by next week I hope to have both the 3D printed pieces and a functioning prototype circuit.

Posted on

Brandon’s Status Update for 10/10

This week, I learned how to use node js and express, including using libraries with them. I was able to use chessjs and chessboardjs to make a working chess game which also prints information about the game’s status as shown at the bottom, so I am on track of schedule.  I hope to get the game working with sockets for next week.

Posted on

Group Status Report for 10/3

Current risks:
  • The current risk is we have taken a bit long to acquire parts, and are now a bit behind schedule. We are managing this by doing the things we can do without those parts ahead of time, this way we’ll still be on schedule.
Changes:
  • We have had to change the specific actuators we were planning on using because of the costs, although it has taken time away from us in the form of extra research. Going forward we’ll keep this lesson and mind and research something thoroughly before deciding on it.

No changes to the schedule have been necessary.

Posted on

Danié’s Status Update for 10/3

This week I settled on working with an Arduino and have gotten reacquainted with programming it so that once the circuit for detection the pieces is wired up, it will be easy to fine tune. 

By next week, I hope to have that circuit built and tested and get ready to move onto the board top.

I am still personally on-schedule, but I will not be if I don’t pick up my pace and meet my expected deliverables for next week.