Displaying Water Temp. Virtual Heater Help
-
@dc42 awesome thank you, I think that clears it up, will test soon to see results.
-
@dc42 Here is what I input like you said, I am not seeing them pop up in the "extra" section. What am I doing wrong here?
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor 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"temp2" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 1 as thermistor on pin temp2
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 S455 ; set temperature limit for heater 1 to 455C
M308 S2 P"temp3" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin temp3
M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C
M308 S3 P"temp1" Y"thermistor" T10000 B4723 C1.19622e-7 ; configure sensor 3 as thermistor on pin temp1
M950 H3 C"out3" T3 ; create chamber heater output on out3 and map it to sensor 3
M307 H3 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H3 ; map chamber to heater 3
M143 H3 S90 ; set temperature limit for heater 3 to 90C
M308 S10 P"1.temp0" Y"thermistor" T10000 B3988 A"Coolant Cold" ; Configure coolant sensor cold side
M308 S11 P"1.temp1" Y"thermistor" T10000 B3988 A"Coolant Hot" ; Configure coolant sensor hot side
I just caught this too, when restarting the board to get new code changes it pops up for a split second and then disappears. Watch it here: YouTube
-
Please send M98 P"config.g" and report the results. That should show us all the syntax errors in config.g
-
-
Can you post your full config?
Have you set the can address of the 3HC?
https://duet3d.dozuki.com/Wiki/CAN_connection
Can you send M122 and M122 B1 and confirm they are both using the same firmware version?
-
@phaedrux
I haven't messed with it physically, it was set to what you see in the picture from the factory, which I think is = 1 based on the chart?
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JTD4-3S46N-TU2GD
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 63876 of which 112 recycled
Never used RAM 145056, free system stack 182 words
Tasks: Linux(ready,79) HEAT(blocked,278) CanReceiv(blocked,848) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,51) MAIN(running,1187) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:57:58 ago, cause: software
Last software reset at 2021-04-15 00:49, reason: User, none spinning, available RAM 145384, slot 0
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 38.5, current 39.1, max 40.4
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 35455, writes 20 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 35457, writes 20 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 35457, writes 20 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 35457, writes 20 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 35457, writes 20 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 35466, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-04-15 01:47:10
Slowest loop: 999.86ms; 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 = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -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 13923, send timeouts 0, received 13915, lost 0, longest wait 1ms for reply type 6027, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 3ms ago
RX/TX seq numbers: 57143/57143
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c884
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.28
Maximum length of RX/TX data transfers: 4532/828M122 B1
Diagnostics for board 1:
Board EXP3HC firmware 3.1.0 (2020-05-15b1)
Never used RAM 163.4Kb, max stack 352b
HEAT 1092 CanAsync 1452 CanRecv 1420 TMC 156 AIN 524 MAIN 2208
Last reset 00:58:47 ago, cause: software
Driver 0: standstill, reads 37134, writes 22 timeouts 0, SG min/max 0/8
Driver 1: standstill, reads 37136, writes 22 timeouts 0, SG min/max 0/8
Driver 2: standstill, reads 37139, writes 22 timeouts 0, SG min/max 0/8
Moves scheduled 0, completed 0, hiccups 0
VIN: 24.1V, V12: 12.2V
MCU temperature: min 43.0C, current 43.2C, max 43.4C
Ticks since heat task active 123, ADC conversions started 3527116, completed 3527116, timed out 0
Last sensors broadcast 00000000 found 0 126 ticks ago
Free CAN buffers: 36
NVM user row de9a9239 aeecffb1 ffffffff ffffffffI see the daughterboard's firmare is different. I assume that may be the issue?
-
Since you're using the SBC you can try sending sudo apt update sudo apt upgrade and see if it detects and flashes the 3HC. If it doesn't, you can try manually flashing it by sending M997 B1.
-
@phaedrux update commands Via SSH or in the DWC console?
-
the sudo commands are for the pi, the M997 B1 is for the Duet firmware. Send accordingly.
-
@phaedrux that's what I thought, trying right now.
-
@phaedrux that did the trick B1 is on 3.2.2! Thank you!
-
Which command worked to update it by the way?
-
@phaedrux well to be honest I believe it was the M997 B1. Because I had previously been on 3.2.2 on the mainboard and did the ssh Sudo upgrade stuff in the pi and it did not change to a newer version on the mainboard. But I did do both, so I don't know with 100% certainty, apologies.
