Whenever I start a print, I have to remove the first instance of TIMELAPSE_TAKE_FRAME or else I get this error: !! Move out of range: -0.013 -0.013 0.285 [355.142]

I'm not sure what's causing it. The timelapse park position is set to Center.

Hello everyone, I am having some problems with the timelapse and ideamaker option.

At start gcode, I have purge line section. When printing with the timelapse function activated by layer change, this at the beginning is repeated at least 2 or even 3 times. can't find why? moreover in the console, I have a lot of command error message, a text that tries to be displayed somewhere?

if anyone has any info?

I note you if below my gcode in idea:

Start Gcode G21 G90 M82 G28 G92 E0 G1 Z15.0 F60 G0 E3 F200 G92 E0 G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position G1 X10.1 Y160.0 Z0.28 F3000.0 E15 ;Draw the first line G1 X10.4 Y160.0 Z0.28 F3000.0 ;Move to side a little G1 X10.4 Y20 Z0.28 F3000.0 E30 ;Draw the second line G92 E0

layer change gcode TIMELAPSE_TAKE_FRAME

And here is an example of what I can find in the console:

I don't know, do you need to provide more information? I'm on mainsail updated

Anyway, thanks in advance if you can help me.

klippy.log moonraker.log

I have two cameras defines, "Upper" and "Lower". In the Settings page for Timelapse I have the Lower camera selected, but on the Timelapse Status page it is showing the view of the Upper camera. I've checked and the saved frames are also not the selected camera. I tried changing the selected camera and then selecting the desired one back, but that didn't fix the issue.

Hi, I just set up moonraker timelapse, and I have the park feature enabled in the config, but it's not parking when it is supposed to send the screenshot gcode or whatever. It takes a picture each layer as enabled in my slicer, but it doesn't park in the same spot. I've attatched both my printer.cfg and timelapse.cfg, if anyone knows what's up, or maybe if I'm doing something wrong, please let me know. Thanks. printer.txt timelapse.txt .

after clicking render during print it saves to that exact layer as mp4, all the other times during print it exports the same file with different filename and without the new layers that have been captured. Still don't know what would happen at the end of the print. I'll update.

Is it possible to modify the timelapse macro to get the last frame after the execution of the end g-code (to not have the hot-end in the last frame)? Or I missed some settings?

Btw I'm not using (and prefer to not use) the park function to avoid stringing and prolonged times.

Hello, I just installed the timelapse function and it is working. But I have problems with the Park Toolhead option, although I have it activated it does not work. What can I do in this case?

hi

i use fluidd, and time-frame/lapse on my command from terminal "TIMELAPSE_TAKE_FRAME" he take picture on my saved directory /tmp/timelapse/

and it names frame000001.jpg

on next command TIMELAPSE_TAKE_FRAME he doesn't take next number frame00002.jpg, he just overite 00001.jpg... what im doing wrong?

when im download pic from raspi (cyberduck) to mac.. i'm only can open in photoshop, in normal pic view program got some error...

sorry for bad eng

some fixed but still having this ones:

check the logfile and fix the issue.

Following plugin has an error:

timelapse Invalid config option 'output_framerate: 20 # Note: this will be ignored if variable_fps is enabled' detected in section [timelapse]. To solve this issue check your moonraker config. This option is invalid and has to be deleted or fixed. In the future this will result in a startup error.

Invalid config option 'time_format_code: %Y%m%d_%H%M' detected in section [timelapse]. To solve this issue check your moonraker config. This option is invalid and has to be deleted or fixed. In the future this will result in a startup error.

Invalid config option 'snapshoturl: http://localhost:8080/?action=snapshot' detected in section [timelapse]. To solve this issue check your moonraker config. This option is invalid and has to be deleted or fixed. In the future this will result in a startup error.

Invalid config option 'pixelformat: yuv420p' detected in section [timelapse]. To solve this issue check your moonraker config. This option is invalid and has to be deleted or fixed. In the future this will result in a startup error.

