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

    Maestro halted after macro launched on DWC

    Scheduled Pinned Locked Moved
    Firmware installation
    2
    3
    436
    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.
    • pabomanundefined
      paboman
      last edited by

      The machine was printing from SD card, I launched a macro calling M122 to see if any hiccups are occuring, after this the DWC stopped responding (host unreachable) so I went to the Panel Due to see if the network module was still online but as soon as I touched the Macro tab button the machine stopped.

      I will try to reproduce this error

      === Diagnostics ===
      RepRapFirmware for Duet 2 Maestro version 2.02RC4(RTOS) running on Duet Maestro 1.0
      Board ID: 08DAM-9F9DA-MWNS8-6J1DG-3SN6K-K406X
      Used output buffers: 1 of 20 (14 max)
      === RTOS ===
      Static ram: 21428
      Dynamic ram: 96812 of which 0 recycled
      Exception stack ram used: 212
      Never used ram: 12620
      Tasks: NETWORK(ready,456) HEAT(blocked,1300) MAIN(running,3672) IDLE(ready,200)
      Owned mutexes:
      === Platform ===
      Last reset 00:00:21 ago, cause: software
      Last software reset at 2018-11-22 20:00, reason: Stuck in spin loop, spinning module GCodes, available RAM 12172 bytes (slot 0)
      Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f80f BFAR 0xe000ed38 SP 0x20000f1c Task 0x5754454e
      Stack: 00440d4f 00444830 21000200 00000004 00000000 00000004 00444a2d 200046dc 00440d4f 00000001 00000004 2001c354 00000004 2001c354 000069c4 00000004 00441075 00000004 00000000 00000000 00419f2f 00441015 00745fff
      Error status: 0
      Free file entries: 9
      SD card 0 detected, interface speed: 15.0MBytes/sec
      SD card longest block write time: 0.0ms, max retries 0
      MCU temperature: min 39.3, current 39.5, max 39.9
      Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: standstill, read errors 0, write errors 1, ifcount 22, reads 857, timeouts 0
      Driver 1: standstill, read errors 0, write errors 1, ifcount 22, reads 857, timeouts 0
      Driver 2: standstill, read errors 0, write errors 1, ifcount 22, reads 857, timeouts 0
      Driver 3: standstill, read errors 0, write errors 1, ifcount 180, reads 857, timeouts 0
      Driver 4: standstill, read errors 0, write errors 1, ifcount 171, reads 857, timeouts 0
      Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 864
      Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 863
      Date/time: 2018-11-22 20:01:12
      Slowest loop: 4581228.50ms; fastest: 0.06ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
      === Move ===
      Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
      Scheduled moves: 0, completed moves: 0
      Bed compensation in use: none
      Bed probe heights: 0.000 0.000 0.000 0.000 0.000
      === Heat ===
      Bed heaters = 0, chamberHeaters = -1 -1
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Stack records: 1 allocated, 1 in use
      Movement lock held by null
      http is ready with "M122" in state(s) 0 0
      telnet is idle in state(s) 0
      file is idle in state(s) 0
      serial is idle in state(s) 0
      aux is idle in state(s) 0
      daemon is idle in state(s) 0
      queue is idle in state(s) 0
      lcd is idle in state(s) 0
      autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 7.61ms; fastest: 0.03ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 1 of 8
      Interface state 5, link 100Mbps full duplex
      === Filament sensors ===
      Extruder 0 sensor: position 0.00, no data received, no calibration data
      
      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        Were you able to reproduce it?

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        pabomanundefined 1 Reply Last reply Reply Quote 0
        • pabomanundefined
          paboman @dc42
          last edited by paboman

          @dc42

          not the same way, but yesterday i paused the print to change filament and the DWC become unreachable again.
          also the maestro freezed, I was unable to resume the print

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