Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Resume job from power down (CNC Issue)

    Scheduled Pinned Locked Moved
    Beta Firmware
    2
    4
    195
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • EducatingSavvasundefined
      EducatingSavvas
      last edited by

      Hiya - I've noticed an issue with resuming after a controlled power down. The spindle router tool, turns on too late and there is not enough time for the spindle to come to full speed before moving along cut toolpaths. It also does this after the spindle has plunged back into the material. Normally with CNC routers the tool turns on, comes to speed and then plunges into material. Even if it is plunging into an already existing cut line - coming to speed can rattle the tool against the edge of material and leave a noticeable mark. The spindle would best turn on during the resurrect-prologue.g or earlier in the resurrect.g file. I think deselecting the tool is causing this - T-1 P0 followed by T1 P6. Is there a way of changing this without having to manually update this every time it is needed?

      I'm using RRF 3.4.0beta7+7.

      M98 Phomeall.g			; home all axes
      M3 S1000				; Turn on spindle
      G1 R1 X0 Y0 F1200		; rapid move X0 Y0
      
      ; File "0:/gcodes/Test for Power Down Job Resume.nc" resume print after print paused at 2022-01-31 10:20
      G21
      G92 X49.337 Y163.160 Z-37.050
      G60 S1
      T1 P0
      M98 P"resurrect-prologue.g"
      M116
      M290 X0.000 Y0.000 Z0.000 R0
      T-1 P0
      T1 P6
      ; Workplace coordinates
      G10 L2 P1 X0.00 Y0.00 Z0.00
      G10 L2 P2 X2.20 Y7.85 Z-29.85
      G10 L2 P3 X0.00 Y0.00 Z0.00
      G10 L2 P4 X0.00 Y0.00 Z0.00
      G10 L2 P5 X0.00 Y0.00 Z0.00
      G10 L2 P6 X0.00 Y0.00 Z0.00
      G10 L2 P7 X0.00 Y0.00 Z0.00
      G10 L2 P8 X0.00 Y0.00 Z0.00
      G10 L2 P9 X0.00 Y0.00 Z0.00
      G55
      M106 S0.00
      M116
      G92 E0.00000
      M82
      M486 S-1
      G17
      M23 "0:/gcodes/Test for Power Down Job Resume.nc"
      M26 S49831
      G0 F6000 Z-35.050
      G0 F6000 X49.337 Y163.160
      G0 F6000 Z-37.050
      G1 F3000.0 P0
      G21
      M24
      
      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @EducatingSavvas
        last edited by

        @educatingsavvas I added a pause to my resume file for this. but you could maybe add a pause to the tpost file

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        EducatingSavvasundefined 1 Reply Last reply Reply Quote 1
        • EducatingSavvasundefined
          EducatingSavvas @jay_s_uk
          last edited by EducatingSavvas

          @jay_s_uk I'm not sure what I've done now but the spindle is not turning on when M916 is sent. I actually think it only turned on previously after plunging because there happen to be an M3 command in the gcode being processed. So essentially resume from power loss doesn't work for CNC as the M3 R1 is missing.

          I wonder if there needs to be different resurrect.g files for CNC, FFF and Laser modes. If there is a way of identify the line the job gets paused on, I guess we can write our own macros.

          Possibly another thing for @dc42 to write on the list.

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @EducatingSavvas
            last edited by

            @educatingsavvas could be the case. I think the last job I ran was with beta 4 or 5

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA