OP25 OP25 persistent error

ewh01

Member
Premium Subscriber
Joined
Jul 9, 2006
Messages
57
Location
vineland, nj
I am running boatbod OP25, starting via ./rx.py. It will run for a while, but at random times it will lock up, each time the stderr file shows the error below

cb transfer status: 5, canceling...
rtlsdr_read_async returned with -5
04/11/24 22:21:34.293170 UI Timeout
04/11/24 22:21:44.306421 UI Timeout
04/12/24 03:21:40.543843 UI Timeout
04/12/24 03:21:46.553775 UI Timeout
04/12/24 07:21:44.473553 UI Timeout
04/12/24 07:21:57.488033 UI Timeout
main: exception occurred
main: exception:
Traceback (most recent call last):
File "/home/******************/op25/op25/gr-op25_repeater/apps/./rx.py", line 1021, in run
time.sleep(1)
KeyboardInterrupt

Does anyone know what is going on and/or how to fix this?

Thanks
 

wgbecks

Active Member
Joined
Jan 17, 2005
Messages
1,035
Location
NE Wisconsin
It looks like a loss of USB connectivity with your SDR dongle. Check that your SDR's USB connections are mechanically and electrically secure and don't overlook the SDR itself or a faulty USB hub or extension cable(s) if used.
 

ewh01

Member
Premium Subscriber
Joined
Jul 9, 2006
Messages
57
Location
vineland, nj
OK, I'll try a different USB port.

It just happened again, and I got the following from running tail -f

04/12/24 11:56:26.502804 voice update: tg(5261), freq(769781250), slot(1), prio(3)
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
cb transfer status: 5, canceling...
rtlsdr_read_async returned with -5
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,417
Location
Talbot Co, MD
Those are definitely errors that you see when the rtl driver looses contact with the hardware device. I've seen it happen under several different conditions:
- RPI with inadequate power supply (low voltage)
- RTL with intermittent USB connector (i.e. a physical issue)
- RTL device going bad (i.e. an electrical issue)
 

ewh01

Member
Premium Subscriber
Joined
Jul 9, 2006
Messages
57
Location
vineland, nj
Those are definitely errors that you see when the rtl driver looses contact with the hardware device. I've seen it happen under several different conditions:
- RPI with inadequate power supply (low voltage)
- RTL with intermittent USB connector (i.e. a physical issue)
- RTL device going bad (i.e. an electrical issue)

Looks like it's time for a new dongle!!

Thanks folks!!
 
Top