chdkptp - alternative ptp client

reyalp

blackhole
Any exposure longer than 18 seconds or 9 seconds plus dark frame causes a timeout problem.

Thanks for checking that. I'll add options for the various timeouts when I get a chance.

On the shorter exposures everything works perfectly.

Just for completeness, this is using a590? What OS and chdkptp version?

reyalp

trig
1) eventually I get ERROR: too many nested source calls,

Yes, this isn't really the way to make a loop, for that you should use Lua
I would suggest doing it something like this:

!dofile('d:/path/to/interval.lua')

where interval.lua is something like

while true do
	status,err=cli:execute('rs -dng d:/path/to/downloaded/pics')
	if not status then break end
	sys.sleep(5000)
	status, err=cli:execute('rm DCIM -skip_topdirs')
	if not status then break end
	sys.sleep(2000)
end
cli:print_status(status,err)

This will run until there is an error. Unfortunately, there is currently no good way to check for input inside a chdkptp script without blocking, but with the above script, turning off the camera would end it.

Note The \ are changed to / in the path, otherwise they will be treated as escape characters.

2) once the script runs, there's no nice way to stop it.

Yeah, this is the input problem mentioned above. I would like to fix this at some point, but it's a bit complicated. In the gui, you could run your script from a timer, but that's more complicated code than I can write off the top of my head right now.

I assume you are using -dng and rm because your camera doesn't yet support jpeg remoteshoot? If so, let us know which camera you have, someone may be able to implement it for you.

lyzby

Regarding the problem of timing out using rs on the A590, the exposure is brief (fraction of a second), and the timeout takes about 10 seconds to occur.

I tried another camera on the Dockstar, an SX40HS. rs works fine, and "rs /var/www/test" puts the file, "test.jpg" in /var/www, where I can view it with a browser from my laptop.

Any further thoughts on getting this to work with the A590?

I'll try compiling chdkptp on a Ubuntu device tomorrow to see if that gets me any further (tho I really need to use the dockstar or other small headless device).

reyalp

lyzby
Regarding the problem of timing out using rs on the A590, the exposure is brief (fraction of a second), and the timeout takes about 10 seconds to occur.

Since a590 apparently works for blackhole, the most likely explanation seems like either a difference in settings (probably Canon firmware, but maybe CHDK) or a difference between the 100e and 101b ports.

I'll try compiling chdkptp on a Ubuntu device tomorrow to see if that gets me any further (tho I really need to use the dockstar or other small headless device).

Since the SX40 works, it seems quite unlikely it would be an OS specific issue. Would be good to confirm though.

edit:
I think I have found the bug
The filewrite task address was incorrect for 100e in the task hook. Try the attached test build.

a590-100e-1.3.0-3352-full-rstest-1.zip

795.01KB

blackhole

reyalp

blackhole
Any exposure longer than 18 seconds or 9 seconds plus dark frame causes a timeout problem.

Thanks for checking that. I'll add options for the various timeouts when I get a chance.

On the shorter exposures everything works perfectly.

Just for completeness, this is using a590? What OS and chdkptp version?

Yes, I'm talking about the a590, I tried with Win XP and Win 7 and there is no difference.
chdkptp client version is r438 and r468, also no difference in use.

lyzby

>I think I have found the bug ... The filewrite task address was incorrect for 100e in the task hook. Try the attached test build.

Yes--that fixed it. Thank you very much. rs works and "rs /var/www/test2" puts test2.jpg in /var/www, from which I can view it in the browser on my laptop, which is what I was looking for.

Thanks very much.

lyzby

I'm now trying a camera with more zoom--the SX120IS.

lua_shoot() works, but rs fails with "unsupported format". Here is the sequence with "set cli_verbose=2" turned on.

/usr/src/chdkptp/chdkptp -i -c
connected: Canon PowerShot SX120 IS, max packet size 512
con> lua set_zoom(20)
con 1> lua set_zoom(10)
con 2> rs
ERROR: not in rec mode
con 3> rec
con 4> lua set_zoom(12)
con 5> rs /var/www/test3
ERROR: unsupported format
con 6> set cli_verbose=2
con 6> rs
rs_init
ERROR: unsupported format
con 7> q
bye

