Delta Printer - Start of Print

number40fan

Is there a way to tell the printer to come down on the outside edge of the bed, run a priming layer towards the middle and then start printing? Getting tired of having to baby sit it to pull the stringy mess off of the nozzle before it starts. Which will end up smack dab in the middle of the print if I don't. I do use a big brim, but it doesn't help.

Yonkiman

An auto-wipe function like that is a good idea. If you can write the gcode to do what you want, you can add that gcode to the starting script of your slicer or as a .g macro file for the firmware.

If you can't come up with the gcode to do what you want, then it's probably not possible. For example: does your delta design allow you to move the head over the edge of the build plate? (I don't think mine will, but I'm gonna check.)

Yonkiman

Here's a page talking about what you want to do: http://reprap.org/wiki/RepRap_Firmware_macros#Head_cleaning

Earlier on that page they mention a start.g file (not in the Duet sys directory by default, but you can add it):
[c];/sys/start.g Executed at print start (add 'M98 P/sys/start.g' in your slicer start code)[/c]

dc42

@Yonkiman:

An auto-wipe function like that is a good idea. If you can write the gcode to do what you want, you can add that gcode to the starting script of your slicer or as a .g macro file for the firmware.

If you can't come up with the gcode to do what you want, then it's probably not possible. For example: does your delta design allow you to move the head over the edge of the build plate? (I don't think mine will, but I'm gonna check.)

You can use M564 S0 to temporarily allow movement outside the normal area, and M564 S1 to resume applying the limits.

number40fan

I have my swipe setup in the O:/sys/start.g, but didn't work. Is there something in the gcode that is keeping it from working?

G90
M82
M106 S0
M140 S70
M190 S70
M104 S210 T0
M109 S210 T0
M104 T0
G28 ; home all axes
M98 O:/sys/start.g
G92 E0

Start of the print gcode.

DjDemonD

Why is it o:?

I normally call a macro using

M98 Pstart.g

number40fan

Everything else is O:, so I figure that is what it needed. I'll switch and try again.

O:/sys/config.g etc….

When I created the start folder it put it as O: as well.

number40fan

Changing it O: to P: in the beginning of the print gcode didn't help. It must be how I have my start.g file in the directory.

number40fan

Going to drop the colon after the P and give it a try.

number40fan

Yep, that worked. Thanks.