A590IS porting...

blackhole

Enabling CAM_EV_IN_VIDEO no adverse effects on the functionality of other features. Memory consumption of 800 bytes is not terrible.

a590_CAM_EV_IN_VIDEO-trunk2951.patch

727b

nafraf

dvip
You may also want to take a look at this bug.
If you set:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Shoot]
it behaves as:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Always]

@dvip
I only see problem with zoom value, behavior of other values are right.
Using [Shoot] parameters appear when you press half_shoot and dissappear after full_shoot. Is that what you are seeing?

This patch should solve zoom value behavior. Please test it.

Index: core/gui_osd.c
===================================================================
--- core/gui_osd.c	(revision 2951)
+++ core/gui_osd.c	(working copy)
@@ -363,7 +363,7 @@
 
     //gui_osd_calc_expo_param();
 
-    if (conf.values_show_zoom)
+    if (conf.values_show_zoom && (showtype==1) )
     {
         int fl, zp=shooting_get_zoom(), fl1=get_focal_length(zp);     
         switch (conf.zoom_value)

dvip

@nafraf,

If on the chdk menu you set:

CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Shoot]
Show Zoom [.]
Zoom Value [EFL]

"Z: ## mm" should show on the screen only when half press (camera_info.state.is_shutter_half_press).

The way it is now, both "Show Misc Values [Shoot]" and "Show Misc Values [Always]" behave the same way, they both always show "Z: ## mm" on the screen.

Perhaps the problem is in the logic of the gui_draw_osd() function.

nafraf

dvip
Perhaps the problem is in the logic of the gui_draw_osd() function.

Please test this version.

dvip

@nafraf, that did it! Thanks! 😁

nafraf

dvip
@nafraf, that did it! Thanks! 😁

I applied the patch I posted previously. Reply #903

dvip

I wonder if the same work that was done in this A720 patch here:

https://chdk.setepontos.com/d/650/1193

can be done for the a590IS.

I have noticed that values like:

-----------------
#undef CAMERA_MIN_DIST
#define CAMERA_MIN_DIST 100 // Override min subject distance
#undef CAMERA_MAX_DIST
#define CAMERA_MAX_DIST 52855 // Override max subject distance

#define CAM_HAS_FILEWRITETASK_HOOK 1

// #define REMOTE_SYNC_STATUS_LED 0xC0xxyyyy // specifies an LED that turns on while camera waits for USB remote to sync

-----------------

Don't look right. I think CAMERA_MIN_DIST can be 52 and #define REMOTE_SYNC_STATUS_LED is commented out... not an expert in this but would like to know if this is correct.
I posted this in the wrong forum and moved it here.

nafraf

dvip
Don't look right. I think CAMERA_MIN_DIST can be 52 and #define REMOTE_SYNC_STATUS_LED is commented out... not an expert in this but would like to know if this is correct.
I posted this in the wrong forum and moved it here.

Hi, how did you get 52 value? Did you use the script posted here?

Blue LED is set as REMOTE_SYNC_STATUS_LED in attached file, please test it and report.

a590-101b-1.2.0-full.zip

654.9KB

waterwingz

nafraf
Blue LED is set as REMOTE_SYNC_STATUS_LED in attached file, please test it and report.

REMOTE_SYNC_STATUS_LED enables CHDK to activate one of the camera's LED while CHDK is waiting to complete the USB sync operation. This is for visual confirmation that its waiting for sync only - its not needed for any CHDK function to work and can be safely commented out.

To test, you will need a USB remote (or the cable that connect your camera to your computer via USB). Setup CHDK like this : http://chdk.wikia.com/wiki/USB_Remote#Enable_Sync and shoot by applying power to the USB port ( switch unit or USB PC cable ). While the power is connected, the LED indicator you selected with the #define should be illuminated. It should also turn off when you remove the USB power.

dvip

@nafraf, I got the 52 by setting the lens to MF and using lua.
Something like this:

post_levent_for_npt("PressSw1AndMF")
set_focus(52)
sleep(1000)
shoot()

I can focus to about two inches which is the min according to the camera's manual.

Also, this basic script returns 51:

press "shoot_half"
sleep 1000
get_focus f
sleep 1000
print "f: ", f
sleep 3000
release "shoot_half"

So it is either 51 or 52. What do you think?
I couldn't set it to 51 from the chdk menu, the min there is 100. Perhaps it should be 51?
Don't know if the infinity value is correct either. The basic script above returns 65535 if I set the lens to infinity in MF and run the script.

