Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Octoprint requires Raspbian Jessie based distro to work with Raspberry Pi 3 #207

Closed
alex-gibson opened this Issue Feb 29, 2016 · 107 comments

Comments

Projects
None yet
@alex-gibson
Copy link

alex-gibson commented Feb 29, 2016

I have been testing ahead of the launch today, and noticed that the standard OctoPi distro gives rainbow screen of death on the Pi 3, and I could not follow the instructions (due to errors) to install for Jessie, using latest NOOBS distro as at last night.

For hassle free OctoPrint on the Pi 3 I recommend starting with the latest Jessie nightly build, which worked well enough that I demo'd it at the Pi 3 launch party today :)

Happy to contribute testing to get a stable Jessie/Pi3 build!!!

@taxilian

This comment has been minimized.

Copy link

taxilian commented Mar 5, 2016

I just ran into this as well; I appreciate knowing that I'm not the only one, and I'll proceed following those instructions =]

@nophead

This comment has been minimized.

Copy link

nophead commented Mar 5, 2016

I have OctoPrint running on a RPi3 by installing latest NOOBS and then following the OctoPrint install instructions for Linux. Tedious but they work and they also work on Ubuntu on an Orange Pi.

@gammy

This comment has been minimized.

Copy link

gammy commented Mar 5, 2016

I installed Raspbian Jessie Lite (2016-02-26), but did so manually rather than via NOOBS. I then followed the OctoPrint installation instructions, except that I checked out v1.2.9(the latest stable version as of writing) rather than using the master. Tedious indeed @nophead! It all works though, including optional dependencies such as mjpg-streamer and cura-engine.

@nophead

This comment has been minimized.

Copy link

nophead commented Mar 6, 2016

What it needs is an OctoPrint install script that runs on any Linux and does what the Linux instructions specify. Then you don't really need OctoPi.

@guysoft

This comment has been minimized.

@pmbdk

This comment has been minimized.

Copy link

pmbdk commented Mar 6, 2016

The latest nightly build works fine with RPi3 (although I havn't actually tried printing with it yet)

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

I have also installed a nightly build (2016-03-02_2016-02-26-octopi-jessie-lite-0.13.0.zip) on RPi 3. The Pi freezes half way through a print.

@seefood

This comment has been minimized.

Copy link

seefood commented Mar 6, 2016

Wow, people got their RP3 quickly :-)
Now @guysoft only needs to take care of a Pine64 version and.... Hey, isn't it time to just create a PPA? :)

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 6, 2016

The Pi freezes half way through a print.

I've run into a similar issue with the Pi3 I just got, mine just sat idly though and suddenly stopped responding altogether, several times. On first look it seems to be power related, switched to a different PSU, haven't been able to reproduce the issue since then (still observing it though).

Since the Pi3 does consume more power than the Pi2, it might be that one simply can't get away with the same power supplies anymore as was still possible with Pi1/Pi2. Just an idea though. I certainly never had a Pi2 just freeze on me with that PSU while doing basically nothing.

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

I don't believe that it's a power issue in my case as mine PPi is connected to a ATX PSU which can deliver 25A on a 5V rail.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 6, 2016

After it just happened again, I have to agree, doesn't seem to be power related.

I also have to correct myself, it apparently doesn't freeze completely after all, it just looses wifi connectivity. Funny thing is, it believes it still does have connectivity, has an IP and everything, but cannot be pinged or SSH'd into. Until I ping the router from the Pi3, then suddenly connectivity is back:

$ ping -t 192.168.1.204

Pinging 192.168.1.204 with 32 bytes of data:
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.204: bytes=32 time=2030ms TTL=64

Happens very reproducibly after some idle time. Maybe some power safe feature of the wifi chipset that's misbehaving (like it also happens with some dongles out there)?

@A-Nesh did it really freeze for you during printing (print stopped) or could it be that just the network connection broke down (print didn't stop, but anything relying on network didn't work anymore, so OctoPrint, SSH, ...).

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

