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

Fix for InfimechTx Start Gcode #5527

Merged
merged 1 commit into from
Jun 2, 2024
Merged

Conversation

jimmyjon711
Copy link
Contributor

Description

  • Current start gcode for InfimechTx printer has the wrong index for Y when creating the Y purge line. Under a rare case if the Y purge line is too small it causes the printer to fault out ( this happened to me). Also under some circumstances the purge line can be backwards.

  • Updated start gcode to use right index for the first_layer_print_min Y value

Was:
G1 X{first_layer_print_min[0]-1.5} Y{min(first_layer_print_min[0] + 60,print_bed_max[0])} F6000

Updated with fix :
G1 X{first_layer_print_min[0]-1.5} Y{min(first_layer_print_min[1] + 60,print_bed_max[0])} F6000

Screenshots/Recordings/Graphs

Without fix purge line backwards 200mm x 30mm primitive
200x30_purgeline_backwards

Y Purge line small and causes printer to error out with MCU error saying MCU is behind:
small_y_purgeline

Tests

Same print after fix, purge line is now correctly 60x60
image

- Current start gcode for InfimechTx has the wrong index for Y when creating the purge line
- Updated start gcode to use right index for the Y value
@jimmyjon711 jimmyjon711 changed the title Fixes InfimechTx Start Gcode Fixes to InfimechTx Start Gcode May 31, 2024
@jimmyjon711 jimmyjon711 changed the title Fixes to InfimechTx Start Gcode Fix for InfimechTx Start Gcode May 31, 2024
Copy link
Owner

@SoftFever SoftFever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you

@SoftFever SoftFever merged commit 5f92fae into SoftFever:main Jun 2, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants