I was just glancing over the timeline for developing our “Safety Timeout Feature”, and I believe that my group may have overshot how quickly we could have this plugin completed. Although the plugin is very simple in theory, I have never worked with a project quite like this and I have ran into several difficulties. This does not mean that I am giving up, I would just like to revise the timeline that we created.


 

Our Previous Timeline:

Overall: The Safety Time Out Feature will consist of creating a plugin that completes the aforementioned request. It will be completed by March 30, 2016. The plugin will consist of 4 different aspects; a user interface that creates a box for the users to enter the time, a timer that sets off an event when the entered time is up, an event that results in checking to see if the printer is inactive, and if the printer is inactive a function that shuts off the temperature to both the nozzle and the hotbed.

Goals:

         March 6: A box that allows users to enter a time (frontend) and allows the program access to that time(backend)

         March 13: A timer that responds by calling an event when the specified time is up

         March 20: An event that checks to see if the printer is actively printing returning True or False

         March 27: A function that shuts off all temperature actuators depending on the Boolean returned by the event


However, the complications that we ran into were plenty. Our group as a whole has not been able to meet during the class time more than 3 times in the past few weeks which means our communication has suffered. A new member has joined our OctoPrint group, so one of the days was spent getting them up to speed. We ran into trouble setting up our plugin using the cookiecutter template used by octoprint, and I scheduled us as working through spring break, which we should do, but I know that I will be unable to meet with my team.


 

A more realistic timeline:

Goals:

         March 15: The plugin tutorial successfully completed

–         March 20: A box that allows users to enter a time (frontend) and allows the program access to that time(backend)

         March 25: A timer that responds by calling an event when the specified time is up

         March 30: An event that checks to see if the printer is actively printing returning True or False

          April 5: A function that shuts off all temperature actuators depending on the Boolean returned by the event


This timeline will allow us to complete the plugin tutorial over spring break and convene ready to move on with completing the plugin.

Aside: I wrote this post over spring break (March 7, 2016). However, I had no internet access so I went back and changed the date after I was able to publish it.