@foosel my printer just stopped printing, after some printing (an hour or so). The extruder and the heated bed was still on. It happened two times today. I don't know if the whole Pi freeze or not but it was not accessible either by HTTP or SSH. I'll check it next time it misbehave.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 6, 2016

If it even stopped printing, that sounds like a different issue then. We are running the same image, so if it's an image issue, I should hopefully see it too during my tests.

From what you describe it indeed sounds like the whole Pi crashes completely. Do you have a chance to attach a monitor to it? That might show what's happening when it goes down. Also of interest would be your /var/log/syslog and you dmesg, maybe something got logged there when it went down.

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

i have now encountered same issue as you @foosel. It did not stop printing but the network died. I'll connect a monitor next time it happens.

Here are my syslog and dmesg:
dmesg.txt
syslog.txt

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

It died again now, after 77%

PING 192.178.1.88 (192.178.1.88): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

I have connected a monitor to the RPi, there is no signal = the RPi is dead

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 6, 2016

I asked in the G+ community if people were seeing this too with OctoPi and the RPi3. So far no definitive answer, but a good question:

If they're running an ATX PSU have they got any dummy load resistors to flatten out the power? I too thought it'd be no problem but noticed under load my ATX was dropping to 4 volts. Added a dummy load and it stabilized the output.

and some good advice I have to agree with:

Check your power supply. Try it without the printer turned on and see if stays up. Try with a separate 5V power supply and running a print. More troubleshooting is needed.

Try a different memory card?

Regarding the wifi going down, that's definitely caused by power management. I disabled it via /boot/octopi-network by adding wireless-power off to my wlan0 config, right after the SSID/PSK combo (basically as described here) and since doing that I couldn't reproduce the "un-ping-able" issue any more. Removed the line again and bam, issue returned. So something appears to be broken with the power management of the Pi3's own wifi.

I've seen older RPis freezing (exact same symptoms you are observing) due to issues with the wired interface, power supply issues (especially when under load), USB devices drawing too much power (which is why I prefer to have a powered hub between my Pi's and their peripherals), etc etc.

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

ok, thanx. Ill try a separate power adapter and report later

@nophead

This comment has been minimized.

Copy link

nophead commented Mar 6, 2016

If you are using an ATX PSU it is much better to use the 5V standby power
rather than the main 5V. It is actually a separate power supply so isn't
affected by the loads on the other outputs and you can also then use the
RPi to control the other half of the PSU.

On 6 March 2016 at 17:41, A-Nesh notifications@github.com wrote:

ok, thanx. Ill try a separate power adapter and report later


Reply to this email directly or view it on GitHub
#207 (comment).

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 6, 2016

Have tried both 5v standby and ordinary 5v rails with no luck. I also believe that it is a power issue. I have connected usb power monitor and can see that there almost no current consumption when the printer is on. Which means that the power must come from the printer to RPi via USB. I use geeetech gt2650 board. It was never issue with OctoPi on mi Raspberry Pi 1.

@nophead

This comment has been minimized.

Copy link

nophead commented Mar 6, 2016

Power should only flow from host to device on a USB cable. If device power is powering the host it is faulty. It wouldn't surprise me from Geeetech.

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 7, 2016

I have left the Pi over night connected to a 3A USB power supply and it was dead this morning. I have connected a monitor and as it was not responding i have restarted the Pi. A couple minutes later, i have found the issue. I am new to linux but it looks to me like file system error.

skarmavbild 2016-03-07 kl 08 46 50

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 7, 2016

That looks like a kernel panic. Download /var/log/syslog (eg via Womack), upload it somewhere (Dropbox or similar), share the link here.

The full log output of the kernel panic might tell us what's up, if it's a hardware issue, a flash gone wrong etc.

Just for the record, my pi3 has been up now since my last post yesterday without issues, using the same image and the above mentioned change to disable the Wi-Fi power management.

