thanks reyalp
i did have a short delay between press("shoot_full_only") and release("shoot_full_only")
but while optimizing my codes. it turns out no delay is needed.. it triggers the camera just fine like this. (my 110hs anyway)
my camera / card is fast enough to do continuous shooting.. relying on pictures being buffered
and processing while the robot moves..
i'm trying to optimize time spent.
atm. my robot can do a 180x360 in under 45 seconds.. hoping to shave this down a tad.
while adding the option of having what ever exposure length with no need to change the robot firmware
if anybody is interested. here is a short clip i made for a Nikon competition a while back
https://www.youtube.com/watch?v=b_b1DiRFx3A(several generations back...(SLOOOW) but representative of the current robot)
the script seems to work.. just working on the code for the robot. should have
it waiting for the camera pretty quick here
basically I'm replacing my fixed delay(xxxx); with a simple sub routine
void camera_delay(){
while (digitalRead(photosensor) == LOW) {
delay(50);
}
}
I have wired the photo transistor so i get logic high when the camera LED is on.
should now wait for that and then carry on to next azimuth / elevation..
will test tomorrow
I'm also adding the option for a CHDK script to transmit configuration settings
to the robot.. via the LED / photo transistor link. number of azimuth / elevations and so on..
oh.. and this is the reason for this thread..
i tried to do a 180x360 spherical panorama of some northern lights in the arctic. (long exposures)..
i had run back to my room like 10 times to change the FIXED delay before it worked out...
Nomore!! haha
https://dl.dropboxusercontent.com/u/1644351/pano/Northern_Lights/index.htmlyes... the 110HS has pretty crappy low light performance.
/Kyndal