Cannot connect to caddx vista in configurator

[leoponce82]

My caddx vista does not show up on the configurator (HOME tab, connect to device). When I go to ROOT tab, I can see a "CDC Serial interface" but it does not connect. (It does not always show up on the root tab)

I tried using develop.fpv.wtf, and I can see the vista on the devices list "DJI Fpv Air unit Lite" but it gives an error: "Could not connect to the device, make sure that ADB server is not running on your machine (adb kill-server) and that you are not connected in another tab/window"

I tried the command, still nothing.

Please help and thanks in advance

v1.0.0 - Trace ID: 5af43bbb-6b74-489c-9185-ac06c25be1ea

[stylesuxx]

@leoponce82 since you closed it, what was the issue?

[leoponce82]

My caddx vista was not recognized by DJI assistant 2 (FPV series). I appeared in "devices and printers" on windows, and sometimes the folder (where naco.txt was) would appear, but not consistently. (On Windows device manager it would appear as Bulk interface) I tried rooting it but the fpv.wtf configurator would not recognize it. On develop.fpv.wtf the vista was recognized but it would not connect. Ultimately, I changed the driver using Zadig. I went fpv.wtf and rooted it successfully.

[robertrypula]

@leoponce82 I think I have the same issue as you had. I have both googles v2 and vista rooted and everything was working fine. I was playing with OSD placement in Betaflight configurator and after few restarts I started to see "Waiting for OSD..." in the googles

Currently I don't see Vista in WTF configurator. Vista mass storage is showing up. DJI Assistant doesn't see Vista at all. In Zadig I see this:

On the left is what I see when Vista is connected (I marked potential Vista devices with orange dots), on the right when it's not. What device you selected and what option you picked to solve the issue?

[leoponce82]

@robertrypula my issue was a little different since I los the "waiting for OSd" but the "not seeing vista in the configurator and assistant " behaviour is the same. I used the Bulk interface and replaced the driver with zadig. I did it two times. First to "USBlib" and then i think it was "winUSb".

[robertrypula]

I figured that out! I was changing many different combinations of the devices and drivers and looks like the device that WTF configurator is using is just "CDC Serial" (Interface 4 on my laptop). The driver that we need to install is USB Serial (CDC). From the dropdown I picked first option "Install Driver":

I needed to root again. I had also problem with Health Checks:

At the end everything works as expected. There is only one bad feeling in my head that the issue will happen again. I have CineLog35 and I'm using 4S lipos. Vista is connected directly to the VBat and I almost always have arcing noise then I connect battery. In the other threads I read that it could be the cause of loosing root and (in my case) ending in "invisible" vista.