Complete beginner

Wow, that's great! I ran free -m through SSH and got a swap of 511. I tried finding Octoprint on Pypi, but it only seems to go back to 1.3.

So, on the troubleshooting steps shown on that page:

If the issue persists, please log into your Raspberry Pi via SSH and check the following:

  • Verify that the process is running: ps -ef | grep -i octoprint | grep -i python should show a python process:

pi@octopi:~ $ ps -ef | grep -i octoprint | grep -i python
pi 1441 1 6 11:12 ? 00:00:15 /home/pi/oprint/bin/python
/home/pi/oprint/bin/octoprint --host=127.0.0.1 --port=5000

  • If it isn't, the question is why. Take a look into ~/.octoprint/logs/octoprint.log, there might be an error logged in there that helps to determine what's wrong.
  • You might also want to try if you can restart the server (if no obvious error is visible): sudo service octoprint restart.

If all that doesn't help to trouble shoot the issue, you can seek support on the OctoPrint Community Forum. Please provide your OctoPi and OctoPrint versions as well as your octoprint.log and explain what you already tried and observed as detailed as possible.

I tried the ps line and it just comes back to the prompt
I tried looking for logs (there's no log folder) and restarting the server, which just returns and the webpage still shows the same.

I'll see if I can create a working OctoPi / OctoPrint image for my RPi Zero W tomorrow and if I'm successful, I'll give you the steps I used.

Using the OctoPi 1.1.0 / OctoPrint 1.11.1 image results in the same failure you are experiencing. I'm going to try the OctoPi 1.0.0 / OctoPrint 1.11.0 (new camera stack) image next.

That image also failed. sudo service octoprint status shows:

pi@rpi0w:~ $ sudo service octoprint status
● octoprint.service - The snappy web interface for your 3D printer
     Loaded: loaded (/etc/systemd/system/octoprint.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Thu 2025-05-15 20:46:50 MDT; 1min 21s ago
    Process: 279 ExecStart=/home/pi/oprint/bin/octoprint serve --host=${HOST} --port=${PORT} (code=killed, signal=ILL)
   Main PID: 279 (code=killed, signal=ILL)
        CPU: 3.674s

May 15 20:46:30 rpi0w systemd[1]: Started The snappy web interface for your 3D printer.
May 15 20:46:50 rpi0w systemd[1]: octoprint.service: Main process exited, code=killed, status=4/ILL
May 15 20:46:50 rpi0w systemd[1]: octoprint.service: Failed with result 'signal'.
May 15 20:46:50 rpi0w systemd[1]: octoprint.service: Consumed 3.674s CPU time.

From what I've found, the signal=ILL is an illegal instruction.

But at least that got further. You got a response from the status request, even if it wasn't positive :smiley:

I'm not sure I'd call it progress. I didn't check the status with the first (bookworm) image, but I imagine it would be the same. The RPi Zero W is an ARMv6-compatible processor rev 7 (v6l). The RPi Zero 2 W is an ARMv7 Processor rev 4 (v7l) as are all the RPi models through the RPi 4.

Some package that OctoPrint uses is not armV6 compatible anymore. Given that the performance will be marginal at best, I don't believe it is worth trying to find a solution. My RPi Zero W is going back to being the host for a https://www.pishop.us/product/3d-rgb-xmas-tree-for-raspberry-pi/.

Hehe. Thanks for testing, Brad. It's much appreciated. Would a Pi Zero 2 be enough to drive my Creality CR6SE? I don't understand how it interfaces with the printer. I was told about OctoPrint by someone at Creality when I asked if an SD card with built-in wifi could be used, instead of having to copy files over.

A quick search of the internet says that the CR6SE can be controlled with OctoPrint and the Pi Zero 2 W is an acceptable system.

The RPi is connected to the printer via a USB cable. Gcode files are transferred from the slicer on the desktop host through OctoPrint's browser interface (via WiFi) and then sent one line at a time to the printer over USB.

As I said earlier, make sure the RPi power supply is at least 2.5a.

My Pi Zero 2 W finally arrived!

1 Like

So, it seems to be working inasmuch as the led on the Pi is solid green, but Octoprint said I needed to do a firmware update on the printer and now it heats the head up to 250Β°C and then shuts down and the UI is all in Chinese. Is the community firmware something to use?

Hi all,
I have OctoPrint working. My printer is using the community firmware. I haven't yet flashed the screen, so the info there is wrong, but I'm using firmware-20210327-155242. I haven't yet managed to print anything with OctoPrint, I use Cura to slice and send the GCode, but it seems to print with the filament being all wispy and not sticking to the bed. The nozzle looks red to me, and I'm sure it should be brass. I guess that's because it has red filament stuck to it? I tried scratching at it, but it won't come off. Do I need to change the nozzle and if so, how do I do it?

B

I see - https://youtu.be/Lma0XIVOFCU

When I plug the USB cable from my Pi to the printer, enough power goes through the cable that the screen blinks on and off, which can't be right. Also, I have flashed the motherboard to rev6.1 of the community firmware, and refactored 1.1 screen firmware. Everything should now be fine, but I get this message every time I try to level or load filament, which doesn't seem good.

Just in that moment?

The printer is switched off - the plug can even be out. The USB goes to the Pi for OctoPi, and that's on permanently.

And you wonder that nothing works?

No, I wonder why the screen stays on when the printer is like that. There is current coming from the USB port, but perhaps this video will make things clearer for you https://www.dropbox.com/scl/fi/x9xv8lc9xmq6l929dadwg/20250608-115304.mp4?rlkey=meen598x2u7dbxdpbsbgz6y7e&dl=0

You may look here: Put tape on the 5V pin - Why and how and here: Printers known to have backpowering issues

1 Like

Excellent! Thank you. My first attempt didn't work because I tried standard brown tape, which wasn't thick enough to block the voltage. My second go was with a "power" tape, much thicker and successful. I powered on the machine, and the Pi connected. I controlled the bed and head temps from the Pi and since I didn't want to try printing anything, turned off the printer. No flashing head light, no flashing screen

B

1 Like