@waterwingz, sadly, I don't have a USB remote to test it.

Thanks guys! 😀

waterwingz

dvip
@waterwingz, sadly, I don't have a USB remote to test it.

All you need is a USB cable suitable for connecting your camera to your PC. Plugging & unplugging the cable does the same thing as pressing the button on a USB remote.

blackhole

@nafraf
@waterwingz
Does not work, LED is not activated.

nafraf

@blackhole, dvip
To test remote sync status LED, please use this setup on remote parameters menu
Enable Remote [ x ]
Switch Type [One Push]
Control Mode [Normal]
Enable Synch [ x ]

Plug USB cable, blue LED should turn on. (0xC02200c4 // direct-print (blue) from wiki)
Unplug USB cable, LED should turn off and camera should take a photo.

About CAMERA_MIN_DIST, 52 can be used according to dvip tests. But I'm not sure about CAMERA_MAX_DIST (could it be >65535?), version in attachment is set up for sdminmax.lua test. Note that script should be run 4-5 times, and use the largest value.

a590-101b-1.2.0-sdminmax-test.zip

654.91KB

a590_sync_led.patch

1.39KB

dvip

@nafraf,
Using sdminmax.lua and a590-101b-1.2.0-sdminmax-test.zip
I get:

min 51
max 1

dvip

>Enable Remote [ x ]
>Switch Type [One Push]
>Control Mode [Normal]
>Enable Synch [ x ]
>
>Plug USB cable, blue LED should turn on. (0xC02200c4 //
>direct-print (blue) from wiki)
>Unplug USB cable, LED should turn off and camera should take
>a photo.

@nafraf,
The LED (direct-print (blue)) is always off.
The camera does take a shot. So it works fine with the USB cable.

There is no change in the LED (direct-print (blue)) state.
It's always off. Unless you use raw, in that case, it turns on while saving the raw file.

blackhole

About CAMERA_MIN_DIST, 52 can be used according to dvip tests. But I'm not sure about CAMERA_MAX_DIST (could it be >65535?), version in attachment is set up for sdminmax.lua test. Note that script should be run 4-5 times, and use the largest value.

Photographers point of infinity for a lens calculated by multiplying "f" number of lenses with 1,000."f" number for the A590 is 5.8, so that the point of infinity is 5.8m or 5800mm, which corresponds to those displayed in Canon GUI, where the point of infinity is shown as approximately 6m. In that case 52855 or 65535 are incorrect value if express the distance in millimeters.

ahull

waterwingz

dvip
@waterwingz, sadly, I don't have a USB remote to test it.

All you need is a USB cable suitable for connecting your camera to your PC. Plugging & unplugging the cable does the same thing as pressing the button on a USB remote.

... assuming the other end of the USB cable is connected to your PC (and the PC is running), as waterwings suggested.... simply plugging in one end of a USB cable to the camera, and leaving the other end disconnected will have no effect. I presume you understood this, but thought it worth checking.

dvip

@blackhole,
It is still not clear what infinity is for the A590is.
get_focus returns 65535.

@ahull,
As indicated in my previous posting the camera does take a shot. So it works fine with the USB cable. Plugging and unplugging the cable does the same thing as pressing the button. When doing this, in my case, the direct-print (blue) LED is always off.

waterwingz

dvip
As indicated in my previous posting the camera does take a shot. So it works fine with the USB cable. Plugging and unplugging the cable does the same thing as pressing the button. When doing this, in my case, the direct-print (blue) LED is always off.

At the risk of repeating myself (and everyone) else, the LED will only light when USB sync mode is enabled and 5V has been applied to the USB power pins.

When using "One Push"mode, the camera behaves a little differently when sync is enabled. With sync disabled, it will do a "half press" when power is applied and a "full press" when its removed. With sync enabled, it also does the "half press" when power is applied but moves immediately to a full press once the camera is ready. The full press completes when power is released.

While these sound very similar, you will notice one big difference. When sync is enabled, the LCD goes black when the USB power is applied. When sync is not enabled, the LCD will stay on (or active).

dvip

>At the risk of repeating myself (and everyone) else, the LED
>will only light when USB sync mode is enabled and 5V has
>been applied to the USB power pins.

Ok, only with the 5V applied to the USB power pins the LED will light.
I tested it just with a plain USB cable since I don't have the other.
Perhaps someone with this:
http://images1.wikia.nocookie.net/__cb20080528132342/chdk/images/e/e4/Remoterelease1rastercy6.gif
can test it with 5V applied to the USB power pins.

« Previous Page Next Page »