Printer Model: Anycubic Chiron with a bunch of mods
MCU / Printerboard:Stock Trigorilla board flashed to klipper, Coprint KCM and Chromahead devices, Eddy
Host / SBC: Raspberry Pi3b+
klippy.log klippy(21).zip (3.0 MB)
Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
In September of this year, I installed a coprint 4 color setup on my Chiron and I’ve been having some weird issues and I don’t know the proper way to diagnose it. During some prints, the pi will lose all network connectivity, but it continues printing like nothing is wrong. It’s a small amount of prints, and it’s always at different times in the print. Some times it happens within 30 minutes of starting a print, other times it takes a few hours. But most of the time, it doesn’t happen. There’s been times where I’ve printed the same file 5 different times and it only loses the network during one of them. When this happens, I’m not able to ping or ssh into the pi. It’s also headless, so no monitor or input devices are connected to it either. I plan on redoing my printer area over the holidays, so I’ll try to get a screen connected to it.
I’ve been trying to get help in the Coprint discord channel, but the only things that have been pointed out is the high bytes retransmit and that I should try a different usb cable. I’ve gone through 5 different cables, all of them under 3 feet. The most recent cable is 15” long, shielded and has ferrite cores on each end of the cable. I even bought a different Pi3b+ thinking that was the issue, but the same issues persisted. I’ve redone the sd card a bunch of times with both 64 and 32 bit versions of bullseye. I always start with a fresh debian install then use kiauh to get everything installed. I’ve done it with both a desktop and nondesktop interface.
I’ve used the klippy log visualizer, but I don’t really understand what I’m looking at or know how to use that info to diagnose the issue. Could someone go over the klippy log file and give me some pointers as to what could be the cause. The main reason I want to get this fixed is so I can continue monitoring the prints when I’m at work and also with the ethernet and wifi both dropping, my knomi is basically useless when this happens.
The network connection from your Pi to your phone/PC is handled by the Linux OS running on your Pi not by Klipper (or moonraker).
It sounds like you’ve eliminated hardware issues by replacing the Pi.
It sounds like you’ve eliminated OS issues by reinstalling Debian.
Did the fresh install get a new SD card?
Have you considered an external wifi antenna?
Do your drop outs coincide with use of a microwave nearby?
I have tried 3 different cards. 2 16gb sandisk, then a 256gb samsung all bought new from Amazon.
I haven’t thought of trying an external antenna, mainly because the pi is also hardwired to the router and both the ethernet and wifi connections seem to drop at the same time. Also, the pi and the wifi router are in the same room about 25-30 feet away with nothing blocking a direct line of sight from pi to router. The pi is in a plastic 3d printed case, so it can’t be blocking the wifi signal.
It hasn’t dropped the connections when a microwave is running.
I’m thinking it has to be isolated to the coprint hardware, eddy, or accelerometer that I’ve installed. Prior to installing all that extra stuff, this issue never happened. I had somewhere around 2500 hours of print time in mainsail on the klipper build with just the printer and a webcam connected to the pi. In addition to all that, I was using a pi2b up until these issues started after the coprint hardware install. At that point, I flipped the klipper pi2b with my pi3b+ I was using as a nas and just swapped the cards between the two. Both still worked the same way in each instance. After that I bought a new pi3b+ thinking the old one might be going bad.
Both technically. When I access the mainsail interface from my computer or phone, I connect to the wired ethernet ip address, then the wifi ip address is generally only used for the Knomi.
I picked up a touch screen and connected it to the 3b+ to install klipperscreen and see what was happening when the network cut out. The pi acts like nothing is wrong with the network. The software shows that the ip address of the wifi and ethernet are active. I turned the wifi off and on, but it still pulled the same ip address(dhcp reservation on router). I even connected to the 5ghz network which I haven’t used on that pi yet and it connected, but wasn’t reachable from my network on that address.
I’m starting to think the Raspberry pi 3b+ wasn’t powerful enough for everything I had connected to it. I decided to bite the bullet and buy a pi 5 8gb board. After setting that up with everything in kiauh that was needed, then restoring my backups, I’ve been printing nonstop for about a week now with no disconnects.