I've just purchased a Raspberry Pi and put an image of Octopi onto an

3D Printing
, , ,
1

I’ve just purchased a Raspberry Pi and put an image of Octopi onto an SD card and tried it out. After hooking it to a TV, keyboard, and network cable, I started it up and went through raspi-config, following the tutorial in adafruit. I set it up to boot into the Graphical desktop, but when it rebooted, after spitting out the normal words, it went to a black screen with a cursor blinking. I reimaged the SD card a few times and tried again, but nothing different. Something to note, I had a usb wifi adapter in the USB port and a keyboard in the other

So I reimaged it, removed the wifi adapter, connected network and power, waited for the lights blinking to stabilize. I tried to login to http://octopi.local, but nothing. I then looked on my router for a new DHCP lease, then typed that IP into my browser and successfully logged onto octoprint. I tried octopi.local again, and it said something like it couldn’t find 63.xxx.xxx.xxx or some wierd IP that was not in my DHCP range. Like the ones windows defaults to when it doesn’t find a dhcp server.

Any advice?

2

PSU too weak? You want a bare minimum 1amp legit output. The more the merrier.

3

Also try a different SD card.

4

The board boots up and I can run Octoprint fine as long as I find the right IP address. If the power was low, wouldn’t I get resets of some sort? What makes you mention the SD card possibly being bad?

5

Power use is managed in the Pi so usage will increase depending on what you’re doing. Ability to boot is no indicator of a solid power supply.

6

RE the SD card, call it a hunch.

7

Interesting, I’ll try grabbing the charger for my tablet. That sucker is rated at an amp. Thanks

8

The “graphical” desktop on the Pi is “light” , i.e. minimal. When you get to the black screen with the cursor, right click for a menu of options!

9

@Mark_Malmros ah, that would explain it. I didn’t have a mouse connected, I just keep making different keys. I guess I need to steal the mouse off my pc as well. I’ll try this later tonight. Larger power supply, keyboard and mouse. Thanks guys

10

@Christopher_Gaul what stinks is that I’m using a brand new Sandisk 2gb. It’s my only full sized SD. I’ll have to use a micro SD and an adapter. I’ll give it a shot if the other stuff doesn’t work. But isn’t having the wrong IP a DNS issue? Which would be in software, not hardware?

11

I think that your router is not able to give a ip to your Rasparerry. Check if your “DHCP Server” in your router is working properly.
your router ip most likely is something like http://192.168.1.1

12

@Frank_Opmeer Sorry, i explained poorly. The pi says that it is 192.168.1.112 while it’s spitting out all the text during boot up. In able to connect using that IP. When I try to connect via octopi.local, it timeouts, and mentions the weird 63 IP that’s not in my dhcp pool. That’s why I think it’s a DNS issue. The server runs fine, I just have to know its IP, which is difficult since I have dhcp. I can give it a static address, but that’s no fun

13

you could keep the dhcp on the pi, but instead set your router to always give the pi the same ip, so it would always be 192.168.1.112

14

+1 on the SD comments. I had one that wouldn’t run right no matter how many times I re-imaged the card, but after doing a low-level format (I used SDFormatter from Trendy and Panasonic, apparently) things are much better.

That said it doesn’t really explain the networking issues. I’m with @cato_hagen in that doing a DHCP reservation on your router is a good idea, or simply hard-code a static IP on the raspi itself just to eliminate those variables. Depending on your network configuration there’s a number of reasons things like DHCP and Bonjour (UPnP et al) won’t work right and going with a static IP will narrow that list of targest in a hurry.

15

My thought was that once the network card was initialized the extra power draw is making the system flakey and the NIC errors out on the DHCP request.

16

Yeah @Christopher_Gaul power is definately a common cause of issues with the Pi, and I agree a beefy ps is a good place to start tshooting as well.

17

So I have a 1A PSU, I reformatted the SD card, I installed all the things from that Howtogeek page and from http://elinux.org/RPi_Advanced_Setup. Which has me run a few more lines in my Rpi, and make changes to my firewall. No dice. I still can’t get the .local name to work. The server works fine using the local ip address. What odd, when I open the webpage of octoprint, when I click on any button or link in octoprint, the bottom of my browser say “waiting for octopi.local…”. It still says this when I reimage the SD card and just boot from scratch. When I ping in windows to octopi.local or anything.local it tries to ping 66.152.109.110 and gets no response (it’s not on my subnet. I tried pinging from my cell phone on wifi, no help either. UGH

18

“It’s not on my subnet”, are you saying the Pi and your PC are on differnent subnets? For the .local name to work you’ll need multicast to work between the Pi and the PC, so if there is routing going on, you’ll need to make sure you’re propagating multicast.

19

@Jason_Gullickson The weird 66.152.109.110 isn’t on my 192.168 subnet. After reading some posts I think you’re right about the multicast thing. But I followed all the instructions about opening the firewall to to UDP port 5353 and installing bonjour. No change. So like a good reprap hobbyist, I walked away from the thing for a while

20

@Jeff_Karpinski no VMware, only one nic. I also tried from my cell phone, which is actually a really good network trouble shooting tool.