Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - c_joerg

Pages: [1] 2 3 4
1
Camera-specific discussion / Re: Canon EOS R / RP
« on: September 18, 2020, 07:41:48 PM »
Interesting. Shutter count also broken here or has some encoding scheme.
Looks like this...
But only on RP.


It meight be interesting getting a dump of a fresh RP with 0 shots taken to find out the origin value.
Yes, would be intresting...
All my M's and 6D had 0 on the biginning.

2
Camera-specific discussion / Re: Canon EOS R / RP
« on: September 18, 2020, 03:37:30 PM »
Counter increased by one but is still invalid.
Intresting...
Maybe the memory is brocken.
Would be intresting to see a dump from an other RP.

3
Camera-specific discussion / Re: Canon EOS R / RP
« on: September 18, 2020, 02:04:34 PM »
ERR70 was a result of my broken Basic script.
Then try it again with original LP-E6N, ;)

4
Camera-specific discussion / Re: Canon EOS R / RP
« on: September 18, 2020, 01:57:19 PM »
There are some interesting logs here :D
Du you use original Batterie?
BatTemperature is always 0.

5
Camera-specific discussion / Re: Canon EOS R / RP
« on: September 18, 2020, 01:53:47 PM »
https://www.magiclantern.fm/forum/index.php?topic=25305.0

TotalShutter value seems to be invalid here. Could someone else with an RP run that script too and post the results here?
Have you tried to make one shoot and  a second dump?     

6
RP:

Shutter count seems to be invalid.

In this case, yes.
But not in the other examples.

7
It's probably because there is a mechanical shutter and electronic shutter.

But it is also on R5

M50 has also an TotalSW2 count...

8
Thanks, looks like your camera was crashed before…
I’m wondering about the BatTemperature = 0.
Do you use external power supply?

And on R5 is a TotalShoot and TotalShutter count...

9
srsa posted some specific code here that can be used to get some interesting information out of the camera.
https://chdk.setepontos.com/index.php?topic=13943.msg144153#msg144153

Code: [Select]
private sub Initialize()
    System.Create()
    CamInfo_Debug(1)
end sub

The Canon Basic Code creates a CameraInfo.xml file.
The file contains information such as TotalShoot, TotalRunningTime, ErrorList ...
I would be interested in a CameraInfo.xml from an R5 and R6, especially one that has already crashed.

A CameraInfo.xml of my M100 is here (renamed to txt).
https://chdk.setepontos.com/index.php?topic=13943.msg144154#msg144154





10
Camera-specific discussion / Re: Canon EOS R5 / R6
« on: September 05, 2020, 08:21:41 AM »
Canon Basic can do a lot more as you can see from these tread.
https://chdk.setepontos.com/index.php?topic=13522.0

This is a M100 snapshot of a Canon Basic Script that I got from srsa.



Perhaps this could also be used to make the temperatures of the R5 visible

11
Camera-specific discussion / Re: Canon EOS R5 / R6
« on: September 04, 2020, 07:38:29 AM »
Edit: I just counted and found that there is a total of 26 buttons (including dials and joystick directions) on the R6. Assuming that there are 2 input combinations to start the script, there are a possible 26x26 = 676 combinations that are possible to be the solution XD

Or a combinaton with touchscreen  ;)

Quote
https://chdk.fandom.com/wiki/Canon_Basic/Card_Setup
Some touchscreen cameras run the script when the focus lever is turned to the left.

12
How do you test Canon basic scripts?
Is there a syntax check or debug facility?
Or do you have to take out the card every time and try again?

13
Camera-specific discussion / Re: Canon EOS R5 / R6
« on: September 02, 2020, 03:01:36 PM »
On my M100, the basic scripts only start every second time (on average).
There has to be some kind of temporal behavior.

14
Camera-specific discussion / Re: Canon EOS R5 / R6
« on: September 02, 2020, 11:06:42 AM »
Unfortunately nothing happens. Have I made a mistake or are we out of luck? Maybe there's a different combination required to trigger the script?
Sure the SD Card is not exfat?
You need FAT.

15
Camera-specific discussion / Re: Canon EOS R5 / R6
« on: August 28, 2020, 07:52:30 AM »
Unfortunately v1.1 means that 1.0 is probably lost for now, considering how many of those were shipped / people wanting to upgrade.
I keep my R v1.0 backup as a relic 8)

I'm not very familiar with ML yet. But from CHDK I know that you can do a dump of the firmware in the camera. Isn't that possible with ML?
If the camera supports Canon Basic, it should be possible ...

16
Camera-specific discussion / Re: Canon R5
« on: August 23, 2020, 01:27:19 PM »
Does the R5 support Canon Basic? 

17
Mystery: the BOARD temperature appears closer to the value ending up in EXIF, at least in the first tests, but since it's not reported during photo capture (on 60D I've had two instances where the indicator showed -128 before and after taking a picture), that gives me some doubts.

