I can't connect to my printer even though it is connected via USB, this happened recently,

Get Help
1

I can't connect to my printer even though it is connected via USB, this happened recently,

2023-05-01 20:13:12,026 - Changing monitoring state from "Offline" to "Detecting serial connection"
2023-05-01 20:13:12,110 - Performing autodetection with 7 port/baudrate candidates: /dev/ttyS0@115200, /dev/ttyS0@250000, /dev/ttyS0@230400, /dev/ttyS0@57600, /dev/ttyS0@38400, /dev/ttyS0@19200, /dev/ttyS0@9600
2023-05-01 20:13:12,112 - Trying port /dev/ttyS0, baudrate 115200
2023-05-01 20:13:12,130 - Connecting to port /dev/ttyS0, baudrate 115200
2023-05-01 20:13:12,178 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:12,185 - Connected to: Serial<id=0x65802088, open=True>(port='/dev/ttyS0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2023-05-01 20:13:12,192 - Send: N0 M110 N0*125
2023-05-01 20:13:14,217 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:14,253 - Send: N0 M110 N0*125
2023-05-01 20:13:16,283 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:16,317 - Send: N0 M110 N0*125
2023-05-01 20:13:18,330 - Trying port /dev/ttyS0, baudrate 250000
2023-05-01 20:13:18,332 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:18,348 - Send: N0 M110 N0*125
2023-05-01 20:13:20,359 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:20,375 - Send: N0 M110 N0*125
2023-05-01 20:13:22,385 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:22,402 - Send: N0 M110 N0*125
2023-05-01 20:13:24,411 - Trying port /dev/ttyS0, baudrate 230400
2023-05-01 20:13:24,413 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:24,427 - Send: N0 M110 N0*125
2023-05-01 20:13:26,437 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:26,449 - Send: N0 M110 N0*125
2023-05-01 20:13:28,459 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:28,473 - Send: N0 M110 N0*125
2023-05-01 20:13:30,485 - Trying port /dev/ttyS0, baudrate 57600
2023-05-01 20:13:30,487 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:30,506 - Send: N0 M110 N0*125
2023-05-01 20:13:30,511 - Recv:  „ð „ð „ð „°"ÿ „ð „ð „ð „0 þ „ð „ð „ð „°"ÿa  þa  †`àa  þa  †`
€a  þa  †`à(` (` (` (@ (` (` (` (` (@  ü þ þ þ ¾
2023-05-01 20:13:30,514 - WARNThe received line contains at least one null byte character at position 0, this hints at some data corruption going on
2023-05-01 20:13:32,532 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:32,544 - Send: N0 M110 N0*125
2023-05-01 20:13:34,556 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:34,570 - Send: N0 M110 N0*125
2023-05-01 20:13:34,578 - Recv:  þ þ þ þ þ ~ þ þ þ þ þ þ ¾
2023-05-01 20:13:34,580 - WARNThe received line contains at least one null byte character at position 0, this hints at some data corruption going on
2023-05-01 20:13:36,594 - Trying port /dev/ttyS0, baudrate 38400
2023-05-01 20:13:36,596 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:36,618 - Send: N0 M110 N0*125
2023-05-01 20:13:38,630 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:38,648 - Send: N0 M110 N0*125
2023-05-01 20:13:40,659 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:40,672 - Send: N0 M110 N0*125
2023-05-01 20:13:42,685 - Trying port /dev/ttyS0, baudrate 19200
2023-05-01 20:13:42,687 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:42,705 - Send: N0 M110 N0*125
2023-05-01 20:13:44,701 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:44,714 - Send: N0 M110 N0*125
2023-05-01 20:13:46,714 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:46,725 - Send: N0 M110 N0*125
2023-05-01 20:13:48,726 - Trying port /dev/ttyS0, baudrate 9600
2023-05-01 20:13:48,727 - Handshake attempt #1 with timeout 2.0s
2023-05-01 20:13:48,744 - Send: N0 M110 N0*125
2023-05-01 20:13:50,741 - Handshake attempt #2 with timeout 2.0s
2023-05-01 20:13:50,758 - Send: N0 M110 N0*125
2023-05-01 20:13:52,757 - Handshake attempt #3 with timeout 2.0s
2023-05-01 20:13:52,770 - Send: N0 M110 N0*125
2023-05-01 20:13:54,769 - Changing monitoring state from "Detecting serial connection" to "Error"
2023-05-01 20:13:54,815 - Changing monitoring state from "Error" to "Offline after error"
2023-05-01 20:13:54,855 - Connection closed, closing down monitor
2

Have you tried different USB cables?

Also, what printer are you using?

Can you also share the systeminfo bundle?

3

It seems to be ok, I used tape to shield the 5V pin of the USB to prevent the Raspberry Pi from saying that it is undervoltage. Unable to connect to printer.

4

But have you actually tried using a different USB cable?

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.