-
-
Notifications
You must be signed in to change notification settings - Fork 964
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
Add Z coordinate when come back to purge tower #6773
Comments
you can specify the name and type of printer, |
Hi. Some times ORCASLICER does not put the Z coordinate when come back to the purge tower. I attach both gcode files. |
Hi. My layer change gcode its just exact like yours in prusaslicer and orcaslicer. I have the factory gcode configuration for all, layer, tool change, etc. Only make changes on start and end gcode. I try to make changes with the semicolon and diferent gcodes but does not works. Just OrcaSlicer not emit the z position when come back to purge tower. That makes he new tool goes to the wipe tower at layer heigh from parking position and hit the tower some times. |
Thanks for the Info: So the Solution is to make the same cange like: Make sure that after wipe tower toolchange the G1 Z is always emitted. Even if the G1 Z would be redundant, it is still emitted. I will try to get in contackt witch : lukasmatena |
Thanks a lot. |
Following, thanks @CorvoConV for reporting. I confirm the behavior. I'm Using 2.2.0 Beta if that matters. Basically this, flaw I would say, prevents me using OrcaSlicer with tool changer at the moment, so quick fix is most welcome. Additional observation:
to Machine G-code: "Change filament G-code" almost works. But the z height after tool changes is not restored for the last layer. EDIT: BTW "Change Filament G-code" should be named "Tool Change G-code". Or is the "Change Filament G-code" intended to match "Color Change G-code" as in PS? Anyway, Tool- and color/filament changes are different things, both should be there as in PS. But I like what I have seen so far after a few days of testing, thanks for the developers. Looking forward to start using OrcaSlicer more because PS has lacked tool preheating functionality for years for everyone. |
@lukasmatena Hi, I have found out that you have made Last time the Change in Prusa Slicer so it Word be Nice if you Could then Help me Check the Code Change and Review, and some Information about "How to" on the Orcas Slicer Projekt. |
This feature was already in 2.2 beta. But it causes this issue - last layer nozzle crash when a single filament change happens on the previous layer. |
I don't know if this helps you, but here's how I handle Z moves during toolchange. [gcode_macro Lift_and_Go_to_Purge] params:Z_LIFT distance to lift the z axis before moving to the purge locationgcode:
[gcode_macro Move_Back_to_Print] params:X x position to move toY y position to move toZ z position to move togcode:
{if layer_num >=0} |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
Is there an existing issue for this feature request?
Is your feature request related to a problem?
Good afternoon.
Reviewing the tool change code, after sending, for example, T1, the gcode back to the purge tower does not take into account the Z coordinate. This is a problem because in the tool change macros the head must be maintained at the height of the printing layer and when the head goes to the purge tower it can hit it. I've had this problem with older versions of PrusaSlicer but simply adding the Z coordinate in the gcode back to the purge tower fixed it.
This is an example of what I mean:
ORCASLICER
G1 x200 y150 purge coordinate
G4s0
PRUSASLICER
G1 x200 y150 purge coordinate
G1 z7.25 purge z coordinate
G4s0
Can you improve this please?
Thanks a lot.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
Just add the layer Z coordinate when come back to purge tower
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: