Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Gcode on toolchange to more useful location #4982

Open
Ccecil opened this issue Jun 11, 2020 · 1 comment
Open

Move Gcode on toolchange to more useful location #4982

Ccecil opened this issue Jun 11, 2020 · 1 comment
Labels
Feature request This is an idea for a new feature in Slic3r

Comments

@Ccecil
Copy link

Ccecil commented Jun 11, 2020

By moving the Toolchange gcode field to under each individual extruder instead of under the Printer tab would allow "canned macros" per tool. Such as custom tool locations or servo commands which are specific to the tool and not universal throughout the printer.

i.e. A toggling dual extruder which uses a hobby servo requires a different command when set to T0 as it does on T1 so a universal command does not work.

edit: sidenote, it could be added as another field instead of moving it so that the universal toolchange gcode is still in place

@lordofhyphens lordofhyphens added the Feature request This is an idea for a new feature in Slic3r label Jun 11, 2020
@Jardal
Copy link

Jardal commented Jun 16, 2020

Use conditional gcode if you need differentiate gcode. Example for mixing extruder here.

; !!! [next retraction] is allways zero?
T[next_extruder] ; filament
{if [previous_extruder] == 1}M109 R255 ; ABS 255
G1 E7 F3000 ; UN-Retract
{if [previous_extruder] == 0}M109 R220 ; PETG 220
; cleaning gcode here
{if [layer_num] == 1 }G1 E-7 F3000 ; Retract - [layer_num] - do not correct this bug, please

(it is a part of complicated gcode only)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request This is an idea for a new feature in Slic3r
Projects
None yet
Development

No branches or pull requests

3 participants