Fuji X-T2, USB ID 04cb:02cd #133

jbreiden · 2017-01-23T19:08:25Z

This is the Fuji X-T2 camera. I'll look into USB communication details next.

$ lsusb | grep Fuji
Bus 004 Device 004: ID 04cb:02cd Fuji Photo Film Co., Ltd

--- a/camlibs/ptp2/library.c
+++ b/camlibs/ptp2/library.c
@@ -1978,6 +1978,7 @@ static struct {
        {"Fuji:Fujifilm X-E2",                  0x04cb, 0x02b5, 0},
        /* Vladimir K <enewsletters@inbox.ru> */
        {"Fuji:Fujifilm X-T1",                  0x04cb, 0x02bf, 0},
+        {"Fuji:Fujifilm X-T2",                 0x04cb, 0x02cd, 0},
        /* https://github.com/gphoto/libgphoto2/issues/32 */
        {"Fuji:Fujifilm X-T10",                 0x04cb, 0x02c8, 0},

jbreiden · 2017-01-23T22:53:36Z

0.066445 print_debug_deviceinfo      (2): Device info:
0.066448 print_debug_deviceinfo      (2): Manufacturer: FUJIFILM
0.066451 print_debug_deviceinfo      (2):   Model: X-T2
0.066453 print_debug_deviceinfo      (2):   device version: 1.00
0.066455 print_debug_deviceinfo      (2):   serial number: '5935333130321611296B3020112361'
0.066457 print_debug_deviceinfo      (2): Vendor extension ID: 0x0000000e
0.066459 print_debug_deviceinfo      (2): Vendor extension version: 100
0.066462 print_debug_deviceinfo      (2): Vendor extension description: fujifilm.co.jp: 1.0; 
0.066464 print_debug_deviceinfo      (2): Functional Mode: 0x0000
0.066466 print_debug_deviceinfo      (2): PTP Standard Version: 100
0.066468 print_debug_deviceinfo      (2): Supported operations:
0.066473 print_debug_deviceinfo      (2):   0x1001 (Get device info)
0.066476 print_debug_deviceinfo      (2):   0x1002 (Open session)
0.066479 print_debug_deviceinfo      (2):   0x1003 (Close session)
0.066482 print_debug_deviceinfo      (2):   0x1004 (Get storage IDs)
0.066484 print_debug_deviceinfo      (2):   0x1005 (Get storage info)
0.066487 print_debug_deviceinfo      (2):   0x1006 (Get number of objects)
0.066489 print_debug_deviceinfo      (2):   0x1007 (Get object handles)
0.066492 print_debug_deviceinfo      (2):   0x1008 (Get object info)
0.066494 print_debug_deviceinfo      (2):   0x1009 (Get object)
0.066497 print_debug_deviceinfo      (2):   0x100a (Get thumbnail)
0.066500 print_debug_deviceinfo      (2):   0x100b (Delete object)
0.066502 print_debug_deviceinfo      (2):   0x100c (Send object info)
0.066505 print_debug_deviceinfo      (2):   0x100d (Send object)
0.066507 print_debug_deviceinfo      (2):   0x100f (Format storage)
0.066510 print_debug_deviceinfo      (2):   0x1014 (Get device property description)
0.066513 print_debug_deviceinfo      (2):   0x1015 (Get device property value)
0.066516 print_debug_deviceinfo      (2):   0x1016 (Set device property value)
0.066518 print_debug_deviceinfo      (2):   0x101b (Get partial object)
0.066521 print_debug_deviceinfo      (2):   0x900c (Unknown VendorExtensionID)
0.066524 print_debug_deviceinfo      (2):   0x900d (Unknown VendorExtensionID)
0.066526 print_debug_deviceinfo      (2):   0x901d (Unknown VendorExtensionID)
0.066529 print_debug_deviceinfo      (2):   0x9801 (Unknown VendorExtensionID)
0.066532 print_debug_deviceinfo      (2):   0x9802 (Unknown VendorExtensionID)
0.066534 print_debug_deviceinfo      (2):   0x9803 (Unknown VendorExtensionID)
0.066537 print_debug_deviceinfo      (2):   0x9805 (Unknown VendorExtensionID)
0.066539 print_debug_deviceinfo      (2): Events Supported:
0.066541 print_debug_deviceinfo      (2):   0x4002 
0.066542 print_debug_deviceinfo      (2):   0x4003
0.066544 print_debug_deviceinfo      (2):   0x4004
0.066546 print_debug_deviceinfo      (2):   0x4005
0.066547 print_debug_deviceinfo      (2):   0x4006
0.066549 print_debug_deviceinfo      (2):   0x4008
0.066551 print_debug_deviceinfo      (2):   0x4009
0.066552 print_debug_deviceinfo      (2): Device Properties Supported:
0.066554 print_debug_deviceinfo      (2):   0x5001
0.066556 print_debug_deviceinfo      (2):   0xd303
0.066558 print_debug_deviceinfo      (2):   0xd406
0.066559 print_debug_deviceinfo      (2):   0xd407

0x4002 ObjectAdded
0x4003 ObjectRemoved
0x4004 StoreAdded
0x4005 StoreRemoved
0x4006 DevicePropChanged
0x4007 ObjectInfoChanged
0x4008 DeviceInfoChanged
0x4009 RequestObjectTransfer

0x5001 BatteryLevel

msmeissn · 2017-01-24T07:41:48Z

So far there is no indication that it has capture opcodes.
The only unknown opcodes are 900c, 900d, 901d
(The 0x98xx opcodes are generic MTP commands.)
There is no event for capturecomplete.
The 0xd303 and 0xd4xx properties are the standard MTP properties.

While capture might be hiding behind the 0x90xx codes or be hidden from the deviceinfo altogether, this seems unlikely.

jbreiden · 2017-01-24T16:29:07Z

Tethering capability was added in firmware revision 1.1 released Nov 2016. I will update the camera today.

jbreiden · 2017-01-24T16:57:17Z

To my surprise, the newer firmware (which supports tethering) has identical opcodes. I'll will shortly have my hands on a Windows computer and will endeavor to monitor USB communication during tethering. If there is a preferred mechanism for USB sniffing on Windows, please let me know.

0.034602 print_debug_deviceinfo      (2): Device info:
0.034605 print_debug_deviceinfo      (2): Manufacturer: FUJIFILM
0.034607 print_debug_deviceinfo      (2):   Model: X-T2
0.034609 print_debug_deviceinfo      (2):   device version: 1.10
0.034611 print_debug_deviceinfo      (2):   serial number: '5935333130321611296B3020112361'
0.034613 print_debug_deviceinfo      (2): Vendor extension ID: 0x0000000e
0.034614 print_debug_deviceinfo      (2): Vendor extension version: 100
0.034617 print_debug_deviceinfo      (2): Vendor extension description: fujifilm.co.jp: 1.0; 
0.034619 print_debug_deviceinfo      (2): Functional Mode: 0x0000
0.034621 print_debug_deviceinfo      (2): PTP Standard Version: 100
0.034622 print_debug_deviceinfo      (2): Supported operations:
0.034627 print_debug_deviceinfo      (2):   0x1001 (Get device info)
0.034629 print_debug_deviceinfo      (2):   0x1002 (Open session)
0.034631 print_debug_deviceinfo      (2):   0x1003 (Close session)
0.034634 print_debug_deviceinfo      (2):   0x1004 (Get storage IDs)
0.034636 print_debug_deviceinfo      (2):   0x1005 (Get storage info)
0.034638 print_debug_deviceinfo      (2):   0x1006 (Get number of objects)
0.034640 print_debug_deviceinfo      (2):   0x1007 (Get object handles)
0.034643 print_debug_deviceinfo      (2):   0x1008 (Get object info)
0.034645 print_debug_deviceinfo      (2):   0x1009 (Get object)
0.034647 print_debug_deviceinfo      (2):   0x100a (Get thumbnail)
0.034649 print_debug_deviceinfo      (2):   0x100b (Delete object)
0.034651 print_debug_deviceinfo      (2):   0x100c (Send object info)
0.034654 print_debug_deviceinfo      (2):   0x100d (Send object)
0.034656 print_debug_deviceinfo      (2):   0x100f (Format storage)
0.034658 print_debug_deviceinfo      (2):   0x1014 (Get device property description)
0.034661 print_debug_deviceinfo      (2):   0x1015 (Get device property value)
0.034663 print_debug_deviceinfo      (2):   0x1016 (Set device property value)
0.034665 print_debug_deviceinfo      (2):   0x101b (Get partial object)
0.034668 print_debug_deviceinfo      (2):   0x900c (Unknown VendorExtensionID)
0.034670 print_debug_deviceinfo      (2):   0x900d (Unknown VendorExtensionID)
0.034672 print_debug_deviceinfo      (2):   0x901d (Unknown VendorExtensionID)
0.034674 print_debug_deviceinfo      (2):   0x9801 (Unknown VendorExtensionID)
0.034677 print_debug_deviceinfo      (2):   0x9802 (Unknown VendorExtensionID)
0.034679 print_debug_deviceinfo      (2):   0x9803 (Unknown VendorExtensionID)
0.034681 print_debug_deviceinfo      (2):   0x9805 (Unknown VendorExtensionID)
0.034683 print_debug_deviceinfo      (2): Events Supported:
0.034684 print_debug_deviceinfo      (2):   0x4002
0.034686 print_debug_deviceinfo      (2):   0x4003
0.034687 print_debug_deviceinfo      (2):   0x4004
0.034689 print_debug_deviceinfo      (2):   0x4005
0.034690 print_debug_deviceinfo      (2):   0x4006
0.034692 print_debug_deviceinfo      (2):   0x4008
0.034693 print_debug_deviceinfo      (2):   0x4009
0.034695 print_debug_deviceinfo      (2): Device Properties Supported:
0.034696 print_debug_deviceinfo      (2):   0x5001
0.034698 print_debug_deviceinfo      (2):   0xd303
0.034699 print_debug_deviceinfo      (2):   0xd406
0.034701 print_debug_deviceinfo      (2):   0xd407

msmeissn · 2017-01-24T17:04:03Z

In in earlier times used SnoopyPro. Not sure if it still lives..

Can you try

gphoto2 --capture-tethered

and press shutter button and see if something happens?

jbreiden · 2017-01-24T17:06:26Z

Nothing. I'll play with the camera and make sure that I'm in the right mode.

31.309643 camera_wait_for_event       (2): no events received.
31.309653 camera_wait_for_event       (2): waiting for events timeout 1000 ms
31.309661 gp_port_get_timeout         (2): Current port timeout is 20000 milliseconds.
31.309667 gp_port_set_timeout         (2): Setting port timeout to 150 milliseconds.
31.309674 gp_port_check_int           (3): Reading 24 = 0x18 bytes from interrupt endpoint...
31.459909 gp_port_check_int           (3): Reading 24 = 0x18 bytes from interrupt endpoint...
31.610150 gp_port_set_timeout         (2): Setting port timeout to 20000 milliseconds.
31.610200 ptp_usb_event [usb.c:530]   (0): Reading PTP event failed: Timeout reading from or writing to the port (-10)

jbreiden · 2017-01-24T17:13:03Z

Now with the camera in the correct mode (Connection Setting > PC Shoot Mode > USB Auto) we get a lot more. Still nothing from gphoto2 --capture-tethered

log.txt

jbreiden · 2017-01-24T17:26:36Z

Wait, maybe I am getting something. Need to charge battery.

jbreiden · 2017-01-24T17:48:05Z

$ gphoto2 --capture-tethered --camera="Fuji Fujifilm X-T2" --debug --debug-logfile=/tmp/debug.txt --debug-loglevel=debug
Waiting for events from camera. Press Ctrl-C to abort.                         
Saving file as DSCF0001.jpg                                                    
^C
Cancelling...

debug.txt

msmeissn · 2017-01-25T10:05:16Z

0.035898 print_debug_deviceinfo (2): 0x100e (Initiate capture)

gphoto2 --capture-image now should also work

jbreiden · 2017-01-26T01:21:09Z

$ gphoto2 --capture-image
                                                                               
*** Error ***              
PTP Device Busy
ERROR: Could not capture image.
ERROR: Could not capture.
*** Error (-110: 'I/O in progress') ***       

For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list <gphoto-devel@lists.sourceforge.net>, please run
gphoto2 as follows:

    env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --capture-image

Please make sure there is sufficient quoting around the arguments.

debug.txt

msmeissn · 2017-01-27T21:37:34Z

usually that should just work as is when called. hard to say why it reports busy :(

can you get output of:

gphoto2 --summary > summary.txt
gphoto2 --list-all-config > allconfig.txt

jbreiden · 2017-01-27T22:12:23Z

Had to reschedule USB tracing, should have that by the end of Monday.

summary.txt
allconfig.txt

jbreiden · 2017-01-30T23:45:12Z

The one of most interest is Single Shot

Data viewer
http://www.totalphase.com/products/data-center/

Traces
https://drive.google.com/drive/folders/0B1NxYWevtHcMdHJmcVBLVEdzalU?usp=sharing

jbreiden · 2017-02-02T18:32:49Z

Decoded USB traces added to same location. Note the double call to InitiateCapture.

jbreiden · 2017-02-02T23:50:54Z

I think the camera is unhappy and becomes "PTP Device Busy" because when we try to list the files on the camera. Here is what gphoto2 is doing.

$ gphoto2 --debug --capture-image |& grep Sending | cut -f2 -d:
 Sending PTP_OC 0x1002 (Open session) (0x1) request...
 Sending PTP_OC 0x1001 (Get device info) request...
 Sending PTP_OC 0x1007 (Get object handles) (0xffffffff,0x0,0xffffffff) request...
 Sending PTP_OC 0x1004 (Get storage IDs) request...
 Sending PTP_OC 0x1007 (Get object handles) (0x10000001,0x0,0xffffffff) request...
 Sending PTP_OC 0x1007 (Get object handles) (0x10000002,0x0,0xffffffff) request...
 Sending PTP_OC 0x100e (Initiate capture) (0x0,0x0) request...
 FAIL

Comparing to the working USB trace, there isn't any attempt to get object handles until after capture is complete. And when it does happen, it looks different to my eye.

$ grep COMMAND Single\ Shot.txt | cut -f4- -d: | less
...
PTP_OC_InitiateCapture         trans:831c payload:'\x00\x00\x00\x00\x00\x00\x00\x00'
...
PTP_OC_InitiateCapture         trans:835e payload:'\x00\x00\x00\x00\x00\x00\x00\x00'
...
PTP_OC_GetObjectHandles        trans:8365 payload:'\xff\xff\xff\xff\x00\x00\x00\x00\x00\x00\x00\x00'
PTP_OC_GetObjectInfo           trans:8366 payload:'\x07\x00\x00\x00'
PTP_OC_GetObjectInfo           trans:8367 payload:'\x07\x00\x00\x00'
PTP_OC_GetObjectInfo           trans:8368 payload:'\x07\x00\x00\x00'
PTP_OC_MTP_GetObjPropList      trans:8369 payload:'\x07\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00'
PTP_OC_GetObject               trans:836a payload:'\x07\x00\x00\x00'
PTP_OC_DeleteObject            trans:836b payload:'\x07\x00\x00\x00'
...

msmeissn · 2017-02-03T07:27:46Z

This is very helpful, thanks. It is setting various properties, that is probably more the reason.

(currently a bit busy witjh work and FOSDEM travel, hope to have some time next week to check it out more)

jbreiden · 2017-02-06T23:13:13Z

This appears to be the magical incantation to allow InitiateCapture() to work. Only works once per camera powercycle. This will make the camera beep, presumably indicating successful autofocus.

propval.u16 = 0x0002; C_PTP_REP (ptp_setdevicepropvalue (params, 0xd207, &propval, PTP_DTC_UINT16));
propval.u16 = 0x0200; C_PTP_REP (ptp_setdevicepropvalue (params, 0xd208, &propval, PTP_DTC_UINT16));
C_PTP_REP(ptp_initiatecapture(params, 0x00000000, 0x00000000));

Add in this part, and we get a click sound after the beep.

usleep(1000*1000);
propval.u16 = 0x0304; C_PTP_REP (ptp_setdevicepropvalue (params, 0xd208, &propval, PTP_DTC_UINT16));
C_PTP_REP(ptp_initiatecapture(params, 0x00000000, 0x00000000));

At this point the camera is blocked and unresponsive to further shot requests. The camera has in image in RAM and is very afraid to lose that data. There is a small LED on the camera body the flashes red and green. I have to unplug USB, turn off the power switch, then hit "okay" to actually powercycle and prepare for next shot.

Here's a debug log when I plumb this through --capture-image-and-download.

debuglog.txt

#133

msmeissn · 2017-02-07T07:32:48Z

ignore last commit, it seems per-captuyre specific.

msmeissn · 2017-02-07T07:38:17Z

(thanks for your work so far ... still not yet found time to properly go over it :/ )

jbreiden · 2017-04-19T21:22:44Z

Looking at Fuji XT-2 again. This is what it takes to make a "beep" (presumably autofocus) then a "click" (presumably shutter release) using gphoto2 --trigger-capture. Contrary to my earlier reports above, the only property I'm messing with is 0xd208. And this is sufficient run multiple times without power cycling. Yay. I am going to try to rewrite this for real. (Also, we need to revert c998fcd which is causing harm)

happy.txt

--- a/camlibs/ptp2/library.c
+++ b/camlibs/ptp2/library.c
@@ -4577,7 +4577,15 @@ camera_trigger_capture (Camera *camera, GPContext *context)
                        _("Sorry, your camera does not support generic capture"));
                return GP_ERROR_NOT_SUPPORTED;
        }