On my EOS M3 I have 3 temperature values with CHDK. They are named Optical, Sensor and Battery. But also without any lens I got an optical temperature. Maybe the optical is the board temperature. The Sensor temperature is always much higher than the optical temperature so I expect that is really the sensor. I had max sensor temperature from around 70 degree.
The EXIF temperature matches exactly with the optical temperature. I’m wondering, why Cannon reports this lower value and not the sensor temperature in the EXIF data.

18
General Help Q&A / Re: Clean HDMI option via ML? (M50)
« on: May 28, 2020, 08:47:01 AM »
As long Canon Basic is available…
https://chdk.setepontos.com/index.php?topic=13489.10

19
and the camera takes shot after shot perfectly with only 1sec between images,
I think that’s the problem. 1s between images is not always enough. You should compare all EXIF timestamps from your images. May be the first and last is enough.

Not sure if this problem still happens
https://www.magiclantern.fm/forum/index.php?topic=21617.msg203896#msg203896

20
Seems to be normal at Samyang….
I had the Walimex Pro (same as Samyang) 14mm f2.8 AE three times. It was exchanged twice. Then I had one with another controller (recognizable by the serial number). But this was decentrally. Now I have the manual one.

21
Share Your Photos / Re: Extreme macro with ML
« on: April 23, 2020, 08:41:45 PM »
I have now managed to port the script to MATLAB. Quite a few changes are necessary. Especially in the operations of 2-dimensional and 3-dimensional matrices. The most important thing was that I learned a lot about the algorithm.

I am really impressed about the script. It works much better than CS6. 
Maybe I made a mistake with the porting. So far I have not carried out an algin. I'll port that next week.

Here is the MATLAB version of the script and the result from 70 images
https://drive.google.com/open?id=1qaQAEvg7g_Zllbq7BDPHxjgqIYSj3zJB

This is the result from HeliconFocus. HeliconFocus crops very strongly and the viewing angle is different


22
Share Your Photos / Re: Extreme macro with ML
« on: April 21, 2020, 07:54:35 PM »
Well, assuming you are using Windows, Octave can be simply unzipped and ran; no need to install it system-wide.

Nothing is simply at beginning ;)

Code: [Select]
E:\New\Stack_Test\M3_100mm_Stack_Test\LR>C:\Tools\octave\mingw64\bin\octave-cli focus_stack.m IMG_5051.jpg IMG_5052.jpg IMG_5053.jpg
warning: addpath: __OH__/share/octave/packages/image-2.10.0: No such file or directory
warning: called from
    load_packages_and_dependencies at line 48 column 5
    load_packages at line 47 column 3
    pkg at line 461 column 7
    focus_stack at line 12 column 1
Processing IMG_5051.jpg .error: could not find any INDEX file in directory __OH__/share/octave/packages/image-2.10.0, try 'pkg rebuild all' to generate missing INDEX files
error: called from
    describe>parse_pkg_idx at line 94 column 5
    describe at line 59 column 40
    pkg at line 555 column 43
    __unimplemented__>check_package at line 540 column 15
    __unimplemented__ at line 321 column 11
    focus_stack at line 44 column 7

I comment that out
Code: [Select]
   
# pkg load image

Code: [Select]
E:\New\Stack_Test\M3_100mm_Stack_Test\LR>C:\Tools\octave\mingw64\bin\octave-cli focus_stack.m IMG_5051.jpg IMG_5052.jpg IMG_5053.jpg
warning: function name 'show' does not agree with function filename 'E:\New\Stack_Test\M3_100mm_Stack_Test\LR\focus_stack.m'
error: 'im' undefined near line 16 column 10
error: called from
    focus_stack at line 16 column 3
   


23
Share Your Photos / Re: Extreme macro with ML
« on: April 21, 2020, 01:53:31 PM »
Haven't touched Matlab in years, but you might be able to run the scripts by commenting any "pkg load" lines, converting comments from # to % and fixing up stuff as you go.

That was the first thing what I did…

But I’m not sure how to use it in MATLAB (Pass the image to the script)
Code: [Select]
Usage: octave-cli focus_stack.m foo.png bar.png baz.png
When I do similar thinks in MATLAB (like Median over Images), I only give a path to the script. Then the script processes every image in this folder.

Well, assuming you are using Windows, Octave can be simply unzipped and ran; no need to install it system-wide. Therefore, as long as you are allowed to use a web browser and a zip extractor, I expect it to work.

https://wiki.octave.org/Octave_for_Microsoft_Windows

I think I will try this….

24
Share Your Photos / Re: Extreme macro with ML
« on: April 21, 2020, 09:03:46 AM »
If you decide to try these scripts, please share the results.

I'd like to try it…
I tried MATLAB but the differences are too big. It is already failing
Code: [Select]
pkg load imageI am not allowed to install Octave on my company computer ..

25
If you start to learn now we may have a beta around 2023.
Because if someone listened 2 years ago we may have an alpha now.
Is that an optimistic estimate?
I probably would have the skills but not the time.
Maybe one first project when I retire in 10 years...

Pages: [1] 2 3 4