Tag: Status Report

Tag needed for posts for status reports.

Sophia’s Status Report for 02/22/2025

This week, I added in a check for different OS to the scanner controller program. So far, it correctly recognizes and adjusts the scanning context based on the OS, since NAPS2 uses a different scanning context object for each OS. I also added a “scans” folder to save each scanned .png file to. Each scan process/cycle will create a new scan folder (in the format of scan0, scan1, scan2, etc.) in the scans directory in order to keep scan cycles cleanly separated. Each scan .png file will be saved in its respective scan cycle folder (in the format of scanPage0.png, scanPage1.png, etc.). So, for example if we take 3 scans of an object, then you could find scanner-controller/scans/scan0/scanPage0.png, scanner-controller/scans/scan0/scanPage1.png, and scanner-controller/scans/scan0/scanPage2.png to send to the image processing component. I would just need to make sure the program knows what scan number it is on, essentially passing a scan ID between functions.

Additionally, I  implemented an exception for if there are no scanners detected. I also did more research into the NAPS2 documentation and how to properly connect the scanner. I usually use WSL to run code that’s stored on my Windows OS filesystem and I can run the code fine through Windows, but I think I’ve found a way to get the scanner recognized in WSL too. So, I believe I would be able to test both the Windows OS and Linux OS environments from my laptop alone. Yon would just have to test the Mac OS version.

The scanner I ordered arrive. Next week will begin testing communication integration with it. I am currently on schedule.

Team Status Report for 02/15/2025

Started working on our individual components, specifically creating the device model in CAD, setting up the software project, and looking into more research for the signals processing. We decided to use a suction cup as our friction tip and set up the hardware and electronics necessary to use it in our first prototype. Instead of testing two different prototypes with different manipulators, we can simply test with the suction on and off.

We have ordered all parts that we believe will be necessary at the moment. We should get all of them by next week and be able to start prototyping and testing with them. The 3D printed part we’ll need is also designed and can be printed anytime.

Our next steps are to progress on our individual tasks to keep on track before attempting and testing integration of the components.

Theo’s Status Report for 2/15/25

This past week I prioritized finishing the manipulator design and ordering the parts. I also finished the CAD mockup, including the first prototype of a 3D printed mount for the electronics. It will freely move vertically on top of the manipulator to account for objects of different heights/thicknesses. I’ll 3D print this mount and test it once the ordered parts have arrived and the rest of the manipulator is put together.

Though I’m still behind on my tasks from the roadmap, a lot of future time was allocated to debugging the hardware, characterizing the working prototype, and designing a new version with a suction cup manipulator (instead of just a friction tip); this time may as well be slack time that’s instead used for this prototype. We’ve gone ahead and ordered the air pump, tubing, and suction cup with the rest of our parts. The suction cup is the same material and size (silicone for high coeff. of friction, 13mm diameter to fit behind a dime or similar coin) as we would’ve made the friction tip, so we will simply test the prototype with and without activating suction instead of needing to build an entirely new prototype/add-on. I believe this will be a massive time save, and don’t foresee any issues with the current design. I’ve uploaded the solidworks assembly+relevant files to github.

Besides working on the design and prototype, I’ve worked with my team on the design review presentation slides. I’ll be presenting on either Monday or Wednesday, and the tentative plan is to finish a draft early enough tonight or tomorrow so that our TA can look it over and give advice.

Sophia’s Status Report for 02/15/2025

I created a branch in GitHub for the scanner controller software. I also created the dotnet project and added the universal scanner NAPS2 library which took a lot longer than you’d think, the dependencies felt never-ending. I never worked with dotnet either that I remember, so figuring out projects and solutions was a difficult time. Additionally, I added simple scan sample code to ensure all needed libraries of NAPS2 were correctly identified.

I also worked on design presentation. I edited and added in most of the slides needed for this sprint and filled out my own relevant software sections, ensuring that the needed topics were covered in the presentation slides.

My next steps are to create mock data and unit tests for the scanner controller code to ensure the simple single scans are working before moving on to scanning multiple times with a delay between.

Yon’s Status Report for 2/15

My main focus this week has been finding additional literature on photometric stereo, and and beginning to parametrize the work’s findings for our use case (orthographic, fixed reflection angle with a variable number of rotations). I also supported my teammates with purchasing components, reviewing mechanical design, and performing cost-benefit analysis on certain design choices (especially to do with modularity).

