<p>I have a long print that keeps aborting. At some random point mid-print the printer says "Click to resume...". There is nothing in the G-code that asks for user confirmation. What could it be that triggers this? I noticed that sometimes (not every time) there is a blob of plastic in the way that should not be there.</p>

<p>On one occasion, after the "Click to resume...", the LCD showed the message <code>FY178.N16466</code> and again waited for a click.</p>

<p>The printer is an Anet A8 with Marlin 1.1.9. Slicer is Cura. I am printing via USB from Cura directly.</p>

<p>This is the error message:</p>

<p><a href="https://i.stack.imgur.com/QXdNc.jpg" rel="nofollow noreferrer" title="&quot;Click to resume...&quot; error message"><img src="https://i.stack.imgur.com/QXdNc.jpg" alt="&quot;Click to resume...&quot; error message" title="&quot;Click to resume...&quot; error message"></a></p>

[{'answer_id': 7263, 'author': 'Greenonline', 'author_id': 4762, 'author_profile': 'https://3dprinting.stackexchange.com/users/4762', 'pm_score': 2, 'selected': False, 'text': '<p><em>This is not an answer/explanation per se, but it might help you track down the cause.</em></p>\n\n<hr>\n\n<p>It <em>might</em> be worth <a href="http://marlinfw.org/docs/gcode/M928.html" rel="nofollow noreferrer">enabling logging</a> <code>M928</code> to the SD card (ensure that the R/W tab on the SD card is set appropriately), so that (after this has happened a few times) then you can look through the log to see what the command preceding the abort was, and if it is consistently the same (sequence of) commands that cause this to happen. </p>\n\n<pre><code>M928 filename\n</code></pre>\n\n<p>If that doesn\'t throw up anything obvious, then, in conjunction with logging, you could enable debugging, see <a href="http://marlinfw.org/docs/gcode/M111.html" rel="nofollow noreferrer"><code>M111</code> Debug level</a>. For example:</p>\n\n<pre><code>M111 S7 ; ECHO, ERRORS, INFO\n</code></pre>\n\n<p>Then run through the long print again. As before, after a few of the <em>click to resume print</em> messages, then go back and check the log for anything that might indicate why this is happening.</p>\n\n<p>To subsequently disable the debugging:</p>\n\n<pre><code>M111 S0\n</code></pre>\n'}, {'answer_id': 7287, 'author': '0scar', 'author_id': 5740, 'author_profile': 'https://3dprinting.stackexchange.com/users/5740', 'pm_score': 4, 'selected': True, 'text': '<p>To answer your question directly, this action (<code>Click to resume...</code>) is triggered by a buffer overflow of the Marlin firmware that is caused by the repetitive sending of <code>M105</code> command by Ultimaker Cura (without checking the result).</p>\n\n<p>This problem is a <a href="https://github.com/Ultimaker/Cura/issues/3994" rel="nofollow noreferrer">reported problem</a> and fixed in the next release of Ultimaker Cura (please do note that as of posting this answer, the 3.6 Beta release is available for <a href="https://ultimaker.com/en/blog/52744-ultimaker-cura-36-beta-available-now" rel="nofollow noreferrer">download</a>). It appears to be a communication problem between Ultimaker Cura 3.4+ and 1.1.8+ versions of the Marlin firmware and has to to with polling of the temperature (<code>M105</code>). The link above also states it is fixed in the 3.6 release (which is the next release) as the fix has been integrated in the main code base.</p>\n\n<p>This describes the problem:</p>\n\n<blockquote>\n  <p>To update the temperatures in the monitor, Cura sends M105 pings every\n  2 seconds. It seems that if this is done during a print without\n  waiting for an <code>OK</code> from the printer, the serial buffer on the printer\n  may still overflow eventually (causing Marlin to complain/pause).</p>\n</blockquote>\n\n<p>and this describes the solution:</p>\n\n<blockquote>\n  <p>During some operations, such as preheating, the printer responds to\n  new commands with <code>echo:busy</code>. While it is busy, it does send\n  temperature messages, but these are not prepended with an <code>ok</code>,\n  because the <code>ok</code> is supposed to show that a command was received and\n  executed. So the two patches I wrote do the following:</p>\n  \n  <ul>\n  <li>the pattern matching no longer looks for <code>ok</code> messages, but looks for\n  temperature updates (this fixes the temperature updating while the\n  printer is preheating) </li>\n  <li>once the printer has said that it is busy, stop\n  asking for temperature updates until the next <code>ok</code> is received (this\n  prevents the serial buffer overflowing while preheating)</li>\n  </ul>\n</blockquote>\n\n<hr>\n\n<p><em>Old answer centered around the firmware (based on the text of the OP, no photo with the actual error message was added yet):</em></p>\n\n<p><strike>The text <code>click to resume print</code> cannot be found (with case insensitive search) in the latest sources of Marlin 1.1.9 down to Marlin 1.1.6. This means that you are using a different fork, an older version of Marlin or the message is not displayed as such.</p>\n\n<p>The text message <code>Resume print</code> can be found, and is part of the message constant <code>MSG_RESUME_PRINT</code></p>\n\n<pre><code>#define MSG_RESUME_PRINT                    _UxGT("Resume print")\n</code></pre>\n\n<p>But, this cannot be found in some sort of a concatenation using <code>MSG_RESUME_PRINT</code>!</strike></p>\n'}, {'answer_id': 7363, 'author': 'divest divest', 'author_id': 13395, 'author_profile': 'https://3dprinting.stackexchange.com/users/13395', 'pm_score': 1, 'selected': False, 'text': "<p>Tonight I had faced the same problem.</p>\n\n<p>I've read somewhere (can't find the source now) that this is a Cura bug that has been fixed in Cura 3.6 beta</p>\n"}, {'answer_id': 7547, 'author': 'HSaturn', 'author_id': 13642, 'author_profile': 'https://3dprinting.stackexchange.com/users/13642', 'pm_score': 2, 'selected': False, 'text': '<p>For your information, this problem has occurred for me with Cura 3.6.0 (yesterday and 2 days ago)</p>\n\n<p>I thought the problem was occurring with Marlin since 1.8.</p>\n\n<p>My Marlin version is 1.3 (... just discover that because of that issue!)</p>\n\n<p>As my printer works perfectly with 1.3, I\'d prefer not to upgrade.</p>\n\n<p>I had the \'click to resume\' problem twice. </p>\n\n<p>I\'ve printed tons of ABS models without problem, two days ago, I\'ve printed PLA models and had this issue. (70&nbsp;°C 200&nbsp;°C).</p>\n\n<p>For sure if the problem occurs again, I\'ll upgrade to Marlin 1.9 (or even 2.0 even if still in beta) because it seems that you <em>have</em> found the problem and already solved it; I was surprised to read that it was fixed in Cura 3.6 since I had the problem with that version.</p>\n\n<p>My printer is a Tevo Tarentula (modified, I\'ve removed the pseudo bed leveling options because I prefer to level manually (no z move while printing)).</p>\n\n<p>One more information is that in parallel, I\'ve decided to print the first layer at a very low speed (adhesion problems).</p>\n\n<p>I\'ve changed from 30&nbsp;mm/s (ABS with big adhesion problems) to 10&nbsp;mm/s with PLA + Cura 3.6 and went into this bug (yes one could argue that I may print faster etc., but that\'s not the point here). Maybe I have the problem because I\'m printing the 1st layer at a this slow speed (thus making the full buffer problem more critical).</p>\n\n<p>The bug does not occur each time I print, even when printing the same model with same parameters...</p>\n\n<p>@HuguesDug reported the <a href="https://github.com/Ultimaker/Cura/issues/3994" rel="nofollow noreferrer">same problem 14 days ago</a> and\n@Leeb answered him that running with Marlin 1.9 solved the problem.</p>\n'}]
['https://3dprinting.stackexchange.com/questions/7217', 'https://3dprinting.stackexchange.com', 'https://3dprinting.stackexchange.com/users/13147/']