Testing cameras after kbd.c change: 27 tested | 2 with minor bugs - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: [1] 2 3 4 5 6 ... 9   Go Down

Testing cameras after kbd.c change: 27 tested | 2 with minor bugs

  • 89 Replies
  • 39310 Views
*

Offline koshy

  • *****
  • 1096
Testing cameras after kbd.c change: 27 tested | 2 with minor bugs
« on: 23 / May / 2015, 19:06:16 »
Advertisements
Hello all, some might have noticed that I was not around for a while. Checking up on what you were doing in the meantime I found that a lot of cams were marked in need for testing after the kbd.c change.

I checked and I have the following 56 of them:

Update 2018: For whatever reason I only got through half the cameras I listed below.
The remaining have not been tested in this context but years later I'm closing the book on this.
Bugs will be found elsewhere.

    A450 100D[tests were fine] [has no jogdial]
    A480 100B[tests were fine] [has no jogdial]
    A490 100E[tests were fine] [has no jogdial]
    A530 100A[tests were fine] [has no jogdial]
    A550 100C[Bug: only powers on if pwr bttn is released quickly, or using Play] [tests were fine] [has no jogdial]
    A570 101A[tests were fine] [has no jogdial]
    A580 101B[tests were fine] [has no jogdial]
    A590 101B[tests were fine] [has no jogdial]
    A610 100E[tests were fine] [has no jogdial] [listed palette related stuff]
    A620 100F
    A630 100C
    A640 100B
    A650 100D
    A700 100B
    A710 100A
    A800 100B
    A1000 100B
    A1100 100C
    A1300 100E
    A2000 100C
    A2100 100A
    A3100 100D
    G7 100I[tests were fine]
    IXUS50_SD400 101B
    IXUS55_SD450 100D[tests were fine] [has no jogdial]
    IXUS60_SD600 100A [tests were fine] [has no jogdial]
    IXUS70_SD1000 101A [tests were fine] [has no jogdial]
    IXUS75_SD750 101A[Bug: only powers on if pwr bttn is released quickly, or using Play] [tests were fine]
    IXUS80_SD1100 101B
    IXUS85_SD770 100A
    IXUS90_SD790 100D
    IXUS95_SD1200 100C
    IXUS100_SD780 100C
    IXUS105_SD1300 100D
    IXUS130_SD1400 100C
    IXUS200_SD980 101C
    IXUS700_SD500 101B[tests were fine] [has no jogdial]
    IXUS750_SD550 100G[tests were fine] [has no jogdial]
    IXUS800_SD700 100B[tests were fine] [has no jogdial]
    IXUS850_SD800 100D[tests were fine] [has no jogdial]
    IXUS860_SD870 100C[tests were fine]
    IXUS900_SD900 100C[tests were fine]
    IXUS950_SD850 100C[tests were fine]
    IXUS960_SD950 100C[tests were fine, bug fixed]
    IXUS970_SD890 100C[tests were fine, bug fixed]
    IXUS980_SD990 100E[tests were fine]
    IXUS1000_SD4500 100D
    IXUSIZOOM_SD30 100G[tests were fine] [has no jogdial]
    IXUSW_SD430 110A[tests were fine] [has no jogdial]
    S2IS 100F
    S5IS 101A
    SX10 102B
    SX30 100E
    SX110IS 100B
    SX120IS 100B
    TX1 101B [tests were fine] [has no jogdial]

Before I get started on going through all of those I figured that it would be useful to check on the planned testing routine with you. Should anything else be tested on all of the above? If so please suggest what else to test now. Thanks. CHDKPTP related stuff for example.

Right now I plan to:

- boot a current CHDK 1.4 unstable build on the cam
- switch to rec mode
- try keys outside of alt mode
- flip though some Canon menu pages
- evaluate keys and jogdial in ALT mode
- shoot RAW / JPEG
- test USB remote
- test ubtest.bas (check scripted keypresses)

Is that all? Should we elaborate on something in the above so that it's clear what steps I'll perform?
« Last Edit: 02 / June / 2018, 20:12:32 by koshy »
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline srsa_4c

  • ******
  • 4451
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #1 on: 23 / May / 2015, 19:24:17 »
Quote from: koshy on 23 / May / 2015, 19:06:16
Should anything else be tested on all of the above? If so please suggest what else to test now. Thanks. CHDKPTP related stuff for example.
In addition to what you listed, I'd press all available buttons via the CHDKPTP GUI too.
And, of course, thanks for your effort.
Logged
*

Offline reyalp

  • ******
  • 14126
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #2 on: 23 / May / 2015, 22:51:56 »
First, thanks for doing this, it's greatly appreciated.

I think your test sounds good. Really, if you verify the camera boots and you can use the keyboard with both the canon and CHDK menus, that's 99%.

Some general suggestions:
The SD card lock logic is affected by this change, so make sure the canon firmware doesn't show the "card locked" message when running CHDK on a locked card.

You don't need to check chdkptp buttons and scripted key presses separately, one or the other is fine.

If you are testing with chdkptp,  remember the canon firmware often ignores key presses either until your switch to rec mode, or send post_levent_to_ui(4484). The levent doesn't work on older cams, and there may be other camera specific quirks.

I wouldn't worry to much about rigorously testing every possible key.  Do verify that you can get into alt mode using the physical key on the camera.

