ADB devices not found

tom

@marian So is SSH working then? I see that you've done some work with this VOXL Cam already based on your post history?
Or were you connecting directly to the Flight Core via JST to USB?

marian

@tom Yes, the ssh and connecting the flight core via jst to usb is working.

When I bought the voxl-cam I understood that came calibrated and ready to use. But, as I used it on a custom frame the sensors like accelerometer, compass and gyroscope are not calibrated.

I used it on the frame on the same way like seekers (of course, I needed it to adapt the /etc/modalai/extrinsics.conf file for my configuration), but

whenever I use a GPS with compass (as M8N u-blox) I can't calibrate the compass, it will see a different position instead of the position the drone really is, it is finishing the calibration anyway, but after reboot it will ask me again to re-calibrate the compass
whenever I used it for indoor navigation, so GPS and compass disabled, I calibrate the accelerometer with ROTATION-NONE as per modalai documentation,then once I have the local position on, the QGC tell me that I have a roll failure detected and, of course, can't proceed with arming.

So, basically I can't use at all the voxl-cam

tom

@marian Okay that is good that at least ssh is working so the board should be functional. I wonder if it is some sort of user privileges issue that ADB isn't coming up. What if you do sudo adb devices? And what if you remove that android rules file: sudo rm /etc/udev/rules.d/51-android.rules and reboot your PC? I'm not sure that file is necessary.

For those other questions, I would open a new forum topic so that the whole team can get eyes on it.

marian

@tom The results are the same even if I use sudo or I remove the 51-android.rules

tom

@marian Did you reboot after removing the android-rules file?

tom

@marian We may have to take a look at your hardware in house, checkout our RMA info here: https://modalai.com/rma

marian

@tom yes, I rebooted the pc

marian

@tom In terms of RMA, can we try to have a remote diagnostic? I'm far a way from US ...

tom

@marian Have you been able to ADB in to any other VOXL devices on this PC in the past? From what I see in your lsusb output everything looks correct. I'm wondering if there's an issue with your ADB install

tom

@marian Here is what a working VOXL looks like on my machine running Ubuntu 18: Bus 001 Device 068: ID 05c6:901d Qualcomm, Inc. We have others at the company who use 20 so that shouldn't be an issue

tom

@marian

[  +0.150491] usb 1-1: New USB device found, idVendor=05c6, idProduct=901d, bcdDevice= 3.18
[  +0.000010] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000005] usb 1-1: Product: APQ8096-MTP _SN:AF0F8B82
[  +0.000004] usb 1-1: Manufacturer: Android
[  +0.000003] usb 1-1: SerialNumber: 4399683d```

marian

@tom I see the same things, but stiill the adb or fastboot commands don't see my device. I tried with two different laptops, and the problem is the same as per images below:

marian

@tom I tried the adb for windows and it is working fine, I'm able to connect onto the voxl-cam via adb shell command.

Still have a problem via wsl to see the devices from ubuntu client, but if is working from windows client for adb I suppose that the device is fine.

tom

@marian Okay that's some good news! Since you're able to ADB from windows that means the VOXL Cam itself is functional. It must be some permission issue. We recommend using Ubuntu 18 directly and none of our engineers here use Windows for software development so I'm not too familiar with WSL. Do USB devices need to be added manually? Not sure they're shared from windows to WSL automatically. You may also need to stop the ADB server from running on the Windows client in order for it to work in WSL. (adb kill-server)

marian

@tom It's working just fine

There were a few issues:

when using WSL we need to start the server on windows via powershell and the first time will ask to set up the security access, just give access on both networks, this is used by wsl to give access to ubuntu client.
On linux, if we install the adb via apt install, the adb version will be older and the connection with the server will not work. Should install it via platform-tools provided by Android studio.
The cable. Using a micro-usb cable to connect the voxl-cam doesn't work every time, is recommended to use a usb 3 data cable to connect via this usb port.

Once we follow all these, is working fine in all the environments : windows, wsl / ubuntu 20, and mac os

Thanks for your help!

tom

@marian This is some really good information, thank you so much for your findings!

Bright Nnadi

@marian Please I am having the same issue you had with ADB here. I installed ADB with Ubuntu but it I don't think it worked because its not Detecting my VOXL CAM yet.

marian

@Bright-Nnadi Hi, did you install ubuntu on windows and using via wsl, or you have a linux machine with ubuntu installed that you use?

Bright Nnadi

@marian i just installed ubuntu on windows but not via wsl

marian

@Bright-Nnadi I understand. I followed the steps below and it works fine for me, I hope that will help you too.

Installation steps :
Install ADB for windows
Install adb for ubuntu.

Check the version on both systems. On ubuntu, if using apt will install an older version than Windows, so should install it via platform-tools provided by Android studio

For Using ADB follow the steps below:
a) Run PowerShell in Admin mode, and go to the folder where ADB is located
There tape the command below:
.\adb.exe -a -P 5037 nodaemon server

That should connect and show the devices:
adb.exe I 02-28 17:55:47 13580 13948 adb.cpp:171] c6f37030: already offline

N.B.: The first time we run it, it will open a security window to give it access through the Firewall. Select the both, local and public network. It is needed to access the device through WSL (see step below).

Into another PowerShell window can connect to the device via .\adb.exe shell

b) on Ubuntu client :

Take the IP address of the WSL from the windows station:
ifconfig -> for me is something like 172.23.0.1 …

Look into the /etc/resolv.conf => there should be the address below, if not change it to this one

Run the command:
adb -H 172.23.0.1 -P 5037 devices

That should allow you to connect to adb device from Ubuntu client on Windows.