S95 Porting Thread

Microfunguy

Post the entire script you are using.

FreeFlow

I named it cr4sdm.bas since I have many version your using....
=====================

@title CAMremote-SDM_4
rem by VP-Systems
rem 25-04-2010

m=0

rem CAMremote-2 (Mini USB connector). Control Method: USB/CHDK+
print "CR: USB/CHDK+"
while 1
do
a = get_usb_power
until a>0
if a<2 then gosub "shoot" else if a<4 then gosub "focus" else if a<6 then gosub "focusoff" else if a<8 then gosub "zin" else if a<10 then gosub "zout" else if a<12 then gosub "rec_video" else if a<14 then gosub "avup" else if a<16 then gosub "avdn" else if a<18 then gosub "tvup" else if a<20 then gosub "tvdn" else if a<22 then gosub "stop_video" else if a<42 then gosub "lensoff" else if a<52 then gosub "pwroff"

a=0
wend
end

:shoot
print "shoot:";a
press "shoot_full"
sleep 1500
release "shoot_full"
release "shoot_half"
return

:rec_video
if m=1 then return
movie_mode
sleep 2000
print "rec_video:";a
press "shoot_full"
sleep 1500
release "shoot_full"
release "shoot_half"
m=1
return

:stop_video
if m=0 then return
print "stop_video:";a
press "shoot_full"
sleep 1500
release "shoot_full"
release "shoot_half"
m=0
record_mode
sleep 2000
return

:video
if m=0 then gosub "rec_video" else gosub "stop_video"
return

:focus
print "focus:";a
press "shoot_half"
return

:focusoff
print "release:";a
release "shoot_half"
return

:zin
print "zoomin:";a
press "zoom_in"
sleep 200
release "zoom_in"
release "shoot_half"
return

:zout
print "zoomout:";a
press "zoom_out"
sleep 200
release "zoom_out"
release "shoot_half"
return

:avup
print "Av+:";a
set_av_rel 0+1
return

:avdn
print "Av-:";a
set_av_rel 0-1
return

:tvup
print "Tv+:";a
set_tv_rel 0+1
return

:tvdn
print "Tv-:";a
set_tv_rel 0-1
return

:capture
print "capture:";a
press "shoot_full"
sleep 500
release "shoot_full"
release "shoot_half"
sleep 1500
return

:lensoff
print "lensoff not supported"
shut_down
sleep 1000
return

:pwroff
print "poweroff"
shut_down
sleep 1000

return

Microfunguy

The CHDK+ pulse widths vary by quite a small amount at the bottom end.
You cannot really guarantee SDM (or CHDK) will measure them with the required precision.

We will try 'tweaking' the values slightly and if that is not reliable use the more widely-spaced CHDK profile pulses.

Replace the line in your script with this SINGLE line :-

if a<3 then gosub "shoot" else if a<5 then gosub "focus" else if a<7 then gosub "focusoff" else if a<9 then gosub "zin" else if a<11 then gosub "zout" else if a<13 then gosub "rec_video" else if a<15 then gosub "avup" else if a<17 then gosub "avdn" else if a<19 then gosub "tvup" else if a<21 then gosub "tvdn" else if a<41 then gosub "stop_video" else if a<50 then gosub "lensoff" else if a<52 then gosub "pwroff"

achillies

@microfunguy - in previous posts, freeflow listed values flowing across the screen whe he pressed a button (make believe values, but for example he pressed remote button 1 and reported a=4,4,5,6). If he could press each button, one by one and report the largest and smallest values for each press (and the button that was pressed), that would help you wouldn't it?

Microfunguy

achillies
that would help you wouldn't it?

Yes, but the above script should be printing the 'a' values anyway.

achillies

@FreeFlow - I really am curious. If it's not too much trouble, can you press each button (1-7) and then write down the numbers for each button. Not necessarily ALL the numbers - if they are all the same for a particular button, one number will do, but if they vary alot try to get max, min and avg.

@microfunguy - This is all dependent on script execution speed, right?

Microfunguy

achillies
This is all dependent on script execution speed, right?

In the sense that a single uBasic statement is executed every 10 msec but some may have to wait longer because other tasks interrupt.

That makes measurement of USB pulse-widths subject to errors of a number of 10 msec.

FreeFlow

I first pressed button 7 and it focus/shoot. Then I pressed Button 5 and it is zooming IN and button 6 is zooming out. They are still jittery and not direct with the press of the buttons.When you press the zoom buttons it does show the zoom indicator on the screen. Pressing button 6 does zoom in and out. it show that on the screen. the 5 button show in and release I also Pressed 8+7 and it changed it to Movie Mode focus and started to record. #7 press will STOP the record.

achillies

It sounds like it is VERY close to working.. do you still see the "a" values on the screen (and can you write them down)?

BTW, this wil never quite be like a camcorder, or like having the camera in your hand. The way everything "communicates", there is always a slight delay. You'll get use to it (and probably pretty good at it too!).

