SR30C Can't get connected to PC

[eddferrell]

So just to report back, I purchased a new DATA cable... No luck. I even installed the software and driver on my Windows 11 work laptop... no luck. It always seems to be "no response from scanner" even when the scanner gets a COM port when I plug it in.
If anyone has successfully connected a Uniden Bearcat SR30C scanner to a PC I would love to know the specific driver and software you used.
Thanks,
Edd

 

[RandyKuff]

This is about the only other thing I could find on this...
This is from over four years ago...

SR30C programming

So the SR30C uses the micro then... Any other cables you have that you can try? No, it doesn't. I suspected that it was a MINI (since that's what the BC125AT, BC75XLT, and BCD325P2 all use) but I wanted to make sure so I downloaded the owners' manual. It's a USB MINI, not micro. The...

forums.radioreference.com

 

[Scan125]

Bit late to this.

I have two users of Scan75 with the SR30C who have communicated with me and have no issues connecting. There are certainly more but as my software does not collect user data I can only see the number of times Scan75 has been downloaded.

For my UBC75XLT on W11 I'm using the Silicon Labs CP210X USB to UART Bridge - V11.4.0.393. Baud rate 57600.

Have you tried using a Terminal Control Program to talk directly to the scanner. A command you can send is MDL to which you should get a response,.

 

[N6JPA]

I have a Uniden Bearcat SR30C. I've installed the drivers and software from Uniden. The PORT (COM4) shows up in DEVICE MANAGER when I connect it to the computer. Neither the Uniden software nor the Scan75 software can find the scanner on COM4 or AutoDetect it. Any suggestions? I've rebooted, uninstalled drivers, and tried 3 different cables, but I'm not sure I'm using the exact cable from Uniden. Is the Uniden cable different from a standard USB "Mini-B"?
Any tips or suggestions would be appreciated.
Thanks, Edd

Is there a setting in the radio scanner to turn on and off the USB connection for data? Earlier Uniden scanners had this option.

 

[eddferrell]

This is about the only other thing I could find on this...
This is from over four years ago...

SR30C programming

So the SR30C uses the micro then... Any other cables you have that you can try? No, it doesn't. I suspected that it was a MINI (since that's what the BC125AT, BC75XLT, and BCD325P2 all use) but I wanted to make sure so I downloaded the owners' manual. It's a USB MINI, not micro. The...

forums.radioreference.com

Bit late to this.

I have two users of Scan75 with the SR30C who have communicated with me and have no issues connecting. There are certainly more but as my software does not collect user data I can only see the number of times Scan75 has been downloaded.

For my UBC75XLT on W11 I'm using the Silicon Labs CP210X USB to UART Bridge - V11.4.0.393. Baud rate 57600.

Have you tried using a Terminal Control Program to talk directly to the scanner. A command you can send is MDL to which you should get a response,.

I downloaded a terminal control program called Putty and when I sent the MDL command it came back with ERR the first time but when I tried again it came back "MDL,SR30C". I guess that means the COM port is working and the scanner answered. When I then go to SCAN75 it says No Scanner found, and when I manually enter COM4 the program says "RC100>Message Sent MDL, response = ERR". Doesn't make any sense to me.

 

[Scan125]

I downloaded a terminal control program called Putty and when I sent the MDL command it came back with ERR the first time but when I tried again it came back "MDL,SR30C". I guess that means the COM port is working and the scanner answered. When I then go to SCAN75 it says No Scanner found, and when I manually enter COM4 the program says "RC100>Message Sent MDL, response = ERR". Doesn't make any sense to me.

Sorry just off to bed UK time.

So far this is really odd. One time the MDL command fails with ERR. Next it comes back with a more intelligent response. Bit like things are not in sync.

Directly after the MDL response you could try Scan75 to see if that now detects your scanner. Also in Scan75 you can force a Port and then use the "R" retry button. Sort of looking like then send & receive from all programs (Putty, Uniden, Scan75) are somehow out of sync.

 

[eddferrell]

Sorry just off to bed UK time.

So far this is really odd. One time the MDL command fails with ERR. Next it comes back with a more intelligent response. Bit like things are not in sync.

Directly after the MDL response you could try Scan75 to see if that now detects your scanner. Also in Scan75 you can force a Port and then use the "R" retry button. Sort of looking like then send & receive from all programs (Putty, Uniden, Scan75) are somehow out of sync.

Hi Scan125, Thanks for your help. Your Scan75 program looks great, if I could get my dumb scanner to talk to it. I've tried a lot of combinations of settings and "do this, then do that" steps. Could you look at my port settings and see if anything looks amiss.
Baud: 57600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
Use FIFO Buffers: On (Rx=High(14), Tx=High(16))
COM port: 4
Driver: Silicon Labs CP210x to UART Bridge (COM4)

Also, is there another simple command, such as MDL, that I could try with Putty?
I appreciate your help. Cheers, Edd

 

[Scan125]

I don't know about other programs but Scan75 sets it's own port control settings.

On my PC when I look in Device manager when Scan75 is not running I have default values of:

Rate: 9600, Bits: 8, Parity: None, Stop Bits: 1, Flow control: None
RX Buffer: High (14), TX Buffer: High (16)

