I have searched this category and verified this feature request does NOT already exist.
on
1. Feature Summary
Ability to use and add ANY filament (by paxx12)
2. Why this feature is needed
In the spirit of opensource, please allow your version of orcaslicer and U1 to add any market filament and read any RFID not just snapmaker’s. There are many options and locking in to Snapmaker’s filaments does not make me want to pay double for youe filaments
3. Expected outcome
There are already written solution by paxx12 as you know but they require update of the printer’s extended firmware. Make it easier on the user and incorporate that so that the fillament in Orcaslicer an printer match and we can enjoy this printer to the fullest.
Thanks for mentioning Bespoke3D! If it works as an extra service on the stock firmware, that sounds like a promising approach.
Most likely, there’s no need to rewrite the RFID driver. Exposing a compatible tag’s UID and its channel could already be enough to identify a spool. The material details and remaining weight could live in a separate database, without writing anything back to the tag.
It would be great if Snapmaker officially supported this through an API or a small extension module. Do you have a link to Bespoke3D? I’d like to understand how it works.
How are you going to run Bespoke3D without first customising the OEM firmware?
Essentially, that’s how all the Paxx additions work: first provide access to the operating system, then run new or alternative services alongside Klipper (and provide more access to the Klipper configuration).
The difference with Bespoke3D is that it enables installable extensions rather than all or nothing, and each individual extension can be maintained separately by their respective developers. The U1 install to support that (yes, there is one) is actually sent over SSH rather than as a firmware update… but it is still a mod.
Bespoke3D sounds great, and I will look into going that way, but it might be as an addition to Paxx.
I thought I had seen some mention of integrating Bespoke3D within Paxx, but perhaps I am wrong or perhaps there was disagreement between them. Anyway, here’s the resource: https://github.com/Bespok3d