G-Code Run on Pause/Continue not working?

edited October 2018 in Questions & Answers
I recently add a jam sensor that requests a pause from host (JAM_METHOD 2), which seems to work well enough  It stops when the filament runs out. (simple switch) However, the g-code I added to run on pause and continue (in the server front end) do not seem to be executing properly.

1.  The move command I have, G1 X0 Y200,  does not happen.  Is there a setting to prevent movements in FW after jams?
2.  When resuming, if the extruder has cooled by any amount, which is expected, it decouples when attempting to re-heat.  I have to kill the job, and restart to clear the error.  Below is the message in the log.  Is this a FW / EEPROM Setting?

23:06:04.361: important:Extruder jam detected
23:06:04.364: RequestPause:Extruder Jam Detected!
23:06:06.086: X:-12.25 Y:12.25 Z:5.200 E:1078.6025
23:06:07.524: Jam control disabled:1
23:07:34.817: Unknown command:N4577
23:07:34.817: Jam control disabled:0
23:07:34.821: Info:Marked all extruders as unjammed.
23:07:47.991: DebugLevel:14
23:07:47.991: Error:One heater seems decoupled from thermistor - disabling all for safety!
23:07:47.991: Error:Temp. raised to slow. Rise = -2.30 after 13080 ms
23:07:47.991: Disabling all heaters due to detected sensor defect.
23:07:47.991: DebugLevel:14
23:08:05.830: Warning: Communication timeout - resetting communication buffer.
23:08:05.830: Connection status: Buffered:63, Manual Commands: 2, Job Commands: 3343
23:08:05.830: Buffer used:63 Enforced free byte:19 lines stored:5
23:08:36.841: Warning: Communication timeout - resetting communication buffer.

Comments

  • You do not have commands/ack enabled in your log, so I can not see if it was send or was send in wrong order. We haven't changed the function since it exist so I would still expect it to work.

    Regarding decouple this is a firmware issue. You need to increase the decouple time to maybe 17 seconds to prevent that problem. Values are just too narrow for that extruder only working from cold temperatures with current timings.
  • Thanks for the information.  I think I fixed the decoupling per your suggestion.  The other issue, however is still an issue.  It appears the move command is getting issued, but still not being executed.   Below is the log from latest trial (bold is the move command).  I tried reordering my script, but it did not help.

    Original Pause Script:
    G1 X0 Y200 ; out of the way so I can reach print
    M602 P1 ; disable jam control
    M601 S1 ; Pause extruders so they do not heat while waiting for interaction

    Reordered Pause Script:
    M602 P1 ; disable jam control
    M601 S1 ; Pause extruders so they do not heat while waiting for interaction
    G1 X0 Y200 ; out of the way so I can reach print

    Additionally, I am finding that I am getting false positives on the sensor.  That is, it is triggering even though there is filament on the switch (though I will double check the mechanical assembly).  Is there a setting for jam detection that culd effect this (like software debounce value or something like that)? 

    Thanks again!:

    21:17:00.797: N1774 G0 F9000 X-3.824 Y11.249
    21:17:01.506: N1775 G1 F2580 X11.249 Y-3.824 E325.83398
    21:17:01.616: N1777 G0 F9000 X11.249 Y-3.117
    21:17:02.178: important:Extruder jam detected
    21:17:02.181: RequestPause:Extruder Jam Detected!
    21:17:02.358: N1778 G1 X0 Y200 ; out of the way so I can reach print
    21:17:02.358: N1779 M602 P1 ; disable jam control
    21:17:02.456: N1780 M601 S1 ; Pause extruders so they do not heat while waiting for interaction
    21:17:03.893: X:11.25 Y:-3.11 Z:1.200 E:325.8261
    21:17:05.279: Jam control disabled:1
    21:17:08.186: N1787 M117 Layer 6/125
    21:17:18.194: N1798 M117 ETA 21:52:05 day 16
    21:17:22.722: N1804 M602 P0 ; enable jam control
    21:17:22.722: N1805 M513 ; clear jam marker
    21:17:22.722: N1806 M601 S0 ; Heat up extruders to previous temperature
    21:17:22.722: N1807 G90
    21:17:22.722: N1808 G1 X11.249 Y-3.117 F6000
    21:17:22.723: N1809 G1 Z1.200 F120
    21:17:22.723: N1810 G92 E325.8340
    21:17:22.723: N1811 G1 F9000
    21:17:22.723: N1812 G1 F2580 X-3.117 Y11.249 E326.67865
    21:17:22.726: Jam control disabled:0
    21:17:22.732: Info:Marked all extruders as unjammed.
    21:17:22.733: N1813 G0 F9000 X-2.410 Y11.249
    21:17:53.739: Warning: Communication timeout - resetting communication buffer.
    21:17:53.739: Connection status: Buffered:105, Manual Commands: 2, Job Commands: 5000
    21:17:53.739: Buffer used:105 Enforced free byte:23 lines stored:7
    21:17:53.739: N1814 M117 ETE 00:34:46
    21:17:53.739: N1817 G1 F2580 X11.249 Y-2.410 E327.48174
    21:17:53.739: N1818 G0 F9000 X11.249 Y-1.703
    21:17:53.739: N1819 G1 F2580 X-1.703 Y11.249 E328.24327
    21:17:53.740: N1820 G0 F9000 X-0.996 Y11.249
    21:18:24.748: Warning: Communication timeout - resetting communication buffer.
    21:18:24.748: Connection status: Buffered:121, Manual Commands: 2, Job Commands: 5000
    21:18:24.748: Buffer used:121 Enforced free byte:23 lines stored:7
    21:18:24.748: N1821 M117 Layer 6/125
    21:18:24.748: N1824 G1 F2580 X11.249 Y-0.996 E328.96323
    21:18:24.748: N1825 G0 F9000 X11.249 Y-0.289
    21:18:24.749: N1826 G1 F2580 X-0.289 Y11.249 E329.64162
    21:18:24.749: N1827 G0 F9000 X0.417 Y11.249
  • If you only have a filament switch there are only 2 possible reasons for false trigger. Crosstalk or it has enough space to trigger with filament inserted. To protect for crosstalk do not go to close to heater and motor cables or at least twist the sensor/motor/heater cables to reduce crosstalk below treshhold.

    For the not executed move check the y length. If you move outside area stored in eeprom firmware will ignore the move, which is currently the only thing making sense for me.
  • Brilliant!  The Y move was outside the bounds.  Doh!  Should have recognized that.  

    I relocated the cable from sensor away from the steppers and LCD.  It was just draped across as a temporary placement.   No more false positives, so crosstalk is likely culprit.  It is not a twisted pair cable either. 

    Thanks for all the help.
Sign In or Register to comment.