-       C_PTP_REP (ptp_initiatecapture(params, 0x00000000, 0x00000000));
+        {
+          PTPPropertyValue     propval;
+          propval.u16 = 0x0200; C_PTP_REP (ptp_setdevicepropvalue (params, 0xd208, &propval, PTP_DTC_UINT16));
+          C_PTP_REP (ptp_initiatecapture(params, 0x00000000, 0x00000000));
+          usleep(1000*1000);
+          propval.u16 = 0x0304; C_PTP_REP (ptp_setdevicepropvalue (params, 0xd208, &propval, PTP_DTC_UINT16));
+          C_PTP_REP(ptp_initiatecapture(params, 0x00000000, 0x00000000));
+        }
+
        return GP_OK;
 }

jbreiden · 2017-04-19T22:19:12Z

... And now I can't communicate with the camera under any circumstance. Same code, nothing obviously different from the logs. Powercycled camera including primary battery removal. Wasn't fooling around with camera settings.

sad.txt

0.163308 camera_trigger_capture      (2): camera_trigger_capture
0.163321 camera_trigger_capture      (2): Triggering capture to , autofocus=0
0.163329 camera_trigger_capture      (2): XXX Hey
0.163356 ptp_usb_sendreq             (2): Sending PTP_OC 0x1016 (Set device property value) (0xd208) request...
0.163428 ptp_usb_senddata            (2): Sending PTP_OC 0x1016 (Set device property value) data...
0.163499 ptp_usb_getresp             (2): Reading PTP_OC 0x1016 (Set device property value) response...
0.363983 ptp_usb_sendreq             (2): Sending PTP_OC 0x100e (Initiate capture) (0x0,0x0) request...
0.364127 ptp_usb_getresp             (2): Reading PTP_OC 0x100e (Initiate capture) response...
0.364739 ptp_usb_getresp [usb.c:466] (0): PTP_OC 0x100e receiving resp failed: PTP Device Busy (0x2019)
0.364752 camera_trigger_capture [library.c:4585](0): 'ptp_initiatecapture(params, 0x00000000, 0x00000000)' failed: 'PTP Device Busy' (0x2019)
0.364763 gp_context_error            (0): PTP Device Busy

