"I can't figure out from the information provided whether they are simply shutting down the cloud services or actually making changes to the hardware (which is how I understand "bricking"). Anyway, this is why I always check that all my automation…"
"I think some confusion could have been avoided if the blog post mentioned - who else than Craig supported this action and their position within the community - how was UAVS given a chance to defend and to correct their actions (ie. who contacted…"
"I mean basic stuff like attacking the protocol, scrambling the signals, fooling the sensors etc. There's only that many options how this can be achieved (that I can think of). Maybe by understanding the limitations of the tech, people will fly more…"
"I wish some technical explanation would be posted with these kind of articles. Many people seem to not know how or why this is possible and when it might or might not work. Why not educate the public?"
"Ugh, not a design flaw. Like already said before, this isn't a hack/exploit, it's a feature of the MAVLink protocol that can be used for malicious purposes. It's a good thing that this (=current implementation of control links as a whole) gets more…"
Didn't find documentation for this. In the attachment, there is no arrow, but once flying, it changes to arrow and the number grows. mission planner red arrow.PNG
"Yes, smaller files do work. I didn't have many files to test right now, but 40MB doesn't work either. 10MB is a pretty short flight (at least with a plane) with Pixhawk default log settings. Maybe some kind of error message would do better than…"
"Hmm it could be that (I definitely lost RC signal a few times), although when I just tested this by turning my transmitter off, the Pixhawk first beeps a deeper tone and then a higher tone similar to the one on my video, but faster. Maybe the video…"
"Speaking of odd sounds, here's another one I can't figure out. Noticed this today and happened quite a few times during the flight: https://www.youtube.com/watch?v=acUk1WFNAbU
"I'm getting this same thing with 3.2.3. Seems to always happen when Pixhawk is moved. Will try to adjust the min PWM later just to be sure it's not coming from the ESC, but since Graham already did that.."