SR-71Habu
lvl.2
Flight distance : 191125 ft
United States
Offline
|
Hey, I'm not trying to be rude here, but, Seriously Mindy?
Are you implying that this message is something to worry about? And that if the message appears then we are not doing something correct and should adjust our flying so that the message never appears? And that we should do that by pushing the sticks gently?
Here's my take as a career IT engineer/administrator in the software dev biz and as a guy that has been into RC for decades:
Complex systems that generate logs use a concept called "logging levels". Events that are logged are categorized based on the criticality of the errors. They need to move this particular message into a category that is not exposed to end users via the Go app. Or using whatever means they use to decide what events end up showing up in real time to the end user.
Not only will this error message appear in the scenario outlined here, but it also pops up when you tilt the camera upwards to the end of travel. It doesn't happen when you tilt the camera downwards to the end of travel in that direction if I recall correctly. So does that also mean that a user has to somehow judge the gimbal accel/decel algorithms accurately enough to let of the spring loaded wheel on the controller in time to keep the gimbal from hitting the stop? I hope not....because that would be a nearly impossible skill to master, particularly considering how adjustable the gimbal behavior is when panning up/down. I've been annoyed too many times already with tweaking the gimbal to get a good looking up/down pan.
The way 3 axis brushless gimbals work internally would rule out damage from hitting a mechanical travel limit anyway. How many people who own Mavics have accidentally turned it on before removing the gimbal clamp? You'd think the gimbal doing its initiation dance while locked down by the gimbal clamp would destroy it, right? Well, it doesn't. I just read about someone getting an error in the Go app telling them to take off the clamp because they powered up left the clamp on. This would be an example of a useful bit of info to pass on to a Mavic pilot...because it will affect the performance of the device and it is something that a user can take action on.
But a ridiculous informational message about "gimbal travel limit" that is invoked during normal use of the product serves no purpose for the end user. Do these gimbals have electronically definable travel limits that should be programmed to activate before mechanical travel limitations? If so, then maybe the team responsible for the gimbal hasn't heeded the log message WE are seeing and needs to tweak the travel limits so that a mechanical stop does not happen.
I actually doubt that, but had to toss it out there. So can we get rid of this useless message please? You guys see how it is worrying people....Or if you won't do that, can we get more detail about the possible damage being inflicted on the gimbal when that message appears? And if there isn't any damage done, then WHY the HECK do I need more distracting pop ups on the screen while I'm trying to fly and film?
Thanks much! |
|