New Install - Can't connect To Printer - HELP!

Get Help
8

I saw the voltage warning to. I was using the power supply from the kit. Just checke it is 0.5A!!. Ordered a new 2.5A supply. Also ordered a new USB cable.

The printer was on. I tried to connect the printer to my laptop and see if I could see a USB device, could not see any. I will look at the pronterface site. I will try the other items you suggested. Thanks!

9

OK, so on my Mac in terminal, I've tried just typing the command "ping octopi". and all I get is this:
ping: cannot resolve octopi: Unknown host
But, on octopi.local, I can turn off my Rpi, reboot it, etc. So I'm clearly connected to it.

10

Bad cable was my problem.

2 Likes
11

stikako, instead of using ping, open terminal and type: ssh pi@octopi.local

If you are asked to accept a key, then you are connected. type yes. When asked for a password, enter: raspberry

12

What was the difference in the cable?
Iā€™ve tried 5 cables. Nothing worked.
I went to the store to pick up a new cable that states it transfers data. But canā€™t return it if I open it. (COVID). It was inexpensive, but I have many of these cables, so donā€™t need an extra.
I donā€™t know how the 5 cables I have are inadequate, but Iā€™m out of options.
I should be getting a second printer sometime this week (fingers crossed), and I should be able to narrow down what the problem is just by setting up another identical printer on original firmware.
If it works, itā€™s either port or firmware. Then Iā€™ll update firmware. Works, itā€™s my port. Doesnā€™t, itā€™s firmware. If it doesnā€™t work right off the bat, then itā€™s most likely cable, or some sort of configuration thatā€™s required on the printer to access it.

13

Weird to have 5 cables that are faulty, seems like it is not a cable issue.

The cable I purchased: https://www.digikey.com/product-detail/en/102-1492-BL-F0050/1175-1808-ND/6005091

14

Maybe I've overseen it, but to what printer do you want to connect?

15

Should be clear. This was for the Ender 3 v2

16

It was the cable!

FIX: Bought a ā€œdata transferableā€ cable. Worked right away.

Thank you for your help!

17

Thank you as well for all your troubleshooting and help!
Still canā€™t see my Pi on the network and donā€™t know what itā€™s IP address is, but I bought a new cable, and itā€™s working!
Well on my way to success!

18

You may connect a HDMI monitor/TV to the Pi.
At the end of the startup sequence the current IP address is displayed.

19

I seem to be in nearly the exact same situation here ...

pi@octopi:~ $ dmesg | tail -n 20
[   12.629033] brcmfmac: power management disabled
[   13.299804] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   13.299817] 8021q: adding VLAN 0 to HW filter on device eth0
[   19.077415] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   19.105101] Bluetooth: Core ver 2.22
[   19.105163] NET: Registered protocol family 31
[   19.105166] Bluetooth: HCI device and connection manager initialized
[   19.105182] Bluetooth: HCI socket layer initialized
[   19.105188] Bluetooth: L2CAP socket layer initialized
[   19.105209] Bluetooth: SCO socket layer initialized
[   19.686320] Bluetooth: HCI UART driver ver 2.3
[   19.686329] Bluetooth: HCI UART protocol H4 registered
[   19.686374] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   19.686491] Bluetooth: HCI UART protocol Broadcom registered
[   24.365811] EXT4-fs (mmcblk0p2): resized to 3670016 blocks
[   24.743102] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   24.743111] Bluetooth: BNEP filters: protocol multicast
[   24.743133] Bluetooth: BNEP socket layer initialized
[   35.002792] EXT4-fs (mmcblk0p2): resized to 6291456 blocks
[   42.954771] EXT4-fs (mmcblk0p2): resized filesystem to 7748608

Any thoughts on this, @PrintedWeezl?

20

Unfortunately I can only give you the same answers - sorry
Try another usb cable and look inside the printers usb port and check for a bent pin

21

Thanks for taking the time to respond :smile:

1 Like
22

Yes! it was the cable for me. IAnd after finding one that worked, and connecting successfully, the output of the tail command looked like this:

pi@octopi:~ $ dmesg | tail -n 20
[ 15.038242] Bluetooth: HCI socket layer initialized
[ 15.038257] Bluetooth: L2CAP socket layer initialized
[ 15.038300] Bluetooth: SCO socket layer initialized
[ 15.053041] Bluetooth: HCI UART driver ver 2.3
[ 15.053057] Bluetooth: HCI UART protocol H4 registered
[ 15.053140] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 15.053365] Bluetooth: HCI UART protocol Broadcom registered
[ 15.228896] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.228903] Bluetooth: BNEP filters: protocol multicast
[ 15.228913] Bluetooth: BNEP socket layer initialized
[ 558.511436] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd
[ 558.647514] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 558.647530] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 558.647544] usb 1-1.2: Product: USB Serial
[ 558.742754] usbcore: registered new interface driver usbserial_generic
[ 558.742817] usbserial: USB Serial support registered for generic
[ 558.745519] usbcore: registered new interface driver ch341
[ 558.745602] usbserial: USB Serial support registered for ch341-uart
[ 558.745684] ch341 1-1.2:1.0: ch341-uart converter detected
[ 558.748887] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

23

What cable did you use? I am wondering if that is my problem right now.

24

Please do not reactive old threads.

To your question:

USB cables come in loading cables with only power wires and proper data cables and can not distinguished.
Data cables usually are thicker and the better ones have ferrites at the ends.
You may have to test some.

1 Like
25

Agree. I just tried a different, better one. And it worked. So test some

26

Have you verified that the RPI port works by connecting some other USB device to it?

27

Seems like a different cable solved the problem :slight_smile: