yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] JohnF1:
Hi, I have been looking at DSLR Controller and trying to get it to work. Initially I tried it with an HTC Desire but that failed, due to the HTC design as I understand it. After a bit of research I got a Samsung Galaxy S4 Mini, partly becasdue the Devices list on the DSLRC Web site said that the Gaalxy S4 did work, and I assumned an S4 Mini would also work. So....

- Tried DSLRC with an OTG cable and the Samsung Galaxy S4 Mini. Did not work.

- Read something that said a 'feature in Android 4.2.n was the casue of DSLRC not working, and the the update to 4.3 would cure the problem.

- Then read on this forum, but still NOT on the Web site, that DSLRC will not work with Samsung Mini series.

- Bit disappointed as that was partly why I got the S4 Mini. Had I known this I might have got the large S4.

- Have now seen the thing about using the TP-LINK wireless router, which looks interesting. It would cost a bit more than a cable, but would have the advantage of being wireless.

So, my enquiry:

1. Will DSLRC ever work with the Samsung Galaxy S4 Mini? What would that require? (Android update, alternative firmware, or will it never work due to S4 Mini hardware)

2. Will DSLRC work on the S4 Mini definitely (or to a high degree of probability anyway) with the TP-Link router?

Looks like a great product, just a bit hardware-conscious.

Thanks, John
[Paid Software Announcement and Discussion] gadgetfl:
deleted
[Paid Software Announcement and Discussion] RTF_copters:
HTC One - TPlink - 5D

App works perfectly through USB, but still can get to work with WIFI, at the moment I'm out of option it look like TPlink will just collect dust :)
[Paid Software Announcement and Discussion] tsbrewers:
just one simple question (I hope) Does the wireless version still require the phone/tablet to have usb host support? I bought the little router and flashed with the hope of using it with my Evo3d which doesn't have usb host support, but it doesn't work.
[Paid Software Announcement and Discussion] Chainfire:
I finally have an HTC set up here, and I can replicate the problem. So I'm out looking for a fix. Check next update (should be soon)

Yes, it should.

Exposure compensation doesn't logically exist in M mode. Not on the camera, not in the app. I've replicated the HDR/AEB issue and I'm looking for fix (check next update).

Please see my response directly above this quote. The HDR/AEB issue is under investigation.

Yes. it is annoying that USB host is not properly supported across all devices.

The Mini does not support it, just like the Desire didn't. It will not support it in the future either. It will probably work with the TP-Link router but the Mini is not very fast.

If you're looking for phone-sized hardware, I'd recommend the Nexus 5, it should only be a little bit more expensive than the S4 Mini, far below S4 price (and better as well).
[Paid Software Announcement and Discussion] JohnF1:
I'll try the router

Ok, thanks. I guess the multiplicity of phones out there makes catering for all of them hard, and if they don't support a feature there's not a lot to be done about it.

I don't want to buy another phone, makes the whole thing a lot more expensive and I only recently got the S4 Mini on a 2 year contract so I can't do any upgrade deals. In any case the S4 (not mini) is too big for other uses, i.e. as a phone.

I'll probably give the router a try.
[Paid Software Announcement and Discussion] maximus96:
Will it be possible for the app to display the battery level of the TP-Link router?
[Paid Software Announcement and Discussion] madadd:
Note 3 and EOS 70d Wireless issue

Hi

DSLR connects correct when using the note3 and 70d via a wireless network, router AP and home network, however the software cannot find the 70d when using the hotspot option on the note3.

The 70d connects to the phone no problem, however thats it. i thought it maybe a access problem on the phone, so i tested this using the BubbleUPNP DNLA server. and connected to the note3 hotspot using my laptop and the phone shares its local stored data without issue.

The connection using the camera as wireless AP and the phone connects fine. however this then dosent give me internet access via my note3 as I have to disable network switching, otherwise the note3 drops the wireless 70d connection due to the connection quality test built into android.

Any ideas or settings that i should be looking at on the note3 to allow access over the hotspot setup ? or is it an issue with the 4.3 android and your software?

Regards

Adam
[Paid Software Announcement and Discussion] tsbrewers:
Just an update, I installed a new kernel on my Evo3d (MiRaGe) and finally got it to work with the wireless router. I tried the OTG cable, but that did not work. I am assuming I would need a powered, splitter cable to get that to work from my phone. I might order one and give it a try.
[Paid Software Announcement and Discussion] fotorex:
HDR/AEB issue with TP-Link wireless

