Using ptp and remote operations for full body scanner - page 2 - General Help and Assistance on using CHDK stable releases - CHDK Forum

Using ptp and remote operations for full body scanner

  • 23 Replies
  • 10197 Views
Re: Using ptp and remote operations for full body scanner
« Reply #10 on: 16 / September / 2017, 00:45:47 »
Advertisements
So what should I do about my camera screen turning off when connected over ptp?

Re: Using ptp and remote operations for full body scanner
« Reply #11 on: 16 / September / 2017, 02:00:53 »
So what should I do about my camera screen turning off when connected over ptp?
That usually means that your O/S has grabbed the USB connection to the camera. You need to disable that.  There is some info here :

http://chdk.wikia.com/wiki/PTP_Extension#Linux

https://chdk.setepontos.com/index.php?topic=10664.msg115401#msg115401
https://chdk.setepontos.com/index.php?topic=6231.msg100671#msg100671
« Last Edit: 16 / September / 2017, 02:06:51 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Using ptp and remote operations for full body scanner
« Reply #12 on: 16 / September / 2017, 02:06:43 »
I hope I'm not jumping the gun here...

But I love you guys

Re: Using ptp and remote operations for full body scanner
« Reply #13 on: 16 / September / 2017, 04:34:46 »
Sorry I worded that pretty poorly, when I said jump I did indeed mean switching. I have a usb trigger that appears to be an and gate (I'm not the one who made it) to allow usb power if a button is pressed (the data line is always on). I have 3 (previously 4 but one died :( ) 24 port manhatten hubs plugged into a powered usb hub. Then the powered hub is connected to a switch which is connected to a computer

I still can't quite picture this but will assume the manhattan hubs are not independently powered.

Do you think the "usb trigger that appears to be an and gate" simply switches mains power on/off to the single powered hub into which the 3 manhattan hubs are plugged?   

If so, this comment:
https://chdk.setepontos.com/index.php?topic=13226.msg134379#msg134379

and that thread could be helpful.


I had to connect 21 at a time through ptpdrive (which automatically mounts them to drive letters)

was libusb installed for all cameras at that time?


Re: Using ptp and remote operations for full body scanner
« Reply #14 on: 16 / September / 2017, 12:34:26 »
Quote
was libusb installed for all cameras at that time?
For some reason libusb didn't like ptpdrive and wouldn't work with it, the cameras were just running winusb.

Quote
Do you think the "usb trigger that appears to be an and gate" simply switches mains power on/off to the single powered hub into which the 3 manhattan hubs are plugged?
Strangely enough the switch works with both powered and unpowered hubs, you just have to hold it a bit for it to work on the powered ones.

*

Offline reyalp

  • ******
  • 14080
Re: Using ptp and remote operations for full body scanner
« Reply #15 on: 16 / September / 2017, 16:44:29 »
Quote
was libusb installed for all cameras at that time?
For some reason libusb didn't like ptpdrive and wouldn't work with it, the cameras were just running winusb.
I think we're narrowing in on the problem here. You are using windows and ptpdrive (http://www.ptpdrive.com/) to try to download the images.

I had assumed you were using the chdk PTP extension (http://chdk.wikia.com/wiki/PTP_Extension)

If the camera receives regular (non-CHDK extension) PTP commands (e.g. a normal file download using your regular OS camera software or ptpdrive), then the screen goes black and you cannot switch to record mode again without disconnecting USB or rebooting the camera. So if you want to shoot and download without breaking the connection, you need to use the CHDK extension to download.

If you use chdkptp (https://app.assembla.com/spaces/chdkptp/wiki) you can batch download the files in various ways. The multicam module (https://app.assembla.com/spaces/chdkptp/subversion/source/HEAD/trunk/lua/multicam.lua) provides code to control and download from multiple cameras.

chdkptp requires that you use libusb, not winusb.


Don't forget what the H stands for.

Re: Using ptp and remote operations for full body scanner
« Reply #16 on: 18 / September / 2017, 08:34:52 »
Quote
chdkptp requires that you use libusb, not winusb.
The problem I think I remember having with libusb is that it didn't work properly with the usb hubs. I haven't tried using it for a while so it may have just been something else I was doing but in your experience has libusb caused trouble with usb hubs?

*

Offline reyalp

  • ******
  • 14080
Re: Using ptp and remote operations for full body scanner
« Reply #17 on: 18 / September / 2017, 13:23:53 »
Quote
chdkptp requires that you use libusb, not winusb.
The problem I think I remember having with libusb is that it didn't work properly with the usb hubs. I haven't tried using it for a while so it may have just been something else I was doing but in your experience has libusb caused trouble with usb hubs?
libusb-win32 and winusb are libraries that applications use to talk to the windows drivers. Generally an application is linked to one or the other, and you need to use whichever one the application requires.

libusb works fine with hubs, it wouldn't be working USB library if it didn't. Essentially all of my chdkptp development is done through hubs.
Don't forget what the H stands for.


Re: Using ptp and remote operations for full body scanner
« Reply #18 on: 18 / September / 2017, 16:01:13 »
So I installed chdkptp and libusb along with the mulitcam script onto a camera but when I try to run it it gives me the error

Code: [Select]
attempt to index global 'chdku' (a nil value)

*

Offline reyalp

  • ******
  • 14080
Re: Using ptp and remote operations for full body scanner
« Reply #19 on: 18 / September / 2017, 16:14:00 »
So I installed chdkptp and libusb along with the mulitcam script onto a camera but when I try to run it it gives me the error
multicam.lua runs in chdkptp, not on the camera. See this post https://chdk.setepontos.com/index.php?topic=13226.msg134374#msg134374 for some information.
Don't forget what the H stands for.

 

Related Topics