When Scan75 is running device manager still shows these settings.

However Scan75 sets and uses the following: ( var_name = def_var_name). I have never understood why Device Manager shows default values even when different values are being set by a program.

'Serial Port Control Constants and Variables
Public Const def_port_name As String = "?" 'default start port
Public Const def_port_rate As Integer = 57600 'default port bit rate '@A00
Public Const def_port_parity As Parity = Parity.None 'default port parity
Public Const def_port_data_bits As Integer = 8 'default port data bits
Public Const def_port_stop_bits As StopBits = StopBits.One 'default port stop bits
Public Const def_port_timeout As Integer = 500 'default port timeout ms

Public port_name As String = def_port_name 'current com port number
Public port_name_last_used As String = "none" 'com port used in last program run '
Public port_rate As Integer = def_port_rate 'com port rate
Public port_parity As Parity = def_port_parity 'com port parity
Public port_data_bits As Integer = def_port_data_bits 'com port data bits
Public port_stop_bits As StopBits = def_port_stop_bits 'com port stop bits
Public port_timeout As Integer = def_port_timeout 'com port timeout

With SerialPort1
.PortName = port
.BaudRate = port_rate
.DataBits = port_data_bits
.Parity = port_parity
.StopBits = port_stop_bits
.Handshake = Handshake.None
.WriteTimeout = port_timeout
.ReadTimeout = port_timeout
.NewLine = vbCr
.Encoding = Encoding.ASCII
'.RtsEnable = False 'did have True but not required - 06 May 22 '@A25
'.DtrEnable = False 'did have True but not required - 06 May 22 '@A25

So what I suggest you try is setting in device manager the usual default values I list above.

For Putty set the values (if available) to those Scan75 uses. NOTE! Only set Carriage Return and not Carriage Return & Linefeed.

Some other simple commands you can try are: VOL or SQL

Lastly Scan75 creates a "scan75-runlog.log" which contains basic log and error information which may be of help.

ALSO with Scan76 NOT running edit the "scan75-ini.ini" file and look for these lines:

# Log File Setting - Changes valid for next run only - size excluded!
ini_log_flag=False

Change ini_log_flag=False to ini_log_flag=True

Now run Scan75 and then close the program. The log file will contain a more detailed trace of what is going on.

The lines in the log for a working connection / scanner will look like these:

03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707156 1598707156 -> Startup of 1.3.1.0
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707625 469 -> <= Read_Ini_Data()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707625 0 -> => Notepad_Data_Read()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707656 31 -> <= Notepad_Data_Read()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707671 15 -> => SerialPort_Get_PortList()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707687 16 -> Detected Serial Ports: COM5 COM4 COM3
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707703 16 -> <= SerialPort_Get_PortList()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707718 15 -> => SerialPort_Try_Ports()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707750 32 -> => SerialPort_Try_Port(COM5)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707765 15 -> => SerialPort_Setup(COM5)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707781 16 -> <= SerialPort_Setup(COM5) = OK
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707796 15 -> => SerialPort_Port_Open(COM5)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707875 79 -> <= SerialPort_Open(COM5) = OK
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707875 0 -> => SerialPort_Test_Port_For_Device(COM5) with MDL
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707906 31 -> => SendCommand(MDL)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707921 15 -> => SerialPort_SendData(MDL)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707937 16 -> <= SerialPort_SendData(MDL) = OK
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707953 16 -> => SerialPort_GetResponse(MDL)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598707968 15 -> => SerialPort_ReadLineData()
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598708000 32 -> <= SerialPort_ReadLineData(MDL,UBC75XLT) by READLINE
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598708000 0 -> <= SerialPort_GetResponse(MDL) = MDL,UBC75XLT (using:READLINE)
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598708031 31 -> <= SendCommand(MDL) = MDL,UBC75XLT
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598708046 15 -> Port Used: COM5 (READLINE) and UBC75XLT
03/03/2025 09:28:27 (GMT:03/03/2025 09:28:27) 1598708062 16 -> <= SerialPort_Test_Port_For_Device(COM5) with MDL = MDL,UBC75XLT
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708734 672 -> => Model_Get()
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708734 0 -> => SendCommand(MDL)
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708750 16 -> => SerialPort_SendData(MDL)
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708765 15 -> <= SerialPort_SendData(MDL) = OK
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708796 31 -> => SerialPort_GetResponse(MDL)
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708812 16 -> => SerialPort_ReadLineData()
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708828 16 -> <= SerialPort_ReadLineData(MDL,UBC75XLT) by READLINE
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708843 15 -> <= SerialPort_GetResponse(MDL) = MDL,UBC75XLT (using:READLINE)
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708875 32 -> <= SendCommand(MDL) = MDL,UBC75XLT
03/03/2025 09:28:28 (GMT:03/03/2025 09:28:28) 1598708906 31 -> <= Model_Get(UBC75XLT)

Any errors (none above) should be logged.

To not bore the people here may I suggest you Email me at: scan75 AT nick-bailey DOT co DOT uk

You can attach the log file and I'll look to see if there is any useful info contained in it.

Nick