Heater Will not turn off once started.

Phaedrux

Can you pull your SD card from the board and then power on and see if the heater still starts to heat automatically?

Turricann

@Phaedrux if I do that I would expect the heater to be off.. the issue seems to be once its on it will not turn off.

Veti

@Turricann
pheadrux wants to test if your mosfet is blown. that is a quick way to test it.

Turricann

What i have done to prove its not hardware is heated the hotend to 200 degrees then powered down and removed the PI I/O cable, when powered back up the heater stayed off.

I then Powered down again and refitted the I/O cable, when powered back up and the temp was @145 degrees fan came on and heater came on although temps were set to 0 and status set to Off.

It seems to be when the hotend fan is on the heater is running ... so if temp goes above 45 degrees fan turns on and heater will not turn off.

If thermostatic control is turned off the fan then the heater comes on when the board is powered ( actual timing is when Pi is booted).

T3P3Tony

@Turricann I am slightly confused by the thread. is the 6HC running in stand alone mode or with an attached SBC?

In either case what version of firmware are you running? Please try upgrading to 3.2b4.1

I have noticed one off thing with your config:

M106 P1 S1 H T45

H should have a heater number after it or be set to -1 (and i assume it is not intended for it to be off) not sure how you have the fans connected as you only have 1 hotend heater configured but if you want these fans to be based on the heater then this should be H1

Turricann

@T3P3Tony The setup is a duet 3 6HC running with a Pi , the pi has its own 5a supply. I am upgrading the firmware and the software to the latest as we speak but originally I was running RRF 3.1.1.

As for the fans currently I have 3 fans on out7,8,9 but nomatter which header I use the same issue occurred.

Yes m103 its set to H1 must of captured that while making changes.

Phaedrux

Can you also send M98 P"config.g" in the console and report the results?

Turricann

not any more since updating to RRF 3 beta 4 i am getting DCS failed to connect to duet 3

Dec 11 22:11:20 duet3 DuetControlServer[3872]: [info] Settings loaded
Dec 11 22:11:21 duet3 DuetControlServer[3872]: [info] Environment initialized
Dec 11 22:11:21 duet3 DuetControlServer[3872]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Dec 11 22:11:21 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Dec 11 22:11:26 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 22:11:26 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 109.
Dec 11 22:11:26 duet3 systemd[1]: Stopped Duet Control Server.

Phaedrux

Can you start from a freshly downloaded version of DuetPi and then update from there with sudo apt update sudo apt upgrade?

https://pkg.duet3d.com/DuetPi-lite.zip

https://pkg.duet3d.com/DuetPi.zip

Turricann

Still the same DCS is not started. RRF 3.1.1 --> board has 3.2 beta 4

Phaedrux

Are you saying you started with a fresh image and updated, then added the unstable branch and updated again?

Turricann

No the image on the Pi is the one from the link but just checked,

pi@duet3:~ $ sudo apt list duetcontrolserver -a
Listing... Done
duetcontrolserver/stable,now 3.1.1 armhf [installed,automatic]
duetcontrolserver/stable 3.1.0 armhf
duetcontrolserver/stable 1.2.4.0 armhf
duetcontrolserver/stable 1.2.3.0 armhf
duetcontrolserver/stable 1.2.2.1 armhf
duetcontrolserver/stable 1.1.0.5 armhf
duetcontrolserver/stable 1.0.4.1 armhf
duetcontrolserver/stable 1.0.3.1 armhf

Phaedrux

Yes, and you can either update the Pi to also be 3.2 b4, or flash the duet back to 3.1.1

Phaedrux

If you wish to use the latest unstable DSF components, you can run the following commands instead:

wget -q https://pkg.duet3d.com/duet3d.gpg
wget -q https://pkg.duet3d.com/duet3d-unstable.list
sudo mv duet3d.gpg /etc/apt/trusted.gpg.d/
sudo mv duet3d-unstable.list /etc/apt/sources.list.d/duet3d-unstable.list
sudo chown root:root /etc/apt/trusted.gpg.d/duet3d.gpg
sudo chown root:root /etc/apt/sources.list.d/duet3d-unstable.list

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

Turricann

