DROTAG.x relies on several open source projects. Airborne Projects takes open source licenses very seriously and we have a public repository for the modifications made to the open source projects it relies on, fulfilling the clauses of GNU Public License and Lesser GNU Public License where applicable. We are not a company of lawyers so if we made any licensing mistake let us know so we can correct it as soon as possible.
1. Reasons for Lack of APM 2.x Support
DROTAG.x does not support APM 2.x and earlier models because these components do not support newer versions of Ardupilot which have critical features for the correct work of DROTAG.x. We cannot backport these features to older versions.
2. Considerations on Appropriate Camera SD Cards.
As you may be aware there are many cards on the market, but not all card models are advised. We advise the Samsung 16GB Class 10 Pro or the Samsung Evo Series cards. There are other adequate cards for use with DROTAG.x, which can be consulted in this page of Camera Card Benchmarks. A good way to sort the benchmark table by the “Tested Write Ran” which represents Random Write characteristics. This characteristic is important because it makes the DROTAG.x tagging faster. It is not essential but a very nice characteristic if you want to land and have all pictures already tagged without further waiting.
If these cards are not available to you, you should look for cards, with at least Class 10 rating, although that is a very weak criteria, as this rating only means that such a card can at least write 10 MB/s, which may not be enough for the Sony Alpha 6100. Another aspect which is important for the performance of you camera and DROTAG.x is that your card should be correctly formatted. We advise that you do avoid formatting the card if possible and just use the default partitioning scheme. This is because a naive formatting may misalign the partition and data layout inside the card and make it under-perform very extremely.
If you think you may need to format it, then when you unpack your camera card for the first time, use Win32Imager to read it and store the Binary Image of it. If afterwards you need to “format” your card, just write this empty image back to the card. This ensures you have a backup of the card state out of the factory. This may seem ridiculous, but is real, with added advantage of providing you with a secure erase of your data. You can read more about the technical reasons in this page, but suffice it so say that there are cards which have a best case write of 11.5MB/s and a worse case write of 33KB/s.