SOLVED - Heater Temp not increasing after initial test.
-
I decided it was a good time to migrate to the latest firmware... i was pre 3.0 so im about done... ill post that here in a second to see if there are any glaring differences you can see
-
updated firmware config
0:/sys/config.g
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Fri Sep 16 2022 10:35:49 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"Ender 5 Plus IWS" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.56 Y80.49 Z801.62 E674.42 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E10000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1200 I10 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X350 Y350 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters
M557 X0:315 Y0:315 S25 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat 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"e0temp" Y"thermistor" T100000 B4138 ; 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; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 S"Nozzle" 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
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossEnder 5 Plus IWS
Send code...
Status
Idle
Mode: FFF
Tool Position
X
0.0
Y
0.0
Z
0.00
Extruder Drives
Drive 0
0.0
Speeds
Requested Speed
0 mm/s
Top Speed
0 mm/s
Sensors
Vin
24.1 V
MCU Temperature
32.4 C
Tools
Extra
Control All
Tool Heater Current Active Standby
Nozzle
T0 - Load Filament Heater 1
off 26.2 C
0
0
Bed Heater 0
off 25.8 C
0
0
Temperature Chart
System Directory -
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: M307: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.hmm not sure what thats about
-
@anvil What command did you put in the console to PID the hotend? The one Jay gave was an example, you don't have a T1 so that wouldn't work.
Follow my adventures in 3D Printing, laser cutting and electronics. https://linktr.ee/Rushmere3D
-
i used T0 for the command after firmware update and it says "no heater tuned"
-
Hotend heater gets error of "temperature rising too slowly"
-
@anvil ah yes, I mean T0 not T1. Where do you see that error about no heater tuned?
When you send M303 do you see any rise out of the temperature at all?Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jay_s_uk both on the web interface and my paneldue
but currently im dealing with a random "incompatible firmware version" that randomly popped up after working fine for a bed tune and trying to tune the nozzle...
grrrrrrr
-
@jay_s_uk
ok got everything connected again and the right firmware all going...but yes the heater rises verrrrryyyyyy slooooowly...
idle at same temp as be so i know the thermistors are correct... but ya it goes from 26.8 to like 27.4 before it says its not increasing fast enough -
@anvil sounds like you have a wiring issue. I'd start by using a multimeter to check the heater of the rapido
-
does the rapido need to be double fed or something? specs say its a 115w heater... not sure why its not heating. its all wired correctly. I cant find any documentation on a wiring diagram for it.
-
@anvil no, it doesn't need to be double fed. Are you using the right voltage version for your system?
Have you checked it with a multimeter? -
Can you send M122 and post the results?
-
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2 (2022-09-13 15:11:16) running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6JKFJ-3S86S-TBDQP
Used output buffers: 1 of 26 (12 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 75112 of which 0 recycled
Never used RAM 13108, free system stack 184 words
Tasks: NETWORK(ready,10.2%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,82.2%,440) IDLE(ready,7.5%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:12 ago, cause: software
Last software reset at 2022-09-16 15:21, reason: User, GCodes spinning, available RAM 13108, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 37.3, current 38.1, max 38.2
Supply voltage: min 24.0, current 24.1, max 24.3, 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 n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-09-16 15:21:13
Cache data hit count 458831398
Slowest loop: 5.52ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 16.01ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address dc:4f:22:6e:6b:09
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22944
WiFi IP address 192.168.0.33
WiFi signal strength -51dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0 -
Your wifi server version is out of date for 3.4.2. How did you update the firmware?
I suggest uploading the firmware zip file again to ensure everything is up to date.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.2/Duet2and3Firmware-3.4.2.zip
Next try tuning the heater again and take a screen shot of the temp graph and capture the complete error message if you get one.
M303 H0 S200
-
So i just noticed something on my paneldue when it starts up.... doesnt show up in the web console for some reason... but it says T0 hasnt been set up and that the bed seems to be overpowered.
I think my bed and nozzle are competing for the same tool definition in the config.. not sure how to fix it... i swapped the numbers and got the nozzle to start increasing temp normally but only by setting the bed temp and activating... can i fix this in my config or do i need to change something in my .json?
-
@phaedrux i think theres something up with the definition of my heaters... can you look it over and see if its odd with the bed and primary tool being the way they are?
-
This post is deleted! -
Is this what you still have for your heater definitions?
; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat 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"e0temp" Y"thermistor" T100000 B4138 ; 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 ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 S"Nozzle" 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 -
@phaedrux said in Heater Temperature not increasing after initial test.:
M303 H0 S200
Sorry, this should have been H1. H0 is the bed. H1 is the nozzle heater.