For the jogdial, you should both sending jogdial actions from script / chdkptp wheel buttons, and using the physical jogdial in the CHDK menu. When using the jogdial in the CHDK menu, the canon UI should NOT respond to the jogdial inputs.

There were some issues I noticed while doing the conversions that I wasn't comfortable trying to fix blind:
* ixus980_sd990 doesn't have the code to respond to jogdial inputs. Scripted jogdial should work. I should be able to come up with a test build with a full implementation.
* confusion about the cameras with the "feather" / "touch wheel" / "touch control dial" feature: http://chdk.setepontos.com/index.php?topic=12245.msg121374#msg121374 - the main thing is to check if the touch feature causes any problems with CHDK.
* synced remote probably doesn't work on s2is. I think regular remote should.

I think there were more, but I'll have to spend some time digging through my notes.
Logged
Don't forget what the H stands for.
*

Offline blackhole

  • *****
  • 946
  • A590IS 101b
    • Planetary astrophotography
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #3 on: 24 / May / 2015, 04:47:49 »
A530 and A590 are working well with the new kbd.c
Logged
*

Offline koshy

  • *****
  • 1096
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #4 on: 24 / May / 2015, 18:23:03 »
Quote from: reyalp on 23 / May / 2015, 22:51:56
* ixus980_sd990 doesn't have the code to respond to jogdial inputs. Scripted jogdial should work. I should be able to come up with a test build with a full implementation.
The Ixus 980 is probably my favorite camera of the lot right now so I'll gladly test whatever you come up with for it. I'll also test special stuff for the other cameras of course.
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline koshy

  • *****
  • 1096
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #5 on: 24 / May / 2015, 18:32:22 »
Thanks for the comments. So this is the updated testing plan:

- boot a current CHDK 1.4 unstable build on the cam
- make sure FW doesn't show "card locked" message
- switch to rec mode
- try keys outside of alt mode
- flip though some Canon menu pages
- select something that responds to jodial in Canon FW
- go to ALT mode and evaluate keys and jogdial
   - make sure that Canon UI does not respond to jogdial
- shoot RAW / JPEG
- test USB remote
- connect to CHDKPTP, go to rec mode and test wheel buttons
   - spot check other buttons
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline reyalp

  • ******
  • 14126
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #6 on: 24 / May / 2015, 18:41:48 »
koshy
That sounds great to me.

Here's a test patch to hopefully enable full jogdial support for ixus980_sd990. If you want a build, just let me know which firmware yours is.
Logged
Don't forget what the H stands for.
*

Offline reyalp

  • ******
  • 14126
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #7 on: 24 / May / 2015, 20:25:21 »
For jogdial, many cameras probably have in issue where using the jogdial in alt mode causes the canon firmware to see jogdial moves after you exit alt mode.

To see this:
make sure there is something in the canon UI that would respond to the jogdial, like Ev compensation or a menu.
go into alt, rotate the wheel in one direction, and exit alt
the thing selected in the canon ui should not change.

Cameras probably possibly affected by this are:
G10 (r31, not needed per waterwingz)
G11 (r39)
* G7 (unclear, vxworks)
G9 (r23)
* ixus1000_sd4500 (r43)
ixus110_sd960 (r49)
* ixus200_sd980 (r39)
ixus300_sd4000 (r43)
ixus870_sd880 (r31)
* ixus90_sd790 (r23)
ixus970_sd890 (r23)
* ixus980_sd990 (r31, should be fixed in patch above, if required)
s80 (vxworks)
s90 (r39)
s95 (r45)
sx1 (r31)
* sx10 (r31)
sx100is (r23)
* sx110is (r31)
* sx120is (r39)
sx130is (r45)
sx150is (r49)
sx20 (r39)
sx200 (r31)
sx210 (r43)


This was an existing issue, not caused by the keyboard changes, but I can probably provide fixes if you run into it.

edit:
Added dryos revs, * for cams on koshy's list
« Last Edit: 24 / May / 2015, 21:30:52 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #8 on: 24 / May / 2015, 20:57:52 »
Quote from: reyalp on 24 / May / 2015, 20:25:21
Cameras probably affected by this are:
G10
I can't make this happen on the G10.  For example, using Func/Set menu in shooting mode,  select the Flash +/-  option, and the jog dial moves left/right through the -2 to +2 choices.   Press the ALT key, scroll down through the main menu with the jog dial, press the ALT key again to exit ALT and the "cursor" in the Flash +/- does not move.  Same thing for other Func/Set menu items.


(CHDK 1.4.0 r4153)
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline reyalp

  • ******
  • 14126
Re: Testing cameras marked needed after kbd.c change: 55 Cams || 0 done || 55 to go
« Reply #9 on: 24 / May / 2015, 21:25:37 »
Quote from: waterwingz on 24 / May / 2015, 20:57:52
I can't make this happen on the G10.  For example, using Func/Set menu in shooting mode,  select the Flash +/-  option, and the jog dial moves left/right through the -2 to +2 choices.   Press the ALT key, scroll down through the main menu with the jog dial, press the ALT key again to exit ALT and the "cursor" in the Flash +/- does not move.  Same thing for other Func/Set menu items.
Thanks. That should have triggered it, so it's possible that older cameras don't need any special code to deal with this.

DryOS r39 onward seem to have different code, with another change art r43. I'll updated my post above with dryos revs.
Logged
Don't forget what the H stands for.
Pages: [1] 2 3 4 5 6 ... 9   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal