Qualcomm RB5 - Remote ID
-
Good afternoon, I have been trying to get the remote ID to work on RB5. I followed the steps in the technical document, and everything was working well until I had to check voxl-remote-id status. I end up getting something like this which is in the technical document. My device is already in SoftAP mode.
voxl:/$ systemctl status voxl-remote-id
voxl-remote-id.service - voxl-remote-id
Loaded: loaded (/usr/bin/voxl-remote-id; enabled; vendor preset: enabled)
Active: active (running) since Thu 1970-01-01 02:19:30 UTC; 52 years 9 months ago
Main PID: 2447 (voxl-remote-id)
CGroup: /system.slice/voxl-remote-id.service
āā2447 /usr/bin/voxl-remote-idJan 01 02:19:30 apq8096 systemd[1]: Started voxl-remote-id.
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Remote ID SN: 1814C4056553343
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null)
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null)
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null)
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null)
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null)
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null)
Jan 01 02:19:31 apq8096 voxl-remote-id[2447]: INFO: Attempting to Connect to hostapd: /data/misc/wifi/hostapd/(null) -
Is there any solution or feedback to the above problem.
-
@doe43john77 It's acting like the softap mode didn't get setup correctly. Are you able to connect to the drone over WiFi? Is there anything in the directory
/data/misc/wifi/hostapd
? -
@Eric-Katzfey Yes, I am able to connect the drone over WiFi.
-
@Eric-Katzfey Also isn't hostapd a conf. file
-
@doe43john77 Here's what I have:
voxl2-mini:/$ cd /data/misc/wifi/ voxl2-mini:/data/misc/wifi$ ls hostapd hostapd.conf wlan_mode wpa_supplicant.conf voxl2-mini:/data/misc/wifi$ ls -l total 80 drwxr-x--- 2 root root 4096 Jun 29 15:56 hostapd -rw-r--r-- 1 root root 66860 Jun 29 15:56 hostapd.conf -rw-rw-rw- 1 root root 8 Jun 29 16:18 wlan_mode -rw-r--r-- 1 root root 444 Jun 29 16:18 wpa_supplicant.conf voxl2-mini:/data/misc/wifi$ cd hostapd voxl2-mini:/data/misc/wifi/hostapd$ ls wlan0 voxl2-mini:/data/misc/wifi/hostapd$ ls -l total 0 srwxrwx--- 1 root root 0 Jun 29 15:56 wlan0 voxl2-mini:/data/misc/wifi/hostapd$
-
@Eric-Katzfey This is what i have when I do what you did above. I add the hostapd into the directory and copied the hostapd.conf into the hostapd directory.
rb5:~$ cd /data/misc/wifi/
rb5:/data/misc/wifi$ ls
hostapd hostapd.conf wpa_supplicant.conf
hostapd-wlan1.conf sta_mode_hostapd.conf
hostapd-wlan2.conf wlan_mode
rb5:/data/misc/wifi$ ls -l
total 284
drwxr-xr-x 2 root root 4096 Jun 30 16:23 hostapd
-rw-r--r-- 1 root root 66929 Oct 13 2022 hostapd-wlan1.conf
-rw-r--r-- 1 root root 66929 Oct 13 2022 hostapd-wlan2.conf
-rw-r--r-- 1 root root 66928 Jun 30 18:31 hostapd.conf
-rw-r--r-- 1 root root 66927 Oct 13 2022 sta_mode_hostapd.conf
-rw-rw-rw- 1 root root 7 Jun 30 18:31 wlan_mode
-rw-r--r-- 1 root root 234 Jun 30 18:31 wpa_supplicant.conf
rb5:/data/misc/wifi$ cd hostapd
rb5:/data/misc/wifi/hostapd$ ls
hostapd.conf
rb5:/data/misc/wifi/hostapd$ ls -l
total 68
-rw-r--r-- 1 root root 66928 Jun 30 16:11 hostapd.conf
rb5:/data/misc/wifi/hostapd$ -
@doe43john77 Checking for an update
-
@Eric-Katzfey what needs to be contained in the wlan0 file
-
@doe43john77 I was able to recreate the issue and we are working on a solution
-
@tom Good morning, is there an update on the solution.
-
@doe43john77 It's on our list, but no movement yet
-
@tom Good morning any updates on the Remote ID
-
@doe43john77 It's probably going to be a couple of weeks before we can provide something.
-
@Eric-Katzfey Good morning, Is there any update on Remote ID? Thank you!
-
@doe43john77 No, sorry, it's on our list for the next release but we haven't had a chance to look at it yet
-
@doe43john77 A fix has been put in place in voxl-remote-id v0.0.9