Failed to Load Crowsnest Extension

Basic Information:

Printer Model: Ender 3 S1 Pro
MCU / Printerboard: STM32F401
crowsnest(1).log (291.1 KB)
klippy(10).log (1.2 MB)
moonraker.log (10.1 KB)

I keep getting a Moonraker error message saying Failed to load extension Crowsnest. I’m thinking this is to do with setting up a camera, I do not have one currently but I may add one later. What do I need to do to correct this error? I’m running a Raspberry Pi 4 Model B - 8GB in case you need that info as well.

Thanks,
Veronica

Maybe a stupid question: Why do you install a service that depends on a webcam, when you do not have one?

Uninstall it: https://crowsnest.mainsail.xyz/setup/uninstall

1 Like

I installed it through a tutorial and at the time I didn’t realize I did install it, I’m really not sure how. I didn’t specifically search and install Crowsnest. I figured it was bundled somewhere in the tutorial I followed. I just noticed the error message and researched what it was and noticed it was for a webcam. I went by this tutorial below. How do I uninstall it, I wasn’t sure how? I could always download and install one when that time comes.

Thanks,
Veronica

Regardless of the software / system / whatever: My simple experience:

  • KISS → Only install things that you understand what they are doing. Start with a minimum configuration and get this running
  • Extend your config one at a time. Again, only with things that you understand what they are doing and that you actually need
  • If things start going wrong, then you need to debug only one addition or simply return to your known good base config
  • This advice holds especially true for the millions of Klipper macros floating around: You virtually need none of them to get a working printer. And if, you should understand what they are doing and why you need them.

(This is a free-of-charge, completely selfish advice to keep my own sanity: Many users go exactly the other way round)

4 Likes

KISS doesn’t seem to be the klipper philosophy. The premise appears to be throw a ton of code with every conceivable option and macro, and have users utilise the bits and pieces relevant to their circumstance. That has some advantages, but if anything needs modification for individual needs, then it becomse necessary to untangle significant pieces of code to get the required outcome.
As a non-software person, it’s quite daunting TBH…

KISS was more likely suggested here in terms of trouble shooting!
If there is an error reduce the used config to the minimum required to get it working and then step by step enhance the config until the error occurs again.

But even for such a sophisticated ecosystem like Klipper KISS can still be used as one can create big macros where a smaller one could perhaps achieve the same…

Under RRF you have to define and write everything as well as under Klipper. But both have much more capabilities compared to Marlin.
If you are not willing to learn how it is working you should not go the Klipper way…

Actually I read @3DPC post as a satiric contribution.

To be honest, my statement was meant for both configuring Klipper and troubleshooting.

In my perception, users create the complexity for themselves:

  • Configuration for a beeper that plays “Highway to Hell”
  • LED installations that put a dance club to shame
  • Time-lapse and camera configuration to create a Nextflix series with 7 seasons and 140 episodes
  • 800 lines of redefined LCD menu, while only using Mainsail or Fluidd
  • Other macros collected all over the www, likely without knowing what they do and why they should need it

Klipper offers many opportunities, but they are not required to get a printer up and running. My printers can mostly live with a print_start and print_end macro (and even they would not be needed and could be replaced by the “traditional” slicer gcodes)

Every common printer can be operated with a bare-metal cfg without any loss of quality whatsoever. And anyone who ever dug deeper into Marlin and compiled their own firmware, would never call Klipper complex. Not to mention the effort needed to sync the Configuration.h files between different Marlin evolutions.
Same goes for RRF. Although I consider it a very powerful firmware, I never got along with its cryptic configuration scheme.

2 Likes

There needs to be a 60 second Klipper introduction video to set expectations and introduce some basic concepts. I’m saying “video” because I don’t think most people today have the attention span to read the equivalent amount of text.

  • The most basic Klipper setup consists of:
    Host :arrow_forward: Controller :arrow_forward: Printer
    This is the set up that every user should start with
    Loading the Klipper software and connecting the components will probably take a new user an hour or two
  • The Host is a linux computer:
    A Raspberry Pi 4B being the device which works best as a host and easiest to set up the first time
    Other Raspberry Pis and Single Board Computers will probably work but may require a more complex set up and software installation process than the Raspberry Pi 4B
    Laptops can be used but will require a significant amount of software customization to act as a reliable Klipper host and are not recommended for new users
  • Klipper software is loaded onto the Host after the basic operating system is loaded and is connected to the Internet
    Along with Klipper, there are web based front ends that provide you with the ability control your printer remotely
    You can also add an LCD based user interface for local control
  • The Controller is a typical 3D printer controller board:
    Most 3D printer controller boards will work with Klipper
    For best results use a board with an STM32 MCU and a USB interface that will plug into the Raspberry Pi
  • The Controller Klipper firmware is generated by the Klipper Host
    The firmware is loaded onto the Controller in the same way other 3D printer firmwares are loaded onto the Controller
  • The Host has a file called printer.cfg that defines the IO pins and their functions of the 3D printer
    In the Host, Klipper has loaded in a number of example printer.cfg files for different printers and controller boards, chances are that you can use an existing one without modification
  • If you follow the instructions provided in klipper3d.org you should be printing with Klipper quickly and painlessly
    When starting out, we recommend that you stay to the basic process outlined here and only make changes to your 3D printer when you are confident in your understanding of the system and what the changes offer
1 Like