开云体育

On Monday, 9 September 2024 08:28:35 EEST you wrote:

But, In the computer of sender, it shows an errror:CameraBin
warning:”Resource busy or not available”;

That is a message from GStreamer, not qradiolink. You can safely ignore that
message if the camera works. From what I can tell, GStreamer tries to claim
the camera interface twice.

In the computer of receiver, it
shows :"ALSA lib pcm.c:8526:(snd_pcm_recover) underrun occurred“ &

Yes well, ALSA is notoriously difficult to configure to avoid underruns and
overrruns. You would not see that message with Pulseaudio. But if the audio is
fine otherwise, just ignore the message. If not, try to configure ALSA for your
user or switch to Pulseaudio. These days there are very few distros not using
it.

[Warning] Video CRC check failed,dropping frame. Have you encountered

these

situations before?

The RF channel is not a perfect information transfer channel. You can have bit
errors caused by weak signal or interference, and those frames which fail CRC
validation will not be displayed. Increase the signal quality to avoid CRC
errors.

In addition, There is no Time Domain Tab in the GUI, I
use the version of qradiolink-0.8.13-2.

Time domain display is released in version 0.9.0

Hi, Adrian M
Thanks very much for your reply!
I have tested successful with model of "Video QPSK 250K".
But, In the computer of sender, it shows an errror:CameraBin warning:”Resource busy or not available”; In the computer of receiver, it shows :"ALSA lib pcm.c:8526:(snd_pcm_recover) underrun occurred“ &
[Warning] Video CRC check failed,dropping frame. Have you encountered these situations before?
In addition, There is no Time Domain Tab in the GUI, I use the version of qradiolink-0.8.13-2.

On Wednesday, 4 September 2024 04:32:14 EEST you wrote:

Is it necessary to set up Mumble server or UDP Streaming?

No, the video mode is radio only. You only need to select it for
both TX and RX, enable TX and RX and press PTT to transmit.

Also, if you have Pulseaudio on you machine, you need to select
the Pulseaudio sinks and sources in the settings. Not using them
will lead to transmission and reception interruptions, and the
signal may be impossible to demodulate.

Is it necessary to set up Mumble server or UDP Streaming?

as the title.

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

Yes initial thought: I must have blown the pa.

But page 7 of 9 in this 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

Version 0.9.0-1 of QRadioLink is now available as source packages.

Changelog:
* Added configurable time domain display
* Added UDP to ZeroMQ proxy (enables SVXLink audio as one of the FM carriers
in MMDVM-multi mode)
* FM is now one of the modes supported by MMDVM-multicarrier


SVXLink-related changes: you can now add a single FM repeater channel in the
multi-carrier transceiver mode.
You will need to set the configuration option *zmq_proxy_channel* to the
relevant FM channel number (should never be channel 1, so the value goes from
2 to 7).

To use the FM carrier with svxlink, start the application using the following
CLI parameters:
$ qradiolink --mmdvm --udp
Then configure svxlink to send audio via UDP to and from the ports configured in
qradiolink.
When combining MMDVM-SDR with this new functionality, you will need to not
start at all the MMDVM instance for the channel number configured here,
otherwise the new functionality will not work.

What this means is that now you can directly mix FM with DMR, YSF or M17 on
your multi-carrier base-station (at the moment only one channel). Note that
other applications can also provide audio via UDP as well, so feel free to
experiment with this functionality.
The documentation will soon be updated with this information.

In the future, we are looking at the possibility of implementing an MPT1327
analog trunking base station with svxlink as a network back-end. If you are
interested in making this happen and want to contribute, contact me via this
mailing list.

Adrian

On Wednesday, 28 August 2024 17:00:00 EEST you wrote:

Measure with Ultra Tiny SA gives 4.5dBm for HackRF versus -22 dBm for Adalm
Pluto on 2400MHz.

When QRadioLink is off, I can question the Pluto:

iio_attr -v -a ip:usb -c ad9361-phy -o voltage0 hardwaregain
Using auto-detected IIO context at URI "usb:3.41.5"
dev 'ad9361-phy', channel 'voltage0' (output), attr 'hardwaregain',
value '-89.000000 dB'

What was your measurement procedure?
Did you use a constant envelope carrier?

You should be seeing anything between 0 and 4 dBm on the ADALM-Pluto output at
that frequency and maximum gain. Check the Analog Devices datasheets.
Unless your measurement procedure was wrong, the PA is probably gone.

Measure with Ultra Tiny SA gives 4.5dBm for HackRF versus -22 dBm for Adalm Pluto on 2400MHz.

When QRadioLink is off, I can question the Pluto:

iio_attr -v -a ip:usb -c ad9361-phy -o voltage0 hardwaregain
Using auto-detected IIO context at URI "usb:3.41.5"
dev 'ad9361-phy', channel 'voltage0' (output), attr 'hardwaregain', value '-89.000000 dB'

SoapySDRUtil --probe="driver=hackrf"

---------------------------------------------------
-- TX Channel 0
----------------------------------------------------
Full-duplex: NO
Supports AGC: NO
Stream formats: CS8, CS16, CF32, CF64
Native format: CS8 [full-scale=128]
Stream args:
* Buffer Count - Number of buffers per read.
[key=buffers, units=buffers, default=15, type=int]
Antennas: TX/RX
Full gain range: [0, 61] dB
VGA gain range: [0, 47, 1] dB
AMP gain range: [0, 14, 14] dB
Full freq range: [0, 7250] MHz
RF freq range: [0, 7250] MHz
Sample rates: 1, 2, 3, 4, 5, ..., 16, 17, 18, 19, 20 MSps
Filter bandwidths: 1.75, 2.5, 3.5, 5, 5.5, ..., 14, 15, 20, 24, 28 MHz

