Simple AF BlTouch
I AM NOT RESPONSIBLE FOR DAMAGE TO YOUR PRINTER - INSTALLING CUSTOM FIRMWARE IS A RISK
I am currently doing a GoFundMe fundraiser to purchase an additional K1 printer, just so we can push out fixed and new features a bit faster.
Yep you can use a CrTouch or 3dTouch as an alternative to a BlTouch, however I have not personally used either of these with a K1 and so I can't currently provide detailed guidance on what config is required. I also think 3dTouch might require slightly different wiring.
Come on over to the pellcorp discord server, here is the invite https://discord.gg/tQFy85DWEV
The #simple-af-support channel has been setup for anyone wanting support for bltouch, crtouch or 3dtouch.
Once you accept the invite, you will be sent a DM from YAGPDB.xyz with a link you need to open to solve a captcha to prove you are not a robot:
Then you should be able to open the #rules channel, click the Agree link to get access to all the channels:
I know its a pain, but we were getting unwanted bots on the server and had no choice.
This guide assumes you have a K1, K1C or K1 Max and you are running stock creality firmware 1.3.3.5 or higher, or alternately you are using my prerooted firmware. Any other pre-rooted firmware is explicitly not supported and the installer.sh will validate this and refuse to proceed if you try to use it on different firmware.
There is an assumption that you are using a slicer like OrcaSlicer and Machine G-code like:
Machine start G-code
M104 S0 ; Stops OrcaSlicer from sending temp waits separately
M140 S0
START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single]
Machine end G-code
END_PRINT
The configuration assumes you are using this mount: https://www.printables.com/model/666186-creality-k1-bltouch-adapter
The probe and the TOUCH port on the Nozzle MCU board both mate with a 5-pin Molex Picoblade connector. A 5-pin cable is needed to connect the probe to the TOUCH port.
Some sellers may call the connector "Micro JST SH 1.25" but that is incorrect. Several premade cables are compatible. Most notably the Creality cable for their CR Touch probe:
- https://www.aliexpress.us/item/1005004960067376.html
- https://www.amazon.com/dp/B0BKPFY24M/
- https://www.bastelgarage.ch/0-1m-creality-cr-touch-bl-touch-adapterkabel-sprite-extruder
Alternatively, two pre-crimped cables can be soldered together:
Or a cable built from pre-crimped wires and connector housings:
Connect to TOUCH port on the nozzle MCU. it is accessible from the side left (LIDAR) side of the printhead and only the external cover of the printhead has to be removed.
IMPORTANT: The configuration file assumes a bltouch is mounted on the back of the tool head. If you have a Crtouch or are mounting your bltouch or 3dtouch using a different model, you must make additional changes to the bltouch-k1.cfg or bltouch-k1m.cfg files before trying to home your printer.
Source: Portions of this section are copied from the K1 Bltouch guide for helper script.
Unfortunately I don't have a CrTouch, so ive never tested it, but I know its possible to use it, this is a model I know other users have used, https://www.printables.com/model/777638-cr-touch-mount-k1-k1maxk1c
But currently I don't have all the right config changes that are required, but probably you will need the change the min and max mesh, max and min positions for y and x might need to be changed.
The installation can only be performed on a printer which has been rooted and ssh granted
You need root access, if you are not already root, then follow this guide https://guilouz.github.io/Creality-Helper-Script-Wiki/firmwares/install-and-update-rooted-firmware-k1/#enable-root-access
You must do a factory reset before running the installer.sh. Follow these steps to do a factory reset, which retains root access and skips the startup calibration checks:
wget --no-check-certificate https://raw.githubusercontent.com/pellcorp/creality/main/k1/services/S58factoryreset
chmod +x S58factoryreset
./S58factoryreset reset
IMPORTANT: Do not CTRL-C or close the terminal running this command until your printer disconnects the session itself, or the K1 screen UI reappears with or without the 3002 error, doing so will interrupt the factory reset and leave things in a weird state. Please ignore 'New firmware is found' message, do not do anything on the screen.
git config --global http.sslVerify false
git clone https://github.com/pellcorp/creality.git /usr/data/pellcorp
sync
RPC Timeouts, try SSH Git Clone
mkdir -p /root/.ssh wget --no-check-certificate "https://raw.githubusercontent.com/pellcorp/creality/main/k1/ssh/git-ssh.sh" -O /root/git-ssh.sh chmod 777 /root/git-ssh.sh wget --no-check-certificate "https://raw.githubusercontent.com/pellcorp/creality/main/k1/ssh/pellcorp-identity" -O /root/.ssh/pellcorp-identity export GIT_SSH_IDENTITY=pellcorp export GIT_SSH=/root/git-ssh.sh git clone [email protected]:pellcorp/creality.git /usr/data/pellcorp cd /usr/data/pellcorp && git remote set-url origin https://github.com/pellcorp/creality.git && cd
If you have pellcorp-overrides in github but not stored locally, you need to recreate the /usr/data/pellcorp-overrides directory before running the installer.sh!
To run the script, you must specify the probe you want to use.
/usr/data/pellcorp/k1/installer.sh --install bltouch
RPC failed; curl 18 transfer closed
You might get this error:error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Just rerun the installer.sh script (with the same probe argument), it will start from the stage that failed (most of the time this will be the Installing Klipper stage!)
You can also prefix the installer command with AF_GIT_CLONE=ssh to force git to clone via ssh, this will take a lot longer, but it will never time out, so its good in a pinch if you are getting repeated klipper repo clone failures.
At the end of the installer process if you get this message:
MCU Firmware updates are pending you need to power cycle your printer!
It means that new MCU firmware updates need to be applied and this can only be done by power cycling the printer. After your printer is power cycled you can verify firmware was updated with the CHECK_FIRMWARE macro from Fluidd or Mainsail, if you see this message:
Your MCU Firmware is up to date!
Your printer MCU firmware was updated successfully. If you still see the MCU Firmware updates are pending you need to power cycle your printer! message after a power cycle, check the /tmp/mcu_update.log, you may be asked to provide this file on Discord if you need additional assistance, sometimes an additional power cycle can solve the problem, there is a very short window of time (15 seconds) in which the MCU firmware can be updated, so there is a chance it will work after an additional power cycle.
If you are using the booty gantry and gantry mount, you will need to adjust the printer.cfg stepper configuration, and the bed mesh configuration in the bltouch-k1.cfg or bltouch-k1m.cfg.
Follow the Paper Test Method
Upon completion SAVE_CONFIG
For the bltouch/3dtouch/crtouch it is extremely important to do the PROBE_CALIBRATE step to configure your z-offset, regardless of what model you have used to mount the probe!
Note: The default z-offset for BLTouch, 3dTouch and CrTouch is 0, so your prints won't stick without doing this step.
as in it will try to dig a hole into the bed.
For bltouch, etc you cannot use more than microsteps: 64.
Next it is highly recommended to perform axis twist compensation calibration before doing anything else, this will affect the quality of your bed mesh, so best to do it before.
- Home All (
G28) - Run
AXIS_TWIST_COMPENSATION_CALIBRATEThe calibration wizard will prompt you to measure the probe Z offset at a few points along the bed Upon completionSAVE_CONFIG
Source: https://www.klipper3d.org/Axis_Twist_Compensation.html
For this first print you can go and do the tuning first (PID Tuning, etc) or you can go ahead and optimise your probe z offset using baby stepping.
In fluidd the save button after you finish or cancel your print can be a bit hard to find, look for
At least PID tuning (bed and extruder) and input shaping is required for acceptable printing. If you try and print after running the installer.sh and a power cycle but before any calibration you will most likely have horrendous quality, the worst you have ever seen on the k1. After PID tuning and input shaping you should see the same kind of quality as you get with stock k1 + input shaper fix.
You can use the QUICK_START Macro to automatically complete Bed and Nozzle PID Tuning and Input Shaping Automatically.
https://www.klipper3d.org/Config_checks.html?h=pid#calibrate-pid-settings
For example you might run these:
PID_CALIBRATE_BED BED_TEMP=65
PID_CALIBRATE_HOTEND HOTEND_TEMP=230
Note: The PID_CALIBRATE_BED and PID_CALIBRATE_HOTEND macros are located in the useful_macros.cfg file and they have defaults
values for BED_TEMP and HOTEND_TEMP so you can just run them by clicking on them if you want that same temperature.
There is no default configuration for input shaping so it is essentially disabled out of the box.
You can use the SHAPER_CALIBRATE macro to run input shaping, just be sure to SAVE CONFIG at the end, to choose the automatically selected shaper config, be aware though that the shaper chosen might be sub-optimal due to a slight difference in vibrations between two options. So you should probably review the output and potentially choose an alternative if it gives you higher recommended max acceleration for minimal increase in vibration.
https://www.klipper3d.org/Measuring_Resonances.html#input-shaper-auto-calibration
Note: The default value for pressure advance is set to: 0.04
Refer to https://github.com/SoftFever/OrcaSlicer/wiki/Calibration for more calibrations
This is an excellent resource for all things 3d print tuning: https://ellis3dp.com/Print-Tuning-Guide/
Octoeverywhere can be installed onto the K1 when running the BlTouch, CrTouch or 3dTouch. However it is strongly recommend that you do not do this as the stress placed on the system by running octoeverywhere is significant. The octoeverywhere companion running on another device on the same WIFI network as the K1 works great.
https://blog.octoeverywhere.com/octoeverywhere-companion-remote-access-for-any-klipper-printer/
Moonraker timelapse is installed but not enabled by default. To enable it there are a few steps, you need to add the following include to printer.cfg:
[include timelapse.cfg]
And uncomment the [include timelapse.conf] in moonraker.conf, you will need to restart moonraker and klipper after this, you can that via the fluidd or mainsail services section.
If you see these messages:
15:14:24 // Unknown command:"_SET_TIMELAPSE_SETUP"
15:14:24 // Unknown command:"HYPERLAPSE"
It means you have not as yet properly restarted moonraker and/or klipper. If in doubt just power cycle your machine.
The /etc/init.d/S58factoryreset has recently been updated not to delete the /etc/localtime, so you can configure it once and it should survive any number of factory resets, following the excellent guide here: https://guilouz.github.io/Creality-Helper-Script-Wiki/firmwares/change-date-and-time/
To update your installation with the latest fixes you should run:
/usr/data/pellcorp/k1/installer.sh --update-repo
/usr/data/pellcorp/k1/installer.sh --update
This backs up your customisations, updates the creality repo, applies all changes to your /usr/data/printer_data/config directory and then reapplies your customisations over the top.
Refer to Update or Reinstall - What gets overriden
A reinstall is only needed if you are switching probes or one or more github repos have got into an inconsistent state, so you can force a reinstall with the --reinstall argument in place of the --install argument. The difference to a --install, is a --install will only finish up a partial install that failed due to a network failure or the like.
Refer to Update or Reinstall - What gets overriden
If the worst happens and you somehow get locked out (for instance for whatever reason the dropbear ssh session does not start or wifi config gets all screwy, it is possible to trigger a emergency factory reset.
It is very easy, you just need to create a empty file called emergency_factory_reset on a USB key and make sure the USB key is plugged in, then power cycle the printer, this will initiate a factory reset.
IMPORTANT: This factory reset method will rename the emergency_factory_reset to emergency_factory_reset.old to avoid a boot loop, so if you need to use this method again you will need to rename the file.
IMPORTANT: This factory reset method will not remove the special service file /etc/init.d/S58factoryreset from the k1, so if you need it you can redo a factory reset even before reinstalling.
Note: This method does not reset wifi or root access