CHDK PTP interface

ultimA

If I want to implement new PTP-query in the camera that returns only a single number or two, is my understanding of the code correct that I only need to do the following?

1) Add a new enum value to ptp_chdk_command
2) Extend the switch in handle_ptp(...)
3) Write ptp.num_param/.param1/.param2 with the return value
4) Do nothing else. PTP will return the params in the ptp structure "automatically" because of the data->send_resp( data->handle, &ptp ); line at the end of the function.

mweerden

fudgey
For windows, the easiest route is this one (I'm not 100% sure if this matches proposal patch version functionally):
http://www.mweerden.net/download/chdk-ptp/libptp2-chdk-win32.zip

I'm pretty sure it doesn't match. I can't quickly build a new version at the moment, but let me know if it's needed. I'm guessing that others have more up-to-date versions.

ultimA
If I want to implement new PTP-query in the camera that returns only a single number or two, is my understanding of the code correct that I only need to do the following?

It seems so, yes.

rudi

Thanks for your informations, but I would give only a hint for return value of the lua-api function. ~~I think the current implementation is wrong. We can't get the success result from "switch_mode_usb()".~~ Sorry for my bad description.

For your information: We had on CHDK-DE version some problems with download/upload files (eg. on IXUS100 and A610). The reason is the constant buffersize. CHDKLover have written a solution. He calculate the max. RAM-buffersize. 50% from that is the ptp-buffersize. He found also a solution to make all vxworks-cams ptp-ready incl. mode-switching (see DE-Trunk 465 and up). But OPT_LUA_CALL_NATIVE is required.

EDIT:
I think, I found the answer for "switch_mode_usb()"-result. It is a tricky tri-state result (mode-val on stack for switching ok and nil for any error at switching). Is that correct?

rudi

reyalp

Some ptp changes here https://chdk.setepontos.com/d/5793/37

I've attached a win32 build of ptpcam, along with source patches. This isn't really useful as is but it shows how to use the new commands.

edit:
patches are against mweerdens github source.

Ptpcam-chdk-1005.zip

53.38KB

reyalp

rudi
I think, I found the answer for "switch_mode_usb()"-result. It is a tricky tri-state result (mode-val on stack for switching ok and nil for any error at switching). Is that correct?

Seems so.

I think switch_mode_usb should not exist. set_record should know if PTP is active, and call C code switch_mode_usb if needed. Many older cameras don't need any special code.

(I agree set_record is a bad name, but I didn't want to confuse with shooting modes which already had get_mode and set_capture_mode...)

rudi

Hello,

for mode-switching in ptp (mode-command) we use for VxWorks the canon event functions. Can we this also use for DryOS-cams?

successful tested with A590:

//equal levent_set_record();
<conn> lua post_levent_to_ui("PressRecButton");post_levent_to_ui("UnpressRecButton")

//for example make a shoot
<conn> lua shoot()

//equal levent_set_play();
<conn> lua post_levent_to_ui("PressPBButton");post_levent_to_ui("UnpressPBButton")

The best is, all cams use only one routine. We don't need to find entrypoints for set_control_event, PB2Rec and Rec2PB on DryOS-cams. I think the two methods are a little bit different and the event-method is a better way (feel stable on tests).
The downside is OPT_LUA_CALL_NATIVE is required for OPT_PTP, but for VxWorks-cams it is already required.

rudi

ultimA

@reyalp: I saw the changes you made to the patch. While implementing, at first I also thought of using a bitfield. But the reason I didn't do that, and why I think it is not a good option right now, is that in my oppinion it complicates code for no foreseeable benefit. I understand that this theoretically makes adding new scripting languages possible, but as I have seen (I think it was this thread earlier) there is really no interest in adding UBasic support to PTP. And I also see no realistic chance of adding a third scripting language later on.

The reason it complicates code so much is that because you start supporting "scripting interfaces", as noted in the code comments. So to truely stay correct and open to future additions in the future, for every script-related PTP command you would need to supply a "target interface" as an argument (=an argument to state which scripting interface you are communicating to). This adds a lot of related problems, like what if there are multiple interface targets specified, how do you handle returning different errors in these cases and so on. And as stated, I cannot foresee supporting a scripting language in PTP other than LUA at the moment. So is this all worth it?

A relatively unrelated note: Maybe it would be better, instead of a ScriptSupport command, to have a general FeatureQuery command, that could return supported features of the current CHDK & camera in a bitfield. Not only for scripting, but games/zoom/native_calls/and other features.

reyalp

rudi
The best is, all cams use only one routine. We don't need to find entrypoints for set_control_event, PB2Rec and Rec2PB on DryOS-cams. I think the two methods are a little bit different and the event-method is a better way (feel stable on tests).
The downside is OPT_LUA_CALL_NATIVE is required for OPT_PTP, but for VxWorks-cams it is already required.

I don't understand why native call is required, you can use without levent native call.

It looks like the code you are using is identical to lua set_record, which doesn't work on (most ?) dryos cameras when USB is connected. I know I tried a bunch of things on D10 and couldn't get it to switch using levent.

@ultimA it seemed to me there was some interest in ubasic support, there are already some constants there for it. ExecuteScript already takes a type option (which is just a constant, not a bitfield) PTP_CHDK_SL_LUA

One reason to use ubasic is cameras with very little memory. Once your scripting optional stuff is done, people will have the option of ubasic only, and might still want ptp.

The way things are now, the "supported" bit will be (1<< (executescript number)). I thought about changing ExecuteScript to use the bitmask values, but as you say it doesn't make sense to pass more than one.

I would assume that if multiple script interfaces are supported, you can only use one at a time, at least until a major protocol change.

hwntw

Deleted by a craven coward

ultimA

reyalp
One reason to use ubasic is cameras with very little memory. Once your scripting optional stuff is done, people will have the option of ubasic only, and might still want ptp.

But this argumentation is only valid if OPT_LUA_CALL_NATIVE is not made a requirement for OPT_PTP.

reyalp
The way things are now, the "supported" bit will be (1<< (executescript number)).

What is "executescript number"?

reyalp

ultimA

reyalp
One reason to use ubasic is cameras with very little memory. Once your scripting optional stuff is done, people will have the option of ubasic only, and might still want ptp.

But this argumentation is only valid if OPT_LUA_CALL_NATIVE is not made a requirement for OPT_PTP.

There is no reason CALL_NATIVE should be required for OPT_PTP. At most you'd need to disable PTP_CHDK_CallFunction (although I'm not sure that's really needed)

Or we could retire PTP_CHDK_CallFunction completely, since you can do it from lua anyway.

reyalp
The way things are now, the "supported" bit will be (1<< (executescript number)).

What is "executescript number"?

PTP_CHDK_SL_LUA
PTP_CHDK_SL_UBASIC

Param2 of PTP_CHDK_ExecuteScript

Bernd R

Is there a wiki or a text explain how ptpcam work ?
I want transfer the chdk files to camera so i need not put SD-Card in Card reader always.

I search in google and see the option --get-all-files for testusage of ptpcam

seem my camera work with ptp.

when i type this in, LCD display get dark, and the LED blink for about 1 sec.
then come the output.

I can redo this command and work always same.

C:\Users\pc>E:\chdk\ptpcam.exe --get-all-files
Camera: Canon IXUS 1000HS

C:\Users\pc>

but some new files are not in c:\users\pc written

I dont like using the shell special windows shell, and i always forget how can in windows change the drive, maybe there is also a GUI for newest ptpcam, that allow the transfer of camera binary zip files to Camera easy ?

reyalp

Bernd R
Is there a wiki or a text explain how ptpcam work ?
I want transfer the chdk files to camera so i need not put SD-Card in Card reader always.

I search in google and see the option --get-all-files for testusage of ptpcam

seem my camera work with ptp.

when i type this in, LCD display get dark, and the LED blink for about 1 sec.
then come the output.

I can redo this command and work always same.

C:\Users\pc>E:\chdk\ptpcam.exe --get-all-files
Camera: Canon IXUS 1000HS

C:\Users\pc>

but some new files are not in c:\users\pc written

I dont like using the shell special windows shell, and i always forget how can in windows change the drive, maybe there is also a GUI for newest ptpcam, that allow the transfer of camera binary zip files to Camera easy ?

I have not had much luck with non-chdk commands in ptpcam. To upload/download files, use
ptp --chdk
this will give you an interactive prompt where you can use CHDK ptp commands, like
download A/DISKBOOT.BIN DISKBOOT.BIN
or
upload DISKBOOT.BIN A/DISKBOOT.BIn

The A/ is important when specifying filenames on the camera, it will probably crash if you leave it out.

Bernd R

I try several things out and here is the shell log of that.
upload a file test.txt(which have content of changelog.txt) give

unexpected return code 0x2ff
upload failed!

what are this error numbers ?
I test also without chdk start, there come same numbers, so it look as on IXus 1000 some functions are miss in chdk

I have use the 1004 trunk build, without your script patches.or is this wrong ?

I see too, that after i install usb dll for my Ixus 1000 for use with ptpcam, i can not use the IE explorer to read files from Camera.

before when i plug in the USB cable display get dark.when i start ptpcam with --chdk display get not dark.
when i start with --get-all-files display get dark and stay dark.

C:\Users\pc>e:\chdk\ptpcam.exe --chdk
error: camera has unsupported camera version 0.1; some functionality may be miss
ing or cause unintented consequences
<conn> download a/diskboot.bin diskboot.bin
unexpected return code 0x2fe
download failed!
<conn> download a/diskboot.bin diskboot.bin
unexpected return code 0x2fe
download failed!
<conn> upload diskbot.bin a/diskboot.bin
could not open file 'diskbot.bin'
upload failed!
<conn> upload test.txt a/test.txt
unexpected return code 0x2ff
upload failed!
<conn> upload test.txt a/test.txt
unexpected return code 0x2ff
upload failed!
<conn>

if you tell me what i should test on my Camera or add testcode in source i can do that.

rudi

Bernd R
<conn> upload test.txt a/test.txt

Write the camera driveletter uppercase e.g. upload test.txt A/test.txt

rudi

reyalp
I don't understand why native call is required, you can use without levent native call.

That's right. For mode-switching we don't need OPT_LUA_CALL_NATIVE. Thanks for your hint.

reyalp
It looks like the code you are using is identical to lua set_record, which doesn't work on (most ?) dryos cameras when USB is connected. I know I tried a bunch of things on D10 and couldn't get it to switch using levent.

Yes, it was my idea. It's a pity. It would be so easy to switch mode on DryOS cameras. Now, I will find the entrypoints for DryOS reference BINs.

rudi

Bernd R

rudi

Bernd R
<conn> upload test.txt a/test.txt

Write the camera driveletter uppercase e.g. upload test.txt A/test.txt

I try that but not work.
I also see, when remove USB cable error is same.so seem ptpcam do just nothing in --chdk

<conn> upload test.txt A/TEST.TXT
unexpected return code 0x2ff
upload failed!
<conn> upload test.txt A/TEST.TXT
unexpected return code 0x2ff
upload failed!
<conn> upload test.txt A/TEST.TXT
unexpected return code 0x2ff
upload failed!
<conn>

when i try this and have USB cable not connect i get this message.

C:\Users\pc>e:\chdk\ptpcam.exe --get-all-files
could not find any device matching given bus/dev numbers

C:\Users\pc>

I test when chdk not run, i get same message as when chdk run

C:\Users\pc>e:\chdk\ptpcam.exe --get-all-files
Camera: Canon IXUS 1000HS

C:\Users\pc>

reyalp

Bernd R
I try that but not work.
I also see, when remove USB cable error is same.so seem ptpcam do just nothing in --chdk

<conn> upload test.txt A/TEST.TXT
unexpected return code 0x2ff
upload failed!

My guess either you have not correctly implemented and enabled CHDK PTP, or your libusb driver is not set up correctly. There is some discussion of the latter in this thread.

C:\Users\pc>e:\chdk\ptpcam.exe --get-all-files
Camera: Canon IXUS 1000HS
C:\Users\pc>

CHDK only uses ptpcam as a convenient place to put some code. As I said earlier, I wasn't able to get many of the non-chdk ptpcam functions to work. It appears to me that ptpcam development was abandoned a long time ago.

Bernd R

>CHDK only uses ptpcam as a convenient place to put some code. As I said earlier, I wasn't able to get >many of the non-chdk ptpcam functions to work. It appears to me that ptpcam development was >abandoned a long time ago.

I dont know, ptpcam is not know in the wiki, there is only chdkcam which you tell not work on newer trunk.
what have change here, and what trunk begin not work on chdkcam ?
and what need change in chdkcam to get it working ?

there is for Ixus 1000 trunk 958 trunk 969 and trunk 1004 working

I can revert to an old trunk,

Do you get not such a message on ptpcam --chdk ?

"""""
error: camera has unsupported camera version 0.1; some functionality may be miss
ing or cause unintented consequences
""""""

I read some posts, but find no source of ptpcam

merry christmas too all

msl

Bernd R
I read some posts, but find no source of ptpcam

Here is the original source code by mweerden: https://github.com/mweerden/CHDK/tree/ptp (in tools/ptpcam)

And here you can find the code with reyalp's modifications: http://my-trac.assembla.com/chdkde/browser/trunk/tools/ptpcam

The last source also contains the necessary things (libUSB components) to compile ptpcam in CHDK-Shell: CHDK-Shell -> console -> make -C tools/ptpcam -f makefile.chdkshell

I wish also merry christmas all

« Previous Page Next Page »