Jump to content

Moonraker connection issues


SamppaD

Recommended Posts

 

Hi to everyone.This will be a long post hope that someone have some idea what can be done at this point... 
Still troubleshooting Moonraker strange disconnect issues. Moonraker will work and then just disconnect connection. 
When this happens its not possible to connect via ssh or web browser (timeout error) 
So after some detective work for hours i came to a conclusion. Lets see what community thinks. 

So what i did: replaced genuine sd Kingston high speed sd card for genuine samsung hi speed model,done a clean install of Klipper and its core components,maisail,moonraker,klipper screen,crownest,sonar,timelapse. Updated rpi software to latest..issue persisted after few prints.. 

RPi was powered via pin header, I suspected that this was reason behind slight voltage drop on rpi header removed that and make a thick AWG18 USB cable 
and set RPi psu to 5.2V..issue persist after few prints... 
During printing process lost chamber light...aborted the print and done extensive harness checks and measuring on all printer electronics. 
Found out that Octopus board controller was damaged due to PB6 port short. This board had already out of factory defective probe port so i had to use spare port to connect probe. 
I suspect as this board was used for 200 hours it must have had some other issues out of factory because no problem was found with harness. 

Well at this point i was thinking yes mainboard partially defective could be a reason for this issue... Swapped a new 429 octopus pro, flashed the mcu and everything was rocking for about few days of printing. So i was like hell yea issue solved..but yesterday out of the blue during print ,moonraker just disconnected connection and wouldn't reconnect on its own during print. Access to ssh not available,printer was printing normally for 13 hours. Klipper screen was responding fast in use exept for cancel object portion,that was slow.. 

So yea getting irritated about this issue so i decided to make a test rig/get as much of hardware and software possibilities out of the picture to try to troubleshoot this issue on another level.. I put a new setup brand new parts,raspberry pi4B 4gb,Kingston hi speed sd hard,genuine product from my local electronic shop. 

Clean install of Klipper,Moonraker,Mainsail,Kiuah. Only rpi4 in use,nothing connected to the board itself,no camera,octopus,klipper screen just Pi and its original power adapter in use,working via wlan. Make sure that i can connect to mainsail..OK,SSH..OK. Everything working fine at this point no moonraker disconect issues...

Run a full update on RPI..OK,updated Klipper and its core components to latest version and ssh in to pi..left this screen opened for a while. As suspected connection was lost after Klipper,mainsail was updated.  

So on one hand we have a Voron that suffer from moonraker issues running rpi4b v:1.2 at 1.5ghz all key components connected to the pi (octopus429,klipper screen,camera) and we have a bare test rig,new components,rpi4 v:1.2 running at 1.8ghz stock,connected to its own genuine usb c power supply,only software portion installed,nothing connected to the pi itselt,no usb devices,no screen,no mainboard and still we have the same issue with moonraker! 

I came to conclusion that this problem is somehow connected not to printers hardware but to software compatibility regarding,PI os and Klipper/maisail. This is making me crazy,waste of money,precious time and mental health to find out that its a compatibility issue with software that was supposed to be solid. 

After all we are using printers remotely  and this should work. One more thing about network manager,mine didn't work so i found klipper solution online https://forum-raspberrypi.de/forum/thread/57368-networkmanager-auf-raspian11-debian11-bullseye-am-terminal-einrichten-serial-ter/?l=2 ,that one worked to display networks but denied access permission,after rebot lost connection to login in to pi. Had to install everything again. So i don't recommend it. If it doesn't work and doesn't make any issues,don't fix it ;.)

 

Setup and printer is running with:

mcu(stm32f429xx)
Version: v0.13.0-373-g6465921a
Host(aarch64, 64bit)
Version: v0.13.0-375-gba79d72f
OS: Debian GNU/Linux 11 (bullseye)
Distro: MainsailOS 1.2.1 (bullseye)

Im out of ideas what to do with this issue,if i could get that network manager to work it might give me more information..

 

 

Edited by SamppaD
Link to comment
Share on other sites

Nice work, I learned to use the Samsung Endurance micro SD cards. That and I use EMMC memory which is much faster yet. The Manta M8P with CM4 4GB with 16GB EMMC memory. No more SD card in Raspberry pi. I do have displays that are Pi driven and the use Pi 5 with the endurance cards and a heat sink with fan to keep it cool. 

I put a heat sink fan on the CM4 as well. 

The board pictured is ready to be installed in an Ender 5 plus as I am converting it to a Core XY after I print a few more things for the Voron 2.4 R2.

20251102_091325[1].jpg

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...