Submitted by eyedesign on Fri, 08/12/2011 - 18:36
Posted in
I'm trying to get my head around keyframes and actions. What I would like to happen is have the camera exposure 800 frames while the dollie is in one postions. After the 800 frames I would like to dollie to start moving for another 1000 frames.
I've set up the slim like this;
port COM9
connect
keyframe camera 0 800 0
action motor o set_motor 1 enable
set_motor 1 dir 1
set_motor 1 steps 50
set_motor 1 disable
set_camera exposure 500
set_camera cycle 5
set_camera shots 1800
set_camera on
start
The camera fired but the dollie never moves, are the keyframe and action setup wrong?
action motor o set_motor 1
action motor o set_motor 1 enableI think you meant '0' instead of 'o' there, the format for the action command you're looking for is:
action motor <action id> enable <motor> <direction>So, you're probably looking for:
action motor 0 enable 1 3(3 for direction == "do not change direction")
Unless you have two motors, or your motor is wired up to the second motor pins, you're probably wanting motor 0, not motor 1 (the motors are zero-indexed, like the actions)
!c
Yes that should have written
Yes that should have written 0 in the post. I'll try the command as you formated it and see what happens "action motor 0 enable 1 3
Thanks
No joy with that format.
No joy with that format. Written below minus the notes is now I'm setting up the program.
Type 'help' for help
[1] > port COM5
[2] > connect
[3] > keyframe camera 0 10 0 Note: keyframe type(camera) (index) (10 shots) (call action 0)
[4] > action motor 0 enable 1 1 Note: action type(motor) (index) (action to be taken enable motor 1 dir = 1). Yes I have my motor wired for motor 1.
[5] > set_motor 1 step 100
[6] > set_camera exposure 500
[7] > set_camera cycle 5
[8] > set_camera shots 100
[9] > set_camera on
[10] > start
This is just a test to see if the camera will sit in one postion for 50secs/10 shots and than start moving the motor.
I'm I placing the keyframe and action commands in the right place, or do I need to add some other command?
Interesting, as far as I
Interesting, as far as I know, I've never had that issue.
Before I get too deep into debugging (mostly because I've been knee-deep in the hardware and firmware for the incompatible desgin), I do have to ask a dumb question =)
Did you validate that the
move <motor> <dir> <steps>command does what you expect it to? If that doesn't move the motor, you likely have a driver or wiring issue.!c