What's new
VORON Design

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members!

West3D Voron Community Store https://West3D.com

MCU Timeout on connect

I got to thinking that when I connected the TX/RX pins from SKR PICO to the Pi4B I also attached a GND pin. Looking at the other GPIO pins I saw another GND/5V pair going to the 5V PSU. That PSU shares a GND to the frame, as does the 24V PSU. The Umbilical PCB has +/- to the 24V PSU, but no GND to the Pi4B anymore since I removed the accelerometer hat. So I added a jumper GND connecting Pi4B and Umbilical. Testing again.
 
Nope. Still mcu timeout. Maybe I'll try removing the HDMI display next. I don't understand how it can print for 20, 40, 90 minutes and then crash. It is never the same amount of time.
 

Attachments

Last edited:
Three consecutive successful prints with the HDMI cable and Screen power cable unplugged.

Revisiting the display vendor's wiki it looks like I never added these three lines to my /boot/firmware/config.txt file.
Code: 
hdmi_group=2
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0

The display draws 400mA during normal operation which does not seem excessive. Continuing to test with the display re-enabled.
 
Last edited:
The intermittent shutdowns persisted. Exchanged the Pi4B for a Pi5. Monitored the syslog with

Code: 
sudo journalctl -f

Caught the failure live as it was chugging along catching Timelapse images. USB Disconnect is the culprit. I find it extremely unlikely for both USB 3 and USB 4 to disconnect simultaneously and then to reconnect 3 seconds later after Klipper has shutdown. What does that mean?
1. Power supply issue affecting both SKR Pico and Picobilical. They both are powered by the Mornsun 200W 24V power supply provided in the LDO V0.2-S1 kit.
2. A USB hub issue if both are connected to the same hub. But there is none. Both connect individually to the Pi5.
3. Pi5 USB controller issue. Brand new board. Pi5 has its own 25W 5V/5A dedicated power supply. The Klipperscreen is getting power from the Pi5 over USB and data over HDMI.

I think the previous tests (particularly the UART instead of USB) combine with this to suggest the Mornsun power supply has issues. New power supply is next. Why not.

I will unplug the HDMI and power from the 5" display and continue to test. If the elimination of the 400mA power draw from that display can help achieve successful prints I guess that wouldn't be so bad.

