Charles Adams
First Officer
Flight distance : 3821312 ft
United States
Offline
|
RuneRider Posted at 2017-9-18 09:35
When I first bought the spark (in early July) updating firmware took days and required a call to Dji as the software crashed constantly. When I finally updated the firmware the update to the batteries would not work. Had someone with experience look at the batteries, I think they used their drone to update the battery FW. After calibration and updates every attempted take-off resulted in a flipped over drone immediately (props are fine, have been changed several times). Now a critical error showed up and flight was impossible. Opened a repair ticket, received shipping labels, critical error disappeared for no apparent reason. I cancelled the repair and successfully updated to the newest FW. I had a nearly successful flight if not for the spark being difficult to control despite both calibrations. Now I constantly calibrate before attempting flight. Still having issues and the latest app has made them worse. The DJI Assistant 2 software now will not talk to my spark at all.
Yep, that's quite the list. Each one merits detailed analysis and conversation. The one that jumps out at me (the one for which I have direct experience) is the one least likely to help you with flights, but let's start there.
I've had exactly the same issue with my DJI Assistant 2 app, where it stopped recognizing the spark. It identified the spark as something entirely different (and I didn't take a screenshot). I even had difficulties uninstalling the assistant app so that I could try a re-install. I ended up going back to a restore point (I'm on Windows), where I was able to try a reinstall of the DJI Assistant 2 App. And that's what finally worked for me.
There was a new version released on 9/7 (v1.1.6), I'm not sure of what version you are currently on. I decided I wouldn't run an "update", I instead uninstalled the prior version and installed 1.1.6. I had no issues and the app still recognized the spark.
That first episode I had, I have no explanation for why it behaved that way, and I have no explanation why I had to go back to a prior restore point. But it's how I addressed the situation.
I recommend attempting to uninstall your app, and installing it again (latest version if that's not the version you already had). And then try with the spark (if you've not shipped it already. If that solves your problem, we'll move on to the next problem. If that doesn't solve your problem, there may be some deeper steps we can go into. I found that when installing the assistant, there's a new driver that it installs. Might be that you are having issues with that driver (if you are running on windows, if a mac then I have to bail as I have no mac experience).
|
|