Invalid config option 'previewimage: True' detected in section [timelapse]. To solve this issue check your moonraker config. This option is invalid and has to be deleted or fixed. In the future this will result in a startup error.

if I insert only: [timelapse]

all works, but if I insert into: [timelapse] enabled: False

error: % fluidd avvisi trovati. Moonraker ha problemi con dei plugin. Controlla i tuoi log, aggiorna la tua configurazione e riavvia moonraker. timelapse Puoi trovare la configurazione dei plug-in Moonraker qui .

It might be a config issue but thumbnails and frames won't load. Any idea why? Error:

error: { code: 401, message: "Unauthorized", traceback: "Traceback (most recent call last):

File "/home/pi/moonraker-env/lib/python3.9/site-packages/tornado/web.py", line 1681, in _execute result = self.prepare()

File "/home/pi/moonraker/moonraker/app.py", line 494, in prepare self.current_user = auth.check_authorized(self.request)

File "/home/pi/moonraker/moonraker/components/authorization.py", line 675, in check_authorized raise HTTPError(401, "Unauthorized")

tornado.web.HTTPError: HTTP 401: Unauthorized (Unauthorized) " }

Custom install paths make issues with the installer, which assumes to find klipper_config under /home/users, however for some reason my klipper install is simply under ~klipper. I have tried to link the folders as shown in a previous issue however now I am running into issues in mainsail where /home/user/printer_data/config/timelapse.cfg does not exist. As a new user to linux, I feel given enough time I can figure something out myself, however custom install paths would be a much appreciated addition

Hi,

I want it to try and render the timelapse on print stop. I think I can add the TIMELAPSE_RENDER gcode to my STOP_PRINT macro, but it says render is an "Internal use" Gcode macro.

Is there a way I can do this?

Thanks.

I have two cameras both streaming via mjpg_streamer using different ports on the same host.

No matter how many times I restart and select the correct one, it still uses one camera.

I wanted to try the snapshoturl in the moonraker.conf, but one of my cameras is mounted upside down (the one I'm trying to use) and I don't see a rotation configuration in the documentation (only 'flipX' and 'flipY').

EDIT: Using fluidd

"Error taking timelapse frame"

Latest releases of Klipper, Moonraker, Fluidd and timelapse.

In moonraker.log i find a lot of lines like the following:

2022-12-05 20:16:57,143 [timelapse.py:getWebcamConfig()] - something went wrong gettingCam UUID:9d2f61bd-263e-4bbf-976b-21d4d7eaa2ce from Database. Exception: Key '9d2f61bd-263e-4bbf-976b-21d4d7eaa2ce' in namespace 'webcams' not found
2022-12-05 20:16:57,239 [shell_command.py:_check_proc_success()] - Command (wget http://localhost:8080/?action=snapshot -O /tmp/timelapse/frame000001.jpg) successfully finished
2022-12-05 20:17:11,822 [timelapse.py:getWebcamConfig()] - something went wrong gettingCam UUID:9d2f61bd-263e-4bbf-976b-21d4d7eaa2ce from Database. Exception: Key '9d2f61bd-263e-4bbf-976b-21d4d7eaa2ce' in namespace 'webcams' not found

Despite the error, it manages to get nearly all the frames but when it doesn't it stops saving them.

Hey, first thanks for all the hard work that went into this. I was browsing through the code when I stumbled upon this macro and I am interested in calibrating the stream delay. From what I could infer, it moves from a small X value to the middle of the bed, takes a snap, and then moves to the other side of the bed. Then we should find the pic in the tmp folder and see if its blurry, and adjust the stream delay compensation higher or lower to make it not blurry.

My problem is that when I tried to do this, I noticed that I got different values if I pre-move X to its starting point, or if I start the test from the far side. With a vale of 0.9 (which seems pretty high, I was taking successful timelapses with the default 0.05), I can take non blurry pics in the middle position, but if the head has to move from the other side of the bed to the starting point, then I get blurry pics again.

So, since the value seems too high, and there is different behavior depending on where the head starts, I take that either I am using the test wrong or the code is a bit buggy. Any word on this?

Thanks!