Submitted by SunboX on Sat, 10/02/2010 - 21:24
Posted in
Would be cool if someone could set how long the dolly should move. This opens up more possibilities. For example, speeden up the shootings in the middle. So the take becomes more "dynamic". :o)
Greetings André
Hi Andre! Let me make sure I
Hi Andre!
Let me make sure I understand clearly: a feature to set the duration of the program based on the distance traveled? But, you also want ramping, correct? There is ramping already, it's based on shots (set how many shots to ramp up to "full speed", and it increases speed after every shot), and if you specify a maximum # of shots, it will automatically ramp down. I'm adding some features right now to trigger ramp ups/down manually while the program is already running.
!c
Hi Chris(?), oh, ok its
Hi Chris(?),
oh, ok its called ramping. ;o) Yes i mean ramping. Thats a cool Feature!
Lets say i take 1000 Shots and specify a maximum number of 500 shots, will it ramp up the first 500 and than ramp the last 500 down? Is the ramping linear or can i choose a exponential function, to get a more natural acceleration?
is it possible to only ramp up and down the movement of the dolly and let the camera take pictures continuously?
so much questions. ;o)
greetings André
The thing I haven’t been able
The thing I haven’t been able to work out yet is how to set it up so motor 2 (or 3/4 when daisy chained) is idle for a specified amount of time/ number of shots while motor 1 ramps up and begins it’s move before the second (third/ fourth) motor begins it’s move. I guess I’ll figure it out once the full documentation that is coming is released.
@birdvideo, with the current
@birdvideo, with the current firmware, you can't quite do that... But it's such an easy feature to add, I'm just going to slip it into the next round of development, like in the next week...
I'll make it so that you can set an 'on delay' for # of shots for a motor, so it wouldn't start until x shots have been fired. In daisy-chaining, for now, it's going to be "simple" -- one will act as the master, and the other as the slave. They will sync up, and the master will send the go signal to the slave, and they'll be configured independently for now. Later features will blank out the slave, and allow for single-point configuration, but that's a huge amount of work to get that done, and I'd kinda rather add support for controlling telescope heads (in addition to 2 DC motors =) first *grin*
@Andre, basically, yes. Presume the following settings for motor 1:
Ramp Shots: 50
Max Speed (speed set on main screen): 1 IPM
And, camera settings:
Max Shots: 1000
So, given those settings, the following would happen when you turn it on:
* The motor speed would initially drop to 0 IPM (ramp up from stop)
* Over the course of 50 shots, the speed would linearly increase to 1 IPM
* At shot 950, the speed would start to decrease
* At shot 1000, the speed would be 0 IPM and the intervalometer would turn off
There's a fixed Shoot-move-shoot mode (instead of auto-calculating the distance between shots in the easy SMS mode) in the current dev branch that let's you specify exactly how far to move between shots, in 1/100" increments. (0.01-30.89" between shots). This gets even better ramps, as the "continuous" mode only has 255 speed intervals, where fixed SMS has about 30,000 =)
!chris
Thank-you, Chris! Adding ‘on
Thank-you, Chris! Adding ‘on delay’ would be wonderful, and you know I’m anxious to control those telescope heads. It must be exciting to be juggling so many balls at once! ;)