What is needed to get this to work?

trig

Thanks so much reyalp, that works great.

reyalp
I assume you are using -dng and rm because your camera doesn't yet support jpeg remoteshoot? If so, let us know which camera you have, someone may be able to implement it for you.

That's right. It would be nice if I could get the images as jpegs. I'm using some old canon powershots: SD700 IS and SD850 IS.
Thanks again!

reyalp

lyzby
Yes--that fixed it. Thank you very much.

Thanks for confirming, and sorry it took so long to get to the root of the problem. I've checked this in to the trunk and stable builds.

lyzby
What is needed to get this to work?

Some additional code needs to be added for each port, same as for trig. This isn't huge job, so I or someone else here may be able to make builds if there is someone willing to test.

What Canon firmware version does your sx120is have?

Note that you should be able to get DNG files using remoteshoot with -dng on any CHDK supported camera. If jpeg support isn't implemented, the jpegs will still be saved to the card though.

trig
That's right. It would be nice if I could get the images as jpegs. I'm using some old canon powershots: SD700 IS and SD850 IS.
Thanks again!

What is the canon firmware version of your sd700 ?

lyzby

Yes, rs -dng worked.

:/usr/src/chdkptp/lua# /usr/src/chdkptp/chdkptp -i -c
connected: Canon PowerShot SX120 IS, max packet size 512
con> rec
con 1> rs /var/www/testdng -dng
con 4> q
bye

Firmware is GM1.00B.

I would be happy to test if someone can enable jpg downloading with rs for the SX120IS.

lyzby

Thanks to nafraf, rs is now working on the SX120IS, using the chdk build he posted on the thread for that camera.

My next question is--how can I switch to low-res to see where I am while remotely controlling pan, tilt, and zoom, and then switch back to hi-res to shoot?

Is it shown somewhere how to stream the lcd headlessly to a browser?

trig

reyalp
What is the canon firmware version of your sd700 ?

sd700-101a and sd850-100c.

Thanks

lyzby

Following nafraf's suggestion regarding resolution, I looked for set_prop information here:

http://chdk.wikia.com/wiki/UBASIC/propertyCaseUse

This text seemed relevant:

24 Image resolution: 0, 1, 2, 4, 8 for L, M1, M2, S, W (these are S3
designations: L is full resolution, M1 and M2 are progressively lower
resolutions, S is 640x480, and W is a â€œwide screenâ€ format: full
resolution width, but less than full resolution height).

I tried the following session:

/usr/src/chdkptp/chdkptp -i -c
connected: Canon PowerShot SX120 IS, max packet size 512
con> rec
con 1> lua set_prop(24,4)
con 2> rs /var/www/test19
con 5> lua set_prop(24,5)
con 6> rs /var/www/test20
con 9> lua set_prop(24,0)
con 10> rs /var/www/test21
con 13> q
bye

I thought this would set higher or lower resolution on my SX120IS, but test19.jpg, test20.jpg, and test21.jpg all were 1600x1200, in accordance with the M3 setting on the camera.

Is the form of my "lua set_prop(24,4) command correct, and if so, what do I need to do to get the settings to take? (NOTE: (24,5) looks wrong--valid settings are single-bit--0,1,2,4,8.)

nafraf

@lyzby
SX120 uses propset 3. Property 220 for Resolution chdk.wikia.com/wiki/PropertyCase

@trig
Test version for ixus800_sd700-101b/101a (filewrite task and simpler loader support) in attachment.

lyzby

Thank you, nafraf--"lua set_prop(220,x)" works for setting the resolution on the SX120IS with chdkptp.

220,4 sets it to vga mode (640x480); 220,0 is full resolution, 10 megapixels, 3648x2736; 220,1 is 6 megapixels, 2816x2112; 220,2 is 4 megapixels, 2272x1704; 220,3 is 2 megapixels, 1600x1200; 220,5 is widescreen, 3648x2048.

Other cameras use different property sets--see: http://chdk.wikia.com/wiki/PropertyCase

/usr/src/chdkptp/chdkptp -i -c
connected: Canon PowerShot SX120 IS, max packet size 512
con> rec
con 1> lua set_zoom(25)
con 2> lua set_prop(220,4)
con 3> rs /var/www/test23
con 6> lua set_prop(220,0)
con 7> rs /var/www/test24
con 10> q
bye

