> why lock down the software? I work with hardware (not quadcopters) that is limited by software and the software is locked down, so I can at least tell you th

> why lock down the software? I work with hardware (not quadcopters) that is limited by software and the software is locked down, so I can at least tell you the reasons we do it: 1. Warranty. We know the limits of the hardware and our customers expect us to warranty that hardware for a reasonable amount of time, so we can't have consumers pushing the hardware beyond the duration/temperature/speed/etc that is going to significantly reduce its lifespan. We're not trying to be jerks, we're just saying here is our warranty and these are the parameters/limits within which we can offer that warranty. 2. Hackers. Hobby hackers are cool and most of us that work on these products are hobby hackers too, so we can appreciate the curiosity, fun and legitimate utility of modifying the software. But, there is a rising threat of malicious hackers and many of our customers (and non-customers) expect us to protect society as a whole from our products being taken over by malicious hackers for the purpose of harming someone. If nothing else, nobody who makes the products want to find out their product was used for that from a moral standpoint, not to mention a liability standpoint. As for Canon, I'm sure people have tried to return camera bodies they've tried to hack and have bricked or otherwise damaged and that's not fair to Canon either. The right solution would be for the manufacturers to make some of their software open source so hobbyists could add features and submit official pull requests that can be vetted by the engineers that are responsible for the reliability of the product and the safety of the people around it. That's my two cents on it anyways.