OP25 OP25 - SDR bug

Status
Not open for further replies.

MTL_Emergencies

Member++
Database Admin
Joined
Sep 6, 2019
Messages
147
Location
Quebec, Canada
Hello all,
I am running OP25 on a Pi 3B and sometimes OP25 bugs.
I was able to catch that in the stderr file this is what I found:
Code:
09/23/23 17:23:10.515841 [0] releasing:  tg(50003), freq(772.256250), slot(1), reason(duid15)
09/23/23 17:23:11.738840 [0] voice update:  tg(50003), rid(0), freq(772.256250), slot(1), prio(4)
09/23/23 17:23:16.910174 [0] releasing:  tg(50003), freq(772.256250), slot(1), reason(duid15)
09/23/23 17:23:19.373668 [0] voice update:  tg(60051), rid(0), freq(770.756250), slot(0), prio(2)
09/23/23 17:23:24.162689 [0] releasing:  tg(60051), freq(770.756250), slot(0), reason(duid15)
09/23/23 17:23:27.989593 [0] voice update:  tg(50001), rid(0), freq(772.006250), slot(0), prio(4)
09/23/23 17:23:39.305234 [0] releasing:  tg(50001), freq(772.006250), slot(0), reason(duid15)
cb transfer status: 1, canceling...
rtlsdr_read_async returned with -5
09/23/23 17:38:23.006066 UI Timeout

It seems to be an error with the rtl-sdr device.
Does anyone know what is causing the error and how to solve that?
Thanks
 

wgbecks

Active Member
Joined
Jan 17, 2005
Messages
1,027
Location
NE Wisconsin
Check the dmesg log and look for USB disconnect messages as confirmation of a loss of communications with the SDR. Look for
under-voltage detected warnings.

The "cb transfer status: 1, canceling..." and "rtlsdr_read_async returned with -5" messages in your log suggest an error condition
with communications to/from the RTL-SDR device. Check that the RTL is firmly seated in the USB connector, try a different USB port,
discontinue use of or replace any USB extension cables, verify the power source feeding your Pi and the SDR have an adequate current
rating, or try replacing the SDR itself with another device.
 
Last edited:

boatbod

Member
Joined
Mar 3, 2007
Messages
3,411
Location
Talbot Co, MD
Unfortunately this is not a bug, but indicative of a hardware failure where the kernel has lost contact with the USB device. If it's a transitory issue (e.g. loose connection) you can simply restart op25 and resume operations, but other times it may be bad hardware or inadequate power supply.
 
Status
Not open for further replies.
Top