With the research completed, the final presentations over, and the start of a new school year fast approaching, it’s time to reflect on the ups and downs of this summer and set new goals moving forward.
First, I would just like to say how happy I was with the program as a whole. I was not expecting to make the sort of progress that I did, and was able to come away not just with a good research experience, but also with a solid deliverable — and more than enough substantive material to fill a two minute elevator speech. If you had told me in April that I would be able to answer the “What did you do this summer?” question with “I built a completely autonomous process for a 3-D printer to accept new jobs via email,” I wouldn’t have believed it. Ten weeks ago, the complexity of automation was barely on my radar (I wrote it off with one sentence in my first blog post — “Week 6: Add wireless capability to FL-Sun7 3D. This can easily be done using a Raspberry Pi and the open source software Octoprint”), and I had been more focused on improving the temperature sensors on my 3D printer. While this could still be in the cards for the future, Jonathan’s work this summer is what really allows high quality prints, and it seems to me that my process will serve best for rapid, remote prototyping of ideas. In fact, Jonathan, Ryan, and I’s work all proved to be much more interconnected than we all had initially thought. Our research this summer laid the groundwork for a future in which someone could, with minimal effort, use a drone to capture and create a 3D model of any subject (Ryan’s work), rapidly prototype a print of that model remotely (my work), and then print it later as a high quality resin model (Jonathan’s work). The exact workflow for this is still a little ways off, but it was awesome to see the flashes of brilliance from everyone in the group that signified how close we are to something like that.
We also learned the importance of remaining flexible, yet motivated. The focus of my project might have changed three or four times throughout these ten weeks, but I never at any point felt that I wasn’t making positive progress. Proper documentation, as practiced in things such as these blog posts, serves to prove to oneself just how much as been tried, even if not that much as been accomplished. We were able to easily hold each other accountable, and exercises such as the biweekly lightning rounds with the DSSF scholars helped to serve as benchmarks for our progress. The occasional joint workshop, while not always catering specifically to our needs, also helped to mix things up and prevent monotony.
Most importantly, we gained experience conducting independent research. I never felt as though I was being watched during this program, but instead I was decidedly aware of the wealth of resources available to me should I need them. Upon encountering a problem, the process usually went like this: First, Google (duh). Then, ask coworkers or our friends in IT. If that didn’t work, we always knew we could go to Eric or Sharon and receive further guidance. It is impossible to understate the importance of being able to solve your own problems.
On that note, I should probably take note of what I accomplished in my final week. I spent a long time trying to help Jonathan set up his new kit (which I’m sure he will go over himself), and we also set up a dedicated Raspberry Pi for him to test configurations on PLA prints. In my research, I did manage to implement the solution to a problem I concluded with in my last blog post — allowing the user to cancel a job mid-print — although not in the way I had originally hoped. Due to the fact that I only had one touch screen device, I decided to change my application to work primarily with a keyboard for ease of use across devices as the program came to a close. The user-program interaction now goes as follows:
- The user sends an email, containing a .stl file, to the email address I have set up.
- The handler program notices a new email, and checks the sender’s email address and their secret code against the database, also verifying that there is an attachment present of filetype .stl.
- After passing the required checks, the handler creates a new job in the database, and assigns the job to a vacant printer.
- The node program notices that a print job has been assigned to its own printer id, downloads the correct attachment from the email, slices the print, and starts the job, updating its progress online as it goes.
- Should the user wish to cancel the print midway through, they press Control + C on the keyboard connected to the RPi that is processing their print. In the future, this could be done remotely.
- If the print is cancelled, the program asks the user if they would like to re-attempt the print. If the answer is no (done through keyboard input), both the .stl file and the job in the database are disposed of. Otherwise, the print is re-attempted as normal.
- If the print continues to completion, the node waits for the user to retrieve the print off of the bed. Once it has been retrieved, the user lets the node know by inputting the correct command using the keyboard.
- Once the node registers that the completed print has been removed, it disposes of the .stl file and removes the job from the database, signaling to the handler that it is available to accept a new job.
This process generally works flawlessly, and I was able to demonstrate it fully during my final presentation on Friday! However, there are currently a few drawbacks. Occasionally, the handler or the node briefly loses connection, which causes connections to the mail server or database to fail. I have implemented try/catch blocks to attempt to retry the connection when this happens, but for some reason it doesn’t correctly re-establish.
Continuing Research
I would certainly like to continue working on this project, and I have been presented with the opportunity to do so by using the project as my senior capstone project for Computer Science. Were I to accept this opportunity, I would likely take steps to implement a number of new features into the program, such as:
- Working with IT to allow a real login process, using a Gettysburg ID
- Allowing remote upload of files via the website
- Implementing webcam support to watch prints as they complete
- Alternative status alerts on prints, such as email or SMS
- A robust scheduling system to assist with the timing of print jobs
- Training system to show how to build and maintain the printing setup (already underway)
To conclude, I would just like to repeat how lucky I feel for being selected to this program and how proud I am of my own results and my peers’. This is the beginning, not the end, of my work in this area.
James






























