A490 Porting - page 11 - DryOS Development - CHDK Forum supplierdeeply

A490 Porting

  • 224 Replies
  • 43772 Views
Re: A490 Porting
« Reply #100 on: 31 / December / 2011, 20:00:55 »
Advertisements
Just reporting my experience with the usb remote shutter.  On my two A495 cameras, it works as expected, but on the first A490 I tested, I am getting the long lag between triggering the voltage and the shutter releasing.  Others have mentioned the 10 second delay, and I tried the various synchable remote menu options, but nothing seems to fix it.  I'm testing a multiple camera setup, so the synch delay feature (shoot on voltage release) would be great.  Again, works fine on my A495 cameras, if that info. is of any use.

I really hope someone can nail this!  Thanks again.

I've spent more than a little time on this over the last few weeks.  I've found quite a few things with the sync code that are broken although the basic functionality you describes works (although quite by accident it turns out when you read the code.)

However,  the kbc.d code (core & platform) for the A490 and A495 are identical.  They should act exactly the same using a USB remote but clearly from your tests they do not.

Having said that,  a quick look at the stubs_entry.S file for the a490 show several issues that the new sigfinder has found with the old A490 port.   

What firmware version are you using on you A490 ?  I can make the changes and post an updated built for you to try if you are interested ?


Additional Questions :   you are using a simple push button switch rather than a Ricoh CA-1 - is that correct ? 
« Last Edit: 31 / December / 2011, 20:24:52 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A490 Porting
« Reply #101 on: 31 / December / 2011, 22:33:46 »
Thanks for the response!

Is this the firmware info. you mean? :
1.0.0-1519
100f

And yes, I'm just using a simple switch, on a variable wall wart power supply set to 4.5V, which has worked fine with the A495.

I'll gladly test any update you post.

Happy New Year!

- Jance

Re: A490 Porting
« Reply #102 on: 01 / January / 2012, 02:36:16 »
Ok, as I'm unboxing and testing my multiple cameras, I'm discovering that some are version D, E, and F.

F has the several second lag with the remote shutter release.
E doesn't have a chdk firmware version?
D seems to work properly and doesn't have the remote shutter release lag at first test (although D seems to insist on saving images to the small 15MB partition created by SDMInst for cards that are 4GB or larger - so that's a problem I need to figure out.)

Just passing along info.  Does anyone have info. on a version E for the A490?

Thanks!

- Jance


Re: A490 Porting
« Reply #103 on: 01 / January / 2012, 02:40:33 »
F has the several second lag with the remote shutter release.
E doesn't have a chdk firmware version?
D seems to work properly and doesn't have the remote shutter release lag at first test
Now that is really interesting!  Its late for me so I'll take a look at the stubs_entry.S files for each version tomorrow to see if it gives some clues.

Quote
Does anyone have info. on a version E for the A490?
Older camera - not likely anyone is working on it.  Your best shot is if the D or F version of CHDK works "as is".

Ported :   A1200    SD940   G10    Powershot N    G16


Re: A490 Porting
« Reply #104 on: 01 / January / 2012, 03:44:13 »
I've got 22 A490's (plus 2 A495's) for my multi-camera test.  I'll keep unboxing and checking firmware versions tonight and tomorrow (and I guess hoping that not too many are version E!).

- Jance

Re: A490 Porting
« Reply #105 on: 01 / January / 2012, 05:57:41 »
Ok, to recap, I've got two A490D's, ten A490E's, and ten A490F's (plus two A495F's to total 24 cameras that I'm trying to remote trigger simultaneously). 

For the A490's, the USB remote shutter release works fine with the D's, there's no version for the E's, and there's a long lag with the F's.  (The A495F's work fine.)

So I'm hoping for a fix to the F, and a version for the E!

waterwingz, thanks for all your responses so far!

- Jance


*

Offline philmoz

  • *****
  • 3114
    • Photos
Re: A490 Porting
« Reply #106 on: 01 / January / 2012, 07:06:56 »
Ok, to recap, I've got two A490D's, ten A490E's, and ten A490F's (plus two A495F's to total 24 cameras that I'm trying to remote trigger simultaneously). 

For the A490's, the USB remote shutter release works fine with the D's, there's no version for the E's, and there's a long lag with the F's.  (The A495F's work fine.)

So I'm hoping for a fix to the F, and a version for the E!

waterwingz, thanks for all your responses so far!

- Jance



The 1.00d code has quite a few obvious mistakes, 1.00f not so many.
Attached are new versions of each with the mistakes I can see fixed - let me know how these go.

The 1.00e firmware is quite different to both 1.00d and 1.00f so will need a new port.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)

*

Offline philmoz

  • *****
  • 3114
    • Photos
Re: A490 Porting
« Reply #107 on: 01 / January / 2012, 07:50:32 »
Attached is a test version for A490 firmware 1.00e.
Chances are I've missed a few changes and it won't do anything; but give it a try anyway.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)


Re: A490 Porting
« Reply #108 on: 01 / January / 2012, 09:32:10 »
The 1.00d code has quite a few obvious mistakes, 1.00f not so many.
Attached is a test version for A490 firmware 1.00e.
Chances are I've missed a few changes and it won't do anything; but give it a try anyway.
Thanks for doing that philmoz.  That was going to be my morning project today - too many other things happening last night to work on CHDK.

Did you find anything other than the things pointed out in stubs_entry.S ?   I still want to understand why the D version (and some other camera 6 months or so ago IIRC) go into timeout mode on sync.   All its doing it waiting for a USB power transisition and the code is broken enough that it should only go one place to do that.

@janceallen : I'll be curious to see how this works.  Even if this fixes the 100d, if you have a little time,  I'd like to track down what was actually causing this. I've attached a file for the 100d (with none of philmoz's fixes) that should change the 10 sec delay timeout that you see ( it will be either 5 sec, 15 sec or 20 sec). Let me know which ?
« Last Edit: 01 / January / 2012, 10:12:16 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3114
    • Photos
Re: A490 Porting
« Reply #109 on: 01 / January / 2012, 14:55:21 »

Did you find anything other than the things pointed out in stubs_entry.S ?   I still want to understand why the D version (and some other camera 6 months or so ago IIRC) go into timeout mode on sync.   All its doing it waiting for a USB power transisition and the code is broken enough that it should only go one place to do that.


The address checks in taskHook were wrong for 1.00d - it probably was not hooking the init_file_modules_task and the capt_seq_task. This would explain why it writes the files to the wrong partition. It might also have something to do with the remote trigger since the 'wait_for_remote_release' call would not have been done.

In theory my 1.00d version should now behave the same as the 1.00f - so it may have the extra delay.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)

 

Related Topics