Multi-printer support

[thijstriemstra]

Afaik only a single printer is supported right now, it's not to possible to send a spool change to a printer other than the one defined in the config.

[bofh69]

Yes, the idea was to have a nfc-reader at the printers spool holder to automatically handle changes as you load the new filament.

What is your idea and workflow here?

Having a single nfc-reader where you tap the spool before mounting it on one of the printers? In that case some more input is needed to the system. Perhaps a tag that represent the printer the spool is moved to? That could also be used when storing a spool to update the location in spoolman.

Support more nfc-readers from the program? Then it is perhaps better to add an environment variable for choosing the configuration file and then just run it once per nfc-reader?

[thijstriemstra]

I bought a roll of ntag215 stickers and made magnetic tags that attach to my spoolbox:

at first i thought of making a rpi-based handscanner but this would need a long cable or battery pack. Since my printers are on same table, a scanner that is mounted to the wall is another idea since i can easily take out the magnetic tags, scan it and place it back.

The OpenSpool project uses an esp32 to control the np532 device and use wifi to transmit the data. These esp32 devices are much cheaper and smaller, more suitable than an rpi IMO.

So what about making a wall-mounted scanner, using esp32 (and maybe even micropython instead of c++)?

I would prefer if we also use YAML instead of json config files, which all klipper related projects seem to use.

Klipperscreen, for example, allows you to define an x nr of printers in the config, something like this:

[printer ender]
moonraker_host: ender.lan

[printer prusa]
moonraker_host: prusa.lan

A small OLED display on the scanner that shows the name of the filament after scanning would be great as well. I guess that would also mean the scanner needs a rotary encoder or something so you can select the printer that will use the spool. A menu option to write a tag would be needed as well.

The scanner could host a webserver where you can add/remove printers so the yaml config would actually not be needed when going this route.

[bofh69]

Nice setup!

I don't think nfc2klipper would be the right place for such a feature/workflow. Its probably better to add klipper/spoolman support to the OpenSpool project instead. They've already got the hardware and a lot of the firmware needed for it.

My klipper doesn't use YAML. It is a custom format that looks like toml/Windows INI-files. Switching to toml instead of json5 should be pretty straight forward and its probably a good idea to be more similar to the wider klipper ecosystem.