web_parrot
Captain
Flight distance : 23625 ft
United States
Offline
|
By now there should be something sponsored by DJI in the Support Section of their Web pages. [ this has also been posted on the MavicPilots Forum ]
As a new owner I spent hours reading the manual, dozens of hours on both the DJI Forum and MavicPilots.com, and similar amounts of time searching out and watching credible videos (As a retiree I have the luxury of that kind of time, but I’m sure not everyone wants to go through all that just to enjoy a hobby BEFORE starting the hobby!)
Anyhow, I found it extremely frustrating wading through the endless (and many times pointless comments and questions). I acknowledge that this is a complex device/machine/hobby/toy.
There is a lot of very VERY credible information, most of it provided by customers ( DJI likes “users” but we’re really customers, first). So much could be resolved if DJI would invest in a well designed hierarchical Trouble Shooting database.
I’ll use Sony cameras as an good example of how it could work. (I’m sure you’ve all seen similar approaches). When you enter the trouble shooting section you respond to a dropdown menu hierarchy. What Camera, What Model, What Firmware (with prompts how to find it), date of purchase, ….
So many of the followup up questions I see could be handled the same way, narrowing the issue…getting to the issue specifics.
Using a hierarchy such as this…
Serial Numbers (gives model, month, and year of manufacture)
Date of Purchase,
AC Firmware,
RC Firmware,
phone/tablet/screen model,
Operating System,
DJI Go Version,
Area of concern ( Flight, SetUP, Repair, Warranty Process )
Chat option
Finally an option to detail a written description for Case review
With that hierarchy and the thousands of questions already resolved ( or pending ) a focused set of FAQ or problem pointers could be resolved.
At a minimum DJI should include a section where Forum members could list the key components in their profiles as a way of cutting down on the number of followup clarifications in the threads. Simply including Firm/Software versions, interface devices, operating system and Go 4 versions would be a real starter.
|
|