UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
UMS3 is visible in the DF, but Cura does nothing when clicking on "Print via cloud"
Posted
· UMS3 is visible in the DF, but Cura does nothing when clicking on "Print via cloud"
Update: Alright. After 2 days of testing everything in the network setup, reinstalling cura, resetting printers, multiple times, creating a new DF account and even setting up a new wifi network, I finally found the issue.
It was the print job file name! The file came from a co-worker who used a comma between the version numbers, in this case "v3,1". As the printer does not have a problem with this when printing over a USB stick or sending the print job over the network, it took me 2 full days to find that out.
Even more strange is, the "error" I see when sending this file. It's a short disconnect symbol on the printer which made me think it was a connection related issue.
This might trouble other users as well because there was never a mentioning of not working signs in the file name.
This might be something to take a look at? @ctbeke
Posted
· UMS3 is visible in the DF, but Cura does nothing when clicking on "Print via cloud"
3 hours ago, Gero said:
A little update: A simple "+" is also not working and disrupts the transmission of the file into the cloud.
There might be even more signs that don't work.
We've started an internal investigation into this. It seems like the printer is a bit too restrictive with which characters it does not allow when parsing file names, and there's also some inconsistency between Cura, Cloud and Printer regarding the validation rules.
Since Cura and the Printer firmware are not released continuously, it'll take some time before any fixes end up in releases, but we're working on it for sure 🙂
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
The full stable release of UltiMaker Cura 5.4 is here and it makes it easier than ever to remove brims and supports from your finished prints. UltiMaker S series users can also look forward to print profiles for our newest UltiMaker PET CF composite material!
Recommended Posts
Gero 47
Update: Alright. After 2 days of testing everything in the network setup, reinstalling cura, resetting printers, multiple times, creating a new DF account and even setting up a new wifi network, I finally found the issue.
It was the print job file name! The file came from a co-worker who used a comma between the version numbers, in this case "v3,1". As the printer does not have a problem with this when printing over a USB stick or sending the print job over the network, it took me 2 full days to find that out.
Even more strange is, the "error" I see when sending this file. It's a short disconnect symbol on the printer which made me think it was a connection related issue.
This might trouble other users as well because there was never a mentioning of not working signs in the file name.
This might be something to take a look at? @ctbeke
Link to post
Share on other sites
Smithy 1,141
Your findings are really helpful, thanks a lot for the feedback!
Link to post
Share on other sites
ctbeke 133
@Gero very helpful and thorough debugging! I'll take this issue back to the team to see if something can be done about it!
Link to post
Share on other sites
Gero 47
A little update: A simple "+" is also not working and disrupts the transmission of the file into the cloud.
There might be even more signs that don't work.
Link to post
Share on other sites
ctbeke 133
We've started an internal investigation into this. It seems like the printer is a bit too restrictive with which characters it does not allow when parsing file names, and there's also some inconsistency between Cura, Cloud and Printer regarding the validation rules.
Since Cura and the Printer firmware are not released continuously, it'll take some time before any fixes end up in releases, but we're working on it for sure 🙂
Link to post
Share on other sites