From 4362c7657bff2bdb6de2bf08d8ea9c3a18b64929 Mon Sep 17 00:00:00 2001 From: Scott Lahteine Date: Thu, 2 Oct 2025 16:22:24 -0500 Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=A8=20Short=20Markdown=20links?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- config/examples/AliExpress/CL-260/README.md | 2 +- config/examples/Anet/ET4+/README.md | 12 ++++++------ config/examples/Anet/ET4-Pro/README.md | 12 ++++++------ config/examples/Anet/ET4/README.md | 12 ++++++------ config/examples/Anet/ET4X/README.md | 12 ++++++------ config/examples/Anet/ET5-Pro/README.md | 12 ++++++------ config/examples/Anet/ET5/README.md | 12 ++++++------ config/examples/Anet/ET5X/README.md | 12 ++++++------ .../i3 Mega/Trigorilla Pro STM32/README.md | 4 ++-- config/examples/BIQU/B1 SE Plus/README.md | 2 +- config/examples/BIQU/B1 SE/README.md | 2 +- config/examples/BIQU/B1/README.md | 2 +- config/examples/BIQU/BX/README.md | 2 +- config/examples/BIQU/Hurakan/README.md | 4 ++-- config/examples/BQ/Hephestos_2/README.md | 6 +++--- config/examples/Creality/Ender-3 V2/README.md | 8 ++++---- .../CrealityV1 (ORIGIN UI)/README.md | 4 ++-- .../CrealityV1 (RELOADED UI)/README.md | 2 +- config/examples/Creality/Ender-6/README.md | 4 ++-- config/examples/Felix/DUAL/README.md | 4 ++-- config/examples/Felix/Single/README.md | 4 ++-- .../examples/FlashForge/CreatorPro/README.md | 2 +- config/examples/FlyingBear/P905H/README.md | 2 +- .../Geeetech/Prusa i3 Pro B/bltouch/README.md | 10 +++++----- .../Geeetech/Prusa i3 Pro B/noprobe/README.md | 10 +++++----- config/examples/Labists/ET4/README.md | 12 ++++++------ config/examples/Malyan/M150/README.md | 2 +- config/examples/Malyan/M200/README.md | 4 ++-- config/examples/Mks/Robin_Lite3/README.md | 2 +- config/examples/Mks/Robin_Pro/README.md | 2 +- config/examples/Mks/Sbase/README.md | 2 +- config/examples/Prusa/MK3/README.md | 12 ++++++------ .../Prusa/MK3S-BigTreeTech-BTT002/README.md | 12 ++++++------ config/examples/Rolohaun/Rook MK1/README.md | 2 +- config/examples/Tronxy/X5SA/README.md | 6 +++--- config/examples/Two Trees/SP-5_V3/README.md | 2 +- .../examples/Velleman/K8200 Upgraded/README.md | 18 +++++++++--------- config/examples/Velleman/K8200/README.md | 14 +++++++------- config/examples/Velleman/K8400/README.md | 8 ++++---- config/examples/WASP/PowerWASP/README.md | 4 ++-- .../Wanhao/Duplicator i3 2.1/README.md | 6 +++--- config/examples/Weedo/Tina2/README.md | 12 ++++++------ .../examples/delta/Anycubic/Predator/README.md | 10 +++++----- config/examples/delta/MKS/SBASE/README.md | 2 +- config/examples/delta/Malyan M300/README.md | 2 +- config/examples/delta/kossel_pro/README.md | 4 ++-- config/examples/delta/kossel_xl/README.md | 2 +- 47 files changed, 149 insertions(+), 149 deletions(-) diff --git a/config/examples/AliExpress/CL-260/README.md b/config/examples/AliExpress/CL-260/README.md index 20b5b1565c..42fba3ee1b 100644 --- a/config/examples/AliExpress/CL-260/README.md +++ b/config/examples/AliExpress/CL-260/README.md @@ -1,6 +1,6 @@ # AliExpress CL-260 -Example configuration for the [AliExpress CL-260](https://www.aliexpress.com/item/32812528331.html) Ultimaker 2 clone. +Example configuration for the [AliExpress CL-260](//www.aliexpress.com/item/32812528331.html) Ultimaker 2 clone. > [!NOTE] > Change `Z_MAX_POS` to 300 for the CL-260MAX. diff --git a/config/examples/Anet/ET4+/README.md b/config/examples/Anet/ET4+/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET4+/README.md +++ b/config/examples/Anet/ET4+/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Anet/ET4-Pro/README.md b/config/examples/Anet/ET4-Pro/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET4-Pro/README.md +++ b/config/examples/Anet/ET4-Pro/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Anet/ET4/README.md b/config/examples/Anet/ET4/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET4/README.md +++ b/config/examples/Anet/ET4/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Anet/ET4X/README.md b/config/examples/Anet/ET4X/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET4X/README.md +++ b/config/examples/Anet/ET4X/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Anet/ET5-Pro/README.md b/config/examples/Anet/ET5-Pro/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET5-Pro/README.md +++ b/config/examples/Anet/ET5-Pro/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Anet/ET5/README.md b/config/examples/Anet/ET5/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET5/README.md +++ b/config/examples/Anet/ET5/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Anet/ET5X/README.md b/config/examples/Anet/ET5X/README.md index 214b66e921..c5ce54ad03 100644 --- a/config/examples/Anet/ET5X/README.md +++ b/config/examples/Anet/ET5X/README.md @@ -1,6 +1,6 @@ # Marlin for Anet ET4/ET5 Series -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -24,11 +24,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -46,7 +46,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/AnyCubic/i3 Mega/Trigorilla Pro STM32/README.md b/config/examples/AnyCubic/i3 Mega/Trigorilla Pro STM32/README.md index dc3ab33e61..c1444bb697 100644 --- a/config/examples/AnyCubic/i3 Mega/Trigorilla Pro STM32/README.md +++ b/config/examples/AnyCubic/i3 Mega/Trigorilla Pro STM32/README.md @@ -28,9 +28,9 @@ The Trigorilla Pro board has many issues and anomalies that have not been acknow - A Ground Loop with the case severely increases Vref noise. Fixes: -- Use [plastic mounting](https://www.printables.com/model/188956-m3-nuts-washer-and-bolts) to isolate the board from the case. +- Use [plastic mounting](//www.printables.com/model/188956-m3-nuts-washer-and-bolts) to isolate the board from the case. - Print over Serial instead of SD Card. - Ground the frame to earth or neutral. ## Credits -This project would not have been possible without the Marlin Discord and their many helpful members. I would like to thank especially The-EG, EvilGremlin, tombrazier, Dust, and Nuck-TH. Additionally [this](https://www.thingiverse.com/thing:5159397/comments) unfinished firmware from Thingiverse user Thr333DDD is what I formerly based these configs on. [This analysis and reverse engineering](https://github.com/napyk/trigorilla-pro) of the Trigorilla Pro board by Github user napyk was also very helpful in figuring out issues. +This project would not have been possible without the Marlin Discord and their many helpful members. I would like to thank especially The-EG, EvilGremlin, tombrazier, Dust, and Nuck-TH. Additionally [this](//www.thingiverse.com/thing:5159397/comments) unfinished firmware from Thingiverse user Thr333DDD is what I formerly based these configs on. [This analysis and reverse engineering](//github.com/napyk/trigorilla-pro) of the Trigorilla Pro board by Github user napyk was also very helpful in figuring out issues. diff --git a/config/examples/BIQU/B1 SE Plus/README.md b/config/examples/BIQU/B1 SE Plus/README.md index 81166c8f75..f96a1709ed 100644 --- a/config/examples/BIQU/B1 SE Plus/README.md +++ b/config/examples/BIQU/B1 SE Plus/README.md @@ -1,3 +1,3 @@ # BIQU B1 SE Plus (SKR 2) Firmware -Flash drive support is enabled, but jumpers to enable support may not have been installed correctly from the factory. [Follow BIQU's instructions, starting with Step 2](https://github.com/bigtreetech/BIQU-B1-SE-PLUS/blob/master/B1-SE%20fimware/B1-SE-U%20Disk%20Usage%20Tutorial-English.pdf) if flash drive support is not working correctly. +Flash drive support is enabled, but jumpers to enable support may not have been installed correctly from the factory. [Follow BIQU's instructions, starting with Step 2](//github.com/bigtreetech/BIQU-B1-SE-PLUS/blob/master/B1-SE%20fimware/B1-SE-U%20Disk%20Usage%20Tutorial-English.pdf) if flash drive support is not working correctly. diff --git a/config/examples/BIQU/B1 SE/README.md b/config/examples/BIQU/B1 SE/README.md index 0806eab908..3c9ca77900 100644 --- a/config/examples/BIQU/B1 SE/README.md +++ b/config/examples/BIQU/B1 SE/README.md @@ -1,3 +1,3 @@ # BIQU B1 SE (SKR 2) Firmware -Flash drive support is enabled, but jumpers to enable support may not have been installed correctly from the factory. [Follow BIQU's instructions, starting with Step 2](https://github.com/bigtreetech/BIQU-B1-SE-PLUS/blob/master/B1-SE%20fimware/B1-SE-U%20Disk%20Usage%20Tutorial-English.pdf) if flash drive support is not working correctly. +Flash drive support is enabled, but jumpers to enable support may not have been installed correctly from the factory. [Follow BIQU's instructions, starting with Step 2](//github.com/bigtreetech/BIQU-B1-SE-PLUS/blob/master/B1-SE%20fimware/B1-SE-U%20Disk%20Usage%20Tutorial-English.pdf) if flash drive support is not working correctly. diff --git a/config/examples/BIQU/B1/README.md b/config/examples/BIQU/B1/README.md index 539a124e4f..077659b8fc 100644 --- a/config/examples/BIQU/B1/README.md +++ b/config/examples/BIQU/B1/README.md @@ -2,7 +2,7 @@ In `Configuration.h` enable the `MOTHERBOARD BOARD_BTT_SKR_V1_4` option at the top to specify the BTT SKR V1.4 motherboard, otherwise the V2.0 board will be applied (slightly farther down). -For the SKR V2.0-based config, flash drive support is enabled by default. Jumpers to enable support may not have been installed correctly from the factory, so [follow BIQU's instructions, starting with Step 2](https://github.com/bigtreetech/BIQU-B1-SE-PLUS/blob/master/B1-SE%20fimware/B1-SE-U%20Disk%20Usage%20Tutorial-English.pdf) if flash drive support is not working correctly. +For the SKR V2.0-based config, flash drive support is enabled by default. Jumpers to enable support may not have been installed correctly from the factory, so [follow BIQU's instructions, starting with Step 2](//github.com/bigtreetech/BIQU-B1-SE-PLUS/blob/master/B1-SE%20fimware/B1-SE-U%20Disk%20Usage%20Tutorial-English.pdf) if flash drive support is not working correctly. ## BLTouch Probe Support diff --git a/config/examples/BIQU/BX/README.md b/config/examples/BIQU/BX/README.md index 009fa00709..22ce32f5ac 100644 --- a/config/examples/BIQU/BX/README.md +++ b/config/examples/BIQU/BX/README.md @@ -4,7 +4,7 @@ In `Configuration.h` enable the `MOTHERBOARD BOARD_BTT_SKR_SE_BX_V3` option at t Enable the `BX_ALL_METAL_HOTEND` option to permit higher printing temperatures for the newer H2 extruder with an all-metal heatbreak. -Enable the `BX_SWAP_ZM_E1M` option to swap Z and E1 motors if they swapped from the factory. This will fix potential issues with [`G34 - Z Steppers Auto-Alignment`](https://marlinfw.org/docs/gcode/G034-zsaa.html) not working correctly. +Enable the `BX_SWAP_ZM_E1M` option to swap Z and E1 motors if they swapped from the factory. This will fix potential issues with [`G34 - Z Steppers Auto-Alignment`](//marlinfw.org/docs/gcode/G034-zsaa.html) not working correctly. ## Homing with a Probe diff --git a/config/examples/BIQU/Hurakan/README.md b/config/examples/BIQU/Hurakan/README.md index c1b1325756..1c8de6d742 100644 --- a/config/examples/BIQU/Hurakan/README.md +++ b/config/examples/BIQU/Hurakan/README.md @@ -24,7 +24,7 @@ The BIQU Hurakan ships with a BigTreeTech Manta M4P motherboard which includes a # Update Hurakan CB1 Image Defaults > [!IMPORTANT] -> Start with the latest `CB1_Debian11_Klipper_kernel*.img.xz` (full) image from [bigtreetech/CB1/releases](https://github.com/bigtreetech/CB1/releases). +> Start with the latest `CB1_Debian11_Klipper_kernel*.img.xz` (full) image from [bigtreetech/CB1/releases](//github.com/bigtreetech/CB1/releases). ## SSH into to the CB1 @@ -36,7 +36,7 @@ Password: `biqu` ## Update Timezone > [!NOTE] -> See [Wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) or run `timedatectl list-timezones` for list of valid time zone names. `America/Los_Angeles` is used in the example below. +> See [Wikipedia - List of tz database time zones](//en.wikipedia.org/wiki/List_of_tz_database_time_zones) or run `timedatectl list-timezones` for list of valid time zone names. `America/Los_Angeles` is used in the example below. ```shell sudo timedatectl set-timezone America/Los_Angeles diff --git a/config/examples/BQ/Hephestos_2/README.md b/config/examples/BQ/Hephestos_2/README.md index b720ede951..574aa2236d 100644 --- a/config/examples/BQ/Hephestos_2/README.md +++ b/config/examples/BQ/Hephestos_2/README.md @@ -1,6 +1,6 @@ -# Example Configuration for BQ [Hephestos 2](http://www.bq.com/uk/hephestos-2) +# Example Configuration for BQ [Hephestos 2](//www.bq.com/uk/hephestos-2) Based on the original configuration file shipped with the heavily modified Marlin fork by BQ. -The forked firmware and configuration files can be found at the [BQ Github repository](https://github.com/bq/Marlin). +The forked firmware and configuration files can be found at the [BQ Github repository](//github.com/bq/Marlin). > [!NOTE] > The look and feel of the LCD menu will change dramatically when using the original Marlin firmware. @@ -27,4 +27,4 @@ The forked firmware and configuration files can be found at the [BQ Github repos ## Support This configuration should work easily with the stock Hephestos 2, nevertheless if you encounter any -issues you may contact me on [Github](https://github.com/jbrazio), [Twitter](https://twitter.com/jbrazio) or by mail. +issues you may contact me on [Github](//github.com/jbrazio), [Twitter](//twitter.com/jbrazio) or by mail. diff --git a/config/examples/Creality/Ender-3 V2/README.md b/config/examples/Creality/Ender-3 V2/README.md index 220d06ff52..ae09fd8c2b 100644 --- a/config/examples/Creality/Ender-3 V2/README.md +++ b/config/examples/Creality/Ender-3 V2/README.md @@ -14,11 +14,11 @@ Use the following pictures to identify your type of display unit: * **DWIN display**, originally shipped with Ender-3 V2 - ![Ender3v2-DWIN](https://user-images.githubusercontent.com/2745567/156829365-a58a3afc-77e3-40b9-9e16-5edfe3073de8.jpg) + ![Ender3v2-DWIN](//user-images.githubusercontent.com/2745567/156829365-a58a3afc-77e3-40b9-9e16-5edfe3073de8.jpg) * **DACAI display**, a DWIN clone - ![Ender3S1-DACAI](https://user-images.githubusercontent.com/2745567/156829472-2c38a4ab-bdde-4c21-b78f-a30692c96500.jpg) + ![Ender3S1-DACAI](//user-images.githubusercontent.com/2745567/156829472-2c38a4ab-bdde-4c21-b78f-a30692c96500.jpg) Emulates the DWIN protocol but without: * Proper brightness control @@ -32,7 +32,7 @@ Use the following pictures to identify your type of display unit: * **SYNWIT / VIEWE display** **`Currently undocumented`**, **`Reduced custom UI compatibility`** - ![Ender3V2S1-SYNWIT-VIEWE](https://user-images.githubusercontent.com/2745567/209407402-25053f01-6a5d-4c76-90c8-da5aec43100c.png) + ![Ender3V2S1-SYNWIT-VIEWE](//user-images.githubusercontent.com/2745567/209407402-25053f01-6a5d-4c76-90c8-da5aec43100c.png) Emulates the DWIN protocol, but without: * Direct pixel blitting @@ -42,7 +42,7 @@ Use the following pictures to identify your type of display unit: * **TJC display** **`Currently undocumented`**, **`Currently incompatible with custom UIs`** - ![Ender3V2S1-TJC](https://user-images.githubusercontent.com/2745567/206931166-24185525-e377-472e-9bed-37a39aab24fb.jpg) + ![Ender3V2S1-TJC](//user-images.githubusercontent.com/2745567/206931166-24185525-e377-472e-9bed-37a39aab24fb.jpg) Appears to emulate the DWIN protocol but without an unknown subset of features that make it currently crash with custom firmware. diff --git a/config/examples/Creality/Ender-5 Plus/CrealityV1 (ORIGIN UI)/README.md b/config/examples/Creality/Ender-5 Plus/CrealityV1 (ORIGIN UI)/README.md index 5a865a9a65..6c311678cc 100644 --- a/config/examples/Creality/Ender-5 Plus/CrealityV1 (ORIGIN UI)/README.md +++ b/config/examples/Creality/Ender-5 Plus/CrealityV1 (ORIGIN UI)/README.md @@ -5,7 +5,7 @@ ## Marlin DGUS UI Instructions -The Ender-5 stock LCD can optionally use a [customized Marlin DGUS interface](https://github.com/coldtobi/Marlin_DGUS_Resources). With the stock LCD firmware Marlin can only be controlled from a host over USB. +The Ender-5 stock LCD can optionally use a [customized Marlin DGUS interface](//github.com/coldtobi/Marlin_DGUS_Resources). With the stock LCD firmware Marlin can only be controlled from a host over USB. - Format an SD card using the FAT32 filesystem with 4K cluster size. - Copy the `DWIN_SET` folder to the SD card. @@ -17,7 +17,7 @@ The Ender-5 stock LCD can optionally use a [customized Marlin DGUS interface](ht ## Restoring Factory Firmware -The original firmware can be restored by downloading the [Ender-5 Plus firmware](https://www.creality.com/download) from Creality. You can follow the same LCD flashing procedure using the Creality-provided `DWIN_SET` folder. +The original firmware can be restored by downloading the [Ender-5 Plus firmware](//www.creality.com/download) from Creality. You can follow the same LCD flashing procedure using the Creality-provided `DWIN_SET` folder. ## Marlin DGUS UI Limitations diff --git a/config/examples/Creality/Ender-5 Plus/CrealityV1 (RELOADED UI)/README.md b/config/examples/Creality/Ender-5 Plus/CrealityV1 (RELOADED UI)/README.md index eb48ffb153..d7276c4d65 100644 --- a/config/examples/Creality/Ender-5 Plus/CrealityV1 (RELOADED UI)/README.md +++ b/config/examples/Creality/Ender-5 Plus/CrealityV1 (RELOADED UI)/README.md @@ -31,4 +31,4 @@ The Ender-5 stock LCD can optionally use a customized Marlin DGUS interface. To ## Restoring Factory Firmware -The original firmware can be restored by downloading the [Ender-5 Plus firmware](https://www.creality.com/download) from Creality. You can follow the same LCD flashing procedure using the Creality-provided `DWIN_SET` folder. +The original firmware can be restored by downloading the [Ender-5 Plus firmware](//www.creality.com/download) from Creality. You can follow the same LCD flashing procedure using the Creality-provided `DWIN_SET` folder. diff --git a/config/examples/Creality/Ender-6/README.md b/config/examples/Creality/Ender-6/README.md index 5ce74cbb47..bb0b0b74a7 100644 --- a/config/examples/Creality/Ender-6/README.md +++ b/config/examples/Creality/Ender-6/README.md @@ -23,7 +23,7 @@ Copy the compiled "`firmware.bin`" file to an SD card, giving it a distinct name ## Marlin DGUS UI Instructions -The Ender-6 stock LCD can optionally use a [customized Marlin DGUS interface](https://github.com/coldtobi/Marlin_DGUS_Resources). With the stock LCD firmware Marlin can only be controlled from a host over USB (see first section). +The Ender-6 stock LCD can optionally use a [customized Marlin DGUS interface](//github.com/coldtobi/Marlin_DGUS_Resources). With the stock LCD firmware Marlin can only be controlled from a host over USB (see first section). - Copy the `DWIN_SET` folder to a microSD card. The microSD card must be smaller than 8 GB and formatted with a 4K cluster size. - Power off the printer and disassemble the front panel to get access to the LCD board. @@ -34,4 +34,4 @@ The Ender-6 stock LCD can optionally use a [customized Marlin DGUS interface](ht ## Restoring Factory Firmware -The Creality firmware can be restored by downloading the [Ender-6 V1.0.1 firmware](https://www.creality.com/download) and following the flashing procedure above with the Creality-provided `DWIN_SET` folder. +The Creality firmware can be restored by downloading the [Ender-6 V1.0.1 firmware](//www.creality.com/download) and following the flashing procedure above with the Creality-provided `DWIN_SET` folder. diff --git a/config/examples/Felix/DUAL/README.md b/config/examples/Felix/DUAL/README.md index 02aa88a3e7..ead600520e 100644 --- a/config/examples/Felix/DUAL/README.md +++ b/config/examples/Felix/DUAL/README.md @@ -6,8 +6,8 @@ Bringing silky smooth prints to Felix. - Install the latest non-beta Arduino software IDE/toolset: http://www.arduino.cc/en/Main/Software - Download the Marlin firmware - - [Latest developement version](https://github.com/MarlinFirmware/Marlin/tree/Development) - - [Stable version](https://github.com/MarlinFirmware/Marlin/tree/Development) + - [Latest developement version](//github.com/MarlinFirmware/Marlin/tree/Development) + - [Stable version](//github.com/MarlinFirmware/Marlin/tree/Development) - In both cases use the "Download Zip" button on the right. ```shell diff --git a/config/examples/Felix/Single/README.md b/config/examples/Felix/Single/README.md index aaeb2bfa7c..395337274f 100644 --- a/config/examples/Felix/Single/README.md +++ b/config/examples/Felix/Single/README.md @@ -6,8 +6,8 @@ Bringing silky smooth prints to Felix. - Install the latest non-beta Arduino software IDE/toolset: http://www.arduino.cc/en/Main/Software - Download the Marlin firmware - - [Latest developement version](https://github.com/MarlinFirmware/Marlin/tree/Development) - - [Stable version](https://github.com/MarlinFirmware/Marlin/tree/Development) + - [Latest developement version](//github.com/MarlinFirmware/Marlin/tree/Development) + - [Stable version](//github.com/MarlinFirmware/Marlin/tree/Development) - In both cases use the "Download Zip" button on the right. ```shell diff --git a/config/examples/FlashForge/CreatorPro/README.md b/config/examples/FlashForge/CreatorPro/README.md index bae63d2bf4..1a708a4557 100644 --- a/config/examples/FlashForge/CreatorPro/README.md +++ b/config/examples/FlashForge/CreatorPro/README.md @@ -4,7 +4,7 @@ > **NOTE ON FLASHING THE FIRMWARE:** > The Mightyboard uses an Arduino Mega bootloader but it doesn't do an automatic reset on DTR. To make the printer reset on DTR you'll need to flash it with a standard (or other) Arduino Mega bootloader. > -> See [this guide](https://github.com/felipeksw/CreatorPro-Marlin-Cura/tree/main/Bootloader) for instructions on how to flash the bootloader. +> See [this guide](//github.com/felipeksw/CreatorPro-Marlin-Cura/tree/main/Bootloader) for instructions on how to flash the bootloader. ## Machine Settings diff --git a/config/examples/FlyingBear/P905H/README.md b/config/examples/FlyingBear/P905H/README.md index dcb9ba1029..05af311bac 100644 --- a/config/examples/FlyingBear/P905H/README.md +++ b/config/examples/FlyingBear/P905H/README.md @@ -7,7 +7,7 @@ This configuration is for a P905H with **a single extruder and inductive Z-senso ## Build Instructions - Get Visual Studio Code and install the "Auto Build Marlin" extension. - - Download the [Marlin source code](https://marlinfw.org/meta/download/). + - Download the [Marlin source code](//marlinfw.org/meta/download/). - Copy the two Configuration files from this folder into the 'Marlin' folder (replacing the existing files). - Open the 'MarlinFirmware' project folder in Visual Studio Code. - Click the "Auto Build Marlin" button and then the Upload button. diff --git a/config/examples/Geeetech/Prusa i3 Pro B/bltouch/README.md b/config/examples/Geeetech/Prusa i3 Pro B/bltouch/README.md index c36feb71ae..3c7a5636d5 100644 --- a/config/examples/Geeetech/Prusa i3 Pro B/bltouch/README.md +++ b/config/examples/Geeetech/Prusa i3 Pro B/bltouch/README.md @@ -1,7 +1,7 @@ -These are example configurations for the low-cost [Acrylic Průša I3 pro B 3D Printer DIY kit](http://www.geeetech.com/acrylic-geeetech-prusa-i3-pro-b-3d-printer-diy-kit-p-917.html) and the [3DTouch auto bed leveling sensor](http://www.geeetech.com/geeetech-3dtouch-auto-bed-leveling-sensor-for-3d-printer-p-1010.html) based on: +These are example configurations for the low-cost [Acrylic Průša I3 pro B 3D Printer DIY kit](//www.geeetech.com/acrylic-geeetech-prusa-i3-pro-b-3d-printer-diy-kit-p-917.html) and the [3DTouch auto bed leveling sensor](//www.geeetech.com/geeetech-3dtouch-auto-bed-leveling-sensor-for-3d-printer-p-1010.html) based on: - `../GT2560/` -- [Marlin 1.1.4 With 3DTouch / BLTouch for i3 Pro B](https://www.geeetech.com/forum/viewtopic.php?t=19846) +- [Marlin 1.1.4 With 3DTouch / BLTouch for i3 Pro B](//www.geeetech.com/forum/viewtopic.php?t=19846) The main characteristics of these configurations are: @@ -27,16 +27,16 @@ The main characteristics of these configurations are: The skew factor must be adjusted for each printer: - First, uncomment `#define XY_SKEW_FACTOR 0.0`, compile and upload the firmware. -- Then, print [YACS (Yet Another Calibration Square)](https://www.thingiverse.com/thing:2563185). Hint, scale it considering a margin for brim (if used). The larger, the better to make error measurements. +- Then, print [YACS (Yet Another Calibration Square)](//www.thingiverse.com/thing:2563185). Hint, scale it considering a margin for brim (if used). The larger, the better to make error measurements. - Measure the printed part according to the comments in the example configuration file, and set `XY_DIAG_AC`, `XY_DIAG_BD` and `Y_SIDE_AD`. - Last, comment `#define XY_SKEW_FACTOR 0.0` again, compile and upload. ## 3DTouch auto leveling sensor - Print a suitable mount to attach the sensor to the printer. The example configuration file is adjusted to http://www.geeetech.com/wiki/images/6/61/3DTouch_auto_leveling_sensor-1.zip -- Unlike suggested in [geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor](https://www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor), the existing end stop switch is expected to be kept connected to Z_MIN. So, the sensor is to be connected to Z_MAX, according to Marlin's default settings. Furthermore, GT2560-A+ provides a connector for the servo next to thermistor connectors (see [GT2560](https://www.geeetech.com/wiki/images/thumb/4/45/GT2560_wiring.jpg/700px-GT2560_wiring.jpg) and [GT2560-A+](http://i.imgur.com/E0t34VU.png)). +- Unlike suggested in [geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor](//www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor), the existing end stop switch is expected to be kept connected to Z_MIN. So, the sensor is to be connected to Z_MAX, according to Marlin's default settings. Furthermore, GT2560-A+ provides a connector for the servo next to thermistor connectors (see [GT2560](//www.geeetech.com/wiki/images/thumb/4/45/GT2560_wiring.jpg/700px-GT2560_wiring.jpg) and [GT2560-A+](//i.imgur.com/E0t34VU.png)). - Be careful to respect the polarity of the sensor when connecting it to the GT2560-A+. Unlike end stops, reversing the connection will prevent the sensor from working properly. -- [Test](http://www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Testing) and [calibrate](https://www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Calibration) the sensor. +- [Test](//www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Testing) and [calibrate](//www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Calibration) the sensor. - If using the GT2560-A+ and with the sensor connected to Z_MAX and an endstop connected to Z_MIN use the following calibration routine instead. ## 3DTouch Calibration with Z_MAX diff --git a/config/examples/Geeetech/Prusa i3 Pro B/noprobe/README.md b/config/examples/Geeetech/Prusa i3 Pro B/noprobe/README.md index c36feb71ae..3c7a5636d5 100644 --- a/config/examples/Geeetech/Prusa i3 Pro B/noprobe/README.md +++ b/config/examples/Geeetech/Prusa i3 Pro B/noprobe/README.md @@ -1,7 +1,7 @@ -These are example configurations for the low-cost [Acrylic Průša I3 pro B 3D Printer DIY kit](http://www.geeetech.com/acrylic-geeetech-prusa-i3-pro-b-3d-printer-diy-kit-p-917.html) and the [3DTouch auto bed leveling sensor](http://www.geeetech.com/geeetech-3dtouch-auto-bed-leveling-sensor-for-3d-printer-p-1010.html) based on: +These are example configurations for the low-cost [Acrylic Průša I3 pro B 3D Printer DIY kit](//www.geeetech.com/acrylic-geeetech-prusa-i3-pro-b-3d-printer-diy-kit-p-917.html) and the [3DTouch auto bed leveling sensor](//www.geeetech.com/geeetech-3dtouch-auto-bed-leveling-sensor-for-3d-printer-p-1010.html) based on: - `../GT2560/` -- [Marlin 1.1.4 With 3DTouch / BLTouch for i3 Pro B](https://www.geeetech.com/forum/viewtopic.php?t=19846) +- [Marlin 1.1.4 With 3DTouch / BLTouch for i3 Pro B](//www.geeetech.com/forum/viewtopic.php?t=19846) The main characteristics of these configurations are: @@ -27,16 +27,16 @@ The main characteristics of these configurations are: The skew factor must be adjusted for each printer: - First, uncomment `#define XY_SKEW_FACTOR 0.0`, compile and upload the firmware. -- Then, print [YACS (Yet Another Calibration Square)](https://www.thingiverse.com/thing:2563185). Hint, scale it considering a margin for brim (if used). The larger, the better to make error measurements. +- Then, print [YACS (Yet Another Calibration Square)](//www.thingiverse.com/thing:2563185). Hint, scale it considering a margin for brim (if used). The larger, the better to make error measurements. - Measure the printed part according to the comments in the example configuration file, and set `XY_DIAG_AC`, `XY_DIAG_BD` and `Y_SIDE_AD`. - Last, comment `#define XY_SKEW_FACTOR 0.0` again, compile and upload. ## 3DTouch auto leveling sensor - Print a suitable mount to attach the sensor to the printer. The example configuration file is adjusted to http://www.geeetech.com/wiki/images/6/61/3DTouch_auto_leveling_sensor-1.zip -- Unlike suggested in [geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor](https://www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor), the existing end stop switch is expected to be kept connected to Z_MIN. So, the sensor is to be connected to Z_MAX, according to Marlin's default settings. Furthermore, GT2560-A+ provides a connector for the servo next to thermistor connectors (see [GT2560](https://www.geeetech.com/wiki/images/thumb/4/45/GT2560_wiring.jpg/700px-GT2560_wiring.jpg) and [GT2560-A+](http://i.imgur.com/E0t34VU.png)). +- Unlike suggested in [geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor](//www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor), the existing end stop switch is expected to be kept connected to Z_MIN. So, the sensor is to be connected to Z_MAX, according to Marlin's default settings. Furthermore, GT2560-A+ provides a connector for the servo next to thermistor connectors (see [GT2560](//www.geeetech.com/wiki/images/thumb/4/45/GT2560_wiring.jpg/700px-GT2560_wiring.jpg) and [GT2560-A+](//i.imgur.com/E0t34VU.png)). - Be careful to respect the polarity of the sensor when connecting it to the GT2560-A+. Unlike end stops, reversing the connection will prevent the sensor from working properly. -- [Test](http://www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Testing) and [calibrate](https://www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Calibration) the sensor. +- [Test](//www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Testing) and [calibrate](//www.geeetech.com/wiki/index.php/3DTouch_Auto_Leveling_Sensor#Calibration) the sensor. - If using the GT2560-A+ and with the sensor connected to Z_MAX and an endstop connected to Z_MIN use the following calibration routine instead. ## 3DTouch Calibration with Z_MAX diff --git a/config/examples/Labists/ET4/README.md b/config/examples/Labists/ET4/README.md index 99b0efa1dc..ed0bed537c 100644 --- a/config/examples/Labists/ET4/README.md +++ b/config/examples/Labists/ET4/README.md @@ -3,7 +3,7 @@ > [!NOTE] > The Labists ET4 is OEM'd by Anet, so the update process is very similar. -A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. +A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is required to flash the the [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases) due to incompatibility with the stock bootloader. Once OpenBLT is flashed, Marlin can be updated by SD card just like the original firmware. ## Flashing OpenBLT Bootloader with an ST-Link V2 @@ -27,11 +27,11 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is _`GND` is connected to `GND` (black wire), `SWDIO` to `SWDIO` (yellow wire), and `SWCLK` to `SWCLK` (green wire). Your ST-Link pinout may differ from the one pictured, so double-check pinout._ 2. Plug in the ST-Link to your computer's USB port & power on your printer. -3. Download & install [STM32 ST-Link Utility](https://www.st.com/en/development-tools/stsw-link004.html). +3. Download & install [STM32 ST-Link Utility](//www.st.com/en/development-tools/stsw-link004.html). 4. Launch STM32 ST-Link Utility & click `Target` then `Connect`. 5. Back up the original motherboard firmware starting at address `0x08000000` with a size of `0x100000`: -6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](https://github.com/davidtgbe/openblt/releases). +6. Download & extract [OpenBLT bootloader for Anet ET4/ET5 series printers](//github.com/davidtgbe/openblt/releases). 7. Click on `Target` then `Program...` 8. Set the `Start Address` to `0x08000000`. 9. Under `File Path`, click `Browse` and select `openblt_et4.bin` extracted in Step 6. @@ -49,7 +49,7 @@ A debugging/programming probe (_e.g._, ST-Link, J-Link, or Black Magic Probe) is 2. Power cycle your printer to start the update process. ## Acknowledgements -- [@davidtgbe](https://github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. -- [Telegram Anet ET4 spanish group](https://t.me/anetet4esp), especially [@olidnon](https://github.com/olidnon), who lent his motherboard for testing. -- [@uwe](https://github.com/uwe) and [@mubes](https://github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](https://github.com/Ebiroll) (BMP/ESP32). +- [@davidtgbe](//github.com/davidtgbe) for porting Marlin to the ET4/ET5 series. +- [Telegram Anet ET4 spanish group](//t.me/anetet4esp), especially [@olidnon](//github.com/olidnon), who lent his motherboard for testing. +- [@uwe](//github.com/uwe) and [@mubes](//github.com/mubes) from Black Magic Probe team, and to [@Ebiroll](//github.com/Ebiroll) (BMP/ESP32). - All contributors and testers. diff --git a/config/examples/Malyan/M150/README.md b/config/examples/Malyan/M150/README.md index 3a5026a4bd..d766c0a65c 100644 --- a/config/examples/Malyan/M150/README.md +++ b/config/examples/Malyan/M150/README.md @@ -4,7 +4,7 @@ Config without automatic bed level sensor, or in other words, "as stock" ## To install: -1. Install [Arduino](https://www.arduino.cc/en/Main/Software) +1. Install [Arduino](//www.arduino.cc/en/Main/Software) 1. Install U8glib * `Sketch` -> `Include Library` -> `Manage Libraries...` diff --git a/config/examples/Malyan/M200/README.md b/config/examples/Malyan/M200/README.md index d0ca6f52be..16b360ba0d 100644 --- a/config/examples/Malyan/M200/README.md +++ b/config/examples/Malyan/M200/README.md @@ -17,9 +17,9 @@ guide you through the configuration and compilation. - If you own a M200 V1 or early run (black V2), choose **Malyan M200 V1**. - If you own a M200 V2 later run (white/black) or V3 (Pro), choose **Malyan M200 V2** (The V2 and V3 both share an STM32F070 MCU). Note that the V3 pinout is not complete (autolevel doesn't work as of this writing). 8. From the **Tools** menu, choose **USB Support** > **CDC No Generic Serial**. -9. Download the [latest Marlin source](https://marlinfw.org/meta/download/) and unzip it. +9. Download the [latest Marlin source](//marlinfw.org/meta/download/) and unzip it. 10. Look in the `Marlin` subdirectory for the `Configuration.h` and `Configuration_adv.h` files. Replace these files with the configurations in the `config\examples\Malyan\M200` folder. -11. If you have an early-run V2, the steps-per-mm are roughly half. Consult the [mpminipro.com wiki](https://mpminipro.com/) for the steps that apply to your unit. Modify `Configuration.h`. +11. If you have an early-run V2, the steps-per-mm are roughly half. Consult the [mpminipro.com wiki](//mpminipro.com/) for the steps that apply to your unit. Modify `Configuration.h`. 12. Inverting Axis. There's no pattern to axes will need to be inverted. The only way to know is to test your particular printer. If you *do* know, go ahead and invert the correct axes. 13. Open the `Marlin/Marlin.ino` file in Arduino IDE. 14. From the **Sketch** menu, select **File** > **Export Compiled Binary**. diff --git a/config/examples/Mks/Robin_Lite3/README.md b/config/examples/Mks/Robin_Lite3/README.md index b61ce7bbbb..ec118e36bf 100644 --- a/config/examples/Mks/Robin_Lite3/README.md +++ b/config/examples/Mks/Robin_Lite3/README.md @@ -1,6 +1,6 @@ # MKS Robin Lite3 -The [MKS Robin Lite3](https://www.aliexpress.com/item/4000295949948.html) is a powerful 32-bit 3D printer control board with: +The [MKS Robin Lite3](//www.aliexpress.com/item/4000295949948.html) is a powerful 32-bit 3D printer control board with: - STM32F103RCT6 processor - Supports MKS LCD12864B/MINI12864/LCD2004/12864 and MKS TFT Touch Screens. - Integrated 5 AXIS interface diff --git a/config/examples/Mks/Robin_Pro/README.md b/config/examples/Mks/Robin_Pro/README.md index 92ffa06c18..e41624d9f4 100644 --- a/config/examples/Mks/Robin_Pro/README.md +++ b/config/examples/Mks/Robin_Pro/README.md @@ -1,6 +1,6 @@ # MKS Robin Pro -The [MKS Robin Pro](https://www.aliexpress.com/item/4000444286159.html) is a powerful 32-bit 3D printer control board with: +The [MKS Robin Pro](//www.aliexpress.com/item/4000444286159.html) is a powerful 32-bit 3D printer control board with: - STM32F103ZET6 processor - 6 AXIS interface - BLTOUCH interface diff --git a/config/examples/Mks/Sbase/README.md b/config/examples/Mks/Sbase/README.md index 9a422fa2b3..24f891be0c 100644 --- a/config/examples/Mks/Sbase/README.md +++ b/config/examples/Mks/Sbase/README.md @@ -27,7 +27,7 @@ If pins different than the J8 ones above are used then the `spi_pins.h` file wil An octopus cable something like the Adafruit 1199 will simply the construction of the custom cable. Just plug the Adafruit 1199 into one of the cables that came with the LCD and the individual pins into J8 and EXP2 as needed. -[Adafruit 10-pin IDC Socket Rainbow Breakout Cable 1199](https://www.adafruit.com/product/1199) +[Adafruit 10-pin IDC Socket Rainbow Breakout Cable 1199](//www.adafruit.com/product/1199) ## 27 APR 2018 diff --git a/config/examples/Prusa/MK3/README.md b/config/examples/Prusa/MK3/README.md index a74d4b73c2..07b99d68c6 100644 --- a/config/examples/Prusa/MK3/README.md +++ b/config/examples/Prusa/MK3/README.md @@ -1,7 +1,7 @@ # Einsy Rambo Config for Průša MK3S ## Requirements -- [Průša MK3S, MK3S+, or MK3 with MK3S/MK3S+ upgrade](https://www.prusa3d.com/original-prusa-i3-mk3/) is required for filament runout to work properly. +- [Průša MK3S, MK3S+, or MK3 with MK3S/MK3S+ upgrade](//www.prusa3d.com/original-prusa-i3-mk3/) is required for filament runout to work properly. - Stock Einsy Rambo with integrated TMC2130s ## Configuration Options @@ -15,13 +15,13 @@ Flags specific to this printer/configuration: - `SUPERPINDA` - SuperPinda present? ## Changes to Start G-code -The `W` in Průša's `G28 W ; home all without mesh bed level` default G-code does not exist in Marlin and [`G80 ; mesh bed leveling`](https://marlinfw.org/docs/gcode/G080.html) cancels the current motion mode, so no bed leveling will take place. +The `W` in Průša's `G28 W ; home all without mesh bed level` default G-code does not exist in Marlin and [`G80 ; mesh bed leveling`](//marlinfw.org/docs/gcode/G080.html) cancels the current motion mode, so no bed leveling will take place. Below are some example start G-code scripts from popular slicers to get you started. ### PrusaSlicer - Set your G-code flavor to "Marlin 2" under "Printer Settings" -> "General" -> "Firmware" -> "G-code flavor". -- Use the "Custom G-code" section under "Filament Settings" to add the [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value since it can be saved on a per-filament basis. +- Use the "Custom G-code" section under "Filament Settings" to add the [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value since it can be saved on a per-filament basis. - Paste the start G-code block below in the "Custom G-code" section under "Printer Settings". ```gcode @@ -42,7 +42,7 @@ G92 E0.0 ``` ### Cura -Paste the start G-code block below in the "Start G-code" section. Add your [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: +Paste the start G-code block below in the "Start G-code" section. Add your [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: ```gcode G90 ; use absolute coordinates M83 ; extruder relative mode @@ -62,7 +62,7 @@ G92 E0.0 ``` ### IdeaMaker -Paste the start G-code block below in the filament's "Start G-code" section. Add your [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: +Paste the start G-code block below in the filament's "Start G-code" section. Add your [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: ```gcode G90 ; use absolute coordinates M83 ; extruder relative mode @@ -82,7 +82,7 @@ G92 E0.0 ``` ### Simplify3D -Paste the start G-code block below in the "Starting Script" section. Add your [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: +Paste the start G-code block below in the "Starting Script" section. Add your [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: ```gcode G90 ; use absolute coordinates M83 ; extruder relative mode diff --git a/config/examples/Prusa/MK3S-BigTreeTech-BTT002/README.md b/config/examples/Prusa/MK3S-BigTreeTech-BTT002/README.md index 9e4ca87d73..61ceada45f 100644 --- a/config/examples/Prusa/MK3S-BigTreeTech-BTT002/README.md +++ b/config/examples/Prusa/MK3S-BigTreeTech-BTT002/README.md @@ -1,7 +1,7 @@ # BigTreeTech BTT002/TMC2209 Config for Průša MK3S ## Requirements -- [Průša MK3S, MK3S+, or MK3 with MK3S/MK3S+ upgrade](https://www.prusa3d.com/original-prusa-i3-mk3/) is required for filament runout to work properly. +- [Průša MK3S, MK3S+, or MK3 with MK3S/MK3S+ upgrade](//www.prusa3d.com/original-prusa-i3-mk3/) is required for filament runout to work properly. - BigTreeTech BTT002 motherboard - 4 x BigTreeTech TMC2209s (DIAG pin location differs from Watterott's & similar designs) @@ -23,13 +23,13 @@ Flags specific to this printer/configuration: ## Changes to Start G-code > [!IMPORTANT] -> The `W` in Průša's `G28 W ; home all without mesh bed level` default G-code does not exist in Marlin and [`G80 ; mesh bed leveling`](https://marlinfw.org/docs/gcode/G080.html) cancels the current motion mode, so no bed leveling will take place. +> The `W` in Průša's `G28 W ; home all without mesh bed level` default G-code does not exist in Marlin and [`G80 ; mesh bed leveling`](//marlinfw.org/docs/gcode/G080.html) cancels the current motion mode, so no bed leveling will take place. Below are some example start G-code scripts from popular slicers to get you started. ### PrusaSlicer - Set your G-code flavor to "Marlin 2" under "Printer Settings" -> "General" -> "Firmware" -> "G-code flavor". -- Use the "Custom G-code" section under "Filament Settings" to add the [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value since it can be saved on a per-filament basis. +- Use the "Custom G-code" section under "Filament Settings" to add the [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value since it can be saved on a per-filament basis. - Paste the start G-code block below in the "Custom G-code" section under "Printer Settings". ```gcode @@ -50,7 +50,7 @@ G92 E0.0 ``` ### Cura -Paste the start G-code block below in the "Start G-code" section. Add your [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: +Paste the start G-code block below in the "Start G-code" section. Add your [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: ```gcode G90 ; use absolute coordinates M83 ; extruder relative mode @@ -70,7 +70,7 @@ G92 E0.0 ``` ### IdeaMaker -Paste the start G-code block below in the filament's "Start G-code" section. Add your [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: +Paste the start G-code block below in the filament's "Start G-code" section. Add your [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: ```gcode G90 ; use absolute coordinates M83 ; extruder relative mode @@ -90,7 +90,7 @@ G92 E0.0 ``` ### Simplify3D -Paste the start G-code block below in the "Starting Script" section. Add your [Linear Advance](https://marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: +Paste the start G-code block below in the "Starting Script" section. Add your [Linear Advance](//marlinfw.org/docs/features/lin_advance.html) (`M900 K0.0`) value in the start G-code block below: ```gcode G90 ; use absolute coordinates M83 ; extruder relative mode diff --git a/config/examples/Rolohaun/Rook MK1/README.md b/config/examples/Rolohaun/Rook MK1/README.md index 26a346c805..0fcc247041 100644 --- a/config/examples/Rolohaun/Rook MK1/README.md +++ b/config/examples/Rolohaun/Rook MK1/README.md @@ -1,6 +1,6 @@ # Rolohaun Rook MK1 by LDO Motors -The [Rook MK1 by Rolohaun](https://www.printables.com/model/387431-rook-mk1-3d-printer) is meant to be built out of parts you have laying around, but vendors like LDO Motors have put a kit together to simplify the build process. This config is meant for the following hardware: +The [Rook MK1 by Rolohaun](//www.printables.com/model/387431-rook-mk1-3d-printer) is meant to be built out of parts you have laying around, but vendors like LDO Motors have put a kit together to simplify the build process. This config is meant for the following hardware: ## Motherboard diff --git a/config/examples/Tronxy/X5SA/README.md b/config/examples/Tronxy/X5SA/README.md index cce2db1b0b..40c1dfc41c 100644 --- a/config/examples/Tronxy/X5SA/README.md +++ b/config/examples/Tronxy/X5SA/README.md @@ -25,7 +25,7 @@ M8512 "currentconfig.gcode" ; save settings to file 4. The printer won't do anything. Just wait a few seconds and stop the print. 5. Your current printer settings are stored in the file: `currentconfig.gcode` -You can read more about it in [this guide](https://www.facebook.com/notes/tronxy-turnigy-x5s-x5sa-x3s-3d-printer-drucker-users/tronxy-firmware-configuration-guide-by-keith-varin-addermk264bit-tuning/649799805579765/). +You can read more about it in [this guide](//www.facebook.com/notes/tronxy-turnigy-x5s-x5sa-x3s-3d-printer-drucker-users/tronxy-firmware-configuration-guide-by-keith-varin-addermk264bit-tuning/649799805579765/). Thanks to KEITH VARIN. @@ -178,7 +178,7 @@ You can customize for your own setup. TFT, Baby Steps and a lot of cool stuff ar 2. Open your board case 3. Remove the "boot" jumper (1) as the image. 4. Change the "v source" jumper (2) from 5V to USB. -5. Open [STM Cube Programmer](https://www.st.com/en/development-tools/stm32cubeprog.html) (linux, mac, windows) or [FLASHER-STM32](https://www.st.com/en/development-tools/flasher-stm32.html) (only windows) +5. Open [STM Cube Programmer](//www.st.com/en/development-tools/stm32cubeprog.html) (linux, mac, windows) or [FLASHER-STM32](//www.st.com/en/development-tools/flasher-stm32.html) (only windows) 6. The size must be **512kb -> 0x80000** 7. Save the file. It must have exactly 524288 bytes (512kb) 8. Disconnect @@ -212,7 +212,7 @@ OBSOLETE! JUST USE THE FIRST METHOD. 2. Open the board case 3. Remove the "boot" jumper (1) as the image. 4. Change the V source jumper (2) from 5V to USB. -5. Open [STM Cube Programmer](https://www.st.com/en/development-tools/stm32cubeprog.html) (linux, mac, windows) or [FLASHER-STM32](https://www.st.com/en/development-tools/flasher-stm32.html) (only windows) +5. Open [STM Cube Programmer](//www.st.com/en/development-tools/stm32cubeprog.html) (linux, mac, windows) or [FLASHER-STM32](//www.st.com/en/development-tools/flasher-stm32.html) (only windows) 6. Flash the YOUR-MARLIN-DIR/.pio/build/chitu_f103/firmware.bin at 0x08000000 7. After the Flash is done, put the back the boot jumper (1) and the V source jumper to 5V. 8. Turn on the printer diff --git a/config/examples/Two Trees/SP-5_V3/README.md b/config/examples/Two Trees/SP-5_V3/README.md index 790072c88d..3d478a24b4 100644 --- a/config/examples/Two Trees/SP-5_V3/README.md +++ b/config/examples/Two Trees/SP-5_V3/README.md @@ -6,7 +6,7 @@ Changes from default Two Trees SP-5 V3 supplied configuration: - Using `TFT_COLOR_UI` - The [original Marlin code from Two Trees](https://wetransfer.com/downloads/80c678c69652aae3dc35635262ebd0a320240418061003/27392ff160a713aeea143b9c7ffad79d20240418061018/6ffdaa?trk=TRN_TDL_01&utm_campaign=TRN_TDL_01&utm_medium=email&utm_source=sendgrid) uses a modified version of `TFT_LVGL_UI` with its own graphics and some additional screens. + The [original Marlin code from Two Trees](//wetransfer.com/downloads/80c678c69652aae3dc35635262ebd0a320240418061003/27392ff160a713aeea143b9c7ffad79d20240418061018/6ffdaa?trk=TRN_TDL_01&utm_campaign=TRN_TDL_01&utm_medium=email&utm_source=sendgrid) uses a modified version of `TFT_LVGL_UI` with its own graphics and some additional screens. To fully support Marlin this configuration uses `TFT_COLOR_UI` instead. diff --git a/config/examples/Velleman/K8200 Upgraded/README.md b/config/examples/Velleman/K8200 Upgraded/README.md index ff5747d26b..629eb232a8 100644 --- a/config/examples/Velleman/K8200 Upgraded/README.md +++ b/config/examples/Velleman/K8200 Upgraded/README.md @@ -1,4 +1,4 @@ -# Updated Example Configuration for Velleman [K8200](http://www.k8200.eu/) +# Updated Example Configuration for Velleman [K8200](//www.k8200.eu/) I have taken @CONSULiTAS' excellent configuration file, and added support for the following: @@ -27,7 +27,7 @@ If you have the VM8201 display unit, uncomment the following line //#define K8200_VM8201 ``` -If you have the *3D Printer Full Graphic Smart Controller with 3Drag adapter* (or other screen based on the [RepRap Discount Full Graphic Smart Controller](https://reprap.org/wiki/RepRapDiscount_Full_Graphic_Smart_Controller)), ensure +If you have the *3D Printer Full Graphic Smart Controller with 3Drag adapter* (or other screen based on the [RepRap Discount Full Graphic Smart Controller](//reprap.org/wiki/RepRapDiscount_Full_Graphic_Smart_Controller)), ensure the following is uncommented, otherwise comment it out ```cpp #define FULLGRAPHIC_CONTROLLER_LCD_SD @@ -46,12 +46,12 @@ Only one LCD screen is supported (they plug into the same place), so only one of There is a configuration option for the K8203 Direct Drive Extruder, but it does nothing at present. -In addition to the firmware sources below, see the following for for genuine [3drag Firmware](https://3dprint.elettronicain.it/blog/2012/09/06/software/) +In addition to the firmware sources below, see the following for for genuine [3drag Firmware](//3dprint.elettronicain.it/blog/2012/09/06/software/) # Original Readme -* Configuration files for **Vellemann K8200** (with [VM8201](http://www.vellemanprojects.eu/products/view/?id=416158) - LCD Option for K8200) +* Configuration files for **Vellemann K8200** (with [VM8201](//www.vellemanprojects.eu/products/view/?id=416158) - LCD Option for K8200) * K8200 is a 3Drag clone - configuration should work with 3Drag https://reprap.org/wiki/3drag, too. Please report. * updated manually with parameters from genuine Vellemann Firmware "firmware_k8200_marlinv2" based on the recent development branch @@ -59,14 +59,14 @@ In addition to the firmware sources below, see the following for for genuine [3d * VM8201 uses "DISPLAY_CHARSET_HD44870 JAPANESE" and "ULTIMAKERCONTROLLER" * german (de) translation with umlaut is supported now - thanks to @AnHardt for the great hardware based umlaut support -I [@CONSULitAS](https://github.com/CONSULitAS) tested the changes on my K8200 with 20x4-LCD and Arduino 1.6.12 for Mac (SD library added to IDE manually), 2016-11-18 - everything works well. +I [@CONSULitAS](//github.com/CONSULitAS) tested the changes on my K8200 with 20x4-LCD and Arduino 1.6.12 for Mac (SD library added to IDE manually), 2016-11-18 - everything works well. -**Source for genuine [Vellemann Firmware](http://www.k8200.eu/support/downloads/)** -* V2.1.1 (for z axis upgrade, date branched: 2013-06-05): [firmware_k8200_v2.1.1.zip](http://www.k8200.eu/downloads/files/downloads/firmware_k8200_v2.1.1.zip) +**Source for genuine [Vellemann Firmware](//www.k8200.eu/support/downloads/)** +* V2.1.1 (for z axis upgrade, date branched: 2013-06-05): [firmware_k8200_v2.1.1.zip](//www.k8200.eu/downloads/files/downloads/firmware_k8200_v2.1.1.zip) * see also https://github.com/CONSULitAS/Marlin-K8200/tree/Vellemann_firmware_k8200_v2.1.1.zip -* V2 (with LCD/SD-Support, date branched: 2013-06-05): [firmware_k8200_marlinv2.zip](http://www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv2.zip) +* V2 (with LCD/SD-Support, date branched: 2013-06-05): [firmware_k8200_marlinv2.zip](//www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv2.zip) * see also https://github.com/CONSULitAS/Marlin-K8200/tree/Vellemann_firmware_k8200_marlinv2.zip -* V1 (without LCD/SD-Support, date branched: 2012-10-02): [firmware_k8200_marlinv1.zip](http://www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv1.zip) +* V1 (without LCD/SD-Support, date branched: 2012-10-02): [firmware_k8200_marlinv1.zip](//www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv1.zip) * see also https://github.com/CONSULitAS/Marlin-K8200/tree/Vellemann_firmware_k8200_marlinv1.zip diff --git a/config/examples/Velleman/K8200/README.md b/config/examples/Velleman/K8200/README.md index 3a10e9c723..2c4d8be2d5 100644 --- a/config/examples/Velleman/K8200/README.md +++ b/config/examples/Velleman/K8200/README.md @@ -1,5 +1,5 @@ -# Example Configuration for Vellemann [K8200](http://www.k8200.eu/) -* Configuration files for **Vellemann K8200** (with [VM8201](http://www.vellemanprojects.eu/products/view/?id=416158) - LCD Option for K8200) +# Example Configuration for Vellemann [K8200](//www.k8200.eu/) +* Configuration files for **Vellemann K8200** (with [VM8201](//www.vellemanprojects.eu/products/view/?id=416158) - LCD Option for K8200) * K8200 is a 3Drag clone - configuration should work with 3Drag https://reprap.org/wiki/3drag, too. Please report. * updated manually with parameters from genuine Vellemann Firmware "firmware_k8200_marlinv2" based on the recent development branch @@ -7,14 +7,14 @@ * VM8201 uses "DISPLAY_CHARSET_HD44870 JAPANESE" and "ULTIMAKERCONTROLLER" * german (de) translation with umlaut is supported now - thanks to @AnHardt for the great hardware based umlaut support -I [@CONSULitAS](https://github.com/CONSULitAS) tested the changes on my K8200 with 20x4-LCD and Arduino 1.6.12 for Mac (SD library added to IDE manually), 2016-11-18 - everything works well. +I [@CONSULitAS](//github.com/CONSULitAS) tested the changes on my K8200 with 20x4-LCD and Arduino 1.6.12 for Mac (SD library added to IDE manually), 2016-11-18 - everything works well. -**Source for genuine [Vellemann Firmware](http://www.k8200.eu/support/downloads/)** -* V2.1.1 (for z axis upgrade, date branched: 2013-06-05): [firmware_k8200_v2.1.1.zip](http://www.k8200.eu/downloads/files/downloads/firmware_k8200_v2.1.1.zip) +**Source for genuine [Vellemann Firmware](//www.k8200.eu/support/downloads/)** +* V2.1.1 (for z axis upgrade, date branched: 2013-06-05): [firmware_k8200_v2.1.1.zip](//www.k8200.eu/downloads/files/downloads/firmware_k8200_v2.1.1.zip) * see also https://github.com/CONSULitAS/Marlin-K8200/tree/Vellemann_firmware_k8200_v2.1.1.zip -* V2 (with LCD/SD-Support, date branched: 2013-06-05): [firmware_k8200_marlinv2.zip](http://www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv2.zip) +* V2 (with LCD/SD-Support, date branched: 2013-06-05): [firmware_k8200_marlinv2.zip](//www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv2.zip) * see also https://github.com/CONSULitAS/Marlin-K8200/tree/Vellemann_firmware_k8200_marlinv2.zip -* V1 (without LCD/SD-Support, date branched: 2012-10-02): [firmware_k8200_marlinv1.zip](http://www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv1.zip) +* V1 (without LCD/SD-Support, date branched: 2012-10-02): [firmware_k8200_marlinv1.zip](//www.k8200.eu/downloads/files/downloads/firmware_k8200_marlinv1.zip) * see also https://github.com/CONSULitAS/Marlin-K8200/tree/Vellemann_firmware_k8200_marlinv1.zip diff --git a/config/examples/Velleman/K8400/README.md b/config/examples/Velleman/K8400/README.md index a739abeb7e..e794292ad4 100644 --- a/config/examples/Velleman/K8400/README.md +++ b/config/examples/Velleman/K8400/README.md @@ -1,6 +1,6 @@ # Velleman K8400 Vertex Configuration -Source: [velleman.eu](https://www.velleman.eu/products/view/?id=417866) +Source: [velleman.eu](//www.velleman.eu/products/view/?id=417866) Configuration files for the K8400, ported upstream from the official Velleman firmware. Like its predecessor, (K8200), the K8400 is a 3Drag clone. There are some minor differences, documented in `pins_K8400.h`. @@ -14,9 +14,9 @@ Single- and dual-head configurations provided. Copy the correct `Configuration.h Upstreamed from: -[birkett/Vertex-K8400-Firmware on GitHub](https://github.com/birkett/Vertex-K8400-Firmware) +[birkett/Vertex-K8400-Firmware on GitHub](//github.com/birkett/Vertex-K8400-Firmware) Credit to Velleman for the original Marlin 1.0.x based code: -- [Download Vertex M1 1.4-H1](https://cdn.velleman.eu/downloads/files/vertex/firmware/vertex-m1-v1.4-h1.zip) -- [Download Vertex M1 1.4-H2](https://cdn.velleman.eu/downloads/files/vertex/firmware/vertex-m1-v1.4-h2.zip) +- [Download Vertex M1 1.4-H1](//cdn.velleman.eu/downloads/files/vertex/firmware/vertex-m1-v1.4-h1.zip) +- [Download Vertex M1 1.4-H2](//cdn.velleman.eu/downloads/files/vertex/firmware/vertex-m1-v1.4-h2.zip) diff --git a/config/examples/WASP/PowerWASP/README.md b/config/examples/WASP/PowerWASP/README.md index 6cab251967..1a8c6e3902 100644 --- a/config/examples/WASP/PowerWASP/README.md +++ b/config/examples/WASP/PowerWASP/README.md @@ -4,7 +4,7 @@ The later versions of the PowerWASP controller board have power loss detection o The retract position on finishing the print has been set at Z190 X0 Y0 -There are provisions made here to use ESP3D wireless printer control from [luc-github/ESP3D](https://github.com/luc-github/ESP3D) +There are provisions made here to use ESP3D wireless printer control from [luc-github/ESP3D](//github.com/luc-github/ESP3D) The original PowerWASP board has available a internal serial port connection with Arduino Serial3. The connections are as follows: @@ -19,7 +19,7 @@ The connections are as follows: `------------´---------------------´ ``` -With the option of wireless file upload to the SD card, the idea of updating the Firmware from the SD can also be useful. This option has been selected, but requires a modified boot loader from [rainerumrobotics/MicroBridge-Arduino-ATMega2560](https://github.com/rainerumrobotics/MicroBridge-Arduino-ATMega2560) +With the option of wireless file upload to the SD card, the idea of updating the Firmware from the SD can also be useful. This option has been selected, but requires a modified boot loader from [rainerumrobotics/MicroBridge-Arduino-ATMega2560](//github.com/rainerumrobotics/MicroBridge-Arduino-ATMega2560) ## USB and SDCARD Firmware flashing for the ARDUINO ATMEGA 2560 and ADK diff --git a/config/examples/Wanhao/Duplicator i3 2.1/README.md b/config/examples/Wanhao/Duplicator i3 2.1/README.md index 7a50749201..efc5262691 100644 --- a/config/examples/Wanhao/Duplicator i3 2.1/README.md +++ b/config/examples/Wanhao/Duplicator i3 2.1/README.md @@ -1,7 +1,7 @@ Configuration for the Wanhao Duplicator i3 v2.1 -[Made by Bot-In-a-Box Educational Robotics](https://botinabox.ca) -[See original configuration repo](https://github.com/BotInABoxER/marlin2-for-wanhao-i3) +[Made by Bot-In-a-Box Educational Robotics](//botinabox.ca) +[See original configuration repo](//github.com/BotInABoxER/marlin2-for-wanhao-i3) > [!NOTE] > - The smaller Marlin logo is used to save memory @@ -15,4 +15,4 @@ Inspirations: Instructions: - Copy the `Configuration.h`, `_Bootscreen.h` (or `Chippy_Bootscreen.h`; rename it `_Bootscreen.h`), and `Configuration_adv.h` to the `Marlin/ directory` -- Flash the firmware onto your Melzi (https://www.fission3d.com/guides/flash-bootloader-and-install-firmware-with-raspberry-pi might help) +- Flash the firmware onto your Melzi (//www.fission3d.com/guides/flash-bootloader-and-install-firmware-with-raspberry-pi might help) diff --git a/config/examples/Weedo/Tina2/README.md b/config/examples/Weedo/Tina2/README.md index d791314892..1a97a1acbd 100644 --- a/config/examples/Weedo/Tina2/README.md +++ b/config/examples/Weedo/Tina2/README.md @@ -9,19 +9,19 @@ There are several versions of the Weedo TINA2 with different hardware. - The TINA2 BASIC is the lite version of the TINA2 with no WiFi module or protective shell. - Uses motherboard R62A/R62AS with ATMEGA2560 MCU. - Firmware files are 8-bit, identified by the "`.hex`" extension. -- [Official TINA2firmware repo](https://github.com/weedo3d/TINA2firmware) +- [Official TINA2firmware repo](//github.com/weedo3d/TINA2firmware) ### TINA2 UPGRADE - V7 hardware. - Current "basic" model. Sometimes called TINA2 or TINA2 BASIC, which adds to the confusion. - Uses motherboard R72A/R72B with a GD32F103RET6 MCU. - Firmware files are 32-bit, identified by the "`.bin`" or "`.wfm`" extension (proprietary format). These firmware files are NOT compatible with the older ATMEGA2560-based models, or vice versa. If your firmware update fails, it may be due to this mismatch. -- [Official Tina2Upgradefirmware repo](https://github.com/weedo3d/Tina2Upgradefirmware) +- [Official Tina2Upgradefirmware repo](//github.com/weedo3d/Tina2Upgradefirmware) ### TINA2S - Current "WiFi" model. Compared to the base TINA2 UPGRADE model, adds WiFi and a heated bed. - Uses motherboard R72H/R72P with a GD32F103RET6 MCU. -- [Official TINA2Sfirmware repo](https://github.com/weedo3d/TINA2Sfirmware) +- [Official TINA2Sfirmware repo](//github.com/weedo3d/TINA2Sfirmware) > [!NOTE] > The "Monoprice Cadet" is a rebranded version of the V2/V3. The provided configuration should work. @@ -34,9 +34,9 @@ There are several versions of the Weedo TINA2 with different hardware. ## Adding WiFi support using ESP3D -You can add WiFi support using [ESP3D](https://github.com/luc-github/ESP3D). +You can add WiFi support using [ESP3D](//github.com/luc-github/ESP3D). Basically connect your own NodeMCU to second serial port of the MCU. -See the [ESP3D wiki](http://esp3d.io/esp3d/) for connection diagrams. +See the [ESP3D wiki](//esp3d.io/esp3d/) for connection diagrams. In `Configuration.h` set: ```c @@ -53,4 +53,4 @@ Feedback is welcome. ## Manufacturer USB support All printers use CH340/CH341 for USB. The driver is often included as part of official driver releases. -[The latest version is also available from the chip manufacturer](https://www.wch.cn/download/CH341SER_EXE.html) +[The latest version is also available from the chip manufacturer](//www.wch.cn/download/CH341SER_EXE.html) diff --git a/config/examples/delta/Anycubic/Predator/README.md b/config/examples/delta/Anycubic/Predator/README.md index fa06405d8e..cf130d6623 100644 --- a/config/examples/delta/Anycubic/Predator/README.md +++ b/config/examples/delta/Anycubic/Predator/README.md @@ -1,14 +1,14 @@ # AnyCubic Predator Notes - At this time, this version is not supported by the stock bootloader as an SD card update. -- Special thanks to Korbinian Heel [[@inib](https://github.com/inib)]. -- Special thanks to Slava Novgorodov [[@Slava N](https://www.youtube.com/channel/UC617QlzItK-dOeTTttKZq3A)] for sharing and making the video of the direct installation method. -- Special thanks to Sebastian Hernandez [[@SXHXC](https://github.com/SXHXC)] for his [fork](https://github.com/SXHXC/Marlin-Anycubic-Predator-Trigorilla-PRO) and doing all the work. +- Special thanks to Korbinian Heel [[@inib](//github.com/inib)]. +- Special thanks to Slava Novgorodov [[@Slava N](//www.youtube.com/channel/UC617QlzItK-dOeTTttKZq3A)] for sharing and making the video of the direct installation method. +- Special thanks to Sebastian Hernandez [[@SXHXC](//github.com/SXHXC)] for his [fork](//github.com/SXHXC/Marlin-Anycubic-Predator-Trigorilla-PRO) and doing all the work. ## Backing Up the Firmware Watch the video below for detailed instructions on the whole process. It is recommended to take the time to make a backup of the firmware currently installed on the board, in case you decide you want to go back to the factory-installed version. -[![Trigorilla Pro reflash to Marlin 2.0.x](https://img.youtube.com/vi/g2cAJXle6t0/0.jpg)](https://www.youtube.com/watch?v=g2cAJXle6t0 "ANYCUBIC Predator original board Trigorilla Pro reflash to Marlin 2.0.x") +[![Trigorilla Pro reflash to Marlin 2.0.x](//img.youtube.com/vi/g2cAJXle6t0/0.jpg)](//www.youtube.com/watch?v=g2cAJXle6t0 "ANYCUBIC Predator original board Trigorilla Pro reflash to Marlin 2.0.x") ## Flashing the Firmware @@ -26,7 +26,7 @@ Use these example config files (adjusted to your needs) and build Marlin as usua ### 3. Get STM32 Flasher -Download the _STM32 Flasher_ software at the ST Micro [download page](https://www.st.com/en/development-tools/flasher-stm32.html#get-software). Use _STM32 Flasher_ to flash your Marlin binary file to the board following the procedure shown in the video. +Download the _STM32 Flasher_ software at the ST Micro [download page](//www.st.com/en/development-tools/flasher-stm32.html#get-software). Use _STM32 Flasher_ to flash your Marlin binary file to the board following the procedure shown in the video. ### 4. Final Steps diff --git a/config/examples/delta/MKS/SBASE/README.md b/config/examples/delta/MKS/SBASE/README.md index 265cb541f9..374e015025 100644 --- a/config/examples/delta/MKS/SBASE/README.md +++ b/config/examples/delta/MKS/SBASE/README.md @@ -19,7 +19,7 @@ From|To If using pins other than the J8 pins listed above the `spi_pins.h` file will need to be modified. -An octopus cable like the [Adafruit 1199](https://www.adafruit.com/product/1199) 10-pin IDC Socket Rainbow Breakout Cable can simplify the construction of the custom cable. Just plug the Adafruit 1199 into one of the cables that came with the LCD and the individual pins into J8 and EXP2 as needed. +An octopus cable like the [Adafruit 1199](//www.adafruit.com/product/1199) 10-pin IDC Socket Rainbow Breakout Cable can simplify the construction of the custom cable. Just plug the Adafruit 1199 into one of the cables that came with the LCD and the individual pins into J8 and EXP2 as needed. --- diff --git a/config/examples/delta/Malyan M300/README.md b/config/examples/delta/Malyan M300/README.md index 194769b273..af4b3b741c 100644 --- a/config/examples/delta/Malyan M300/README.md +++ b/config/examples/delta/Malyan M300/README.md @@ -15,7 +15,7 @@ guide you through the configuration and compilation. 6. Open the **Tools** > **Board** submenu, scroll all the way down, and select **3D Printer Boards**. 7. From the **Tools** menu, select a board part number **Malyan M300**: 8. From the **Tools** menu, choose **USB Support** > **CDC No Generic Serial**. -9. Download the [latest Marlin source](https://marlinfw.org/meta/download/) and unzip it. +9. Download the [latest Marlin source](//marlinfw.org/meta/download/) and unzip it. 10. Look in the `Marlin` subdirectory for the `Configuration.h` and `Configuration_adv.h` files. Replace these files with the configurations in the `config\examples\Malyan\M300` folder. 11. Open the `Marlin/Marlin.ino` file in Arduino IDE. 12. From the **Sketch** menu, select **File** > **Export Compiled Binary**. diff --git a/config/examples/delta/kossel_pro/README.md b/config/examples/delta/kossel_pro/README.md index 37b5ccf07f..9fcda88f6b 100644 --- a/config/examples/delta/kossel_pro/README.md +++ b/config/examples/delta/kossel_pro/README.md @@ -1,5 +1,5 @@ -# Example Configuration for OpenBeam Kossel Pro [BRAINWAVE_PRO](http://www.openbeamusa.com/3d-printers/kossel/) +# Example Configuration for OpenBeam Kossel Pro [BRAINWAVE_PRO](//www.openbeamusa.com/3d-printers/kossel/) * Configuration files for the **Openbeam Kossel Pro** as delivered in their KickStarter distribution -I [@Wackerbarth](https://github.com/Wackerbarth) tested this version on my Kossel Pro and Arduino 1.6.5 for Mac. +I [@Wackerbarth](//github.com/Wackerbarth) tested this version on my Kossel Pro and Arduino 1.6.5 for Mac. This configuration is a transition to merge Terence Tam's configuration with up-to-date Marlin source and a current Arduino IDE diff --git a/config/examples/delta/kossel_xl/README.md b/config/examples/delta/kossel_xl/README.md index 0ae681a1f7..cf83b51202 100644 --- a/config/examples/delta/kossel_xl/README.md +++ b/config/examples/delta/kossel_xl/README.md @@ -5,7 +5,7 @@ This example configuration is for a Kossel XL with a printable bed diameter of 2 You might need (or want) to edit at least the following settings in `Configuration.h`: * `MANUAL_Z_HOME_POS` - The available height of your printing space. Auto Bed Leveling makes it less important to have the exact value. * `PRINTABLE_RADIUS` - The printable radius is how far from the center the nozzle can reach. -* `DEFAULT_AXIS_STEPS_PER_UNIT` - Steps-per-millimeter for the delta steppers, and for the extruder [to optimize the amount of filament flow](http://zennmaster.com/makingstuff/reprap-101-calibrating-your-extruder-part-1-e-steps). +* `DEFAULT_AXIS_STEPS_PER_UNIT` - Steps-per-millimeter for the delta steppers, and for the extruder [to optimize the amount of filament flow](//zennmaster.com/makingstuff/reprap-101-calibrating-your-extruder-part-1-e-steps). ### Fine tuning * Increase `DELTA_RADIUS` if the model comes out convex (with a bulge in the middle)