Is it possible to set up a time lapse sequence that only shoots during certain hours, say 9am to 5pm every day for a period of months using OpenMoco? If so how do I do that?
Submitted by shutterdrone on Wed, 04/28/2010 - 01:24.
Presently, no. However, you can say that after, say, 10 hours of shooting to disable the camera (and thereby disable motors, etc.) and then re-enable the camera another 12 hours later (or whatever time you want), but you can't presently say "shoot between these hours of the day."
It would be fairly easy to make the changes, presuming you first told it what time it was, but the difficulty is that there isn't a real-time clock on the arduino, so one would have to have one, else "5pm" would slowly either get later or earlier in the day =)
Well since it's not too easy I may go with a intervalometer card I found for this project but will experiment with this. I just have to figure out how to integrate the RTC into OpenMoco. Some things with OpenMoco are a lot easier, like triggering multiple cameras but some are harder like integrating a RTC into the system. Cost per board will be pretty similar adding the cost of the RTC into the equation otherwise I would have liked to go with Ardinos since I can use them later on other projects.
Submitted by shutterdrone on Wed, 04/28/2010 - 17:06.
How hard or how easy is always a matter of perspective and skill =)
I find integrating an i2c-based RTC to be pretty easy, but I know i2c and am familiar with doing it on the arduino platform *grin*
The idea behind OpenMoco was not to provide an engine that does everything for everyone, but a good platform for people who feel like building something new or unique to add new features to without having to re-invent the whole moco wheel every time. Others may also desire to achieve the use-case you're looking for - so in this way everyone would benefit if you integrated an RTC and then shared your technique. For yet others, the RTC would take up valuable I/O resources that they need for something else.
OpenMoco is designed to make it easier to build a system from scratch, not necessarily to be easier than commercial products for achieving specific use-cases =) It's fairly hard for a DIY project to compete with a fully-assembled and ready-to-run commercial system in "ease of achieving a shot".
I have given this another thought. Why should this be implemented in the engine? A controller with a RTC like a PC or other device could control the engine at the required interval.
Presently, no. However, you
Presently, no. However, you can say that after, say, 10 hours of shooting to disable the camera (and thereby disable motors, etc.) and then re-enable the camera another 12 hours later (or whatever time you want), but you can't presently say "shoot between these hours of the day."
It would be fairly easy to make the changes, presuming you first told it what time it was, but the difficulty is that there isn't a real-time clock on the arduino, so one would have to have one, else "5pm" would slowly either get later or earlier in the day =)
!c
It could be done by adding a
It could be done by adding a real time clock :-). http://www.sparkfun.com/commerce/product_info.php?products_id=99 looks like one that could dothe job. This is only an example because the accuracy is not that great (but good enough).
Well since it's not too easy
Well since it's not too easy I may go with a intervalometer card I found for this project but will experiment with this. I just have to figure out how to integrate the RTC into OpenMoco. Some things with OpenMoco are a lot easier, like triggering multiple cameras but some are harder like integrating a RTC into the system. Cost per board will be pretty similar adding the cost of the RTC into the equation otherwise I would have liked to go with Ardinos since I can use them later on other projects.
Cheers
RC Fisher
How hard or how easy is
How hard or how easy is always a matter of perspective and skill =)
I find integrating an i2c-based RTC to be pretty easy, but I know i2c and am familiar with doing it on the arduino platform *grin*
The idea behind OpenMoco was not to provide an engine that does everything for everyone, but a good platform for people who feel like building something new or unique to add new features to without having to re-invent the whole moco wheel every time. Others may also desire to achieve the use-case you're looking for - so in this way everyone would benefit if you integrated an RTC and then shared your technique. For yet others, the RTC would take up valuable I/O resources that they need for something else.
OpenMoco is designed to make it easier to build a system from scratch, not necessarily to be easier than commercial products for achieving specific use-cases =) It's fairly hard for a DIY project to compete with a fully-assembled and ready-to-run commercial system in "ease of achieving a shot".
!c
I have given this another
I have given this another thought. Why should this be implemented in the engine? A controller with a RTC like a PC or other device could control the engine at the required interval.