@taxilian

This comment has been minimized.

Copy link

taxilian commented Mar 7, 2016

Just as a datapoint, I installed using the raspbian image and then followed the octoprint install instructions and have been printing back to back jobs since Friday night with no issues.

Have not used Wi-Fi our changed any other settings.

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 7, 2016

@foosel here is my syslog
syslog.txt

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 7, 2016

@taxilian actually it worked fine for me to when i installed latest Jessie and manually installed OctoPi. I don't know why did i install a nightly build instead when everything worked fine.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 7, 2016

@A-Nesh because giving us early feedback on how the nightlies perform is the only way to root out issues before release, and you knew that and wanted to help? ;)

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 7, 2016

@foosel yes, it's was pretty much my plan :)

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 7, 2016

@A-Nesh I took a look into your syslog. Seems like the issue you made a picture of above didn't make it into the log :/ But there are a LOT of errors with the wifi interface, including some traces while trying to get an IP via dhcp. Have you tried disabling WiFi power management as described above? It's just a complete shot in the dark... if that doesn't help, I'd suggest reflashing/another SD card, to rule out issues with the flash and the card.

Can't help myself, I don't have the feeling that their drivers are all "there" yet, the raspberry forums are also quite full with "doesn't work" posts in the wifi thread at the moment.

Might also be interesting to see if they maybe did things differently between the lite and the full raspbian image. OctoPi uses the lite image.

@A-Nesh

This comment has been minimized.

Copy link

A-Nesh commented Mar 7, 2016

@foosel Yes, i also notice a DHCP attempt today. It still connects to the manual IP (.88). My DHCP range is .100 an up. I also took a look in the syslog and couldn't find the error message. Maybe it died died before it could write the log.

I have used the full Jessie image earlier. I will try to to flash a new nightly image to a new SD card, as soon i find it. :) just to eliminate sd card issue

I didn't have a chance yet to disable wifi power management, i'll do it first now.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 29, 2016

The Jessie Lite base image doesn't have X included, and considering how much bloat that whole desktop cruft adds without being needed for the actual usage scenario that's a very very good thing.

If you DO have a desktop locally, I don't think Octoprint is designed
to run and display on an OctoPi. (I guess this means they didn't test it
or the proxy doesn't like it? I'm clueless.)

"They" did and it works just fine but "they" do NOT recommend it (and in fact strongly discourage it) since running a full desktop environment with CPU and memory hogging components including a software rendering browser next to a critical real-time job such as feeding a file to a 3d printer is a recipe for tears. OctoPrint is designed to be accessed from a different computer than the one it's running on for a reason, which means a lot of resource hungry things happen on the client to keep load off the backend. If you run both on the same device, you throw away all advantages.

And now surely people will swoop in again and tell me "oh, but I run it just fine, the four cores are plenty and I NEVER saw any bad consequences by running my full blown desktop environment on my Pi and accessing OctoPrint through that while printing a 20 hour print job with lots of curves, you are wrong!" - and I can just say, YMMV, but I wouldn't risk it.

Experience has shown that people will run way too much stuff next to OctoPrint on even a single core pi (ideally with an insufficient PSU for extra party) and then complain that it's Octo's fault their prints fail, so being able to build upon on a way less bloated base image that doesn't contain that particular risk in the first place has many advantages (download size being one of them btw, that stuff costs money...).

And if people desperately need X against all recommendations:

$ sudo ~pi/scripts/install-desktop
@nicolinux

This comment has been minimized.

Copy link

nicolinux commented Mar 29, 2016

You should add "server" next to OctoPrint's name so people won't get the wrong idea.
One does not run servers with X, except you really need it for the server's task, which for OctoPrint is not the case.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 29, 2016

Wouldn't help ;)

@3driffs

This comment has been minimized.

Copy link

3driffs commented Mar 29, 2016

