Creality CR Touch Not Probing: Diagnosis and Fixes

A CR Touch that is not deploying, with the pin staying up at power-on or at the start of a probe, almost always has one of four causes. The pin may be bent, dirty or binding in its housing; the cable may be loose or pinched; the power and control wires may be swapped; or the firmware may lack probe support. Check them in that order.

Not deploying is one of three ways a CR Touch fails to probe. In the first, the LED flashes red and the pin never drops. In the second, the pin drops but the carriage keeps descending as if nothing triggered. In the third, the mesh dies part way through with a probing error. Each is a different fault, and the order you check them in matters: reflashing firmware will not cure a bent pin, and a new probe will not cure a swapped wire.

Why is my CR Touch not deploying?

Usually the pin can’t move freely, or the probe isn’t getting power and a control signal. A healthy CR Touch drops and retracts its pin twice at power-on, then the LED settles to steady blue. If that power-on cycle doesn’t happen, the fault is mechanical or electrical. If the self-test passes but the pin stays up when you home or level, suspect firmware or configuration first.

Match what you see to the likely cause before you take anything apart:

The last row comes from a CR-10 Pro V2 thread on 3D Printing Space. In the same thread, one owner found a probe wire that had come out of its socket, probably snagged by the extruder. Another found the pin was still bent inside the housing after straightening the visible part.

How to fix a CR Touch pin that will not drop

Owners in a long Ender-3 V3 SE thread on Creality’s forum have reported fixes, and most of them are mechanical. Work through these steps in order:

1. Power off and inspect the pin. It should be straight and slide in and out with no grit or drag. One SE owner cleared the error just by “carefully moving the cr-touch by hand”. Another powered off, eased the pin out with tweezers, restarted and re-leveled.
2. Clean and re-lubricate. In the same thread, an owner explained that dust mixed with the factory lubricant can get sticky enough to hold the pin up. Their fix was cleaning with isopropyl alcohol, then applying fresh lubricant sparingly. This matches the “error after sitting overnight, pin works if pushed” pattern.
3. Try a shim if the plunger binds. One owner traced repeated errors to the plunger binding and creating suction, and reported a printed shim had kept it “99% error free” for two months. Another fitted a ring about 1 mm thick, cut from a pen refill or small PU hose, around the pin.
4. Reseat every connector and check the routing. On the V3 SE, an owner found the hotend cover pressing on the CR Touch cable when its screws were tightened. Removing the left screw stopped the false contact for testing, at the cost of some vibration. Another owner rerouted the cable behind the cover bracket.
5. Clear the latched alarm. Send M280 P0 S160 in Marlin, or BLTOUCH_DEBUG COMMAND=reset in Klipper (the Klipper docs note that a probe left in an inconsistent state “starts blinking red”). Then command pin down and pin up and watch the pin.
6. Power-cycle and watch the self-test. Two full cycles and a steady blue LED is Creality’s pass condition. If it still won’t move, the 3D Printing Space thread has the right diagnosis: it is “binding in the throat somewhere.”
7. Replace the probe if steps 1 to 6 don’t bring it back. Creality’s product page claims more than 100,000 uses, but a buyer reviewing it there reported their pin stopped deploying after seven months.

On Creality’s forum, a V3 KE owner reported the error appeared after updating to Creality Print 6.1.1.2274 and cleared after rolling back to the previous version. That was before the replacement probe they had ordered arrived. If the error started right after a software change, rule that change out before buying a probe.

Read the probe before you touch anything

Creality’s own checklist for the “CR-Touch error” on the Ender-3 V3 SE is short. The fault analysis page calls it a “CR-touch Self-check Abnormality”. It tells you to check “whether the red light is flashing / there is no light flashing” and “whether the probe can be probed normally twice after the machine is turned on.” A healthy probe cycles its pin twice at power-on and settles to steady blue. Flashing red is an alarm. No light points to a power fault, not a fault in the probe itself.

The CR Touch uses the BLTouch servo-angle protocol, which is why Marlin runs it under the BLTOUCH define and Klipper under [bltouch]. It is still a different part. Creality’s product page describes a metal probe and a “light-triggered” normally-open Hall-effect switch. Marlin’s probe documentation describes the BLTouch as a Hall-effect sensor watching a magnetic pin. Most BLTouch advice transfers. The exception is the Klipper docs’ procedure for pushing a BLTouch’s magnetic core back down through its top screw, which is written for the ANTCLABS part.

One reading that fools people: Marlin’s M119 docs note that “the BLTOUCH probe only sends a brief pulse, so TRIGGERED indicates the probe is in error state.” A z_probe: TRIGGERED at idle means alarm, not “working”.

Cause 1: the pin is stuck or bent

