RAWOPINT.LUA

Hi, I'm new here and need help

I must have a fundamental mistake in the settings somewhere. The exposure time does not change despite the changed lighting conditions (sunset). I use a G1X and RAWOPINT.lua and try to capture the sunset and the stars.
Whatever I do, the exposure time stays the same.

Does somebody has any idea?
Best regards
Stephan

The problem is solved. The attached hot shoe was obviously blocking chdk

Thank`s

Same problem as
https://chdk.setepontos.com/index.php?topic=12697.msg146212#msg146212

Total frustrating:

Old Problem again." must have a fundamental mistake in the settings somewhere. The exposure time does not change despite the changed lighting conditions (sunset). I use a G1X and RAWOPINT.lua and try to capture the sunset and the stars.
Whatever I do, the exposure time stays the same."

Hotshoe was not the key problem. Any ideas?

Best regards Stephan

Old Problem again." must have a fundamental mistake in the settings somewhere. The exposure time does not change despite the changed lighting conditions (sunset). I use a G1X and RAWOPINT.lua and try to capture the sunset and the stars.
Whatever I do, the exposure time stays the same."

Hotshoe was not the key problem. Any ideas?

If you post the rawopint.csv log, that might provide some clues.

Also beware that the camera could think the hot shoe is occupied when it's not.

Another thing you can do is check whether normal CHDK overrides are working with the same camera settings. Put the camera in P, half press and check what exposure the Canon firmware would use, use CHDK override to set it to something else, and see if worked.  For example, if the Canon UI showed shutter 1/100, set it to 1/20th and check whether it's correctly exposed (override didn't work) or very overexposed.

Ok,
thanks for the tips.
I am complete frustratet. All timelapse pics the same aperturetime... A holiday in africa for nothing. Just now I make a new timelapseshot and I will post the rawopint.csv log. The pics from Africa   ARE DELETED grrr

Best regards Stephan.

Here the log files

And

I am complete frustratet. All timelapse pics the same aperturetime... A holiday in africa for nothing.

Ouch, that is frustrating. I'm sorry you didn't get the timelapse you wanted 

From your log, it looks like the script is trying to set exposure, and the firmware is ignoring it. That's similar to what some people have seen with the hot shoe issue, but could maybe be caused by other Canon settings as well. What shooting mode and drive mode was the camera set to?

For hot shoe, if there's nothing physically in it, the microswitch could be stuck. There should be some indication in the Canon UI if it thinks something is there, but I don't have a cam with hot shoe to check exactly.  You can set the "Hotshoe override" to "Empty" to force the Canon firmware to think there is nothing there.

Unfortunately, it's quite difficult to make a reverse engineered hack Just Work for everyone on 180+ models, so it's important to test and make sure things are working (or not) in advance.

I am complete frustratet. All timelapse pics the same aperturetime... A holiday in africa for nothing.

Did it work before?
Or have you never tested it before?

For hot shoe, if there's nothing physically in it, the microswitch could be stuck. There should be some indication in the Canon UI if it thinks something is there, but I don't have a cam with hot shoe to check exactly.

In this case, the flash icon disappears from the screen.