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

    [3.3.0] My tool disappeared after 3.3.0 install (?)

    Scheduled Pinned Locked Moved
    Firmware installation
    4
    8
    457
    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.
    • paralepsisundefined
      paralepsis
      last edited by

      I've got a recently upgraded Makerbot R2X that has a Duet Wifi brain now. Was printing well on 3.2.2. Upon installation of 3.3, the "HotEnd" tool is no longer visible in the web UI nor in PanelDue 5i.

      Configuration and M122 below.

      Help :)! Thanks,

      Rob

      Screen Shot 2021-06-17 at 8.10.38 PM.png

      ; Configuration file for Duet WiFi (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 29 2021 06:56:32 GMT-0500 (Central Daylight Time)
      
      ; General preferences
      G90                                            ; send absolute coordinates...
      M83                                            ; ...but relative extruder moves
      M550 P"Peanut"                                 ; 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 backwards (lazy wiring!)
      M569 P1 S1                                     ; 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 X88.89 Y88.89 Z400.00 E96.27520187         ; set steps per mm
      M566 X900.00 Y900.00 Z600.00 E1200.00          ; set maximum instantaneous speed changes (mm/min)
      M203 X18000.00 Y18000.00 Z1170.00 E1600.00     ; set maximum speeds (mm/min)
      M201 X1000.00 Y1000.00 Z150.00 E2000.00        ; set accelerations (mm/s^2)
      M906 X550 Y600 Z400 E800 I30                   ; set motor currents (mA) and motor idle factor in per cent
      ; M906 X800 Y800 Z400 E800 I30
      M84 S30                                        ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1                               ; set axis minima
      M208 X275 Y150 Z150 S0                         ; set axis maxima. Note X>250 is not on build plate...
      
      ; Endstops
      M574 X2 S1 P"!xstop"                           ; configure active-low endstop for high end on X via pin (!)xstop
      M574 Y2 S1 P"!ystop"                           ; configure active-low endstop for high end on Y via pin (!)ystop
      M574 Z1 S1 P"!zstop"                           ; configure active-low endstop for low end on Z via pin (!)zstop
      
      ; Z-Probe
      ;M558 P0 H5 F120 T6000                          ; disable Z probe but set dive height, probe speed and travel speed
      ;M557 X15:215 Y15:150 S20                       ; define mesh grid
      
      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4066 A"Bed[C]" ; 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.897 C158.7 D1.38 S1.00 V23.9 B0     ; from M303 H0 S115
      M307 H0 R0.6 C158.7 D1.38 S1.00 V23.9 B0     ; from M303 H0 S115 (modified)
      M140 H0                                        ; map heated bed to heater 0
      M143 H0 S120                                   ; set temperature limit for heater 0 to 120C
      M308 S1 P"spi.cs2" Y"thermocouple-max31856" A"HotEnd[C]"
      M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 R2.244 C198.3 D5.75 S1.00 V24.0        ; from M303 H1 S250
      M143 H1 S280                                   ; set temperature limit for heater 1 to 280C
      
      ; MCU Temp and TMC drivers -- need this before we set up the fan
      M308 S10 Y"mcu-temp" A"MCUTemp[C]"
      M308 S11 Y"drivers" A"TMC[Warning]"
      M308 S12 P"e1temp" Y"thermistor" T100000 B4092 A"PwrSupply[C]"
      
      ; Fans
      M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S1.0 H1 T45 C"HotEnd"                  ; set fan 0 value. Thermostatic control is turned on
      M950 F2 C"fan2" Q100
      M106 P2 S1.0 B0.5 L0.4 T35:40 H10:11 C"Duet"      ; turn on the fan if we get a warning from TMC or the MCU gets hot
      ;M106 P2 S0.2 C"Duet"                             ; turn on the fan all the time
      
      ; Tools
      M563 P0 S"HotEnd" D0 H1 F-1                    ; define tool 0, no part cooling fan
      G10 P0 X0 Y0 Z0                                ; set tool 0 axis offsets
      G10 P0 R0 S0                                   ; set initial tool 0 active and standby temperatures to 0C
      
      ; DHT22 (pin 1 +V, pin 2 GND, pin 4 (E2 Stop) Data)
      M308 S2 P"exp.e2_stop" Y"dht22" A"AmbTemp[C]"
      M308 S3 P"S2.1" Y"dhthumidity" A"AmbHumid[%]"
      
      ; LEDs: assign e1heat, treat as a fan so we get a slider, turn them on, name them
      M950 F3 C"e1heat" Q500
      M106 P3 S255 C"Lights"
      
      ; Custom settings are not defined
      
      ; Miscellaneous
      M575 P1 S1 B57600                              ; enable support for PanelDue
      T0                                             ; select first tool
      
      6/17/2021, 7:40:37 PM 	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
      Board ID: 08DDM-9FAM2-LW4SD-6JKD2-3S86R-KLW7X
      Used output buffers: 3 of 24 (19 max)
      === RTOS ===
      Static ram: 23876
      Dynamic ram: 75916 of which 332 recycled
      Never used RAM 11436, free system stack 122 words
      Tasks: NETWORK(ready,14.1%,244) SENSORS(delaying,0.0%,80) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,313) MAIN(running,85.6%,407) IDLE(ready,0.1%,29), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:15:10 ago, cause: software
      Last software reset at 2021-06-11 05:59, reason: User, GCodes spinning, available RAM 14012, slot 1
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Step timer max interval 0
      MCU temperature: min 32.6, current 34.5, max 36.0
      Supply voltage: min 24.0, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0
      Driver 0: position 24000, standstill, SG min/max 0/206
      Driver 1: position 12889, standstill, SG min/max 0/154
      Driver 2: position 2000, standstill, SG min/max 0/493
      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-06-17 19:40:36
      Cache data hit count 4294967295
      Slowest loop: 8.26ms; fastest: 0.14ms
      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.2ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 63073ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 17, completed moves 17, 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: 15.83ms; 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 2c:3a:e8:0b:36:69
      WiFi Vcc 3.46, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 25120
      WiFi IP address 192.168.1.220
      WiFi signal strength -65dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      

      Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

      1 Reply Last reply Reply Quote 0
      • paralepsisundefined
        paralepsis
        last edited by

        @paralepsis said in [3.3.0] My tool disappeared after 3.3.0 install (?):

        M563 P0 S"HotEnd" D0 H1 F-1 ; define tool 0, no part cooling fan

        To solve my own problem, it's that "F-1" in the M563 line.

        How do I correctly define there to be no part fan?

        Thanks!

        Rob

        Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

        Nuramoriundefined dc42undefined 2 Replies Last reply Reply Quote 0
        • Nuramoriundefined
          Nuramori @paralepsis
          last edited by

          @paralepsis I believe you simply don’t define a fan by removing the “F-1”

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

            I'd be curious to see what errors if any get reported by sending M98 P"config.g" with the F-1 in place.

            Z-Bot CoreXY Build | Thingiverse Profile

            paralepsisundefined 1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators @paralepsis
              last edited by

              @paralepsis said in [3.3.0] My tool disappeared after 3.3.0 install (?):

              How do I correctly define there to be no part fan?

              What are you trying to achieve? If you want M106 commands in the GCode file being printed to be ignored for that tool, then you would have to define a dummy fan number and use that in the M563 command. If you don't specify a fan number at all in M563, then M106 without a P parameter will default to controlling fan 0 when that tool is active.

              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

              paralepsisundefined 1 Reply Last reply Reply Quote 0
              • paralepsisundefined
                paralepsis @dc42
                last edited by

                @dc42 I'm trying to avoid having my fan spuriously controlled during prints. I think the right thing is for me to just not use fan 0 but rather to define that fan to another "position" so that it doesn't matter.

                Thanks.

                Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

                dc42undefined 1 Reply Last reply Reply Quote 0
                • paralepsisundefined
                  paralepsis @Phaedrux
                  last edited by

                  @phaedrux said in [3.3.0] My tool disappeared after 3.3.0 install (?):

                  I'd be curious to see what errors if any get reported by sending M98 P"config.g" with the F-1 in place.

                  This is something I can answer :):

                  Error: in file macro line 70 column 28: M563: expected number after 'F'
                  

                  Of course I wasn't seeing that on the console when I booted.

                  Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @paralepsis
                    last edited by dc42

                    I'm trying to avoid having my fan spuriously controlled during prints. I think the right thing is for me to just not use fan 0 but rather to define that fan to another "position" so that it doesn't matter.

                    @paralepsis I think you can achieve that by not creating fan number 0, i.e. do not use a M950 H0 command; or if you want o be explicit, use M950 F0 C"nil".

                    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

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