A590IS porting...

dvip

peabody,
waterwingz is doing some set_focus() work. Let's hope he or someone can find this out.
I'm not sure if infinity SD is 47533 or 65535 either.

waterwingz

peabody
Back in July I raised a question about the subject distance when the camera is in manual focus at infinity. If I set the camera that way manually, and go into Alt mode, the display shows SD as 47533 in CHDK v1.2. But in v1.3, it shows SD as 65535. Can someone explain where these numbers come from? Are they being read from the camera, or are they just defined in camera.h or some other file? In overrides menu, you can select Inf for subject distance, but it's not clear what value is being used as the Inf value. Can someone please clarify what's going on here?

dvip
peabody,
waterwingz is doing some set_focus() work. Let's hope he or someone can find this out.
I'm not sure if infinity SD is 47533 or 65535 either.

With the huge depth of field on the little P&S camera lenses, it does not really matter if the focus setting is 47 meters or 65 meters as both are effectively focused at infinity either way.

dvip

Possible in the future to be able to control CAM_COLORMATRIX1 from the chdk menu or a script?
Would it affect both jpg/dng, or just the jpg?

philmoz

dvip
Possible in the future to be able to control CAM_COLORMATRIX1 from the chdk menu or a script?
Would it affect both jpg/dng, or just the jpg?

It would be possible; but why would you want to?
It would only affect the DNG file.

Phil.

dvip

>It would be possible;

Ok

>but why would you want to?

Just to have different CAM_COLORMATRIX1 on the user menu and tweak things from there.

>It would only affect the DNG file.

Ok

mngc

I have problem with external power supply. What diameter original Canon ACK-800 power plug?
I tested power plug 2.35x0.7mm, it works, but not good (contact flawed because wobble). I think original connector bigger, the hole approx. 2.8mm.

Center pin positÃve, voltage not critical stable 3v works good. Minimum 2v required. Original adapter 3.15v.

peabody

2.35 x 0.7 sounds right. It's supposedly the EIAJ-01 connector.

HrClausen

I am using CHDK 1.4.1, rev. 4742.

I experience that whenever I use set_zoom(), The camera locks up once it has completed the zoom.

Has anyone experienced something similar?

waterwingz

HrClausen
I experience that whenever I use set_zoom(), The camera locks up once it has completed the zoom. Has anyone experienced something similar?

Unfortunately, this is an old story. More information here : set_zoom problems in uBASIC & Lua scripts

There are a couple of build option that can help. I'll take a look if you are willing to do some testing.

HrClausen

I'd be glad to do some testing, if you have any ideas on how to fix it.

reyalp

HrClausen
I'd be glad to do some testing, if you have any ideas on how to fix it.

One cause can be the CHDK trying to re-focus after zooming. If your are currently using AF, you could try using MF instead. If you have some kind of continuous autofocus enabled, turning it off might help. Even if it isn't a solution for your situation, it might help narrow down the problem

Posting a romlog from the crash might also be useful: http://chdk.wikia.com/wiki/Debugging#Camera_crash_logs_.28romlog.29

In the thread that waterwingz linked, A590 is reported as working, so there may be another factor https://chdk.setepontos.com/d/7071/5

waterwingz

reyalp

HrClausen
I'd be glad to do some testing, if you have any ideas on how to fix it.

One cause can be the CHDK trying to re-focus after zooming. If your are currently using AF, you could try using MF instead. If you have some kind of continuous autofocus enabled, turning it off might help. Even if it isn't a solution for your situation, it might help narrow down the problem

Posting a romlog from the crash might also be useful: http://chdk.wikia.com/wiki/Debugging#Camera_crash_logs_.28romlog.29

In the thread that waterwingz linked, A590 is reported as working, so there may be another factor https://chdk.setepontos.com/d/7071/5

@reyalp : the A590 is an old port. Is it worth trying the newer options ?

    #undef  CAM_NEED_SET_ZOOM_DELAY             // Define to add a delay after setting the zoom position before resetting the focus position in shooting_set_zoom                                  
    #undef  CAM_USE_ALT_SET_ZOOM_POINT          // Define to use the alternate code in lens_set_zoom_point()
    #undef  CAM_USE_ALT_PT_MoveOpticalZoomAt    // Define to use the PT_MoveOpticalZoomAt() function in lens_set_zoom_point()

@HrClausen : did you try testing with the script posted here :
Re: set_zoom problems in uBASIC & Lua scripts - help wanted with testing

reyalp

waterwingz
@reyalp : the A590 is an old port. Is it worth trying the newer options ?

Since it was previously reported as working by blackhole, I kind of suspect it's a different problem.

HrClausen

I tried waterwings' test script. It worked well until i added 'switch_mode_usb(1)' at the start of the script. 

Then the screen vent black (but still on). I could stop the script, using the shoot button, but the power button was not responsive. The only way to get the camera back to normal was to take out the batteries.

ROMLOG.LOG

3.19KB

reyalp

HrClausen
I tried waterwings' test script. It worked well until i added 'switch_mode_usb(1)' at the start of the script.

Was the camera not in record mode (picture taking, not playback) when it "worked"?

The camera needs to be in record mode for any of the zoom functions to have effect. However, unless you have the camera connected to USB at the time, you should use the normal control on the camera or the set_record function

HrClausen

If I have the camera in record mode and use switch_mode_usb(1) it crashes. If it is in preview mode and I use switch_mode_usb(1), it works.

reyalp

HrClausen
If I have the camera in record mode and use switch_mode_usb(1) it crashes. If it is in preview mode and I use switch_mode_usb(1), it works.

Thanks for the clarification. Was your original problem with set_zoom crashing also caused by this, or is it still unresolved?

FWIW, you should not use switch_mode_usb(1) if the camera is already in record mode, or if you do not have the camera connected to USB. If your script calls switch_mode_usb(1) it should use get_mode() first to check if a switch is needed.

Actually, in all normal cases you should use set_record instead of switch_mode_usb, since it detects whether USB is connected and works like switch_mode_usb() if needed.

HrClausen

Thanks, unfortunately it did not solve my original problem.

My application not starts up with the following

set_remote_timing(1000)
usb_force_active(true)
set_record(true)
while not get_mode() do
  sleep(10)
end
set_exit_key("no_key")

Then it receives commands via USB. However when it receives zoom commands, it crashes. I have attached a ROM log.

ROMLOG.LOG

3.19KB

reyalp

Thanks, that's useful information.

When you start the camera, is the play/rec switch in the playback or record position? In general, you should always start in playback if you intend to use USB mode switching.

Do you have some delay between the set_record and starting the zoom? If not, I'd try putting something like 1 second between them as a test.

The last entry I see in the romlog is

00014730: SSAPI:😁oAFLock

Does you script try to engage AF Lock?

HrClausen

Yes, the play/rec switch is in playback position.

I read somewhere a suggestion that autofocus should be locked before zooming.

In the attached l have removed the AF lock and unlock commands.

ROMLOG.LOG

3.22KB

« Previous Page Next Page »