*** Error ***              
PTP Device Busy
0.364778 gp_camera_trigger_capture [gphoto2-camera.c:1369](0): 'camera->functions->trigger_capture (camera, context)' failed: -110
ERROR: Could not trigger capture.
*** Error (-110: 'I/O in progress') ***

jbreiden · 2017-04-24T16:51:34Z

Flashed camera firmware to from v1.10 to v2.00; no change. Camera does not want to talk to me anymore.

msmeissn · 2017-04-24T18:51:49Z

urks :( sorry to hear :(

and sorry i currently did not pursue this issue further .. quite busy and i focused a bit more on pentax and canon eos m, but wanted to get back here

msmeissn · 2017-04-24T18:56:22Z

check for possible causes of busy condit9ion ... sd card full? bttery empty? ;)

msmeissn · 2017-11-15T15:34:03Z

I tried this with a XT-2 of a colleague today and the d202 does not seem to do receive changes here.
also d38c seems not settable.

did you make any further progress here?

anarcat · 2018-07-18T03:54:28Z

so for what it's worth, i have a X-T2 body with the latest (i believe) firmware version 4.10 here and capture definitely does not work with gphoto2 2.5.17-1 as compiled in debian unstable (but running in stable/stretch). I get the Sorry, your camera does not support generic capture error, with the following logfile:

my-logfile.txt

i'm available for further debugging if that's useful at all. it would be great to see this working! but in the meantime, maybe it would be better to add a notice about the problems here in the support page so people know it's not quite there yet...

more debug info:

$ gphoto2 --auto-detect
Modèle                        Port                                             
----------------------------------------------------------
Fuji Fujifilm X-T2             usb:002,034

HTH!

jbreiden · 2018-07-18T18:22:12Z

I haven't used gphoto2 for a while, but I did write some other software that happily talks to the X-T2 on a daily basis. Will take a look when I have the chance.

SET UP > CONNECTION SETTING > PC SHOOT MODE : USB AUTO

msmeissn · 2018-07-19T07:33:38Z

I used a colleagues XT-2 soem days ago, it was working fine with capture :/

darix · 2018-07-21T15:52:09Z

@jbreiden Where is your software?

jbreiden · 2018-07-21T22:41:02Z

@darix proprietary

anarcat · 2018-07-22T05:12:14Z

SET UP > CONNECTION SETTING > PC SHOOT MODE : USB AUTO

Duh. I didn't remember I had set that to "USB card" mode or something. Obviously, it works with that, although live view doesn't which is kind of annoying.. But thanks!

darix · 2018-07-22T14:52:30Z

live view will probably work in master. you can grab the tarball from here https://build.opensuse.org/package/show/graphics/libgphoto2 or pull it via github and build that. that should give you all the improvements from the hackweek, where @msmeissn tested with my x-t2

darix · 2018-07-22T14:52:54Z

@jbreiden pity :P

anarcat · 2018-07-22T16:54:56Z

On 2018-07-22 07:52:32, darix wrote: live view will probably work in master. you can grab the tarball from here https://build.opensuse.org/package/show/graphics/libgphoto2 or pull it via github and build that. that should give you all the improvements from the hackweek, where @msmeissn tested with my x-t2

amazing, thanks!!!

jbreiden · 2018-07-23T18:12:40Z

I'm attaching an annotated transcript of exactly what I send to the Fuji X-T2 with my own progam. Hope it helps, and happy to discuss with @msmeissn or @elijahparker. I have never attempted setting either d38c or d202.

EDIT: I just tried setting d38c on an Fuji X-T2 with ancient firmware, and didn't get an error. As far as I can tell, it didn't actually do anything. Not sure what d202 is even supposed to do.

transcript.txt

ghost · 2019-08-27T21:10:24Z

Not sure whether to open a new issue or to place it here. As I’m facing the same issues with my X-T1 as they are reported above, i placed it in this issue. I hope that's ok.
According to the support page, the X-T1 should work the same, as the X-T2.
But the command "capture-image-and-download" results exactly in the same behavior as reported above in # #133 (comment) : Just once per power cycle and the camera body the flashes red and green and is afraid of losing the picture in its RAM...
The command "--capture-preview" works well, indeed.

My setup is:

Camera: Fuji X-T1
SW version camera: 5.51
Camera Mode: PC SHOOT MODE : USB AUTO
no sd card inserted
gphoto: 2.5.23

Here's a debug log for "env LANG=C gphoto2 --debug --debug-logfile=debug_XT1.txt --capture-image-and-download"

debug_XT1.txt

I’m available for further debugging and would be very happy to see this working! Thank you!

kritzikratzi · 2019-11-20T00:00:49Z

just a side note to this thread:

today i got my x-t1 (seemed the perfect timelapse camera). gphoto gets stuck after --capture-image with the red-green blinking led (don't know enough about usb to figure out why).

for now i'm using the camera + sd-card and this script to take an image and download it:

mkdir out
# kill with signal 9 after 2 seconds
# gphoto would get stuck forever otherwise ... 
gtimeout -s 9 2 gphoto2 --auto-detect --capture-image
gphoto2 --get-all-files

last=$(ls out | sort | tail -n 1)
seq=${last%.jpg}
seq=$(echo $seq | sed 's/^0*//')
seq=$(printf '%d' "$seq")
echo "Last sequence number: $seq"

for file in *.jpg
do
	seq=$((seq + 1))
	next=$(printf '%07d.jpg' "$seq")
	echo "$file -> out/$next"
	mv $file out/$next
done
echo seq=$next
gphoto2 --delete-all-files --folder=/store_10000001

i've only taken a few hundred images to test, seems fine so far. and as ugly as it is, it's good enough for my purposes.

gphoto2 2.5.23 clang, popt(m), no exif, no cdk, no aa, jpeg, readline
libgphoto2 2.5.23 all camlibs, clang, ltdl, no EXIF
libgphoto2_port 0.12.0 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, clang, ltdl, USB, serial without locking
osx 10.14 with coreutils installed (for gtimeout)

anarcat · 2019-12-19T15:45:45Z

live view will probably work in master. you can grab the tarball from here https://build.opensuse.org/package/show/graphics/libgphoto2 or pull it via github and build that. that should give you all the improvements from the hackweek, where @msmeissn tested with my x-t2

live view still doesn't work in 2.5.23 on Debian buster, for the record. well, it kind of works once, then stops working...

msmeissn · 2020-08-09T07:02:02Z

The Fuji X-T1 is confirmed to work to my knowledge.

FernandaRamosTL · 2020-08-09T15:11:36Z

The Fuji X-T1 is confirmed to work to my knowledge.

Merci!

FernandaRamosTL · 2020-08-10T19:51:27Z

The Fuji X-T1 is confirmed to work to my knowledge.

Dear Marcus, good evening.
My Xt1 arrived, and I am not able to make it work. Do you think you could enlight me some how? I just want it to take a picture, download to the raspbian computer, and then erase it. The camera is recognized, but i cant get it to work. I already tried PTP and PC SHoot. Thank you so much, Fernanda.

msmeissn · 2020-08-11T08:03:27Z

Two things:

is the USB Mode of the camera set to USB Tethering (in the camera menu)?
what is the gphoto2 --version output ?

FernandaRamosTL · 2020-08-11T12:23:38Z

Dear Marcus, thank you again for your reply! I am using the PC MODE (auto or fixed, both works). Yesterday I spent all the day trying to manage it, and I finaly found a way to make it happen. Also, I used a script for updating the gphoto and libphoto written by guy named Gonzalo. I couldnt find my way to get to know the versions I was using, but I did the apt-get update. The way that I did works, but not without a huge U turn to adresss some issues. It is working, but this is not the best camera for the purporse I need. What I did was: 1 - trigger capture (image capture was freezing ) 2) copy photos from camera 3) erase all photos in the camera. And that only worked using 2 different scripts, because I could not make it happen in the same script at once.

