#timelapse not working
69 messages · Page 1 of 1 (latest)
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:
- Wrong adress
- Creality printer don't have wget installed
- The folder it's trying to save to is not available
Run wget http://localhost/webcam/?action=snapshot -O /usr/data/printer_data/frames/frame000001.jpg on ssh and send the output
ping localhost
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?
mmmm
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
Change the snapshot url in Mainsail to http://ip.of.your.printer:8080/?action=snapshot
Send a screenshot, that I can check it
You write that you run the command, but the screenshot is not showing it, so what should that screenshot show me?
The macro appears automatically when I do the installation
How should I test if it works?
What are you talking about now?
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?
gives me this code
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
// {"code":"key61, "msg":"Unknown command:M240", "values": ["M240"]}
What?
Send a screenshot of your whole console
not just the upper part of it
Send your moonraker.log and klippy.log
You are not using our macros, you adjusted them
you basically changed the timelapse_take_frame gcode to m240
Do not manually edit any of our macros, if you want support from us
I recommend to just reinstall it
Here is the original code, but you should not just copy paste it:
https://github.com/mainsail-crew/moonraker-timelapse/blob/main/klipper_macro/timelapse.cfg
timelapse
i think i fixeit, im going to test
If you didn't get it, that's wrong
yes, and the snapshot link
I think my friend was missing the link and that's why he started modifying the gcode.
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.
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