I've run and successfully auto-tuned. That took about 7 minutes.
I applied the values then told the printer to heat to 220degC.
It gets to 200degC fairly quickly, but the final stage is very, very slow.
I've run and successfully auto-tuned. That took about 7 minutes.
I applied the values then told the printer to heat to 220degC.
It gets to 200degC fairly quickly, but the final stage is very, very slow.
Thanks, your numbers are roughly what I get on my other printer (currently running Rumba).
I totally get the bed will take a few minutes to reach 100C, but the hot-end should be much quicker.
I'm running on 15V, but don't have a clue about the power rating of the heating block. It was previously running off Ramps 1.4.
I expect this is a tuning issue, so may look at playing with the numbers when I get in from the office.
Hmm, I think my question was lost in the mess above.
From "room temperature". How long should a typical hot end take to reach (approx) 220C?
I did run the tune (details above) and don't mind that taking a while (about 7 minutes).
My main concern is that it takes so long to stabilise on a normal heat.
I don't have much details on the hot-end other than it's a J-Head, with a proper heat cartridge (not a leaded power resistor)
Hi!
Is it normal for the autotune to complete, but then for the system to take a long time to actually reach the set-point?
The screenshot shows the autotune completed (I repeated it to get the timings listed below). My config.g file has;
[[language]]
M307 H1 A471.1 C133.9 D20 B0
However, to reach my set-point of 220degC took a very long time compared to Marlin when I autotuned that.
The hot-end was started with the temperature matching the bed/ambient (so ~23degC)
To reach 200degC took 1min 50 seconds.
To reach the final set-point of 220degC took 4mins 40 seconds!
I never had problems with Marlin autotune on this printer.
I had to back the max PWM value down on the autotune.
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Version: 1.15e (2016-10-02)
WiFi Server Version: 1.02
Web Interface Version: 1.12
Yep, I'm loving mine too.
Really getting into the finer tweaking regarding extrusion, and am seeing better and better results.
Web control is awesome, and I can see why they couldn't understand me wanting to use SD cards (unless wifi was down).
From what I understand, you can upload (I guess to the onboard SD Card) and print from that. If (or when in my case…) Wifi Drops out, it doesn't really matter.
It's a shame I'm mega busy at the moment, partying tonight, gigging tomorrow, family time Sunday, then back to the day job Monday.
I can't see me having much time on it this weekend.
Homing sequence complete Found the homez.g file and homeall.g files, tweaked and very easy once I'd grokked it.
Very flexible approach!
Thanks for your help!
Aw, thanks guys. Help appreciated. I've limited time right now and not being with the printer in the day job makes it harder to get going on a fairly new board.
I did use the Web Based on config tool (found last night), but I'm confident I'll get some good progress tonight.
I received my DuetWifi yesterday (with IR probe and Panel).
Very impressed so far.
Wifi working (occasional dropout, but I've a closer Access point that can be used.
Motion on XYZ, 16x with interpolation is much smoother than the Ramps+Polo at 16x
Love the Web Interface.
Nice to see Crimp housing and crimps included!
I'm a bit stuck on end-stops. I'll re-wire as N/C (or at least double-check what I have). Homing appears a bit different than Marlin. I've disabled Z Probe for now (just using Z end-stop on my MendelMax).
But it lifts Z a few mm then travels towards the switch but manually pressing the switch doesn't stop motion.
The End-stop switch is wired across the Input and GND (which appears correct as the input has a 3V3 pullup)
It's early days, I only had about 90mins on it last night, so hope to get it homing tonight and possibly the heated bed running.