Well, the stable build has both X and a browser as part of it, so if it's not supposed to be there, someone made a mistake in that drop. I have a keyboard/monitor/mouse in the workroom with the printer, so I can operate it directly without fighting with the tiny LCD screen on the printer itself.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 29, 2016

The stable build is based on Raspbian Wheezy, where no lite version without all the clutter they added (like Minecraft and whatnot, on top of X) was available. With 1.5GB base size.

The nightlies are based on Raspbian Jessie Lite.

@3driffs

This comment has been minimized.

Copy link

3driffs commented Mar 29, 2016

So going forward, no built-in GUI capability. Bummer - that's a big loss of functionality for me. Guess I'll have to dust off my linux skills and build my own platform, or run two different Pi's. Hmmm...that's an idea.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Mar 29, 2016

Or just install an X server? You know, via the existing package system? Or actually even something as simple as this (and yes, that is already included in the current 0.13 builds):

And if people desperately need X against all recommendations:

$ sudo ~pi/scripts/install-desktop

That means you'll have to wait a bit while it downloads a bunch of packets that are not needed for the core use case, but that's a one time thing.

And that you download these packets only if you need them instead of having them included in the image saves us time on every release trying to figure out what additional crud got added to the full Raspbian image that is not needed and only blows up the download size and saves everyone kind enough to provide a download mirror actual money for the saved traffic, not to mention saves everyone who just wants to run OctoPi as a headless server (the majority) the time needed to download the extra megabytes of image size they don't need for their use case. So win win for everyone really.

apt-get is there for a reason. Not every possible use case needs to be shipped out of the box if stuff is easy to install post-flash. Especially not if trying to do that doubles or triples the download size for everyone.

@3driffs

This comment has been minimized.

Copy link

3driffs commented Mar 29, 2016

