E3D Tool Changer Example Config Files

jay_s_uk

@fcwilt its more to allow someone to set different speeds for the approach, but as you say, in this instance they aren't needed.

engikeneer

@fcwilt might also allow for easier editing of the approach move as some tools have different depths (e.g. hemera vs v6 bowden)?

Definitely not needed, but can make it easier to see what's going on and where you can edit things

fcwilt

@jay_s_uk
@engikeneer

All that makes sense.

It might be good if E3D is going to publish example files to have a few more comments.

Thanks again.

Frederick

gloomyandy

Remember it is not just the speed of the move it is the path that is taken as well. I think you would need a minimum of 3 moves to keep the same path. You need to be sure that there is no danger of the mounted tool hitting the other docked tools. So for instance moving directly to (-160.5, 120) or even (-160.5, 100) might not be safe to do from some starting points.

dc42

@fcwilt said in E3D Tool Changer Example Config Files:

Why are there 4 G1 commands under the ;Move In section as opposed to just 2?

Good question! I can see a reason to use three:

First move to a position that is clear of the tool but in line with it
Then move most of the way in to pick up the tool
Do the last part of the move in more slowly

My current files for 2 Titan bowden and 2 Hemera direct tools use this in tfree0.g:

G53 G1 X-160.5 Y50 F50000			; move to location
G53 G1 Y115 F50000				; move in
G53 G1 Y127.2 F5000

The Y position of the tool changed when I extended the docks to allow use of the Hemera tools.

fcwilt

@gloomyandy said in E3D Tool Changer Example Config Files:

Remember it is not just the speed of the move it is the path that is taken as well. I think you would need a minimum of 3 moves to keep the same path. You need to be sure that there is no danger of the mounted tool hitting the other docked tools. So for instance moving directly to (-160.5, 120) or even (-160.5, 100) might not be safe to do from some starting points.

I have one macro file that does all the putting and getting of tools. I prefer having all the related code together in one file.

It accepts parameters from -1 to 3.

Passing -1 puts the current tool back in the dock. Passing 0 to 3 gets that tool from the dock.

The code performs various error checks and insures the proper paths are taken.

Frederick

gloomyandy

@fcwilt So do you have it all working? How many tools and what type?

fcwilt

@gloomyandy said in E3D Tool Changer Example Config Files:

@fcwilt So do you have it all working? How many tools and what type?

I have the tool putting and getting working. For testing I have just been putting and getting the blank tool plates.

I have only one tool and last night decided I wasn't happy with it.

So today I am printing the parts for another one that I hope I will like better.

Frederick

gloomyandy

@fcwilt One of the things I've found is that fine tuning multiple tools can be tricky. The way the tool sits in the dock can be slightly different for each tool which may mean you need to adjust the pickup/drop off code for each one to get really reliable changes. A combination of several 3d printed parts joined together by bolts all of which have tolerances, needing things like the docking pins to be able to slide, the tension from the filament feed and control wires all add up. Keeps you busy though! Good luck....

fcwilt

@gloomyandy said in E3D Tool Changer Example Config Files:

@fcwilt One of the things I've found is that fine tuning multiple tools can be tricky. The way the tool sits in the dock can be slightly different for each tool which may mean you need to adjust the pickup/drop off code for each one to get really reliable changes. A combination of several 3d printed parts joined together by bolts all of which have tolerances, needing things like the docking pins to be able to slide, the tension from the filament feed and control wires all add up. Keeps you busy though! Good luck....

Thanks.

This is the chunk of code which specifies the finally XY position for each tool where docking/undocking will be attempted:

; --- set xpos and ypos variables based on tool variable ---

if   var.tool = 0
  set var.xpos = -156.9 ; determined by testing
  set var.ypos =  141.5 ; determined by testing
elif var.tool = 1
  set var.xpos =  -67.6 ; determined by testing
  set var.ypos =  141.5 ; determined by testing
elif var.tool = 2
  set var.xpos =   67.0 ; determined by testing
  set var.ypos =  141.8 ; determined by testing
elif var.tool = 3
  set var.xpos =  157.0 ; determined by testing
  set var.ypos =  141.8 ; determined by testing