Rather than developing command line or GUI applications and supporting them for three different operating systems, a browser interface should be all that is required to configure a RFNM device and access browser-based functions (such as the On-Device FFT)
The IP link between device and host computer can happen either via the ethernet connection, or when not available, as a secondary USB function multiplexed at the same time as the other features we need running (Soapy streaming, mostly).
Automatic IP address discovery
Every time the device comes online, it should gather its local IP address and forward it to RFNM's server. RFNM can then update the subdomain allocated to the order number, which will default to the preorder code, to this local IP address.
For example, order number ABC-DEF comes online for the first time via ethernet. DHCP assigns it an address, but the customer doesn't know what this is. Rather than needing to access the leases of the router, the customer can read its emails and discover that abc-def.rfnm.me now points to this local address.
The customer can then change its subdomain from order number to a nickname of choice. The same page at rfnm.me can also help discover local USB IP addresses for which RFNM didn't receive any ping back from the deployed device.
Current development status
No work done yet.