Posts made by pkm

Thanks David.
By "switching" I meant switching from older firmware to 1.19. I wish it was simpler.

Could you make some ALL-IN-ONE firmware file to update everything at once?

I think the switching method is a bit cumbersome. Besides, I suspect that running the web-server in ESP is better for stable printing, there won't be any lags when the web-interface is updated. I vaguely remember that the printer used to freeze for a moment when I connected to duet 0.8.5.

I'm not sure I want to upgrade to 1.19. The web-server works OK for me.

Can I just upgrade DWC to 1.16?

Please make it possible to choose and move/delete multiple files.
Thanks

Thanks!
I had 117 files in "gcodes".
It probably stopped showing new files after 95.

Please make some interface to choose and move/delete multiple files.

I counted some 95 files in web-interface.
Is there a way to remove them fast?

Yes, there are many files, I can count them tomorrow.

BTW, a few times I wanted to clean the files, but could not find a way to choose and delete many files at once. Is there any trick to do that?

I use Chrome

Hello,
I upl;oad and print a file but it doesn't get to the G-code files list. I think this problem appeared after updating to 1.18

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.18.1 (2017-04-09)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.15a

I think you can adjust autotuning to more agressive temperature rise, even if it leads to a small overshoot.

Thanks David.
I did a few tests and M307 H1 A650 C200 D5.0 B0 proved to work well enough.
Not sure why autotuning was a bit off.

The average PWM is 0.333 at 235C which corresponds to A650…

Those were settings from 1.18RC2 autotuning…
I just tried once again:

[[language]]
11:39:33M307 H1
Heater 1 model: gain 745.5, time constant 250.1, dead time 10.0, max PWM 1.00, mode: PID
Computed PID parameters for setpoint change: P6.0, I0.024, D41.9
Computed PID parameters for load change: P6.0, I0.235, D41.9
11:10:55Warning: Heater 1 appears to be over-powered and a fire risk! If left on at full power, its temperature is predicted to reach 765C.
Auto tune heater 1 completed in 328 sec
Use M307 H1 to see the result, or M500 to save the result in config-override.g
11:07:05Auto tune phase 3, peak temperature was 211.1
11:06:52Auto tune phase 2, heater off
11:05:32Auto tune phase 1, heater on
11:05:26M303 H1
Auto tuning heater 1 using target temperature 200.0C and PWM 1.00 - do not leave printer unattended

I think this might explain something:
Computed PID parameters for setpoint change: P6.0, I0.024, D41.9
This is exactly when the problem occurs, for example changing the temp from 230C to 238C is very slow.
So why is I 10 times less for a setpoint change?

Thanks, I'll try that!
IIRC autotuning said that the hotend would reach 750C at full PWM. Hard to believe, actually.
Also interesting that the dead time is 10s for hotend but 1s for bed… Does it make sense to decrease D to 2s?
I'll also try to measure average PWM at work temp.

I have e3D Volcano.
Not sure about the fan, it's been the same for a long time. And that tiny 30mm fan just can't blow too much…
Also, the hotend heats up really fast (24V 40W heater), but only up to 5-10C below the target temp, then the curve just gets flat.

If it matters, that's what the autotuning put to config-override.g recently
M307 H0 A290.3 C1404.5 D1.0 S1.00 B0
M307 H1 A722.7 C248.3 D10.0 S1.00 B0

Yep, I just installed 1.18RC2, and before that I had 1.18beta and 1.17 something.

Hello,
Since I switched to the new heating controller in 1.15, I often notice the hotend heating very slow when the temperature is 5-10C below the target.
Sometimes it takes 2-3 minutes to go from 230C to 238C!
I use autotuning and save the results. Did that a few times.
What could be the problem?

pause on heater fault
15
14
17 + filament monitor and pause on filament issue

On the contrary, I usually see the list after connection… Anyways, that's not a big deal.