Welcome to the SeeMeCNC Community

If you've done the setup right you just pass the tool name...T0 or T1, etc...

IMBoring25 wrote:If you've done the setup right you just pass the tool name...T0 or T1, etc...

Pass it as a command like a G or M code? I did try to send it via that and it locks up. I can pause the printer and then switch tools but the prior tool unloads the filament despite a retraction of -5.

I can print easily with all extruders just a bit of treble switching tools.

Thanks.

I don't have it in front of me but your sd card should have several g-codes on it...t0-pre.g, t0-post.g, and t0-free.g, as I recall, would be the ones for the first tool. Pre is the g-code to run before the tool is selected. Post is the g-code to run after it is selected. Free is the code to run when it ceases to be active.

After your tool change macros make sense, check that your tools are configured correctly. For a single-out hot end, all the tools should specify the same heater and active and standby temperatures.

I did set up these pre,post and free files per RepRap site. I will post them when back to my Mac. Even when I left these blank it stil would unload the filament. Somewhere there is a code that is messing this up.

Thanks.

Here are my Pause.g and Resume.g files.
M83 ; relative extruder moves
G1 E-4 F2500 ; retract 4mm
G91 ; relative moves
G1 Z2 F5000 ; raise nozzle 2mm
G90 ; absolute moves
G1 X0 Y200 F5000 ; move head out of the way of the print

G1 R1 Z2 F5000 ; move to 2mm above resume point
G1 R1 ; lower nozzle to resume point
M83 ; relative extruder moves
G1 E4 F2500 ; undo the retraction

Here is an example of my Tool.g change files.

; tfree1.g
; Put G/M Codes in here to run when Tool 1 is freed
M83 ; relative extruder mode
G1 E-5 F2500 ; retract 5mm

; tpost1.g
; Put G/M Codes in here to run after Tool 1 is selected
; un-comment the following line if you have a dual-nozzle build
M116 P1 ; wait for tool 0 only to reach operating temperature
M83 ; relative extruder mode
G1 E5 F2500 ; undo retraction

; tpre1.g
; Put G/M Codes in here to run before Tool 1 is selected
; un-comment the following line if you have a dual-nozzle build
G1 X0 Y0 F6000 ; move the head away from the print

All of this is based on information in the following link.
(http://reprap.org/wiki/Configuring_RepR ... on_section)

Thank you!! Any help in understanding why my released tool completely unloads would be a awesome. I will keep reading!!!


...................................................

Addendum 5/15/2016: Here is a link to my newest config.g files and other set up files!!!

(http://forum.seemecnc.com/viewtopic.php ... 654#p90654)

Are you using absolute extruder coordinates otherwise?

IMBoring25 wrote:Are you using absolute extruder coordinates otherwise?

Hummmm. Will have to check. Maybe that is it??

if you are, a -5 would definitely do it unless you added a code to change it to incremental before doing that.

I do have my extruders set to: M83 ; relative extruder moves in my config.g.

However I notice that I have an M90 and M91 commands in my pause.g. This needs to be an M82 and M83, respectively correct?

Suggestions on how to do this. Put an M82 command into my tool commands! If so should I put the M83 back in?

Thanks.

I'm not sure exactly how extruders move specifically the effect of relative vs. absolute. The wiki doesn't give those details.

You (or your slicer) can override absolute/relative settings at any time. If the slicer is taking you to absolute extrusion in its start gcode, going to relative in your tool changes and not returning to absolute before returning to the generated gcode will be problematic.

The G90 and G91 sequence puts you in relative coordinates for a 2-mm lift in Z. That reference is correct, provided you're otherwise using absolute x, y, and z coordinates (which is typical).

IMBoring25 wrote:You (or your slicer) can override absolute/relative settings at any time. If the slicer is taking you to absolute extrusion in its start gcode, going to relative in your tool changes and not returning to absolute before returning to the generated gcode will be problematic.

The G90 and G91 sequence puts you in relative coordinates for a 2-mm lift in Z. That reference is correct, provided you're otherwise using absolute x, y, and z coordinates (which is typical).

So my above codes look appropriate, the question is if my slicer is giving an M82 absolute in the start gcode. I will check. If that is the case I should remove it from the start code.

Addendum: would you ever just use absolute all the way through. What are the advantages. Seams like there is a thread I've read in that regard.

Thanks.

This brings up a question. Pending how I print I should only be using one start, stop, pause and resume code/macro. MC slicer has this for the print gcode. If I am using the Duet we interface which also has all these macros, I should not slice with these same code. Seams intuitive but good to make sure!

Thanks

Make sure you get that Peek fan running as soon as possible, it is that important. The Peek Fan should run whenever power is going to the hotend.

3D-Print wrote:

IMBoring25 wrote:Are you using absolute extruder coordinates otherwise?

Hummmm. Will have to check. Maybe that is it??

So I am using relative settings in all my extruder settings. Here is what I have in my config.g
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

I sliced the file with MC slicer which did have all the "standard g-codes."

Here are all my .g files. I anyone sees any issue as to why the "old tool" unloads the filament on tool change, let me know. I will post this on RepRap as well.

Thanks,

Dan

...................................................

Addendum 5/15/2016: Here is a link to my newest config.g files and other set up files!!!

(http://forum.seemecnc.com/viewtopic.php ... 654#p90654)

OK...I was thinking of a basic rolling tool change. If you're using a g-code initiated pause as part of the tool change code you're inserting, you need to have an M400 wait for moves to finish before it. I was getting weird behavior on resume until I did that.

The MC macros shouldn't matter unless you're calling them.

IMBoring25 wrote:OK...I was thinking of a basic rolling tool change. If you're using a g-code initiated pause as part of the tool change code you're inserting, you need to have an M400 wait for moves to finish before it. I was getting weird behavior on resume until I did that.

The MC macros shouldn't matter unless you're calling them.

Thank makes since. Where do I put this M400 g-code into the pause g-code?

Or resume g-code?

Thanks.

To the extent that I've messed with this I just edited the slicer's gcode file to insert M400 and then M226 after the G1 Z* move corresponding to the layer where I wanted the pause. I haven't edited the pause.g the board came with but I'd expect the M400 should go at the end of pause.g if you're wanting to macro a more-complex routine.

Getting closer!!!

Printing the BandAid in multi-color. Inserted the M567 P0 E1.00:0.00:0.00 gcode into the print file gcode at each change in geometric shape. This switches the extruder and extrudes each color at 100% (I.e. 1.0).

The cool part with this mixing g-code is that you can set any ratio of the extruders.

For example is that you can:

• Run extruders 1 and 2 using Tool 0 at 50% each: M567 P0 E0.50:0.50:0.00
• Run all three extruders using Tool 0 at 33%: M567 P0 E0.33:0.33:0.33

Options are endless!!!

As well, with the Duet web interface you can issue this M567 code and send it to the printer at any point in the print. The one issue I need to resolve is that there is a 30 seconds delay and pause in the print when I send this code. I think this is due to the print buffer being used/full.

I have a question out to the RepRap forum on if a M400 g-code as suggested by "IMBoring25" will keep the buffer clear and make the change without pause. I am going to try that next!!!

The final print!!

Turned out great!

Have you tried converting 0..255 RGB values into percentages and see how close you get to the target color? I won't be as good as CYMK, but it might be ballpark-ish.

g.

M400 clears the buffer at a moment in time. It's used when you absolutely don't want one command to start executing until the previous one has completed but has no impact once the buffer has cleared.