Problem running RX888

[John Ackermann N8UR]

On a freshly installed ka9q-radio on a new (used) machine, I'm getting
an error at startup. All the console output is below, but the key is:

No rx888 data for 5 seconds, quitting
Transfers completed
rx888 has aborted, exiting radiod

I haven't seen this before. There's no further info in /var/log/syslog.
The hardware is a Lenovo tiny PC with i5-8750T and one USB3 5GB hub.
Nothing else is plugged in to USB.

(I'm also seeing "local name collision" messages but I don't think they
are related to this issue, as I see them on other systems with recent
ka9q-radio installs that seem to be working properly.)

Any suggestions what the issue might be?

Thanks,
John

====
jra@n8ur-tc-2:/etc/radio$ radiod /etc/radio/rad...@rx888-web.conf
KA9Q Multichannel SDR main.c last modified Thu Jan 2 20:30:56 2025
Copyright 2023, Phil Karn, KA9Q. May be used under the terms of the GNU
Public License
Loading config file /etc/radio/rad...@rx888-web.conf...
found rx888 vendor 04b4, device 00f1, manufacturer 'sdr prototypes',
product 'RX888mk2', serial '0009090602532B1A', selected
rx888 USB speed: Super (5 Gb/s)
Failed to add service: Local name collision
Failed to add service: Local name collision
Nominal samprate 64,800,000, reference 27,000,000.000000, feedback
divisor 28 + 4/5, VCO 777,600,000.000000, integer divisor 12 * 1, output
= 64,800,000.000000
Output divider 12 + 0/1, rdiv 1, actual samprate = 64,800,000.000000
rx888 VHF: rx888 reference 27,000,000.0 Hz, nominal sample rate
64,800,000 Hz, actual 64,800,000.000 Hz (synth err 0.000 Hz; 0.000 ppm),
AGC on, requested gain 10.0 dB, actual gain 10.0 dB, atten 0.0 dB, gain
cal -1.4 dB, dither 0, randomizer 0, USB queue depth 16, USB request
size 32 * pktsize 16,384 = 524,288 bytes (0.00404543 sec)
Established under name 'web-pcm.local'
Established under name 'web-pcm.local'
fftwf_import_system_wisdom() succeeded
fftwf_import_wisdom_from_filename(/var/lib/ka9q-radio/wisdom) succeeded
rx888 running
0 total demodulators started
Failed to add service: Local name collision
Established under name 'web.local'
No rx888 data for 5 seconds, quitting
Transfers completed
rx888 has aborted, exiting radiod

[John Ackermann N8UR]

After a couple of reboots this problem seems to have cleared up. I
still don't know what caused it, but I suspect something sitting on the
USB device was keeping radiod from reading it.

On 1/2/25 15:40, John Ackermann N8UR wrote:
> On a freshly installed ka9q-radio on a new (used) machine, I'm getting
> an error at startup.  All the console output is below, but the key is:
>
> No rx888 data for 5 seconds, quitting
> Transfers completed
> rx888 has aborted, exiting radiod
>
> I haven't seen this before.  There's no further info in /var/log/syslog.
> The hardware is a Lenovo tiny PC with i5-8750T and one USB3 5GB hub.
> Nothing else is plugged in to USB.
>
> (I'm also seeing "local name collision" messages but I don't think they
> are related to this issue, as I see them on other systems with recent
> ka9q-radio installs that seem to be working properly.)
>
> Any suggestions what the issue might be?
>
> Thanks,
> John
>

[Tom McDermott]

Hi John - I have seen the RX888 not correctly initialize a few times. For me, unplugging the RX888 USB

connection, then re-plugging cleared the issue, and another time rebooting cleared the issue.

If I use the radio command to start the RX888 in a shell  (as opposed to systemctl) and the RX888 hangs on

initialization, then after stopping radiod there can be up to 6 processes hung. After individually killing those

processes everything came up correctly the next command attempt.

It smells like a USB init failure.

-- Tom, N5EG

--
You received this message because you are subscribed to the Google Groups "ka9q-radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ka9q-radio+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ka9q-radio/3ec9266b-b778-488e-ad23-ca7eec1926cc%40febo.com.
For more options, visit https://groups.google.com/d/optout.

[Phil Karn]

If the hung processes you're talking about are the avahi-publish tasks,
I recently reordered the startup operations in main.c to not start them
until the hardware has successfully initialized. I did it for just this
reason.

Phil

[Phil Karn]

The local name collision messages are almost certainly normal. They
happen when two hosts publish the same service or IP address on
multicast DNS using avahi-publish. There's no problem as long as they're
all publishing the same things, which is common when you have several
copies of radiod feeding the same multicast groups.

I do wish I could quiet down the avahi-publish commands without turning
off true errors.