Dear All,

I was using Cannon S100 previously for mapping purpose with CHDK, 1/2000 shutter speed, IS turned off and focus set to Infinity but still get around 50% blurry image.

Now I will use Sony Nex 5n camera on Flatmap1 gimbal with 16mm stock fixed lens and IR triggered from APM for more ground coverage and quality image (hope so..)

Please share your Nex 5n camera setting (Auto or manual or shutter priority?) and any experiences, pros & cons using Nex 5n for mapping purpose.

Let me start from what I was reading from some forum (forgot the link):

Sony Nex 5 series  Camera Setting for Mapping:



  • More pixel compare with S100 = More ground coverage
  • Fixed lens 16mm = less blurry image result
  • ??


  • Heavier compare with S100
  • No GPS onboard
  • Nex 5n Time between shutter > 2 sec = S100 faster < 2 sec (if you need to fly really fast)
  • ??

I will update first page regularly that may be useful for others.

Many thanks in advance for your contribution.


You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –


      • 300km

        Hi iskess. How do you trigger the a5100? I don't think it has IR

        • It uses USB (multiport)
    • Hi Darryl,

      I've just checked my last log and don't miss a single shot (363 pics).
      My cable is a Gentle IR trigger.

      Here my setup
      speed: 12-18m/s

      Did you check the log of your RCOUT trigger channel? Matches the
      trigger/pics count?

      Wolfgang R.

    • How quickly (seconds) are your pictures being taken? There are two issues I can see.

      1. You're in auto iso mode - your camera has a limit to how fast it can refocus and take a picture (~2 seconds)

      2. The IR trigger sending signals while your camera is still taking the last picture.

      We had this issue - you can decrease overlap or fly higher.

  • Great to see a lot of different setups being used for geo-mapping :) thumbs up!
    As I see most of you guys are working with Sony MULTI equipped cameras. Would like to share a great trigger solution for your aerial photography, ''Plug & Play'' solution with ON/OFF function (great to save battery life and for landing plane type crafts) and features multiple trigger modes. Super small and light weight with an option to chose ANGLED connector to fit your design best. We have a 10% discount coupon: DIYDRONES  @
    Hope you found this helpful guys!

  • My setup for fixed wing use S100

    • f3/5
    • 1/1000
    • ISO 400
    • mode : TV
    • W/B : Daylight
  • Thanks for your input Gents. I believe the common size lens would be 15- 20mm wide angle for mapping? I like the Sony Cams because there seems to be more trigger options for them.

  • What is the quality of Image like with the NEX5? I ask because i have been offered two cameras at more or less the same price. One being a Sony A6000 with out a lens and a Sony NEX-5R with 2 lenses. Not sure which to go for.

    • I would go for A6000 simply because of 24 MP resolution and it's lightweight.
      You will get more mapping coverage area compare with Nex5 series.
      • In my experience, having more resolution is great but useless if your mapping area is large as you will dealing with gigabytes of data that took up to several days on large computer to process. The processing time can be speed up by lowering the resolution that makes utilising very high res camera become useless. Somehow i found 20Mp is more than enough. The next thing to consider is the weight and camera's sensor size. Sony nex3, nex5, A5000 and A6000 using an exactly same sensor size but has different resolution. Nex3 and A5000 is the lightest while A6000 is slightly heavier.

This reply was deleted.


Abdulatif Tlaib liked Ryan's profile
20 hours ago
DIY Robocars via Twitter
RT @SmallpixelCar: First time at @wsraceways. After tuning @HokuyoUsa lidar signal and camera sensor on @NVIDIAEmbedded, my car was able to…
DIY Robocars via Twitter
RT @breadcentric: The handy bit about racing with self-driving cars is that one can type while the car is racing. Report from #AWSDeepRacer…
Jun 18
DIY Robocars via Twitter
RT @chr1sa: Our Bay Area @DIYRobocars meetup is now at 2,700 members. Next in-person events (in Oakland) are training day on July 17 and…
Jun 18
DIY Robocars via Twitter
Videos from the ICRA autonomous racing workshop are now available:
Jun 10
DIY Robocars via Twitter
RT @SmallpixelCar: Prepared race track for Warm Spring Raceways @wsraceways and looking forward to test my new car at RAMS RC @ramsaicar fa…
Jun 6
DIY Robocars via Twitter
RT @f1tenth: Trying out some nasty blocking maneuvers 🏎️🤖 #f1tenth #autonomousracing
Jun 5
DIY Robocars via Twitter
May 27
DIY Robocars via Twitter
RT @araffin2: I will talk this Saturday from 18:00 to 19:00 Paris time for the @diyrobocars community about learning to race in hours using…
May 27
DIY Robocars via Twitter
RT @a1k0n: Luckily the infeasible hairpin problem was easily reproducible in simulation and I could test the fix before bringing the car ba…
May 26
DIY Robocars via Twitter
RT @a1k0n: Another problem was that I was over-constraining the car's allowed accelerations, so it didn't think it could turn as tight as i…
May 26
DIY Robocars via Twitter
RT @a1k0n: Breaking the map up into two halves worked, but I had to be more careful about separating the inner track from outer. There's se…
May 26
DIY Robocars via Twitter
RT @a1k0n: Here's a datalog for my fastest lap of the day. Lap timer is tiny window lower-left.
May 26
DIY Robocars via Twitter
May 26
DIY Robocars via Twitter
RT @a1k0n: Here was my car's POV. Man this track is confusing in first-person! After the incident my camera was all scuffed up and I was af…
May 23
DIY Robocars via Twitter
RT @circuitlaunch: Loved seeing so many familiar (masked) faces at Circuit Launch today for our first in person @diyrobocars in over a year…
May 22