sdrtrunk and adrspy

[ForeignStatic]

I'm trying to set up SDRTrunk 6.0 and SDRSharp at the 90066 zip code. As a test, I'm using CRIS and ICI trunks with sites near this zip code. The attached pic1 shows the settings for ICI. When I run it, I can see the control channel being active, and I see channel activity in the waterfall view, but nothing appears in the "Now Playing" window (see attached pic2). I had the opportunity to test this hardware setup with one of the trunks in TX, and it worked right out of the gate. But when I moved to the new zip code, it started behaving the way I reported. I would greatly appreciate any help in figuring out what I'm doing wrong.

 

[maus92]

First I would use the latest release version of SDRT. Second how busy is the Culver City site and how many of the tgs carried on it are encrypted? I know that the LA area has several systems that use frequencies in the T band, so the waterfall may be displaying activity on unrelated systems.

 

[RMason]

Although the screenshot shows that SDRTrunk has found the control channel, the Details tab is not populated with the information about the system from the control channel. I suspect that SDRTrunk is not decoding the control channel. How strong is the control signal on your waterfall? (It looks like the control channel that SDRTrunk is locked on is 482.2625) Do you get any messages in the Messages tab or the console window?

 

[ForeignStatic]

First I would use the latest release version of SDRT. Second how busy is the Culver City site and how many of the tgs carried on it are encrypted? I know that the LA area has several systems that use frequencies in the T band, so the waterfall may be displaying activity on unrelated systems.

Thank you, I'm running 0.6.0. After looking into the messages view I believe that I have hardware problem. Will provide more details in the response for next comment.

 

[ForeignStatic]

Although the screenshot shows that SDRTrunk has found the control channel, the Details tab is not populated with the information about the system from the control channel. I suspect that SDRTrunk is not decoding the control channel. How strong is the control signal on your waterfall? (It looks like the control channel that SDRTrunk is locked on is 482.2625) Do you get any messages in the Messages tab or the console window?

Although the screenshot shows that SDRTrunk has found the control channel, the Details tab is not populated with the information about the system from the control channel. I suspect that SDRTrunk is not decoding the control channel. How strong is the control signal on your waterfall? (It looks like the control channel that SDRTrunk is locked on is 482.2625) Do you get any messages in the Messages tab or the console window?

Thanks for pointing toward right direction. I think I have a hardware problem.

This is what I see in the messages view:

2024:09:09 15:51:00 APCO-25 0 <-> SYNC LOSS - BITS PROCESSED [1570]
2024:09:09 15:51:00 APCO-25 0 <-> SYNC LOSS - BITS PROCESSED [1570]
2024:09:09 15:51:00 APCO-25 0 <-> SYNC LOSS - BITS PROCESSED [1570]
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK3**CRC-FAILED** VENDOR:V191 UNRECOGNIZED OSP OPCODE MSG:A5BFD57410001FC8E1E00520
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK3**CRC-FAILED** VENDOR:V168 UNRECOGNIZED OSP OPCODE MSG:5BA800E0A087FED062697AA2
MSG:3E16FDE395DACFF1EAA79487
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK1**CRC-FAILED** ID:1 OFFSET:30000000 SPACING:6250 BASE:2775272170 FDMA BW:12500
2024:09:09 15:50:59 APCO-25 0 <-> SYNC LOSS - BITS PROCESSED [526]
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK3**CRC-FAILED** VENDOR:V136 UNRECOGNIZED OSP OPCODE MSG:E18887F902D100D2D11A3981
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK3**CRC-FAILED** VENDOR:MIDLAND UNRECOGNIZED OSP OPCODE MSG:5E803FBF6ABFFFFFFFFB4328
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK2**CRC-FAILED** TO ADDR:1442827 TO ID:12408131 SYSTEM:191 RESPONSE:ACCEPT
2024:09:09 15:50:59 APCO-25 0 NAC:2521 TSBK1 RFSS_STATUS_BCST SYSTEM:2514 RFSS:1 SITE:29 LRA:0 ACTIVE NETWORK CONNECTION SERVICE OPTIONS:[DATA, VOICE, REGISTRATION]


