Im getting a basic error:563 bad driver number for my heater 1

Phaedrux

Don't run those. They are for factory testing and you won't have the same hardware connected obviously.

You can test the heater by turning it on in the web interface.

Jeffrey_101

@Phaedrux
i tried but it trips an error
Error: Heating fault on heater 1, temperature rising much more slowly than the expected 1.7°C/sec
its wired to the correct heater and everything

jay_s_uk

PID tune your hot end and your bed.
For your bed

M303 H0 S60

For your hotend

M303 H1 S200

Tune your hotend with it close to your bed and your part cooling fan running at the speed you would usually use for printing

Phaedrux

After tuning PID send M500 to save the results and add M501 to the end of your config.g to load them at startup.

jay_s_uk

yes, that helps

Jeffrey_101

@jay_s_uk
im thinking the hardware might be broken
9/24/2020, 1:59:35 PM Auto tune cancelled because temperature is not increasing
9/24/2020, 1:58:58 PM Auto tune phase 1, heater on
9/24/2020, 1:58:53 PM M303 H1 S200
Auto tuning heater 1 using target temperature 200.0°C and PWM 1.00 - do not leave printer unattended

jay_s_uk

@Jeffrey_101 where do you have the heater wired into?
maybe post a photo

droftarts

@Jeffrey_101 said in Im getting a basic error:563 bad driver number for my heater 1:

im thinking the hardware might be broken

Unlikely. If you have a multimeter, disconnect the heater wires from the Duet, and test the resistance of the heater wires where they connect to the Duet. A 'normal' hot end heater should have a resistance of around 4 to 15 ohms, depending on voltage and power.

If you've run the 'factory' macros, reset your board. I seem to remember that they set the heaters to non standard settings.

Ian

Jeffrey_101

@jay_s_uk
the setup is messy rn because my printer is down XD

jay_s_uk

ok. you're wired into E1 heater and yet you're using E0.
Move the heater to the other green block next to where you're wired in.
Do it without power just incase!

Jeffrey_101

wow, that embarrassing haha, i tried that before but that was when i was running the RRF3 config on the RRF2 firmware, It works now! i learned a lot thank you for all your help!