Thanks, I missed that in the earlier post. No disagreement on the strategy, just wasn't aware it had changed. I may yet just run two PI's (they're cheap enough), my old 2 as the dedicated server, and the 3 with a full desktop environment. I haven't seen issues, but your point about load on during a long print is well taken.

@3driffs

This comment has been minimized.

Copy link

3driffs commented Apr 2, 2016

And just to close out my part in the thread, two pi's works great. Thanks for the info.

@yenoromp

This comment has been minimized.

Copy link

yenoromp commented Apr 2, 2016

I'm sticking with the image I installed a week or so ago when the octopi install was fixed
Done heaps of prints since then

Paul Moroney
0400720144

Sent from my iPhone

On 2 Apr 2016, at 12:04 PM, 3driffs notifications@github.com wrote:

And just to close out my part in the thread, two pi's works great. Thanks for the info.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@glm1157

This comment has been minimized.

Copy link

glm1157 commented Apr 5, 2016

Which nightly are you using? I tried the one of the latest builds (either 2016-04-04 or 2016-04-05, I forget) and I had problems setting up WiFi and connecting to my printer. It might be me or the build. Just want to try something that has worked for someone to eliminate one of the variables.

Thanks,

Gary

@yenoromp

This comment has been minimized.

Copy link

yenoromp commented Apr 5, 2016

Mine is an oldish nightly

I will check later , but if you check the size of the download , mine is the second one after the size increase .... And it's working fine

Paul Moroney
0400720144

Sent from my iPhone

On 6 Apr 2016, at 8:14 AM, glm1157 notifications@github.com wrote:

Which nightly are you using? I tried the one of the latest builds (either 2016-04-04 or 2016-04-05, I forget) and I had problems setting up WiFi and connecting to my printer. It might be me or the build. Just want to try something that has worked for someone to eliminate one of the variables.

Thanks,

Gary


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@glm1157

This comment has been minimized.

Copy link

glm1157 commented Apr 6, 2016

Thanks. I grabbed 2016-03-25_2016-03-18-octopi-jessie-lite-0.13.0.zip and had the same problems. I cannot get Wi-Fi to work. I am using WEP which might be part of the problem. Some folks have had problems with it on their Pi2s.

My second problem was fixed by switching to a lower baud rate. I assumed that I could use 250000 like I did on my PogoPlug version of Octoprint. I had to go down to 115200. It's working now. Printing a case for my PI now.

Thanks,

Gary

@fireman1396

This comment has been minimized.

Copy link

fireman1396 commented Apr 6, 2016

ok sooo i have literally NO idea what I'm doing... have a pi 3, running the latest nightly, got past the login screen, and have no clue what to do next.. all videos and such show only setting up with a version with GUI. i get i need to use the command line, but whats the next step? not sure if my wifi is connected or working

@yenoromp

This comment has been minimized.

Copy link

yenoromp commented Apr 6, 2016

My wifi worked

I used the old way without the supplicant , as well as edited the networks file directly ...

Paul Moroney
0400720144

Sent from my iPhone

On 6 Apr 2016, at 2:34 PM, glm1157 notifications@github.com wrote:

Thanks. I grabbed 2016-03-25_2016-03-18-octopi-jessie-lite-0.13.0.zip and had the same problems. I cannot get Wi-Fi to work. I am using WEP which might be part of the problem. Some folks have had problems with it on their Pi2s.

My second problem was fixed by switching to a lower baud rate. I assumed that I could use 250000 like I did on my PogoPlug version of Octoprint. I had to go down to 115200. It's working now. Printing a case for my PI now.

Thanks,

Gary


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@notcranium

This comment has been minimized.

Copy link

notcranium commented Apr 25, 2016

Hi. Great job on what has been done so far. I hope this keeps progressing. I am supporting the project through Patreon!

I'm using jessie-lite-0.13.0. I don't have my printer yet so can't post if there are issues with that for another week. But the problems I see right now are:

  • SD card is not initialized so I cannot upload files to it. Selecting the option to initialize it doesn't do anything.
  • Timelapse is completely greyed out. The Logitech C310 appears to work like a champ though.
  • I have a profile set up in the Cura Engine but can't seem to do anything with a .STL that I uploaded (maybe because there is no printer attached?)

I'm completely new to this so maybe my issues are related to not really knowing what I'm doing. :)

@nophead

This comment has been minimized.

Copy link

nophead commented Apr 25, 2016

You can't upload to SD without a printer attached because the SD card it refers to is one attached to the printer. You also can't set the timelapse options without a printer attached.

Not sure about slicing as I don't use it.

@SirVer

This comment has been minimized.

Copy link

SirVer commented Apr 27, 2016

I have a similar issue and found out that my raspberry does not like 2.4GHz channels 12 and 13 - if your router is set to AUTO choose the channels, this might be your issue. See raspberrypi/linux#1442 (comment).

@yenoromp

This comment has been minimized.

Copy link

yenoromp commented Apr 27, 2016

Hi

Could this to be with time zones as some channels are not allowed in certain countries ?

Paul Moroney
0400720144

Sent from my iPhone

On 27 Apr 2016, at 5:33 PM, Holger Rapp notifications@github.com wrote:

I have a similar issue and found out that my raspberry does not like 2.4GHz channels 12 and 13 - if your router is set to AUTO choose the channels, this might be your issue. See raspberrypi/linux#1442 (comment).


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@guysoft

This comment has been minimized.

Copy link
Owner

guysoft commented May 1, 2016

Fixed in 0.13.0

@guysoft guysoft closed this May 1, 2016

@alex-gibson

This comment has been minimized.

Copy link
Author

alex-gibson commented May 1, 2016

Thanks to everyone who contributed to fixing this issue!

@SIXM6N

This comment has been minimized.

Copy link

SIXM6N commented Nov 29, 2016

After it just happened again, I have to agree, doesn't seem to be power related.

