Posts made by JB1

@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

@Eric-Katzfey thank you!

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?

What is the lead time to purchase a M0193 with JR nano bay enclosure? Is there a radio tx controller you recommend pairing with it? thank you!

Modal AI recommends the iFlight Commando 8 Controller programmed with ELRS 3 for the Starlings. While the M0184 ELRS RX is NDAA compliant, the controller is not. Are there any recs that are NDAA compliant?