From d0b426d5b0bb31de92f3fe9fb1d6159d5da30fec Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Thu, 6 Apr 2023 06:44:26 -0400 Subject: [PATCH 01/12] Updated readme. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index f7165b9..096f3b9 100644 --- a/README.md +++ b/README.md @@ -103,6 +103,8 @@ You can choose *either* of the 2 following methods. 💡 I recommend no filament be loaded for any of these steps. +💡 Find explanations for gcode commands at [https://marlinfw.org/](https://marlinfw.org/) and [klipper.org](https://www.klipper3d.org/G-Codes.html). + 1. `G28` 1. Check to see if `X` and `Y` max positions (`G90`, `G1 X223 F3000`, `G1 Y223 F3000`) can be reached, and adjust `position_max`, if necessary. You can probably go all the way up to `225` for `X` and `Y` both, however, I would not recommend it. 2. Do a `G34`; mechanical gantry calibration. After the controlled collision against the beam at the top, there will be a 10 second pause for you to verify that both sides of the gantry are pressed up agaisnt the `stoppers` at the top. You will hear a succession of beeps. From 953daefa329d76e568dd12bbb733b4089814c50c Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Fri, 7 Apr 2023 09:52:06 -0400 Subject: [PATCH 02/12] Adjusted PRINT_START sequence to save time, and to prevent oozing. Increased microsteps to 128, and added square_corner_velocity. --- cfgs/misc-macros.cfg | 18 +++++++++++------- printer.cfg | 9 +++++---- 2 files changed, 16 insertions(+), 11 deletions(-) diff --git a/cfgs/misc-macros.cfg b/cfgs/misc-macros.cfg index e9a3d16..64ecf79 100644 --- a/cfgs/misc-macros.cfg +++ b/cfgs/misc-macros.cfg @@ -121,19 +121,23 @@ gcode: {% set hotendtemp = params.HOTEND|int %} {% set chambertemp = params.CHAMBER|default(0)|int %} + # Set safe speeds + {% set maxVelocity = printer.configfile.settings.printer.max_velocity|default(200)|int %} + {% set maxVelocityAdjusted = (0.95 * maxVelocity * 60)|int %} + ADJUST_FILAMENT_SENSOR_STATUS ENABLE=1 - G28 X Y - # + G90 M140 S{bedtemp} ; set & don't wait for bed temp - M104 S{hotendtemp} ; set & don't wait for hotend temp + G28 X Y M190 S{bedtemp} ; set & wait for bed temp - # TEMPERATURE_WAIT SENSOR="temperature_sensor chamber" MINIMUM={chambertemp} ; wait for chamber temp - # - M109 S{hotendtemp} ; set & wait for hotend temp - # + M104 S{hotendtemp} ; set & don't wait for hotend temp G28 Z ; final z homing + + G1 X0 Y0 F{maxVelocityAdjusted} + M109 S{hotendtemp} ; set & wait for hotend temp + BED_MESH_PROFILE LOAD=default G1 Z20 F3000 ; move nozzle away from bed diff --git a/printer.cfg b/printer.cfg index c29a092..1d08719 100644 --- a/printer.cfg +++ b/printer.cfg @@ -23,6 +23,7 @@ max_velocity: 200 max_accel: 3000 max_z_velocity: 15 max_z_accel: 45 +square_corner_velocity: 8.0 ##################################################################### # X/Y/Z Stepper Settings @@ -32,7 +33,7 @@ max_z_accel: 45 step_pin: PC2 dir_pin: !PB9 enable_pin: !PC3 -microsteps: 64 +microsteps: 128 rotation_distance: 40 endstop_pin: tmc2209_stepper_x:virtual_endstop position_endstop: 0 @@ -54,7 +55,7 @@ diag_pin: PA5 step_pin: PB8 dir_pin: PB7 enable_pin: !PC3 -microsteps: 64 +microsteps: 128 rotation_distance: 40 endstop_pin: tmc2209_stepper_y:virtual_endstop position_endstop: 0 @@ -76,7 +77,7 @@ diag_pin: PA6 step_pin: PB6 dir_pin: !PB5 enable_pin: !PC3 -microsteps: 64 +microsteps: 128 rotation_distance: 4 endstop_pin: probe:z_virtual_endstop position_min: -4 @@ -100,7 +101,7 @@ diag_pin: PA7 step_pin: PB4 dir_pin: !PB3 enable_pin: !PC3 -microsteps: 64 +microsteps: 128 rotation_distance: 4.65 # NOTE Calibrate e-steps and adjust https://www.klipper3d.org/Rotation_Distance.html nozzle_diameter: 0.400 filament_diameter: 1.750 From 1f3707123a74c9c727a72c0d6d7c659403d8dbf5 Mon Sep 17 00:00:00 2001 From: Bassam Husain <61985779+bassamanator@users.noreply.github.com> Date: Fri, 7 Apr 2023 13:47:17 -0400 Subject: [PATCH 03/12] Update issue templates --- .github/ISSUE_TEMPLATE/bug_report.md | 34 +++++++++++++++++++++++ .github/ISSUE_TEMPLATE/feature_request.md | 20 +++++++++++++ 2 files changed, 54 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..bb8b451 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,34 @@ +--- +name: Bug report +about: Create a report to help us improve +title: "[BUG]" +labels: '' +assignees: '' + +--- + +**Describe the bug** +A clear and concise description of what the bug is. + +**To Reproduce** +Steps to reproduce the behavior: +1. Go to '...' +2. Click on '....' +3. Scroll down to '....' +4. See error + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Screenshots** +If applicable, add screenshots to help explain your problem. + +**What kind of device are you using to host Klipper?** + - OS: [e.g. old laptop, PC, Raspberry Pi] + - Version: [] + +**How did you install Klipper?** + - Manual install, KIAUH, MainsailOS, FluiddPi, etc. + +**Additional context** +Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..bbcbbe7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,20 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: '' +labels: '' +assignees: '' + +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. + +**Additional context** +Add any other context or screenshots about the feature request here. From 8c6ebbca2cd96f414554ae05d3289275f8e8c5f2 Mon Sep 17 00:00:00 2001 From: Bassam Husain <61985779+bassamanator@users.noreply.github.com> Date: Fri, 7 Apr 2023 13:56:28 -0400 Subject: [PATCH 04/12] Create CONTRIBUTING.md --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..30a0878 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,8 @@ +# Contribution Guidelines + +When contributing, please ... +- provide a clear and concise explanation of your pull request. +- try to make small changes, ie, make many small pull requests as opposed to a single large pull request. This allows me to check your work more quickly, thus merge more quickly. +- try to follow the patterns I've already established. + +Thank you. From b3040f424486d30d94bd2b647922231404cbdb4d Mon Sep 17 00:00:00 2001 From: Bassam Husain <61985779+bassamanator@users.noreply.github.com> Date: Fri, 7 Apr 2023 14:04:00 -0400 Subject: [PATCH 05/12] Create CODE_OF_CONDUCT.md --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..4769dd0 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +bassamanator.2cj4t@simplelogin.com. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From 9e68610908f2a4e4c2f233b668527f870d43cebd Mon Sep 17 00:00:00 2001 From: Bassam Husain <61985779+bassamanator@users.noreply.github.com> Date: Fri, 7 Apr 2023 18:07:24 -0400 Subject: [PATCH 06/12] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 096f3b9..1ce7fb5 100644 --- a/README.md +++ b/README.md @@ -231,7 +231,8 @@ A simple runout sensor can only detect a change in state. So, if you start a pri - [Everything Sovol SV06](https://github.com/bassamanator/everything-sovol-sv06) - [RP2040-Zero ADXL345 Connection Klipper](https://github.com/bassamanator/rp2040-zero-adxl345-klipper) -- ⭐⭐⭐ [Ellis' Print Tuning Guide](https://ellis3dp.com/Print-Tuning-Guide) +- ⭐⭐⭐⭐⭐ [Ellis' Print Tuning Guide](https://ellis3dp.com/Print-Tuning-Guide) +- [Simplify3D Print Quality Troubleshooting Guide](https://www.simplify3d.com/resources/print-quality-troubleshooting/) ## Links From 6dc119cf99e9f4b2bdf6d29cdd96192f0b895e1b Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Fri, 7 Apr 2023 19:44:30 -0400 Subject: [PATCH 07/12] Added pause/runout/m600 to faq. Reduced speed in print_start. --- README.md | 29 +++++++++++++++++++++++++++++ cfgs/misc-macros.cfg | 2 +- 2 files changed, 30 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1ce7fb5..9683c98 100644 --- a/README.md +++ b/README.md @@ -35,6 +35,7 @@ Although I've made switching over to Klipper as easy as is possible, it can stil ## Before You Begin - Read this documentation *fully!* +- Make sure your printer is in good physical condition, because print and travel speeds will be *a lot faster* than they were before. Consider yourself warned. - Follow the steps in order. - If an error was reported at a step, do no proceed to the next step. - It is assumed that you are connected to your host Raspberry Pi (or other host device) via SSH, and that your printer motherboard is connected to the host via a data USB cable. Note that most of the micro USB cables that you find at home are *unlikely* to be data cables, and it's not possible to tell just by looking. @@ -227,6 +228,34 @@ Make the following changes according to your needs. A simple runout sensor can only detect a change in state. So, if you start a print without filament loaded, the printer will not know that there is no filament loaded. You should test your sensor by having filament loaded, starting a print, then cutting the filament. The expected behaviour is that the print will pause, and as long as you have beeping enabled, you will hear 3 annoying beeps. +##### What happens when I put in `M600`/colour change at a certain layer? + +1. The printer will beep 3 times (not annoyingly). +2. Printing will stop. +3. The printhead will park itself front center. +4. The hotend will turn off, but the bed will remain hot. + +##### What happens when I pause a print? + +Same behaviour as `M600`/colour change *except* there won't be any beeping. + +##### What happens when filament runouts out? + +*If* you have a working filament sensor, the same behaviour as `M600`/colour change will occur*except* the beeps will be fairly annoying. + +##### How do I resume a print after a colour change or filament runout? + +*Do no disable the stepper motors during this process!* + +The printhead is now parked front center waiting for you to insert filament. You will: + +1. Heat up the hotend to the desired temperature. + - Use your Klipper dashboard. +2. Purge (push) some filament through the nozzle. + - Use your Klipper dashboard, and extrude maybe 50mm (for a colour change you probably want to extrude more). + - OR, you can push some filament by hand *making sure to first disengage the extruder's spring loaded arm*. +3. Hit resume in your Klipper dashboard. + ## Useful Resources - [Everything Sovol SV06](https://github.com/bassamanator/everything-sovol-sv06) diff --git a/cfgs/misc-macros.cfg b/cfgs/misc-macros.cfg index 64ecf79..47225be 100644 --- a/cfgs/misc-macros.cfg +++ b/cfgs/misc-macros.cfg @@ -123,7 +123,7 @@ gcode: # Set safe speeds {% set maxVelocity = printer.configfile.settings.printer.max_velocity|default(200)|int %} - {% set maxVelocityAdjusted = (0.95 * maxVelocity * 60)|int %} + {% set maxVelocityAdjusted = (0.90 * maxVelocity * 60)|int %} ADJUST_FILAMENT_SENSOR_STATUS ENABLE=1 From 238091d860f5e2397711adbdac7cf61f742a1d5e Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Thu, 13 Apr 2023 17:28:55 -0400 Subject: [PATCH 08/12] Minor speedup in print_start. --- cfgs/misc-macros.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/cfgs/misc-macros.cfg b/cfgs/misc-macros.cfg index 47225be..45ba93b 100644 --- a/cfgs/misc-macros.cfg +++ b/cfgs/misc-macros.cfg @@ -129,6 +129,7 @@ gcode: G90 M140 S{bedtemp} ; set & don't wait for bed temp + M104 S150 ; set & don't wait for hotend temp G28 X Y M190 S{bedtemp} ; set & wait for bed temp From 5abaf73b9c826617e080830ad8a28457c2f1bb66 Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Thu, 13 Apr 2023 17:32:44 -0400 Subject: [PATCH 09/12] Comment cleanup in print_end. --- cfgs/misc-macros.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cfgs/misc-macros.cfg b/cfgs/misc-macros.cfg index 45ba93b..d33af02 100644 --- a/cfgs/misc-macros.cfg +++ b/cfgs/misc-macros.cfg @@ -145,7 +145,7 @@ gcode: [gcode_macro PRINT_END] gcode: ADJUST_FILAMENT_SENSOR_STATUS ENABLE=0 - CONDITIONAL_BEEP I=2 DUR=30 FREQ=8500 ; NOTE Comment out this line to stop the beeps at the end of a print + CONDITIONAL_BEEP I=2 DUR=30 FREQ=8500 {% set PRE_PURGE_PRIME_LENGTH=printer["gcode_macro _globals"].pre_purge_prime_length|default(1.40)|float %} M400 ; wait for buffer to clear From a30d367d1dc47254997b014deb9251703355ca5f Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Mon, 17 Apr 2023 00:21:03 -0400 Subject: [PATCH 10/12] Commented out raspberry pi temperature section. --- cfgs/misc-macros.cfg | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/cfgs/misc-macros.cfg b/cfgs/misc-macros.cfg index d33af02..7356d51 100644 --- a/cfgs/misc-macros.cfg +++ b/cfgs/misc-macros.cfg @@ -1,8 +1,9 @@ [force_move] enable_force_move: True -[temperature_sensor raspberry_pi] -sensor_type: temperature_host +# NOTE If you're using a Raspberry Pi, you can uncomment the next to lines, optionally. +# [temperature_sensor raspberry_pi] +# sensor_type: temperature_host [virtual_sdcard] path: /home/pi/printer_data/gcodes From 807c91507a96dc8310d4a1c37eabdae3f73bd64f Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Mon, 17 Apr 2023 00:41:03 -0400 Subject: [PATCH 11/12] Pulling in from personal branch. --- cfgs/misc-macros.cfg | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/cfgs/misc-macros.cfg b/cfgs/misc-macros.cfg index 7356d51..6872a33 100644 --- a/cfgs/misc-macros.cfg +++ b/cfgs/misc-macros.cfg @@ -1,7 +1,7 @@ [force_move] enable_force_move: True -# NOTE If you're using a Raspberry Pi, you can uncomment the next to lines, optionally. +# NOTE If you're using a Raspberry Pi, you can uncomment the next 2 lines, optionally. # [temperature_sensor raspberry_pi] # sensor_type: temperature_host @@ -124,24 +124,28 @@ gcode: # Set safe speeds {% set maxVelocity = printer.configfile.settings.printer.max_velocity|default(200)|int %} - {% set maxVelocityAdjusted = (0.90 * maxVelocity * 60)|int %} + {% set maxVelocityAdjusted = (0.90 * maxVelocity * 60)|int %} + {% set bedtempAlmost = (bedtemp - 2)|int %} + {% set hotendtempStepOne = 150|int %} + {% set hotendtempStepTwo = 170|int %} + BED_MESH_PROFILE LOAD=default ; NOTE if not using a mesh, comment out this line ADJUST_FILAMENT_SENSOR_STATUS ENABLE=1 G90 - M140 S{bedtemp} ; set & don't wait for bed temp - M104 S150 ; set & don't wait for hotend temp + M140 S{bedtempAlmost} ; set & don't wait for bed temp + M104 S{hotendtempStepOne} ; set & don't wait for hotend temp G28 X Y + M190 S{bedtempAlmost} ; set & wait for bed temp + M104 S{hotendtempStepTwo} ; set & don't wait for hotend temp M190 S{bedtemp} ; set & wait for bed temp - M104 S{hotendtemp} ; set & don't wait for hotend temp G28 Z ; final z homing - G1 X0 Y0 F{maxVelocityAdjusted} M109 S{hotendtemp} ; set & wait for hotend temp + G1 X0 Y0 F{maxVelocityAdjusted} - BED_MESH_PROFILE LOAD=default - G1 Z20 F3000 ; move nozzle away from bed + G1 Z20 F3000 ; move nozzle away from bed [gcode_macro PRINT_END] gcode: From 8bfed9c57301ce70cfffb550ef576e7cb766e16c Mon Sep 17 00:00:00 2001 From: Bassam Husain Date: Tue, 18 Apr 2023 07:44:09 -0400 Subject: [PATCH 12/12] Spelling fixes. --- .vscode/settings.json | 13 ++++++++++++- README.md | 6 +++--- 2 files changed, 15 insertions(+), 4 deletions(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index 384e9d9..cdb8a73 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -4,5 +4,16 @@ "editor.detectIndentation": false, "git.mergeEditor": false, "spellright.language": ["en-GB-10-1."], - "spellright.documentTypes": ["markdown", "plaintext"] + "spellright.documentTypes": ["markdown", "plaintext"], + "cSpell.words": [ + "ADXL", + "gcode", + "hotend", + "Klipper", + "Klipperized", + "octahedroflake", + "PARKBED", + "runout", + "Sovol" + ] } diff --git a/README.md b/README.md index 9683c98..9c7f2a3 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ I work on this repository all the time and a lot of new features are coming. Wat # Preface -Although I've made switching over to Klipper as easy as is possible, it can still be a challenge for some, especially considering that most of you have likely never used GNU+Linux. Save yourself the fustration, and fully read all documentation found on this page. Also note that Klipper is not a *must*, and is not for everyone. You can stick with Marlin, and have a fine 3D printing experience. +Although I've made switching over to Klipper as easy as is possible, it can still be a challenge for some, especially considering that most of you have likely never used GNU+Linux. Save yourself the frustration, and fully read all documentation found on this page. Also note that Klipper is not a *must*, and is not for everyone. You can stick with Marlin, and have a fine 3D printing experience. # Installation Steps @@ -108,7 +108,7 @@ You can choose *either* of the 2 following methods. 1. `G28` 1. Check to see if `X` and `Y` max positions (`G90`, `G1 X223 F3000`, `G1 Y223 F3000`) can be reached, and adjust `position_max`, if necessary. You can probably go all the way up to `225` for `X` and `Y` both, however, I would not recommend it. -2. Do a `G34`; mechanical gantry calibration. After the controlled collision against the beam at the top, there will be a 10 second pause for you to verify that both sides of the gantry are pressed up agaisnt the `stoppers` at the top. You will hear a succession of beeps. +2. Do a `G34`; mechanical gantry calibration. After the controlled collision against the beam at the top, there will be a 10 second pause for you to verify that both sides of the gantry are pressed up against the `stoppers` at the top. You will hear a succession of beeps. 1. Figure out your `Z` `position_max` by baby stepping your way up to the beam. The range is 250 to 261 from what I've seen, could be even higher for you. Adjust `position_max`, if necessary. I can go all the way to 258, however, I would not print anything higher than 257. 3. Pid tune the bed, but first move the printhead to the center. Ideally, all Pid tuning should occur at the temperatures that you print most at. 1. `G28` @@ -239,7 +239,7 @@ A simple runout sensor can only detect a change in state. So, if you start a pri Same behaviour as `M600`/colour change *except* there won't be any beeping. -##### What happens when filament runouts out? +##### What happens when filament runs out? *If* you have a working filament sensor, the same behaviour as `M600`/colour change will occur*except* the beeps will be fairly annoying.