Hello all,
We are interested in using Bambu Farm Manger as a solution for supporting a fairly large user base of engineers and designers in combination with a fleet of six H2D Pro printers.
We currently have the farm manager server deployed and have connected an A1 Mini to the farm as a test device since we haven’t put in the purchase order for the H2D Pro machines yet.
I think I understand the basic functionality of the setup now with this single printer and single spool of material (we don’t have an AMS for this A1 Mini). I still have some questions about how this all interfaces with Bambu Studio - especially when it comes to the AMS.
My first question is around the “queue”. It appears that you can upload files from Bambu Studio to the farm, and then create a task for each sent print job and send them to the same printer. You can then start a job, let it finish, clear the bed, confirm removal, and then start the next job (either from the printer interface, or from the Farm Manager Client). I don’t see any way to make the next print in the queue start automatically after the above steps are performed (without manually starting the next job in line)… Is my assumption here correct – there’s no way to automatically start the next job?
We have an aging fleet of UM S5 printers that DO allow for a first in, first out queue that starts automatically when the bed clearing confirmation is completed, so this will require some additional training (and etiquette) for the user base.
My second question is a bit more complicated. I am accustomed to using the cloud connection features of Bambu Studio and my account to allow me to use the “Sync Info” button in BS to update the available filaments in the AMS. My understanding so far is that with the Print Farm Manager, the manager client will show users what materials are present on each printer, but this info can’t be synced up with BS. I assume that this means that the users must manually create the H2D Pro printer instance in BS, along with the editing this printer configuration to include an AMS for each nozzle. Is it true that an assortment of materials will also need to be added to match up with the materials on a target printer in the farm?
We would mostly just be using Bambu PLA Matte in these machines in a variety of colors. Most prints wouldn’t be multi-material, but the ability to choose a preferred color would be helpful. Is the color selection option possible once you send the print job?
This step in the process seems like it would be the most confusing option for our users who may not be as tech-savvy as others.
As a side question, is there a better way of managing an environment where multiple printers and multiple users are present? Our IT department is very picky about the cloud connection, so it would be important to keep everything on our own network.
We even tried LAN-only mode with this A1 Mini and were able to add the printer to multiple BS instances (different users, not signed into a Bambu account on BS). However, there’s no way to send a print job to a machine that’s already printing, and it seems that there’s no enforcement of the clearing of the build plate. We are able to send a print job to this A1 Mini without confirming removal, and it happily begins another print job right over the top of the previous print job. This fact alone felt like a non-starter for us, and makes us lean toward the print farm manager instead. The inability to queue another print behind a running print job is another issue too, since our users are very much accustomed to this workflow.
I’m hoping I’m missing something here, so I’m hoping someone can chime in and either confirm my assumptions or tell me I’m wrong!
Thanks!