EOS M3 porting [M3] [EOS_M3]

c_joerg

Ant
IIRC you need to call function GetCameraInformationData.

How?
If I do

call_event_proc('GetCameraInformationData')

I got -1. That means event procedure is not found (or otherwise cannot be executed). Native call functions is enabled.

Ant
XML document will be found somewhere in RAM dump.

You mean the dump in the debug menu which gives me a file like CRW_0001.JPG?

Ant

c_joerg That means event procedure is not found (or otherwise cannot be executed).

Call function by address from *.csv file.

You mean the dump in the debug menu which gives me a file like CRW_0001.JPG?

Yes. Plus you can type "rmem 0x10 0x02000000 -f=filename"

chdkptp still not allows to read from address 0.

c_joerg

Ant
Call function by address from *.csv file.

I still have not figured out how this works with function call by address from *.csv file.
Any link, which can help me?

Ant
Plus you can type "rmem 0x10 0x02000000 -f=filename"

I never did it from chdkptp but this works very wellâ€¦ 😀

I've seen another interesting function â€˜GetAoriAccelerationDataâ€™. What does â€˜Aoriâ€™ mean? May be that gives the information for the â€˜FreeFallâ€™ â€¦

Ant

c_joergAny link, which can help me?

https://app.assembla.com/spaces/chdk/subversion/source/HEAD/trunk/platform/m3/sub/101a/funcs_by_name.csv

call_func_ptr(0xFCxxxxxx)

c_joerg

Ant [code]call_func_ptr(0xFCxxxxxx)[/code]

Thanks for your helpâ€¦
Interesting, I saw in my log file the crash, which I had described in Reply #282. It was a â€™E50 FormatErrorâ€™. But not happened again.

CameraInfo.xml

2.15KB

62ndidiot

ç...½ã‚Š"aori". Gust (of wind). Influence.

c_joerg

@Ant
Which DC coupler are you using?
Original Canon or replica? Does the camera recognize the difference between Canon or replica DC coupler?
Does the camera register for a replica DC coupler like a replacement battery?

Ant

I don't have DC coupler.
Camera recognizes the DC coupler by absence of connection on two middle contacts. In this case camera do not display battery icon and maybe increases battery shutdown level.

c_joerg

Ant
I don't have DC coupler.
Camera recognizes the DC coupler by absence of connection on two middle contacts. In this case camera do not display battery icon and maybe increases battery shutdown level.

But I saw a lot of DC coupler entries in the XML file from Reply #214. I this not your cam?

Ant

It's modified LP-E12 battery without thermistor contact (LP-E12 is slightly shorter).

c_joerg

Ant
It's modified LP-E12 battery without thermistor contact (LP-E12 is slightly shorter).

And that fits? How did you do this?
But you must confirm the use with the camera or?

Ant

There were reasons in 2015 to do this modification.
Now I can only confirm that you should buy third party LP-E17.

Ant

I've checked the newest firmware 1.2.0:
IS related bugs are still present, but rollback to previous fw is still available...

c_joerg

Ant
but rollback to previous fw is still available...

good to know... 😀

reyalp

I split the discussion of benchmarks and the sd card info function: https://chdk.setepontos.com/d/13089

srsa_4c

Can somebody with this camera check whether CHDK exposure overrides remain effective after the shutter is held halfway down for a few seconds?
On the M10, they are getting overridden by the Canon firmware in all shooting modes except M. That means, when CHDK overrides are set, they are reflected on the Canon overlay for a few moments after a half press, then the exposure parameters return to Canon calculated values.

When that happens, I get these entries in the camera log:

00034020: UI:ShootSeqToUI:0x00003157:adr:0xfc2a50cb,Para:-64335669
00034030: UI😁SIC:e3,0
00034030: UI:VTMLock
00034070: UI:VTMUnLock

c_joerg

srsa_4c
Can somebody with this camera check whether CHDK exposure overrides remain effective after the shutter is held halfway down for a few seconds?
On the M10, they are getting overridden by the Canon firmware in all shooting modes except M. That means, when CHDK overrides are set, they are reflected on the Canon overlay for a few moments after a half press, then the exposure parameters return to Canon calculated values.

Not sure if I understood it correct. I never work with override beforeâ€¦
I go on the M3 to AV Mode. ISO100, Av=3.5 and the Camera measure 1/6s.
I got to Enhanced Photo Operation => Override Tv â€˜ShrtExpâ€™ and set it to 0.001s.
Now the Canon menu shows Tv=1/1000 when I go to half shutter press. The value is not changing. I did it for 15s.
I that what you mean?

Update:
I can reproduce it. But it is only happening, when the cam canâ€™t focus (when I got the red square). When the cam focus correct, it is not changing.

srsa_4c
When that happens, I get these entries in the camera log:

ROMLOG.LOG?
This Shows only older stuff..

ROMLOG.LOG

184b

srsa_4c

c_joerg
I go on the M3 to AV Mode. ISO100, Av=3.5 and the Camera measure 1/6s.
I got to Enhanced Photo Operation => Override Tv â€˜ShrtExpâ€™ and set it to 0.001s.
Now the Canon menu shows Tv=1/1000 when I go to half shutter press. The value is not changing. I did it for 15s.
I that what you mean?

Yes.

Update:
I can reproduce it. But it is only happening, when the cam canâ€™t focus (when I got the red square). When the cam focus correct, it is not changing.

Thanks for finding this, I'm experiencing the exact same behaviour.
I had the cam set to MF when I noticed the override issue.

edit:

c_joerg
ROMLOG.LOG?
This Shows only older stuff..

No, I have a script that saves the camera log to file. The romlog also contains this log up to the point where the camera crashed, but the camera log is always active when the camera is on.

c_joerg

srsa_4c
I had the cam set to MF when I noticed the override issue.

Yes, the same happens when I go to MF. Does that means rawopint will not work in MF Mode or with manual lens?

Here is another thing which I only noticed at the M3:

c_joerg
Normally the aperture does not change between the shoots in rawopint (which is at least my other cameras so).
However, with the M3, the shutter is opened and closed with each shot. This is, however, only in single mode. This does not happen in the continuous mode. In continuous mode the aperture remains fixed in the set position.

I mean the mode just one half press and then only full pressâ€¦

srsa_4c

c_joerg
Yes, the same happens when I go to MF. Does that means rawopint will not work in MF Mode or with manual lens?

I'm not familiar with that script, so I can only give a generic answer.
If you shoot right after focus/exposure has settled, the overrides may work. The longer you wait after half pressing, the more likely that the firmware overrides the CHDK override. The issue happens when
- focusing is set to manual
- auto focus doesn't find focus
- "there's no lens", meaning any manual lens that doesn't communicate with the body

« Previous Page Next Page »