-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proper RFID Programming #24
Comments
Sorry to hear you're having trouble programming tags. Is it unreliable or what is the problem you were finding? Program a tag you go into the web interface at http://openspool-xxxxxx.local or http://192.168.x.x Then you need to select the filament type filament color and filament brand and filament temperature range. After you said that press the right NFC button and then touch tag to the reader. It works best in the corners of the reader, hold it for one to two seconds. If there's a problem writing, it will light up red and you'll see an error in the logs |
Okay that is what I needed. Wasn't sure. I try to scan the rfid on my phone and no info shows up. I have a android phone. |
Can we add our own filament to the program? |
Currently, it only supports a select, subset of bambu recognized codes. If it's not a filament that is currently recognized just select generic. There are plans to improve this and pull from other databases, but for now it's only the bambu codes |
If we put a brand (because I use the NFC tags for more than just scanning to the printer, I use them to inventory my filament as well) So, if I put brand as "Jayo" or "Flashforge" or "Reprapper"... will the device just treat that as generic or will it error because its not one of the defined brands? |
get_bambu_code() It will return an empty string which the printer will probably ignore (unverified). Would you be willing to open a feature request to change that behavior? We could make it fall back to |
What are the proper steps to program the RFID Tags for Bambu Labs X1C? Just having issues with the programming.
The text was updated successfully, but these errors were encountered: