Hi, could you please move it to the appropriate section?
I didn't know where to put it?
General?
I already did. It's just Get Help.
Duhh, thanks!
1 Like
Additional information about your hardware (Hardware you are trying to connect to, hardware you are trying to connect from, router, access point, used operating systems, ...)
• Running Win10k, using octopi.local on Google Chrome web browser, nothing special
• Raspberry Pi 4 8Gb with OEM Raspberry power supply
• 128Gb Sundisk microSD (also tried 8Gb, 16Gb, 32Gb)
• Creality Ender 5 plus with Meanwell SE-600-24 power supply, Biqu116-A2 heatbed mosfet, OEM BLTouch v3, BTT S42B Closed loop driver, Marlin 2.0.7.1
Yessir, no problems whatsoever with pronterface
Both motherboards SKR1.4 and Creality board connect fine to pronterface
Have you tried to connect a HDMI TV/monitor and USB mouse and keyboard to the Pi to check if the USB works.
Yes, HDMI works, I’ll check the usb tomorrow with a mouse, but the creality board lights up when connected to the pi via USB
So, did you power the printer on?
Yes ofcourse, tried with and without power, all logical diagnostic steps, something screwy is going on
I was surprised when you said, that the printer display lights up when you connected the printer to the Pi's USB. It should be lit when the printer is powered on.
yeah, powerbus is working, I'm suspecting irq or port conflicts or something like that, but who knows
Have you already tried this: ?
Ah, so think there is a significant voltage drop due to drawn current by the printer motherboard causing hardware not recognising bus signal
Interesting, I'll try it
Sounds like you know what you're talking about, we just operate on 'it fixes many things, most of which are unexplained'...
No, I just break a lot of things 
1 Like
Well, that's disapointing...connected a keyboard via usb, rebooted, I think it's not being recognised? Or is it AMA0?
dmesg | grep -i usb
[ 0.151018] usbcore: registered new interface driver usbfs
[ 0.151421] usbcore: registered new interface driver hub
[ 0.151495] usbcore: registered new device driver usb
[ 0.151840] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 1.965227] usbcore: registered new interface driver r8152
[ 1.965313] usbcore: registered new interface driver lan78xx
[ 1.965380] usbcore: registered new interface driver smsc95xx
[ 1.966774] usbcore: registered new interface driver uas
[ 1.966838] usbcore: registered new interface driver usb-storage
[ 1.977098] usbcore: registered new interface driver usbhid
[ 1.977113] usbhid: USB HID core driver
[ 5.965729] usbcore: registered new interface driver brcmfmac
pi@octopi:~ $ dmesg | grep -i tty
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 smsc95xx.macaddr=DC:A6:32:98:61:C1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=f2e06639-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[ 0.001101] printk: console [tty1] enabled
[ 1.997219] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
[ 3.744340] systemd[1]: Created slice system-getty.slice.
I thank you for your help guys, hardware failure, not even 1 year old...
I'll see how and if I can return or fix this.
Octoprint rocks, one way or another, I'm fixing this. 
1 Like