<p>After installing a screen on my printer I discovered Pronterface is sending a "Wait for user" G Code to the printer.</p>

<p>Because this changes the question too much and invalidates the existing answer I've asked a new question at <a href="https://3dprinting.stackexchange.com/questions/518/what-makes-pronterface-wait-for-user">What makes Pronterface wait for user?</a></p>

CC BY-SA 3.0
2016-02-07T16:14:47.803Z
2016-02-07T16:14:47.803Z
2017-04-13T13:00:58.447Z
Nir
<p>A problem I have come across when using Pronterface is that the operating system starves the resources of the program if the program's window is not in the front.</p>

<p>If I, for instance, started a print, then started browsing the web, it would sometimes suddenly stop. When bringing Pronterface back to the front, it would take a few seconds, and then continue (if I remember correctly).</p>

<p>On OS X - which I am using - I believe this is called <em>app nap</em>, while a similar mechanism exist for Windows. I ended up printing form an SD card myself after this, but you might want to try manually setting the resource priority for Pronterface in your OS.</p>

<p>In Windows, you could trying to increase the resource allocation for Pronterface by going to <code>Task Manager -&gt; Details -&gt; Right click the Pronterface process -&gt; Set Priority</code>. I would be careful to set it too high, since you are basically allowing the program more juice to potentially do something wrong.</p>

<p>In OS X you could try to <a href="https://www.ihash.eu/2015/01/disable-app-nap-per-app-os-x-yosemite/" rel="nofollow">disable app nap</a> for Pronterface.</p>

CC BY-SA 3.0
2016-01-20T20:19:07.877Z
That's not it, just happened to me while the Pronterface window was the active foreground window
Nir
CC BY-SA 3.0
2016-01-20T07:43:06.507Z
2016-01-20T08:18:48.987Z
2016-01-20T08:18:48.987Z
Tormod Haugene
<p>When I use Cura with the Pronterface UI it sometime just stops printing.</p>

<p>When it stops the printer just stops, the UI looks like it's still printing but nothing is moving in the printer, also, trying to control the printer from the UI does nothing.</p>

<p>It always stops early in the printing process, usually during the auto-leveling process or while printing the skirt, the latest it happened was during the first solid layer of a raft.</p>

<p>Usually closing the printing window and re-opening it solves the problem but not always, this never happened to me with the basic UI, I couldn't find any settings that makes the problem better or worse, it just happens randomly.</p>

<p>Anyone knows how to stop that from happening?</p>

<p>My printer is a Robo 3D R1+</p>

<p><strong>Update</strong></p>

<p>After installing a screen on my printer I discovered Pronterface is sending a "Wait for user" G Code to the printer.</p>

<p>Because this changes the question too much and invalidates the existing answer I've asked a new question at <a href="https://3dprinting.stackexchange.com/questions/518/what-makes-pronterface-wait-for-user">What makes Pronterface wait for user?</a></p>

CC BY-SA 3.0
2016-01-20T21:30:39.363Z
Have you tried to printing from a different source, such as a SD card? If this works well, it is probably not the printer itself that is the problem. Does the screen go blank for a moment before it happens? If it does, it could be that the arduino receives a "connect" command from some other process, and cuts it current action. Could it be any of these, you think?
Tormod Haugene
CC BY-SA 3.0
2016-01-21T09:20:34.893Z
@TormodHaugene the problem happens only with cura and the pronterface ui, both SD card and cura with the basic ui don't have this problem. I really don't know if the problem is in the printer or the software
Nir
CC BY-SA 3.0
2016-01-21T21:44:11.990Z
So if you leave Pronterface out of it all, everything works just fine? Then I would reconsider using Pronterface for direct printing altogether. In my opinion, needing to have a computer always connected is sort of unnecessary. Are there any particular reason why you want to print directly from Pronterface?
Tormod Haugene
CC BY-SA 3.0
2016-01-22T06:57:33.973Z
@TormodHaugene my printer does not have a screen, so if I want any manual control what so ever I don't really have a choice (a screen is currently on its way from China, but it takes a while to arrive)
Nir
CC BY-SA 3.0
2016-01-22T08:03:31.600Z
Oh, I see. That makes it a bit more complicated!
Tormod Haugene
<software>
Cura with Pronterface UI stops printing
Nir
# Cura with Pronterface UI stops printing

(Asked by: username_0 on 2016-01-19)

When I use Cura with the Pronterface UI it sometime just stops printing.

When it stops the printer just stops, the UI looks like it's still printing but nothing is moving in the printer, also, trying to control the printer from the UI does nothing.

It always stops early in the printing process, usually during the auto-leveling process or while printing the skirt, the latest it happened was during the first solid layer of a raft.

Usually closing the printing window and re-opening it solves the problem but not always, this never happened to me with the basic UI, I couldn't find any settings that makes the problem better or worse, it just happens randomly.

Anyone knows how to stop that from happening?

My printer is a Robo 3D R1+

**Update**

After installing a screen on my printer I discovered Pronterface is sending a "Wait for user" G Code to the printer.

Because this changes the question too much and invalidates the existing answer I've asked a new question at [What makes Pronterface wait for user?](https://3dprinting.stackexchange.com/questions/518/what-makes-pronterface-wait-for-user)

**Tags:** software
> **Comments:**
> **username_1**: Have you tried to printing from a different source, such as a SD card? If this works well, it is probably not the printer itself that is the problem. Does the screen go blank for a moment before it happens? If it does, it could be that the arduino receives a "connect" command from some other process, and cuts it current action. Could it be any of these, you think?  
> **username_0**: @TormodHaugene the problem happens only with cura and the pronterface ui, both SD card and cura with the basic ui don't have this problem. I really don't know if the problem is in the printer or the software  
> **username_1**: So if you leave Pronterface out of it all, everything works just fine? Then I would reconsider using Pronterface for direct printing altogether. In my opinion, needing to have a computer always connected is sort of unnecessary. Are there any particular reason why you want to print directly from Pronterface?  
> **username_0**: @TormodHaugene my printer does not have a screen, so if I want any manual control what so ever I don't really have a choice (a screen is currently on its way from China, but it takes a while to arrive)  
> **username_1**: Oh, I see. That makes it a bit more complicated!  

---

## 2 answers

### Answer by username_0 on 2016-02-07. Score: 1 | Accepted answer

After installing a screen on my printer I discovered Pronterface is sending a "Wait for user" G Code to the printer.

Because this changes the question too much and invalidates the existing answer I've asked a new question at [What makes Pronterface wait for user?](https://3dprinting.stackexchange.com/questions/518/what-makes-pronterface-wait-for-user)


---

### Answer by username_1 on 2016-01-20. Score: 1

A problem I have come across when using Pronterface is that the operating system starves the resources of the program if the program's window is not in the front.

If I, for instance, started a print, then started browsing the web, it would sometimes suddenly stop. When bringing Pronterface back to the front, it would take a few seconds, and then continue (if I remember correctly).

On OS X - which I am using - I believe this is called *app nap*, while a similar mechanism exist for Windows. I ended up printing form an SD card myself after this, but you might want to try manually setting the resource priority for Pronterface in your OS.

In Windows, you could trying to increase the resource allocation for Pronterface by going to `Task Manager -> Details -> Right click the Pronterface process -> Set Priority`. I would be careful to set it too high, since you are basically allowing the program more juice to potentially do something wrong.

In OS X you could try to [disable app nap](https://www.ihash.eu/2015/01/disable-app-nap-per-app-os-x-yosemite/) for Pronterface.

> **Comments:**
> **username_0**: That's not it, just happened to me while the Pronterface window was the active foreground window  

---

