I run Octopi (Raspberry Pi image) with a Pi Cam V2. I often watch the print start from the Control tab in OctoPrint. However, this causes OctoLapse to error every time. Strangely enough when this happens the print job doesn't start.
- Has anyone else experienced this issue?
- Is there a work around, I'd like to be able to use the Control view concurrently with OctoLapse.
- I do not want OctoLapse to kill a print job. Is there a configuration element that will allow OctoPrint to proceed even if OctoLapse fails?
Here's my hypothesis, when the Control view of the camera is active in OctoPrint it has exclusive access to the connection and prevents OctoLapse from connecting to the camera service on port 8080.
Supporting this theory is that when I access the http service for the camera (e.g. 192.168.1.10:8080) OctoLapse generates the same error. I find this strange as an HTTP service (apache or whatever) should allow multiple connections. OctoLapse is configured to use the loopback address (http://127.0.0.1:8080)
For anyone experiencing issues with OctoLapse here's my notes:
I use Cura, added G90 (Absolute XYZ) to the printer gcode. This moves the bedplate and nozzle to the position specified in OctoLapse (e.g. Left Back). It is configured to trigger for each new layer. This way you get those nice timelapse videos where everything is stationary. I found some good explanations on how to do this on YouTube.
It's late, I'll provide more specific s and details later. Thank for any help with this issue.