msmeissn · 2020-08-11T16:06:33Z

you can find out the version in use as I wrote by running:

gphoto2 --version

FernandaRamosTL · 2020-08-11T16:18:45Z

Thank you! Here we go:
gphoto2 2.5.23

gphoto2 comes with NO WARRANTY, to the extent permitted by law. You may
redistribute copies of gphoto2 under the terms of the GNU General Public
License. For more information about these matters, see the files named COPYING.

This version of gphoto2 is using the following software versions and options:
gphoto2 2.5.23 gcc, popt(m), exif, no cdk, no aa, no jpeg, no readline
libgphoto2 2.5.22 all camlibs, gcc, ltdl, EXIF
libgphoto2_port 0.12.0 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, ltdl, USB, serial without locking

kermesse · 2020-09-05T17:41:12Z

Same problem on my side. X-T1 not working and hanging indefinitely with --capture-image, --capture-image-and-download, --capture-tethered. --capture-preview works. --capture-movie only downloads a preview, then stops.

Fuji X-T1 with firmware 5.51 (last stable).

System: *ubuntu 20.04.1 LTS

gphoto2 2.5.23

gphoto2 comes with NO WARRANTY, to the extent permitted by law. You may
redistribute copies of gphoto2 under the terms of the GNU General Public
License. For more information about these matters, see the files named COPYING.

