DDserver on RaspberryPi can't get list of Camera connected

qDslrDashbord error reports
hubaiz
Site Admin
Posts: 1699
Joined: 27 Jan 2015, 18:58

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by hubaiz » 04 Sep 2017, 20:10

Check that the system does not mount automatically the camera SD card, that could prevent ddserver from connecting to the camera.

Jarrod
Posts: 15
Joined: 27 Aug 2017, 14:40

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by Jarrod » 05 Sep 2017, 03:22

Also what does syslog on the RPi say when you tell the client to connect to DDServer?

PiKmera
Posts: 8
Joined: 27 Aug 2017, 19:14

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by PiKmera » 05 Sep 2017, 10:52

I'll try your comments later today when will be at home. However something I forgot to add in my last comment, when I ran sudo ./ddserver there's not any output.. is that normal or I should receive some kind of message.. or at least return to the root@raspberrypi:/home/pi/package/DslrDashboardServer# line?

Jarrod
Posts: 15
Joined: 27 Aug 2017, 14:40

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by Jarrod » 06 Sep 2017, 16:36

Normal, ddserver writes its messages to /var/log/messages (that's the syslog output I was asking you for). If you want to run it in the background, append an '&' to the command:

./ddserver &

That will run the program in the background and then return the command prompt.

PiKmera
Posts: 8
Joined: 27 Aug 2017, 19:14

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by PiKmera » 07 Sep 2017, 19:01

still no luck.
I did notice that I had a custom firmware in my canon, so I tried once again with the original firmware from Canon with the hope that this was making the problems. However now the application looks for the server at a totally different IP. I can't see in the settings on the app anything about it, the IP for the Rpi is 192.168.0.20 (when I was trying with the custom firmware in the canon, the app was detecting the server in the correct IP)

Image

1. Turning on the Rpi
2. As Root, I'm running the command sudo ./ddserver
3. I'm pluggin the camera to the Rpi
4. I'm checking that the server is runing
5. I'm turning on the camera
6. I'm trying to connect to the server in the app in my phone (connected to the same network)

I even thought that the issue could be that I was using the Rpi with a Wifi dongle, so I tried with the Ethernet cable instead, with the same result. :cry: :cry:

This is the log file, I don't see anything relevant (Am I wrong?)
root@raspberrypi:/# nano /var/log/messages
GNU nano 2.7.4 File: /var/log/messages

Aug 16 01:40:43 raspberrypi mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.4"
Aug 16 01:40:43 raspberrypi mtp-probe: bus: 1, device: 4 was not an MTP device
Aug 16 01:40:43 raspberrypi mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.1"
Aug 16 01:40:43 raspberrypi mtp-probe: bus: 1, device: 3 was not an MTP device
Aug 16 01:40:43 raspberrypi liblogging-stdlog: [origin software="rsyslogd" swVersion="8.24.0" x-pid="250" x-info="http://www.rsyslog.com"] s$
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Linux version 4.9.41+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1$
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] OF: fdt:Machine model: Raspberry Pi Model B Plus Rev 1.2
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] cma: Reserved 8 MiB at 0x1b400000
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Memory policy: Data cache writeback
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 113680
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Kernel command line: bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 v$
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Memory: 435932K/458752K available (5949K kernel code, 489K rwdata, 1952K rodata, 400K init$
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] Virtual kernel memory layout:
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] vmalloc : 0xdc800000 - 0xff800000 ( 560 MB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] lowmem : 0xc0000000 - 0xdc000000 ( 448 MB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] .text : 0xc0008000 - 0xc05d78dc (5951 kB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] .init : 0xc0842000 - 0xc08a6000 ( 400 kB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] .data : 0xc08a6000 - 0xc0920788 ( 490 kB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] .bss : 0xc0920788 - 0xc09d7f88 ( 734 kB)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Aug 16 01:40:43 raspberrypi kernel: [ 0.000000] NR_IRQS:16 nr_irqs:16 16
Aug 16 01:40:43 raspberrypi kernel: [ 0.000030] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
Aug 16 01:40:43 raspberrypi kernel: [ 0.000061] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
Aug 16 01:40:43 raspberrypi kernel: [ 0.000151] bcm2835: system timer (irq = 27)
Aug 16 01:40:43 raspberrypi kernel: [ 0.000611] Console: colour dummy device 80x30
Aug 16 01:40:43 raspberrypi kernel: [ 0.000635] console [tty1] enabled
Aug 16 01:40:43 raspberrypi kernel: [ 0.000661] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
Aug 16 01:40:43 raspberrypi kernel: [ 0.060297] pid_max: default: 32768 minimum: 301
Aug 16 01:40:43 raspberrypi kernel: [ 0.060726] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Aug 16 01:40:43 raspberrypi kernel: [ 0.060742] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Aug 16 01:40:43 raspberrypi kernel: [ 0.061809] Disabling cpuset control group subsystem

Jarrod
Posts: 15
Joined: 27 Aug 2017, 14:40

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by Jarrod » 07 Sep 2017, 21:07

However now the application looks for the server at a totally different IP. I can't see in the settings on the app anything about it, the IP for the Rpi is 192.168.0.20
Long-press the connect to server icon. A window will pop up that lets you enter the IP address of your DDServer.

Yes, I bet the custom camera firmware was what was causing your issue before. I'm not sure why the autodetect of the IP was working before and isn't now. In my case IP broadcast/autodetect works when I have my Pi/DDServer and qDSLRDashboard devices both connected to my router, but does NOT work when I set up my Pi as a wireless AP and connect my qDSLRDashboard device to the Pi's AP. Not sure why, but in the end it doesn't really matter once you know how to set the IP it connects to.

