Ok - would be interested in the MQTT gets the remaining filament from the RFID or from the AMS working it out by pulling filament and counting the number of rolls.
I guess though that even if it does report 100% from reused filaments it might be possible to do some sort calculation to get a rough idea of how often the filament that is assigned the the reused tags has been reported.
Will give your system a try and see what happens with BL and NonBL spools.
Hi @Rdiger-36 , thanks for this tool! I just installed it together with spoolman and it worked out of the box. Will check and test how this combination helps to support my workflow in the future.
Thanks again
Falk
This integration looks fantastic, thank you for you for sharing!
As this is dependant on using Bambu spools and the usage reported I take it you haven’t found a way to capture usage for 3rd party filament? It is going to be a limited number of people who stick to their spools only.
Thanks for your feedback. Yes, unfortunately there is no ‘simple’ integration that enables support for filaments from third party manufacturers without additional hardware. For the assignment you need some kind of uniqueness, which unfortunately is only given by a serial number. In addition, the AMS does not determine data from spools without a serial number, either 100% or 0% is specified there.
If you are looking for an option with external hardware, you can take a look at the OpenSpool and OpenSpoolMan projects. These are also available on GitHub
Hi @Rdiger-36 thank you for your reply. I had briefly looked at OpenSpool a few months ago when it hit my radar but not seen OpenSpoolMan. Interesting ideas, I will setup OpenSpoolMan as it links to SpoolMan and take a look, thanks!
Take a look at openspoolman hxxp://github.com/drndos/openspoolman
It assigns the spool to the ams, can set a custom filament profile for the spool, so that Bambu Studio uses it, it has a printhistory and the best thing is it updates the spools in spoolman with the used filament.
Hi! That step means you need to create your own printers.json file. It doesn’t come with the tutorial because it needs to contain specific information about your printer(s), which only you can provide.
What you need to do:
1. Create a file named printers.json. The structure must match the example given in the GitHub repo
2. Save the file locally.
For example, on Linux, place it like here:
/home/user/container/printers/printers.json
3. Tell Docker where to find it by mounting the folder.
Your Docker volume setup should look like this:
/home/user/container/printers:/app/printers
(This maps your local folder to the /app/printers folder inside the container.)
If you’re on Windows:
1. Save the file to a path like:
C:\Users\YourName\container\printers\printers.json
2. Then set up your Docker volume like this:
C:/Users/YourName/container/printers:/app/printers
(Make sure to use forward slashes / instead of backslashes .)
Let me know if you need help creating the printers.json file or setting up the Docker volumes correctly
I’m sorry, but the A1 AMS Lite isn’t supported for filament tracking because the printer doesn’t publish any data that my app can use for tracking. However, OpenSpoolMan could manage this. You can take a look at it, as it’s mentioned earlier in the post.