CHDK PTP interface - page 15 - General Discussion and Assistance - CHDK Forum
supplierdeeply

CHDK PTP interface

  • 1244 Replies
  • 524107 Views
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK PTP interface
« Reply #140 on: 25 / December / 2009, 07:57:14 »
Advertisements
@Marcio Lima
Use you the windows program chdkcam from ewavr' site? You must also install a usb driver libusb.

@reyalp
PTP service should be added optional in trunk. It works ok for me. Sometime I have a little instabil usb connection. The webcam function is also ok. I have included ptp interface in my branch of chdk_de svn server. Binary files are available here.

For the A540 is a small correction necessary - see attachment. Without this the compiler displays a warning.
CHDK-DE:  CHDK-DE links

*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: CHDK PTP interface
« Reply #141 on: 25 / December / 2009, 08:07:33 »
connected directly (on board USB, nVidia GeForce 8200 chipset) it behaves very instable, the connection mostly get lost after some seconds.
I saw the same thing with SX10 and some computer (I don't remember chipset model). When camera is switched to USB 1.1  ("B") mode, connection is stable, but frame rate is 1..2 fps ;). On the same computer connection with A710 and IXUS700 is perfect.

*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: CHDK PTP interface
« Reply #142 on: 25 / December / 2009, 10:58:36 »
Trying to shoot after switch to rec crashed the cam.
RAW saving is off?

*

Offline whoever

  • ****
  • 280
  • IXUS950
Re: CHDK PTP interface
« Reply #143 on: 25 / December / 2009, 12:18:51 »
Note, I added add_ptp_handler to sig_ref_vxworks_1.txt, seems to be a good match.
Gives good match (though <100%) and finds the function correctly here, too (Ixus950): NSTUB(add_ptp_handler, 0xFF9EC59C).

So, if findsig can be trained to find add_ptp_handler() on (all) other cameras, I don't see any obstacle to including the basic PTP handling stuff to the autobuild right away.

There remains the mode switching stuff, for which I'd hard-code the "logical events" PressRecButton/PressPBButton -- if I read Microfunguy correctly, this works on most (all) cameras that he supports. It may not work correctly with PTP (e.g., may disconnect), but shouldn't crash the camera.

Then, I'd bundle mweerden's ptpcam as a basic PC-side client (ewavr's extensions require much more attention for each camera and computer).

Such minimal implementation, together with reyalp's Lua additions (levents, call by name/address, etc.), already gives a powerful interface.

It may be useful to make PTP extensions run-time-optional, although it is not obvious how to do that neatly (PTP handler registration happens in a task that is not synchronized with reading of config).

EDIT: Almost forgot... Merry Christmas! Und guten Rutsch, etc.!
« Last Edit: 25 / December / 2009, 12:29:07 by whoever »


*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: CHDK PTP interface
« Reply #144 on: 25 / December / 2009, 14:13:47 »
There remains the mode switching stuff, for which I'd hard-code the "logical events" PressRecButton/PressPBButton -- if I read Microfunguy correctly, this works on most (all) cameras that he supports.
It seems that this works only on some VxWorks cameras (a540, a710, ixus700, a610). On DryOS (SX10) "PressRecButton" event has no effect if USB cable is connected.

*

Offline yvesson

  • ***
  • 209
  • A540 SX10IS
    • poll about some pics (not much serious) ^^
Re: CHDK PTP interface
« Reply #145 on: 25 / December / 2009, 16:21:21 »
Hej,
well as I'm not too much into using patches and stuff, I'll just wait for it is in a built...

By the way, wouldn't this help in one of the most wanted CHDK feature request, camera acting like a card reader ?

*

Offline reyalp

  • ******
  • 14118
Re: CHDK PTP interface
« Reply #146 on: 25 / December / 2009, 16:57:58 »
There remains the mode switching stuff, for which I'd hard-code the "logical events" PressRecButton/PressPBButton -- if I read Microfunguy correctly, this works on most (all) cameras that he supports.
It seems that this works only on some VxWorks cameras (a540, a710, ixus700, a610). On DryOS (SX10) "PressRecButton" event has no effect if USB cable is connected.
Maybe the functions used on the other cameras can be found with the sig finder. I was hoping to find an eventproc that did the same thing, but I haven't yet.

I'm not sure about putting it in the autobuild yet, I think we want room to break things for a while until we work out the best way to put it all together. Turning making the PTP stuff a runtime option shouldn't be too hard. I've had quit a few crashes/hangs just playing with script stuff in ewavrs chdkcam

@yvesson
both ewavrs chdkcam and the modified ptpcam lets you upload/download any file, although it doesn't act like a drive. With fuse we could do this quite easily on linux :)

also another most wanted feature, use camera like web cam :)
Many thanks tow mweerden and ewavr!
Don't forget what the H stands for.

Re: CHDK PTP interface
« Reply #147 on: 26 / December / 2009, 08:46:34 »
Guys

It worked on the SX200 but I used the binaries from ewavr. I would like to have the worked sources (trunk, patch, etc) because I want to add new features and also to port to SX120. Can Anybody tells me where I can download it ?

Guys Great work!


*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: CHDK PTP interface
« Reply #148 on: 26 / December / 2009, 12:58:14 »
It worked on the SX200 but I used the binaries from ewavr. I would like to have the worked sources (trunk, patch, etc) because I want to add new features and also to port to SX120. Can Anybody tells me where I can download it ?
Hmmm - what are you missing ?
There's the diff against the official CHDK trunk (rev. #863) and also the complete source code for the Windows app (Borland C++ Builder 6) on ewavr's site...

So just load trunk #863 from here (DL link for the zip file is at the bottom), apply the diff & compile it !
On Windows i suggest do use the CHDKShell

Re: CHDK PTP interface
« Reply #149 on: 28 / December / 2009, 08:22:10 »
There remains the mode switching stuff, for which I'd hard-code the "logical events" PressRecButton/PressPBButton -- if I read Microfunguy correctly, this works on most (all) cameras that he supports.
It seems that this works only on some VxWorks cameras (a540, a710, ixus700, a610). On DryOS (SX10) "PressRecButton" event has no effect if USB cable is connected.

I'm currently working on a solution for that (I'm using the G9). The problem is, that all the whole operating mode of the camera is different when the USB cable is connected. I'm still reverse engineering the firmware to understand the "ModeDial" system. I made some progress but my work isn't finished until now. If anyone works on similar stuff I would appreciate to collaborate.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal