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

    RRF 3.5B2 Error: No bed heater has been configured for slot 0

    Beta Firmware
    4
    11
    309
    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.
    • jp.douarvil 0undefined
      jp.douarvil 0
      last edited by jp.douarvil 0

      Hello all,

      I use RRF 3.5B2 on Duet 3 in standalone mode on a cartesian FFF machine. I used to reserve the heater slot 0~9 for the extruder heaters and 10 for the bed. In my case, this way of allocating the heater number makes the difference between extruders and bed heater very clear for the users.

      The below configuration worked smoothly on RRF 3.4

      ; Bed heater
M308 S10 P... Y...	; configure bed temperature sensor
M950 H10 C... T10 	; create bed heater
M140 H10		; map temp sensor to heater
;M140 H10 P0		; same as above
M143 H10 S...		; set bed temperature limit
M307 H10 R... K... D... E... S1.00 B0	; heater tuning parameters

; Extruder 0 heater
M308 S0 P... Y...	; configure E0 temperature sensor
M950 H0 C... T0		; create nozzle heater
M143 P0 H0 S...		; set heater temperature limit
M307 H0 R... K... D... E... S1.00 B0 V...	; heater tuning parameters
M570 H0 P10 T15	; configure heater fault detection

; Extruder 1 heater
M308 S1 P... Y...	; configure E1 temperature sensor
M950 H1 C... T1		; create nozzle heater
M143 P1 H1 S...		; set heater temperature limit
M307 H1 R... K... D... E... S1.00 B0 V...	; heater tuning parameters
M570 H1 P10 T15	; configure heater fault detection

