Dear,
I have just received my ender 3V3 SE and did my first print. after this print I get the error cr touch error please contact customer service. I have checked the cables and reseated them and I also rest the config. but not it is stuck in a boot loop with the same error. Can someone please advise?
Thanks in advance,
Ben
carfuly moving the cr-touch by hand seems to fixed it!
Do you mean the probe was stuck in the retracted position?
Hello, dear Ben
I have solved the same problem with these steps:
I hope it would be usefull
Best wishes?
Semyon
Thank you for your help)))
Same problem here until little bit hardly move entire part plastic of this sensor (around of it)
this realy works well i just replaced my hot end and it didnt work. thank you for the tip 
The issue is very simple to fix. Itās a false contact in the cable. The hotend casing puts too much pressure on the CR Touch sensor cable when itās placed on its mounting points and the screws are tightened. Just design a casing to your liking that leaves the area where the cables connect free. Donāt forget to leave room for the preparation of fan 2.
PD: Even so, itās a factory issue due to poor design.
Or leave that single lefthand screw off as a test, no screw no pressure?
That causes a bit of vibration in the head, but it works for testing.
Iāve routed the CRtouch cable behind the cover fixing bracket, no chance of it being pinched now.
If the problem persists, the CR-Touch needs to be cleaned, perhaps with isopropyl alcohol, because the dust combined with the lubricant from the metal part may be preventing it from deploying, as the force of the part to move downward does not overcome the viscosity that has formed. Donāt forget to lubricate after cleaning.
Do you have a pic of that? It looks to me like it is fully captured. Thanks!
I shall get you one on Monday
Having a slightly similar issue here but oddly different at the same time. After letting the printer sit for awhile I booted it back up & started an auto level. Went to the center, probe touched the plate, then went to the origin & pritner emitted a long beep that only could be fixed by a manual shut off.
There is nothing on the screen error wise, I have sprayed some air at the probe & gently pulled the probe down, cables look intact. But cannot seem to understand what is wrong.
Well it turns out Iām not sure that is the issue. For the 2194 error I have taken everything apart and put it back together. Checked for bent pins and bad connections on everything even the 30 pin cable to the board and carriage and everything looks good. I still have the error but can click ok pull out the pin on the touch and it seems to work. I oiled the pin and it does not seem bent at all it moves very easily.
I saw the post about adding 8 volts but that is a magnetism issue and should only happen when it gets hot. My issue happens after sitting all night and trying to print so it shouldnāt be that hot.
My next move is to switch out the touch but I really donāt think thatās it.
Any suggestions?
Iāve had same problem and tried EVERYTHING!!
the plunger was binding and created some kind of vacuum. One small shim and 99% error free now for 2 monthsā¦
https://www.printables.com/model/1099261-fixed-cr-touch-error
Just try it
Seriously, I had to create an account here just to thank you for this AMAZING solution.
Iām waiting for Creality support to resolve or send me a CR Touch and so far I havenāt found any valid solution for the CR Touch to work on my Ender 3 V3 ke, when the pin decided to work the table wouldnāt level properly, when it was leveled the pin wouldnāt work, in short, total chaos. But thanks to you my dear friend, you helped me a lot and I really appreciate it!!! If you were from Brazil I would buy you a pizza. Thank you very much!
I had just upgraded to CrealityPrint_6.1.1.2274_Release and got the error. I went through all of the troubleshooting and even ordered a replacement CR Touch but something told me to undo the update and role back to the previous version of Creality Print and low and behold my Ender 3 KE is up and running again. Donāt know why and canāt explain it but thats was my solution.