Spoolman - Filament Management

[PFarm]

@adamo000 You are welcome, for a fresh install I'd delete all of the Spoolman files. I run my Spoolman on an Ubuntu Server and point Mainsail to the IP address in Moonraker. Some members here run a separate Pi for Spoolman this way if something happens like in your case it is isolated from your Klipper install.

[claudermilk]

Huh, I hadn't noticed that but I see the same thing. Two different printers both with the same issue. As @PFarm mentioned, I have Spoolman running on a different server so both printers can use the same database.

[claudermilk]

Now that I've got both printers updated, I'm looking at this integration again. I noticed that I can once again see the filament type in the Fluidd interface.

Now what I want to do is be able to grab what the current spool is from Spoolman and use that in my macros. Right now I have my own variable stored of what filament type is loaded so my print_start can yell at me if I, say, have ABS flagged as loaded and I try to print a file sliced for PLA. Spoolman has that info, so why not use that? Anyone figured out how to get what the current spool info is from Spoolman?

[mvdveer]

Spoolman originally designed as utilising user permissions. This meant, if running a dedicated server, you had to be logged in, in order to get all the information from the server.  This is since changed, (since latest update) and spoolman is now enabled on a systems level - the server only needs to be up and running, no longer need to be logged in.

8 hours ago, claudermilk said:

Right now I have my own variable stored of what filament type is loaded so my print_start can yell at me if I, say, have ABS flagged as loaded and I try to print a file sliced for PLA.

I do not have any macro’s  specifically integrated with spoolman, but I do get a warning if the slicer reports ASA and I have a ABS spool as per spoolman. My slicer “Start GCode is:

START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single] MATERIAL=[filament_type] SIZE={first_layer_print_min[0]}_{first_layer_print_min[1]}_{first_layer_print_max[0]}_{first_layer_print_max[1]} INITIAL_TOOL=[initial_tool]

Although I must say, the Klippain macro is quite comprehensive

[claudermilk]

I did some more poking around and I think that right now the answer is it isn't possible. I found the URL to retrieve the JSON: http://<server_ip>:<port>/api/v1/spool/<spool_id>. But there's no way right now for Klipper of Moonraker to retrieve that spool id that I see. There's some threads from others looking for the same thing. I have no idea how Fluidd or Mainsail is remembering what spool was last used, and there are a couple of auto-generated macros to set the spool. I just want to intercept the currently set spool's id, then send that get request. From there I can figure out how to parse down to the filament/material node and see what type it is. So it looks like this is a project for later.

I do have my own setup to tell me if the printer's stored loaded filament type has a mismatch from what the slicer reports. But it would be nice to have it automatically update that via Spoolman since the data is there.

[therm_virtual0y]

On 11/3/2023 at 2:44 AM, mvdveer said:

Thanks @PFarm Works brilliantly. Decided to install on a dedicated Raspi Pi 4 (as a server)  as I have 12 printers accessing the database. I installed it directly and not in a docker container.

An example of it in operation on the new Trident 300mm build:

Spools in use at present:

Slowly building the database of filaments

and Vendors

Next I will be implementing QR scanning:

Thank you again - you're a champion

I have so many questions lol!  I have 2 printers and after installing both realized that they are separate databases.  I did use docker so how do I go about referencing one?  like you said, have a separate Pi where Spoolman resides and then in each moonraker.conf, reference the IP address of that PI ( server)?

question 2. how did you get your UI to look like that?  looks cool!

[mvdveer]

3 hours ago, therm_virtual0y said:

I have so many questions lol!  I have 2 printers and after installing both realized that they are separate databases.  I did use docker so how do I go about referencing one?  like you said, have a separate Pi where Spoolman resides and then in each moonraker.conf, reference the IP address of that PI ( server)?

As an example, my spoolman server's ip address is "spoolman.local". Thus in each of my 11 printer's moonraker.conf files, I have:

[spoolman]
server: http://spoolman.local:7912
#   URL to the Spoolman instance. This parameter must be provided.
sync_rate: 5
#   The interval, in seconds, between sync requests with the
#   Spoolman server.  The default is 5.

The printers then access the single spoolman server.

2. The Mainsail UI can be themed. See here.  The trident from the above is a black and red build, thus the theme. You can create any theme you wish. Here are a few examples from my printers:

   

   

[claudermilk]

Yes, as @mvdveer shows, install Spoolman on a separate server--in my case I'm piggybacking on my Pi-based Plex server. Then reference the server's IP address as shown. Works like a charm.

Also an update on my issue from page 1 of the thread here with the system forgetting how much filament to log being used. I ended up bouncing between a couple of Githubs--of course; it ended up being a logic error in Fluidd. The developer found it, fixed it, and the fix is set to be in the next release.

[zav3nd]

@mvdveer Just curious if it works with ERCF? Or have you tried?

 

Not that I plan on feeding rabbits carrots... but maybe someday. The iceburg keeps getting bigger.

[mvdveer]

33 minutes ago, zav3nd said:

@mvdveer Just curious if it works with ERCF? Or have you tried?

Not that I plan on feeding rabbits carrots... but maybe someday. The iceburg keeps getting bigger.

Yes it does. (Spoolman Support)

 

[therm_virtual0y]

On 4/14/2024 at 11:59 PM, mvdveer said:

As an example, my spoolman server's ip address is "spoolman.local". Thus in each of my 11 printer's moonraker.conf files, I have:

[spoolman]
server: http://spoolman.local:7912
#   URL to the Spoolman instance. This parameter must be provided.
sync_rate: 5
#   The interval, in seconds, between sync requests with the
#   Spoolman server.  The default is 5.

The printers then access the single spoolman server.

2. The Mainsail UI can be themed. See here.  The trident from the above is a black and red build, thus the theme. You can create any theme you wish. Here are a few examples from my printers:

   

   

Appreciate your time 

[therm_virtual0y]

I keep getting an error message saying The material of the active spool (PETG ) does not match the material of the G-Code (PETG)..  not sure what that is about or how to fix it.

[mvdveer]

7 minutes ago, therm_virtual0y said:

I keep getting an error message saying The material of the active spool (PETG ) does not match the material of the G-Code (PETG)..  not sure what that is about or how to fix it.

Normally happens when your slicer profile has a different filament name than the one's you defined in spoolman. For example - ABS(no space) vs ABS (space after ABS) or ABS+. Had this happen on occasion. It is a feature I like as I have often sliced a print in ASA by accident and when I go to print, I get the warning. I then go back to my slicer, make sure the correct filament is selected and re-slice again.

There is actually nothing wrong - it is just a warning.

[therm_virtual0y]

[therm_virtual0y]

the filament id 7 starts with the type instead of the name.  It works for all my other filament except this one

 

[therm_virtual0y]

Oh gosh.  it shows me right in the warning.  I guess I didn't understand what you meant by space after the filament type.  (PETG ) vs (PETG)  

Thanks!