Symptom: red flash at self-check, or the mesh stalls after a few points with the pin retracted. An Ender 3 V2 thread on Creality’s forum describes exactly that, stuck around the third point with the LED flashing red. Creality Support’s reply: re-plug the probe cable and, powered off, press the probe tip for 10 seconds. Others cleared it with the menu self-test or by cycling the pin by hand. If the pin is visibly bent, which the DREMC install guide lists as the first flashing-red cause, replace the probe. A straightened pin drags in the housing and the alarm comes back.

Cause 2: wiring, connector and the ribbon cable

Creality has not kept the wire colour order consistent across CR Touch batches. The Duet3D forum’s CR Touch thread opens with an owner who destroyed a probe on swapped wires, and the Duet maintainer confirms “what hasn’t been consistent is the wiring colour/order Creality use.” Verify the pinout from the probe, not the colours. On a 4.2.2 board the five wires land on the probe header as G, V, IN, G, OUT.

The SE Configuration_adv.h says a probe that is not deploying needs a Reset and Self-Test, then a check of the “BROWN, RED and ORANGE wires” (power and control). An unrecognised trigger, it says, “has been very often because the BLACK and WHITE wires needed to be swapped.” So if the pin moves but never triggers, check the signal pair; if the pin never moves, check the power and control wires. ANTCLABS’s V3 page adds that a red LED flashing at 80 percent duty during a print means a power-wire fault.

On the V3 SE and KE, the CR Touch is mounted on the toolhead, and Creality’s SE fix is to re-plug the CR Touch and the adapter-board ribbon at both ends. Check the SE and KE hardware differences before following the model-specific wiring procedure. The KE’s error 2194 page lists “CR-touch red light flashing, probe not deploying” as a cause of Z failing to home in self-test; the fix is to re-seat the 30-pin ribbon at both ends. A V3 KE owner who tapped the pin with a screwdriver to get through self-check had the same fault.

V3 Plus owners should use their model’s strain-gauge service procedure and model-specific Z-offset guidance. The CR Touch wiring and pin-test commands below apply only to printers fitted with a CR Touch or a compatible deploying-pin probe.

Cause 3: firmware that does not know a probe exists

The CR Touch kit is sold for the 32-bit 4.2.2 and 4.2.7 boards only. Creality’s product page warns that it “doesn’t work for the 8-bit mainboard” and tells you to download the CR-Touch firmware and flash it from the SD card. Stock Ender-3 and V2 firmware homes Z on the endstop switch. If you fit the probe without the firmware, Z homes with the pin retracted and the nozzle goes down first.

According to the Marlin docs, a probe on the Z-min pin needs Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN. Creality’s SE Configuration.h enables that along with USE_PROBE_FOR_Z_HOMING, Z_SAFE_HOMING and a 4 x 4 bilinear mesh. The firmware update guide covers the flashing steps.

Cause 4: offsets that send the pin off the plate

If the pin drops over thin air at a bed edge, Marlin drives to Z_PROBE_LOW_POINT and STOPs; in the SE config that point is -2 mm below the expected trigger. An Ender-3 owner on a 4.2.7 board reported probe points about 1.5 cm right of where they belonged. The moderator’s fix was Configuration > Advanced Settings > Probe Offsets, using the standard Ender-3 values of X -45 and Y -5. Creality’s SE source carries three different NOZZLE_TO_PROBE_OFFSET sets for different production runs, so check yours against the physical probe. Once the offsets are fixed, Marlin’s M999 docs apply: a failed deploy aborts probing and STOPs the printer, “note that this disables all heaters,” and M999 restarts it.

Cause 5: probing faster than the pin can retract

Creality ships the SE with BLTOUCH_HS_MODE on, under Marlin’s own warning: “Danger: Disable if your probe sometimes fails… If the machine can’t raise Z fast enough the BLTouch may go into ALARM.” The rest of the SE probe block:

• Z_PROBE_FEEDRATE_FAST (10*60), which is 10 mm/s, with a commented 4 mm/s alternative
• a slow probing speed of half that
• MULTIPLE_PROBING 2
• BLTOUCH_DELAY 350 ms
• 10 mm deploy clearance and 3 mm between points

A mesh that fails at random points on a tired Z lead screw fits this cause. Compile with HS mode off, or drop the fast feedrate to 4*60.

The KE’s Klipper printer.cfg declares speed: 5, lift_speed: 20, probe_with_touch_mode: true and stow_on_each_sample: false, with a 5 x 5 mesh at horizontal_move_z: 8. The Klipper docs warn that stow_on_each_sample: False travels with the pin down, so if clearance is lost, the pin can catch on a bed clip.

Reset and test commands

For Marlin with a configured CR Touch or compatible BLTouch probe, send these from a terminal. The M280 angles come from the ANTCLABS manual:

