#timelapse not working

69 messages · Page 1 of 1 (latest)

fiery sable
#

I installed timelapse using helper script, all the buttons and settings appear, I added the gcode to the layer change but it doesn't generate the timelapse at any time

slow sinew
#

Send the camera settings in MAinsail

#

Right now, it cannot capture the frames:
Command (wget http://localhost/webcam/?action=snapshot -O /usr/data/printer_data/frames/frame000001.jpg) exited with return code 1

#

There are three possibilities:

  1. Wrong adress
  2. Creality printer don't have wget installed
  3. The folder it's trying to save to is not available
fiery sable
fiery sable
slow sinew
#

Run wget http://localhost/webcam/?action=snapshot -O /usr/data/printer_data/frames/frame000001.jpg on ssh and send the output

fiery sable
slow sinew
#

ping localhost

fiery sable
#

do i need a raspberry? or with only the printer i can doit?

slow sinew
#

It should be able to do it with just the printer

#

but your current setup is not a default setup

#

You are using the creality helper script, as you otherwise could not use all the software you are right now using

#

Tbh I don't know what the issue should be, as everything seems to be fine, so I would guess it's some creality specific issue

#

what webcam service are you using?

#

crowsnest or webcamd?

fiery sable
#

mmmm

slow sinew
#

If not crowsnest, try to run this: wget http://localhost:8080/?action=snapshot

#

If that doesn't work, please try to get help in a community specific for this printer

fiery sable
slow sinew
#

Change the snapshot url in Mainsail to http://ip.of.your.printer:8080/?action=snapshot

fiery sable
#

ok

#

and then?

slow sinew
#

Send a screenshot, that I can check it

fiery sable
#

i used the "timelapse take frame" macro

slow sinew
fiery sable
#

The macro appears automatically when I do the installation

#

How should I test if it works?

slow sinew
#

That message of you is out of context

#

I know that you the gcode is getting installed with it, but what does it has to do with this?

fiery sable
slow sinew
# fiery sable How should I test if it works?

Running the command and looking into the moonraker.log, but my message was just about you writing that you executed the command, but the screenshot is just showing the cam on the dashboard

fiery sable
#

// {"code":"key61, "msg":"Unknown command:M240", "values": ["M240"]}

slow sinew
#

Send a screenshot of your whole console

#

not just the upper part of it

fiery sable
slow sinew
#

Please type in TIMELAPSE_TAKE_FRAME on the console

#

then send a screensot

fiery sable
slow sinew
#

Send your moonraker.log and klippy.log

fiery sable
slow sinew
#

You are not using our macros, you adjusted them

#

you basically changed the timelapse_take_frame gcode to m240

fiery sable
#

maybe my partner changed it

#

What is the original code?

slow sinew
#

Do not manually edit any of our macros, if you want support from us

#

I recommend to just reinstall it

fiery sable
#

do i have to reinstal the timelapse plugin?

#

or what plugin?

slow sinew
#

timelapse

fiery sable
#

done, getting the same error

fiery sable
#

i think i fixeit, im going to test

slow sinew
#

If you didn't get it, that's wrong

fiery sable
#

yes, and the snapshot link

#

I think my friend was missing the link and that's why he started modifying the gcode.

fiery sable
#

hi

#

Now I'm having the problem that if the timelapse is too long at the time of rendering, when the printing ends the printer crashes and I lose the frames and the render.

slow sinew
#

A printer crash should not influence timelapses. Do you click on the firmware restart button?

#

But in the end, the only option, is to not do timelapses

#

You are using a weak host and encode a video on the CPU of it. That results in a high load and therefore it shuts down

#

Another option would be, to not use a K Series printer and to use a host like the Pi, but that's a more expensive option