Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    [3.4-b5] Heaters off on start up?

    Beta Firmware
    2
    9
    145
    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.
    • jumpedwithbothfeet
      jumpedwithbothfeet last edited by

      Morning all, I've just noticed my heaters are now off on start up is this the norm on 3.4? I was under the impression the hot end heater starts active as a safety feature, have I missed it in the change logs? I did jump from 3.3 to 3.4b4/5 so more than possible!

      Voron Trident based (4Z) - too much to list!

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

        @jumpedwithbothfeet do you really mean heaters, or do you mean fans?

        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

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

          @dc42 I really mean the heaters but mainly the hot end heater always used to start in active but ambient temp and 0 degrees requested so the heater doesn't actually heat now when turning on the printer it is set to off, I repeated this a few times to confirm, my fans work fine, hot end fan starts at 40 and stays on until it drops below.

          Voron Trident based (4Z) - too much to list!

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

            @jumpedwithbothfeet if you have a T0 command in config.g (usually at the end) then that tool will be activated and its heaters put in active mode. If you don't have a T command in config.g (or a M568 command to activate heaters deliberately) then no tool heaters should be activated.

            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

            jumpedwithbothfeet 3 Replies Last reply Reply Quote 0
            • jumpedwithbothfeet
              jumpedwithbothfeet @dc42 last edited by

              @dc42 I do have T0 at the end..

              ; Configuration file for Duet 3 (firmware version 3)
              ; executed by the firmware on start-up
              ;
              ; generated by RepRapFirmware Configuration Tool v2.1.8 on Mon Apr 06 2020 18:55:28 GMT+0100 (British Summer Time)
              
              ; General preferences
              G90                                         ; send absolute coordinates...
              M83                                         ; ...but relative extruder moves
              M550 P"Duet 3"                              ; set printer name
              G4 S1                                       ;wait for expansion boards to start
              M669 K1                                     ; select CoreXY mode
              M575 P1 S1 B57600                           ; paneldue
              ;M552 S1                                     ; Enable networking
              
              ; Drives
              M569 P0.0 S0                                ; physical drive 0.0 goes forwards
              M569 P0.1 S0                                ; physical drive 0.1 goes forwards
              M569 P0.2 S0                                ; physical drive 0.2 goes forwards
              M569 P0.3 S1                                ; physical drive 0.3 goes backwards
              M569 P0.4 S1                                ; physical drive 0.4 goes backwards
              M569 P0.5 S0                                ; physical drive 0.5 goes forwards
              M569 P121.0 S0                              ; physical drive tool board 1.1 goes forwards
              M584 X0.4 Y0.1 Z0.0:0.2:0.3:0.5 E121.0      ; set drive mapping
              M671 X-35:395:395:-35 Y420:420:-10:-10 S4 ; Z leadscrews locations
              M350 X16 Y16 Z16 E16 I1                     ; configure microstepping with interpolation
              M92 X80.00 Y80.00 Z800.00 E812.6            ; set steps per mm
              M566 X900.00 Y900.00 Z12.00 E120.00         ; set maximum instantaneous speed changes (mm/min)
              M203 X30000.00 Y30000.00 Z600.00 E3000.00   ; set maximum speeds (mm/min)
              M201 X5000.00 Y5000.00 Z20 E5000.00           ; set accelerations (mm/s^2)
              M906 X1200 Y1200 Z950 E850 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 X360 Y360 Z300 S0                      ; set axis maxima
              
              ; Endstops
              M574 X2 S1 P"io4.in"                        ; configure active-high endstop for low end on X via pin io4.in
              M574 Y2 S1 P"io5.in"                        ; configure active-high endstop for low end on Y via pin io5.in
              M574 Z1 S2                                  ; configure Z-probe endstop for low end on Z
              
              ; Z-Probe
              M950 S0 C"nil"                                   ; create servo pin 0 for Mini IR
              M558 P8 C"121.io2.in" H5 F120:60 T6000 R1 A3 S0.005 ; set Z probe type to Mini IR and the dive height + speeds
              G31 P50 X0 Y-30 Z2.954                   ; set Z probe trigger value, offset and trigger height
              M557 X50:320 Y40:300 S45:52                      ; define mesh grid
              
              ; Heaters
              M308 S0 P"temp0" Y"thermistor" A"Bed" T98801 B4185           ; configure sensor 0 as thermistor on pin temp0
              M950 H0 C"out0" T0                                    ; create bed heater output on out0 and map it to sensor 0
              M143 H0 S130                                          ; set temperature limit for heater 0 to 120C
              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
              M308 S1 P"121.TEMP_0" Y"thermistor" A"Hotend" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp2
              M950 H1 C"121.out0" T1                               ; create nozzle heater output on out1 and map it to sensor 1
              M143 H1 S300                                          ; set temperature limit for heater 1 to 350C
              M307 H1 B0 S1.00                                      ; disable bang-bang mode for heater  and set PWM limit
              M308 S2 P"mcu-temp" Y"mcu-temp" A"mcu-temp"           ; configure sensor 2 as thermistor on pin temp2
              ;M308 S3 P"temp1" Y"thermistor" A"Enclosure temp" T100000 B4725 C7.06e-8 ; configure sensor 3 as thermistor on pin temp1
              ;M308 S1 P"spi.cs0" Y"rtd-max31865"                    ; define temperature sensor number 1 as a PT100 on the first port of a temperature daughter
              
              ; Fans
              M950 F1 C"121.out2" Q500                                  ; create fan 1 on pin out.2(toolboard) and set its frequency (Hotend fan)
              M106 P1 H1 T40 C"Hotend fan"                              ; set fan 1 value. Thermostatic control is turned on
              M950 F0 C"121.out1" Q255                                  ; create fan 0 on pin out1(toolboard) and set its frequency (New parts fan)
              M106 P0 S0 H-1 C"Part cooling fan"                        ; set fan 0 value. Thermostatic control is turned off
              M950 F2 C"out7" Q500                                          ; create fan 2 on pin out.2  and set its frequency (Hotend fan)
              M106 P2 H1 T40 C"CPU fan"                                 ; set fan 2 value. Thermostatic control is turned on
              
              ; Tools
              M563 P0 S"V6" 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
              M912 P0 S-7.9
              M955 P121.0 I05
              ;M593 F40.5  ; cancel ringing at 40.5Hz
              
              ; Miscellaneous
              M501                                        ; load saved parameters from non-volatile memory
              T0                                          ; select first tool
              
              
              

              Voron Trident based (4Z) - too much to list!

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

                @dc42 Further to the config file, I have been on occasion experiencing the tool board not starting when turning on the printer this is solved by pressing the stop button and it jumps into action but obviously it does connect when the heaters are shown in DWC

                25/10/2021, 11:06:50	M122
                === Diagnostics ===
                RepRapFirmware for Duet 3 MB6HC version 3.4.0beta5 (2021-10-12 13:53:56) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
                Board ID: 08DJM-956L2-G43S8-6JKDG-3SS6L-KB12H
                Used output buffers: 4 of 40 (20 max)
                === RTOS ===
                Static ram: 151104
                Dynamic ram: 65928 of which 328 recycled
                Never used RAM 133312, free system stack 200 words
                Tasks: SBC(ready,0.6%,520) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,299) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,8.0%,92) MAIN(running,90.5%,921) IDLE(ready,0.9%,30), total 100.0%
                Owned mutexes: HTTP(MAIN)
                === Platform ===
                Last reset 00:04:44 ago, cause: software
                Last software reset at 2021-10-25 11:01, reason: User, none spinning, available RAM 133312, slot 1
                Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
                Error status: 0x00
                Aux0 errors 0,0,0
                Step timer max interval 134
                MCU temperature: min 31.3, current 33.3, max 44.6
                Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
                12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
                Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                Driver 0: pos 0, standstill, SG min/max 0/0, reads 16704, writes 14 timeouts 0
                Driver 1: pos 0, standstill, SG min/max 0/0, reads 16704, writes 14 timeouts 0
                Driver 2: pos 0, standstill, SG min/max 0/0, reads 16704, writes 14 timeouts 0
                Driver 3: pos 0, standstill, SG min/max 0/0, reads 16704, writes 14 timeouts 0
                Driver 4: pos 0, standstill, SG min/max 0/0, reads 16704, writes 14 timeouts 0
                Driver 5: pos 0, standstill, SG min/max 0/0, reads 16704, writes 14 timeouts 0
                Date/time: 2021-10-25 11:06:38
                Slowest loop: 1.55ms; fastest: 0.05ms
                === Storage ===
                Free file entries: 10
                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, comp offset 0.000
                === MainDDARing ===
                Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                === AuxDDARing ===
                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, chamberHeaters = -1 -1 -1 -1
                Heater 1 is on, I-accum = 0.0
                === GCodes ===
                Segments left: 0
                Movement lock held by 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 idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty
                === CAN ===
                Messages queued 2527, received 5555, lost 0, longest wait 2ms for reply type 6031, peak Tx sync delay 474, free buffers 49 (min 48), ts 1425/1424/0
                Tx timeouts 0,0,0,0,0,0
                === SBC interface ===
                State: 4, failed transfers: 0, checksum errors: 0
                Last transfer: 2ms ago
                RX/TX seq numbers: 12249/12249
                SPI underruns 0, overruns 0
                Disconnects: 0, timeouts: 0, IAP RAM available 0x2b7b0
                Buffer RX/TX: 0/0-0
                === Duet Control Server ===
                Duet Control Server v3.4-b5
                Code buffer space: 4096
                Configured SPI speed: 8000000Hz
                Full transfers per second: 43.75, max wait times: 77.5ms/51.5ms
                Codes per second: 0.25
                Maximum length of RX/TX data transfers: 3008/812
                
                25/10/2021, 11:07:26	M122 B121
                Diagnostics for board 121:
                Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta5 (2021-10-12 13:59:06)
                Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
                Never used RAM 2576, free system stack 2789 words
                Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,99) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.9%,57) MAIN(running,91.9%,350) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
                Last reset 00:05:22 ago, cause: software
                Last software reset data not available
                Driver 0: pos 0, 812.6 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 22, reads 30305, writes 11, timeouts 1, DMA errors 0, failedOp 0x6a, steps req 0 done 0
                Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                Peak sync jitter 5/9, peak Rx sync delay 216, resyncs 0/0, no step interrupt scheduled
                VIN voltage: min 24.5, current 24.5, max 24.5
                MCU temperature: min 45.8C, current 46.8C, max 47.5C
                Last sensors broadcast 0x00000002 found 1 73 ticks ago, loop time 0
                CAN messages queued 6303, send timeouts 0, received 2860, lost 0, free buffers 37, min 37, error reg 100000
                dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
                Accelerometer detected: yes, status: 00
                I2C bus errors 0, naks 3, other errors 0
                

                Voron Trident based (4Z) - too much to list!

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

                  @dc42 I've just restarted the printer again and carried out M122 and M122 B121 the heater is shown off on start up..

                  25/10/2021, 11:10:18	M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 3 MB6HC version 3.4.0beta5 (2021-10-12 13:53:56) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
                  Board ID: 08DJM-956L2-G43S8-6JKDG-3SS6L-KB12H
                  Used output buffers: 1 of 40 (17 max)
                  === RTOS ===
                  Static ram: 151104
                  Dynamic ram: 65928 of which 328 recycled
                  Never used RAM 133312, free system stack 200 words
                  Tasks: SBC(ready,0.3%,514) HEAT(notifyWait,0.0%,347) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,88.7%,921) IDLE(ready,3.1%,30), total 100.0%
                  Owned mutexes: HTTP(MAIN)
                  === Platform ===
                  Last reset 00:01:02 ago, cause: power up
                  Last software reset at 2021-10-25 11:01, reason: User, none spinning, available RAM 133312, slot 1
                  Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
                  Error status: 0x00
                  Aux0 errors 0,0,0
                  Step timer max interval 132
                  MCU temperature: min 34.7, current 35.3, max 43.0
                  Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
                  12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
                  Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                  Driver 0: pos 0, standstill, SG min/max 0/0, reads 22617, writes 14 timeouts 0
                  Driver 1: pos 0, standstill, SG min/max 0/0, reads 22617, writes 14 timeouts 0
                  Driver 2: pos 0, standstill, SG min/max 0/0, reads 22617, writes 14 timeouts 0
                  Driver 3: pos 0, standstill, SG min/max 0/0, reads 22617, writes 14 timeouts 0
                  Driver 4: pos 0, standstill, SG min/max 0/0, reads 22618, writes 14 timeouts 0
                  Driver 5: pos 0, standstill, SG min/max 0/0, reads 22618, writes 14 timeouts 0
                  Date/time: 2021-10-25 11:10:09
                  Slowest loop: 1.24ms; fastest: 0.04ms
                  === Storage ===
                  Free file entries: 10
                  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, comp offset 0.000
                  === MainDDARing ===
                  Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                  === AuxDDARing ===
                  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, chamberHeaters = -1 -1 -1 -1
                  === GCodes ===
                  Segments left: 0
                  Movement lock held by 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 idle in state(s) 0
                  Autopause is idle in state(s) 0
                  Code queue is empty
                  === CAN ===
                  Messages queued 480, received 967, lost 0, longest wait 3ms for reply type 6049, peak Tx sync delay 5, free buffers 49 (min 48), ts 314/313/0
                  Tx timeouts 0,0,0,0,0,0
                  === SBC interface ===
                  State: 4, failed transfers: 1, checksum errors: 0
                  Last transfer: 2ms ago
                  RX/TX seq numbers: 1005/1005
                  SPI underruns 0, overruns 0
                  Disconnects: 1, timeouts: 1, IAP RAM available 0x2b7dc
                  Buffer RX/TX: 0/0-0
                  === Duet Control Server ===
                  Duet Control Server v3.4-b5
                  Code buffer space: 4096
                  Configured SPI speed: 8000000Hz
                  Full transfers per second: 9.04, max wait times: 95.7ms/75.0ms
                  Codes per second: 0.02
                  Maximum length of RX/TX data transfers: 2968/64
                  
                  25/10/2021, 11:12:26	M122 B121
                  Diagnostics for board 121:
                  Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta5 (2021-10-12 13:59:06)
                  Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
                  Never used RAM 2576, free system stack 2789 words
                  Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.9%,57) MAIN(running,91.9%,350) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
                  Last reset 00:03:11 ago, cause: power up
                  Last software reset data not available
                  Driver 0: pos 0, 812.6 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 12, reads 29982, writes 12, timeouts 0, DMA errors 0, steps req 0 done 0
                  Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                  Peak sync jitter 5/9, peak Rx sync delay 215, resyncs 0/0, no step interrupt scheduled
                  VIN voltage: min 16.2, current 24.5, max 24.5
                  MCU temperature: min 45.3C, current 47.0C, max 47.0C
                  Last sensors broadcast 0x00000002 found 1 97 ticks ago, loop time 0
                  CAN messages queued 3554, send timeouts 0, received 1643, lost 0, free buffers 37, min 37, error reg 0
                  dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
                  Accelerometer detected: yes, status: 00
                  I2C bus errors 0, naks 3, other errors 0
                  

                  Voron Trident based (4Z) - too much to list!

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

                    @jumpedwithbothfeet what do you have in config-oevrride.g?

                    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

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

                      @dc42 nothing of note I don't think... I have just started the printer to get this and the heater is active this time so it does appear intermittant.

                      ; config-override.g file generated in response to M500 at 2021-10-19 18:55
                      ; This is a system-generated file - do not edit
                      ; Heater model parameters
                      M307 H0 R0.224 C452.715:452.715 D7.32 S1.00 V24.1 B0 I0
                      M307 H1 R1.917 C230.500:230.500 D4.60 S1.00 V24.3 B0 I0
                      ; Workplace coordinates
                      G10 L2 P1 X0.00 Y0.00 Z0.00
                      G10 L2 P2 X0.00 Y0.00 Z0.00
                      G10 L2 P3 X0.00 Y0.00 Z0.00
                      G10 L2 P4 X0.00 Y0.00 Z0.00
                      G10 L2 P5 X0.00 Y0.00 Z0.00
                      G10 L2 P6 X0.00 Y0.00 Z0.00
                      G10 L2 P7 X0.00 Y0.00 Z0.00
                      G10 L2 P8 X0.00 Y0.00 Z0.00
                      G10 L2 P9 X0.00 Y0.00 Z0.00
                      

                      Voron Trident based (4Z) - too much to list!

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