Create Backend

[yldbouk]

Since there are no options that can do exactly what we want, I believe the easiest solution is to create a backend that relies on other applications. Here is a rundown on what the backend might do. A script monitors the print db for the first queued job. When a job is first in line, it checks to see if the printer is ready to print something through this solution. If not, wait. If it is ready, slice the file, then begin printing it, checking the status every few minutes. If it errors, send a notification through some solution, like slack or discord (discord allows for webhooks, so it might be easier). When it is done printing, set the job status as needs processing. Notify the requester and the admin (we can notify the user by checking the state of their print and displaying a banner). When it is done, the admin would ready the printer for a new print, and set the job as done. Repeat.

Issues with this method:

• if a job is outgoing, it will make every other job wait for the job to be done, even if the next job is on a different printer.
• that’s it so far.

[yldbouk]

@pro6dog said:

The software can be found here at this Link. The goal is to set up on the laptop/server.

[yldbouk]

@pro6dog said:

This needs to be in place to automatically take the files that are in the "Queue" from the website upload. Then the converter will automatically place the new .gcode into the correct queue for that printer.

[yldbouk]

@yldbouk said:

This can be done with a manual backend component. The component would access the db to find the queued job and its file. It would then copy it over to a workspace, and slice it through a CLI solution. Then, it’ll look at the assigned printer, and place the sliced file in the corresponding queue.

[deanmand]

Pronterface does work with 3d printer. Confirmed.

[yldbouk]

Closed for now. Saved for later.

[yldbouk]

From #39, @pro6dog said:

The purpose of this is to add settings on the website to control the slicer so the user can choose to add a raft and or supports to their object. This information can then be fed to the slicer so it can determine whether or not to print with a raft and/or supports.

[yldbouk]

From #32, @pro6dog said:

A solution must be in place to print the .gcodes in the queue on the appropriate printer.