Open guruofquality opened 8 years ago
The work around that I have used is to attribute a fixed IP address to the redpitaya (using the router DHCP server and the MAC address of the RP) and hard the SoapyRedpitaya.cpp file with that static IP address.
/***********************************************************************
* Device interface
**********************************************************************/
class SoapyRedPitaya : public SoapySDR::Device
{
public:
SoapyRedPitaya(const SoapySDR::Kwargs &args):
_addr("192.168.0.100"), _port(1001)
{
Red pitaya doesnt advertise any service on mdns does it? You dont happen to see it show up in mdns-scan
or something like that.
Or maybe it could just be added to the redpitaya since its just embedded linux: https://linux.die.net/man/5/avahi.service
I was thinking another thing that could help is if the module supported looking at a particular environment variable for the address.
It's possible to advertise the SDR transceiver application via Avahi when the application is running on the Red Pitaya board.
There currently isnt a way to discover RedPitayas on a local network. Some drivers require that the user explicitly enter the IP address (Ex addr=192.168.10.100). I put this issue here because it may be worthwhile to implement a discovery multicast/broadcast discovery protocol. Example SSDP: https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol Also, there may be some existing service to run on the RedPitaya size like avahi.