I also have to correct myself, it apparently doesn't freeze completely after all, it just looses wifi connectivity. Funny thing is, it believes it still does have connectivity, has an IP and everything, but cannot be pinged or SSH'd into. Until I ping the router from the Pi3, then suddenly connectivity is back:

$ ping -t 192.168.1.204

Pinging 192.168.1.204 with 32 bytes of data:
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.204: bytes=32 time=2030ms TTL=64
Happens very reproducibly after some idle time. Maybe some power safe feature of the wifi chipset that's misbehaving (like it also happens with some dongles out there)?

@A-Nesh did it really freeze for you during printing (print stopped) or could it be that just the network connection broke down (print didn't stop, but anything relying on network didn't work anymore, so OctoPrint, SSH, ...).
I have pretty much tried everything and have condemned my Pi3 after the above happened to me as well Foosel. That was a copy paste of yours back in March by the way. But mine was identical. I was able to boot it move around in config but that was it. At this rate raspberry Pi is not on my good side. Octoprint was great at first and then the time lapse feature stopped working about a week ago and now the Pi has totally stopped communicating. Extremely frustrated. I reloaded the Pi several times and set it up for wifi. It fixed it the first time. But after that no more communication over the wifi. Below is my log for the time lapse issue at hand. Sorry to blow up this post. Maybe the the Pi was causing the time lapse failures. I'm a noob at this so please excuse my terminology if it fails you. I'm going to pick up another Pi this weekend unless you can convince me otherwise. I have tried the above network.text code that you added and I am running the latest and greatest (not beta). Thanks for your time.

https://db.tt/ehSBNU4a

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Nov 29, 2016

@SIXM6N Your timelapse issues are caused by the path to ffmpeg being misconfigured. On OctoPi 0.13 (which is what you should be running) that should read /usr/bin/avconv. If you are still running into those WiFi power management issues with OctoPi 0.13 I have no idea. Stuff has been pretty solid for me since the kernel module got fixed, and apparently it's also been working great for the people out there. Maybe there's something wrong with your specific Pi after all.

@picclock

This comment has been minimized.

Copy link

picclock commented Nov 29, 2016

@ghollingworth

This comment has been minimized.

Copy link

ghollingworth commented Nov 29, 2016

The Power management on the Pi3 WiFi is disabled in a downstream patch

raspberrypi/linux@e1d6cd1

Please check your dmesg for "power management disabled" to see if you have this. If not then you need to update your linux kernel, modules and firmware

Gordon

@SIXM6N

This comment has been minimized.

Copy link

SIXM6N commented Nov 29, 2016

Okay thanks for looking into it for me. Very much appreciated.

@SIXM6N

This comment has been minimized.

Copy link

SIXM6N commented Nov 30, 2016

Okay I did get my Pi3 resurrected and communicating by installing a fresh download from the Octoprint site. So excited.
The line /usr/bin/avconv was changed because I read the change on a site that would put the files directly into the exact path on my PC. And it actually worked for about 5 prints. But after the clean install it actually works the way it is supposed to.
I have another question about a post I read today about deleting a time lapse caused a deletion in the network.text file which leads me to believe that the Time lapses are stored on the SD. Is that true? Because I do remember deleting some time lapses just before my network stopped operating. My SD is only 30G so not much room if thats the case. I also noted that shutting down the power before shutting down the server through Octoprint 1st could corrupt it at well. At this point I'm not sure which one or maybe both caused the issue. I hope you can clarify this somewhat.

@foosel

This comment has been minimized.

Copy link
Collaborator

foosel commented Nov 30, 2016

OctoPrint doesn't even have write access to the network configuration file ;) And no, timelapse management cannot cause that. Pulling the power though at the wrong moment can. Always shut down the Pi first via the System menu and wait until it stops blinking before pulling power.

In general, if you have any doubts/questions/etc, best get in touch on the mailing list or in the G+ community, those are the official support channels. You'll get competent help there (as long as you provide enough information to get help of course ;)). There's a lot of misinformation across the net.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.