Code: 
Jun 29 16:40:39 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:40:39] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:40:39 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000227.jpg) successfully finished
Jun 29 16:40:42 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:40:42] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:40:42 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000228.jpg) successfully finished
Jun 29 16:40:46 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:40:46] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:40:46 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000229.jpg) successfully finished
Jun 29 16:40:50 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:40:50] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:40:50 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000230.jpg) successfully finished
Jun 29 16:40:54 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:40:54] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:40:54 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000231.jpg) successfully finished
Jun 29 16:40:57 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:40:57] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:40:57 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000232.jpg) successfully finished
Jun 29 16:41:00 voron kernel: usb 1-1: USB disconnect, device number 2
Jun 29 16:41:00 voron kernel: usb 3-1: USB disconnect, device number 2
Jun 29 16:41:01 voron spyglass[1067]: 127.0.0.1 - - [29/Jun/2025 16:41:01] "GET /snapshot HTTP/1.0" 200 -
Jun 29 16:41:01 voron python[1036]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000233.jpg) successfully finished
Jun 29 16:41:03 voron kernel: usb 3-1: new full-speed USB device number 3 using xhci-hcd
Jun 29 16:41:03 voron kernel: usb 1-1: new full-speed USB device number 4 using xhci-hcd
Jun 29 16:41:03 voron kernel: usb 3-1: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
Jun 29 16:41:03 voron kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 29 16:41:03 voron kernel: usb 3-1: Product: rp2040
Jun 29 16:41:03 voron kernel: usb 3-1: Manufacturer: Klipper
Jun 29 16:41:03 voron kernel: usb 3-1: SerialNumber: 4D4E383131102E55
Jun 29 16:41:03 voron kernel: usb 1-1: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
Jun 29 16:41:03 voron kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 29 16:41:03 voron kernel: usb 1-1: Product: rp2040
Jun 29 16:41:03 voron kernel: usb 1-1: Manufacturer: Klipper
Jun 29 16:41:03 voron kernel: usb 1-1: SerialNumber: 4550357127929EF8
Jun 29 16:41:03 voron kernel: cdc_acm 1-1:1.0: ttyACM2: USB ACM device
Jun 29 16:41:03 voron kernel: cdc_acm 3-1:1.0: ttyACM3: USB ACM device
Jun 29 16:41:03 voron mtp-probe[8268]: checking bus 1, device 4: "/sys/devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-1"
Jun 29 16:41:03 voron mtp-probe[8268]: bus: 1, device: 4 was not an MTP device
Jun 29 16:41:03 voron mtp-probe[8269]: checking bus 3, device 3: "/sys/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci-hcd.1/usb3/3-1"
Jun 29 16:41:03 voron mtp-probe[8269]: bus: 3, device: 3 was not an MTP device
Jun 29 16:41:03 voron mtp-probe[8276]: checking bus 1, device 4: "/sys/devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-1"
Jun 29 16:41:03 voron mtp-probe[8276]: bus: 1, device: 4 was not an MTP device
Jun 29 16:41:03 voron mtp-probe[8277]: checking bus 3, device 3: "/sys/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci-hcd.1/usb3/3-1"
Jun 29 16:41:03 voron mtp-probe[8277]: bus: 3, device: 3 was not an MTP device
Jun 29 16:41:04 voron python[1036]: [klippy_connection.py:_process_status_update()] - Klippy has shutdown
Jun 29 16:41:04 voron KlipperScreen-start.sh[1261]: 20250629 16:41:04,996 [printer.py:change_state] - Changing state from 'printing' to 'shutdown'
Jun 29 16:41:04 voron python[1036]: [proc_stats.py:_handle_shutdown()] -
Jun 29 16:41:04 voron python[1036]: Moonraker System Usage Statistics:
Jun 29 16:41:04 voron python[1036]: System Time: 1751240435.174464, Usage: 0.48%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240436.175125, Usage: 1.21%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240437.178254, Usage: 0.51%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240438.175131, Usage: 0.4%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240439.175391, Usage: 0.91%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240440.175478, Usage: 0.58%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240441.176621, Usage: 0.54%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240442.177899, Usage: 0.52%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240443.177903, Usage: 1.05%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240444.177714, Usage: 0.6%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240445.179167, Usage: 0.56%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240446.179306, Usage: 0.97%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240447.179505, Usage: 0.95%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240448.180228, Usage: 0.46%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240449.179912, Usage: 0.46%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240450.180127, Usage: 0.44%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240451.180405, Usage: 0.91%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240452.181119, Usage: 0.62%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240453.180627, Usage: 0.61%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240454.180973, Usage: 0.91%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240455.179230, Usage: 0.79%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240456.180821, Usage: 0.85%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240457.179976, Usage: 0.58%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240458.180853, Usage: 0.88%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240459.180515, Usage: 0.58%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240460.181015, Usage: 0.55%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240461.179914, Usage: 0.63%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240462.180345, Usage: 0.9%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240463.181686, Usage: 0.53%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: System Time: 1751240464.181306, Usage: 0.55%, Memory: 52012 kB
Jun 29 16:41:04 voron python[1036]: CPU Temperature: 45.75
Jun 29 16:41:04 voron python3[1039]: 2025-06-29 16:41:04 mobileraker.voron.sync INFO Klippy has reported a shutdown state
Jun 29 16:41:04 voron KlipperScreen-start.sh[1261]: 20250629 16:41:04,997 [printer.py:change_state] - Adding callback for state: shutdown
 
Last edited:
Even with the HDMI and Display power cables unplugged I cannot get through a complete print. I moved one USB A connector to a neighboring port this time for a trial too. Still failed. More evidence that it isn't insufficient power to the Pi5, but rather insufficient power to the SKR Pico and Picobilical. Klippy.log hasn't been letting me download the file lately. A new browser window pops open but no file is downloaded so I've just been going off the Pi5 log files. I can still use scp to transfer the klippy.log to my computer with "scp voron@192.168.196.190:~/printer_data/logs/klippy.log ~/Downloads/" but the Pi5 log is just easier to read and share.

