I have gotten up and running now. But the Thermistor is reporting incorrect values. I will search and start anew thread.

@Phaedrux OI think that one of my z axis was binding. I put some teflon lubricant on the z screw drives and it is working.

It is strange that I have had these difficulties with the firmware. I hope to someday install firmware without any snags. Not today.

I have a duet 3 mini 5+.

I used the configuration tool to get the right firmware and commands under duet 3. Here is a copy of my m115

m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3RC2 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-05-11 14:55:40
ok

My config G

; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sun Oct 23 2022 21:15:12 GMT-0400 (Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"LRNSenior" ; set printer name
M665 R105.6 L215 B85 H175 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
M918 P1 E4 F2000000 ; configure direct-connect display

; Network
M551 P"elbow7986diesel" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
M587 S"SETUP-AF8D" P"elbow7986diesel" : added to attempt connect 10/23/2022

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E663.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z0 S1 ; set minimum Z

; Endstops
M574 X1 S1 P"io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Y1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in
M574 Z1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in

; Z-Probe
M558 P5 R0.4 C"io3.in+io3.out" H5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 R85 S20 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"pt1000" ; configure sensor 0 as PT1000 on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"pt1000" ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out5" Q500 ; create fan 0 on pin out5 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out6" Q500 ; create fan 1 on pin out6 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"se heater" 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

; Miscellaneous
T0 ; select first tool

When I run m997 this is what I get
m997
Error: M997: In-application programming binary “0:/firmware/Duet3_SDiap32_Mini5plus.bin” not found
ok

My sd card structure

bcm2708-rpi-b-plus.dtb
bcm2708-rpi-b-rev1.dtb
bcm2708-rpi-b.dtb
bcm2708-rpi-cm.dtb
bcm2708-rpi-zero-w.dtb
bcm2708-rpi-zero.dtb
bcm2709-rpi-2-b.dtb
bcm2710-rpi-2-b.dtb
bcm2710-rpi-3-b-plus.dtb
bcm2710-rpi-3-b.dtb
bcm2710-rpi-cm3.dtb
bcm2711-rpi-4-b.dtb
bcm2711-rpi-400.dtb
bcm2711-rpi-cm4.dtb
bootcode.bin
cmdline.txt
config.txt
COPYING.linux
filaments
firmware
fixup_cd.dat
fixup_db.dat
fixup_x.dat
fixup.dat
fixup4.dat
fixup4cd.dat
fixup4db.dat
fixup4x.dat
gcodes
issue.txt
kernel.img
kernel7.img
kernel7l.img
kernel8.img
LICENCE.broadcom
macros
menu
overlays
start_cd.elf
start_db.elf
start_x.elf
start.elf
start4.elf
start4cd.elf
start4db.elf
start4x.elf
sys
www

@droftarts
T100 worked on USB power ,my duet 2 is around five years old: how much of a factor is that?

Here is my config.g with the correct T value.

M308 S1 P"e0temp" Y"thermistor" T1000000 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 ; set temperature limit for heater 1 to 280C

My M115 FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2022-10-05 09:01:07

I have gotten up and running now. But the Thermistor is reporting incorrect values. I will search and start anew thread.

This is a different presentation of a previous problem. I have an E3d Thermistor and this is my printer with a Semitec 104GT thermistors this is my configuration

M308 S1 P"e0temp" Y"thermistor" T1000 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 ; set temperature limit for heater 1 to 280C

I het a reading of -50.8 for the temp with low voltage and I get a heater fault -273 when I turn on the power switch. I am using a smart effector and am using the two middle plugs to get the temp for T0. I redid the wiring there are not likely any wiring issues, however it does seem that after I bumped the smart effector the temps started registering wonky, full dislosure. The run for the wiring is long too, I am not sure how much that matters it is about 1.5 meters.

@Phaedrux OI think that one of my z axis was binding. I put some teflon lubricant on the z screw drives and it is working.

@droftarts It looks like this solved my problem thanks

The bed tramming on my railcore stated to misfire. I was using four point mesh and decided to more to threepoint mesh and changed the location of the points to see if that could effect anything. It still does not, the bed is higher towards the ;eft front origins and lower towards the back left. One corner is lower than the others is seems. I wonder if it is because the center is being sampled? Can any one shed some light? Duet3 V3.3 firmware

M561 ; clear any existing bed transform
G1 Z5 ; RRF3 remove S2
G30 P0 X15 Y45 Z-99999
G30 P1 X15 Y265 Z-99999
G30 P2 X275 Y165 Z-99999
;G30 P3 X275 Y45 Z-99999 S1 ;changed ocotober 13 2022 LN
;G1 X0 Y0 F5000 ; move the head to the corner (optional)

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.26

@dc42 where is the full information I need to configure a PT1000?

I switched over to Duet 3 firmware yesterday. Thanks for the help everyone, now my hotend temp is reporting incorrectly, 1t is saying 165 degree s c at ambient temp while the bed reports regular temps. I am considering getting the resistance values from the unit and changing that in the profile. I have an 3d v6 canister thermistor that goes through the heat block, not a surface mounted one.

droftarts

I thought that I read in the DWC repository that if I used the online config tool, I would get the update gcode identifiers. Looks like you are saying that is not the case. To clarify, I downloaded a json file, used the configuration tool and I still cannot get info from the temp sensors. It looks like I have to do that manually? Do I need to compose from scratch to get the changes of Gcode from duet 2 to 3?

from the link we have both seen. No caveats about using existing json, however it looks like this may be a reality.

Important! These instructions relate to RRF3.0 and to some extent to later versions of RRF3 however they are not kept up to date. Please refer to the Gcode Dictionary and use the RepRapFirmware configuration tool to migrate from RRF2 to RRF3.