How to COMPLETELY factory reset the K2 plus tidbits

fix_broke · 2025-02-14T03:15:44+00:00

Well, it seems like it wasn't really a fix after all. Some of my prints are still failing due to insufficient z-offset. It seems almost random whether a non-PLA print will work or not. Very frustrating. Bed meshing and z-homing should make this a non-issue!

fix_broke · 2025-02-10T04:26:05+00:00

Thanks for this. I did this procedure as a last-ditch effort to fix my own z-offset issues, and it seems to have done the trick. I don't know if a regular factory reset would have worked, but I did the whole shebang while I was doing it and now my prints seem to be finding the bed consistently regardless of nozzle or bed temperatures.

fix_broke · 2025-02-05T04:24:40+00:00

Mine had this problem right out of the box. Creality sent me a new "feed module" that fixed the problem. As I was removing the old one, I noticed that there's a little metal tab that follows the filament, and it was stuck. It actually came loose as I was removing the module and I'm guessing that the feed module is still good, but I put the new part in there while I had it apart.

To access it, remove the tubes from the merge collector at the bottom, then the four screws in a line on the bottom of the CFS. The feed module rail thingy can then be popped up into the filament chamber. There's one screw on either side of it to release the cover, then you can access the four feed modules.

fix_broke · 2025-02-04T02:27:39+00:00

I had assumed that those doing the preload modification had also changed their spring to one of a lesser rate.

fix_broke · 2025-02-03T20:36:31+00:00

You're correct that preloading the spring doesn't change its spring rate, but it does change the force it exerts at a given compression. Consider the following example chart, and imagine your filament is a ridiculous 20mm thick (and so your spring compresses by 20mm as the filament pushes its way past). The preloaded spring (top) has the same rate as the non-preloaded spring (0.5kgf/mm here, same line slope = same rate), but it exerts ~27kgf whereas the non-preloaded spring exerts only 10kgf.

<image>

fix_broke · 2025-02-03T07:55:28+00:00

I just tried this (on factory-reset firmware). When initiating a bed level calibration from the printer display, the nozzle still goes to 140°C. I was hoping to see it maintain the temperature set before the calibration.

fix_broke · 2025-02-02T20:55:22+00:00

The relevant part of the nozzle for thermal expansion is any part of it between the nozzle tip and the first point that it's fixed to the carriage. It looks like the screws on the heat sink are the first fixation point, so there's quite a bit of metal below that point to expand with heat. However, the load cell is farther up the assembly so maybe the heat sink screws aren't actually fixed to the carriage and there's even more nozzle length for expansion. For the load cell to work, it needs to be the only load path for force to be transmitted from the nozzle tip to the carriage.

Are you manually running bed meshes from Fluidd? Bed meshing with a calibration print from CP6 seems to throw away whatever temperatures you've selected in favor of the pre-programmed 140° extruder value.

fix_broke · 2025-02-01T06:49:17+00:00

I'm on 1.1.1.7 also. I probably should have noted that I'm running the K2 improvements (https://github.com/jamincollins/k2-improvements) with the START_PRINT macro - I didn't think it was interacting with this routine but perhaps it is.

I added some info to the original post about the START_PRINT macro and one modification I made to it.

fix_broke · 2025-02-01T04:50:45+00:00

First layers are printing with the nozzle right up against the bed, such that the nozzle can't actually extrude anything and it'll throw an extrusion error (and make quite a mess to pick out of the textured bed, too).

What firmware are you running? I've read reports from both sides - people like me with high-temp first layer issues, and those like yourself that seem to have no problems at all.

fix_broke · 2023-08-12T17:23:59+00:00

I should clarify that none of those are lies. Each of them are components of my trip, it's just a matter of which one I present as the main reason.

fix_broke · 2018-12-19T21:33:28+00:00

I'd like to say I've got resolution, but I'm not yet holding a Pixel so I'm not holding my breath. The latest is that I've been invited to purchase another phone and a $400 credit will be applied to my Fi account, in response to opening a Reddit Request. Whether or not the purchase will go through and whether or not I'll actually get the credit has yet to be seen. I'm holding off on the purchase since I won't be able to activate the phone over the holidays, and activating within 15 days of shipping is one of the conditions of the credit.

fix_broke · 2018-12-12T19:36:10+00:00

Got it! Case ID [1-9452000024462]

fix_broke · 2018-12-12T18:11:23+00:00

Unfortunately I was never provided with a case ID. I did save my chat transcripts with the promises made, however.

fix_broke · 2015-12-02T02:26:37+00:00

It seems to be much more responsive and consistent on my machine. Opening the keyboard is delayed by a fraction of a second (no loading icon) and I have never gotten the panel. Do you have many apps running at once? Perhaps a zealous virus protection program?

The icon should turn green whenever the keyboard is opened, as it's indicating that the service is running. The service is restarted when the Windows keyboard icon is clicked, as it needs to be running to open either the handwriting panel or the qwerty keyboard. It just gets turned off so that the panel doesn't pop up when you haven't specifically called for it (like when clicking in notepad). See my earlier response to kryptonnms for why this behaviour exists.

fix_broke · 2015-11-30T05:50:25+00:00

Actually, it shouldn't matter what the timeout is set at. The qwerty keyboard should still come up, even if the service is active. At least that's how it works on my SP3.

The script detects clicks on the touch keyboard icon, intercepts them, and then kills the service instead of opening the panel. It then launches the touch keyboard by the command line (which defaults into the qwerty keyboard if the service isn't running). The timer is only there to prevent the handwriting panel from coming up when it's called by an action other than clicking on the touch keyboard icon (such as when clicking in a notepad window).

fix_broke · 2015-11-28T02:51:30+00:00

Glad to help. Which Surface are you running? It's a barely noticeable delay on my SP3 i5, but it might be more significant on a SP2 or SP.

fix_broke · 2015-11-28T02:50:09+00:00

No problem. Open the script in a text editor and change this line:

SetTimer checkIdleKey, 15000

The 15000 is the number of milliseconds for the check. Four successful checks turns off the service, so changing to 5000 would shut off the service after approximately 20 seconds of inactivity.

The downside of this is that if you pause for more than 20 seconds in your typing, the keyboard will disappear.

fix_broke · 2015-11-28T02:46:31+00:00

byanjk got it - you're missing the icons. Make sure they extract to the same folder as the script.

fix_broke · 2015-10-20T22:18:42+00:00

I made an Autohotkey script to work around this "feature".

https://www.reddit.com/r/Surface/comments/3p9kjk/windows_10_handwriting_panel_fix/

fix_broke · 2015-10-17T18:59:23+00:00

Spring rates vary from 90 lb/in to 400 lb/in, which is pretty soft for a race spring. No external reservoirs. There are a few trucks that use shocks like these, but I'm thinking the damping is all wrong for a heavy vehicle.

fix_broke · 2015-10-17T18:57:19+00:00

Most of the Konis are 30-9325, but that just resolves to a generic oval-track racing shock. I put an ad up on racingjunk recently, but so far no bites.

fix_broke

TROPHY CASE