This version of gphoto2 is using the following software versions and options:
gphoto2 2.5.23 gcc, popt(m), exif, cdk, aa, jpeg, readline
libgphoto2 2.5.25.1 standard camlibs (SKIPPING lumix), gcc, ltdl, EXIF
libgphoto2_port 0.12.0 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, ltdl, EXIF, USB, serial without locking

Available to post debug files and any thing that could be useful (or to modify the code if necessary).

kermesse · 2020-09-05T17:42:00Z

Dear Marcus, thank you again for your reply! I am using the PC MODE (auto or fixed, both works). Yesterday I spent all the day trying to manage it, and I finaly found a way to make it happen. Also, I used a script for updating the gphoto and libphoto written by guy named Gonzalo. I couldnt find my way to get to know the versions I was using, but I did the apt-get update. The way that I did works, but not without a huge U turn to adresss some issues. It is working, but this is not the best camera for the purporse I need. What I did was: 1 - trigger capture (image capture was freezing ) 2) copy photos from camera 3) erase all photos in the camera. And that only worked using 2 different scripts, because I could not make it happen in the same script at once.

Fernanda, could you share you scripts? I have not been able to capture any image even using scripts.

msmeissn · 2020-09-25T13:29:47Z

https://github.com/gonzalo/gphoto2-updater are the gphoto updater scripts

