On 5/3/2019 at 9:40 AM, Flyver said:Hey. I have tried since update 5.8.2 and cura 4.0 came out. Try logging into my printer from home. unsuccessfully. my printer stand on my job. and run with fixed IP. I have logged in to cura connect and start Connect to cloud. but when I try and log on to my S5 there at home I can not even find it even though I log on to my cura user. hope you can help. as i would be able to stop printing from home and not have to go to work if something happens during print
Lasse
Danmark
6
If you manually add the printer, the cloud connection doesn't work. As you might have noticed, the cloud connection functionality is at the bare minimum right now. The 4.1 cura release will already have a more fleshed out implementation.
Recommended Posts
Top Posters In This Topic
20
15
14
13
Popular Days
Mar 22
34
Mar 28
24
Mar 21
17
Mar 23
16
Top Posters In This Topic
Smithy 20 posts
ScanHD 15 posts
kmanstudios 14 posts
itretail 13 posts
Popular Days
Mar 22 2019
34 posts
Mar 28 2019
24 posts
Mar 21 2019
17 posts
Mar 23 2019
16 posts
Popular Posts
SandervG
Hi everyone, Thank you for all the time and energy you invest in sharing your messages here, trying to share your perspective with others. I like to think that this all comes from the sa
Smithy
Since we only ever fill the threads with complaints and blames about bugs and errors, the positive should also be highlighted. Bringing the firmware from UM3 to the same code base was cert
nallath
There are 400+ people working for Ultimaker. There is no way that everyone can know what is happening at any given moment. So yeah, I do work for Ultimaker, but that doesn't mean that I can give answe
Posted Images
kfsone 5
@SandervG Is there a way for QA to leverage volunteered end-users for final bake testing? Unless you have hitl fuzzers, you're just never going to get that release-to-wild feedback until you release-to-wild(*)
Perhaps you might consider providing them (QA) a means to have some small number of customers sign an NDA in exchange for "T-1" access to release builds with, potentially, specific test prints.
-Oliver
(* c.f: Engineer I worked with so vigorously and thoroughly tested a build across hundreds of internal build configs that he ultimately had to rush the release. First customer it encountered happened to be installing on a brand new machine that had never had the software installed before, and when he rebooted his machine an hour later, it wouldn't boot back up. The installer had tried to remove the previous installation, but it only caught *that* scenario if there was a record of where the previous entry had been. After that, it went ahead and deleted everything in the current directory, which was by default C:\... Hundreds of users had trashed their C:\ folder before the release was pulled)
Link to post
Share on other sites