Quote from: Paco on 30 / September / 2014, 01:01:57It is supposed to work that way but on mine it doesn't. In either mode, the shutter triggers as soon as +5V is applied. Normal mode does not wait until it is removed for some reason. (I am simply plugging and unplugging the USB cable to test this feature out)That is quite unusual. I'm a little bit familiar with the USB remote code and I have access to six different camera models - none of which do that. However, I guess it's possible here is an error in the port for your A530 - the USB status bit might be inverted (for example).Can you post a screen shot of the USB remote menu showing your setup? For example, do you have "Sync" enabled ? If so, the CHDK code will initiate the shot when the 5V is applied )but it won't complete until it is removed).
It is supposed to work that way but on mine it doesn't. In either mode, the shutter triggers as soon as +5V is applied. Normal mode does not wait until it is removed for some reason. (I am simply plugging and unplugging the USB cable to test this feature out)
How do you get a screenshot?
The manual states that "Enable Script Start Tells CHDK to activate the currently loaded script when the USB remote performs a full press." But in Normal mode, full press is not accomplished until the signal is off, and yet the script was being started when USB went high, or at half press.
Quote from: Paco on 30 / September / 2014, 10:26:34How do you get a screenshot?Use chdkptp liveview mode if you want to do it directly on your PC. Otherwise take an actual picture with a second camera / mobile phone.
QuoteThe manual states that "Enable Script Start Tells CHDK to activate the currently loaded script when the USB remote performs a full press." But in Normal mode, full press is not accomplished until the signal is off, and yet the script was being started when USB went high, or at half press.QuoteI'll correct the manual.
I'll correct the manual.
It seems that is only for Windows.
So it's the manual and not the firmware or my camera.
Quote from: Paco on 30 / September / 2014, 13:17:05 It seems that is only for Windows.Nope. http://chdk.wikia.com/wiki/PTP_Extension#Platformshttps://www.assembla.com/spaces/chdkptp/wiki/Install
However, I am curious about how the "default" script was able to take a picture (if that in fact is what happened).
Yes it did and that's a very good question. Maybe it's because default.bas is an empty file so CHDK reverts to default behavior? That's what I would expect for the default script. I mean you wouldn't want it to do something unexpected.
The default script is not supposed to do anything - never mind actually take a picture. I'm guessing that because you had both the "launch script when remote pressed" option and the "normal control mode" enabled, then you got what you asked for - both actions!
but CHDK is still active, which is why remote triggering still works.
Quote from: zeno on 30 / September / 2014, 18:10:09 but CHDK is still active, which is why remote triggering still works.This applies to a lot of other CHDK functionality too - things like exposure overrides, subject distance overrides, zebra, histogram, edge overlay all work when you are not in CHDK <ALT> mode.
Started by Coutts « 1 2 » Creative Uses of CHDK
Started by Idrove « 1 2 » General Chat
Started by careyer Firmware Dumping
Started by smilem General Help and Assistance on using CHDK stable releases
Started by hroldan Hotwire! Hardware Mods, Accessories and Insights
