I updated the README with some of this great info.
The image count is
-C (capital C), so -C 1000 will get you 1,000 images.
./tlapser360.sh -W y -I 5 -C 1000 -m 1 -r h -i 100 -s 0.5 -w auto -O /mnt/tmp/tlapser_test/
Here’s some tips:
- WiFi API access will shut off if you plug the camera into the USB port of your computer. To solve this, plug the camera into a wall socket or a battery (not your comptuer)
- You may need to disable sleepDelay by setting the value to
- You may need to disable offDelay by setting value to
I have heard of someone using it for a month using the WiFi API. I don’t have the details on that project, so it’s not 100% confirmed, but it seems likely the WiFi API will work for at least a week.
I’m curious to learn more about your experience as I think the script could be used as the foundation for other projects that need to access a loop.
The project also adds input from sensors like GPS and Lux, so that may be of interest for either triggers or additional data.
For example, I’m involved with a community to learn about IoT and I have this sensor on my desk.
The TMD3782 provides the lux and color measurement that I think Jason’s sensor uses.
I also have this vibration and motion sensor on my desk
I’m thinking of triggering images based on motion or vibration of an external sensor.
Even if you only use the timelapse feature of the script, it is still very valuable to get your usage example as you’re the only one on this discussion thread that is a professional artist.