Printer Model: Anycubic Kobra Neo - LEGACY
MCU / Printerboard: the TriGorrila one
Host / SBC
klippy.log (3.9 KB)
I have flashed the firmware correctly,but when I look for serial devices, there is none, even when I run lsusb. Is there any way to fix this?
Hello @windows12 !
Please upload your klippy.log file here, not on a file server. The system already marked your post as spam.
You do not have a printer.cfg.
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/printer_data/config/printer.cfg'
But for that, i cant find the serial port to put into the printer.cfg
It looks like your printer is not setup at all or at least not correctly. Follow a respective guide step by step, e.g.
For extended information and a ready printer.cfg file see GitHub - 1coderookie/Klipper4KobraGoNeo: Files for getting Klipper installed and running on the Anycubic Kobra Go & Neo
These are user contributed information for this type of printer, so YMMV.
How have you wired your serial port to your host (and what is it)? Diagrams and photos are helpful.
What sources of information are you using for the wiring - the documentation for the TriGorilla boards basically consists of what other people put up on forums and it’s not always right or specific to a certain version of the board.
Well, if the current state is No such file or directory: '/home/pi/printer_data/config/printer.cfg' then we have some steps to go before worrying about a potentially wrong wiring.
But for the printer.cfg to work, i need to know my serial port, which i cant find, and all the methods cant find it
I use USB.
Then I have to ask how do you know you flashed the Firmware correctly?
I typically turn on the Status LED on the board when I build my Firmware so that I can see that it is working correctly. If you don’t have an LED, then turn on a fan.
Use the “GPIO pins to set at micro-controller startup” option in make menuconfig.
I know because the LCd dosent work with klipper, so that the screen is off, firmware is flashed
I will try firmware firmware at:
THIS IS THE MCU SECTION I ALWAYS NEED WITH THE PRECOMPILED FIRMWARE!!!
[mcu]
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method: command
Uhmmm. No.
The only conclusion that you can draw from the LCD no longer working is that you changed the Firmware.
Sorry for coming in strongly but I think you need to go right back to the start.
First off, you need to exactly detail your hardware. This includes:
Once we have that, we’ll work through making sure your set up is correct.
@Sineos suggested that you read through Installing Klipper with KIAUH and that’s really good advice because it appears you’re trying to follow other people’s websites and Firmware builds and you’re not going to be successful following that approach. I was especially concerned with the link you passed with prebuilt firmware that is more than a year old.
Learning about Klipper, it’s architecture, how to build firmware and create configuration files is a bit of work but it’s not all that technical and it will serve you well over the course of time.
Let’s start with getting a complete understanding of your systems and what you’ve done and we’ll get things working for you.
First of all, thanks to @Sineos for linking to that GH repo, as that one is correct and offers working files for the Kobra Neo (I’m “1coderookie”, the maintainer).
@mykepredko I do appreciate that you’re worried, but in this specific case there’s no need to be concerned - yes, the bin-files are not up to date, but for that specific MCU nothing really changed and it’s totally safe to still use that v12 for example (I personally run v12 as well on my three Neos, nothing wrong with that).
However, I probably should either offer an up-to-date version or none at all, so thx for reminding me.
Either way, I’m also offering a comprehensive infosite specifically about the Kobra Neo where @windows12 also finds a specific chapter about Klipper for this machine, I also linked to it from that GH repo.
Since @windows12 might have overseen it, here you go: Klipper (MOD) - KobraGoNeo Insights → There one can find a list and a screenshot of the settings you have to use for creating an up-to-date bin-file yourself for that specific board.
As for your actual issue itself @windows12 :
Make sure to use this specific printer.cfg : Klipper4KobraGoNeo/cfg/NEO_1coderookie_printer.cfg at main · 1coderookie/Klipper4KobraGoNeo · GitHub
Rename it to printer.cfg and put it in /home/pi/printer_data/config/ of your Klipper host. If you’re not sure how to do so, please refer to the official Klipper doc.
Tipp: if you’re using Mainsail or Fluidd and have network access to the host, you can upload, create and/or edit files directly using the UI.
As for what you wrote here: that’s the serial id of the Neo being connected to the host. Like it’s the specific address of the printer which you need to find out, so you need to open a terminal on your host / SSH into your host and run ls /dev/serial/by-id/*
It’s being described here in the Klipper doc: Installation - Klipper documentation
Once you got that specific address of the printer, replace the one in the printer.cfg , save the changes and restart. See if everything connects and if so, continue with the configuration checks…
…just fyi: in this specific case with this printer model it’s actually really the case.
If you’re running the stock firmware of the Neo and flash Klipper, the lcd & control unit becomes unusable, so it’s actually a good indicator if flashing was successful, especially since the mSD reader of that printer is quite picky sometimes. (Assuming the person created/obtained a correct bin-file of course… 
)
Read what I wrote again - I’m stating that just because the LCD no longer works is not proof that Klipper Firmware is installed and running correctly which is why I suggested that you turn on an LED or a fan in make menuconfig.
Over the years, I’ve had many years of thinking a Flash update was successful or that my configuration was correct only to find a simple error. I’ve found this in building both Marlin and Klipper Firmwares.
The more I think about it, it seems that @windows12 posted an edited klippy.log and they haven’t explained what their host system is.
@windows12 could you confirm that what you posted was a complete klippy.log file and what your host system is?
I’m pushing for the host system because the process is fairly straightforward for a Raspberry Pi but gets messy with some other Single Board Computers (“SBC” when you first put in your request) and becomes very challenging when you’re using an old laptop with Mint on it.
@Catnippr , I’ve seen your page before and I reviewed it again last night before making my post and while it’s quite good, there is the implication in it that the user doesn’t have to look any further.
@Sineos suggested to @windows12 that they review the basic Klipper pages to learn about the Klipper ecosystem, how to install Klipper and what to expect. This is really good advice and I think that should be part of your page; you’re obviously experienced in setting up Anycubic products and understand Klipper but you’re not providing your users with the basic Klipper knowledge.
ThNK YOU, IF IT WORKS, i WILL MARK IT AS SOLUTION
Yeah… It’s an annoying bug but a good success indicator
