GPS message source block initializes a new multi-USRP object, which can affect any previously-initialized multi-USRP or RFNoC-API connections to the same USRP.
For example, if a Tx or Rx streamer has been set up and connected to a specific RFNoC block, that same streamer will still work after initialization of the GPS message source, but attempting to disconnect it will result in an error. (Error message: "Attempting to disconnect output port 0, which is not registered as connected.")
The reverse does not currently hold true; if the USRP GPS message source is initialized before any other USRP blocks, its functionality is not affected since it only queries the underlying GPS object for certain parameters.
Possible fixes include:
Passing into the message source block a reference to an existing USRP object.
Providing callbacks into the GPS message source block for accessing the three relevant properties in the USRP property tree: gps_time, gps_locked, and gps_gpgga.
GPS message source block initializes a new multi-USRP object, which can affect any previously-initialized multi-USRP or RFNoC-API connections to the same USRP.
For example, if a Tx or Rx streamer has been set up and connected to a specific RFNoC block, that same streamer will still work after initialization of the GPS message source, but attempting to disconnect it will result in an error. (Error message: "Attempting to disconnect output port 0, which is not registered as connected.")
The reverse does not currently hold true; if the USRP GPS message source is initialized before any other USRP blocks, its functionality is not affected since it only queries the underlying GPS object for certain parameters.
Possible fixes include: