I seems to me that CHDK for this camera/firmware isn't properly connecting the actual port to the "remote" variable.
Enabled remote and ran script using the 'Play' button. Sorry, no response.
Results for 1.2.0-2018 are:Enable only - no responseEnable, onepush - no responseEnable, onepush, normal - no responseEnable, twopush, normal - no responseEnable, onepush, quick - no responseEnable, onepush, zoom - no response to 1, 2, 3, 4, or 5 quick (manual) pulses
int get_usb_bit(){ return( (physw_status[2] & USB_MASK) == USB_MASK) ; // don't call _kbd_read_keys_r2(physw_status)}
YAHOO ...THANK YOU WATERWINGZ!
OnePush, TwoPush with Normal and Quick work perfectly. I think it is possible to confuse the camera by initiating a new sequence too soon.Zoom - one, two and three pulses work properly. 4 and 5 pulses will begin zooming, then camera will turn off. I tried 4 and 5 from zoom centered, to see if how long it takes to achieve full zoom is the issue. Doesn't seem so. Camera doesn't always turn off, so I think that it may sometimes interpret my pulse train as a 1 or 2 pulses. I can only pulse so fast by hand. I don't have the stuff to generate pulses electronically at this time.In step zoom, the lens actually moves on the falling edge of the pulse. Also, as a note, the first use of remote zoom pulse/s disables the zoom buttons on the camera- until powered down and back up.The best news is that REMOTE.BAS, the little loop that looks at the "remote button" then "shoots" works properly. Most previous versions did not recognize that the remote button had been pushed (I didn't check you last quick & dirty patch). So now creative ways to to a bunch of stuff - including a more sophisticated zoom control.
I think it is possible to confuse the camera by initiating a new sequence too soon.
Zoom - one, two and three pulses work properly. 4 and 5 pulses will begin zooming, then camera will turn off. I tried 4 and 5 from zoom centered, to see if how long it takes to achieve full zoom is the issue. Doesn't seem so. Camera doesn't always turn off, so I think that it may sometimes interpret my pulse train as a 1 or 2 pulses. I can only pulse so fast by hand. I don't have the stuff to generate pulses electronically at this time. In step zoom, the lens actually moves on the falling edge of the pulse.
Also, as a note, the first use of remote zoom pulse/s disables the zoom buttons on the camera- until powered down and back up.
The best news is that REMOTE.BAS, the little loop that looks at the "remote button" then "shoots" works properly. Most previous versions did not recognize that the remote button had been pushed (I didn't check you last quick & dirty patch). So now creative ways to to a bunch of stuff - including a more sophisticated zoom control.
Looking at the patch waterwingz posted, GetBatteryTemperature was disabled in the current svn code. Can someone please check in waterwingz build whether the camera crashes if you change the "show temperature" setting in the osd menu to "battery" ?
Started by mr_waiyawit General Help and Assistance on using CHDK stable releases
Started by dezza Feature Requests
Started by jannoon028 DryOS Development
Started by smirnov992 Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by tqft DryOS Development