Code: 
Jun 29 20:13:58 voron NetworkManager[777]: <info>  [1751253238.9109] dhcp4 (wlan0): state changed new lease, address=192.168.196.190
Jun 29 20:14:05 voron spyglass[995]: 127.0.0.1 - - [29/Jun/2025 20:14:05] "GET /snapshot HTTP/1.0" 200 -
Jun 29 20:14:05 voron python[963]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000190.jpg) successfully finished
Jun 29 20:14:19 voron spyglass[995]: 127.0.0.1 - - [29/Jun/2025 20:14:19] "GET /snapshot HTTP/1.0" 200 -
Jun 29 20:14:19 voron python[963]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000191.jpg) successfully finished
Jun 29 20:14:37 voron spyglass[995]: 127.0.0.1 - - [29/Jun/2025 20:14:37] "GET /snapshot HTTP/1.0" 200 -
Jun 29 20:14:37 voron python[963]: [shell_command.py:_check_proc_success()] - Command (wget http://localhost/webcam/snapshot -O /tmp/timelapse/printer/frame000192.jpg) successfully finished
Jun 29 20:14:57 voron kernel: usb 1-1: USB disconnect, device number 2
Jun 29 20:14:57 voron kernel: usb 3-2: USB disconnect, device number 2
Jun 29 20:15:00 voron kernel: usb 3-2: new full-speed USB device number 3 using xhci-hcd
Jun 29 20:15:00 voron kernel: usb 1-1: new full-speed USB device number 3 using xhci-hcd
Jun 29 20:15:00 voron kernel: usb 3-2: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
Jun 29 20:15:00 voron kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 29 20:15:00 voron kernel: usb 3-2: Product: rp2040
Jun 29 20:15:00 voron kernel: usb 3-2: Manufacturer: Klipper
Jun 29 20:15:00 voron kernel: usb 3-2: SerialNumber: 4D4E383131102E55
Jun 29 20:15:00 voron kernel: usb 1-1: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
Jun 29 20:15:00 voron kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 29 20:15:00 voron kernel: usb 1-1: Product: rp2040
Jun 29 20:15:00 voron kernel: usb 1-1: Manufacturer: Klipper
Jun 29 20:15:00 voron kernel: usb 1-1: SerialNumber: 4550357127929EF8
Jun 29 20:15:00 voron kernel: cdc_acm 1-1:1.0: ttyACM2: USB ACM device
Jun 29 20:15:00 voron kernel: cdc_acm 3-2:1.0: ttyACM3: USB ACM device
Jun 29 20:15:00 voron mtp-probe[3644]: checking bus 1, device 3: "/sys/devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-1"
Jun 29 20:15:00 voron mtp-probe[3644]: bus: 1, device: 3 was not an MTP device
Jun 29 20:15:00 voron mtp-probe[3645]: checking bus 3, device 3: "/sys/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci-hcd.1/usb3/3-2"
Jun 29 20:15:00 voron mtp-probe[3645]: bus: 3, device: 3 was not an MTP device
Jun 29 20:15:00 voron mtp-probe[3651]: checking bus 1, device 3: "/sys/devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-1"
Jun 29 20:15:00 voron mtp-probe[3651]: bus: 1, device: 3 was not an MTP device
Jun 29 20:15:00 voron mtp-probe[3652]: checking bus 3, device 3: "/sys/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci-hcd.1/usb3/3-2"
Jun 29 20:15:00 voron mtp-probe[3652]: bus: 3, device: 3 was not an MTP device
Jun 29 20:15:01 voron python[963]: [klippy_connection.py:_process_status_update()] - Klippy has shutdown
Jun 29 20:15:01 voron python3[967]: 2025-06-29 20:15:01 mobileraker.voron.sync INFO Klippy has reported a shutdown state
Jun 29 20:15:01 voron KlipperScreen-start.sh[1176]: 20250629 20:15:01,765 [printer.py:change_state] - Changing state from 'printing' to 'shutdown'
Jun 29 20:15:01 voron KlipperScreen-start.sh[1176]: 20250629 20:15:01,765 [printer.py:change_state] - Adding callback for state: shutdown
Jun 29 20:15:01 voron python[963]: [proc_stats.py:_handle_shutdown()] -
Jun 29 20:15:01 voron python[963]: Moonraker System Usage Statistics:
Jun 29 20:15:01 voron python[963]: System Time: 1751253272.262400, Usage: 0.59%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253273.265905, Usage: 0.59%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253274.266658, Usage: 0.61%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253275.266437, Usage: 0.51%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253276.266012, Usage: 0.49%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253277.266023, Usage: 0.8%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253278.266602, Usage: 0.87%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253279.266576, Usage: 0.51%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253280.267144, Usage: 0.52%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253281.266785, Usage: 0.55%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253282.266806, Usage: 0.47%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253283.266917, Usage: 0.47%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253284.266897, Usage: 0.51%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253285.266889, Usage: 0.45%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253286.267694, Usage: 0.51%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253287.267832, Usage: 0.97%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253288.267176, Usage: 0.49%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253289.266847, Usage: 0.53%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253290.267380, Usage: 0.48%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253291.267650, Usage: 0.52%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253292.268030, Usage: 0.49%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253293.268416, Usage: 0.56%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253294.268066, Usage: 0.62%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253295.268023, Usage: 0.58%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253296.268799, Usage: 0.58%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253297.268324, Usage: 1.04%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253298.268438, Usage: 0.62%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253299.269195, Usage: 0.59%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253300.268028, Usage: 0.62%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: System Time: 1751253301.268784, Usage: 0.67%, Memory: 52056 kB
Jun 29 20:15:01 voron python[963]: CPU Temperature: 38.05
Jun 29 20:15:01 voron KlipperScreen-start.sh[1176]: 20250629 20:15:01,767 [job_status.py:set_state] - Changing job_status state from 'printing' to 'paused'
Jun 29 20:15:01 voron python[963]: [proc_stats.py:_handle_shutdown()] - Throttled Flags:
Jun 29 20:15:01 voron python3[967]: 2025-06-29 20:15:01 mobileraker.voron INFO Fetched 1 app Cfgs!
 
Last edited:
I commented out this 60W limitation a while ago so that the bed would heat up quicker at full 100W. I am going to set the bed max_power to 0.6 of 100W and see how that goes for the next few days until the new power supply arrives.

Code: 
#####################################################################
#   Bed Heater
#####################################################################

[heater_bed]
heater_pin: gpio21
## Check what thermistor type you have. See https://www.klipper3d.org/Config_Reference.html#common-thermistors for common thermistor types.
## Use "Generic 3950" for Keenovo heaters
sensor_type: ATC Semitec 104NT-4-R025H42G
sensor_pin: gpio26
smooth_time: 3.0
max_power: 0.6                                                     # Only needed for 100w pads
min_temp: 0
max_temp: 120
#control: pid                                                        # Do PID calibration after initial checks
#pid_kp: 68.453
#pid_ki: 2.749
#pid_kd: 426.122
 
This could be the issue: Jun 29 20:15:01 voron python[963]: CPU Temperature: 38.05
See if you can put a fan or anything to cool it.
 
I removed the 200W Mornsun PSU and installed a 350W Meanwell PSU. I also attached a power meter between the wall and power cord so I could visualize the max power consumed. Peak of 168W observed with all fans, heaters, motors, displays, LEDs running. Three successful consecutive prints with no failures. Will continue testing for a week this way. If all goes well then I'll buy the properly sized 200W PSU in the Meanwell brand and toss the Mornsun in the trash. Since the Pi5 has its own 25W PSU, this means the Mornsun couldn't even give a stable supply of 168-25=143 W to the SKR Pico and Picobilical boards, which is lame. I wish there were better diagnostic tools to have pointed to this earlier. Learning curves everywhere.
 

Attachments

  • Power_meter_and_supply_compressed2.png
    Power_meter_and_supply_compressed2.png
    817.3 KB · Views: 3
Last edited:
You must log in or register to reply here.

Similar threads

F
Problems flashing SB2209 (RP2040)
Replies
0
Views
279
Feelflow
F
T
Cannot get klipper to connect
Replies
3
Views
2K
thespacecowboy
T
A
mcu unable to connect message
Replies
2
Views
334
AVC
A
D
Cannot connect to MCU : Octopus V1.1 + PI 4
Replies
3
Views
691
claudermilk
claudermilk
F
MCU unable to connect
Replies
0
Views
278
Foxy
F
Top