k2 plus issues after FW 1.4.x.x

Flagship K Series Creality Flagship K2 Plus & CFS
1

has anyone had issues with the new FW 1.4.x.x and how did you resolve it. My k2 plus would do one print then crash on the next homing cycle. I had to roll back to 1.3xxx

3 Likes
2

I had some issues with the print head forgetting where it was and failing to home. That stopped prints from starting, but a power cycle immediately followed by a manual home command always fixes it for me.

3

I upgraded and got increasing numbers of system errors until it would not print - I tried following the wiki solutions - too hard, so I gave up and went back to 1.3.x.x

1 Like
4

IMHO, nothing wrong with 1.3.x.x i didn’t see a big improvement in 1.4.x.x. I thought about rolling back too, but decided the work around was easy enough for my needs.

5

what was the work around? Creality asked me factory default after the upgrade then try and i get the following error {“code”:“key60”, “msg”:“Internal error on command:BED_MESH_CALIBRATE”, “values”: [“BED_MESH_CALIBRATE”]}

6

Power cycle followed immediately by homing all axes in Fluidd as soon as it connects. Then everything would work normally for a few days.

7

thank you, i reverted to 1.1.3.X.. it works fine, i just didnt want to be on older FW

1 Like
8

This is more for the Dev’s than for us users:
I hit the problem again, but this time I was watching in Fluidd and got an interesting error:
”{“code”: “key353”, “msg”:“MCU ‘mcu’ shutdown: Stepper too far in past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.”, “values”: }”

Just a guess, but since I don’t get the error in Fluidd, but I do get it in Print, maybe Print is trying to do the initial calibration just a little too fast. OR, maybe I need to run a round of lubrication. :man_shrugging: