Yeah I started there but when I asked for 16 points it wouldn't generate the points, "suggest probing points" was greyed out. In the end since my maths has utterly left me, I just moved the head around manually and entered the coordinates of some suitable points.
Also nowhere on the page does it ask for Probe offset. It is a very useful tool, I might run some of the numbers on my Kossel Mini through it.
I'd like to add my thanks here too! The community around the Duet is by far the most helful and friendly I have come across. It is partucularly helpful having core developers like dc43 and T3P3Tony around and willing to answer questions. Maybe it's becuase we're all mad keen to make the most out of our kit?
Well, after much testing (and some time off to do a few other projects) I've come to the conclusion that the probing issues I've had with the IR Probe are due to the fact that I use CA to fix scratches and divots in my PEI. PEI has different IR characteristics. I developed this "fix" for PEI several years ago to allow me to have a perfect first layer as that is the most visible on the fly fishing reels I manufacture. I love the idea of the IR probe but its nearly impossible to visually tell where a CA fix has been made in order to change the probing location. I've gone back to my FSR probing and everything has been working great.
It's not been extensively tested to determine if it will shut off the power before a fire begins, but it does latch in an off state when smoke is detected and requires manually resetting once the fault has been cleared, I expect it would work best in an enclosure. No false triggers yet after over a year in use, no genuine one either thankfully. It's obviously independent of the controller, and fairly simple.
What I have started using on my new printer is a plug-in rcd (ground fault device) right next to the machine. I can hit the test button as an emergency stop or general off switch, it should protect me against a mains heat bed problem and its double pole so shuts off the power to the device completely.
Hi Pete, yes I think the problem is in the gcode at the start of the file. There are commands to set the tool temperatures but no commands to select tools until the first T0 command. Also it has commands like G1 T0 E8 but I have never seen a T parameter used on a G1 command before or documented anywhere.
You should aim for your start gcode to look something like this:
G10 T0 S220 R170 ; set tool 0 active and standby temperatures
G10 T1 S220 R170 ; set tool 1 active and standby temperatures
T0 ; select tool 0
G1 E8 ; prime tool 0
I have chosen a standby temperature of 170C in the above but you may want to adjust that.
Also, we recommend to select relative extruder coordinates if your slicer supports it.
Just a quick update on this for anyone who comes across this thread. It seems that T0 isn't triggered during a macro. What makes it freaky is that pressing a move button on DWC doesn't just send a simple G1 move command so it is treated like a macro as far as the trigger handling code is concerned. The triggers work fine if I use use say G1 Z100 F240 in the top left corner of DWC and hit send but if I press the "Z+100" button on DWC.they are ignored. DC42 has it in mind to change the handling of T0 triggers in his next firmware release (but please don't nag him - he's a very busy man).
Nice, congrats! I just got my (first) wifi in too, and I'm contemplating on whether I should save it for my new cartesian prototype, or put it in my delta in place of the 0.8.5. Besides quieter operation, I'm not sure if there is much other reason to replace the perfectly fine 0.8.5, is there?
In the future I would like to modify the firmware to act as both a laser burner and 3D printer while only swapping the printer head. Has this already been reduced to a simple fix or will I have to brush up on my coding skills?
1. Add an extra tool with an unused E drive (haven't checked yet if M571 requires one to be configured, but I'd assume so)
2. Run M571 in the tool change macros of your new tools. That way you could enable and disable this particular feature for a specific tool.
3. Use G10 to set the offset of your laser
Chrishamm maintains the web interface. I suggested to him some time ago that we should time stamp each file with either the upload date or the last-modified date of the original file. I expect he will read this, but I'll add it to my work list anyway.