Thanks that is what i needed to sort that issue, I upgraded to try and resolve the original issue about the heater recommended by @T3P3Tony ,

I will redo config.g now and see what happens with the heaters.. thanks for your support.

Turricann

OK config.g redone left every thing else default from a clean install on the Pi

On my duet 3 6hc i have the below,
Running on a 24v supply

Out0 - heatbed. - on/off working OK
Out1 - 24v heater.
Out7 - Hotend fan
Out8 - Partcooling fan
Out9 -Partcooling fan (Disconnected)
TEMP0 - Heatbed thermistor(B9350)
TEMP1 - Hotend Thermistor (B4138)
Temp3- Thermistor from Z probe.
IO_0 = pannal Due - currently disconnected.
IO_3 = Z probe Pinda v2 type
Driver 0 = X
Driver 1 = Y
Driver 2 = Z1
Driver 3 = E0
Driver 4 = Z2
Driver 5 = Z3

Thats is everything connected and my config.g is,

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.10 on Mon Dec 07 2020 21:49:17 GMT+0000 (Greenwich Mean Time)

; General preferences
G21 ; Work in millimetres
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name
M669 K1 ; select CoreXY mode

; Drives
M569 P0.0 S0 ; physical drive 0.0 goes backwards (X)
M569 P0.1 S1 ; physical drive 0.1 goes forwards (Y)
M569 P0.3 S1 ; physical drive 0.3 goes forwards (E0)
M569 P0.2 S0 ; physical drive 0.2 goes backwards (Z1 Front Left Motor)
M569 P0.4 S0 ; physical drive 0.4 goes backwards (Z2 Back Left Motor)
M569 P0.5 S0 ; physical drive 0.5 goes backwards (Z3 Right Motor)

M584 X0.0 Y0.1 Z0.2:0.4:0.5 E0.3 ; three Z motors connected to driver outputs 2,4 and 5
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation

M671 X205:205:-195 Y-205:205:0 S0.01 ; leadscrews at Front left (X195 Y195), Rear left (X195 Y-195) and right (X0 Y-195)

M92 X160.00 Y160.00 Z80.00 E420.00 ; set steps per mm M92 X80 Y80 for 1.8º degree steppers and M92 X160 Y160 for 0.9º
M566 X600.00 Y600.00 Z360.00 E600.00 ; set maximum instantaneous speed changes (mm/min)

M203 X6000.00 Y6000.00 Z600.00 E1200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z120.00 E120.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1800 I30 ; 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 X410 Y410 Z410 S0 ; set axis maxima

; Endstops
M574 X1 Y1 S3 ; use stall guard for XY endstops (X min, y max)
M574 Z1 S2 ; Set endstops controlled by probe

;M915 X Y R0 F0 H400 ; Stall guard config when not homing

; Z-Probe

M558 P5 C"^io3.in" I1 H1 F1000 T6000 A20 S0.005 ; Prusa PindaV2 sensor config.
M308 S2 P"temp3" A"Pinda V2" Y"thermistor" T100000 B3950 ; Prusa PindaV2 temperature config.
G31 P500 X0 Y30 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:375 Y15:375 S20 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; 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"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
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 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0.7 H1 ; set fan 0 value. Thermostatic control is turned
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out9" Q500 ; create fan 2 on pin out9 and set its frequency
M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 S"HOTEND" 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
M575 P1 S1 B57600 ; enable support for PanelDue
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
T0 ; select first tool

Phaedrux

@Turricann So with a fresh config and Pi the heater is still staying on once enabled?

But it's not turning on automatically when power is first applied, right?

Turricann

yes that is correct as long as the hotend is below 45 Degrees or fan0 has not got thermostatic control disabled .

If thermal control is enabled and the hotend is below 45 degrees the heater will turn on and off normally,
If its above 45 Degrees the hotend will come on with power.

This is why i came to the conclusion the heater will not turn when the fan is on.

one more thing is if there are no fans set up i cannot control the heater.

Phaedrux

It looks like your config was pasted twice maybe in your last post?

Turricann

One other thing is when the heater comes on at power up its not instant there is about a 30 second delay like it only happens when the pi powers up.