msmeissn · 2020-09-25T13:30:14Z

i did some small changes in current libgphoto2 GIT for FUji XT capture .. not sure if it will help

msmeissn · 2020-10-04T08:48:19Z

good to hear the olympus works :)

not sure if anything is left in here to do.

msmeissn · 2021-06-19T15:11:18Z

fuji xt capture has been improved, if there are new / unfixed issues, feel free to open a new issue

msmeissn closed this as completed in e7b37b1 Jan 23, 2017

msmeissn reopened this Jan 24, 2017

msmeissn added a commit that referenced this issue Jan 29, 2017

updated debuginfo from #133

3e5629b

msmeissn self-assigned this Feb 3, 2017

msmeissn added a commit that referenced this issue Feb 7, 2017

set two undocumented property values when starting up Fuji XT

c998fcd

#133

msmeissn added the Fuji tagging Fuji reports label Oct 20, 2019

FernandaRamosTL mentioned this issue Sep 5, 2020

just a mistake, please delete it #560

Closed

msmeissn closed this as completed Jun 19, 2021

Fuji X-T2, USB ID 04cb:02cd #133

Fuji X-T2, USB ID 04cb:02cd #133

Comments

jbreiden commented Jan 23, 2017 • edited

jbreiden commented Jan 23, 2017 • edited

