Motor Initialization Is Not Completed (?) - Head Unit Not Working

I seem to have lost my head unit/touchscreen thing as a control interface. I printed a 10 hour print Saturday night, and yesterday morning it had finished, but I then tried to print something else from the touch UI, and it doesn’t seem to respond. I’ve seen weirdness before where the touchscreen and the machine get out of sync, and I typically just reboot it. I turned it off, gave it 10 or so minutes, then turned it back on.

Now, it never really seems to load right. The network never connects, it says there is no camera, when I touch “home” it says “Motor Initialization is not complete”, and the temperatures never load.

It seems like the UI part isn’t interfacing with the part that handles the machine.

I can still access and control my machine mostly through FLUIDD, and it I can see the camera through Creality Print, but I can’t HOME it, see any temperatures, nor fans on.

The head unit no longer recognizes my CFS.

Its like 20 things all of a sudden went wrong. I’m fairly certain this is a situation where some service isn’t starting correctly, but I have no idea how to troubleshoot this.

The moonraker.log had an interesting error during initialisation.

2025-03-23 19:07:36,884 [moonraker.py:_initialize_component()] - Performing Component Post Init: [authorization] 2025-03-23 19:07:36,959 [extensions.py:start_unix_server()] - Creating Unix Domain Socket at ‘/mnt/UDISK/printer_data/comms/moonraker.sock’ 2025-03-23 19:07:36,963 [extensions.py:start_unix_server()] - Failed to create Unix Domain Socket: /mnt/UDISK/printer_data/comms/moonraker.sock Traceback (most recent call last): File “/usr/share/moonraker/components/extensions.py”, line 119, in start_unix_server self.uds_server = await asyncio.start_unix_server( File “/usr/lib/python3.9/asyncio/streams.py”, line 132, in start_unix_server File “/usr/lib/python3.9/asyncio/unix_events.py”, line 296, in create_unix_server FileNotFoundError: [Errno 2] No such file or directory

I created that folder through SSH (‘/mnt/UDISK/printer_data/comms/’), and that specific error went away, but the head unit still isn’t controlling the machine, and anytime I try to reset it I get “Filament detected in extruder. Please unload before factory reset.” There is no filament in the extruder, and I’ve replaced the detector for good reason.

Its like the machine can’t see any of its canbus attached components.

What should I try next?

Is there a way to just “hard reset” this machine to factory images/defaults?

The “reset to defaults” option doesn’t work because it says the filament detector is triggered, but I’m fairly certain that is because all the devices attached through the CAN bus (which includes the CFS and the extruder) aren’t being initialized correctly.

Open to all ideas.

Maybe this can help https://www.reddit.com/r/Creality_k2/comments/1ieylv9/how_to_completely_factory_reset_the_k2_plus/

See K2 Plus Factory Reset: USB Drive Method Guide | Creality Wiki