PiKmera
Posts: 8
Joined: 27 Aug 2017, 19:14

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by PiKmera » 30 Sep 2017, 20:12

Hey Guys, finally could make it work! Thanks for the support.
Just in case I made a quick video about the app and also using it wth the Rpi :) may be useful for someone else.

https://www.youtube.com/watch?v=3ZhMnmugDWk

auge
Posts: 4
Joined: 22 Jul 2019, 12:44

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by auge » 25 Jul 2019, 10:55

I have the same problem.
ControlMyCamera reports:
Error getting DSLR list from IP 192.168.1.112
Magic Lantern was deactivated on 550D. (Firmware is 1.0.9)
Any ideas?
======================================

Configuration:
Canon EOS 550D on Raspberry Stretch.
dderserver was installed and started.
See message logs:

Code: Select all

Jul 25 12:44:43 raspberrypi1 kernel: [ 3379.339888] usb 1-1.2: new high-speed USB device number 16 using dwc_otg
Jul 25 12:44:43 raspberrypi1 kernel: [ 3379.471648] usb 1-1.2: New USB device found, idVendor=04a9, idProduct=31ea, bcdDevice= 0.02
Jul 25 12:44:43 raspberrypi1 kernel: [ 3379.471666] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 25 12:44:43 raspberrypi1 kernel: [ 3379.471676] usb 1-1.2: Product: Canon Digital Camera
Jul 25 12:44:43 raspberrypi1 kernel: [ 3379.471685] usb 1-1.2: Manufacturer: Canon Inc.
Jul 25 12:44:43 raspberrypi1 mtp-probe: checking bus 1, device 16: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"
Jul 25 12:44:44 raspberrypi1 mtp-probe: bus: 1, device: 16 was not an MTP device
Jul 25 12:44:44 raspberrypi1 gvfs-gphoto2-vo[851]: device (null) has no BUSNUM property, ignoring
Jul 25 12:44:57 raspberrypi1 ddserver: recv: 57
Jul 25 12:44:57 raspberrypi1 ddserver: Client multicast query DslrDashboardClient{49867b4e-5c20-4e8f-8baf-c3a4f7a2bea7}
Jul 25 12:44:57 raspberrypi1 ddserver: Server message length: 57   msg: DslrDashboardServer{49867b4e-5c20-4e8f-8baf-c3a4f7a2bea7}
Jul 25 12:44:57 raspberrypi1 ddserver: Incoming client connection
Jul 25 12:44:57 raspberrypi1 ddserver: Awaiting client connection
Jul 25 12:44:57 raspberrypi1 ddserver: USB Devices in
Jul 25 12:44:57 raspberrypi1 ddserver: Number of possible configurations: 1 Device Class: 0 VendorID: 1193, ProductID: 12778
Jul 25 12:44:57 raspberrypi1 ddserver: Number of alternate settings:
Jul 25 12:44:57 raspberrypi1 ddserver: Interface class: 6 Interface number: 0 Number of endpoints: 3
Jul 25 12:44:57 raspberrypi1 ddserver: Found USB imaging device, get vendor and product
Jul 25 12:44:57 raspberrypi1 ddserver: Number of possible configurations: 1 Device Class: 255 VendorID: 1060, ProductID: 60416
Jul 25 12:44:57 raspberrypi1 ddserver: Number of alternate settings:
Jul 25 12:44:57 raspberrypi1 ddserver: Interface class: 255 Interface number: 0 Number of endpoints: 3
Jul 25 12:44:57 raspberrypi1 ddserver: Number of possible configurations: 1 Device Class: 9 VendorID: 1060, ProductID: 38164
Jul 25 12:44:57 raspberrypi1 ddserver: Number of alternate settings:
Jul 25 12:44:57 raspberrypi1 ddserver: Interface class: 9 Interface number: 0 Number of endpoints: 1
Jul 25 12:44:57 raspberrypi1 ddserver: Interface class: 9 Interface number: 0 Number of endpoints: 1
Jul 25 12:44:57 raspberrypi1 ddserver: Number of possible configurations: 1 Device Class: 9 VendorID: 7531, ProductID: 2
Jul 25 12:44:57 raspberrypi1 ddserver: Number of alternate settings:
Jul 25 12:44:57 raspberrypi1 ddserver: Interface class: 9 Interface number: 0 Number of endpoints: 1
Jul 25 12:44:57 raspberrypi1 ddserver: Imaging USB devices found: 0
Jul 25 12:44:59 raspberrypi1 ddserver: Closing USB device

hubaiz
Site Admin
Posts: 1699
Joined: 27 Jan 2015, 18:58

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by hubaiz » 25 Jul 2019, 11:39

Probably the system is auto mounting the camera SD card and ddserver can't access the camera.
Check this post: https://www.raspberrypi.org/forums/view ... hp?t=91677

auge
Posts: 4
Joined: 22 Jul 2019, 12:44

Re: DDserver on RaspberryPi can't get list of Camera connected

Post by auge » 25 Jul 2019, 12:58

Thought canceling the window of automount is sufficient, but it was not.

Solution:
Changing file:
/home/pi/.config/pcmanfm/LXDE-pi/pcmanfm.conf

mount_on_startup=0
mount_removable=0

Thank hubaiz you for the quick response!!
Now it works!!!

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests