SX170 porting - page 24 - DryOS Development - CHDK Forum supplierdeeply

SX170 porting

  • 266 Replies
  • 96440 Views
*

Offline reyalp

  • ******
  • 14111
Re: SX170 porting
« Reply #230 on: 15 / February / 2015, 20:30:18 »
Advertisements
1.4.0, autobuild 4010, firmware 1.01a = The dial works fine.
Thanks, I've checked this in for 1.3 as well.
Don't forget what the H stands for.

*

Offline TMHKR

  • **
  • 77
  • Canon PowerShot SX170 IS (1.01a firmware)
Re: SX170 porting
« Reply #231 on: 18 / February / 2015, 09:46:56 »
Note on aperture override values for SX170, firmware 1.01a

Max. achievable aperture = f/11 on wide, f/16 on tele

I have done the aperture tests, and checked the resulting images on my IPS monitor. Here are the results:

FULL WIDE
Exposure ranges from 3.60 to 11.31 - the unmarked values give the 11.31 equivalent

    3.60 - starting exposure
    4.10 - lower
    4.72 - lower
    5.26 - lower
    5.67 - lower
    6.08 - lower
    6.35 - lower
    7.12 - lower
    8.00 - lower
    8.98 - lower
  10.07 - lower
  11.31 - lowest exposure
  12.69 -
  14.25 -
  16.00 -

FULL TELE
Exposure ranges from 5.67 to 16.00 - the unmarked values give the 5.67 equivalent

    3.60 -
    4.10 -
    4.72 -
    5.26 -
    5.67 - starting exposure
    6.08 - lower
    6.35 - lower
    7.12 - lower
    8.00 - lower
    8.98 - lower
  10.07 - lower
  11.31 - lower
  12.69 - lower
  14.25 - lower
  16.00 - lowest exposure

Settings: P mode, ISO 100, 12 Mpx 16:9, JPEG, CHDK Av override
« Last Edit: 21 / February / 2015, 05:20:52 by TMHKR »

*

Offline TMHKR

  • **
  • 77
  • Canon PowerShot SX170 IS (1.01a firmware)
Re: SX170 porting
« Reply #232 on: 21 / February / 2015, 15:15:37 »
(unnecessary post, ignore this)
« Last Edit: 21 / February / 2015, 15:38:16 by TMHKR »

*

Offline srsa_4c

  • ******
  • 4451
Re: SX170 porting
« Reply #233 on: 21 / February / 2015, 16:09:46 »
Test build for fw 101a with
Code: [Select]
static long *nrflag = (long*)(0xA900-4); // see NRTBL.GetDarkSubType, 0xffa2fe18, 0xffa2fe20, 0xffa2fe24 (fw 100a) Let's hope I made no mistake.

edit:
attachment removed
« Last Edit: 21 / February / 2015, 20:19:55 by srsa_4c »


*

Offline TMHKR

  • **
  • 77
  • Canon PowerShot SX170 IS (1.01a firmware)
Re: SX170 porting
« Reply #234 on: 21 / February / 2015, 16:28:57 »
Test build for fw 101a with
Code: [Select]
static long *nrflag = (long*)(0xA900-4); // see NRTBL.GetDarkSubType, 0xffa2fe18, 0xffa2fe20, 0xffa2fe24 (fw 100a) Let's hope I made no mistake.

Dark Frame Subtraction doesn't work at all now, neither of the three settings work. Tested both JPEG and DNG, shutter speed = 2 seconds.

*

Offline srsa_4c

  • ******
  • 4451
Re: SX170 porting
« Reply #235 on: 21 / February / 2015, 20:19:22 »
Dark Frame Subtraction doesn't work at all now, neither of the three settings work. Tested both JPEG and DNG, shutter speed = 2 seconds.
Apparently I'm missing something.
Next try, moved the hook(s) upwards, using nafraf's nrflag. I expect some issues with the auto setting, even if it starts to work somewhat.

code_gen.txt diff
Code: [Select]
Index: .
===================================================================
--- . (revision 4031)
+++ . (working copy)
@@ -255,26 +255,16 @@
 //////////////////////////////////////////////////////////////
 FUNC ref=0
 ASM
