[HELP] Ender 3 Pro + Duet WiFi 2
-
@Phaedrux
I'll do those changes soon and update.
one question about the leveling procedure, so when I homeall and it does the Z axis I can see that the bltouch stops the motor, but how does it know if the bed is leveled? isn't it supposed to take samples from different locations on the bed to do that? -
homeall does not do bed leveling.
G29 does mesh bed leveling
-
See here: https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation
The ender 3 doesn't have any way to "level" the bed other than the adjustment screws on the bottom of the bed. So getting those leveled to begin with is important. Mesh compensation takes probe readings from many points on the surface of the bed and creates a height map to automatically adjust the Z height during a print to keep the nozzle the same distance from the bed.
An important part of the z probe setup is getting the offsets correct. See here: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
@Phaedrux
Changed the Z speeds and it looks much better.
Regarding the extruder, I tried to do the configuration using the guide but my extruder doesn't extrude anything
if I look carefully at the motor it seems like the wheels/brass things are turning a bit and then turning back to the same spot as before and the filament is not moving anywhere. any suggestions on that? -
Is the hotend heater on and at temp?
-
@Phaedrux
It was the cable... I switch with the X to check and the motor works.
I ordered an extra cable, in the meantime I'll calibrate the extruder and follow the guide for the bedmesh and update later. -
Hey guys,
so I managed to calibrate the extruder and to create the mesh grid successfully. I can finally see progress with this upgrade (thanks to you!). I'm still waiting for the cables to arrive and finally close the case with all the wiring appropriately.
Is there anything specific that I should add to the configurations?
I've noticed that I can set the amount of amps to each motor, should I modify this or just leave it as 800 800 900?thanks!
Didi -
set them to 75% of the rated current.
i think the ender motors are 1A so 800 is close enough.
touch them during a print to see if they dont get to hot. -
800 sounds fine for the Ender, though some people find the motors noisy, so lowering the current a bit might help, though you're limited to 100ma steps and if you go too low you risk heavy axis like Y skipping steps. I wouldn't go lower than 600.
-
So I just printed a bed level print and it looks great. one thing that bothers me is that whenever I start the print it go into slow motion mode (all motors becomes extremely slow, but on the initial homing everything was fine, just when I sent the print). after the print I wanted to see if this continues and it is, every movement (no matter which axis) is slow. did the print itself had like instructions to move slow or something? I checked the config file and it looks okay.
-
@didi767 I bet you're using cura and the start gcode section has some commands that override your speed settings. Check there first.
-
Hey guys,
I don't see that my part cooling fan is turned on at any stage.
I tried to manually send a command to start it but nothing. I've connected it to the FAN0 on the board and it appears like this in the config:; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Part Cooling" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"Hot End" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1:0 T45 ; set fan 2 value. Thermostatic control is turned on -
What command did you send to start it?
M106 P0 S1 should do it.
Does the fan itself work if you connect it to the always on fan port?
-
@Phaedrux I tried that command, the problem was that the fan was faulty (maybe I burned it or something :))
I replaced it and it works now. but I have to manually turn it on when printing, doesn't it supposed to start automatically whenever I print?
trying the new configuration now with first print, looking good so far
-
@didi767 said in [HELP] Ender 3 Pro + Duet WiFi 2:
doesn't it supposed to start automatically whenever I print?
Can you post your gcode file so we can see if the slicer is trying to turn the fan on? Or can you search it for an M106 S command?
-
@Phaedrux So I guess it was something in the gcode. it did start from time to time. so the fan is okay.
I wanted to ask something else, so few prints have failed, at the end, and then i noticed that my first few layers are not really sticking to the bed so well, so I changed the bed to glass and did the bed leveling and changed the btlouch offset (which is 1.250, is that okay?) and still it seems like it doesn't really stick well, should I increase the bed temp? (currently it's 60).
I manually level the bed with the piece of paper method and then run the mesh compensation (also when I'm loading it, it gives me a warning message: "Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset."so unfortunately no successful prints so far, hopefully you can help out. Thanks!!
-
So I just tried to print a bed leveling test and it doesn't really look good. in some corners the squares look great and in other the PLA didn't stick to the bed. Isn't the mesh compensation supposed to take care of this issue?
I also tried to fine tune the nozzle after the "G30 S-1" command as described in: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Calibrate_the_Z_probe_trigger_heightAm I missing something?
-
@didi767 said in [HELP] Ender 3 Pro + Duet WiFi 2:
changed the btlouch offset (which is 1.250, is that okay?)
You should measure it. https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Calibrate_the_Z_probe_trigger_height
@didi767 said in [HELP] Ender 3 Pro + Duet WiFi 2:
"Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset."
That's a bit of a problem. Post your current config.g, homeall, homez, and slicer start gcode so we can see what's happening at the start of the print. The error basically means that the heightmap was loaded before the bed has been probed with a G30.
-
-
from your homeall.g
G29 S1
G30 ; home Z by probing the bedmove the G29 S1 to the start g code of your slicer, after the G28