![]() I need to get into open-source flight controllers more and settle down for a few evenings with a PixHawk setup. ![]() I have always enjoyed using user-supported software such as Linux which discreetly notifies you that an update is available, you choose what you wish to include and when you want to do it and the process is done in the background while you get on with work. Microsoft seem to decide on updates and force them on you at inconvenient times, DJI seem to produce updates that breal systems that were working. I think I need to build a Win 7 machine and run the DJI software (Naza, Wookong, A2, Zenmuse, IOSD and Lightbridge) from there, keeping it well away from the internet after the initial build. Both the Wookong software and firmware are at the “latest” (2016!) level. Both my desktop and laptop Win 10 machines have managed to behave with the Wookong Assistant. I’ve been lucky so far with sorting a different receiver on the Wookong controlled S900 I bought recently. I remember when W10 was released and Naza owners started having issues DJI said to use a usbser.sys file that was created in 2010. Even though on both PC’s they have the same creation date there is is difference of 1.5kB in file size. Something else I’ve noticed buried in the Windows System32 directory is a difference between the usbser.sys file. To name a few, this PC that everything is running on will never connect to the internet again. Ran the Naza Assistant software and voila!! The Naza Assistant is talking with the Naza Flight Controller. I booted it up while disabling internet access so Microsoft couldn’t hijack it. Consequently no communication between the PC and the Naza Assistant.ĭetermined to get to the bottom of this I pulled out a PC I hadn’t used for some time. I tried to run everything on another PC but before I could plug in a USB cable W10 did an update. I think that as I suspected a W10 update has hosed the Naza Assistant and/or the DJI VCM driver. It looks like I’m right on cue for abusing my pain medication today. Even the Smart Battery code was released and now you can use any off the shelf LiPo with the Solo and still have all the smart features of the original battery. The 3DR Solo was released in 2015 and today there is still a very large community continuously evolving the drone’s capabilities with Opensource firmware and software releases, even though 3DR dropped the product entirely in 2018. If a manufacturer, in this case DJI, decide that continuing support for one of their products is no longer viable, why can they not just release the SDK to the OpenSource community? This worked wonders for the 3DR Solo when 3DRobotics released all their code to the public. ![]() Rob, ran into a similar issue with Apples iOS 14 and the DJI Groundstation APP, whereby the APP would crash when trying to access the iPad’s Bluetooth connection. ![]() I fear this is just another example how tech luddites, such as myself, have fallen foul of those that create Operating System upgrades and hardware manufacturers that refuse to keep their utilities up to date. To rule out a hardware fault on the quad I’ve tried connecting my F550 and Xugong Pro2, both with Naza-M V2’s, only to have the same negative response, even though a few weeks ago everything was working fine. I’ve run the Windows Compatibility routine. I’ve tried different USB cables and ports. The Device Manager shows that the DJI VCP driver is installed correctly. However when I connected the quad via USB to the Naza Assistant V2.40 there was no communication. Last night I set about configuring a recent quad purchase (Steadidrone with Naza-M V2), and due to a recent W10 update I had to install the DJI VCP drivers again which went without a hitch. Since the release of Windows 10, and subsequent updates, I have become accustomed of having to force DJI’s unsigned drivers to install so I can still configure my Naza and Wookong flight controller.
0 Comments
Leave a Reply. |