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

    duet 2 wifi stop in printing

    Scheduled Pinned Locked Moved
    General Discussion
    3
    6
    261
    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.
    • flyingpig507undefined
      flyingpig507
      last edited by

      Hi, my DWC reconnect in printing then last progress was lost, the “status” display: No Job running.

      It is DIY Cartesian i3 style. Just stuck in there:
      1321902341.jpg

      Here's some information:

      Board: Duet 2 WiFi (2WiFi)
      Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11)
      Duet WiFi Server Version: 1.25

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
      Board ID: 0JD0M-9K662-MGPSS-6J9DL-3S86P-18V6Z
      Used output buffers: 3 of 24 (10 max)
      === RTOS ===
      Static ram: 23460
      Dynamic ram: 73228 of which 40 recycled
      Never used RAM 15352, free system stack 193 words
      Tasks: NETWORK(ready,183) HEAT(blocked,308) MAIN(running,449) IDLE(ready,20)
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:00:15 ago, cause: software
      Last software reset at 2021-04-26 21:28, reason: StuckInSpinLoop, GCodes spinning, available RAM 15108, slot 2
      Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200040ac Task MAIN Freestk 772 ok
      Stack: 0041f9c3 00459a3c 610f0200 3f800000 3d7df000 3edb6db7 b61cf800 49742404 3c3fdc9b 440739fd 40e190bc 0000bb9b 00000000 3e4fa932 41ddae4f 4e64e1c0 38533333 3f800000 3f800000 20000011 00000000 00000001 00000000 00000000 20002544 00000001 0041f9c3
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU temperature: min 32.6, current 33.3, max 33.5
      Supply voltage: min 24.8, current 25.0, max 25.2, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: position 0, standstill, SG min/max not available
      Driver 1: position 0, standstill, SG min/max not available
      Driver 2: position 0, standstill, SG min/max not available
      Driver 3: position 0, standstill, SG min/max not available
      Driver 4: position 0, standstill, SG min/max not available
      Driver 5: position 0
      Driver 6: position 0
      Driver 7: position 0
      Driver 8: position 0
      Driver 9: position 0
      Driver 10: position 0
      Driver 11: position 0
      Date/time: 2021-04-26 21:29:14
      Cache data hit count 17227880
      Slowest loop: 6.87ms; fastest: 0.21ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 1.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP is idle 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
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 177.94ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8

      • WiFi -
        Network state is active
        WiFi module is connected to access point
        Failed messages: pending 0, notready 0, noresp 0
        WiFi firmware version 1.25
        WiFi MAC address 50:02:91🇩🇪aa:53
        WiFi Vcc 3.49, reset reason Power up
        WiFi flash size 4194304, free heap 26568
        WiFi IP address 192.168.0.198
        WiFi signal strength -60dBm, mode 802.11n, reconnections 0, sleep mode modem
        Clock register 00002002
        Socket states: 0 0 0 0 0 0 0 0

      =================================================================
      config.g

      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"daZhu_i3" ; set printer name

      ; Network
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0 S0 ; physical drive 0 goes forwards
      M569 P1 S0 ; physical drive 1 goes forwards
      M569 P2 S1 ; physical drive 2 goes forwards
      M569 P3 S1 ; physical drive 3 goes forwards
      M584 X0 Y1 Z2 E3 ; set drive mapping
      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
      M92 X100.00 Y100.00 Z800.00 E381.92 ; set steps per mm
      M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X7200.00 Y7200.00 Z3600.00 E1800.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
      M906 X600 Y600 Z600 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X172 Y200 Z150 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
      M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
      M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop

      ; Z-Probe
      ; M558 P0 H5 F120 T7200 ; disable Z probe but set dive height, probe speed and travel speed
      ; M557 X15:190 Y15:195 S20 ; define mesh grid
      ; Z-Probe
      M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H5 F120 T3000 ; set Z probe type to bltouch and the dive height + speeds
      G31 P25 X-42.8 Y-5.5 Z3.011 ; set Z probe trigger value, offset and trigger height
      M557 X10:128 Y10:190 S118:180 ; define mesh grid

      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 R0.213 C685.2 D3.92 S1.00 V24.0 ; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0 ; map heated bed to heater 0
      M143 H0 S100 ; set temperature limit for heater 0 to 100C
      M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 R3.569 C137.0 D6.19 S1.00 V24.0 ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S280 ; set temperature limit for heater 1 to 280C

      ; Fans
      M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

      ; Tools
      M563 P0 D0 H1 F0 ; define tool 0
      G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
      G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

      ; Custom settings are not defined

      ; Miscellaneous
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

      Please help me, Thanks.

      felekundefined 1 Reply Last reply Reply Quote 0
      • felekundefined
        felek @flyingpig507
        last edited by

        @flyingpig507
        Hi!
        Did you have similar issue before?
        According to stack trace it looks like some sd card issue.
        Let's replace this sd card.

        alankilianundefined flyingpig507undefined 2 Replies Last reply Reply Quote 0
        • alankilianundefined
          alankilian @felek
          last edited by

          @felek I'm interested in learning more about how you come to this conclusion.

          I see:

          reason: StuckInSpinLoop, GCodes spinning
          

          And in RepRapFirmware-3.3beta3/src/Platform/RepRap.cpp" line 734 there is:

          ticksInSpinState = 0;
          spinningModule = moduleGcodes;
          gCodes->Spin();
          

          Which points me to whatever the method gCodes->Spin() is doing.

          SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

          felekundefined 1 Reply Last reply Reply Quote 0
          • felekundefined
            felek @alankilian
            last edited by

            @alankilian
            In M122 you have more precise information:

            Stack: 0041f9c3 00459a3c 610f0200 3f800000 3d7df000 3edb6db7 b61cf800 49742404 3c3fdc9b 440739fd 40e190bc 0000bb9b 00000000 3e4fa932 41ddae4f 4e64e1c0 38533333 3f800000 3f800000 20000011 00000000 00000001 00000000 00000000 20002544 00000001 0041f9c3
            

            Next step is download file with map file. You need to do it for your board and firmware version.
            In your case it is this zip file https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Symbols-RepRapFirmware-Duet2.zip

            There is .map file which include functions addresses in memory.
            Then you need to compare your stack address and map file function address.

            1 Reply Last reply Reply Quote 1
            • flyingpig507undefined
              flyingpig507 @felek
              last edited by

              @felek
              This is my TF
              571916773.jpg
              This duet board I used almost a year ago. It's been good before (Firmware 1.x). Similar problems was happen until I update Firmware.
              I not sure always used this TF, maybe changed it...
              I will chang other TF try again.
              Thanks you.

              1 Reply Last reply Reply Quote 0
              • flyingpig507undefined
                flyingpig507
                last edited by

                I changed TF, it is fine. thank felek (。・∀・)ノ゙

                1 Reply Last reply Reply Quote 1
                • sgereviniundefined sgerevini referenced this topic
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA