Hello folks I noticed, I have quite a few issues with Octoprint. Of of the most annoying is, that it is constantly crashing on different situations (becomes unresponsible). Often when I upload a gcode file via Browser to the SD-Card or the local storage, the process stops at a random point and after that I have to power off the big box and power it on again to become OctoPrint running again. I was able to check the logs during an occurrence, and it said: Code: Send: N2 G90*18 Recv: Error:Line Number is not Last Line Number+1, Last Line: 0 Recv: Resend: 1 Recv: ok Send: N1 M110 N0*124 Recv: ok Send: N2 G90*18 Recv: Error:Line Number is not Last Line Number+1, Last Line: 0 Recv: Resend: 1 Recv: ok Send: N1 M110 N0*124 Recv: ok Send: N2 G90*18 Recv: Error:Line Number is not Last Line Number+1, Last Line: 0 Recv: Resend: 1 Recv: ok Send: N1 M110 N0*124 This is repeating all the time. Does anybody else know, what the issue chould be?
Could be a faulty step down converter, assumed that your connection is ok. Maybe your camera settings are too ambigious too. Did you go through this step? http://wiki.e3d-online.com/wiki/File:Putty_raspi_config.jpg
Yes, I went through this step. Anyway, I only upload directly to OctoPrint when I have very small files under 0.5MB, since it takes about 10 minutes to upload files, which are bigger (is this normal?). I didn't get the point with the camera - what do you mean by that?
I thought you possibly changed options in /boot/octopi.txt. If not, can't be the reason. Uploading big files takes some time, that's normal. It's always easier to put files directly on SD-card. Perhaps you try to log your serial connection to see what happens.
Thanks for your answer. I didn't change anything in octopi.txt. I would not completely agree, that it is easier, but it seems to be faster at least. An other advantage of uploading the files directly within OctoPrint is - in my humble opinion - that I can see the details in Octoprint (like estimated printing duration, full file names, upload time, and so forth). When I upload them to the SD card (by taking the SD card out and put it into the PC), I do only see 8 chars of the filename within octoPrint, which doesn't really help to recognize the correct file. Anyway, I will activate the serial.log - maybe it could help to find the issue, thanks!
I don't have a bigbox yet, but I have octopi set up on my current printer and even though it's using a wifi connection it doesn't take very long to upload files at all. I just tried uploading a 50MB gcode file and it took 5 seconds. Admittedly my printer uses a slightly higher baud rate but it still shouldn't take 10 minutes. Are you uploading them to the SD on the pi or to the printer? I always upload them locally as it takes much longer to upload them to the printer SD card for no real benefit.
I think that the printer SD is safer as you don't use USB in between. Had some broken prints with octopi in the past and it's annoying when a 14h print breaks after 12h. But its a raspberry issue, it's not something with octoprint.
On mine I haven't diagnosed if it is the DC-DC psu or what, but to get working, I just put a new PI outside the case (in its own case) with a regular RPi wall-wart PS. moved stability from "maybe I will work for 5 mins" to "very solid". May need to put a fan on the case as video streaming seems to warm it up a tad...
I tried a few times to upload the files to local via OctoPrint instead of uploading it to SD card via OctoPrint. And it looks like the time consuming process is to move it from local to the SD card. When I just upload it to the local storage it is extremely fast (compared to SD card) and I have all the advantages I want to have (estimated print time, file names, upload time, and so on). Looks like this one is solved for now, thanks for your hints, especially @Sarah Nicholson .
