How to Upload Custom Firmeare Settings Cura .ini
When someone buys a new slice of engineering science, the outset thing they tend to practise is plug information technology in and kickoff using it. Updating things similar the firmware tends to get ignored most of the time, but it shouldn't. Updating the firmware tin can bring in new features and prepare known bugs making it well worth doing the upgrade. That said, in some cases, the articles firmware may not be the all-time choice.
Here are the steps to install custom Marlin firmware on a 32-chip Creality board.
- Install Visual Studio Code
- Download Marlin Firmware and Configuration Examples
- Re-create Configuration Files to the Marlin Firmware Directory
- Update the platformio.ini File
- Update the Marlin Configuration
- Build the Firmware
- Copy the Firmware to an SD Menu
- Install the Firmware on the Printer
*This process assumes you lot accept a Creality 32-bit mainboard and plan to Marlin firmware on it. If you are looking to run the prebuilt Cerality firmware, you should follow this guide, "Creality 32-Bit Mainboard Firmware Upgrade Guide".
** This process has been tested using the Creality 4.2.ii and 4.2.7 mainboard.
Why Move to the Marlin Firmware?
The Marlin firmware is has been around a while and has a big user community backside it, meaning you can get support and bugs fixed if needed. As well, it'southward free, compatible with most with a broad range of mainboards, and has frequent updates.
You can also download a copy of Marlin I built with the required changes and apply supplied configs as a starting point. The firmware is available to download from "3D Printscape Marlin Builds".
Step-by-Footstep Firmware Upgrade Guide
Requirements
Required Hardware
- Creality printer with 4.2.2 or iv.2.7 mainboard
- Micro SD card *8GB or smaller
- SD Card Reader
- BLTouch
- Computer
*Links are to Amazon and for the products I utilise.
Required Software
- Visual Studio Code
Step-by-Step Guide
If you encounter an issue or need assistance, bring together united states on Discord.
Install Visual Studio Code
The commencement thing you need to do is download and install Visual Studio Lawmaking (VS Lawmaking). Bold y'all are not doing anything out of the ordinary, the install process tends to be quick and easy.
Follow these steps to install VS Code
- Download VS Code for the operating system y'all are running.
- Run the VS Code installer using the default values provided
- Launch VS Code
Install Platform.io
Once yous have VS Code installed, you will need to install the Platform.io plugin. To do this, you will desire to click on Extensions on the left side menu and search for platform.io. Y'all will see PlatformIO IDE come up in the search results. Click on that so click install.
The install process will run in the background and update you lot with a notification at the bottom correct of the VS Code user interface when information technology's washed. Once done, y'all volition want to restart VS Lawmaking.
Download Marlin Firmware and Configuration Examples
Next, we will demand to download the firmware nosotros program on using. There are 2 things we need to become from there, the firmware and the configuration example.
Firmware
To do that, get to the Marlin download site and download both bugfix-ii.0.x.zero, shown below.
Configuration Examples
To become the example configurations, click on View/Download adjacent to the firmware you just downloaded to become to the GitHub page. Then click on the green code button and click Download Zip.
Unzip Files
Now that we take downloaded both packages nosotros need, you will want to unzip them. You can unzip both files in the location they are in, but yous volition desire to motion the unzipped firmware to your desktop or somewhere closer to the root of the drive. The firmware needs to exist close to the root of the bulldoze to prevent whatever issue effectually the length of the file path.
Copy Configuration Files to the Marlin Firmware Directory
Now nosotros volition want to copy the example configs from the example directory to the Marlin folder in the firmware directory, in my case, "C:\Users\Owner\Desktop\Marlin-bugfix-2.0.x\Marlin".
You will find the example configs in the Configurations-bugfix-2.0.x binder that you lot extracted. Once in that folder, you will want to get the examples for the printer you are working with. I have the Ender 3 Pro with the 4.2.2 board, so that'due south what I will be looking for and tin can be constitute in the Creality binder. From at that place, I need to get into the folder for the board I'm using.
In that binder, you will find four config files ending with .h. Y'all desire to copy those files to the Marlin folder mentioned to a higher place, overwriting any files that already exist.
Update the platformio.ini File
Next, we will want to update the default_envs value in the platformio.ini file that is in the root directory of the firmware.
| Default Value | New Value |
|---|---|
| default_envs = mega2560 | default_envs = STM32F103RET6_creality |
*** If your printer was purchased in 2022 y'all may have the RCT6 bit (or 256k). If you exercise, you will want to use STM32F103RC_creality. You tin can follow this video to see what chip you lot have.
Make sure to salvage the file subsequently you brand the change.
Update the Marlin Configuration
Load Firmware into VS Code
The next thing you will want to practise is load the firmware into VS Code to make the necessary changes and build it. To exercise that, you lot will want to follow these steps.
- Open up VS Code
- Go to File – Open Folder
- Browse to the firmware folder and click Select Folder
Recommended Changes
At present I will go over the changes yous should make if regardless of the mods you are running. If y'all have the BLTouch, you lot will desire to make these changes and the changes in the next section.
Configuration.h Changes
Path: Marlin\Configuration.h
| Default Value | New Value | Notes |
|---|---|---|
| #define CUSTOM_MACHINE_NAME "Ender-3 Pro V1.5" | #ascertain CUSTOM_MACHINE_NAME "CUSTOM VALUE Here" | Repalce "CUSTOM VALUE HERE" with what you desire on the display. |
| //#ascertain S_CURVE_ACCELERATION | #define S_CURVE_ACCELERATION | |
| //#ascertain LEVEL_BED_CORNERS | #ascertain LEVEL_BED_CORNERS | |
| //#ascertain INDIVIDUAL_AXIS_HOMING_MENU | #define INDIVIDUAL_AXIS_HOMING_MENU | |
| #warning "Creality 4.2.2 boards may have A4988 or TMC2208_STANDALONE drivers. Check your board and make sure to select the right DRIVER_TYPE!" | //#warning "Creality 4.2.2 boards may have A4988 or TMC2208_STANDALONE drivers. Cheque your lath and make certain to select the correct DRIVER_TYPE!" | Verify the driver is correct, then comment out this line |
*You should also make any additional changes you want/need to at his point.
Required Changes if Running a BLTouch
If you lot have the BLTouch, yous will desire to make these changes besides.
Configuration.h Changes
Path: Marlin\Configuration.h
| Default Value | New Value | Notes |
|---|---|---|
| #ascertain Z_MIN_PROBE_ENDSTOP_INVERTING false | #define Z_MIN_PROBE_ENDSTOP_INVERTING true | Only needed if using a build before July 2021. You will become an error if using this on a afterward build. |
| //#define BLTOUCH | #define BLTOUCH | |
| #define NOZZLE_TO_PROBE_OFFSET { ten, ten, 0 } | #define NOZZLE_TO_PROBE_OFFSET { Ten, Y, 0 } | X & Y should be replaces with your offsets |
| //#define AUTO_BED_LEVELING_BILINEAR | #define AUTO_BED_LEVELING_BILINEAR | |
| //#define Z_SAFE_HOMING | #define Z_SAFE_HOMING |
If you lot have z-end and bltouch probe both plugged in, make these changes as well.
| Default Value | New Value |
|---|---|
| #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN | //#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN |
| //#define USE_PROBE_FOR_Z_HOMING | #define USE_PROBE_FOR_Z_HOMING |
Configuration_adv.h Changes
Path: Marlin\Configuration_adv.h
| Default Value | New Value | Notes |
|---|---|---|
| //#define BLTOUCH_DELAY 500 | #define BLTOUCH_DELAY 500 | |
| //#define BLTOUCH_FORCE_SW_MODE | #define BLTOUCH_FORCE_SW_MODE | |
| //#define BLTOUCH_HS_MODE | #define BLTOUCH_HS_MODE | This is optional but will speed things upward. |
| //#define PROBE_OFFSET_WIZARD | #define PROBE_OFFSET_WIZARD | |
| // #define PROBE_OFFSET_WIZARD_START_Z -4.0 | #ascertain PROBE_OFFSET_WIZARD_START_Z -iv.0 | |
| //#define BABYSTEP_DISPLAY_TOTAL | #define BABYSTEP_DISPLAY_TOTAL | |
| // #define BABYSTEP_ZPROBE_OFFSET | #define BABYSTEP_ZPROBE_OFFSET |
Build the Firmware
Once all your changes accept been fabricated, yous will want to click on the checkmark in the bottom left of the VS Code user interface. That will kick off the build and shouldn't take longer than a couple of minutes to complete. You should encounter success in the terminal window if everything worked. If it didn't, you will be able to get the error from there to troubleshoot.
Copy the Firmware to an SD Bill of fare
In one case the firmware has been successfully built, y'all volition want to elevate information technology to an empty SD menu that is nether 8GB or less.
You can find the firmware under "firmware\.pio\build\STM32F103RET6_creality" , firmware should be replaced with the path where yous have the firmware. In my case, the path is "C:\Users\Owner\Desktop\Marlin-bugfix-two.0.x\.pio\build\STM32F103RET6_creality".
The file proper name will be firmware-date-randomnumber.bin, so firmware-20210225-125416.bin for me.
Install the Firmware on the Printer
This step sounds harder than it actually is. Assuming you copied the right file to an empty SD card, all you need to do is put the SD bill of fare in the printer and power information technology on. From there, the printer volition pull the file and install it on the printer. The entire process should take less than thirty seconds. One time the printer boots into the standard interface, yous can remove the SD bill of fare.
Related Questions
What if I have an 8-bit Creality mainboard? – You will need to install a bootloader on the printer, then push the firmware to information technology. I created a video roofing the process of migrating to the TH3D firmware on an viii-bit board that you tin can see here.
What if I want to add a BLTouch? – I created a video covering the procedure from showtime to finish that you tin see below or can take a look at the commodity that I wrote that covers the process "Guide to Install a BLTOUCH on a Creality 32-fleck Mainboard" .
Practise I demand to recalibrate my e-steps after changing the firmware? – I would recommend doing so to make sure everything is working as expected. Here is a video and article covering the process "3D Printer Eastward-step Calibration (Footstep-by-Step Guide)".
Related Articles
- Creality 32-Bit Mainboard Firmware Upgrade Guide
- Create a Temperature Tower Using Cura – The Piece of cake Mode
- Cura Profiles
- 3D Printscape Marlin Builds
Recap
If yous are looking at making modifications to your 3d printer, yous will most probable need to run a custom firmware build. Moving to the Marlin firmware gives you a great community, more features, and the ability to customize the configuration to meet your needs. The process may look a little intimidating, merely it's really not that bad, and there are a lot of people able to help out if you lot come across bug.
Make sure you bank check out our YouTube channel, and if you would like any additional details or take any questions, please leave a comment beneath or bring together u.s. on Discord. If you liked this article and want to read others click here.
Source: https://3dprintscape.com/marlin-firmware-on-creality-board-complete-guide/
0 Response to "How to Upload Custom Firmeare Settings Cura .ini"
Post a Comment