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

    Error on resume print

    Scheduled Pinned Locked Moved Solved
    General Discussion
    2
    3
    131
    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.
    • Erinellundefined
      Erinell
      last edited by

      Hello,
      I have an issue. When I resume a print after a pause, the printer go back to printing position and completely stop the print with this error : "Error: in GCode file line 0: G1: Axis X is already used by a different motion system".
      Following several prints with a pause/resume (with the same slicer profile), it seems to happen randomly (sometimes, it work fine). It's getting annoying because I can't find the cause and it completely stops the print.
      I'm running on 3.5.0, and from what I found in the source code, it's related to a feature since version 3.5.

      Here is my M122 output :

      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.5.0 (2024-04-16 09:43:06) running on Duet 3 MB6HC v1.01 (SBC mode)
      Board ID: 08DJM-956L2-G43S8-6JKD6-3SJ6M-KA06G
      Used output buffers: 1 of 40 (17 max)
      Error in config.g line 111 while starting up: Bad command: @   <--- (i don't have 111 lines in my config.g)
      === RTOS ===
      Static ram: 155208
      Dynamic ram: 88248 of which 4984 recycled
      Never used RAM 94696, free system stack 204 words
      Tasks: SBC(2,ready,0.7%,434) HEAT(3,nWait 6,0.0%,337) Move(4,nWait 6,0.0%,336) CanReceiv(6,nWait 1,0.0%,940) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,336) TMC(4,nWait 6,8.9%,56) MAIN(2,running,90.3%,103) IDLE(0,ready,0.0%,30), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:30:42 ago, cause: power up
      Last software reset at 2024-06-04 19:34, reason: User, Platform spinning, available RAM 94168, slot 1
      Software reset code 0x6000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x00
      Aux1 errors 0,0,2011
      MCU temperature: min 23.6, current 44.5, max 44.6
      Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
      Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/48/16, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min n/a, mspos 8, reads 43747, writes 15 timeouts 0
      Driver 1: standstill, SG min n/a, mspos 8, reads 43747, writes 15 timeouts 0
      Driver 2: standstill, SG min n/a, mspos 8, reads 43748, writes 15 timeouts 0
      Driver 3: standstill, SG min n/a, mspos 8, reads 43748, writes 15 timeouts 0
      Driver 4: standstill, SG min n/a, mspos 8, reads 43748, writes 15 timeouts 0
      Driver 5: standstill, SG min n/a, mspos 8, reads 43749, writes 14 timeouts 0
      Date/time: 2024-06-04 20:48:49
      Slowest loop: 26.77ms; fastest: 0.04ms
      === Storage ===
      Free file entries: 20
      SD card 0 not detected, interface speed: 37.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks held by null, null
      HTTP* is doing "M122" in state(s) 0
      Telnet is idle in state(s) 0
      File is idle in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger* is idle in state(s) 0
      Queue is idle in state(s) 0
      LCD is idle in state(s) 0
      SBC is idle in state(s) 0
      Daemon is idle in state(s) 0
      Aux2 is assembling a command in state(s) 0
      Autopause is idle in state(s) 0
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x80000003
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 16497, received 0, lost 0, errs 8720968, boc 0
      Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 9215/0/0
      Tx timeouts 0,0,9214,0,0,7281 last cancelled message type 4514 dest 127
      === SBC interface ===
      Transfer state: 5, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 6513/6513
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x253c0
      Buffer RX/TX: 0/0-0, open files: 0
      === Duet Control Server ===
      Duet Control Server version 3.5.0 (2024-04-17 17:50:47, 32-bit)
      HTTP+Executed:
      > Executing M122
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 18.69, max time between full transfers: 51.4ms, max pin wait times: 69.3ms/7.4ms
      Codes per second: 0.02
      Maximum length of RX/TX data transfers: 6792/864
      
      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator @Erinell
        last edited by

        @Erinell said in Error on resume print:

        Error in config.g line 111 while starting up: Bad command: @ <--- (i don't have 111 lines in my config.g)

        What other macros are getting called?
        Share your config.g and the results of sending M98 P"config.g"

        3.5.1 is released now. you should update again.

        Z-Bot CoreXY Build | Thingiverse Profile

        Erinellundefined 1 Reply Last reply Reply Quote 0
        • Erinellundefined
          Erinell @Phaedrux
          last edited by

          @Phaedrux

          Thanks for your reply.
          I've updated to 3.5.1 and it seems to work fine, the error message is no longer appearing after somes test.
          For the config file error, this is my macro call to turn on a led strip. Here again, this error disappeared with the update.
          What an idiot, I should have started by updating.

          So, everything is fine now, thanks anyway.

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined Phaedrux marked this topic as a question
          • Phaedruxundefined Phaedrux has marked this topic as solved
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA