SX280 / 275 / 270 porting - page 28 - DryOS Development - CHDK Forum

SX280 / 275 / 270 porting

  • 338 Replies
  • 160313 Views
*

Offline srsa_4c

  • ******
  • 4217
Re: SX280 / 275 / 270 porting
« Reply #270 on: 08 / March / 2016, 11:41:33 »
Advertisements
bought one SX270 on ebay - and got it today - unfortunately it has firmware 1.01b not 1.02x - and I cannot find a CHDK verson for 1.01b - did I miss something?
You need to upgrade to the official 102b (1.0.2.0) firmware: http://www.canon-europe.com/support/consumer_products/products/cameras/digital_compact/powershot_sx_series/powershot_sx270_hs.aspx?type=firmware
Once done, you can use STICK's "unofficial release" method to prepare the card.

Re: SX280 / 275 / 270 porting
« Reply #271 on: 08 / March / 2016, 13:25:19 »
Thanks a lot this helped - I am happy.


greetings
Zweistein

Re: SX280 / 275 / 270 porting
« Reply #272 on: 13 / April / 2016, 08:08:48 »
Hey :)


I installed CHDK on my sx280hs and everything works fine - apart from the scripts.


For example: If i start the "motions detection" script, my camera keeps on shooting photos - also if no motion occures!
I already tried to adjust parameters or write a new script with the same function, but nothing changed.


Anyone here  have a suggested solution?


Thanks a lot for your replys. :)


oli_

Re: SX280 / 275 / 270 porting
« Reply #273 on: 13 / April / 2016, 09:44:51 »
installed CHDK on my sx280hs and everything works fine - apart from the scripts.
Do you have issues with any scripts other than motion detection?

Quote
Anyone here  have a suggested solution?
Did you study this :  Motion Detection : Performance Tuning ?

As all motion detection scripts use the same function for detecting motion,  writing a different script will not help.  You simply need to tune it correctly - which as you have noticed can be tricky.  The link I just posted mentions that  setting the "g" (or grid) parameter to 3 helps a lot when tuning.
« Last Edit: 13 / April / 2016, 09:46:46 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline srsa_4c

  • ******
  • 4217
Re: SX280 / 275 / 270 porting
« Reply #274 on: 13 / April / 2016, 11:04:09 »
If i start the "motions detection" script, my camera keeps on shooting photos - also if no motion occures!
Framebuffer related functions are not yet implemented (on DIGIC 6 ports in general). That includes motion detection. This is part of the reason why the port is still called 'prealpha'.

This is actually mentioned in the thread's first post, but that part of the post is a mess. I'll try to emphasize the missing features a bit more.

Re: SX280 / 275 / 270 porting
« Reply #275 on: 15 / August / 2016, 11:09:36 »
If i start the "motions detection" script, my camera keeps on shooting photos - also if no motion occures!
Framebuffer related functions are not yet implemented (on DIGIC 6 ports in general). That includes motion detection. This is part of the reason why the port is still called 'prealpha'.

This is actually mentioned in the thread's first post, but that part of the post is a mess. I'll try to emphasize the missing features a bit more.
I got Motion to work fine. (v1.5 port.) It takes a little tweaking. See bottom.

I've been obsessed with capturing images of lightning. Up until now, I've been doing it the old fashioned way - taking random exposures of 15 seconds (then waiting another 15 for the noise cancellation), hoping that I caught a strike in the process. Then I tripped across a guy on youtube using the Motion script in CHDK.

So I came here for the port of CHDK for my SX280. (Thanks to the developer for the port!)

Even tho framebuffer stuff isn't working, I can report that Motion (and the latest Lightning script) both work fine. I don't get the nice green grid like I do with the same script on my SX160. (Unless I'm in test mode on the Lightning Script.) But the motion detect part works.

At first, running the script with its default settings caused the SX280 to keep taking photos even without motion. But that was due to a few reasons.

One, I had to turn off AutoFocus and go to Manual. That stopped the image from "moving."

Two, I had better success with Manual exposure, so that the image also doesn't "move" as the camera figures out the exposure.

Last, and most critical, I had to increase the threshold for Motion. I find that 12 to 15 keeps it from constantly snapping photos. (Although I haven't had a chance yet to try it at night for lightning to see if that's too high. Update: Works well! It caught a bunch of strikes!)

Having said all that for the stock Motion LUA script, I didn't have to make any changes to the settings in the latest Lightning script for it to work. (Just Manual Focus.) I had to increase the threshold on the latest Lightning script for it to work too.

Also, it helps to turn off the "Review" feature on the camera.
« Last Edit: 22 / August / 2016, 12:10:01 by pmikep »

*

Offline reyalp

  • ******
  • 12537
Re: SX280 / 275 / 270 porting
« Reply #276 on: 22 / August / 2016, 13:40:21 »
I got Motion to work fine. (v1.5 port.) It takes a little tweaking. See bottom.
As srsa_4c posted earlier, motion detection cannot work correctly in the builds posted up to now. The code expects the frame buffer to be in a different format than it actually is. Only code changes (which are in development https://chdk.setepontos.com/index.php?topic=12918.0) can address this, no script settings can fix it.

It may appear to work because it still detects changes in the frame buffer, but it definitely does not function as intended, and users should not expect it to work reliably.
Don't forget what the H stands for.

*

Offline Ant

  • ****
  • 436
Re: SX280 / 275 / 270 porting
« Reply #277 on: 22 / August / 2016, 14:27:31 »
but it definitely does not function as intended
Can you explain?


*

Offline srsa_4c

  • ******
  • 4217
Re: SX280 / 275 / 270 porting
« Reply #278 on: 22 / August / 2016, 15:11:28 »
Can you explain?
I can - partly - explain: the original routines expect a pixel encoding where 6 byte blocks represent 4 pixels (4 pixels share the same chroma). See this link.
On D6, viewport buffers use pixel formats where 2 pixels are encoded on 4 bytes.
As a result, the original motion detection routine can't work as intended: it misinterprets pixel data.

*

Offline Ant

  • ****
  • 436
Re: SX280 / 275 / 270 porting
« Reply #279 on: 22 / August / 2016, 15:20:23 »

 

Related Topics