Punchbuggy
First Officer
Flight distance : 573054 ft
Australia
Offline
|
OK. Solved this.
Going back to Assistant 2 v1.0.9 (thanks SED) didn't help - slightly different error amounting to the same thing - "frame alignment error".
Thought I'd try the latest again - v.1.1.2-2. Uninstalled .09, restarted laptop with driver signature enforcement off (Shift-Restart - Troubleshooting settings), ran the .2-2 executable in Admin mode, and when it opened up the DOS CMD box to install the various drivers I paused the script and received a "no signature - do you want to install?" for one of the drivers - I'm sure the timing of pausing it was coincidental.
So there IS at least one unsigned driver in the latest version of the installation still - you'd think DJI would have sorted this by now.
Ran Assistant 2 .2-2 and once the craft was recognised, entered "Calibration". The "frame error" still appears, but this time it didn't ask me perpetually to reboot the craft and the button to Calibrate could be selected. Yay! VPS calibration successfully performed on both my P4 and P4P.
[edit - days later] So tried to do a VPS calibration ofter another firmware refresh of my P4, and error still there (as above) but this time I can't start calibration again. Huh? Back to yh start! Nothing had changed on my laptop since my last success, so what changed? Aha! Rebooted with driver signature enforcement off and restarted Assistant 2 in Admin mode. Success. Sadly that means that each time I want Assistant 2 to work properly I have to restart Windows with driver enforcement off. Sigh.
|
|