Exactly - as a quick fix (in my optinion) it would be a good idea to disable the pause/abort buttons in such a case to avoid confusion.
Yes this is a bit awkward, we realize.
The short answer is there is no workaround, except for going to the printer :(
From a technical standpoint the USB job does not exist inside Connect (this is because connect is a add on to the original firmware, etc) and you are aborting a job object not a printer, so it is not the printer that has an abort/pause.
This seems like a mistake in hindsight, we will have to either make sure all jobs are always in Connect or allow a pause/abort on the printer level iso the job, so that the buttons always work.
I'll check if this is on our list of things to fix, if not I'll add it because this behavior does indeed suck.
- 3
- 2 years later...
On 11/22/2017 at 3:15 PM, robinmdh said:Yes this is a bit awkward, we realize.
The short answer is there is no workaround, except for going to the printer 😞
From a technical standpoint the USB job does not exist inside Connect (this is because connect is a add on to the original firmware, etc) and you are aborting a job object not a printer, so it is not the printer that has an abort/pause.
This seems like a mistake in hindsight, we will have to either make sure all jobs are always in Connect or allow a pause/abort on the printer level iso the job, so that the buttons always work.
I'll check if this is on our list of things to fix, if not I'll add it because this behavior does indeed suck.
Is there any progress? We are also struggling with this issue. Sometime even prints sent by network do not appear in print list (although they are printed).
Till then, maybe there is a workaround? Like sending a http-request to printer to stop whatever it is doing?
The S5 is not very cheap and mainly sold to business users. It's annoying that you cannot stop the printer from the network/home in some cases. We think about buying an IP-socket (120$ and more) because the software of printer shows the bugs mentioned. This should not be workaround intended.
It's not a secret that printers fail and often need to print for days. So there should be a reliable (!) solution for aborting a print on a 6500$ machine remotely. No matter whether the print was started via USB or network. Even with network printing, the jobs sometimes don't show up in Cura Connect. Please fix this! Thanks in advance 🙂
On 1/24/2020 at 4:54 PM, frowin said:
Is there any progress? We are also struggling with this issue. Sometime even prints sent by network do not appear in print list (although they are printed).
Till then, maybe there is a workaround? Like sending a http-request to printer to stop whatever it is doing?
The S5 is not very cheap and mainly sold to business users. It's annoying that you cannot stop the printer from the network/home in some cases. We think about buying an IP-socket (120$ and more) because the software of printer shows the bugs mentioned. This should not be workaround intended.
It's not a secret that printers fail and often need to print for days. So there should be a reliable (!) solution for aborting a print on a 6500$ machine remotely. No matter whether the print was started via USB or network. Even with network printing, the jobs sometimes don't show up in Cura Connect. Please fix this! Thanks in advance 🙂
An S5 with the latest firmware should be able to pause/resume/abort jobs via Connect or Cloud fine, regardless if they were started from USB or not.
Recommended Posts
SandervG 1,521
Hi @Macio,
If I understand it correctly, you start a print via USB and then when you monitor your print via Cura you want to pause it on your computer?
No, afaik that is not possible indeed. But I can imagine it would be desirable. I'll share this idea with our developers and perhaps it can be included in a future Cura. I don't think it is technically impossible, it is probably a feature which has not been build yet.
Link to post
Share on other sites