M280 P0 S160   ; alarm release and pin up
M280 P0 S120   ; self-test, cycles the pin 10 times
M280 P0 S10    ; pin down
M280 P0 S90    ; pin up
M119           ; z_probe should read open with the pin up
M999           ; clear a STOP once the cause is fixed

For Klipper on the KE, or a conversion fitted with a CR Touch or compatible BLTouch probe and configured with [bltouch], use these commands from the Klipper docs:

BLTOUCH_DEBUG COMMAND=reset      ; clear a latched alarm
BLTOUCH_DEBUG COMMAND=pin_down
BLTOUCH_DEBUG COMMAND=touch_mode
QUERY_PROBE                      ; expect "probe: open"
QUERY_PROBE                      ; nudge the pin up first: expect "probe: TRIGGERED"
BLTOUCH_DEBUG COMMAND=pin_up
PROBE_ACCURACY

If pin_down does nothing, the Klipper docs say to go back and check wiring and configuration before going further. “BLTouch failed to raise probe” is mechanical, so go back to cause 1. “BLTouch failed to verify sensor state” is the clone check. Klipper says to set pin_up_touch_mode_reports_triggered: False only if the manual test above passes every time and the error persists. The same page warns that setting the clone flags to False wrongly “can increase the risk of damaging the printer.”

How to verify the fix

1. Power cycle. The pin drops and retracts twice and the LED settles blue, Creality’s own pass condition.
2. M119 or QUERY_PROBE reads open at idle.
3. Home with the fingernail test from the Klipper docs: touch the pin before it reaches the bed and Z must stop; then home again untouched.
4. Run a full mesh (16 points on the SE, 25 on the KE) with no red flash and no STOP.
5. On the SE, read the Z compensation value. Creality’s leveling failure page puts normal values between -1 and -3. A reading of -0.04, 0 or -10 means the height calibration failed even though the probe moved.

Then tune the first layer with the Z offset guide and the bed leveling and extrusion tuning post. If the probe is dead and a replacement is days away, fdmdesk’s manual bed leveling walkthrough keeps an Ender-3 printing on the four knobs.

If probing and homing pass normally but plastic fails to extrude, diagnose extrusion stoppages before changing the probe configuration.

If you own a K1, K1C or K1 Max

There is no CR Touch on the K1 series; its leveling strain sensors are at the heatbed. The bed leveling guide explains the K1 Max’s four heatbed sensors. Creality’s K1 Max leveling page works from the mesh data. Under 3 mm from highest to lowest point is normal. Over 5 mm with a normal trend means the Z axis needs re-tensioning, and an abnormal trend points at the strain gauge. It is a different sensor with a different fault tree.

Related across the network

• How to Level a Bed With BLTouch: Marlin and Klipper Guide — printlabguide.com
• Klipper vs Marlin: Which Firmware Should You Run? — klipperlab.com
• How to Calibrate E-Steps on Ender 3 (Step by Step) — printlabguide.com
• Pressure Advance Calibration for Klipper and Marlin — printlabguide.com
• Anycubic Bed Leveling: The Paper Method and Z Offset — anycubicguide.com

FAQ

why is my cr touch flashing red and not deploying

A flashing red CR Touch has latched an alarm, usually because the pin hit something, is bent, or is binding in the housing during the power-on self-test. Power off, confirm the pin slides freely and is straight, and reseat the cable. Then clear the alarm with M280 P0 S160 in Marlin or BLTOUCH_DEBUG COMMAND=reset in Klipper.

how do i reset a cr touch

Send M280 P0 S160 from a Marlin terminal to release the alarm and raise the pin, then M280 P0 S120 to run the self-test. On Klipper, use BLTOUCH_DEBUG COMMAND=reset. A full power cycle also re-runs the self-test, and Creality Support has suggested pressing the probe tip for 10 seconds with the printer off.

can a stuck cr touch pin be fixed without replacing it

Often, yes. Owners on Creality’s forum have cleared sticky pins by cleaning the plunger with isopropyl alcohol and re-lubricating it, freeing it by hand with the power off, or fitting a ring about 1 mm thick around the pin to stop it binding. A visibly bent pin is the exception: replace the probe.

does a cr touch need special firmware

Yes, on printers that shipped without a probe. Stock Ender-3 and Ender-3 V2 firmware homes Z on the endstop switch, so Creality tells CR Touch kit buyers to flash its CR Touch firmware from the SD card. The kit only supports the 32-bit 4.2.2 and 4.2.7 boards; Creality says it does not work on 8-bit mainboards.

how long does a cr touch last

Creality’s product page rates the CR Touch for more than 100,000 uses, but that is a manufacturer claim, not an independent figure. Real-world life depends on crashes and dirt. One buyer reviewing the probe on Creality’s store reported it stopped deploying after seven months, and a bent pin usually means you need a new probe.