Hello,

my name is Frank, I am from Germany and this is my first post here on the board.

I´m using a Galaxy S3 mini with Android 4.1.2 and knowing about the fact that the S3 mini does not support the USB OTG cables I was very pleased when I learned that there is a Wifi solution with the TP-Link available. So I tbought a TP-Link and tried to work with it. Unfortunately I was running in the exact same problems with HDR/AEB issue as mentioned above. So I'm looking forward for any updates to DSLR Controller.

[mod-edit]

Additional I was asking me the same question if even for the wifi Solution with the TP-Link it is necessary to have a smartphone/tablet which has the USB OTG comptibility.

But as I experienced a working setup together with DSLR Dashboard and TP-Link, I think that it is not the case that for the TP-Link wireless communication a smartphone with OTG compatibility is necessary.

regards,

Frank
[Paid Software Announcement and Discussion] gadgetfl:
You need to set the camera wifi up in smartphone mode and then connect the phone to the AP ssid set by the camera which will be the name that you assign to the camera. Once you do that DSLRC will be able to connect. I would think you would not be able to have internet in this situation because you're connected to an ad hoc wifi network. If I am reading your post correctly this is how it seems that you tested it with.

If I understand you correctly, you are trying to set the phone up as a hotspot and then having the camera connects to the phone while also trying to access the internet from I'm assuming another device via the hot spot? I believe the reason why the camera cannot connect to the phone via the phones hotspot is because the note 3's hotspot does not support adhoc networks. I do not believe you will ever be able to have an internet connection while also connected as a adhoc connection on Android phone. If I remember my networking correctly and it's been quite a while, this is called a Multi-homed network. Which involves additional protocols or at least advanced network support. I may not have this completely right I'm pretty sure I'm near the mark.

As to the quility test, I believe this is a 4.3 issue, not a DSLRC issue.

I have been using this on my 6D for quite a while, but my new 70D will be here tomorrow. I will be testing it over the next few days. I will let you know.
[Paid Software Announcement and Discussion] tripp9r:
Hey there,

i installed the DSLR-Controller a few month ago on my S2 and it was all fine with my otg-cable... just plug and play :)

Now i had to reset my phone and updated android to 4.1.2 and the DSLR Controller wont find my camera (600D)... i dont even get that popup.

Same problems on my Tablet (Samsung Galaxy Tab 3 8.0 - Android 4.2.2) that i just bought a few days ago... no popup.

Now it worked sometimes on both devices... but i cant figure out why or when - i could say it doesnt work 9 of 10 times trying.

Im using an original Samsung OTG-Cable, is there a difference between OTG-Cables and OTG adapters?
[Paid Software Announcement and Discussion] madadd:
Hi

You have it correct what i am trying to do. however it said in the info it can connect via a mobile hotspot. this wouldnt be adhoc as the mobile hotspot is acting as a routing device, and you set the 70d to connect via an infrastructure connection.

As mentioned the mobile connection to the 70d works, but I want to control the camera using the EOS utility protocol in DSLR Controller, as this allows better control of the camera.

Also I can connect to the 70d and the eos utility on my laptop via the note3 hotspot. This proves the the note 3 is acting as an infrastructure routing AP Hotspot.

So it makes no sense that the software on the note 3 cannot connect to the 70d. Very odd
[Paid Software Announcement and Discussion] gadgetfl:
I tested this on mine and it also does not work on 70D or 6D on my Note 3. I think I remember getting this to work on my Bionic. The Bionic, I believe, had routing support in the ROM / WiFi Tether app I was running. Unfortunately WiFi Tether for Root (app) does not work on the Note 3. So I am thinking this is either Device, ROM, Hotspot App or OS specific. I am leaning toward Device or OS as the "Slow Connection" warning is new to 4.3 / Note 3. This of course is just speculation.

Lately I have been using the Tp-link for my WiFi connection because it seems more stable and it is easier to switch between 3 cameras. Unfortunately this also does not give you internet.
[Paid Software Announcement and Discussion] maximus96:
Chainfire

*

When you address the AEB/HDR issue, will it be possible to add a timer delay between each *of the shots in the bracket? This would be very helpful when a flash pop is needed in all the frames. The delay would allow time for the flash to recycle.

