Hi everybody,

i measured power-draw at the wall outlet:
Just the Duet: 9W
Starting bed heating: 320W
Later on, at 60C: 280W.

So the bed heater uses around 310W at the beginning and 270W later on.
Seems about correct.

So i don't know what i measured or remembered from before. I guess i will live with the heat-up times for now. At least i am finished with ABS printing for now. Too much warping even on small parts (7x7x8cm) without a full enclosure. I will go back to PETG, so heating times will not be soooo bad.

THX for all your input!

Greetings,
Markus

Hi Ian,
i use a 6mm aluminum plate, with glas on top.
The thermistor is inside the silicon heat pad and should show a temp change really quick.
Actually, the glass itself is not lagging behind much in temperature. When the thermistor shows 100C the glass has reached 98C. (measured via infrared)

I will use a "power-outlet energy cost measuring thing" tonight to see how much current is drawn while heating only the bed with nothing else connected.

I will report back
Side note: The thing is that i was absolutely happy with the new printer regarding the heat-up times. They were much faster than my old i3 clone (Anet A8). Now they are slower - so something has changed.

Greetings,
Markus

@peirof:

Can you try another heat cartdrige?

Its the heat bed… not the hotend...
Unfortunately i do not have another heatbed available at the moment.

THX for all your ideas.

Measured resistance is - as reported in first post - 1.6 to 1.7Ohms - which corresponds nicely with the 350W the pad should have at 24V.

BUT - direct connection to the power supply showed no improvement. (good idea!)
Heat up to 80C still takes 8:10 minutes.
(Bed heater still uses bang-bang mode)

So either my power supply is bad - which i dont think since the DuetWifi still reports 24.3V while the bed is heated directly connected to the power supply.
Or the heat pad is bad, but somehow shows the correct resistance…...

Strange.... but the Duet itself is now taken out of the equation.

Greetings,
Markus

@dc42:

Have you checked that the screws in the power input and bed heater terminals on the Duet are still tight?

Yes, they were tight and are now tight again….
Warm-Up time to 100C was 16 Minutes tonight

If there are no options to set the current in the configuration it can only be

• a defective head pad?
• power supply issue?

Or can the duet itself be affected somehow?
Am i correct to think of the duet as a "on/off" switch regarding the bed heater connector? So it should route through the whole current or nothing... but not a reduced current/voltage?

Strange thing is that the system works just fine - only very slow heating....
Voltage during print is 23.5 to 24.2V - i guess with and without heating the bed.

Greetings,
Markus

Hi,
the first days after setting up the DuetWifi everything was fine: the bed heated extremly fast.

Now i need around 9 minutes to reach 80C or approximately 14 Minutes to 100C.
Friends with nearly the same hardware need only 4 minutes to 80C and i am sure that it initially was a lot faster.

Initially i used firmware 1.19, now i use 1.20.
I do not know if the changed heating behaviour occured only after the firmware change since i used only PLA during the change time.
Now that i use ABS again i noticed the slow heat-up.

I have measured the resistance of the silicon heatpad: 1.7Ohms. Which gives me round about the 350W @ 24V that are promised.

Any ideas what could cause this behaviour?

Are there settings in the configuration that limit the current for the heatbed?

My setup:
300x300 heatpad 24V, 350W.
DuetWifi, Firmware 1.20
Meanwell 500W 24V power supply

THX for any ideas what i could check to find the error.

Greetings,
Markus

THX David.

Even renaming the old www folder to www_old and copying a "new" 1.19.3 WC did not help.

Then i upgraded to 1.20RC3 and noticed that DWC did not upgrade to 1.20 even though the files were correctly uploaded.
I completly deleted the old www folders (www and www_old) and created a new one with the 1.20RC3 contents… now it works.
Thumbs UP

I am still trying to figure out why the SD-card contents was not recocgnized correctly though….

Hello everybody,

i am having trouble to set up the Duet for my Hypercube Evolution.

Not working for me in WebControl

• Set temperatures for Bed and Hotend.

• -> "chamber heater not defined" (???) and Java Script error

• Extruder Control

• -> no reaction at all - even after "M302 P1"

What is working:

• Homing

• Heating Bed manually by G-Code

• Using Extruder-Motor by G-Code (after using M302 P1 to enable cold-extrusion)

What catches my eyes is that the text "Heater1" etc. is not colored in WebControl as in the example screenshots i saw.

I would be very gratefull for any help.

Greetings,
Markus

---

As much additional information as possible :

Software Versions:

Complete Web-Control-Window:

Pushing the "extrude" button in the "Extrude Control" does nothing…..

Trying to heat Heater1 using the dropdown selection box next to "Heater 1":

When trying to heat the bed using Button next to "Heater 0"

My config.g:

[[language]]
; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sun Dec 17 2017 22:14:21 GMT+0100 (Mitteleuropäische Zeit)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z280 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 S1 ; Set active high endstops
;M558 P0 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
;G31 P600 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S20 ; Define mesh grid

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation
M92 X80 Y80 Z405 E95 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z1200 E4800 ; Set maximum speeds (mm/min)
M201 X700 Y700 Z250 E250 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C

; Tools
M563 P1 D0 H1 ; Define tool 1
G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C

; Network
M550 PHEVO ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured

; Miscellaneous
T1 ; Select first tool

Photo:

Hi,
thx for the long response.

I do not have a probe. I wanted to use two seperate "normal" optical endstops on both sides of the heatbed to automatically "level" it. (not for real leveling, just for keeping both leadscrews in sync).

But i have now found another "problem": the normal DuetWIFI i already purchased has not enough Z-Stepper drivers IIRC. I guess normally both Z-motors are controlled by one driver?
Since i want to keep the option to print two different filaments i will need both extruder drivers…..

Greetings,
Markus

Hi,

is it possible to use double Z optical endstops to level the heatbed in the direction between dual Z-motors?

See:
https://www.thingiverse.com/thing:2501604

THX
Markus