Hotend 100˚ less on ToolBoard?
-
@Dizzwold what type of thermistor did it come with? Or have you reused the original thermistor?
-
It's a NTC 100k. I was using it before fitting the toolboard with no issues.
-
Can you send M122 and M122 B121 in the gcode console in DWC and copy and paste the results here?
Can you reconnect the heather and thermistor to the main duet board and reconfigure to confirm that the thermistor reading is then correct?
What PID values did you get? Do you have saved PID values from when the heater and thermistor were connected to the mainboard to compare with?
When and where did you purchase the toolboard?
-
@Phaedrux
Ahh, That could be the problem. I have the above pid settings in my config.g from when I first set everything up (on the main board).
Now that I've installed the toolboard an ran the pid tune, and the new figures are in the config-override.g, as I typed M500 afterwords.
Is that correct or not?; config-override.g file generated in response to M500 at 2022-10-21 12:57 ; This is a system-generated file - do not edit ; Heater model parameters M307 H0 R0.199 K0.237:0.000 D1.87 E1.35 S1.00 B0 M307 H1 R2.414 K0.284:0.000 D8.15 E1.35 S1.00 B0 V23.6 ; Probed tool offsets G10 P0 X0.00 Y0.00 Z0.00 ; 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.00M122
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.2 (2022-09-13 15:17:43) running on Duet 3 MB6HC v1.01 (SBC mode) Board ID: 08DJM-956BA-NA3TJ-6J9DA-3SN6T-9AAYV Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 152664 Dynamic ram: 66192 of which 100 recycled Never used RAM 128476, free system stack 124 words Tasks: SBC(ready,4.4%,466) HEAT(notifyWait,0.1%,194) Move(notifyWait,0.1%,232) CanReceiv(notifyWait,0.2%,772) CanSender(notifyWait,0.0%,328) CanClock(delaying,0.0%,339) TMC(notifyWait,63.6%,57) MAIN(running,31.5%,923) IDLE(ready,0.1%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 10:58:01 ago, cause: power up Last software reset at 2022-10-20 16:22, reason: User, GCodes spinning, available RAM 131616, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 135 MCU temperature: min 23.4, current 38.8, max 39.0 Supply voltage: min 23.7, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/136/136, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 504, reads 33279, writes 73 timeouts 0 Driver 1: standstill, SG min 0, mspos 328, reads 33279, writes 73 timeouts 0 Driver 2: standstill, SG min 0, mspos 488, reads 33271, writes 81 timeouts 0 Driver 3: standstill, SG min 0, mspos 488, reads 33271, writes 81 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 33341, writes 11 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 33342, writes 11 timeouts 0 Date/time: 2022-10-21 21:06:02 Slowest loop: 532.96ms; 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 16, maxWait 5594217ms, bed compensation in use: mesh, comp offset -0.120 === MainDDARing === Scheduled moves 779, completed 779, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 107], 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 0 -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 361722, received 790664, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 280, free buffers 47 (min 45), ts 197410/197409/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 33514/33514 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2b1a0 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.2 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 38.82, max time between full transfers: 158.1ms, max pin wait times: 57.4ms/14.5ms Codes per second: 0.18 Maximum length of RX/TX data transfers: 3364/1496M122 B121
M122 B121 Diagnostics for board 121: Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.2 (2022-09-13 15:06:56) Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2) All averaging filters OK Never used RAM 3576, free system stack 45 words Tasks: Move(notifyWait,0.0%,91) HEAT(notifyWait,1.9%,75) CanAsync(notifyWait,0.0%,59) CanRecv(notifyWait,0.1%,74) CanClock(notifyWait,0.1%,65) TMC(delaying,21.4%,57) MAIN(running,41.2%,351) IDLE(ready,0.0%,40) AIN(delaying,35.2%,142), total 100.0% Last reset 11:05:51 ago, cause: power up Last software reset data not available Driver 0: pos 382432, 333.4 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 45, reads 52140, writes 45, timeouts 0, DMA errors 0, CC errors 0, steps req 520060 done 520060 Moves scheduled 5701, completed 5701, in progress 0, hiccups 0, step errors 0, maxPrep 518, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 6/11, peak Rx sync delay 216, resyncs 0/0, no step interrupt scheduled VIN voltage: min 23.5, current 24.1, max 24.2 MCU temperature: min 31.1C, current 39.4C, max 47.8C Last sensors broadcast 0x00000002 found 1 32 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 800026, send timeouts 0, received 365930, lost 0, free buffers 37, min 36, error reg 110000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 429, adv 35647/74652 Accelerometer: none I2C bus errors 4573, naks 4573, other errors 4573 -
@Dizzwold said in Hotend 100˚ less on ToolBoard?:
Is that correct or not?
Yes that is fine. You have M501 at the end of your config.g so it would load config-override.g at the end and those values would override whatever you had in the config.g itself.
When and where did you purchase the toolboard? Has it ever read correctly?
-
It's the Fysetc purchased June 21 and it's never been used.
I just tried testing the temp with another handheld thermometer and I get 188˚c, when I've asked for 238˚c in DWC,
DWC states 238˚c, yet only 188˚c
One thing I didn't do when doing the pid on the nozzle (the last 3 times), was I didn't move the head around. That wouldn't be the cause would it? -
Oh, so it's a clone board.
Also those handheld temperature meter's aren't great for stuff like this I've found.
-
@Dizzwold
I've fixed it, with stripping the extruder to check for any ware, new heater cartridge, new NTC thermistor, new heatblock sock, rebuilt and re-pid tune. -
Yep, a clone Toolboard and clone Hemera.
I'm disabled, and on UK benefits due to health, so after purchasing the original and authentic Duet3 6HC, I couldn't afford the authentic Toolboard or Hemera, so please don't hold that against me. I will over time manage to afford these as original products.
-
@Dizzwold said in Hotend 100˚ less on ToolBoard?:
@Dizzwold
I've fixed it, with stripping the extruder to check for any ware, new heater cartridge, new NTC thermistor, new heatblock sock, rebuilt and re-pid tune.Glad you got it working.
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
-
@Dizzwold Not holding it against you at all. Just mention it next time as it may lead the help/advice a different route. Technically there isn't a clone Hemera just similar looking products.
Glad it's working now.
