firmware 3.4 Rc1 Heater Fault
-
when I start tuning takes too long something in the algorithm must be changed. if I put 3 as hysteresis comes to completion for example. something needs to be changed in the tuning procedure. my hotend is geometrically excellent, it is designed to perform every temperature and material
-
@massimilianoconti do me a favour and run the tuning and post the results here.
-
10/2/2022, 13:29:16 Warning: heater behaviour was not consistent during tuning
Auto tuning heater 1 completed after 3 idle and 50 tuning cycles in 2520 seconds. This heater needs the following M307 command:
M307 H1 R2.558 K0.275:0.103 D6.31 E1.35 S1.00 B0 V23.9
Send M500 to save this command in config-override.g
10/2/2022, 13:05:33 Warning: heater behaviour was not consistent during tuning
Auto tune starting phase 4, measuring with fan on -
@massimilianoconti said in firmware 3.4 Rc1 Heater Fault:
my hotend is geometrically excellent
Can you give us some details about it?
-
my hot end is Phaetus dragonfly bmsBMSÕ«×Õ+⵿íÕ×ï.stl BMS Wireframes (7).pdf
-
That's a lovely hotend. What power is the heater? Are you using the sock? Do you have a part cooling fan and duct? Can you share an image of the temperature graph from the tuning?
-
@massimilianoconti said in firmware 3.4 Rc1 Heater Fault:
M307 H1 R2.558 K0.275:0.103 D6.31 E1.35 S1.00 B0 V23.9
Have you tried bumping up the "deadtime" D6.31? I bumped mine up to D8.31 and the heat faults have gone away.
-
I try thanks
-
you have the silicone socks I'm reviewing everything as soon as I perform a new test I attach it
-
hello as soon as I have the data I attach them. I wanted to know what compiler you need to open the source code to change the firmware... from the asset I downloaded in zip the purge code but you need a compiler ...
-