lyzby

What command line arguments should I use to set resolution and zoom, shoot with rs, disconnect, quit, and then be able to do it again?

This is what I tried (3 sequences):

root@dock84:/usr/src/chdkptp/lua# /usr/src/chdkptp/chdkptp -c -e"rec" -e"lua set_prop(220,4)" -e"lua set_zoom(10)" -e"rs /var/www/current" -e"dis" -e"q"
connected: Canon PowerShot SX120 IS, max packet size 512
ERROR: already in rec
bye
root@dock84:/usr/src/chdkptp/lua# /usr/src/chdkptp/chdkptp -c -e"rec" -e"lua set_prop(220,4)" -e"lua set_zoom(5)" -e"rs /var/www/current" -e"dis" -e"q"
connected: Canon PowerShot SX120 IS, max packet size 512
ERROR: already in rec
ERROR: a script is already running
bye
root@dock84:/usr/src/chdkptp/lua# /usr/src/chdkptp/chdkptp -c -e"rec" -e"lua set_prop(220,4)" -e"lua set_zoom(5)" -e"rs /var/www/current" -e"dis" -e"q"
connected: Canon PowerShot SX120 IS, max packet size 512
ERROR: already in rec
bye

The camera stays in rec mode (should I put "play" at the end, or can I rely on it's being in rec mode after the first time)?

When I get "ERROR: a script is already running" it doesn't shoot. If I re-enter the exact same command, that error doesn't occur and it does shoot. How do I terminate the running script?

What is the proper way of doing this without getting errors (assuming we'll really always be in "rec" mode)?

(Note that it did shoot the first and 3rd times.)

SX120IS

reyalp

lyzby
Is it shown somewhere how to stream the lcd headlessly to a browser?

There isn't currently a way to do this. You can run the GUI remotely with VNC or X, but performance is likely to be pretty poor.

It should be relatively easy for someone with the required programming skills to make something that reads the live view output and converts it to something an existing video streaming system accepts.

lyzby

reyalp

lyzby
Is it shown somewhere how to stream the lcd headlessly to a browser?

There isn't currently a way to do this. You can run the GUI remotely with VNC or X, but performance is likely to be pretty poor.

It should be relatively easy for someone with the required programming skills to make something that reads the live view output and converts it to something an existing video streaming system accepts.

Where is the live view output documented?

reyalp

lyzby
Thank you, nafraf--"lua set_prop(220,x)" works for setting the resolution on the SX120IS with chdkptp.

Using the propcase module is highly recommended. Then you can refer to the propcases by name, which is not platform dependent, like
lua set_prop(require'propcase'.RESOLUTION,x)

lyzby
The camera stays in rec mode (should I put "play" at the end, or can I rely on it's being in rec mode after the first time)?

It should stay in whatever mode you last put it in. Using -e commands, the error from rec should be harmless (this is not case for command files used with -r, in those an error will prevent all subsequent commands from completing.)

When I get "ERROR: a script is already running" it doesn't shoot. If I re-enter the exact same command, that error doesn't occur and it does shoot. How do I terminate the running script?

You are using lua ... which does not wait for the script to finish. Since set_zoom takes a significant amount of time, it isn't finished when you try to run the rs, so you get the "script already running" error.

To make chdkptp wait for the script, use luar instead.

You shouldn't need -e"dis" and -e"q", if you don't use -i it will automatically quit when the commands are done.

reyalp

lyzby
Where is the live view output documented?

In the source https://tools.assembla.com/svn/chdk/trunk/core/live_view.h

The chdkptp source has examples of how to decode it, in https://tools.assembla.com/svn/chdkptp/trunk/liveimg.c and https://tools.assembla.com/svn/chdkptp/trunk/lua/gui_live.lua

You could use the liveimg.c code to convert to RGB, but it currently only supports planar output (r, g and b each in their own buffer) and scaling is handled by the GUI code.

You would also have to arrange to get chdkptp to send the live view data while still accepting commands, which is not currently possible in the cli.

« Previous Page Next Page »