Search the Community
Showing results for tags 'api v2.4'.
Found 2 results
-
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 2.4.6.13.
-
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?