Solved PT1000 reading 2000c on a new 1LC Board
-
Currently working on setting up a voron 2.4 with a toolboard. Everything was going well until I wired up my PT1000 sensor from a Rapido v2 UHF to the toolboard. It's reading 2000 degrees C whether I have the sensor plugged in or not. If I measure the resistance across the male side connector for the PT1000 I get 1080ohms or so. When it's installed to the 1LC board, I get roughly 750ohms.
Any ideas on what's going on or how to diagnose it? This sensor was just working great on my duet 2 setup.
Currently on DSF 3.4.4, mainboard is on 3.4.0 and 3HC and 1LC are both at updated from 3.4.0.
Firmware related to heater and temp sensor:
;Heaters & Temp sensors
M308 S1 P"121.TEMP_1" Y"PT1000" ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" 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 S350 ; set temperature limit for heater 1 to 350C -
@michaelr123 said in PT1000 reading 2000c on a new 1LC Board:
Currently on DSF 3.4.4, mainboard is on 3.4.0 and 3HC and 1LC are both at updated from 3.4.0.
They should all match versions.
Can you send M122 and M98 P"Config.g" in the gcode console in DWC and post the replies?
@michaelr123 said in PT1000 reading 2000c on a new 1LC Board:
This sensor was just working great on my duet 2 setup.
Can you confirm if it still works?
Do you have a standard thermistor to test on the toolboard?
-
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6J1D4-3SD6R-9U479
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 64972 of which 0 recycled
Never used RAM 134700, free system stack 200 words
Tasks: SBC(ready,0.4%,468) HEAT(notifyWait,0.0%,373) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,351) TMC(notifyWait,7.7%,92) MAIN(running,89.7%,1231) IDLE(ready,2.2%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:44 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 133
MCU temperature: min 26.6, current 36.4, max 36.5
Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 50029, writes 15 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 50029, writes 15 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 50029, writes 15 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 50029, writes 15 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 50034, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 50030, writes 15 timeouts 0
Date/time: 2024-01-28 20:20:22
Slowest loop: 1.11ms; fastest: 0.03ms
=== 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 241, received 1001, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 5, free buffers 50 (min 49), ts 221/220/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 1593/1593
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b880
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.4
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 60.46, max time between full transfers: 217.8ms, max pin wait times: 40.2ms/54.1ms
Codes per second: 1.40
Maximum length of RX/TX data transfers: 2868/904 -
@Phaedrux
M98 P"Config.g" returns a warning that the macro file wasn't found.
Here is my whole config file:; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Tue May 16 2023 19:10:31 GMT-0500 (Central Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Voron2" ; set printer name
G4 S2 ; wait for expansion boards to startM569 P0.0 S1 D2 ; driver 0.0 goes forwards (X axis) D2 - Spreadcycle
M569 P0.1 S1 D2 ; Driver 0.1 goes forward (X axis, AWD) D2 - SpreadcycleM569 P0.2 S1 D2 ; driver 0.2 goes forwards (Y axis) D2 - Spreadcycle
M569 P0.3 S1 D2 ; Driver 0.3 goes forward (Y axis, AWD) D2 - SpreadcycleM569 P0.5 S1 D2 ; Driver 0.5 goes forward (Z axis - 1) D2 - Spreadcycle
M569 P1.0 S1 D2 ; Driver 1.0 goes forward (Z axis - 2) D2 - Spreadcycle
M569 P1.1 S0 D2 ; Driver 1.1 goes forward (Z axis - 3) D2 - Spreadcycle
M569 P1.2 S0 D2 ; Driver 1.2 goes forward (Z axis - 4) D2 - SpreadcycleM569 P121.0 S1 D2 ; Driver 121.0 goes forward (E axis on 1LC) D2 - Spreadcycle
M584 X0.0:0.3 Y0.1:0.2 Z0.5:1.0:1.1:1.2 E121.0 ; set axis mapping
M350 X16 Y16 Z16 I1 ; configure microstepping with interpolationM671 X-65:-65:320:320 Y-20:350:350:-20 S20 ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right)
M92 X80.00 Y80.00 Z400 E420.00 ; set steps per mm
M566 X600.00 Y600.00 Z30.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z1000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z50.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 X Y E S30 ; Set idle timeout; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout; Fans
M950 F0 C"121.out2+out2.tach" Q450 ; create fan 0 on pin out5 and set its frequency
M106 P0 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on;Heaters & Temp sensors
M308 S1 P"121.TEMP_1" Y"PT1000" ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" 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 S350 ; set temperature limit for heater 1 to 350C; Tools
M563 P0 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
M501 ; load saved parameters from non-volatile memory -
Can you confirm if it still works?
Do you have a standard thermistor to test on the toolboard?
I've got the duet pretty well torn apart, I can dig up a power supply and try reading from it quick. Would it be faster to grab a thermistor and try reading that instead? If it can read a different temp probe type then we should be able to say that input pin works right?
-
Your firmwares are out of sync and out of date. I suggest updating. You're using an rpi, so use the pi terminal to send
sudo apt updateandsudo apt upgrade. Then check your firmware versions with M122 again. It should update to 3.4.6 -
updated to latest stable build and updated both CAN boards, no difference on the PT1000 reading.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6J1D4-3SD6R-9U479
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 153252
Dynamic ram: 66084 of which 0 recycled
Never used RAM 131336, free system stack 200 words
Tasks: SBC(ready,0.5%,466) HEAT(notifyWait,0.0%,343) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,751) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,347) TMC(notifyWait,7.3%,90) MAIN(running,92.1%,1231) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:20:17 ago, cause: software
Last software reset at 2024-01-30 19:31, reason: User, GCodes spinning, available RAM 131336, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 134
MCU temperature: min 42.2, current 42.9, max 43.0
Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 25607, writes 15 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 25607, writes 15 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 25607, writes 15 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 25607, writes 15 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 25611, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 25607, writes 15 timeouts 0
Date/time: 2024-01-30 19:51:37
Slowest loop: 21.49ms; 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 10842, received 19593, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 468, free buffers 50 (min 49), ts 6090/6089/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 45472/45472
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ab34
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.6
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 40.16, max time between full transfers: 71.0ms, max pin wait times: 37.4ms/1.5ms
Codes per second: 0.03
Maximum length of RX/TX data transfers: 3020/904 -
undefined michaelr123 marked this topic as a question
-
undefined michaelr123 has marked this topic as solved
-
I'm an idiot, I was using temp_1 instead of temp_0 in my config. disregard, works great now.