msmeissn commented Jan 24, 2017

jbreiden commented Jan 24, 2017 • edited

jbreiden commented Jan 24, 2017

msmeissn commented Jan 24, 2017

jbreiden commented Jan 24, 2017 • edited

jbreiden commented Jan 24, 2017 • edited

jbreiden commented Jan 24, 2017

jbreiden commented Jan 24, 2017

msmeissn commented Jan 25, 2017

jbreiden commented Jan 26, 2017

msmeissn commented Jan 27, 2017

jbreiden commented Jan 27, 2017

jbreiden commented Jan 30, 2017 • edited

jbreiden commented Feb 2, 2017 • edited

jbreiden commented Feb 2, 2017 • edited

msmeissn commented Feb 3, 2017

jbreiden commented Feb 6, 2017 • edited

msmeissn commented Feb 7, 2017

msmeissn commented Feb 7, 2017

jbreiden commented Apr 19, 2017 • edited

jbreiden commented Apr 19, 2017 • edited

jbreiden commented Apr 24, 2017 • edited

msmeissn commented Apr 24, 2017

msmeissn commented Apr 24, 2017

msmeissn commented Nov 15, 2017

anarcat commented Jul 18, 2018 • edited

jbreiden commented Jul 18, 2018

msmeissn commented Jul 19, 2018