Next week I’ll have to finish up parametrize the math and translate that into code. I’ll also help test the manipulator subsystem by analyzing the alignment of the output images.

Theo’s Status Report for 2/08/2025

My work this past week consisted of helping with the proposal presentation and drafting a prototype + its CAD model. I was responsible for the hardware requirements, specifications, and solutions in the proposal, and helped with edits to the entire presentation in the time leading up to presentation day.

The CAD model is a few days behind schedule according to the roadmap. This is mainly due to me wanting to render the functioning linear actuator/lead screw, rotation motor, and microcontroller. I am still working on this model and have additional free time this week to catch up. The current prototype will be built out of 1-inch T-slot aluminum extrusions (CADing done with parts from 80/20), using an ESP32 dev board capable of operating a motor driver and at least one stepper or servo motor. I am still weighing the pros and cons of a linear actuator vs a manual lead screw, as well as a stepper motor vs a servo motor. The circuit will likely need an external power supply to power any of these motors, since the traces on an ESP32 won’t handle the power necessary to keep the motor powered over an extended period. This should all be resolved and the parts can be ordered by the end of next week. Though this places the hardware behind schedule, I am not worried. Assembly will be simple and can be done the day the parts arrive, and all should be back on track after that; the characterization task that comes after assembly should really only take a day or two, and the programming itself will be simple motor control. There is plenty of slack time in these first few hardware tasks that allow for this setback.

I’ve started on a basic arduino program for controlling the ESP32 and testing the stepper motor system’s accuracy. One of the first things we’ll be testing once we have the ESP32 is our ability to send it commands from our project’s software. If the arduino IDE/language doesn’t work, MicroPython is the next most likely route of hardware programming.

Team Status Report for 02/08/2025

Our team created our proposal slide deck and presented it. This helped us flesh out more details of our project and how all of our parts will interact as a system. We considered how user-friendly we wanted the process to be, the maximum amount of time it should take to scan and generate a 3D model, and the scope of what objects would be scannable. We realized some limitations that real world conditions would present to us. We will have to test how much noise will occur from outside lighting and other real conditions with the flatbed. We will also consider different options for our mechanical arm based on how either rotating with a felt tip on a glass surface or electro-adhesion would work with different materials and geometries. Additionally, we need to see if it’d be necessary to place anything under the scanned object, such as film, to prevent scratching or if it would help/hinder rotation of the object.

Next week we plan on looking through the inventory list for components of our manipulator, and placing orders for a flatbed scanner and potentially any manipulator parts that we can’t find in the inventory.

Yon’s Status Report for 02/08/2025

This week I mostly prepared for our proposal presentation. This meant I worked with my teammates on coming up with our semester’s Gantt chart based on my assessments of my own responsibilities and the dependencies we have on each other’s work. I believe we are on schedule, as we have just created the schedule.

Next week we plan on placing an order that is relevant to all of our subsystems – the scanner – so I plan on providing some input as to the purchase and looking over my teammates recommendations and needs. I also plan on getting started on parametrizing the math from V. Skala and R. Pan via the parameters we plan on optimizing.

Sophia’s Status Report for 02/08/2025

Most of my work time this week was spent on preparing the proposal presentation. Including fleshing out requirements and quantitative measures for it, diagrams, and creating the slides themselves. I worked with my teammates over calls to flesh it out. My team all agreed that I would be presenting the proposal presentation. I spent time practicing to make sure I explained the project in a clear manner, not just directly reading from the slides, and asking my teammates about their parts of the project so that I had a thorough understanding of all of the elements.

Decided on scanner and library – I did research on what software libraries could potentially work for our project, particularly what libraries were available to command scanners. I found one called Naps2 that should work for any popular brand of scanner. I also decided on a scanner to buy, it’s a 4800 dpi Cannon scanner. 4800 dpi is plenty of detail for the scans, Cannon is a very common brand, and the scanner is small and shouldn’t be too difficult to move or store. It’s also less than $100, which leaves plenty of budget for materials for the hardware of our device.

My progress is currently on schedule. Next week, I will start into using the Naps2 library and creating the software that would interact directly with the scanner sending commands, would receive those scans, and then send them to Yon’s image processing software. Depending how far I get, I could even start unit testing it. Hopefully it will be in a decent state by the time the scanner is ordered and arrives for practical testing.