Jump to content

Search the Community

Showing results for tags 'wbtapi'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • QRC General
    • General Discussion
    • Question and Answer
  • QRC Products
    • Wide Band Transcorder
    • Surveyor and ICS
    • QSAK (Phone Tools)
  • Group Boards

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Found 5 results

  1. Does this currently exist API for the WBT that will allow it to transmit directly from an IQ data stream? There is a way to playback a file that would technically be transmission, but is there a way to directly transmit from a stream? If not, the intended way of handling it would be to write a file (or series of files) to be played back by the WBT. The files would be short packets of IQ data and would be used to transmit IQ data from a GRC flowchart. Would the Transmit function of the WBT be too slow for this method to be feasible? There would be two files, one being read by the wbt and the other being written by (a GNURADIO-Companion flowchart>. At the end of reading the file being transmitted, the flowchart app would then clear the file, and write the next packet of data to be transmitted. The WBT would go to read the other file. It it essentially a buffer system, feed in the data on one end, read out on the other.
  2. Let me describe the issue that I have. There is a file which contains data from both tuners and TunerA sample rate is 42 MS/s and TunerB is 13.3 MS/s. The app dumps the processed packets number and encountered metadata (WbtVRTFileReadIterator::getCurrentMetadataAsJSON) to debug output. I start processing TunerA data. The first metadata has "GPS Fix UTC Seconds" value of 1446218004. By the time app processed 815M samples (which should constitute approx. 19 seconds of data) the metadata timestamp is 1446218019 - only 15 seconds later than the starting value. The difference is even bigger in case of TunerB. After processing 250M samples (~18 sec.) the metadata timestamp is 1446218009 - moved forward by only 5 sec. What is happening here and is it the expected behavior?
  3. Something must have changed in recent firmware update because now the API rejects the tuner change if the sample rate is more than 42. So, if I set the bandwidth to more than 37.8 MHz (acceptable value) then the calculated sample rate is more than 42 (unacceptable value) and WbtSystem.updateTunerSettings() returns false. Do I have to manually limit the sample rate from now on or is this a temporary development? Can I rely on getMaxBandwidth or rather hardcode it to 42? API version is
  4. In WBT v2.4 there is this new feature that the tuner span can be set to some arbitrary value (instead of a predefined list). For this there are WbtCommon::Data::RadioFrontend::getMinBandwidth() and WbtCommon::Data::RadioFrontend::getMaxBandwidth() methods. Currently they return values 0.7 and 42. However, in the Session screen of the WBT device the threshold at which the tuner config is switched to "Combined" is 40Mhz. The app has a screen similar to the Session screen and has to mimic its behavior. What is the proper way to determine when the tuners have to be combined/uncombined?
  5. question #1: What is the difference between Partial and Full sweeps (pertaining to WbtApi::WbtSweeper::setSweepPartiallCompletionCallback and WbtApi::WbtSweeper::setSweepCompletionCallback question #2: When would i want to use one versus the other?