FAQ FAQ  Forum Search   Events   Register Register  Login Login

E-mount electronic protocol reverse engineering

Page  <1 121314
Author
bostwickenator View Drop Down
Newbie
Newbie

Joined: 19 June 2009
Status: Offline
Posts: 28
Post Options Post Options   Quote bostwickenator Quote  Post ReplyReply Direct Link To This Post Posted: 25 September 2020 at 02:42
Sorry I didn't realize how I left those scattered around it's been a while since I was in the code. I've updated the readme with a diagram of the connections (MS paint sorry) https://github.com/LexOptical/E-Mount/blob/master/README.md
 



Back to Top
profhankd View Drop Down
Newbie
Newbie

Joined: 11 February 2010
Country: United States
Location: Lexington, KY
Status: Offline
Posts: 28
Post Options Post Options   Quote profhankd Quote  Post ReplyReply Direct Link To This Post Posted: 25 September 2020 at 04:19
Originally posted by bostwickenator bostwickenator wrote:

Sorry I didn't realize how I left those scattered around it's been a while since I was in the code. I've updated the readme with a diagram of the connections (MS paint sorry) https://github.com/LexOptical/E-Mount/blob/master/README.md


Just to be clear, I wasn't complaining. :-)

I just want to make sure that when I wire it up any failure to duplicate the behavior you saw is due to me testing with a different E body model. I modified a Voking extension tube and am expecting my Teensy 3.5 next week, so probably another week before I have results to post here....
Back to Top
bostwickenator View Drop Down
Newbie
Newbie

Joined: 19 June 2009
Status: Offline
Posts: 28
Post Options Post Options   Quote bostwickenator Quote  Post ReplyReply Direct Link To This Post Posted: 25 September 2020 at 15:07
Sounds good! Happy to help if you have any issues with getting that bootstrapped
Back to Top
profhankd View Drop Down
Newbie
Newbie

Joined: 11 February 2010
Country: United States
Location: Lexington, KY
Status: Offline
Posts: 28
Post Options Post Options   Quote profhankd Quote  Post ReplyReply Direct Link To This Post Posted: 13 October 2020 at 05:54
Ok. I managed to hack connections into a Voking adapter and hooked it up as you suggested to a Teensy 3.5. It spews lots of C and c messages and when my NEX-5 is turned off shows a B and L. Mixed in among the C and c messages are things like:

00:44:31.248 -> C 5971747
00:44:31.248 -> c 5988131
00:44:31.248 -> [B:5988268]
00:44:31.248 -> [l:5988582]
00:44:31.248 -> Init Complete
00:44:31.248 -> [b:5988595]
00:44:31.248 -> C 5988605
00:44:31.248 -> [B:5993466]
00:44:31.248 -> [b:5994175]
00:44:31.248 -> [L:5994184]
00:44:31.248 -> [l:5994832]
00:44:31.248 -> Body->Lens F02900020001FFFFFFFFFF7F0000000000000000000000000000000000000000000000000000A60555 5995290
00:44:31.248 -> Us->Body no message
00:44:31.281 -> c 6004815
00:44:31.281 -> C 6005113

However, the camera doesn't seem to be getting much out of this. The only sign that a lens is attached is that the camera is not letting me fire the shutter. It still has "F--".

Is this roughly what you'd expect? What do you think I should be doing next?

Thanks.

Back to Top
Dyxum main page >  Forum Home > Dyxum Community > Knowledge Base Page  <1 121314

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.047 seconds.

Monitor calibration strip

Dyxum.com - Home of the alpha system photographer

In memory of Cameron Hill - brettania

Feel free to contact us if needed.