Visual Feedback and UI Improvements

[GoogleCodeExporter]

I can't gather from the app installed, nor from your description or blog if 
there is visual feedback. Does the bluetooth data rate even support any sort of 
wireless video feed?

I have the app installed but have not invested in the Arduino setup as of yet. 
I want to clear a few things up before I start building.

Also, does this need to be wireless?

https://market.android.com/details?id=eu.chainfire.dslrcontroller
Granted the above app doesn't even use Arduino but if the data rate could be 
higher without using bluetooth maybe that could be a possibility.

Also, I do design work here and there, if I wind up going this path maybe I can 
throw some GUI improvements your way on the Android side of things?

Original issue reported on code.google.com by hjpa...@gmail.com on 25 Aug 2011 at 11:15

[GoogleCodeExporter]

There is NO visual feedback. As you mentioned, the data rate on Bluetooth 
cannot support visual feedback. Another significant limitation is the 
processing power of the ATMEGA368 chip.

I included the liveview button to implement the "move focus" functions. As of 
now, Focus can only be moved when liveview is ON. Which makes sense anyway 
because I guess you won't be looking THROUGH the viewfinder while using your 
android device to move the focus.

To get a get a visual feedback, I would suggest a video transmitter/receiver 
system coupled with a portable LCD monitor connected to the video out of the 
EOS. This could be useful in Movie Production Setups where the camera is 
mounted on cranes.

Also, the application needs MAJOR interface redesign. That was a quick n lazy 
build using app inventor. An updated version will be posted soon. Thanks for 
your help and I will contact you soon to discuss about this. 

In the link you sent, the Android Device is acting like a USB HOST itself. That 
is fundamentally different to this project, where the Arduino system acts as 
the host. 

[I would like to mention that visual feedback will be implemented in ANOTHER 
project, based on an ARM Cortex gumstix board. The method of operation will be 
vastly different from this project, obviously.]

Original comment by manis...@gmail.com on 26 Aug 2011 at 9:04

[GoogleCodeExporter]

On your point:

"Also, does this need to be wireless?"

Well, you COULD technically connect the Android directly, but that would 
basically dismiss the purpose of this project. i.e wireless EOS control. 

And I believe that directly wired implementations would have very limited 
PRACTICAL utility in the photography world. (I could be wrong though, I am not 
a pro photographer) 

Original comment by manis...@gmail.com on 26 Aug 2011 at 10:13

[GoogleCodeExporter]

Original comment by manis...@gmail.com on 26 Aug 2011 at 11:23

• Changed state: Accepted

[GoogleCodeExporter]

Would it be possible to get record time, size left on memory card, and or 
record/stop function for video mode? That would be a really good reason to have 
wireless for me. I can start and stop cameras wireless and monitor their record 
time/time left on card.

For me I can go the wired route to get some external monitor solution, but this 
wireless solution would probably be more beneficial to me.

Original comment by hjpa...@gmail.com on 26 Aug 2011 at 6:21

[GoogleCodeExporter]

Yes definitely possible. In fact, the start/stop feature for video can be 
implemented in less than 10 minutes of coding. (You will see what I am talking 
about here when I release the source code.) 

I couldn't include this feature because I have no video capable DSLR to 
experiment with right now. 

The record time will be slightly more complex, but still very do-able. 

Original comment by manis...@gmail.com on 26 Aug 2011 at 6:31

[GoogleCodeExporter]

I would appreciate any of those added features, I'm going to order the parts in 
the next few days and see if I can help at all.

Original comment by hjpa...@gmail.com on 26 Aug 2011 at 6:35

[GoogleCodeExporter]

I you are going to experiment, I recommend you to use a regular large(i.e not 
mini) Arduino and the regular version of the USB sheild. 

The Arduino mini is VERY small. Look at the usb connector on the main page to 
get a relative idea. 

That's what I did for version 1.0 of the prototype. 

Original comment by manis...@gmail.com on 26 Aug 2011 at 6:46

[GoogleCodeExporter]

What specific Canon video dslr do you have? 

I can try running simulations based on your  camera's properties.. 

Original comment by manis...@gmail.com on 26 Aug 2011 at 7:02

[GoogleCodeExporter]

I'm actually using t2i's running Magic Lantern which might complicate it too 
much.

Is the only problem with the Arduino mini is its size? And did you get the 3.3v 
or 5v version. Because I noticed that the USB shield for that is only 3.3v.

Original comment by hjpa...@gmail.com on 26 Aug 2011 at 7:50

[GoogleCodeExporter]

I never used Magic Lanterm, so I can't guarantee compatibility here.

And yes, the size is the only inconvenience that I can identify for the Arduino 
mini. Everything else works as it should.

I'd recommend the 3.3v to minimise hardware complexity. You will also be able 
to power it from a 3.7v LiPo. Very useful. 

Original comment by manis...@gmail.com on 26 Aug 2011 at 8:41

[GoogleCodeExporter]

there is different alternative for the USB shield?
can i use the Arduino nano instead the mini?

Original comment by dmx...@gmail.com on 21 Sep 2013 at 2:10

[GoogleCodeExporter]

You can use the arduino nano instead of the mini. Just make sure the USB shield 
is connected to the appropriate pins of the atmega chip. Regarding the USB 
shield alternative, I don't think there are equivalents on the market right now.

Original comment by manis...@gmail.com on 21 Sep 2013 at 2:12

[GoogleCodeExporter]

thank you.

Original comment by maoza...@gmail.com on 2 Oct 2013 at 9:43