Punchbuggy
Second Officer
Flight distance : 483166 ft
Australia
Offline
|
As you say, the problem is with the PC, not the drone. Problems getting calibration to run have in the past been caused by Windows preventing the Vision drivers from being installed (when Ass2 is installed). The Vision drivers are required for the two-way communication which allows the app to "see" what the drone sees. The issue was due to the drivers not being properly digitally signed, so Windows skipped past them on install - but I thought that issue had been resolved with recent Ass2 versions.
Perhaps the old fix is worth a try? Have you tried installing Ass2 with driver signature enforcement disabled on your PC? If not, uninstall Ass2 and reboot the PC in debug mode, selecting the option to disable driver signature enforcement on boot up (Google "driver signature enforcement disable"). Then install Ass2 again. When the CMD box opens to install those drivers from DOS (it's a black box on the screen), you'll be prompted as to whether you want to installl them, and you say "Yes". Of course, if DJI have fixed the driver signatures, all drivers should just install OK without intervention. |
|