ddserver V0.2-13 OpenWrt images for the TP-Link MR3040

As I mentioned in my previous post I discovered a bug in the ddserver code that would result in a broken USB and wireless connection.

With the V0.2-13 version I fixed that error.

I provided the firmware images (factory, sysupgrade) in the downloads section as a new method for updating the ddserver package.

I suggest that everyone who already has the latest MR3040 ddserver OpenWrt firmware to use the new package updater as it is faster and less error prone.

36 thoughts on “ddserver V0.2-13 OpenWrt images for the TP-Link MR3040”

  1. Hello, I could use a little help.
    I am just getting started with flashing the firmware on my 3040 router. As you instructed I flashed it first with the –
    VO.2-12 V2factory image.
    But where do I go next? What order do I install the firmware to end up with the latest update? Do install in the order below.
    Or can I jump right to the V2 sysupgrade image VO.2-13 version
    V2 sysupgrade image VO.2-12
    V2 factory image VO.2-13
    V2 sysupgrade image VO.2-13
    I’m doing this on a Mac. Thanks for your help!

    1. How did you get OpenWRT to work using Mac? It’s not working for me with OS X 10.10.1 Yosemite. I don’t see clear steps anywhere for a Mac.

      1. It is a same procedure as on other platform.
        Pair you platform wireless with the MR3040 wireless.
        Start qDD and press the ‘Network’ button or long press the ‘Network’ button and enter the IP of MR3040.
        If your Max is connected to your local network (wired connection) there is a chance that your router has also the 192.168.1.1 IP address in this case it will not work.

  2. Yes, I already have OpenWrt ” V2factory image”
    version VO.2-12 on the router. My router is a “V2”

  3. The problem with loosing WiFi and USB connection is still present.
    I found that if router is charging the problem disappears but if fully charged (even when pluged in) back again.
    It happens a lot more often with D610 than D7000.

    1. The V0.2-13 fixed a bug that occur when ddserver would get a specific packet from the connected camera. Not sure what problem you are referring. What is the distance between your device and the router? Does your device lose the wireless connection with the router? ddserver works the same way while the router is on charger or on battery. If the network connection is lost between qDD and ddserver for a specific time then ddserver will close the connection as the connection to the conneted camera.

      1. The distance between phone/PC and router has no influence.
        No matter if I put phone directly on MR3040 or 5 or 10m away.

        No. There are no problems with WiFi connection to router. Only DSLRDashboard disconnects with camera.

        Sometimes router loses USB connection with camera (rather rare) – USB LED on router truns off and USB cabel must be unplugged and plugged again. This problem also never happened on dds older than v0.12.

        First I thought it was problem with router itself but after switching to older version of DDserver and older version of DSLRDashboard problems stopped.

    2. Can you tell me how you make D7000 work with TP Link? I have brand new TP LINK router now.. can you outline list of packages I should In stall on this to make D7000 work with.

      Thank you

  4. Hi, I have a Canon EOS 30D and a Samsung S3 device and I can confirm that some kind of disconnection problems occurs with USB (rarerly) and always with TP-LINK MR3040. I have installed the factory firmware (v0.2-13) on a new TP-LINK device then, after a connection in qDslrDashboard (clickin in the LAN icon, not the WiFi icon) and after few shots using the LRTimelapse feature, something qDslrDashboard crash or sometimes exits the LRtimelapse windows and I have to reconnect (by plugging/unpluggin the usb cable or restarting qDslrDashboard).

    I attach some logs of the OpenWrt: they show that the usb connection is detecte but some minutes later a disconnection occurs:

    Jul 21 12:30:44 OpenWrt user.info syslog: Number of possible configurations: 1 Device Class: 0 VendorID: 1193, ProductID: 12563
    Jul 21 12:30:44 OpenWrt user.info syslog: Number of alternate settings:
    Jul 21 12:30:44 OpenWrt user.info syslog: Interface class: 6 Interface number: 0 Number of endpoints: 3
    Jul 21 12:30:44 OpenWrt user.info syslog: Found USB imaging device, get vendor and product
    Jul 21 12:30:44 OpenWrt user.info syslog: Device Manufacturer: Canon Inc.
    Jul 21 12:30:44 OpenWrt user.info syslog: Device Product: Canon Digital Camera
    Jul 21 12:30:44 OpenWrt user.info syslog: Imaging USB devices found: 1
    Jul 21 12:30:44 OpenWrt user.info syslog: Incoming client connection
    Jul 21 12:30:44 OpenWrt user.info syslog: Awaiting client connection
    Jul 21 12:30:44 OpenWrt user.info syslog: USB Devices in
    Jul 21 12:30:44 OpenWrt user.info syslog: Checking device with vendorId: 04a9 and productId: 3113
    Jul 21 12:30:44 OpenWrt user.info syslog: Checking device with vendorId: 04a9 and productId: 3113
    Jul 21 12:30:44 OpenWrt user.info syslog: Trying to open device
    Jul 21 12:30:44 OpenWrt user.info syslog: Number of possible configurations: 1 Device Class: 0 VendorID: 1193, ProductID: 12563
    Jul 21 12:30:44 OpenWrt user.info syslog: Number of alternate settings:
    Jul 21 12:30:44 OpenWrt user.info syslog: Interface class: 6 Interface number: 0 Number of endpoints: 3
    Jul 21 12:30:44 OpenWrt user.info syslog: Found USB imaging device, get vendor and product
    Jul 21 12:30:44 OpenWrt user.info syslog: Device open success
    Jul 21 12:30:44 OpenWrt user.info syslog: USB device opened
    Jul 21 12:30:44 OpenWrt user.info syslog: Read endpoint adress: 129
    Jul 21 12:30:44 OpenWrt user.info syslog: Write endpoint adress: 2
    Jul 21 12:30:44 OpenWrt user.info syslog: USB interface claimed
    Jul 21 12:30:44 OpenWrt user.info syslog: vendor: 1193 product: 12563
    Jul 21 12:30:44 OpenWrt user.info syslog: vendor: 43268 product: 4913
    Jul 21 12:30:44 OpenWrt user.err syslog: Error reading total packet size: 0
    Jul 21 12:30:44 OpenWrt user.err syslog: Stoping client
    Jul 21 12:30:46 OpenWrt user.info syslog: Closing USB device
    Jul 21 12:34:13 OpenWrt daemon.info hostapd: wlan0: STA 5c:0a:5b:a2:0f:87 WPA: group key handshake completed (RSN)
    Jul 21 12:35:02 OpenWrt kern.info kernel: [ 670.770000] usb 1-1: USB disconnect, device number 8
    Jul 21 12:35:02 OpenWrt user.err syslog: Error command packet USB bulk write: -4
    Jul 21 12:35:02 OpenWrt user.err syslog: Stoping client
    Jul 21 12:35:03 OpenWrt kern.info kernel: [ 671.050000] usb 1-1: new high-speed USB device number 9 using ehci-platform
    Jul 21 12:35:04 OpenWrt kern.info kernel: [ 671.960000] usb 1-1: USB disconnect, device number 9
    Jul 21 12:35:04 OpenWrt kern.info kernel: [ 672.240000] usb 1-1: new high-speed USB device number 10 using ehci-platform
    Jul 21 12:35:04 OpenWrt kern.info kernel: [ 672.730000] usb 1-1: USB disconnect, device number 10
    Jul 21 12:35:04 OpenWrt user.info syslog: Closing USB device
    Jul 21 12:35:04 OpenWrt user.err syslog: Unable to release USB interface
    Jul 21 12:35:05 OpenWrt kern.info kernel: [ 673.020000] usb 1-1: new high-speed USB device number 11 using ehci-platform
    Jul 21 12:35:09 OpenWrt kern.info kernel: [ 677.270000] usb 1-1: USB disconnect, device number 11
    Jul 21 12:35:09 OpenWrt kern.info kernel: [ 677.550000] usb 1-1: new high-speed USB device number 12 using ehci-platform

    1. This is normal regarding the MR3040. It is only a proxy, the error source is qDD. What was the interval you using? Was there enough timer for qDD to downlaod the JPG? What intervalometer are your using, is it keeping the camera in ‘half press’ after the camera finished the capture?

      Please use the forum.

      1. Hi Zoltan,

        I’m using Aputure AP-TR3C intervallometer. I set just the interval time between 2 shots. At the beginning I though as you suggest that there was not enough time for qDD to download the jpg from the camera, so I increased the time interval: it was ok for a while then the problem occured againg.

        These evening I’ll try again with a sunset timelapse and trying to start with a longer interval time to be sure that it is not the problem. I’ll try also at different distances.

        It don’t seem to me that the intervallometer leave the camera in “half press”: I think that if happaned the USB communication between the camera and the MR3040 could be busy and qDD couldn’t be able to communicate with the ddserver, right?

        I’ll let you know, I really like this project!

        Regards,
        Matteo

  5. Hi
    is it possible to have D800 nikon connected to tplink 3040 v2(have one) if possible please let me know the steps i am new to this. Thank you

  6. Suceccfuly installed ddserver on tplink 703n Attidude 12.09 and workig with Nikon d7000 over wifi to galaxy s3 and on windows 8 machine over ethernet.. Excellent app.. looking forward to see ios app as i own ipad….. i’m graphic designer so if you need help i will be glad to help you developing future android and ios version of dslr dashboard

  7. Hi. Can you tell me – I have tp-link MR3040 with V2.1 firmware. Can I flash it the same ddserver V0.2-13 OpenWrt images for the TP-Link MR3040 – for V2 firmware?

  8. Dear Zoltan,

    thanks a lot for – in advance – for what you did so far 🙂

    I do have the brand.new D810 Nikon (same time as Mr. W 🙂

    issue:
    wireless works…DSLR app works…

    however:
    connection ‘tp.router’ with USB 2 USB 3 cabel @ Nikon D810 vs. ‘Galaxy Note 3’…the camera can be found (name in green)…click on camera name …opens the app…

    great…and than: game over /tilt / … 🙂

    I guess: when it comes to the point the ‘app’ tries to open the ‘lievView’ of the camera…the app stops is closing…

    even if I open the ‘liveView’ before.hand @ Nikon D810…as soon as I start the ‘app’: I can hear that there is a command coming from the app to the camera and telling the camera what needs to be done…however…the camera (mirrors/AF) tries ‘at its best’ – however again: I cannot get the ‘liveView’ on my ‘Galaxy screen’ and the app stops/is closing.

    best regards…

    Christof

  9. Hi Zoltan;

    please delete my comment/post from before.

    I am in contact with Gunther…he told me that you both…are working on the D810 issue…

    thanks a lot and best regards,

    christof

  10. Yes, I do have problem also with my D810. The application will definitely crash once I switch to live view. I believe all the situs will closely monitoring this and provide best solution once for all. Thanks!

    1. Dear all,

      How’s about this Topic (TP link Nikon D810) – any updates available e.g. Nikon offers support for the D810 interface to TP link

      If there is a solution – please let me know 🙂

      Txx a lot and best regards,

      chris*

  11. I was trying to update the firmware on the Tp link device which already had the version V0.2-12.
    I was trying to update it to the V0.2-13, i downloaded the
    V2 sysupgrade image and tryied to flash the device with this new firmware but i guess the device fails to update.

    Am attaching a screen shot of the overview status of my device present details.

    Thanks

  12. Hi,

    I have been using the TP-Link MR3040 before but bought a new camera. The pentax k-3, and when I connect the camera shuts down… Any ideas or solutions on this for the time being?

  13. MR3040 V1 and D90 with ASUS tablet, its working with a couple of hours of hard work, did not realize that the router needs to be connected with the LAN cable to the computer and the internet LAN cable pulled (not the USB connection), then the 192.168.1.1 talks directly to the router (and the openWRT download has to be done first while online), then its a direct firmware upgrade with the router in charge, then it opened and worked until first photo taken then no contact, in DSLR dash settings changed IP address to the above 192.. and voila, up and running, very exciting

  14. by “not the USB connection” I mean do not connect the router with the USB cable, also I was searching for 192.168.. with the internet connected and it was looking for the router on the web and failing,
    also found that when tethered by cable an OTG USB cable is essential, wasted months with a standard USB cable before a Wiki search, was using a mini to micro cable thinking I was smart,
    with Wifi tethering the OTG thing may not be required, I tried two mini to standard USB male connectors and both worked between camera and router.

Leave a Reply

Your email address will not be published. Required fields are marked *