supplierdeeply
« previous next »
Pages: 1 [2] 3   Go Down

Maximum operating voltage of the G1x / M3 / M10

  • 23 Replies
  • 694 Views
*

Offline waterwingz

  • ******
  • 11048
    • Waterwingz
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #10 on: 29 / June / 2017, 17:37:28 »
    Advertisements
    Quote from: reyalp on 29 / June / 2017, 16:45:26
    This kind of behavior may be camera/sd card/script logging strategy dependent. IIRC waterwingz did see something similar to what you describe with one of his scripts.
    link >  KAP & UAV Exposure Control Intervalometer Script Post #785
    Logged
    Ported : A1200  SD940  G10  Powershot N  G16*
    *

    Offline lapser

    • *****
    • 1053
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #11 on: 29 / June / 2017, 18:30:23 »
    Thanks for the reply, reyalp. Let me say that the script hooks are fantastic! I'm really looking forward to working with them. I'll post my test script in a new topic when it's ready and maybe you can help me with it. I'm going to try to use the test script tomorrow night to do a time lapse of the moons of Jupiter through a telescope, using the EOS-M3 and your hook_shoot routines. I've been wanting to do that for years.

    The timing problem I described only happens when saving Canon RAW files. When you hold the shutter down on the G1X with RAW files, it gets very irregular after awhile. The camera says "Busy" a lot as it waits for the 14mb raw files to be written when the buffer is full.

    I've discovered that the keyboard task (and script) is blocked during this "Busy" time. Writing to a log file during the busy time blocks the script even longer.

    The problem with hook_shoot is that the shutter has to be triggered by the script, in the keyboard task, which is blocked when the camera is "Busy".

    I minimized this by using an independent set_shot_interval() which runs independently of the script. But I really love the amount of control your hooks give to scripts. So would you consider adding a few simple functions to your shooting hook? They would do something like this:

    set_next_shutter_open_time(tick_count)

    get_last_shutter_open_time()

    get_last_shutter_ready_time()

    That would still give the script total control but eliminate the need for polling, and the timing problems that go with it.

    Also, I recall my development topic was "Shot Histogram Request." From reading your info on the new histogram functions, you fulfilled that request beyond my wildest dreams! I can wait to try them out.
    Logged
    EOS-M3_101a / SX50_100b / SX260_101a / G1X_100g / D20_100b
    https://www.youtube.com/user/DrLapser/videos
    *

    Offline c_joerg

    • ****
    • 424
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #12 on: 30 / June / 2017, 04:15:44 »
    Quote from: lapser on 29 / June / 2017, 12:13:26
    My G1X doesn't shut down or display "low battery" when the external battery gets low. It just crashes like you unplugged the power cable. I'm not using a Canon dummy battery. Does your G1X do a controlled shut down when the external battery is depleted?

    Ok, now I understood. If I use external battery, I don’t have the battery symbol and I don’t see "low battery". I don’t know if my G1x do a controlled shut down with external battery, because rawopint made the controlled shut down instead. I didn’t had other situations before.

    Quote from: lapser on 29 / June / 2017, 12:13:26
    Are you using a Canon dummy battery?

    I think so. What do mean with Canon dummy battery? In my first topic you can see a photo of the adapter which I use. Is this not the same what you are using?

    Quote from: lapser on 29 / June / 2017, 12:13:26
    What's the fastest shot rate you've done with rawopint on the G1X saving raw files? I usually use 1500 msec intervals.

    I the past, I always used RAW + JPG, because I don’t had much experience with RAW development. I never tried intervals with only RAW’s less than 2000msec.  But I can try it with 1500msec.

    If you need fast Interval, we have to port the EOS M5/M6  ;)

    Quote from: reyalp on 29 / June / 2017, 16:45:26
    This kind of behavior may be camera/sd card/script logging strategy dependent.

    That’s the think. Rawopint give you the ‚sleep‘ value (How long the script slept between shots). On some of my SD cards, the value looks very noisy.  Sometimes this value is nearly constants and then I got a big jump on one shoot. So SD cards have a big influence of shortest interval.


    Quote from: lapser on 28 / June / 2017, 09:09:48
    I use an 8.4 volt battery pack designed for bicycle lights. It has rubber straps to attach it to handlebars that attach nicely to tripod legs. It's also very inexpensive!
    I have one for my S110 with 3,7V. But I have always discussions on the airport with this batteries..



    Back to the main question:
    If I use my sixfold battery holder with standard AA batteries I could do the following
    1) Running it with 6 * 1.6V = 9.6V would be to high voltage.
    2) Running it with 5 * 1.6V + one dummy = 8V.
    3) Running it with 6 * 1.6V + diode in series = 8.9V.

    How much time (shoots) I have more with option 3 against option 2?
    And what would be the minimum operating voltage of G1x when I have not taken care about the batteries.

    I’m still thinking about this solution:
    http://www.studiolighting.net/items/5v-Usb-Drive-Cable-Ack-e15-Dr-e15-lc-e15e-Lp-e15-Dc-Battery-For-Canon-100d_301984952177.html

    Or

    Open two powerbanks.
    https://chdk.setepontos.com/index.php?topic=12485.msg124202#msg124202
    Place the 3.7v batteries on sockets and connect them in series as shown
    https://chdk.setepontos.com/index.php?topic=12485.msg124291#msg124291


    « Last Edit: 30 / June / 2017, 05:30:47 by c_joerg »
    Logged
    *

    Offline lapser

    • *****
    • 1053
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #13 on: 30 / June / 2017, 13:04:18 »
    I didn't realize a "powerbank" had 18650 cells. If you can get 18650's on the plane, I recommend buying one of these:
    https://www.amazon.com/Hanperal-18650-Resistant-Battery-Bicycle/dp/B018A96ZVK/

    When the connectors broke on a battery bank I was using, I took the 18650's out of it and put them in the above battery box. It ran the G1X all night one time. You can take the 18650's out of the box to go on the plane. It has the added bonus of a USB connector, so you can also charge phones with it.
    ===
    Try rawopint with raw+jpg at 1500 interval or less, and check the sleep times. Watch the camera and note when it says "busy". That should correspond to shorter or 0 sleep times.

    I log the "sleep" value, and also the time it takes to write each line of the log file. I'll attach the log file from last Wednesday night. You can watch the time lapse here:
    https://www.youtube.com/watch?v=zqY6H4botD0

    The timing info consist of "IntD", which is the sleep time before the shot. A negative value means the shot is late. "PD" is the time spent in the print statement.

    These values are seconds*100, so add a 0 at the end to get msec. A value of 100 is 1 second. Note that the print delay, PD, reaches 1 second without IntD being affected.

    My script does smoothed ETTR, which overexposes a little sometimes, especially right after sunset. I can fade out the video track a little to counteract that. I also posted a test video which shows original and faded versions together:
    Logged
    EOS-M3_101a / SX50_100b / SX260_101a / G1X_100g / D20_100b
    https://www.youtube.com/user/DrLapser/videos
    *

    Offline c_joerg

    • ****
    • 424
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #14 on: 30 / June / 2017, 13:57:05 »
    Quote from: lapser on 28 / June / 2017, 17:04:45
    With an external battery, the camera just turns off like you unplugged the power. In continuous mode, you lose all the pictures in the current directory (up to 2000) and the log file written since the camera changed directories.
    I can’t confirm it. I just tried it. I run rawopint in continuous mode. I used external power supply and went slowly down with power. Camera goes off. Lens goes in. Log file from rawopint was empty (only first info line was OK). But RAW Data was there and OK. May be unplugging the power is different. But I don’t want to try this.
    Quote from: lapser on 30 / June / 2017, 13:04:18
    Try rawopint with raw+jpg at 1500 interval or less, and check the sleep times.
    Why now raw+jpg? I tried raw already on the afternoon
    Quote from: lapser on 29 / June / 2017, 12:13:26
    What's the fastest shot rate you've done with rawopint on the G1X saving raw files? I usually use 1500 msec intervals.
    Made 2 runs with rawopint in continuous mode. Only RAW. 1400msec doesn’t work. 1500msec looks Ok. At least for 35 shoots. THe two runs are behind in one plot.
    Quote from: lapser on 30 / June / 2017, 13:04:18
    and check the sleep times.
    Sleep is around 500ms on the 1500msec Interval but when I got to 1400msec, it doesn’t work anymore. What does sleep really say?
    Quote from: lapser on 30 / June / 2017, 13:04:18
    I didn't realize a "powerbank" had 18650 cells. If you can get 18650's on the plane, I recommend buying one of these: .
    My wife and children always go through with your fat powerbanks (10000 to 22000mAh) and have never problems. Powerbanks has just everyone ... nobody see the cells…
    My battery holder with the AA NiMh 2800mAh is sent several times through the scanner and reviewed. Presumably, it is the free cables and the hot glue. Then it is sometimes decided, the batteries are not allowed with. I would think, single 18650 cells would be the same problem.
    Quote from: lapser on 30 / June / 2017, 13:04:18
    My script does smoothed ETTR, which overexposes a little sometimes, especially right after sunset.
    Locks great  :). Locking forward to hear more about it…

    « Last Edit: 30 / June / 2017, 13:58:53 by c_joerg »
    Logged
    *

    Offline reyalp

    • ******
    • 10668
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #15 on: 30 / June / 2017, 23:33:49 »
    Quote from: c_joerg on 30 / June / 2017, 13:57:05
    Sleep is around 500ms on the 1500msec Interval but when I got to 1400msec, it doesn’t work anymore. What does sleep really say?
    Sleep is the time between time between when the script reaches the point it thinks it can shoot again (the remote hook) and when the next shot should occur. Some things can happen in parallel, so it wouldn't be totally surprising if the camera can't actually maintain the interval implied by sleep, although AFAIK all of my cameras do.

    Note the location of the remote hook in the G1 X port was changed recently (1.5 build 4799 /  1.4 build 4800) to address a bug. This might affect the behavior of rawopint because it changes where in the process the script waits.
    Logged
    Don't forget what the H stands for.
    *

    Offline reyalp

    • ******
    • 10668
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #16 on: 30 / June / 2017, 23:45:46 »
    Quote from: lapser on 29 / June / 2017, 18:30:23
    I minimized this by using an independent set_shot_interval() which runs independently of the script. But I really love the amount of control your hooks give to scripts. So would you consider adding a few simple functions to your shooting hook? They would do something like this:
    I'd need a better understanding of the problem first. If it's really only specific to the g1x I wouldn't want to add a bunch of features to script just to work around problems with one port. I haven't seen the problem you described on g7x (which FWIW can shoot raw at ~1 FPS) but I have done a lot of timelapse with it.

    Quote
    Also, I recall my development topic was "Shot Histogram Request." From reading your info on the new histogram functions, you fulfilled that request beyond my wildest dreams! I can wait to try them out.
    All the raw hook / raw meter / histogram stuff was inspired by your work, so thank you! (and uh, sorry it took a few years  :-[)
    Logged
    Don't forget what the H stands for.
    *

    Offline c_joerg

    • ****
    • 424
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #17 on: 01 / July / 2017, 02:35:38 »
    Quote from: reyalp on 30 / June / 2017, 23:33:49
    Note the location of the remote hook in the G1 X port was changed recently (1.5 build 4799 /  1.4 build 4800) to address a bug. This might affect the behavior of rawopint because it changes where in the process the script waits.
    Well Ok. It's time for an update. When you are happy, ‘You never change a ruining system’. So I will try it again.
    Logged
    *

    Offline c_joerg

    • ****
    • 424
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #18 on: 01 / July / 2017, 08:35:40 »
    I did some measuring with the simple 6 AA batteries in the sixfold battery holder.
    Voltage on the dummy batterie outside the camera 9,6V.
    The camera shows in record mode 8,8V. So it works.
    It looks as if the construction has a very large transitional resistance (approx. 0,8V / 0.4A = 2Ohm)
    NB10L Batterie
    Outside 8,3V; Inside 8,1V.
    I notice the transitional resistance from the sixfold battery holder before. The power supply is noisier. Plot shows voltage from NB10L and 6 AA NiMh batteries while time-lapse.
    Logged
    *

    Offline c_joerg

    • ****
    • 424
  • Publish
    Re: Maximum operating voltage of the G1x / M3 / M10
    « Reply #19 on: 02 / July / 2017, 12:12:51 »
    Quote from: lapser on 29 / June / 2017, 12:13:26
    What's the fastest shot rate you've done with rawopint on the G1X saving raw files? I usually use 1500 msec intervals.

    Quote from: reyalp on 30 / June / 2017, 23:33:49
    Note the location of the remote hook in the G1 X port was changed recently (1.5 build 4799 /  1.4 build 4800) to address a bug. This might affect the behavior of rawopint because it changes where in the process the script waits.
    Update CHDK to 1.5 build 4841.
    I can run rawopint now with 1100ms intervals without error (40 shoots).  :)  :)  :)
    Is this build really faster or is just calculation of sleep now correct?
    Logged
    Pages: 1 [2] 3   Go Up
    « previous next »
     

    Related Topics