FreeFlow

@achillies
Button8 = nothing on screen
Button7 = shoot:1 and shoot:2
Button6 = zoomout:9 and zoomout 10
Button5 = zoomin: 7 and release:6
Buttons 1-4 servos nothing to screen

achillies

@Freeflow - I understand what the button function is and what they do.. in previous posts, you were telling microfunguy some numbers (something like15,17,15,16,17,17,15). when you pressed a button. THAT is what I'm looking for (if possible - I don't know how you guys got them on the screen.. ~~I'll read back~~) like in this message -> https://chdk.setepontos.com/d/5641/564

Microfunguy
In the sense that a single uBasic statement is executed every 10 msec but some may have to wait longer because other tasks interrupt.
That makes measurement of USB pulse-widths subject to errors of a number of 10 msec.

CHDK/CHDK + must be related to processor type/speed. Does ubasic always have that 10ms (in vxworks, digic3, digic4, etc)?

@microfunguy - looking back at those times (from the post mentioned above), that falls within the usb/CHDK method times for those keys.

Microfunguy

Use the following SINGLE line with the ordinary CHDK (not CHDK+) profile :-

if a<6 then gosub "shoot" else if a<12 then gosub "focus" else if a<17 then gosub "focusoff" else if a<24 then gosub "zin" else if a<30 then gosub "zout" else if a<37 then gosub "rec_video" else if a<43 then gosub "avup" else if a<49 then gosub "avdn" else if a<55 then gosub "tvup" else if a<61 then gosub "tvdn" else if a<67 then gosub "stop_video" else if a<73 then gosub "lensoff" else if a<76 then gosub "pwroff"

Microfunguy

achilliesDoes ubasic always have that 10ms (in vxworks, digic3, digic4, etc)?

Yes.

As I understand it, it is determined by _SleepTask(10) in the keyboard code.
_SleepTask() is a Canon firmware function whose parameter value is in msec.

FreeFlow

Running with the CHDK and the single line from post 2487 seems to be a little better. it works the best when you quickly press/release buttons 5 or 6. If you hold them down they still stop then move a bit more then stops and moves a bit more...etc.
One other thing is the zoomin and the zoomout it will randomly zoom its movement then backup to park when you press either button 5 or 6 and other times it will zoom and stop at it's distance that it moved. In other words, it will back up just a little randomly.
On another note: I can't seem to get it from MOVIE mode back to photo mode

Microfunguy

When it is behaving randomly are you keeping a note of the 'a' values ?

My last time of asking ... how do you use the 8+ combination buttons ?

I ask because you have to use that combination to start/stop video recording.

FreeFlow

I have been looking at them zoomin and zoomout and release #'s to see if it happens with the same # each time. I will let you know on that.

Playing around a little bit with the 8+ is... In that software you can create 7 different profiles. One on earh tab. then when I click Save Setting to CAMremote it has 7 stored in it. LIKE: Profile #1 might have "Any (CHDK Compatible) Camera and Control Method [USB/CHDK+] and profile #2 might have "Any (CHDK Compatible) Camera and Control Method [USB/CHDK]. Then when i'm all connected to the camera I can press and hold button #8 for 6 sec then the LED's on the CR start flashing and while it's flashing I can choose to press 8+2 for the CHDK profile or do it again and I can choose 8+1 to go back to CHDK+ profile. The LED's light up in accordance to them profiles. I haven't charted all that or figured it out. I would think Linnar has all that Info since he is the man getting the CR hardware.
Then you can also DO: Press quickly 8+7 and it takes me to MOVIE Mode. Lot of combo's..???

Microfunguy

FreeFlow
Then you can also DO: Press quickly 8+7 and it takes me to MOVIE Mode. Lot of combo's..???

Right, that is what I needed to know.

Does the same combination stop video recording and return to Record mode ?

With your camera in Tv mode, set a shutter speed and take a photo.

Now see if you can change that shutter speed a certain amount with 8+1 and 8+2.
Take a photo with button 7 to find out.

FreeFlow

I am using Button #7 to start and stop the video and to shoot a photo. Button 8+7 quickly changes from photo to movie mode on the camera. currently I can get it to switch back from movie to photo mode.

achillies

"The LED's light up in accordance to them profiles. I haven't charted all that or figured it out." <- the LED combos are listed in this post https://chdk.setepontos.com/d/5641/603 for each profile. But if you set all of the profiles to be the same for now, it isn't important.

Microfunguy

FreeFlow
I am using Button #7 to start and stop the video and to shoot a photo. Button 8+7 quickly changes from photo to movie mode on the camera. currently I can get it to switch back from movie to photo mode.

Yes, the problem is the script does not correspond with the key designations.

Only one key is shown for stop/start video.

Change this bit :-

if a<37 then gosub "rec_video"

to :-

if a<37 then gosub "video"

I think 8+7 should then start/stop video.

« Previous Page Next Page »