Hi Everyone,

I'm having a very strange problem and I have no idea What's causing it or why this has suddenly Popped up. I have a Duet mini5+ hooked up to 2 1xd's and 1 toolboard 1lc. I have a BlTouch hooked up to the Toolboard through the io0 port and I've had almost no issues until now. When I give the command to touch off Z it doesn't deploy the probe. I have rewired the sensor thinking that was the issue but nothing changed. At which point I broke out my oscilloscope to see if it was even generating a PWM signal to deploy the probe at which point I discovered its no longer generating any PWM signal. I updated the firmware with zero change and I'm not sure what to do at this point. I have attached my config file as well as my M122.

Thanks for all the help in advance

config.g

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.3 (2024-01-24 17:56:48) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: K1NVW-8096U-D65J0-40KM6-1D03Z-HSZ5X
Used output buffers: 1 of 40 (30 max)
=== RTOS ===
Static ram: 103200
Dynamic ram: 115352 of which 28 recycled
Never used RAM 22836, free system stack 202 words
Tasks: NETWORK(1,ready,24.1%,183) ETHERNET(5,nWait 7,0.6%,561) HEAT(3,nWait 6,0.0%,366) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,796) CanSender(5,nWait 7,0.0%,337) CanClock(7,delaying,0.0%,354) TMC(4,nWait 6,0.8%,102) MAIN(1,running,73.0%,667) IDLE(0,ready,0.5%,30) AIN(4,delaying,0.8%,260), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:29 ago, cause: software
Last software reset at 2024-03-17 13:04, reason: User, Gcodes spinning, available RAM 22836, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 29527, completed 29527, timed out 0, errs 0
MCU temperature: min 24.8, current 25.7, max 25.7
Supply voltage: min 25.4, current 25.5, max 25.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 44, reads 1525, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 59, reads 1521, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 59, reads 1521, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 59, reads 1520, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 59, reads 1521, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-03-17 13:05:18
Cache data hit count 50460393
Slowest loop: 2.42ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 288, received 1063, lost 0, errs 0, boc 0
Longest wait 2ms for reply type 6053, peak Tx sync delay 3, free buffers 26 (min 25), ts 148/147/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 6.60ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 3 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 2 5 2 2 2 0 0 0

So I recently bought myself a Duet 2 Mastero as my choice of motherboard when building my custom 3d printer. Upon booting and testing everything about the board I've been attempting to use a thermistor that came with my new bed that I bought. Since I did not know what the exact measurement of the thermistor I used a volt meter to measure the resistance at room temperature and put in a B value that may not have been perfect but should have yielded results good enough for testing. No matter what I seem to do from editing the firmware or applying different levels of resistance to the leads, I cannot get any of the thermistor ports to work. The readout on the web interface is always 2000 degrees C no matter what I do to it.

Any suggestions?