@burtoogle:

What settings are you using for this? I've been cranking up the temperature to reduce pressure and slipping.

For a v6 with 0.4mm nozzle, bowden, titan, 1.75mm PLA @ 200deg I am using M592 D0 A0.010 B0

This gives me reasonably linear extrusion between 1mm/S and 5mm/S extrusion rate.

Thanks, will experiment with this a bit once my print finishes. Currently pushing around 14mm/s at with 0.6mm nozzle 0.4 layer heights at 100mm/s speeds. Hopefully this is the solution along with pressure advance.

Thanks. And thanks. I suspected there must be already a solution.

I've set mine to 5 taps, but if the first and second agree it moves on, and so far they always have using Piezo20 probe units (I'm using 0.03mm tolerance on that particular machine as it is not very precise, I am using 0.01mm tolerance on my delta with smart effector and sometimes it needs to probe 3 times to get agreement, but that's 10 microns, so I think its pretty good). Yes its slower than 1 tap probing, but this feature reduces the risk of a bad calibration/levelling, which does not stop or pause the print resulting in a bad print or a head crash, and this risk is greater the more automated and less attended your printer is.

Thanks for the dimming feature! It's exactly what I wanted.

@Markdnd:

Another thing to bear in mind is that, although you can use a self signed certificate, it would only stop casual snooping and is easily spoofed. To implement SSL properly (and stop browsers and web security packages bleating) would require an official SSL certificate per printer at a cost of about £40 per year.)

If you configure your browser/OS to trust your self-signed cert, you get the same kind of security as an expensive bought cert. Spoofing it with a MITM attack would trigger a security warning, just like spoofing any website cert would. So there's nothing insecure about using self-signed certs, really.

I would like a tool to issue from windows command to locate the duet on the network to learn its IP

@dc42:

This is something for the generation 3 Duets, because it needs more RAM than the current generation has and an RTOS. I already have plans for the next-generation firmware to read multiple streams of GCode from SD files at once.

Could it be done atm by assigning all the heads to a color mix mode, and instead of changing the tool, pushing a % ratio of the second, third or fourth color/material? Since for the e3d setup there’s no motion attached to the head but is a parking system if the wipe is fixed a-la bcn3dsigma as long as you can send a gcode to push 2/3/4 purge it would be already be purging (that’s the slowest part along heat/cooling). But for heat/cooling Cura already has a nice code to preheat before use, so mostly the remaining thing is just the purge.

Ofc multi gcode streams could be really nice, specially if the machine doesn’t ise a park system, but maybe (atm) is a bit overkill.

The only issue I see on my % theory is that the gcode will force the purge speed. But maybe that could be separated somehow, like just sending a G0 Purge&DontwaitToolX ?

Last time I played with baby step and tried to alter the z offset in G31 it wasn't working, I was still needing my baby steps.
Yesterday I read the changelog and old threads about baby step, maybe I should have re-probed again. Anyway I can't remember exactly what I did few months ago, I'll try again.

This definitely needs more documentation.

thanks,

Seems Repetier Host, can simulate…

If you put command M0 at the end of your slicer end gcode then it will run macro sys/stop.g when the print finishes. if that macro is not found, the firmware turns off the heaters and the motors.

There is not yet a facility to send an email when a print finishes.

Well, it's the first time I hear that there are open source (and closed source) endstops.
Anyway, here is the other side of the endstop: https://photos.app.goo.gl/ZloK0XzaNELNieJk2

It's the standard optical endstop found from hundreds of sellers on ebay.

I measured the voltage on the input signal:

no interruption: 0.99 Volt
endstop interrupted : 3.26 V
Voltage on the V-in pin : 3.27 Volt

So it gets the whole Vin voltage on the pin. I am looking again at my M574 X2 Y1 Z0 S2. S2 is now used for the Z probe to home axis, which is not my case. Should I use S1?

Later edit: I changed my M574 to S1 and M558 P4 changed to P6 and got everything working fine now. I guess I just had to RTFM better..

@dc42:

I would like slicers to flag each move with the type of that move (except where the type is the same as the previous move) as I described in my proposal for GCode that is less printer-dependent. See http://forums.reprap.org/read.php?1,803621,page=1.

I would really like this too. It just makes sense from a usability stand point - it also allows you to easily tweak settings in the machine while it's printing rather than having to stop reslice and restart. I would also like to see the filament files in firmware become more robust and have a UI that allows you to set any filament related parameters in the machine.

I know nobody really likes $tratasys but they are a good example to learn from. Their slicers only tell the machine trajectories and extrusion sizes, support trajectories, and some set up info like nozzle size (which limits the layer height and extrusion widths), as well as checking for special cases ie min layer time and special geometry, etc. Because so much of this work is offloaded for later, their slicing is much faster. You don't even have to tell it what material you are using (the machine takes care of this through the cartridge eeprom) although it can be input (I'm not sure how that affects the results). They have a couple hundred parameters in each of their material files which is specific to every material, model of machine, and nozzle size. The machines then use the on-board parameter files and the incoming information from the slicer to compile the actual moves the machine makes as the print runs.

Interesting stuff. When I get time I'll write out the differential equation that describes the effect of commanding a sudden velocity change, and see if I can find an online tool to solve them numerically.

+1 for an option to be able to pause or halt on a warning message. I'd use this if delta calibration generated a value over x mm deviation.