Remote ID Invalid - Is an updated script available?
-
The Serial Number generated via remote-id considered invalid when attempting to register with FAA. Currently using starling 2 max running 1.6.4~beta4.
Referencing other messages, appears that the serial generated hard codes length character as C, which would require 12 digits. Since actual serial is 10 digits, it should be A.
Has there been any updates to scripts to correct this?
-
@JB1 Yes, you are correct. It has been updated to use the 10 character ID. You can find the updated package here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-remote-id_0.1.0-202605281019_arm64.deb
-
@JB1 FYI: The code repo is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-remote-id. You can see my commits on the dev branch.
-
@Eric-Katzfey thank you!
-
@Eric-Katzfey appreciate the help. related questions.
when starting up the voxl-remote-id service, noticing that hostapd was not connecting. identified that it was inactive, so started it, with no luck. for reference, using the m0213 botsunlimited sparrow.
traced the following:
- In the hostapd.conf file, it operates at 5Ghz (hw_mode=a) and at channel 149. is this expected? Should remote-id operate at 2.4Ghz (hw_mode=g, channel=6)?
- noticed there is nothing telling hostapd to create a socket directory, added ctrl_interface=/data/misc/wifi/hostapd
Added those changes, and now remote-id successfully connects to hostapd, mavlink-server, and can enter active mode
However, that identified some other items during troubleshooting:
- when attempting to register drone with FAA - receive invalid serial number - is there specific format that you register drones with faa?
- /persist partition on /dev/sda2 has a bad superblock or wrong filesystem type - it fails each time - without persist, RTC doesn't save and resets every reboot - is that expected behavior?
- wifi does not reinitialize on soft reboot - requires a full power cycle
-
@JB1 I'll look into your questions. There is no RTC on VOXL2.
