On Thursday, 29 August 2024 14:27:05 EEST you wrote:
Yes initial thought: I must have blown the pa.
But page 7 of 9 in this pdf
matic_revd_0.1.pdf seems like there is nothing active after the 936x ?
Same measure method, being ft8 tone tune from wsjtx on an old HackRF gives
+4.5dBm. This value is enough to drive cheap aliexpress PA and make
contacts over QO100
Poking the -89 value to 0 did not change a thing:
leo@ptr-1w3hb1:~> iio_attr -v -a ip:usb -c ad9361-phy -o voltage0
hardwaregain 0 Using auto-detected IIO context at URI "usb:3.41.5"
dev 'ad9361-phy', channel 'voltage0' (output), attr 'hardwaregain', value
'0.000000 dB' wrote 2 bytes to hardwaregain
dev 'ad9361-phy', channel 'voltage0' (output), attr 'hardwaregain', value
'0.000000 dB'
Wonder if connecting the u.fl for the second TX from the Pluto would make a
chance?
Leo/on1aad
If you are using audio from another application piped into qradiolink, there
is a chance that the input audio level does not have the desired value and is
causing the issue. I would be helpful to describe the audio pipe setup.
Before doing anything to you device, measure the output power of the ADALM-
Pluto at that frequency using a constant envelope carrier transmission, like
the FM, M17 or any of the FSK RRC modes. For one of my devices I get -0.49 dBm
on FM and 0.55 dBm for the M17 modem at 2400 MHz, all at maximum gain. The
small differences to the values stated in the datasheet are due to not using
the maximum DAC range of -1.0 to 1.0 to avoid waveform clipping (not just on
the ADALM-Pluto but also on the USRP and other devices).
So you should be able to obtain at least -1 dBm of power from it.
Adrian
