You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No response
Are you looking for hardware support?
No response
Describe the feature you want
Hello, I'm grappling with a complex setup involving a 3-axis 3D printer with an additional 5-axis component. I'm experimenting with post-processing tasks such as part removal and other functions using these extra axes. My question is, is there a method to synchronize the homing process for these two additional axes? I'm seeking a solution akin to QUICK_HOME for the X and Y axes.
Previously, I attempted to integrate new functions into G28.cpp, motion.cpp and motion.h, following a similar approach to QUICK_HOME. However, it appears that Marlin controls the extra axes differently, resulting in unsuccessful outcomes.
Additional context
No response
The text was updated successfully, but these errors were encountered:
@DerAndere1 Thank you for your answer, I'm looking forward to your pull request.
BTW, your fork has great features, and it seems great for my next prototype.
Is your feature request related to a problem? Please describe.
No response
Are you looking for hardware support?
No response
Describe the feature you want
Hello, I'm grappling with a complex setup involving a 3-axis 3D printer with an additional 5-axis component. I'm experimenting with post-processing tasks such as part removal and other functions using these extra axes. My question is, is there a method to synchronize the homing process for these two additional axes? I'm seeking a solution akin to QUICK_HOME for the X and Y axes.
Previously, I attempted to integrate new functions into G28.cpp, motion.cpp and motion.h, following a similar approach to QUICK_HOME. However, it appears that Marlin controls the extra axes differently, resulting in unsuccessful outcomes.
Additional context
No response
The text was updated successfully, but these errors were encountered: