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

    Can't use emergency stop button after update

    Scheduled Pinned Locked Moved
    General Discussion
    3
    12
    485
    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.
    • Bennyundefined
      Benny @jay_s_uk
      last edited by

      @jay_s_uk It used to come back on after

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

        @benny make sure you have M552 S1 in your config and it should. What board and firmware are you running?

        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

        Bennyundefined 1 Reply Last reply Reply Quote 0
        • Bennyundefined
          Benny @jay_s_uk
          last edited by

          @jay_s_uk said in Can't use emergency stop button after update:

          M552 S1

          Yea thats in there, wifi 1.4
          I've had it years now

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

            @benny post and output of M115.
            Also confirm the version of WiFi firmware you are running. This can be obtained from M122

            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

            Bennyundefined 1 Reply Last reply Reply Quote 0
            • Bennyundefined
              Benny @jay_s_uk
              last edited by Benny

              @jay_s_uk
              m115

              FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2021-06-15 21:45:03

              m122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
              Board ID: 08DGM-9T6BU-FG3SN-6JKD0-3S86K-9AZVF
              Used output buffers: 3 of 24 (14 max)
              === RTOS ===
              Static ram: 23876
              Dynamic ram: 76072 of which 12 recycled
              Never used RAM 14456, free system stack 112 words
              Tasks: NETWORK(ready,14.2%,236) HEAT(delaying,0.0%,208) Move(notifyWait,0.2%,309) DUEX(notifyWait,0.0%,24) MAIN(running,85.3%,420) IDLE(ready,0.3%,29), total 100.0%
              Owned mutexes: WiFi(NETWORK)
              === Platform ===
              Last reset 00:20:22 ago, cause: software
              Last software reset at 2021-08-02 19:06, reason: User, GCodes spinning, available RAM 14456, slot 1
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
              Error status: 0x10
              Step timer max interval 0
              MCU temperature: min 39.0, current 41.4, max 41.8
              Supply voltage: min 24.0, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
              Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
              Driver 0: position 0, standstill, SG min/max 0/1023
              Driver 1: position 0, standstill, SG min/max 0/1023
              Driver 2: position 22271, standstill, SG min/max 0/107
              Driver 3: position 0, standstill, SG min/max 0/1023
              Driver 4: position 0, standstill, SG min/max 0/102
              Driver 5: position 0, standstill, SG min/max not available
              Driver 6: position 0, standstill, SG min/max not available
              Driver 7: position 0, standstill, SG min/max not available
              Driver 8: position 0, standstill, SG min/max not available
              Driver 9: position 0, standstill, SG min/max not available
              Driver 10: position 0
              Driver 11: position 0
              Date/time: 2021-08-02 19:26:56
              Cache data hit count 4294967295
              Slowest loop: 220.39ms; fastest: 0.07ms
              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.9ms, write time 409.6ms, max retries 0
              === Move ===
              DMs created 83, maxWait 218101ms, bed compensation in use: mesh, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 471, completed moves 471, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 48], 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
              Heater 0 is on, I-accum = 0.0
              === 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.
              === DueX ===
              Read count 1, 0.05 reads/min
              === Network ===
              Slowest loop: 413.84ms; 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.26
                WiFi MAC address 84:f3:eb:42:b0:cb
                WiFi Vcc 3.36, reset reason Turned on by main processor
                WiFi flash size 4194304, free heap 25600
                WiFi IP address 192.168.50.163
                WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem
                Clock register 00002002
                Socket states: 0 0 0 0 0 0 0 0
              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Post your full config.g?

                Can you verify that your DWC version is also 3.3?

                Z-Bot CoreXY Build | Thingiverse Profile

                Bennyundefined 1 Reply Last reply Reply Quote 0
                • Bennyundefined
                  Benny @Phaedrux
                  last edited by

                  @phaedrux yea 3.3
                  ; Configuration file for Duet WiFi (firmware version 3)
                  ; executed by the firmware on start-up
                  ;
                  ; generated by RepRapFirmware Configuration Tool v3.1.4 on Thu Oct 22 2020 17:33:54 GMT+0100 (British Summer Time)

                  ; General preferences
                  G90 ; send absolute coordinates...
                  M83 ; ...but relative extruder moves
                  M550 P"HevORT" ; set printer name
                  M669 K1 ; select CoreXY mode

                  ; Network
                  M552 S1 ; enable network
                  M586 P0 S1 ; enable HTTP
                  M586 P1 S0 ; disable FTP
                  M586 P2 S0 ; disable Telnet
                  ;BED LEVEL
                  M671 X-30:330 Y200:200 S6

                  ; Drives
                  M569 P0 S0 ; physical drive 0 goes forwards
                  M569 P1 S1 ; physical drive 1 goes forwards
                  M569 P2 S0 ; physical drive 2 goes forwards
                  M569 P3 S1 ; physical drive 3 goes forwards
                  M569 P4 S0
                  M569 P5 S1 ; physical drive 5 goes forwards

                  M584 X0 Y1 Z2:4 E3:5 ; set drive mapping

                  M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
                  M92 X80.00 Y80.00 Z400.00 E397.28:419.00 ; set steps per mm
                  M566 X1500.00 Y1500.00 Z105.00 E900.00:3000.00 ; set maximum instantaneous speed changes (mm/min)
                  M203 X30000.00 Y30000.00 Z1200.00 E10000.00:18000.00 ; set maximum speeds (mm/min)
                  M201 X9000.00 Y9000.00 Z120.00 E4000.00:2000.00 ; set accelerations (mm/s^2)
                  M906 X1200 Y1200 Z1000 E1100:1000 I30 ; set motor currents (mA) and motor idle factor in per cent
                  ;M593 F34.2
                  M84 S30 ; Set idle timeout

                  ;M566 X400 Y400 Z8 C2 E2:2:2:2 ; Set maximum instantaneous speed changes (mm/min)
                  ;M203 X35000 Y35000 Z1200 C5000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min)
                  ;M201 X6000 Y6000 Z400 C500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2)
                  ;M906 X1800 Y1800 Z1330 I30 ; Idle motion motors to 30%

                  ; Axis Limits
                  M208 X-30 Y0 Z-5 S1 ; set axis minima
                  M208 X280 Y280 Z300 S0 ; set axis maxima

                  ; Endstops
                  M574 X1 S3 ; configure sensorless endstop for low end on X
                  M574 Y1 S3 ; configure sensorless endstop for low end on Y
                  M574 Z1 S2 ; configure Z-probe endstop for low end on Z

                  ; Z-Probe
                  M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch
                  M558 P9 C"^zprobe.in" H5 F120 T10000 ; set Z probe type to bltouch and the dive height + speeds
                  G31 P25 X60 Y-10 Z2.45 ; set Z probe trigger value, offset and trigger height
                  M557 X80:280 Y20:280 S60 ; define mesh grid

                  ; Heaters
                  M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 ; configure sensor 0 as thermistor on pin bedtemp
                  M950 H0 C"bedheat" T0 Q10 ; create bed heater output on bedheat and map it to sensor 0
                  M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
                  M140 H0 ; map heated bed to heater 0
                  M143 H0 S140 ; set temperature limit for heater 0 to 120C
                  M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; 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 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
                  M143 H1 S280

                  ; 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 S"BMG" 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
                  M563 P1 S"TITAN" D1 H1 F0 ; define tool 1
                  G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
                  G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

                  ; Custom settings are not defined

                  ; Miscellaneous
                  M501 ; load saved parameters from non-volatile memory
                  M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
                  T0 ; select first tool
                  M564 H0

                  1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    You say "after update" What firmware version were you using before?

                    You say when you connect USB power that the module instantly connects. What LEDs are lit before and after connecting USB?

                    Do you have multiple access points saved? Check with M587 by itself to see a list of added APs.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Bennyundefined 1 Reply Last reply Reply Quote 0
                    • Bennyundefined
                      Benny @Phaedrux
                      last edited by Benny

                      @phaedrux 3.2 i think , blue red and green.
                      yes Ive got multiple AP's on there.

                      Phaedruxundefined 1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @Benny
                        last edited by

                        @benny said in Can't use emergency stop button after update:

                        yes Ive got multiple AP's on there.

                        I would suggest removing all APs except the one you want it to connect to since it may be trying to connect to a different one that isn't actually able to connect for some reason. It tries to prioritize the AP with the highest signal strength.

                        Z-Bot CoreXY Build | Thingiverse Profile

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