The VGA and AMP do appear as rotation tune knobs in the QRadioLink gui

Better tx pluto results on 23cmm stronger signals.

On V and UHF I connected a CN103 Diawa meter, but scale is 20 Watt, so needle did not move.

Installing soapysdr0.8-module-hackrf made the hackrf detectable in QRadioLink,
so I can now test one software, 2 different hardwares ...

Stays fun!

On Monday, 12 August 2024 17:54:33 EEST you wrote:

QradioLink and Adalm Pluto certainly does some tx on 70cm.
Hardly moves the signal meter on the rx ham gear, but things like the
QradioLink roger beep is clearly audible. In tx ssb I can hear my voice.

Depending on how close is your antenna, that may not be normal.
I am able to open a local FM repeater almost full quieting without even
using an external PA stage on the Pluto (2 dBm output in the 70 cm
band). I would double check the RF and audio gain settings if I were you.

Otherwise, measurement of the transmit power is really required, and for
the kinds of power these SDR devices can output, there are plenty of very
cheap digital power meters that can tell you the signal level with 0.1 dB
precision, with or without included attenuators.

Consider that these SDR devices are really just waveform generators,
there is a lot of RF engineering involved to get a functional amateur radio
station out of them. Signal characterization, filtering for spurious output,
band-pass filtering the RX input, matching the drive input to an external
PA to avoid over-driving, compression and distortion, and the list goes on.

Adrian

QradioLink and Adalm Pluto certainly does some tx on 70cm.
Hardly moves the signal meter on the rx ham gear, but things like the QradioLink roger beep is clearly audible.
In tx ssb I can hear my voice.

I did play around on 23 and 70CM, my ham gear could hear the pluto TX.

Maybe I should try to open local reapeater as proof of concept.

On Monday, 12 August 2024 17:01:17 EEST you wrote:

[image: image.png]

I try to tx ft4/ft8 via a pluto.

Transmit Wsjtx audio via Sdrangel and Hackrf I can drive a PA and

make some

contacts, while using QRadioLink and Pluto as receiver on 433 MHz.

TX and RX device args in QRadioLink are
soapy=0,device=PlutoSDR,driver=plutosdr,label=PlutoSDR#0usb:

3.28.5,uri=usb:3

.28.5

Would it make sense to try to get HackRF as TX advice? It does not

show

op, but maybe with some soapy drivers and settings ...

Unless Soapy finds it (if you have installed the module), direct support
via gr-osmosdr requires some device string like "hackrf=0". I myself
don't know, since I don't own such a device, but have heard it from
other users. Beware the HackRF is not full duplex so you can't enable TX
and RX simultaneously on it.

End goal should be TX with Pluto.
Audio level meter in the screenshot above indicates the audio does

arrive

in QRadioLink. PTT is pressed, TX freq 2400 MHz.

I have the idea there is some TX level config missing or too low, and

do

not have access to SHF power meter.

It's not clear to me what the problem is with Pluto TX. Have you tried it
on another band like 70 cm before and it didn't work? If so, what was
the issue?

Adrian

[image: image.png]

I try to tx ft4/ft8 via a pluto.

Transmit Wsjtx audio via Sdrangel and Hackrf I can drive a PA and make some
contacts, while using QRadioLink and Pluto as receiver on 433 MHz.

TX and RX device args in QRadioLink are
soapy=0,device=PlutoSDR,driver=plutosdr,label=PlutoSDR#0usb:3.28.5,uri=usb:3.28.5

Would it make sense to try to get HackRF as TX advice? It does not show
op, but maybe with some soapy drivers and settings ...

End goal should be TX with Pluto.
Audio level meter in the screenshot above indicates the audio does arrive
in QRadioLink. PTT is pressed, TX freq 2400 MHz.

I have the idea there is some TX level config missing or too low, and do
not have access to SHF power meter.

All hints welcome!
73 de on1aad

Nope. My DP4801e and SL4000e got Capacity Max and CapMax Advantage licenses active + I have Capacity Max Radio Manager software.

You can not identify presence of Capacity Max entitlement. And it's pretty expensive.
Also, you can not program those with CPS2, you need CapMax RM, which is really hard to obtain.

On Sunday, 11 August 2024 12:00:28 EEST you wrote:

Hello,

can anyone shed some light on how to identify Tier III compatible
Motorola radios?

What Motorola radios would be recommended for dmrtc?

On Hypera it's the SW00029 license, can be checked in the CPS in
Common/Feature Control, item "DMR Trunking".

73 Christian DB9CR

Hi Christian,

I don't have any Motorola radios, but the R7 seems to be everywhere nowadays,
it supports Tier III from what I can tell, and you can easily find it in DL.
The licensing model is a big headache with Motorola, it has separate licenses
for even minor features, and also the fact that trunking is most often
advertised as Capacity Max (Capacity Plus is something else altogether), but
not which features are Motorola proprietary and which features are standard
tier III.

I always look at the radio datasheet and search for mention of TS 102 361 -4
But it seems like some Motorola radios don't even mention this standard in the
datasheet but support parts of it nevertheless, like the DP4801e

From whatever info I could gather in public postings, these are the major
manufacturers of DMR trunking radios:
Motorola, Hytera, Tait, Kenwood, Simoco

Anyone who can shed more light here is welcome to add more info.

Adrian