*

thanks
[Paid Software Announcement and Discussion] Chainfire:
I have finally found and fixed this issue (some devices like the HTC One not finding the TL-MR3040). For the technically inclined, the problem was caused by a bug/misdocumentation of Android's networking API. Very few people even use these APIs so I'm not surprised to discover yet another strange occurance with it (there's a fairly long list already).

This isn't planned, no.

No promises, but it may be that the bugfix mentioned above may actually solve this issue as well. Try with the next update (should be within a few days). The case you describe is not one I specifically support, but I don't see a good reason why it wouldn't work either.

Both may be suffering from API issues. Unfortunately Samsung has mucked up quite a few of its recent firmwares (including S2 and specifically Tab2 and Tab3 ones) breaking USB host support. Try the free "USB host diagnostics" app from Play and see what it tells you on both devices.

In DSLR Controller go to options (cogwheel) and scroll down a bit, there should be a "Strobe recharge delay" option, which should be exactly what you're after.
[Paid Software Announcement and Discussion] xceejhaex:
thanks! great app!

very helpful to me :)
[Paid Software Announcement and Discussion] Chainfire:
The HDR/AEB issue ended up being a problem with the TL-MR3040 firmware. Downloading and installing the latest version ( http://dslrcontroller.com/devices.php ) on the TL-MR3040 solves the problem.
[Paid Software Announcement and Discussion] fotorex:
HDR/AEB is now working with S3mini and 5DMII

Hi Chainfire,

thank you very much for the quick solution. I just downloaded the new TL-MR3040 FW and now everything is working fine.

regards

Frank
[Paid Software Announcement and Discussion] maximus96:
I just installed the 0.99.4 version from the playstore. In M mode, AEB (thru the cog wheel) only works when I have strobe delay turn on. I tried 3 sec and it works and takes all the shots. If i turn off strobe delay, only the first shot fires.

The version of the tp-link software i installed (back on 11/30) is openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin. This appears to be the same as the latest on the website. Should I download the .bin file again to re-flash the tp-link?

edit: never mind, I just re-read what you wrote. I assume "latest version" actually means 0.99.4 and not the later version of the tp-link firmware?

edit 2: i just went ahead and flashed the tp-link firmware. AEB works great now in M mode. Thanks for the fix! Will it be possible to change the shooting mode in the future with the app, changing from M to Av? I think I read Camranger can do this but I could be wrong.
[Paid Software Announcement and Discussion] fotorex:
As the filename for the TP-Link Firmware stays the same, it is difficult to distuinguish between an older and newer version.

Maybe the MD5 checksum should be given as well with the filename.

These are the MD5 checksums from the latest two versions:

TP-Link Firmware DSLR Controller: BBD51A39BE77FEBD262AC289FA5CEBA2 before 20.12.2013

TP-Link Firmware DSLR Controller: D39350CD980F946874FFCF86A5F84BBB after 20.12.2013

The checksum will also be displayed as soon as the TP Link brwoser GUI uploaded the Firmware in the PC memory after pressing the "Flash Firmware" button.

regards

Frank
[Paid Software Announcement and Discussion] pixelk:
As I saw nothing about it in the FAQ or first posts, please excuse me if those questions were already answered :

- Is there any plan to support other OpenWRT-capable routers ( I have a few TP-Link WR703N and MR3020 laying around )

- Is there any documentation/how-to about adding DSLR Controller myself to a running OpenWRT router

- If not, is it ok to try to do so ? (I am an early supporter of DSLR Controller and I don't want to do anything that could harm the author)

** EDIT ** grammar
[Paid Software Announcement and Discussion] Skyr:
Router functionality still working?

Before grabbing one of those shiny TP-Link devices, I'd like to know: After flashing the custom firmware, will I still be able to use the TP-Link as Wireless Router (given that some UMTS stick is plugged in instead of the camera ;)? Alternatively, is it possible to switch between the original and the dslrcontroller firmware?
[Paid Software Announcement and Discussion] fotorex:
The answer is given on the dslrcontroller page:

It shouldn't be a problem to reflash the original firmware as long as you can find the original FW as bin file somewhere on the internet or you restore somehow the original FW from the TP-Link to your harddrive.

Frank
[Paid Software Announcement and Discussion] Chainfire:
There are no plans to support other OpenWRT-capable routers, no. It would be a support nightmare - and DSLR Controller is already one of the worst apps ever to support. As such, there's no documentation how to and I would not appreciate others creating one. (Sorry)

The custom firmware is just a full OpenWRT firmware. You can still use it as a wireless router for other purposes. I'm not sure about UMTS sticks and such still working, I have not tested, though I would expect so. I've read that there are ways to restore the original firmware but it's not something I support, nor would I even know how.
[Paid Software Announcement and Discussion] kalmos:
Focus bracketing question

Hi,

First of all, congrats for that wonderful application.

I am using DSLR on Galaxy SII and the both WiFi solutions (Alternatively I mean) described on your web site. I am a happy user ...

I have a question concerning the Focus bracketing sequence. When we tap Go to start the sequence of acquisition, each new shoot is made only after the transfer to the SII of the previous one. I mean the sequence is Shoot - transfer- shoot. Is it possible to set up a sequence like this ; Shoot-shoot- .... shoot then transfer of all the pictures to SII memory.

The number of picture acquired is calculated by DSLR based on all the parameters entered at the set up of course.

By doing like I expect it's possible to do, there will be much less time between each shoot.

If it's an already possibility, I am sorry I did not catched it ...

Thanks for your answers.

Regards.

kalmos.
[Paid Software Announcement and Discussion] airlion:
connection DSLRController to TP-LINK TL-MR3040 fails

Hi Chainfire,

After plenty of unsuccessful attempts to connect DSLR-Controller with my cameras through the recommended TP-Link box I joined this forum in order to ask for help or any advice.

First of all… yes, I followed strickly all instructions on the DSLRController homepage.

But whenever I try to use the WiFi connection, DSLR Controller comes up with the error message that it couldn't find a compatible camera and that I should ensure that the cam is on and awake and a memory card is present.

When I pull out the USB cable of the TP-Link and attach it dircetly with an OTG Adapter to the tablet, everything works in the well known, perfect way.

It seems that the tablet at least finds and establishes a WLAN connection to the TP-link unit (I can see and sign-in to “DSLRController” in the Android WiFi menu) However the communication with DSLRController APP and the cams doesn’t work.

I even reinstalled DSLR Controller from Google Play Store and flashed the WiFi unit twice. Nothing helped.. the issue remains.

The involved devices are as follows:

- ASUS 7” Fonepad 1 (not the 2013 version) with Android 4.1.2 and the latest ASUS system updates installed

- DSLR-Contoller 0.99.4

- Canon EOS 50D and EOS 7D running the recent Canon firmware and all C-Fn's set according your advice

-TP-LINK TL-MR3040 (vers. 2.1) flashed with firmware file : openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin (downloaded on dslrcontroller.com on 20.Dec.2013)

Any idea whats wrong or what I could try?

Is this issue related to your post about the HTC ONE units ?

Thanks !!
[Paid Software Announcement and Discussion] fotorex:
Hi kalmos,

To avoid the sequence shoot-transfer-shoot you have to disable the option that the pictures should also be stored on your android device (switch to: camera only). But this will unfortunately mean, that you have to transfer your pictures after the bracketing sequence manually.

regards

Frank
[Paid Software Announcement and Discussion] rdcamps:
htc one (M7)

I have been a long time user of DSLRCONTROLLER and have had no problems with wired connections (even my rooted nook worked). So I was keen to try and go wireless with the TPLINK router. The instruction video was very encouraging, it seemed to be a straightforward connection as long as the units/devices are compatible.I got one this morning (verson 2.2). Followed all instructions and was able to establish the DSLRCONTROLLER NETWORK and connected my HTC One (M7) to the network. Everything was going ok until the time I connected the tplink to my EOS 7D and opened the DSLRCONTROLLER APP ...... zzzap ........ my HTC one can't talk to my camera/tplink connection. The HTC One can't find a compatible device. But if connected through a host usb connection, it works flawlessly. I hope this could be resolved soon. The router is practically married now to the app. It will be a hassle recovering the original firmware:crying:
[Paid Software Announcement and Discussion] gadgetfl:
I personally have used the TP-Link with the 7D (6D, 60D, 70D as well) and it works perfect. My guess is it is an HTC issue of some sort.

---------- Post added at 04:44 AM ---------- Previous post was at 04:34 AM ----------

I want to share a photo I just did for a client. Using the TP-Link / DSLRC made this possible (or at least a whole lot easier).

This is a 5 light setup with a whole lot of light shaping going on. Obviously there is some Photoshop going on here but mainly on the cats.

The TP-Link paired to my Note 3, allowed me to walk around the whole seen and tweek the lighting and poses.

The Tp-Link worked purr-fect during the whole shoot.

FYI, this is my clients Christmas card / Christmas letter, there is a whole story that goes with it told in a Film Noir Detective novel style. It was so much fun to shoot.
[Paid Software Announcement and Discussion] rdcamps:
Well, there was a post a few days back that they had actually deciphered what is causing the trouble. Something about the API and that they will soon have fix for it (hurray!). I guess, it is a bit of a hit or miss with so many android phone brands out there and Android itself having many flavors. That is probably why, the camranger chose IOS to be its initial platform because it is less problematic when dealing making an app for only one brand/one flavor of OS. Of course, the camranger comes at a very steep price although it uses practically the same hardware.

PS: Nice shot.
[Paid Software Announcement and Discussion] Chainfire:
When did you download/install the TP-Link firmware from our site? To be sure you're running the latest, download and install it *again*. Also make sure you are running the very latest HTC One firmware (Android 4.3).
[Paid Software Announcement and Discussion] rdcamps:
htc one (M7)

1. I Downloaded the firmware Dec 23

2. I am already on android 4.3

3. After I flashed the firmware the first time, I can't access the router admin page (192.168.0.1) anymore. everytime i try this IP, I fail to connect. I checked the router's IP and found out it has changed to 192.168.1.1 which takes me to the openwrt admin page. Should I use this page instead? Could you give me instructions on how?

Thanks
[Paid Software Announcement and Discussion] chompy18:
After you flash the new firmware, the admin console IP is changed to 192.168.1.1

Try that, it should work.
[Paid Software Announcement and Discussion] chompy18:
LRTimeLapse and 'Holy Grail' timelapse compatibility

Hey Chainfire

First thing's first - this is an amazing app!

I have purchased it about 1.5 years ago and have used it successfully ever since on many many occasions :)

I recently even got the TP-Link router to work so now I can also control the camera over Wifi, which is a real treat.

One question though (I have searched the thread but found nothing regarding this, I apologize if I missed it).

Shooting 'Holy Grail' day to night (or night to day) time lapses and processing using LRtimeLapse - one needs to modify the exposure during the timelapse sequence shoot. Usually by 1EV.

Currently, the timelapse shoot mode in DSLRController allows for setting the interval and number of shots, AEB/HDR or single etc, but there is no option to modify the exposure manually when the ambiance light in the scene changes from within DSLR Controller and so one is forced to do it on camera.

So, what I am asking is this:

Is it possible to add the option to be able to manually modify the exposure while shooting in timelapse mode (Aperture, Shutter or ISO)? 1EV steps are great, 1/3 and 1/2 EV steps would also be appreciated.

A mix of them would also be great (i.e. instead of +1EV in shutter, +1/2 in shutter and +1/2 in ISO for example).

Also, having the EV steps Lightmeter feedback to see if the current exposure settings yield an over/under exposed image and by how much would help alot since then you won't have to check the camera for it which would give the wifi remote real power!

See attached image to see what I mean, I don't think I was very good with my explanation :)

I was thinking of this as a mock for the UI (just a suggestion, naturally :) ):

step <selector between 1/3, 1/2 or 1 EV steps>

<- step btn> ISO <+ step btn>

<- step btn> Shutter <+ step btn>

<- step btn> Aperture <+ step btn>
[Paid Software Announcement and Discussion] rdcamps:
I downloaded this after and reflashed as you instructed. Went to 192.168.1.1 and opended admin page, then to system, then to flash firmware. Chose the .bin file and the reflashing commenced without a hitch. I connected to the dslrcontroller network with my HTC without problem. Connected my 7d to tplink and started the app on my htc. The same problem, htc does not talk to the 7d.

Did you make changes to the firmware between yesterday and today? My original download was yesterday dec. 23 which i successfully flashed but had the "No Talk" problem. I downloaded again the firmware this afternoon and have the same results. Was my second download an updated firmware or did I download the same firmware version as the one from dec. 23?