Hotend and Heated bed reading 2000deg celcius and fault
-
You did not change the P parameter, it should be:-
M308 S0 P"bed_temp"
M308 S1 P"e0_temp" -
i changed it now and it still isnt doing it
-
@NEVER-LUCKY said in Hotend and Heated bed reading 2000deg celcius and fault:
i changed it now and it still isnt doing it
Why do you have M303 commands in config.g? They don't belong there! They are for manual use only.
-
i removed it and still no results. same problem and for some reason the hotend fan stopped spinning last night.
-
@NEVER-LUCKY Please send M115 to the Duet and post the reply. Your config.g is set up for RepRapFirmware 3, but I think your Duet is running RepRapFirmware 2.
Ian
-
-
im really lost here. what should i do?
-
@NEVER-LUCKY Yes, you're using a config.g file for RRF3, but your board has RRF 2.05.1. The first line of your config.g is
; Configuration file for Duet Maestro (firmware version 3)So the config tool does tell you what firmware version it's for.Is this a new board, or was it working before? If this is a new install, either:
- If you have the config.json file you used to generate your current config.g, go to the RRF config tool and load it. Then, on the 'General' tab, change the firmware version from '3.0 or later' to '2.03 to 2.05'. Then go through and check that it's set up correctly, export config.g, and try that.
Or
- Update your Maestro to RepRapFirmware 3 (which is going to be the future of the firmware) and sort out config.g issues there.
If it was working before, revert to the config.g you were using.
Ian
-
@droftarts said in Hotend and Heated bed reading 2000deg celcius and fault:
RRF config tool
oh nice. its doing fine now.
however im getting new errors: the hotend doesnt heat up and is at -273,1 and the bed gets the error for heating up slowly.
-
@NEVER-LUCKY Which did you do, update to RRF 3, or generate new config.g? If new config.g, post it. Please post the whole config.g, as text, in the 'code' tags, using </> from the formatting bar.
-273 means that the thermistor is not connected. Probably you have defined it for the wrong pins.
Ian
-
i updated the firmware to 3.0.
; Configuration file for Duet Maestro (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Jan 18 2020 15:59:57 GMT+0100 (Central European Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Colossus" ; set printer name M665 R154 L324 B150 H700 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP 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 S1 ; physical drive 2 goes forwards 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.00 Y80.00 Z80.00 E663.00 ; set steps per mm M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure active-low endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-low endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-low endstop for high end on Z via pin zstop ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 R85 S20 ; 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 M143 H0 S130 ; set temperature limit for heater 0 to 130C 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 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 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Tools M563 P0 S"Extruder_TOOL" 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 loss -
i didnt change a thing in the config and didnt generate a new one. only the RRF is 3.0 now
-
@NEVER-LUCKY Okay. Hot end thermistor should be on e0temp, the right-hand two-pin connection here:
If it is, can you test the wiring with a multimeter? If not, try swapping bed and hot end thermistors connections, see if you get a reading for the hot end thermistor on the bed.
Ian
-
alright! its all fine the wiring was wrong... so dumb of me!
the bed heater is still fault for rising slowly though.
-
@NEVER-LUCKY You'll need to tune the bed with M303. RRF3 doesn't assume that any heater is a bed, so it just thinks something is wrong.
First, you need to get your temperature sensors reporting accurately. You're using:
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0tempT100000 B4138 is the default thermistor setting, for a Honeywell 135-104QAD-J01 thermistor that shipped with hot ends from RepRapPro, who have been out of business for 4 years! So I doubt you have the correct thermistor settings, and likely the temperature your heaters are reporting is not accurate. All 100k ohm thermistors have a resistance of 100k ohms at 25C, and will be fairly accurate at room temperature, but they report very differently as they get hotter. So please check what thermistors you have in your bed and hot end, and set them correctly, then you have a chance of accurately setting extrusion temperature.
Then, your heater settings. For full details see: https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control
Your heater settings are at the default. It looks like you haven't tuned your heaters THEN sent M500 (to store them to config-override.g). Alternatively you can copy the heater tuning to config.g. This hasn't been done, as the heater profiles in your config.g are still:
M307 H0 B0 S1.00 M307 H1 B0 S1.00While the hot end will probably heat up, the temperature control won't be smooth. So, tune heaters with something like:
M303 H0 S60 M303 H1 S200Run them each a number of times (usually three times will do), but wait for the heater to be at room temperature before doing it again. Once the results converge, send M500 to save them to config-override.g
Then either add M501 to the end of config.g so they load from config-override.g, or copy the heater settings to config.g
You can check the current heater settings by sending
M307 H0orM307 H1from the console.Ian
-
thanks for the tips!!
so now im doing the tuning by sending the commands from above, ill do it 3 times as you said, but where exactly must i add M501 in config.g ?
at the last line of ;Heaters or the last line of config.g ? -
@NEVER-LUCKY
Either add M501 to the end of config.g so they load from config-override.g, or copy the heater settings (M308 for bed and hot end) to config.g (from config_override.g to config.g)Ian
-
right. and should i send M500 after i tune the bed and then tune the hotend and send M500 again? Or can i tune the bed and hotend both 3 times and afterwards sent M500 once ?
-
@NEVER-LUCKY Send M500 after each. I'm not sure if the tunes values are applied immediately after tuning, or if they need to be saved and loaded by a reboot. Actually, you don't even have to reboot. Save with M500 which saves the values to config-override.g and then send M501, which loads config-override.g.
For what it's worth I've only ever run the tuning once. IF you do run it multiple times, don't forget to let it reach room temp before starting again.
-
for some reason my hotend fans stopped spinning. should i tune the hotend without fans?
im not sure what the problem is, the two fans stopped spinning last night, but when i click on TestFans, they do just fine and start spinning and after the test they go off.
