Messages

All you need to do on EOS is

Code Select Expand


private sub Initialize()
    CamInfo_Debug(1)
end sub


Yes I know.
With my M100 and G9xII I sometimes have the problem that it doesn't work (I suspect timing or SD card). With the beep I can immediately hear whether it worked. This simplifies troubleshooting.
I was hoping that these simple commands would also work with the R.

Interpreter is (most likely) the same. Available commands beyond keywords are different.

I was hoping a simple shooting Canon basic script would work on the R too
https://chdk.setepontos.com/index.php?topic=13522.0
Is there an overview about keywords?

The following code

Code Select Expand

dim c
private sub Initialize()
    System.Create()
    Driver.Create()
    for c=1 to 3
      BeepDrive(3)
      Wait(500)
    next
   
    CamInfo_Debug(1)
   
    for c=1 to 2
      BeepDrive(3)
      Wait(500)
    next
end sub

Runs on M100 but crashes EOS R and R5 with

Code Select Expand

-<ErrorList>
-<Kind>
<ID>E70</ID>
<Count>1</Count>
-<ErrorLog>
<BatTemperature>max:0 min:0</BatTemperature>
<FirstOccurTime>2022.01.06 17:59:34</FirstOccurTime>
<LastOccurTime>2022.01.06 17:59:34</LastOccurTime>
-<Log>
<DateTime>2022.01.06 17:59:34</DateTime>
<Reason>DS-EID:101</Reason>
<BatTemperature>0</BatTemperature>
<LensID>0000103c</LensID>
<ReleaseCount>265</ReleaseCount>
</Log>
</ErrorLog>
</Kind>
</ErrorList>

Any Idea why?
Commands are different on M and R?

You can verify which one you have with Canon Basic script, mentioned on previous pages:

It contains some info, including:

Code Select Expand


<FirmwareVer>
    <Internal>0.7.3.9</Internal>
    <Major>1.8.0</Major>
</FirmwareVer>


I have a new EOS R, one month old that shows

Code Select Expand


<FirmwareVer>
    <Internal>0.7.4.0</Internal>
    <Major>1.8.0</Major>
</FirmwareVer>


The R5 has this feature

Most are annoyed about the fact that this mode cannot be switched off with Canon lenses ...

If you would create a crop RAW, then probably no RAW converter could process the RAW.

"I don't now how to do all the things on the EOS R without ML (f. e. Intervalometer, Motion detection, the modules). "

At least simple things like Intervalometer, would work with Canon Basic.
https://chdk.setepontos.com/index.php?topic=13522.0

Okay, but your comments about different cams, in a Digic 8 and X thread were confusing and don't seem relevant.

Sorry for the confusion.
Since the CameraInfo part is already available in the Powershot firmware, I assumed that this part also ended up in the firmware of the R and was only expanded.

It was understood that we would like to know whether there is a fixed start number for TotalShutter at RP.
For that you would need an unused RP. And I don't think the RP from j1080 is a total new one.

With 1,086,947,603 shutter activations? 

No, because of 701 TotalShoot and 173 PowerOnCount

RP is anomaly.

Yes, of course, TotalShutter on RP is anomaly.

What does it mean that new RP don't show 0 via this method of querying it? 

I would assume that the goods were returned.

I bought the G7x 3 times. The first two had single-digit releases. The third was 0. The first two were definitely returned goods. Of course, that doesn't mean that the R's is any different.

Already clear. I mean I would have seen a 0 on an M6II.
I would also expect a 0 for an  new R.

We don't know much about RP yet, nobody can give you a definitive answer.  How much do these values go up on every cam due to testing Canon does in the factory?  We don't know.

IIRC, my M10 and M100 start with 0 shoots.
Also my 6D.
I think the counters are reset at the factory or do not even run.

Any idea what the functions do:

Code Select Expand

dev_cropcheck
dev_cropcontcheck
I was hoping to find features like disable_crop ...

How do you mean?

I would start ramping when the exposure time is 2s below the start interval time.

I see exFAT in EOScard. Does exFAT work?

• Keyframe 2: Keyframe time: 19:10:00, Aperture: ON, F8.0, Interval time: 5s
• Keyframe 3: Keyframe time: 19:40:00, Aperture: ON, F2.8, Interval time: 15s
• Keyframe 4: Keyframe time: 20:10:00, Aperture: ON, F2.8, Interval time: 25s

Then every few seconds in the finished video there is a jump in time. I can't imagine it looking good.

I would not make that dependent on the time but on the current exposure situation.

I don't know what kind of signal you get through the hotshoe port, though - is it a logic signal active during the entire exposure, or something else?

The center contact is closed as long as the exposure is on. You can even measure the exposure time with it, but not very precisely. I control my dolly with the hotshoe

For this task you actually need a script with interval ramping. The lrtimelapse pro timer can do that too.

The problem is the different interval times. If the interval is more than 8s, the sunset becomes too fast. The starry sky takes about 30s. It is important for interval ramping that the transition is as smooth as possible. You should therefore not necessarily let the interval run over the exposure time. If, for example, a cloud comes in front of the sun before sunset, then the interval speed should not always change.


I wanted to do that with a CHDK lua script last year.
My idea was:

