@phaedrux
what means 'sudo apt update'?

@dc42
did not upgrade);
After receiving the board, it was 3.4 as a result.
I think I received the upgraded version.

@deckingman

Should I connect the tamp0 to tool0?;(

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Tue Jan 26 2021 16:38:54 GMT+0100 (Central European Standard Time)

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

; Network
;M551 P"Macarena88" ; set password

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

; Drives
M569 P0 S1 ; physical drive 0.0 goes forwards
M569 P1 S1 ; physical drive 0.1 goes forwards
M569 P2 S1 ; physical drive 0.2 goes forwards
M569 P3 S0 ; physical drive 0.3 goes forwards
M569 P4 S0 ; physical drive 0.3 goes forwards
M569 P5 S0 ; physical drive 0.3 goes forwards

M584 X5 Y1:2 Z3 E4 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E492.45 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E800.00 ; set maximum instantaneous speed changes (mm/min)
M203 X15000.00 Y15000.00 Z400.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E500.00 ; set accelerations (mm/s^2)
M906 X1400 Y2500 Z2500 E1400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-25 Y-72 Z0 S1 ; set axis minima
M208 X1020 Y500 Z500 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"^!io0.in" ; configure active-high endstop for low end on X via pin io0.in
M574 Y1 S1 P"^!io1.in" ; configure active-high endstop for low end on Y via pin io1.in
M574 Z1 S1 P"^!io2.in" ; configure active-high endstop for low end on Z via pin io2.in

; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io7.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-30 Y-2 Z3.3 ; set Z probe trigger value, offset and trigger height
M557 X20:980 Y10:490 S120 ; define mesh grid

; Heaters
M308 S0 P"temp2" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out2" T0 Q1 ; create heater output on out0 and map it to sensor 0 ; disable bang-bang mode for heater and set PWM limit
M143 H0 S70 ; set temperature limit for heater 0 to 70C
M140 P1 H0

M308 S2 P"temp3" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H2 C"out3" T2 ; create heater output on out1 and map it to sensor 1 ; disable bang-bang mode for the bed heater and set PWM limit
M143 H2 S350 ; set temperature limit for heater 1 to 70C

M307 H0 A200.8 C850.6 D2.0 S1.00 V24.0 B0
M307 H2 A491.0 C185.5 D4.9 S1.00 V24.0 B0

; Fans
M950 F0 C"out8" Q255 ; create fan 0 on pin out4 and set its frequency
M106 P0 S0.7 L0.3 X0.7 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out7" Q200 ; create fan 1 on pin out5 and set its frequency ; set fan 1 value. Thermostatic control is turned on
M106 P1 S0.7 L0.3 X0.7 H2

; Tools
M563 P0 D0 H2 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

//config-override.g//

; config-override.g file generated in response to M500 at 2021-01-27 15:58
; This is a system-generated file - do not edit
; Heater model parameters

; 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

@macgyver
Immediately after uploading the board firmware.(Cache, no temporary files) );

@phaedrux this is RPI

; Heaters
M308 S0 P"temp2" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out2" T0 Q1 ; create heater output on out0 and map it to sensor 0 ; disable bang-bang mode for heater and set PWM limit
M143 H0 S70 ; set temperature limit for heater 0 to 70C
M140 P1 H0

@phaedrux Thank you for your answer
You can control the heater by setting the temperature. It rises as expected.
I don't know exactly what kind of heater and thermistor are, but I think it's 1000K 24V.
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTDG-3S86S-TUB2S
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 61604 of which 0 recycled
Never used RAM 141684, free system stack 219 words
Tasks: SBC(ready,20.8%,326) HEAT(delaying,0.1%,325) Move(notifyWait,0.2%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,30.5%,93) MAIN(running,48.4%,1252) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 06:15:47 ago, cause: software
Last software reset at 2022-04-15 08:05, reason: User, none spinning, available RAM 141468, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 132
MCU temperature: min 48.3, current 48.7, max 55.6
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 38330, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 38324, writes 17 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 38324, writes 17 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 38324, writes 17 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 38324, writes 17 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 38324, writes 17 timeouts 0, SG min/max 0/0
Date/time: 2022-04-15 14:21:00
Slowest loop: 63.36ms; 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, 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 = -1 0 -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 202923, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 112740/0/0
Tx timeouts 0,0,112739,0,0,90182 last cancelled message type 4514 dest 127

=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 1ms ago
RX/TX seq numbers: 56802/56802
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 34.49, max wait times: 6.4ms/0.0ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 2868/804

@burtonenator
Thank you.
I try that

Hello.

I'm making two printers, but I'm inquiring because there's a problem.
A heater temperature reading error message appears and continues to interrupt while one printer is leveling the G29 bed.
However, temperature sensor sensing works well without errors.
I wonder what caused this.

@phaedrux

Thank you.
Renamed and executed, but the same result.

I think we need to downgrade the board to 3.3
Do you know how to do it?