Yuma’s Status Report for 4/6

Accomplishments This Week

We were able to show the interim demo this week on the real software, and it was pretty good. Afterwards, I was able to keep developing the software so multiple scanner modules would be able to plug in. We had some issues where server closes were not detected by the client, so we fixed it by spawning reader threads. One problem I ran into was that when the scanner module is shut down & restarted, the unique identifier I was using would change. This would make the central computer think it was a completely different scanner module joining, rather than one that was already in the system. I’ve been trying to fix this, but at least for the same localhost, restarts after shutdowns are working well.
Demo is viewable at this link: https://drive.google.com/file/d/1JqQbArqMs0_zuo20xcsWn8leIyXCxjUR/view?usp=sharing

Project Schedule and Progress
Progress is strong, and I have accomplished what I expected this time last week. I expect to contribute less during Carnival week due to Booth commitments, though. I have yet to integrate the UI and the OCR, as these parts are handled by my partners and these are still not completed.

Goals for the Next Week
I hope to find other ways to distinguish between the scanner modules even when they are restarted. I hope to also implement a C-ACK for the items being sent, as ACK’ing each item is a lot of messages when a CACK for the most recent item could ACK all the messages behind it as well.

Leave a Reply

Your email address will not be published. Required fields are marked *