USB Log Interpretation

qDslrDashbord error reports
Post Reply
_r2h
Posts: 2
Joined: 16 Sep 2018, 21:45

USB Log Interpretation

Post by _r2h »

Hello all,

Can I get some help interpreting this log?

Hardware: GL-AR300m with DDServer 0.2-14, Canon 5D Mark III, Pixel 4a with qDslrDashboard 3.6.4

I can get qDslrDashboard to give a message that it had found 1 camera and attempts to connect to it, but it hangs and eventually closes out to the app drawer.

This is the system log from the AR300m

Code: Select all

Sat Jan 29 20:48:06 2022 kern.info kernel: [  274.795699] epc = 00401869 in ddserver[400000+4000]
Sat Jan 29 20:48:06 2022 kern.info kernel: [  274.800794] ra  = 00401869 in ddserver[400000+4000]
Sat Jan 29 20:51:03 2022 user.info : DslrDashboardServer starting
Sat Jan 29 20:51:03 2022 user.info : Starting socket server on port 4757
Sat Jan 29 20:51:03 2022 user.info : Awaiting client connection
Sat Jan 29 20:51:03 2022 user.info : Starting UDP listener
Sat Jan 29 20:51:03 2022 user.info : join multicast group: 224.1.2.3
Sat Jan 29 20:51:03 2022 user.err : error in joining multicast group -1
Sat Jan 29 20:51:15 2022 user.info : Incoming client connection
Sat Jan 29 20:51:15 2022 user.info : Awaiting client connection
Sat Jan 29 20:51:15 2022 user.info : USB Devices in
Sat Jan 29 20:51:15 2022 user.info : Number of possible configurations: 1 Device Class: 0 VendorID: 1193, ProductID: 12858
Sat Jan 29 20:51:15 2022 user.info : Number of alternate settings:
Sat Jan 29 20:51:15 2022 user.info : Interface class: 6 Interface number: 0 Number of endpoints: 3
Sat Jan 29 20:51:15 2022 user.info : Found USB imaging device, get vendor and product
Sat Jan 29 20:51:15 2022 user.info : Device Manufacturer: Canon Inc.
Sat Jan 29 20:51:15 2022 user.info : Device Product: Canon Digital Camera
Sat Jan 29 20:51:15 2022 user.info : Number of possible configurations: 1 Device Class: 9 VendorID: 7531, ProductID: 2
Sat Jan 29 20:51:15 2022 user.info : Number of alternate settings:
Sat Jan 29 20:51:15 2022 user.info : Interface class: 9 Interface number: 0 Number of endpoints: 1
Sat Jan 29 20:51:15 2022 user.info : Imaging USB devices found: 1
Sat Jan 29 20:51:16 2022 user.err : Error reading total packet size: 0
Sat Jan 29 20:51:16 2022 user.err : Stoping client
Sat Jan 29 20:51:16 2022 user.info : Incoming client connection
Sat Jan 29 20:51:16 2022 user.info : Awaiting client connection
Sat Jan 29 20:51:16 2022 user.info : USB Devices in
Sat Jan 29 20:51:16 2022 user.info : Checking device with vendorId: 04a9  and productId: 323a
Sat Jan 29 20:51:16 2022 user.info : Trying to open device
Sat Jan 29 20:51:16 2022 user.info : Number of possible configurations: 1 Device Class: 0 VendorID: 1193, ProductID: 12858
Sat Jan 29 20:51:16 2022 user.info : Number of alternate settings:
Sat Jan 29 20:51:16 2022 user.info : Interface class: 6 Interface number: 0 Number of endpoints: 3
Sat Jan 29 20:51:16 2022 user.info : Found USB imaging device, get vendor and product
Sat Jan 29 20:51:16 2022 user.info : Device  open success
Sat Jan 29 20:51:16 2022 user.info : USB device opened
Sat Jan 29 20:51:16 2022 user.info : Read endpoint adress: 129 max pSize 512
Sat Jan 29 20:51:16 2022 user.info : Write endpoint adress: 2 max pSize 512
Sat Jan 29 20:51:16 2022 user.info : Interrupt endpoint address: 131 max pSize 8
Sat Jan 29 20:51:16 2022 user.info : USB interface claimed
Sat Jan 29 20:51:16 2022 user.info : vendor: 1193 product: 12858
Sat Jan 29 20:51:16 2022 user.info : vendor: 43268 product: 14898
Sat Jan 29 20:51:18 2022 user.info : Closing USB device
I think my problem is the "Stopping client" and "Closing USB Device" messages, but I'm not sure what they are indicating.

Appreciate the help.
hubaiz
Site Admin
Posts: 2001
Joined: 27 Jan 2015, 18:58

Re: USB Log Interpretation

Post by hubaiz »

From the log can't tell it.
What power supply do you use? Try a 2A power supply if you used a weaker one.
_r2h
Posts: 2
Joined: 16 Sep 2018, 21:45

Re: USB Log Interpretation

Post by _r2h »

Just tried again with a 2A power supply and same result.

I did notice this little bit below the "Closing USB device" this time around.

Code: Select all

Sat Jan 29 20:50:40 2022 kern.info kernel: [  165.505900] do_page_fault(): sending SIGSEGV to ddserver for invalid write access to 00000000
Sat Jan 29 20:50:40 2022 kern.info kernel: [  165.514750] epc = 00401869 in ddserver[400000+4000]
Sat Jan 29 20:50:40 2022 kern.info kernel: [  165.519864] ra  = 00401869 in ddserver[400000+4000]
Edit:

Very similar to this post.

Crazy thing I had this working around October 2018 with zero issues and working great. A couple weeks ago, I pulled the router out of a drawer wanting to play with this again, so I updated all the software and reinstalled the app to my phone and only now am having a problem.
Last edited by _r2h on 04 Feb 2022, 21:45, edited 1 time in total.
hubaiz
Site Admin
Posts: 2001
Joined: 27 Jan 2015, 18:58

Re: USB Log Interpretation

Post by hubaiz »

I don't have that router so don't know what could be the problem.
Tested with the TP-Link WR703N and that worked with a Nikon D500.
I made some small changes to ddserver last year so if you can and build and install the latest one ( https://github.com/hubaiz/DslrDashboardServer )
Post Reply