Development #21
Open
Development #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Completely re-written autocalibration code (still needs some optimization). Lots of other updates ;-)
Only adjust radius if centre point is outside defined precision Reduce default autocal travelrate to 200mm/s
| @@ -372,7 +372,7 @@ | |||
| #define Z_STEP_PIN 46 | |||
| #define Z_DIR_PIN 48 | |||
| #define Z_ENABLE_PIN 62 | |||
| #define Z_MIN_PIN 18 // autolevel probe for deltabot | |||
| #define Z_MIN_PIN 14 // autolevel probe for deltabot | |||
There was a problem hiding this comment.
Z_MIN_PIN on RAMPS 1.4 is PIN 18
Y_MIN_PIN 14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a special request, is it possible to add the g-code instead of this:
define Z_PROBE_DEPLOY_START_LOCATION {0, 0, 50, 0} // X, Y, Z, E start location for z-probe deployment sequence
define Z_PROBE_DEPLOY_END_LOCATION {0, 0, 50, 0} // X, Y, Z, E end location for z-probe deployment sequence
define Z_PROBE_RETRACT_START_LOCATION {0, 0, 50, 0} // X, Y, Z, E start location for z-probe retract sequence
define Z_PROBE_RETRACT_END_LOCATION {0, 0, 50, 0} // X, Y, Z, E end location for z-probe retract sequence
repetier firmware supports it and it is a nice alternative, it separates the lines of g-code by \n exemple :
"G01 X75 Y-82 Z15 F5000\nG01 X85 Y-82 Z5 F5000\nG01 X0 Y0 F5000"