a495 chdk ptp - page 4 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 2 3 [4]   Go Down

a495 chdk ptp

  • 36 Replies
  • 10896 Views
*

Offline agrath

  • *
  • 21
Re: a495 chdk ptp
« Reply #30 on: 06 / May / 2011, 23:09:55 »
Advertisements
Quote from: reyalp on 06 / May / 2011, 22:57:29
Quote from: agrath on 06 / May / 2011, 22:54:43
The script doesnt do any IO either, it just waits for a trigger, takes the photo then refocuses (half shutter) until the next shoot perhaps that's it?
If you are sitting in half shoot, I could see that as doing it indirectly by changing the behavior of the Canon firmware somehow. I would try releasing for a few seconds and see what happens.

sweet, we're just setting up the 4th testing card and then we'll test the scripts

Thanks so much for all your help
Logged
*

Offline agrath

  • *
  • 21
Re: a495 chdk ptp
« Reply #31 on: 07 / May / 2011, 19:56:00 »
Hi reyalp, in on a sunday testing this out.
We're using the remote usb +5v trigger today..
Just wanted to confirm that adding the sleep after the shoot while the script was running did not affect whether the eyefi cards uploaded the photos afterwards :(
Logged
*

Offline reyalp

  • ******
  • 13350
Re: a495 chdk ptp
« Reply #32 on: 07 / May / 2011, 20:03:13 »
Quote from: agrath on 07 / May / 2011, 19:56:00
Hi reyalp, in on a sunday testing this out.
We're using the remote usb +5v trigger today..
Just wanted to confirm that adding the sleep after the shoot while the script was running did not affect whether the eyefi cards uploaded the photos afterwards :(
That is very strange. I suggest experimenting with a camera+eyefi manually to see if you can figure which parts of the camera state influence eyefi downloading. Eyefi really has very little insight into what the camera is doing, so I seriously doubt it is directly related to the script running. It has to be related to disk access patterns somehow. I don't think eyefi would really even know when a file was closed or not, although they might be guessing based on fat updates or something.

I assume you've released halfshoot before the sleep ? What about switching to play mode ?

I assume you have USB remote enabled ? If not, scripts will still detect the USB signal, but the camera will also think it is plugged into USB and try to act like it's in PTP mode (which would generally mean your script won't work, so I'm guessing this isn't the case....)
Logged
Don't forget what the H stands for.
*

Offline agrath

  • *
  • 21
Re: a495 chdk ptp
« Reply #33 on: 07 / May / 2011, 20:41:08 »
Hey
Yeah, I thought it was pretty strange.
Without the script running everything works sweet, and if we powercycle the cameras they work great.
What's the command to get the camera to switch between playback and record mode? At the moment, i'm using a click("half_shutter") to get it into record mode.
I can script it dropping into playback mode for 3 sec and then back to record mode quite quickly so I can test that.

Haven't directly released halfshoot: this is what we're doing:
:loop
   press "shoot_half"
   wait_click
   is_key k "remote"
   if k=1 then
      print "shoot"
      click "shoot_full"
      sleep 2000
   endif

goto "loop"

Yes, USB remote is enabled, and that's triggering okay - it's just the script that we have to quit to get teh upload to happen.
When just shooting by hand (no chdk) the eyefi uploads fairly quicky, I can try a variety of different things on the camera natively however because just quitting the script kicks the upload off, something must not be happening while the script is running which eye-fi is waiting for.

We're [client and myself] not completely happy with the shutter release delay/timings, so we're going to try a few more approaches (the ms offset is one of these tests) this afternoon - but right now because we have to powercycle to get the photos to upload, the eye-fi option is not viable - too unreliable powercycling the cameras and hoping all of them come back online.
Logged
*

Offline reyalp

  • ******
  • 13350
Re: a495 chdk ptp
« Reply #34 on: 07 / May / 2011, 21:17:03 »
You are using press "shoot_half", without a corresponding release. This means the camera thinks you are holding half press all the time, which I suggested earlier was the likely cause of your problem with eye-fi.

I would put release "shoot_half" directly above the sleep 2000. I'll bet you a beer this fixes it  ;)

you can use set_record 0 to go to play mode, and set_record 1 to switch to rec. See http://chdk.wikia.com/wiki/Script_commands#set_record.28state.29 and pay attention to the note about sleeping. You can use CHDK/SCRIPTS/TEST/SETREC.BAS as an example.

edit:
link directly to the section in the wiki
« Last Edit: 07 / May / 2011, 21:21:40 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline eternalMortal

  • *
  • 9
Re: a495 chdk ptp
« Reply #35 on: 12 / September / 2011, 23:01:37 »
I have a few questions regarding getting PTP started on a A495.

Some initial info;

> ptpcam --chdk
    unexpected return code 0x2005
    error: cannot get camera CHDK PTP version; either it has an unsupported version or no CHDK PTP support at all
    <conn> version
    ptpcam: 2.0
    unexpected return code 0x2005

> ptpcam -l
   Listing devices...
   bus/dev   vendorID/prodID   device model
   001/014   0x04A9/0x31EF   Canon PowerShot A495

CHDK Build Info;
  CHDK Ver: CHDK-DE 1.1.0
  Revision: 001
  Date: Sep 12 2011
  Camera: a495
  FW Vers: 100f
  Compiler: GCC 4.5.1
 
I cannot start ptpcam --chdk in autoboot mode of CHDK, as the camera is not recognized.

If I start in regular mode, then the ptpcam detects the camera, but is unable to start with the interactive --chdk mode, I'm able to execute ptpcam -G and it downloads all the images on to the computer into the folder from where the command was executed.

I'm testing this on linux and not windows;
Ubuntu 11.04 ( 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux)

This is fresh machine with nothing else built on top of it.

Is there anything missing which makes ptpcam --chdk fail to start ? Any insights would be useful.

EDIT: Tried it on Windows XP using ptpCamGui 2.0.108, get this message;
** init() start ...
>> version << error: cannot get camera CHDK PTP version; either it has an unsupported version or no CHDK PTP support at all
ptpcam: 2.0 (Length: 122) [unexpected return code 0x2005
unexpected return code 0x2005 (Length: 60)]

So something is not set right in the build.
« Last Edit: 12 / September / 2011, 23:14:15 by eternalMortal »
Logged
*

Offline eternalMortal

  • *
  • 9
Re: a495 chdk ptp
« Reply #36 on: 13 / September / 2011, 00:29:24 »
Answering my own previous question;

I had to reformat the SD card and copy the CHDK package from CHDKDE, cos that's where I picked up the ptpcam version.

Also CHDK was set to start on boot. CHDK has to be running to get ptpcam to work
Logged
Pages: 1 2 3 [4]   Go Up
« previous next »
 

Related Topics