Dear Community, dear Zoltan,
qdslrdashboard V 0.3.4.1 on IOS 10.11.3 on my MacBookPro connects via USB successfully
but not via DDserverAP TP-Link.
I installed the app several times but the result always is the same:
when connecting the CANON 5Ds via USB-cable the app works fine.
When I link the camera via TP-Link and DDserverAP (the connection is confirmed) the app does not connect to the camera.
By the way: when I do the same on my iPad / iPhone the wifi-connection via TP-Link and DDserverAP works without hustle.
Any idea what may be the reason ?
Thanks a lot.
MiGuCa
qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
I went here:
Is this mandatory and essential for the functionality of DDserverAP in this case ?
Regarding TP-Link can you access the OpenWrt web interface at http://192.168.1.1 from a web browser?
A dialogue opens and asks me to set a password.
Is this mandatory and essential for the functionality of DDserverAP in this case ?
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
No it is not.
Is your MacBook also connected with wired network connection?
Is your MacBook also connected with wired network connection?
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
No, if you mean "LAN-cable".
As soon as I try to link it with the camera it is only connected wireless to the TP-Link / DDServerAP.
And with nothing else.
As soon as I try to link it with the camera it is only connected wireless to the TP-Link / DDServerAP.
And with nothing else.
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
After connecting the wireless with the MR3040 wireless open a web browser and navigate to http://192.168.1.1
It should open the OpenWrt administration page. Did it open?
Connect your DSLR with USB cable to the MR3040 full size USB port and turn it on.
In the administration page navigate to 'Status->System log' and scroll to the end.
You should have something like this:
It should open the OpenWrt administration page. Did it open?
Connect your DSLR with USB cable to the MR3040 full size USB port and turn it on.
In the administration page navigate to 'Status->System log' and scroll to the end.
You should have something like this:
Code: Select all
Feb 21 19:55:28 Arduino kern.info kernel: [289844.670000] usb 1-1.1.3: new high-speed USB device number 12 using ehci-platform
Feb 21 19:55:28 Arduino kern.info kernel: [289844.880000] usb 1-1.1.3: New USB device found, idVendor=04a9, idProduct=3253
Feb 21 19:55:28 Arduino kern.info kernel: [289844.880000] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 21 19:55:28 Arduino kern.info kernel: [289844.880000] usb 1-1.1.3: Product: Canon Digital Camera
Feb 21 19:55:28 Arduino kern.info kernel: [289844.890000] usb 1-1.1.3: Manufacturer: Canon Inc.
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
There is nothing about CANON.
The last +- 20 rows show this: (let me know if you require the whole report)
--------------------
Sep 8 15:44:22 OpenWrt user.info syslog: DslrDashboardServer starting
Sep 8 15:44:22 OpenWrt user.info syslog: Starting socket server on port 4757
Sep 8 15:44:22 OpenWrt user.info syslog: Awaiting client connection
Sep 8 15:44:22 OpenWrt user.info syslog: Starting UDP listener
Sep 8 15:44:22 OpenWrt user.info syslog: join multicast group: 224.1.2.3
Sep 8 15:44:35 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 15:44:35 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 15:44:35 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPREQUEST(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa
Sep 8 15:44:35 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPACK(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa MYNAME
Sep 8 15:47:20 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: disassociated
Sep 8 15:47:21 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sep 8 15:56:30 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 15:56:30 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 15:56:30 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPREQUEST(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa
Sep 8 15:56:30 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPACK(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa MYNAME
Sep 8 16:00:01 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: disassociated
Sep 8 16:00:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 16:04:02 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPREQUEST(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa
Sep 8 16:04:02 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPACK(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa MYNAME
Sep 8 16:10:48 OpenWrt kern.info kernel: [ 1616.050000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Sep 8 16:17:18 OpenWrt kern.info kernel: [ 2006.410000] usb 1-1: USB disconnect, device number 2
Sep 8 16:38:53 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:38:53 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 16:40:10 OpenWrt kern.info kernel: [ 3377.990000] usb 1-1: new high-speed USB device number 3 using ehci-platform
------------
The last +- 20 rows show this: (let me know if you require the whole report)
--------------------
Sep 8 15:44:22 OpenWrt user.info syslog: DslrDashboardServer starting
Sep 8 15:44:22 OpenWrt user.info syslog: Starting socket server on port 4757
Sep 8 15:44:22 OpenWrt user.info syslog: Awaiting client connection
Sep 8 15:44:22 OpenWrt user.info syslog: Starting UDP listener
Sep 8 15:44:22 OpenWrt user.info syslog: join multicast group: 224.1.2.3
Sep 8 15:44:35 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 15:44:35 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 15:44:35 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPREQUEST(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa
Sep 8 15:44:35 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPACK(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa MYNAME
Sep 8 15:47:20 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: disassociated
Sep 8 15:47:21 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sep 8 15:56:30 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 15:56:30 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 15:56:30 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPREQUEST(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa
Sep 8 15:56:30 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPACK(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa MYNAME
Sep 8 16:00:01 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: disassociated
Sep 8 16:00:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:04:02 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 16:04:02 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPREQUEST(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa
Sep 8 16:04:02 OpenWrt daemon.info dnsmasq-dhcp[922]: DHCPACK(br-lan) 192.168.1.158 e4:ce:8f:16:3d:fa MYNAME
Sep 8 16:10:48 OpenWrt kern.info kernel: [ 1616.050000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Sep 8 16:17:18 OpenWrt kern.info kernel: [ 2006.410000] usb 1-1: USB disconnect, device number 2
Sep 8 16:38:53 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: authenticated
Sep 8 16:38:53 OpenWrt daemon.info hostapd: wlan0: STA e4:ce:8f:16:3d:fa IEEE 802.11: associated (aid 1)
Sep 8 16:40:10 OpenWrt kern.info kernel: [ 3377.990000] usb 1-1: new high-speed USB device number 3 using ehci-platform
------------
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
- Does it make any sense to contact the distributor of the TP-LINK MR3040 who made the firmware-Modifikation for qDslrDashboard ?
- Does it make sense to update the firmware ?
- Does it make sense to install the firmware newly ?
- How to check which firmware-version is implemeted currently ?
KR
MiGuCa
- Does it make sense to update the firmware ?
- Does it make sense to install the firmware newly ?
- How to check which firmware-version is implemeted currently ?
KR
MiGuCa
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
Does changing of the ip of the TP-LINK help ?
I found this in the forum :
http://dslrdashboard.info/phpBB3/viewto ... ?f=4&t=157
I found this in the forum :
http://dslrdashboard.info/phpBB3/viewto ... ?f=4&t=157
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
Hi @ all,
I also had problems, to get my EOS 700D connected via TP-Link to QDSLR-Dashboard.
Here is, what I found.
It seems to be relevant to start the equipment in the right order.
What I do:
1. start the TP-Link, wait until 2 LED are on (about 35 sec.).
2. connect your tablett via WLAN - 2nd LED now is blinking)
3. start the app (about 15 sec.)
4. power up your cam
5. wait until 3 LEDs are on - this may take a while.
6. push the "net-connect buttom of the app.
Now you should be connected and be able to use QDSLR-Dashboard via TP-Link.
If the 3. LED does't light up during 2 minutes, shut down the cam, wait a moment and power up again.
Sometimes, it might be necessary to restart the whole system / process
This is not, what I would call a performat system, but unfortunately, I don't know a better one
Norbert
I also had problems, to get my EOS 700D connected via TP-Link to QDSLR-Dashboard.
Here is, what I found.
It seems to be relevant to start the equipment in the right order.
What I do:
1. start the TP-Link, wait until 2 LED are on (about 35 sec.).
2. connect your tablett via WLAN - 2nd LED now is blinking)
3. start the app (about 15 sec.)
4. power up your cam
5. wait until 3 LEDs are on - this may take a while.
6. push the "net-connect buttom of the app.
Now you should be connected and be able to use QDSLR-Dashboard via TP-Link.
If the 3. LED does't light up during 2 minutes, shut down the cam, wait a moment and power up again.
Sometimes, it might be necessary to restart the whole system / process
This is not, what I would call a performat system, but unfortunately, I don't know a better one
Norbert
Re: qdslrdashboard V 0.3.4.1 on IOS 10.11.3 connects via USB but not via DDserverAP TP-Link
If your PC/MAC is only connected with the wireless network then changing the IP will not help.
Your camera is not recognised by the MR3040.
Do you use the USB cable that you get with your camera?
Do you connect the camera to the full size USB port of the MR3040?
Only use an USB cable (if you can try another), not need for an USB OTG adapter.
Did you flashed the firmware from here: http://dslrdashboard.info/downloads/
You can try and do a sysupgrade as described here: http://dslrdashboard.info/tp-link-mr304 ... e-upgrade/
Your camera is not recognised by the MR3040.
Do you use the USB cable that you get with your camera?
Do you connect the camera to the full size USB port of the MR3040?
Only use an USB cable (if you can try another), not need for an USB OTG adapter.
Did you flashed the firmware from here: http://dslrdashboard.info/downloads/
You can try and do a sysupgrade as described here: http://dslrdashboard.info/tp-link-mr304 ... e-upgrade/