The interval starts with a fixed interval. If the exposure time comes in an order of magnitude (interval - exposure time <2s) then I would start the ramping. Perhaps I would adjust the ramping speed slightly, depending on the difference. But I would only ever increase the interval. Only when the maximum interval has been reached for a certain time could ramping be allowed to run in the other direction (For the night-day transition).


https://youtu.be/HHiEXPJUs5w

[not]

If the step-up converter sticks out of the powerbank attached only to the USB connector,

Just for clarifying:
The adapter in post Reply #16 and Reply #19 is not a DC/DC step-up converter! This adapter communicates with the power bank and only tells it that the power bank should supply a different voltage. On QC 3.0 it can deliver 8.4V / 2A.

The adapter on Reply #2 is a DC/DC step-up converter and works with 5V Powerbanks. But this one only dilvers 8.4V / 1.4A which is not enough for my 6D
https://www.magiclantern.fm/forum/index.php?topic=21660.msg197698#msg197698

it will break very easily, especially if you move the camera around.

Two ways to get around it:
You remove the plug and socket of the adapter and replace it with a piece of USB cable. This is my favorite solution
You could use the adapter with a Y cable. The adapter only needs to communicate with the power bank once at the beginning until the 8.4V comes in. Then you can theoretically pull it off. But I have not yet produced that. 

Here you see other solutions with Quick charge. This adapter also prevents the power bank from being switched off in standby
https://gwegner.de/know-how/qc-powerbank-stromversorgung-kamera-slider-qccp-adapter/

How much current does your 6D draw while video recording with Global draw ONthis adapter also prevents the power bank from being switched off in standby?

I never used 6D with video. Only time-lapse.
But with the Adapter in Reply #2 the cam goes off when the mirror goes up. So 6D needs mor than 1.5A.

"I made more tests yesterday, I think 8.90 Volt made the camera overheats quicker than usual, I re-added one diode to drop voltage to ~8.55 and that was fine and it doesn't overheat quickly it was normal,

Really?
I never notice this on my 6D. If I increase voltage, the current goes down.
How du you messure?

Could you please measure the exact voltage in this 8.55V scenario under load,

Is this not possible to log voltage with ML?
On my cams with CHDK I contionus log input voltage und temperature in a file.

If you can find a powerbank with adjustable output voltage (7.5 - 8V) and 2A output capability, that would be the ideal solution - powerful, compact and no casing required.

Do you read my  Reply #16 and Reply #19?
https://www.magiclantern.fm/forum/index.php?topic=21660.msg224698#msg224698
https://www.magiclantern.fm/forum/index.php?topic=21660.msg232081#msg232081

Every cheep Powerbank with Quick Charge 3.0 can do this. With Quick Charge 3.0 you can set the voltage in 0.2V steps to 7.8V and 2A.
You must only tell the powerbank, that you need 7.8V. That is what the quick charge USB tester in Reply #19 did..

My concern is much more the smart charger that I will have to build to protect the cells when charging.  I'll check and see if I can find 3,7V cells with built in overcharge protection circuits inside.  If someone has used such cells, please share your experience here.

I thought every 18650 cell contains a protection against overcharging and deep discharge. I once had some that definitely had this protective circuit.
After these cells were taken from me twice at the airport security checkpoint, I only use power banks.

Short Answer: Welcome to Syria

Ok then I understand...

But has nothing to do with the topic of power banks, does it?

I bought my last dummy adapter for less than 5 € in China..

Can you find a way to reproduce it?

Not always...
I used LV in M Mode and continuous shooting s.
I look like, it is only happening with Frame Autodetect. If I change to 7 Frames, I haven't seen it until now.

The memory differs at last crash

Code Select Expand

Free Memory  :  381K + 1889K

This is the first time I've had a crash with ML on my 6D while using the Advanced Bracket.
I haven't used the function before.
My version is a bit older. Should I update something first?

Code Select Expand

ML ASSERT:
0
at ../../src/raw.c:611 (raw_lv_realloc_buffer), task livev_hiprio_task
lv:0 mode:3

livev_hiprio_task stack: 2086c0 [208838-204838]
0x0048F7E0 @ 487934:208720
0x0048F750 @ 48f840:208718
0x0048D1DC @ 48f780:208710
0x0044C9F4 @ 48d37c:2086f0
0x0044C478 @ 44ca50:2086c0

Magic Lantern version : lua_fix.2018Sep17.6D116
Mercurial changeset   : 0040e6ccea8d (lua_fix) tip
Built on 2018-09-17 16:45:37 UTC by jenkins@nightly.
Free Memory  : 384K + 1895K

Would be interesting to know whether you could also switch off the crop mode for EFS lenses.

No link given and therefore unable to check source.

If it is important and something changes, then I can look for it in the CHDK forum.

They could have done so back in 2012, when we were accepting donations, or in 2013, when we've got a massive popularity spike after announcing ...

Thank you very much for the detailed explanation.
As an enthusiastic CHDK and ML fan, I naturally hope that it will continue ...

Update: just received an e-mail from Open Collective, titled: " We can host Magic Lantern! "

In the CHDK forum I once heard the statement that as soon as CHDK became more commercial, Canon could protect its cameras better for debugging. Is that to be expected here too?