Correct I have the same issue with this cable. No not direct to the board. I cut a regular MicroUSB cable in half and then reconnect it but without the +5v line connected. I guess you could just strip back the wire on the sheathing and cut the +5v line if you know which color it is but I confirmed the lines with a multimeter.
The best USB cable for connecting to a Creality printer is usually shielded with ferrite cores on each end and as short as possible. Putting tape on the 5V pin on the RPi end (USB A connector) is probably easier than cutting through the shielding to get to the actual wire.
Hmm. The one I'm using doesn't have the ferrite cores. I'll order one with those and give it a shot. Of course now i want it to fail it's not failing. Just cancelled the second print and trying again. 
So there is a success followed by a failure in the attached serial.log file. Are there any other logs you would like that could assist in troubleshooting?serial.zip (1.8 MB)
Comparing the successful probe and the failed probe:
2021-02-07 17:53:26,990 - Send: N10 G29*35
2021-02-07 17:55:50,324 - Recv: Bilinear Leveling Grid:
2021-02-07 17:55:50,337 - Recv: 0 1 2 3 4
2021-02-07 17:55:50,342 - Recv: 0 -0.232 -0.148 -0.067 +0.097 +0.273
2021-02-07 17:55:50,347 - Recv: 1 -0.218 -0.140 -0.043 +0.120 +0.299
2021-02-07 17:55:50,351 - Recv: 2 -0.226 -0.135 -0.045 +0.126 +0.291
2021-02-07 17:55:50,354 - Recv: 3 -0.280 -0.174 -0.058 +0.118 +0.289
2021-02-07 17:55:50,358 - Recv: 4 -0.277 -0.163 -0.060 +0.112 +0.286
2021-02-07 17:55:50,362 - Recv:
2021-02-07 17:55:50,365 - Recv: X:220.00 Y:220.00 Z:12.72 E:0.00 Count X:17600 Y:17600 Z:5272
2021-02-07 17:55:50,380 - Recv: ok
Success reported by firmware 144 seconds later.
2021-02-07 18:38:45,632 - Send: N10 G29*35
2021-02-07 18:40:36,219 - Recv: Error:Probing Failed
Failure reported by firmware 111 seconds later.
The failure is reported by the firmware. OctoPrint is just passing the failure on. The timeout values in OctoPrint are not effecting the outcome (i.e. the current values are sufficient).
I don't have (nor do I want) a Creality printer but this appears to be yet another issue with their firmware. Apparently, when printing from the SD card, the firmware seems to ignore errors and just keeps going.
A wild shot in the dark... Add an M420 S0 before the G29 in the start gcode.
1 Like
Thanks @b-morgan I'll give that a shot. So you think that those errors are also occurring when printing locally but it continues on. Wonder if there is a way of capturing that somehow. Maybe I should give klipper a try?
Thanks,
Fil
Flash vanilla Marlin firmware first, Klipper takes a lot more effort to setup (IMO, ready to get slaughtered by some klipper fan).
Unless the printer shows a message on the LCD then it is not possible to find more details, since there is nowhere for it to go.
2 Likes
Hi mates,
Here I send my serial.log but I thing it's exactly like the one of @Fil ....
@Charlie_Powell where do I get that firmware to test?
serial.log (41.5 KB)
Just in case @Charlie_Powell doesn't have a pointer in his back pocket, I did a google search for "creality ender 3 v2 firmware update" and found many links and videos that should answer that question.
1 Like
Yeah need to compile the base marlin for the ender 3 v2 with bltouch for it. Found a site where you can pay for the fw but haven't had the time to go through and compile it with the correct settings/options yet. If I get it working properly I'll post it somewhere.
Ok I will check that too.... Besides Smith3D I can only found another solution from th3dstudio.com, they provide a firmware for our printer but he way I see if changing the lcd firmware too.
Hi @Fil ,
I've done two things to try to fix the Probing Failed and until now I don't have any fail and I already have done lots of probing test through Octoprint...
1- I compiled myself the Marling with last version and with Smith3d menus (because the features they have);
2- I tightened the top screw of my BLtouch (half a turn in clockwise direction).
The firmware is ready for Ender 3 v2 with BLtouch v3.1
Try and give us feedback.
Thanks. Sounds promising I'll give it a shot. Didn't have the time this weekend to work on this.
Did you get this message?
Info: Firmware Development Build
Your printer's firmware is a development build. It might be more unstable than a release version and should be updated regularly.
Thanks,
Fil
1 Like
So completed one short print and on just kicking off a 3hr print and so far so good.
Excellent news! Give us feedback after some more tries.
About the message is because the Marlin is the last Nightly Built, in other words, is the last version plus everyday fixes they do so of course there's a possibility to have some type of bugs but maybe little things that will not be important for us... who knows...
Thanks
1 Like
I also tried your compiled firmware, and so far it works perfect. I like the extra info at the bottom of the LCD, nice touch.
1 Like
Cool, good to know.
That extra info comes already in this last Marlin build.
I will do some more tests and try to make the leveling a little more faster.
Btw I give more 1cm of possible bed using (23cm x 23cm) vs the 22cm x 22cm.
As I see it's possible to personalize the menus with GCODE macros (like Smith3D does) which is cool.
If anyone has ideas for useful things tell me... for now I'm using the menu's from Smith3D and I know the Marlin is open source but I don't know if Smith3D care about me using this part of their work
So far so good..have completed half a dozen prints with zero failures so I would say it was definitely something in the Smith3d firmware that was messed up.
1 Like
Cool... I've done some prints too using Octoprint and everythings works fine too.
I suspect of a option to use 5v in BLtouch. for BLtouch version 3.0 and 3.1 that option is a must to have to have better stability in the BLtouch... but as I'm saying is just a suspecion...
I will try to study a little more the Marlin and maybe create some useful functions in the menus but without mess with the firmware core.
1 Like