darix commented Jul 21, 2018

jbreiden commented Jul 21, 2018

anarcat commented Jul 22, 2018

darix commented Jul 22, 2018

darix commented Jul 22, 2018

anarcat commented Jul 22, 2018 via email

jbreiden commented Jul 23, 2018 • edited

ghost commented Aug 27, 2019

kritzikratzi commented Nov 20, 2019

anarcat commented Dec 19, 2019

msmeissn commented Aug 9, 2020

FernandaRamosTL commented Aug 9, 2020

FernandaRamosTL commented Aug 10, 2020

msmeissn commented Aug 11, 2020

FernandaRamosTL commented Aug 11, 2020 • edited

msmeissn commented Aug 11, 2020

FernandaRamosTL commented Aug 11, 2020

kermesse commented Sep 5, 2020

kermesse commented Sep 5, 2020

msmeissn commented Sep 25, 2020

msmeissn commented Sep 25, 2020

msmeissn commented Oct 4, 2020

msmeissn commented Jun 19, 2021

jbreiden commented Jan 23, 2017 •

edited

jbreiden commented Jan 23, 2017 •

edited

jbreiden commented Jan 24, 2017 •

edited

jbreiden commented Jan 24, 2017 •

edited

jbreiden commented Jan 24, 2017 •

edited

jbreiden commented Jan 30, 2017 •

edited

jbreiden commented Feb 2, 2017 •

edited

jbreiden commented Feb 2, 2017 •

edited

jbreiden commented Feb 6, 2017 •

edited

jbreiden commented Apr 19, 2017 •

edited

jbreiden commented Apr 19, 2017 •

edited

jbreiden commented Apr 24, 2017 •

edited

anarcat commented Jul 18, 2018 •

edited

jbreiden commented Jul 23, 2018 •

edited

FernandaRamosTL commented Aug 11, 2020 •

edited