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

[Support] Timelapse Broken #693

Closed
Klikini opened this issue Dec 26, 2014 · 6 comments

Comments

Projects
None yet
2 participants
@Klikini
Copy link
Contributor

commented Dec 26, 2014

I have been using OctoPrint for about a week, with timelapses working the whole time. Today, they are not rendering.

I have tried:

  • updating OctoPi and sudo apt-get update
  • deleting config.yaml and starting over

Bug report info:

  1. What were you doing?
    Printing a .gcode file with zchange timelapse enabled
  2. What did you expect to happen?
    Timelapse is rendered and saved.
  3. What happened instead?
    No render notice, no timelapse in list later.
  4. Branch & Commit or Version:
    1.1.1 master/OctoPi, 1.1.1-11-g6307b76 master/OctoPi
  5. Printer model & used firmware incl. version
    Printrbot Simple Metal/Printrboard Rev F Marlin
  6. Link to octoprint.log on gist.github.com or pastebin.com:
    https://gist.github.com/Klikini/49bd72cc863a620985ce
  7. Link to contents of terminal tab on gist.github.com or pastebin.com:
    https://gist.github.com/Klikini/49bd72cc863a620985ce

I love cookies!

@Klikini Klikini changed the title Timelapse Feature Broken Timelapse Broken Dec 26, 2014

@foosel

This comment has been minimized.

Copy link
Owner

commented Dec 27, 2014

Did you by any chance try to print this file from SD card?

@Klikini

This comment has been minimized.

Copy link
Contributor Author

commented Dec 27, 2014

No, I uploaded it to the RasPi and hit load & print. I don't do SD printing because I can't do timelapses.

Updated the gist at https://gist.github.com/Klikini/49bd72cc863a620985ce to include my config.yaml

foosel added a commit that referenced this issue Dec 27, 2014

Timelapses: Do not try to use image counter if still set to None and …
…synchronize decrementing of image counter via mutex as well

 Possible fixes for #693, the latter maybe also for #690
@foosel

This comment has been minimized.

Copy link
Owner

commented Dec 27, 2014

I just pushed a bunch of changes I backported from the devel branch that make the whole timelapse capturing a bit more error resilient, and also fixed something else I just noticed which might happen rarely. Can you please update and test and if that solves your issues mark this ticket as closed? Thanks!

@Klikini

This comment has been minimized.

Copy link
Contributor Author

commented Dec 28, 2014

Now on 1.1.1-11-g6307b76 (master branch).
Timelapse is still broken. Here is the log now: https://gist.github.com/Klikini/6ba9b5f9970a866529ba

@foosel

This comment has been minimized.

Copy link
Owner

commented Dec 28, 2014

That's not a bug though, that's your camera being unreachable:

14-12-28 00:07:21,501 - octoprint.timelapse - ERROR - Could not capture image /home/pi/.octoprint/timelapse/tmp/tmp_00000.jpg from http://192.168.1.102/image/jpeg.cgi, decreasing image counter again 
[...]
IOError: [Errno socket error] [Errno 113] No route to host

You'll have to debug that one on your end. Of no images can be captured at all, of course there can also be no time lapse.

@foosel foosel changed the title Timelapse Broken [Support] Timelapse Broken Dec 28, 2014

@foosel foosel added the type:support label Dec 28, 2014

@Klikini

This comment has been minimized.

Copy link
Contributor Author

commented Dec 28, 2014

I went out and bought an ethernet switch so I could wire the camera/RasPi instead of WiFi, and now it works fine! Danke shön!

@Klikini Klikini closed this Dec 28, 2014

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.