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

Get Help
2

Let's see if your pi detects the printer at all

Turn on your printer, then turn on the pi.
Log into your pi via ssh then disconnect your printer, connect it again, enter dmesg | tail -n 20 and post the output here.

If you need help with the ssh part


Scroll down and start with the Connecting to Your Raspberry Pi over SSH part.
The first part is already done for you in the octopi image.
1 Like
3

Thank you for your response, I’d like to follow the steps illustrated above.
You’re going to hate me for this, but for some reason I can’t see my Pi on the network to determine it’s IP address.
But I know it’s online, as I’ve connected to it through my browser. I did the entire setup wizard on the Octopi. I do have a monitor and keyboard I could hook up to the Pi, but I don’t think there is anything to display?

4

You can also connect to it's hostname - octopi :slight_smile:

One simple way to get the ip is to just ping the pi.
Open cmd or powershell and enter ping octopi

5

I was recommended to see if I could connect my printer to my computer and see if my slicer would see it. But I'm not seeing anything there either. So, now I'm down to either, Bad USB cable (tried 5 cables now), bad USB port on the Ender, or firmware update made the serial port non-functional.

6

I am having the same problem. Printed Weezl, my dmesg output below. Guess it is the USB connection. I tried another cable and no go.
Thanks!

pi@octopi:~ $ dmesg | tail -n 20
[ 10.490642] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 10.490654] brcmfmac: power management disabled
[ 10.980107] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 10.980122] 8021q: adding VLAN 0 to HW filter on device eth0
[ 14.471919] Under-voltage detected! (0x00050005)
[ 16.155107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 17.012500] Bluetooth: Core ver 2.22
[ 17.012600] NET: Registered protocol family 31
[ 17.012608] Bluetooth: HCI device and connection manager initialized
[ 17.012632] Bluetooth: HCI socket layer initialized
[ 17.012646] Bluetooth: L2CAP socket layer initialized
[ 17.012690] Bluetooth: SCO socket layer initialized
[ 17.036807] Bluetooth: HCI UART driver ver 2.3
[ 17.036823] Bluetooth: HCI UART protocol H4 registered
[ 17.036915] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 17.037137] Bluetooth: HCI UART protocol Broadcom registered
[ 17.424817] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.424825] Bluetooth: BNEP filters: protocol multicast
[ 17.424841] Bluetooth: BNEP socket layer initialized
[ 20.711820] Voltage normalised (0x00000000)

7

@stikako
I see. You could look inside the printers usb port (with a flashlight or something). Maybe there is a bent pin and you're able to bend it back.

@techydoc
the first thing I notice here is the undervoltage warning.
Make sure you're using a sufficient power supply and no phone charger.
I assume the printer is turned on and plugged in into your mains power.
Try this Put tape on the 5V pin - Why and how
When you're done with the tape mod unplug your pi and plug it in again. Sometimes the usb controller crashes and doesn't work again until the pi has been fully power cycled.

If that doesn't help try the same as @stikako - connect the printer to your pc and test if it works with something like pronterface .

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