And now it works… many thanks!
David - is it worth noting that gotcha in your IR sensor instructions? I'm sure I won't be the last to fall for that one.
I have just had to take the nozzle out of my E3Dv6 for cleaning, and now I can't get the height right. Regardless of the value I put in the config.g file's G31 command, after the Duet is reset the nozzle comes down a little too far and grabs the paper too tight. Lifting the nozzle 0.3 gives me exactly the clearance I want. What's confusing me is that it seems that no matter what value for Z I put in the config.g file, the clearance always ends up too small, and Z+0.3 always sets the gap right. It's as if whatever I put in the config.g file is being ignored and it's still using an old value from somewhere.
Duet 0.6 running 1.19.2 firmware
V1.2 mini height sensor board
I do use bed mapping.
The process I followed (from the Mini height sensor board web page):
1. Heat the bed and hot-end to working temperature.
2. Home X and Y, then move the carriage to the centre of the bed.
3. Lower the head until the nozzle just grips a sheet of thin paper.
4. Send G92 Z0
5. Raise the head 5mm and remove the paper.
6. Send G30 S-1
7. Read the value for Z in web page, or from M114 (I get 0.787).
8. Put the value into the M32 line of config.g (G31 P500 X0 Y0 Z0.787 ; Set threshold and offsets)
9. Save config.g and accept the Duet reset.
10. Heat the bed and nozzle again, home everything, and retest.
This is all very frustrating, as this setup has been working happily for many months. However I do seem to have problems every time I try to set the nozzle height… Am I missing a step here? Am I doing something wrong?
One other reason for me using Cura is that I find slic3r very flaky - it sometimes crashes when I add a STL file, for example. I also find the whole structure of slic3r inconvenient - I have to have 10 or 12 different setup files simply to accommodate the different diameters of filament I use. In Cura I just find the relevant line and change the number. The same goes for infill, etc.
I would like to use Cura, but it crashes under linux. The python gui seems to have had this issue on early versions too.
How up-to-date is your linux kernel? My installation of Cura used to crash regularly until a kernel update fixed a bug in Mono - which was something that the Cura author couldn't work around.
The Mono bug went away about a year ago, so if your kernel is older…
A Cura plugin for controlling a Duet with RepRapFirmware.
Thanks to resam for this, thread is here:
I tried installing that, but I couldn't get it to appear in the plugins/extensions list. I recently updated Cura to 3.1.0, so maybe this hasn't caught up?
I seem to be in the minority - but I prefer Cura. It just seems to produce a nicer end product. It's not perfect, as sometimes it doesn't provide support where i'd expect it to, but generally it's my preferred slicer.
One of these days I'll go mad and pay for a slicer… but I haven't felt the need yet.
I had this problem a while back! The cure for me was to put an 'E' after the comment semi-colon, like this:
G1 Z220 ;E drop the print bed (E to exclude from layer count)
(Obviously, you need to be in absolute positioning mode for this to work)
I recently changed to 0.9 degree steppers for the X and Y motors on my CoreXY - that made a huge difference to the noise level. The Duet board drives them properly and quietly. Not just that they are quiet in themselves, but the assorted resonances I was getting from the frame and its panels have also gone completely.