And this what I see in the log file:
20240909 155133.621 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31834] times so far. Transfer buffer holding queue (error/total) [7/8] [172MB/1GB 15%]
20240909 155133.634 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31835] times so far. Transfer buffer holding queue (error/total) [7/8] [189MB/1GB 17%]
20240909 155133.637 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31836] times so far. Transfer buffer holding queue (error/total) [7/8] [197MB/1GB 18%]
20240909 155133.640 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31837] times so far. Transfer buffer holding queue (error/total) [7/8] [204MB/1GB 18%]
20240909 155133.646 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31838] times so far. Transfer buffer holding queue (error/total) [7/8] [221MB/1GB 20%]
20240909 155133.654 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31839] times so far. Transfer buffer holding queue (error/total) [7/8] [230MB/1GB 21%]
20240909 155133.675 [sdrtrunk scheduled thread 3] INFO i.g.d.s.t.u.USBTunerController - Successfully resubmitted previous error USB transfer buffer. Current transfer buffer status (error queue/total available) [6/8] [277MB/1GB 25%]
20240909 155133.675 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31840] times so far. Transfer buffer holding queue (error/total) [6/8] [278MB/1GB 25%]
20240909 155133.677 [sdrtrunk scheduled thread 3] INFO i.g.d.s.t.u.USBTunerController - Successfully resubmitted previous error USB transfer buffer. Current transfer buffer status (error queue/total available) [5/8] [283MB/1GB 25%]
20240909 155133.677 [sdrtrunk USB tuner - bus [1] port [5]] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31841] times so far. Transfer buffer holding queue (error/total) [5/8] [284MB/1GB 26%]
20240909 155133.679 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Attempt to submit USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31842] time(s) so far. Transfer buffer holding queue (error/total) [6/8] [284MB/1GB 26%]
20240909 155133.679 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Attempt to submit USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31843] time(s) so far. Transfer buffer holding queue (error/total) [7/8] [284MB/1GB 26%]
20240909 155133.679 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31844] times so far. Transfer buffer holding queue (error/total) [7/8] [284MB/1GB 26%]
20240909 155133.679 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Attempt to resubmit previous error USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31845] times so far. Transfer buffer holding queue (error/total) [7/8] [284MB/1GB 26%]
20240909 155133.680 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Attempt to submit USB transfer buffer failed with status [LIBUSB_ERROR_BUSY] - this may be temporary and has happened [31846] time(s) so far. Transfer buffer holding queue (error/total) [8/8] [284MB/1GB 26%]
20240909 155133.680 [sdrtrunk scheduled thread 3] ERROR i.g.d.s.t.u.USBTunerController - Maximum USB transfer buffer errors reached - transfer buffers exhausted - shutting down USB tuner [284MB/1GB 26%]
20240909 155133.683 [sdrtrunk cached thread 4] INFO i.g.d.s.t.m.DiscoveredTuner - Tuner Error - Stopping - Airspy USB Bus:1 Port:5 Error: USB Error - Transfer Buffers Exhausted [285MB/1GB 26%]
20240909 155133.684 [sdrtrunk cached thread 4] INFO i.g.d.s.t.m.DiscoveredTuner - Stopping Tuner: Airspy USB Bus:1 Port:5 [285MB/1GB 26%]

 

[maus92]

There is no magical answer for you - just use standard troubleshooting techniques. Recheck your USB cables, use a different USB port on the computer, etc. Interesting messages about opcodes - have you tried your setup on a different system? Is your setup working for anything? I run the nightly build, and I have the 0.6.1 (for RSP1A) and 0.6.0 versions available on the machine - it's possible to have multiple versions installed.

 

[mtindor]

There are unknown opcodes on many systems. Of course, with the CRC-FAIL, I wouldn't put much credence in those particular lines.

Either your USB subsystem can't keep up with the bandwidth of the dongles (which should not be the case but often is the case) or you have other issues with the devices plugged in. Default USB drivers/packages are often known to be problematic. I run mostly Dells. I run all Intel. I always go and download the latest USB drivers the particular USB chipset (which you can find in Device Manager) and install them, replacing any drivers that had been installed during the OS setup or by the manufacturer (Dell). And that has yielded better results 100% of the time.

For instance, my laptop I'm using right now has the Intel C216 USB chipset. I specifically downloaded those drivers from Intel's website for Windows 10 64-bit and installed them. No issues. All USB stuff performed better than it did with OEM drivers from Dell.

So if all else fails, you might want to consider updating your USB drivers. If it breaks your system, that's on you.

 

[ForeignStatic]

There are unknown opcodes on many systems. Of course, with the CRC-FAIL, I wouldn't put much credence in those particular lines.

Either your USB subsystem can't keep up with the bandwidth of the dongles (which should not be the case but often is the case) or you have other issues with the devices plugged in. Default USB drivers/packages are often known to be problematic. I run mostly Dells. I run all Intel. I always go and download the latest USB drivers the particular USB chipset (which you can find in Device Manager) and install them, replacing any drivers that had been installed during the OS setup or by the manufacturer (Dell). And that has yielded better results 100% of the time.

For instance, my laptop I'm using right now has the Intel C216 USB chipset. I specifically downloaded those drivers from Intel's website for Windows 10 64-bit and installed them. No issues. All USB stuff performed better than it did with OEM drivers from Dell.

So if all else fails, you might want to consider updating your USB drivers. If it breaks your system, that's on you.

Thank you mtindor and maus92.

Machine was setup and configured with 0.6.0 by me in TX and tested with GATRRS trunk. Once shipped to LA and connected to the local trunk, it start behaving this way. I can run SDR# and listen to the local LA stations but sdrtrunk stop working. Going to ship HP elitedesk g5 and new sdrspy as replacement - its currently seating on my desk and listening to the whole GATTRS without any issues. My guess - machine with the trouble has USB3 only, when replacement will came with USB2. Will update on the result once replacement is set.

Thanks again for the help!