-FW 33
-PATCHSUB ref=0
-->FW
-ENDASM
-ENDFUNC
-
-FUNC ref=0
-ASM
-FW 20
+FW 32
 >>>
 "    BL      wait_until_remote_button_is_released\n" // added
 "    BL      capt_seq_hook_set_nr\n"                 // added
 <<<
 FW 1
-//->FW
-FW $
+->FW
 ENDASM
 ENDFUNC
 
-
 //////////////////////////////////////////////////////////////
 // task_developseq
 //////////////////////////////////////////////////////////////

edit:
test build removed
« Last Edit: 22 / February / 2015, 09:33:24 by srsa_4c »

*

Offline TMHKR

  • **
  • 77
  • Canon PowerShot SX170 IS (1.01a firmware)
Re: SX170 porting
« Reply #236 on: 22 / February / 2015, 05:20:36 »
Apparently I'm missing something.
Next try, moved the hook(s) upwards, using nafraf's nrflag. I expect some issues with the auto setting, even if it starts to work somewhat.

Test results:

- ON works fine
- OFF works fine
- AUTO doesn't work at all

*

Offline srsa_4c

  • ******
  • 4451
Re: SX170 porting
« Reply #237 on: 22 / February / 2015, 09:32:58 »
- ON works fine
- OFF works fine
- AUTO doesn't work at all
As expected, thanks.
The next test build enables the explicit AUTO setting (#define NR_AUTO (0)). If we're lucky, it will work.

Can you also run the vidtest.lua script (it's in the CHDK/SCRIPTS/TEST directory on card, included in full zips from the autobuild) and upload the log it creates (note that it will switch the cam to rec mode, switch modes and record a small video)?

edit:
test build removed
« Last Edit: 04 / April / 2015, 12:38:35 by srsa_4c »


*

Offline TMHKR

  • **
  • 77
  • Canon PowerShot SX170 IS (1.01a firmware)
Re: SX170 porting
« Reply #238 on: 22 / February / 2015, 10:47:31 »
As expected, thanks.
The next test build enables the explicit AUTO setting (#define NR_AUTO (0)). If we're lucky, it will work.

Can you also run the vidtest.lua script (it's in the CHDK/SCRIPTS/TEST directory on card, included in full zips from the autobuild) and upload the log it creates (note that it will switch the cam to rec mode, switch modes and record a small video)?

Nope, AUTO still doesn't work at all. ON and OFF work fine.

Note that I'm doing the DFS testing with these parameters:

  Mode = P
  Shutter speed = Set in CHDK, Override Tv function, 2 seconds (to trigger the DFS in AUTO)

I've attached the vidtest.log file, from the latest 1.3.0 autobuild.
« Last Edit: 22 / February / 2015, 11:05:45 by TMHKR »

*

Offline srsa_4c

  • ******
  • 4451
Re: SX170 porting
« Reply #239 on: 22 / February / 2015, 12:53:31 »
Nope, AUTO still doesn't work at all. ON and OFF work fine.

Note that I'm doing the DFS testing with these parameters:

  Mode = P
  Shutter speed = Set in CHDK, Override Tv function, 2 seconds (to trigger the DFS in AUTO)
Oh, I see. For most (or all) CHDK overrides, the Canon code doesn't take the overridden values into account. So, you won't be able to trigger DFS in P mode this way. Use M or Tv mode and set the exposure time with Canon controls.

If that still isn't enough, the attached test build saves the nrflag's original value before the shot. You can use this short Lua script to display it (after the shot):
Code: [Select]
--[[
@title display latest recorded NR flag
--]]
print("nrflag: "..peek(0x40000000))
This test build doesn't touch the nrflag when set to AUTO. If you need to do this debug step, leave the NR menu entry at 'AUTO', shoot (short and long exposures with Canon controls) and run the script after each shot.

Quote
I've attached the vidtest.log file, from the latest 1.3.0 autobuild.
Thanks. Please repeat the test with the attached test build to check whether the detection of an ongoing video recording is working now.

edit:
test build removed
« Last Edit: 04 / April / 2015, 12:38:09 by srsa_4c »

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal