Timelapse in v2

Timelapse comes built in but I'm guessing I need to do something to get options for it to appear in mainsail. What is required?
9 Replies
billyd
billyd•16mo ago
I should have made it more clear that I am not seeing a way to control timelapse in the mainsail settings but it is built in to v2.
miklschmidt
miklschmidt•16mo ago
Yeah you need to add the necessary configuration, check the mainsail timelapse docs on how to set it up
ptegler
ptegler•16mo ago
I posted a Q here about timelapse myself. for V2 ..still couldn't get it to show up in settings. final trick got it back. moonraker.conf near the top just add [timelapse]
# Load the RatOS moonraker defaults
[include RatOS/moonraker.conf]

[timelapse]
# Load the RatOS moonraker defaults
[include RatOS/moonraker.conf]

[timelapse]
any setting you add under there just permanently sets that variable you could have changed vi the timelapse interface. so don't add anything under it. down the bottom of moonraker.cfg you need to add the typical update stuff as instructed on the github page
[update_manager timelapse]
type: git_repo
primary_branch: main
path: ~/moonraker-timelapse
origin: https://github.com/mainsail-crew/moonraker-timelapse.git
managed_services: klipper moonraker
[update_manager timelapse]
type: git_repo
primary_branch: main
path: ~/moonraker-timelapse
origin: https://github.com/mainsail-crew/moonraker-timelapse.git
managed_services: klipper moonraker
miklschmidt
miklschmidt•16mo ago
last part is already present in RatOS/moonraker.conf so no need to add that. just the [timelapse] section is required.
ptegler
ptegler•16mo ago
Mikkel... I kid you not...the only thing that was in my moonraker.conf was
# Load the RatOS moonraker defaults
[include RatOS/moonraker.conf]

# If you use a non standard ip range in your local network,
# you can specify it under trusted_clients here.
[authorization]
cors_domains:
http://app.fluidd.xyz
https://app.fluidd.xyz
https://my.mainsail.xyz
http://my.mainsail.xyz
http://*.local
http://*.lan
trusted_clients:
127.0.0.1
10.0.0.0/8
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.168.0.0/16
FE80::/10
::1/128
FD00::/8
# Load the RatOS moonraker defaults
[include RatOS/moonraker.conf]

# If you use a non standard ip range in your local network,
# you can specify it under trusted_clients here.
[authorization]
cors_domains:
http://app.fluidd.xyz
https://app.fluidd.xyz
https://my.mainsail.xyz
http://my.mainsail.xyz
http://*.local
http://*.lan
trusted_clients:
127.0.0.1
10.0.0.0/8
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.168.0.0/16
FE80::/10
::1/128
FD00::/8
I manually added all the update manger entries and add timelapse at the beginning. yep...just went back and check my initial config backup (always on any fresh install as a ref) there was nothing in that file except as above . It was my biggest single point of confusion and why I thought so much more had been integrated or something, not needing this anymore. Regardless... I too am hoping it is a simple as you stated for the masses. (I know i know...i'm a 'special' case 🤪
correct-apricot
correct-apricot•16mo ago
yup, same here. [timelapse] was not present in the moonraker.conf. I did a full clean install.
miklschmidt
miklschmidt•16mo ago
That's intentional No need to add the update manager entries, they're already in the included file. That's on purpose. To reiterate. All you need to use timelapse is to add [timelapse] to moonraker.conf, and you're done. [include RatOS/moonraker.conf] contains everything else.
correct-apricot
correct-apricot•16mo ago
And I guess don't forget about the [include timelapse.cfg] in printer.cfg
miklschmidt
miklschmidt•16mo ago
that too