I don't have my printer networked at all, I keep using it via a thumb drive. It would be weird for an issue with the network stack causing problems with material recognition, but interesting nonetheless.
Thanks.
I don't have my printer networked at all, I keep using it via a thumb drive. It would be weird for an issue with the network stack causing problems with material recognition, but interesting nonetheless.
Thanks.
Hi @18erik, thank you for your message. It is not clear from my message if you have tried with multiple spools of PVA or just one. It could be possible that the NFC chip on your spool of PVA is not working, if the bay does read PLA/Tough PLA. Have you tried different spools of PVA, or other UM materials for that matter?
Unfortunately the Tough PLA and Natural PVA that came with the printer are the only ones I have on hand that are Branded w/NFC. I have some more on order.
The NFC failure doesn't concern me that much, these things happen.
The one that is more confusing is the Material Handler and Printer recognizing "Touch Black PLA" and me using the Ultimaker Tough Black PLA in Cura, and the printer still making me ignore a "material conflict" when beginning a print.
Hello, a material conflict can also occur when you configure to use Ultimaker PLA with a BB print core for example. Have you verified that all configurations are correct? Perhaps you can share a screenshot if you are not sure. Do you get a material conflict when you print a single extrusion print too?
Thanks,
I would start by physically removing all rolls in the material station except Bay A that is correctly recognized a tough black PLA. Then try to rerun your print. Looks like it was not expecting to use the second extruder.
If that works, then try adding one reel at a time and let the material station identify them. If it does not read or reads wrong, remove and try a different bay. I just had a reel of PVA be idenfied in one bay as ABS repeatedly, and relocated to another bay and been read correctly.
Good luck
Hi @18erik, I had a moment to discuss this with our product experts and this is a known bug when you print over USB. Can you confirm this is the case? This will be solved in the next firmware release. For the time being, if you would print over network you would work avoid this message. Or if you can't, ignoring/clicking it away also works.
Let me know if this works!
Recommended Posts
slnielsen 1
I see the same issue quite often. New firmware seems to help. I have updated it some times already. It also helps when the network functionally seems to have an error.
Link to post
Share on other sites