...

      The same configuration still works (M140 behavior hasn't changed) on the 3.5B2 but the bed heater does not appears properly on the dashboard, as you can see below.

      df53e0d5-37e2-4e91-bf3f-d1d63ebc25f4-image.png

      The dashboard temperature command does not work as expected:

      • bed heater is not recognized by the dashboard (shows heater #-1)
        -> temperatures set up using the M140 SXXX RYYY commands are not being reflected on the corresponding active/standby controls of the dashboard
        -> dashboard's bed heater controls are unresponsive (can't turn ON/OFF/Standby, can't set up the temperature using the dashboard)

      On the other hand replacing the line 4 with M140 H10 with M140 P10 H10 will solve the dashboard control issue. But then, everytime I need to setup the bed temperature through GCODE, I have to remember to indicate the slot number (M140 P10 SXXX RYYY) to avoid triggering an Error: No bed heater has been configured for slot 0 error.
      This new behavior appears to needlessly complicate user's experience without obvious benefit. Plus, depending on the slicer used, the P10 parameter can be quite annoying to robustly implement.

      Is that a bug or is there a practical reason why the DWC's behavior changed in the way described above?

      Thank you in advance for your help.

      Regards,

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

        Is your DWC up to date as well?

        Z-Bot CoreXY Build | Thingiverse Profile

        jp.douarvil 0undefined 1 Reply Last reply Reply Quote 0
        • jp.douarvil 0undefined
          jp.douarvil 0 @Phaedrux
          last edited by

          @Phaedrux Hello,

          According to the info in Settings > General I am currently using the version Duet Web Control 3.5.0-beta.2. It is the version delivered with RRF Beta2 I took from there:
          https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0beta2
          I haven't tried the 3.5.0-b2+ yet, should I?

          Prior to that, when DWC was working as expected, I was using the version Duet Web Control 3.4.2.

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

            Can you share the full config.g?
            Also please send M122 and M98 P"config.g" and copy paste the results here.

            Z-Bot CoreXY Build | Thingiverse Profile

            jp.douarvil 0undefined 1 Reply Last reply Reply Quote 0
            • jp.douarvil 0undefined
              jp.douarvil 0 @Phaedrux
              last edited by jp.douarvil 0

              edit: attached config.g file is erroneous, this post may be ignored.

              original post:

              @Phaedrux Hello,

              Attached is a "minimal" configuration exhibiting the issue.
              config.g

              And below the extract of the eventlog in debug mode following the >execution of an M122 and M98 P"config.g".

              2023-03-27 17:51:17 [info] Event logging started at level debug

;M122 response

2023-03-27 17:51:17 [info] Running: Duet 3 MB6HC v1.01: 3.5beta2 (2023-02-08 17:43:01)
2023-03-27 17:51:49 [debug] === Diagnostics ===
2023-03-27 17:51:49 [debug] RepRapFirmware for Duet 3 MB6HC version 3.5beta2 (2023-02-08 17:43:01) running on Duet 3 MB6HC v1.01 (standalone mode)
2023-03-27 17:51:49 [debug] Board ID: 08DJM-956BA-NA3TN-6JKDG-3S86S-TUB6S
2023-03-27 17:51:49 [debug] Used output buffers: 1 of 40 (18 max)
2023-03-27 17:51:49 [debug] === RTOS ===
2023-03-27 17:51:49 [debug] Static ram: 154344
2023-03-27 17:51:49 [debug] Dynamic ram: 117024 of which 0 recycled
2023-03-27 17:51:49 [debug] Never used RAM 71248, free system stack 206 words
2023-03-27 17:51:49 [debug] Tasks:
2023-03-27 17:51:49 [debug]  NETWORK(ready,30.4%,254)
2023-03-27 17:51:49 [debug]  ETHERNET(notifyWait,0.1%,443)
2023-03-27 17:51:49 [debug]  HEAT(notifyWait,0.0%,321)
2023-03-27 17:51:49 [debug]  Move(notifyWait,0.0%,342)
2023-03-27 17:51:49 [debug]  CanReceiv(notifyWait,0.0%,943)
2023-03-27 17:51:49 [debug]  CanSender(notifyWait,0.0%,335)
2023-03-27 17:51:49 [debug]  CanClock(delaying,0.0%,334)
2023-03-27 17:51:49 [debug]  TMC(notifyWait,8.1%,90)
2023-03-27 17:51:49 [debug]  MAIN(running,61.3%,446)
2023-03-27 17:51:49 [debug]  IDLE(ready,0.0%,30)
2023-03-27 17:51:49 [debug] , total 100.0%
Owned mutexes:
2023-03-27 17:51:49 [debug] === Platform ===
2023-03-27 17:51:49 [debug] Last reset 00:07:05 ago, cause: software
2023-03-27 17:51:49 [debug] Last software reset at 2023-03-27 17:44, reason: User, Gcodes spinning, available RAM 71396, slot 2
2023-03-27 17:51:49 [debug] Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
2023-03-27 17:51:49 [debug] Error status: 0x00
2023-03-27 17:51:49 [debug] Step timer max interval 150
2023-03-27 17:51:49 [debug] MCU temperature: min 32.7, current 33.6, max 33.8
2023-03-27 17:51:49 [debug] Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
2023-03-27 17:51:49 [debug] 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
2023-03-27 17:51:49 [debug] Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0
2023-03-27 17:51:49 [debug] Events: 0 queued, 0 completed
2023-03-27 17:51:49 [debug] Driver 0: standstill, SG min n/a, mspos 8, reads 11201, writes 14 timeouts 0
2023-03-27 17:51:49 [debug] Driver 1: standstill, SG min n/a, mspos 8, reads 11202, writes 14 timeouts 0
2023-03-27 17:51:49 [debug] Driver 2: standstill, SG min n/a, mspos 8, reads 11211, writes 14 timeouts 0
2023-03-27 17:51:49 [debug] Driver 3: standstill, SG min n/a, mspos 8, reads 11212, writes 14 timeouts 0
2023-03-27 17:51:49 [debug] Driver 4: standstill, SG min n/a, mspos 8, reads 11215, writes 11 timeouts 0
2023-03-27 17:51:49 [debug] Driver 5: standstill, SG min n/a, mspos 8, reads 11216, writes 11 timeouts 0
2023-03-27 17:51:49 [debug] Date/time: 
2023-03-27 17:51:49 [debug] 2023-03-27 17:51:49
2023-03-27 17:51:49 [debug] Slowest loop: 12.85ms; fastest: 0.06ms
2023-03-27 17:51:49 [debug] === Storage ===
Free file entries: 19
2023-03-27 17:51:49 [debug] SD card 0 detected, interface speed: 25.0MBytes/sec
2023-03-27 17:51:49 [debug] SD card longest read time 2.8ms, write time 1.7ms, max retries 0
2023-03-27 17:51:49 [debug] === Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
2023-03-27 17:51:49 [debug] no step interrupt scheduled
2023-03-27 17:51:49 [debug] === DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
2023-03-27 17:51:49 [debug] === DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
2023-03-27 17:51:49 [debug] === Heat ===
2023-03-27 17:51:49 [debug] Bed heaters 10 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
2023-03-27 17:51:49 [debug] === GCodes ===
2023-03-27 17:51:49 [debug] Movement locks held by null, null
2023-03-27 17:51:49 [debug] HTTP is idle in state(s) 0
2023-03-27 17:51:49 [debug] Telnet is idle in state(s) 0
2023-03-27 17:51:49 [debug] File is idle in state(s) 0
2023-03-27 17:51:49 [debug] USB is idle in state(s) 0
2023-03-27 17:51:49 [debug] Aux is idle in state(s) 0
2023-03-27 17:51:49 [debug] Trigger is idle in state(s) 0
2023-03-27 17:51:49 [debug] Queue is idle in state(s) 0
2023-03-27 17:51:49 [debug] LCD is idle in state(s) 0
2023-03-27 17:51:49 [debug] SBC is idle in state(s) 0
2023-03-27 17:51:49 [debug] Daemon is idle in state(s) 0
2023-03-27 17:51:49 [debug] Aux2 is idle in state(s) 0
2023-03-27 17:51:49 [debug] Autopause is idle in state(s) 0
2023-03-27 17:51:49 [debug] File2 is idle in state(s) 0
2023-03-27 17:51:49 [debug] Queue2 is idle in state(s) 0
2023-03-27 17:51:49 [debug] Q0 segments left 0, axes/extruders owned 0x0000000
2023-03-27 17:51:49 [debug] Code queue 0 is empty
2023-03-27 17:51:49 [debug] Q1 segments left 0, axes/extruders owned 0x0000000
2023-03-27 17:51:49 [debug] Code queue 1 is empty
2023-03-27 17:51:49 [debug] === CAN ===
2023-03-27 17:51:49 [debug] Messages queued 3832, received 0, lost 0, boc 0
2023-03-27 17:51:49 [debug] Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 2130/0/0
2023-03-27 17:51:49 [debug] Tx timeouts 0,0,2129,0,0,1701 last cancelled message type 30 dest 127
2023-03-27 17:51:49 [debug] === Network ===
2023-03-27 17:51:49 [debug] Slowest loop: 4.63ms; fastest: 0.03ms
2023-03-27 17:51:49 [debug] Responder states:
2023-03-27 17:51:49 [debug]  MQTT(0)
2023-03-27 17:51:49 [debug]  HTTP(0)
2023-03-27 17:51:49 [debug]  HTTP(0)
2023-03-27 17:51:49 [debug]  HTTP(0)
2023-03-27 17:51:49 [debug]  HTTP(0)
2023-03-27 17:51:49 [debug]  HTTP(0)
2023-03-27 17:51:49 [debug]  HTTP(0)
2023-03-27 17:51:49 [debug]  FTP(0)
2023-03-27 17:51:49 [debug]  Telnet(0)
2023-03-27 17:51:49 [debug]  Telnet(0)
2023-03-27 17:51:49 [debug] HTTP sessions: 1 of 8
2023-03-27 17:51:49 [debug] = Ethernet =
State: active
2023-03-27 17:51:49 [debug] Error counts: 0 0 0 1 0 0
Socket states:
2023-03-27 17:51:49 [debug]  5
2023-03-27 17:51:49 [debug]  2
2023-03-27 17:51:49 [debug]  2
2023-03-27 17:51:49 [debug]  2
2023-03-27 17:51:49 [debug]  2
2023-03-27 17:51:49 [debug]  0
2023-03-27 17:51:49 [debug]  0
2023-03-27 17:51:49 [debug]  0
2023-03-27 17:51:49 [debug] === Multicast handler ===
Responder is inactive, messages received 0, responses 0



;M98 P"config.g" response


2023-03-27 17:51:58 [warn] Warning: M918: Command is not supported
2023-03-27 17:51:58 [debug] HTTP is enabled on port 80
2023-03-27 17:51:58 [debug] FTP is disabled
2023-03-27 17:51:58 [debug] TELNET is disabled
2023-03-27 17:51:58 [warn] Warning: Sensor number 0 has not been defined
2023-03-27 17:51:58 [info] G10 P0 X0 Y0 Z0                              
2023-03-27 17:51:58 [info] G10 P0 R0 S0
              droftartsundefined 1 Reply Last reply Reply Quote 0
              • droftartsundefined
                droftarts administrators @jp.douarvil 0
                last edited by droftarts

                @jp-douarvil-0 This is the bed settings from your attached config.g:

                M308 S10 P"temp0" Y"pt1000" ;Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0
M950 H10 C"out0" T0                           ; create bed heater output on out0 and map it to sensor 0

                You created sensor 10 with M308 S10 ..., but are referring to sensor 0 with M950 H10 ... T0. That's why you get the message with M98 P"config.g":

                2023-03-27 17:51:58 [warn] Warning: Sensor number 0 has not been defined

                Change the M950 line to T10.

                This error:

                2023-03-27 17:51:58 [warn] Warning: M918: Command is not supported

                Is because you have M918 P1 E4 F2000000 ; configure direct-connect display in your config.g. 12864 displays are not supported on MB6HC.

                Ian

                Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard

                jp.douarvil 0undefined 1 Reply Last reply Reply Quote 0
                • jp.douarvil 0undefined
                  jp.douarvil 0 @droftarts
                  last edited by

                  @droftarts Hello,

                  Thank you for the feedback.

                  I profusely apologize for posting an erroneous config.g file.

                  The issue doesn't actually go away after correcting it.

                  Let me share the corrected config.g and the corresponding eventlog after:

                  • execution of M122
                  • execution of M98 P"config.g"
                  • set the temperature to 70C via the dashboard --> error
                  • set the temperature to 60C via a test print file BedHeaterTest.gcode containing only the command M140 S60 P10 --> error
                  • set the temperature via M140 S50 --> no error but the set temperature (50C) is not reflected on the dashboard as show on the capture below

                  ce4e4c58-db88-44f7-a433-fee2266cf402-image.png

                  config.g

                  eventlog.txt

                  2023-03-29 17:01:50 [info] Event logging started at level debug


;M122 response


2023-03-29 17:01:50 [info] Running: Duet 3 MB6HC v1.01: 3.5beta2 (2023-02-08 17:43:01)
2023-03-29 17:01:56 [debug] === Diagnostics ===
2023-03-29 17:01:56 [debug] RepRapFirmware for Duet 3 MB6HC version 3.5beta2 (2023-02-08 17:43:01) running on Duet 3 MB6HC v1.01 (standalone mode)
2023-03-29 17:01:56 [debug] Board ID: 08DJM-956BA-NA3TN-6JKDG-3S86S-TUB6S
2023-03-29 17:01:56 [debug] Used output buffers: 1 of 40 (29 max)
2023-03-29 17:01:56 [debug] === RTOS ===
2023-03-29 17:01:56 [debug] Static ram: 154344
2023-03-29 17:01:56 [debug] Dynamic ram: 117436 of which 0 recycled
2023-03-29 17:01:56 [debug] Never used RAM 73692, free system stack 200 words
2023-03-29 17:01:56 [debug] Tasks:
2023-03-29 17:01:56 [debug]  NETWORK(ready,30.6%,194)
2023-03-29 17:01:56 [debug]  ETHERNET(notifyWait,0.1%,441)
2023-03-29 17:01:56 [debug]  HEAT(notifyWait,0.0%,318)
2023-03-29 17:01:56 [debug]  Move(notifyWait,0.0%,342)
2023-03-29 17:01:56 [debug]  CanReceiv(notifyWait,0.0%,773)
2023-03-29 17:01:56 [debug]  CanSender(notifyWait,0.0%,335)
2023-03-29 17:01:56 [debug]  CanClock(delaying,0.0%,340)
2023-03-29 17:01:56 [debug]  TMC(notifyWait,8.1%,90)
2023-03-29 17:01:56 [debug]  MAIN(running,61.2%,446)
2023-03-29 17:01:56 [debug]  IDLE(ready,0.0%,30)
2023-03-29 17:01:56 [debug] , total 100.0%
Owned mutexes:
2023-03-29 17:01:56 [debug]  LwipCore(NETWORK)
2023-03-29 17:01:56 [debug] === Platform ===
2023-03-29 17:01:56 [debug] Last reset 00:28:25 ago, cause: software
2023-03-29 17:01:56 [debug] Last software reset at 2023-03-29 16:33, reason: User, Gcodes spinning, available RAM 69940, slot 0
2023-03-29 17:01:56 [debug] Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
2023-03-29 17:01:56 [debug] Error status: 0x00
2023-03-29 17:01:56 [debug] Step timer max interval 129
2023-03-29 17:01:56 [debug] MCU temperature: min 35.8, current 36.0, max 36.6
2023-03-29 17:01:56 [debug] Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
2023-03-29 17:01:56 [debug] 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
2023-03-29 17:01:56 [debug] Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
2023-03-29 17:01:56 [debug] Events: 2 queued, 2 completed
2023-03-29 17:01:56 [debug] Driver 0: standstill, SG min n/a, mspos 8, reads 35243, writes 3 timeouts 0
2023-03-29 17:01:56 [debug] Driver 1: standstill, SG min n/a, mspos 8, reads 35242, writes 3 timeouts 0
2023-03-29 17:01:56 [debug] Driver 2: standstill, SG min n/a, mspos 8, reads 35243, writes 3 timeouts 0
2023-03-29 17:01:56 [debug] Driver 3: standstill, SG min n/a, mspos 8, reads 35243, writes 3 timeouts 0
2023-03-29 17:01:56 [debug] Driver 4: standstill, SG min n/a, mspos 8, reads 35246, writes 0 timeouts 0
2023-03-29 17:01:56 [debug] Driver 5: standstill, SG min n/a, mspos 8, reads 35246, writes 0 timeouts 0
2023-03-29 17:01:56 [debug] Date/time: 
2023-03-29 17:01:56 [debug] 2023-03-29 17:01:56
2023-03-29 17:01:56 [debug] Slowest loop: 18.15ms; fastest: 0.06ms
2023-03-29 17:01:56 [debug] === Storage ===
Free file entries: 19
2023-03-29 17:01:56 [debug] SD card 0 detected, interface speed: 25.0MBytes/sec
2023-03-29 17:01:56 [debug] SD card longest read time 2.9ms, write time 3.8ms, max retries 0
2023-03-29 17:01:56 [debug] === Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
2023-03-29 17:01:56 [debug] no step interrupt scheduled
2023-03-29 17:01:56 [debug] === DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
2023-03-29 17:01:56 [debug] === DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
2023-03-29 17:01:56 [debug] === Heat ===
2023-03-29 17:01:56 [debug] Bed heaters 10 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
2023-03-29 17:01:56 [debug] === GCodes ===
2023-03-29 17:01:56 [debug] Movement locks held by null, null
2023-03-29 17:01:56 [debug] HTTP is idle in state(s) 0
2023-03-29 17:01:56 [debug] Telnet is idle in state(s) 0
2023-03-29 17:01:56 [debug] File is idle in state(s) 0
2023-03-29 17:01:56 [debug] USB is idle in state(s) 0
2023-03-29 17:01:56 [debug] Aux is idle in state(s) 0
2023-03-29 17:01:56 [debug] Trigger is idle in state(s) 0
2023-03-29 17:01:56 [debug] Queue is idle in state(s) 0
2023-03-29 17:01:56 [debug] LCD is idle in state(s) 0
2023-03-29 17:01:56 [debug] SBC is idle in state(s) 0
2023-03-29 17:01:56 [debug] Daemon is idle in state(s) 0
2023-03-29 17:01:56 [debug] Aux2 is idle in state(s) 0
2023-03-29 17:01:56 [debug] Autopause is idle in state(s) 0
2023-03-29 17:01:56 [debug] File2 is idle in state(s) 0
2023-03-29 17:01:56 [debug] Queue2 is idle in state(s) 0
2023-03-29 17:01:56 [debug] Q0 segments left 0, axes/extruders owned 0x0000000
2023-03-29 17:01:56 [debug] Code queue 0 is empty
2023-03-29 17:01:56 [debug] Q1 segments left 0, axes/extruders owned 0x0000000
2023-03-29 17:01:56 [debug] Code queue 1 is empty
2023-03-29 17:01:56 [debug] === CAN ===
2023-03-29 17:01:56 [debug] Messages queued 7789, received 6922, lost 0, boc 0
2023-03-29 17:01:56 [debug] Longest wait 0ms for reply type 0, peak Tx sync delay 21, free buffers 50 (min 50), ts 4327/4327/0
2023-03-29 17:01:56 [debug] Tx timeouts 0,0,0,0,0,0
2023-03-29 17:01:56 [debug] === Network ===
2023-03-29 17:01:56 [debug] Slowest loop: 34.82ms; fastest: 0.03ms
2023-03-29 17:01:56 [debug] Responder states:
2023-03-29 17:01:56 [debug]  MQTT(0)
2023-03-29 17:01:56 [debug]  HTTP(0)
2023-03-29 17:01:56 [debug]  HTTP(0)
2023-03-29 17:01:56 [debug]  HTTP(0)
2023-03-29 17:01:56 [debug]  HTTP(0)
2023-03-29 17:01:56 [debug]  HTTP(0)
2023-03-29 17:01:56 [debug]  HTTP(0)
2023-03-29 17:01:56 [debug]  FTP(0)
2023-03-29 17:01:56 [debug]  Telnet(0)
2023-03-29 17:01:56 [debug]  Telnet(0)
2023-03-29 17:01:56 [debug] HTTP sessions: 1 of 8
2023-03-29 17:01:56 [debug] = Ethernet =
State: active
2023-03-29 17:01:56 [debug] Error counts: 0 0 0 0 0 0
Socket states:
2023-03-29 17:01:56 [debug]  5
2023-03-29 17:01:56 [debug]  2
2023-03-29 17:01:56 [debug]  2
2023-03-29 17:01:56 [debug]  2
2023-03-29 17:01:56 [debug]  2
2023-03-29 17:01:56 [debug]  0
2023-03-29 17:01:56 [debug]  0
2023-03-29 17:01:56 [debug]  0
2023-03-29 17:01:56 [debug] === Multicast handler ===
Responder is inactive, messages received 0, responses 0


; M98 P"config.g" response


2023-03-29 17:01:58 [debug] HTTP is enabled on port 80
2023-03-29 17:01:58 [debug] FTP is disabled
2023-03-29 17:01:58 [debug] TELNET is disabled
2023-03-29 17:01:58 [info] G10 P0 X0 Y0 Z0                              
2023-03-29 17:01:58 [info] G10 P0 R0 S0                                 


; set the temperature to 70deg via the dashboard


2023-03-29 17:02:04 [warn] Error: M140: No bed heater has been configured for slot 10


; set the temperature to 60C via a test print file containing only "M140 S60 P10"


2023-03-29 17:02:06 [debug] File BedHeaterTest.gcode selected for printing
2023-03-29 17:02:10 [warn] Started printing file 0:/gcodes/BedHeaterTest.gcode
2023-03-29 17:02:10 [warn] Error: No bed heater has been configured for slot 10
2023-03-29 17:02:10 [debug] Done printing file
2023-03-29 17:02:10 [debug] Done printing file
2023-03-29 17:02:10 [warn] Finished printing file 0:/gcodes/BedHeaterTest.gcode, print time was 0h 0m


; set the temperature to 50C via console command "M140 S50"


2023-03-29 17:02:33 [warn] Error: Heater 10 fault: temperature rising too slowly: expected 2.32°C/sec measured -0.02°C/sec
2023-03-29 17:02:33 [info] M291: - Event notification - Heater 10 fault: temperature rising too slowly: expected 2.32°C/sec measured -0.02°C/sec
2023-03-29 17:02:33 [debug] - Event notification -
2023-03-29 17:02:33 [debug] Heater 10 fault: temperature rising too slowly: expected 2.32°C/sec measured -0.02°C/sec

                  Thank you very much for your help.

                  chrishammundefined 1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators @jp.douarvil 0
                    last edited by

                    @jp-douarvil-0 Thanks for reporting this, I think there is something wrong with bed and chamber control in DWC 3.5-b2. I'm going to fix this in 3.5-b3.

                    Duet software engineer

                    1 Reply Last reply Reply Quote 1
                    • droftartsundefined
                      droftarts administrators
                      last edited by droftarts

                      @jp-douarvil-0 Okay, I am pretty sure this is a bug in DWC 3.5beta2, and @chrishamm is looking at it.

                      It seems the bed heater controls in DWC are referring to the bed heater 'slot' (or 'index') number (6HC supports up to 12 heated bed 'slots') but using the 'heater' number. The M140 command in config.g sets up which heater is the bed heater, with P0 (bed heater index 0) being the default. Yours M140 is M140 H10, which is the same as M140 P0 H10, or 'bed heater slot 0 is heater 10'. However, DWC 3.5beta2 shows bed heater slot 10 (using the heater number, not the slot number, which doesn't exist, and when you click the 'Heater' it sends M140 P10 S60. That is why you get this error message when you click on bed heater controls in DWC, and using the same Gcode in your test file:

                      Error: M140: No bed heater has been configured for slot 10

                      I think you can work around this if you set the bed heater slot to the same as the bed heater number. In config.g, change M140 H10 to H140 P10 H10. Your BedHeaterTest.gcode will also work then. (EDIT: I realise this is what you said in your first post!)

                      In DWC 3.5beta2, there is also a new setting in Settings > Machine-Specific to group heater control. For beds this is 'Single bed control'. If you enable this, M140 commands from DWC are sent without the P parameter, which should also work, as this sends commands without the P parameter, eg M140 S50, like you send from the console.

                      This then causes the final problem, the Heater 10 fault. This is because you have not tuned the bed heater; your M307 for the bed heater is still the default. You should be able to tune the heater; see https://docs.duet3d.com/en/How_to_guides/Commissioning#h-7-tune-heaters

                      EDIT: Any time M140 is sent without P parameter, it defaults to P0. So if you want to control it with the slicer without adding the P parameter, and with DWC, leave it in config.g as M140 H10 and enable single bed control, which should allow you to select heater slot 0 in DWC. Alternatively, set the bed heater up as Heater 0.

                      Ian

                      Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard

                      jp.douarvil 0undefined 1 Reply Last reply Reply Quote 1
                      • jp.douarvil 0undefined
                        jp.douarvil 0 @droftarts
                        last edited by

                        @droftarts , @chrishamm Hello,

                        The single bed control tip allows for controling the bed temperature via the dashboard at least, I can live with that 😄 .

                        Thank you very much for the explanations.

                        On the heater fault, its OK 👍 . I hadn't even connected the heater to the board as it was just a "unit test" built for the purpose of diagnosing the specific dashboard control issue.

                        droftartsundefined 1 Reply Last reply Reply Quote 0
                        • droftartsundefined
                          droftarts administrators @jp.douarvil 0
                          last edited by

                          @jp-douarvil-0 one of the perils of being a beta-tester! But thanks for pointing this out, we appreciate the feedback. We also found a couple of other related bugs; active and standby temps not showing if set by Gcode commands and same issue with chambers. It does work correctly if you revert to DWC 3.4.5, but there may be other issues running that with the beta firmware.

                          Unless you need specific features of the beta version, running the release version may be better for you, though we appreciate the feedback.

                          Ian

                          Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard

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