DonaldGallagher
Member
If you already have the "UPDATER" it will find the available updates automatically when run.
If not, download the BC_VUP3 updater for DMA scanners here.
BCD996P2FirmwareUpdate < UnidenMan4 < TWiki
- Status
If you already have the "UPDATER" it will find the available updates automatically when run.
If not, download the BC_VUP3 updater for DMA scanners here.
BCD996P2FirmwareUpdate < UnidenMan4 < TWiki
RDL88
Member
UPMan, I am trying to install the latest firmware BCD325P2/BCD996P2 Update 1.08.0, and get an error message that my comm port is not the right port. It also won't auto detect. It works fine on the Scanner Master software. Thanks for any help you may provide, UPMAN.
I don't think UPMan will be able to help you with that. I'm not a computer expert, but I think the problem is most likely in your computer settings.
I would have the uniden usb driver.
Last edited:
CanesFan95
Active Member
Running 1.08.01 on a BCD996P2 and still having the same problem. The scanner fails to properly track Capacity Plus talk groups. In fact, it doesn’t even stop on active TGs. The scanner just keeps scrolling ID SEARCH even when someone is keyed up and talking. Here’s a couple screenshots of this system, monitoring just Site 5:
https://www.radioreference.com/apps/db/?sid=8588
This is side-by-side comparison with DSD+ and the scanner using ProScan software. You can see a full signal strength and DSD+ shows an active talk group, but the scanner never stops ID SEARCHing. I’ve reported on this same issue in 2 other threads with photos & videos on earlier firmwares and no one from Uniden ever says anything.
BCD996P2 Missing Calls On Cap+ Trunking: Side-By-Side Comparison With DSD+
BCD996P2 Not Stopping On Capacity Plus Talk Groups
Some posters say, oh, it works fine on my scanner, no problem. But how do you really know without doing a side-by-side test?
https://www.radioreference.com/apps/db/?sid=8588
This is side-by-side comparison with DSD+ and the scanner using ProScan software. You can see a full signal strength and DSD+ shows an active talk group, but the scanner never stops ID SEARCHing. I’ve reported on this same issue in 2 other threads with photos & videos on earlier firmwares and no one from Uniden ever says anything.
BCD996P2 Missing Calls On Cap+ Trunking: Side-By-Side Comparison With DSD+
BCD996P2 Not Stopping On Capacity Plus Talk Groups
Some posters say, oh, it works fine on my scanner, no problem. But how do you really know without doing a side-by-side test?
Have you set the LCN'S to the proper number and I use a programmed radio to test it pays to have friends that own 2way shops
CanesFan95
Active Member
Yep yep yep, I know the right LCNs cos DSD+ tells you the LCNs.
oldtimeradio
Member
Had problem where Windows (On Rebooting) would install the driver they thought was best for "My Uniden Com Port".
I was getting the message "com port not available" even though it was the correct one.
In Windows 7 I disabled that function so it won't change any drivers from windows update option they use. (search)
Once I installed the correct Uniden Driver everything worked.
(And as always,,, use the correct Mini USB Cable plugged into the front of the receiver while loading data.)
Hope this helps.
mike
oldtimeradio
Member
Well that was a waste of time. Windows lets you do it but it does not work. I even tried deleting the driver in the system folder and it won't let you. More research. mike
1. Ensure the LCNs are correct. Note that DSD shows you the LSNs not the LCNs.
LCN = (SLOT 2 LSN)/2
2. What about other Cap+ systems?
3. If you have SDSx00 or BCDx36HP, what about them?
4. Could you get a debug log?
If a BCD996P2 is used, connect front USB port to PC.
Set MENU/Settings/Set C-CH Output/Extend/Front Port.
Run terminal software (like TeraTerm) on the PC.
When the scanner has run long enough to log the issue, copy the part that would include the issue and paste to text file.
Attach the text file to your reply.
LCN = (SLOT 2 LSN)/2
2. What about other Cap+ systems?
3. If you have SDSx00 or BCDx36HP, what about them?
4. Could you get a debug log?
If a BCD996P2 is used, connect front USB port to PC.
Set MENU/Settings/Set C-CH Output/Extend/Front Port.
Run terminal software (like TeraTerm) on the PC.
When the scanner has run long enough to log the issue, copy the part that would include the issue and paste to text file.
Attach the text file to your reply.
Last edited:
CanesFan95
Active Member
Well, I'm double-triple checking the LCNs / LSNs (which I've done before), but I could be wrong. DSD+ is setup with the following on Site 5 per the screenshot above (which works properly):
1 462.3000
2 462.3000
3 452.3375
4 452.3375.
The BCD996P2 has the same 2 frequencies programmed as:
1 462.3000
2 452.3375.
Here's a screenshot of ProScan with how it's programmed:
I don't have any SDSx00 or BCDx36HP scanners. I've always wished I could try the BCD996P2 side-by-side with another exact same model and/or other models to see if they all behave the same. I do have a discriminator tap mod done on the BCD996P2. I will work on posting a debug log as I have more time to figure out how to do it (never knew about this).
1 462.3000
2 462.3000
3 452.3375
4 452.3375.
The BCD996P2 has the same 2 frequencies programmed as:
1 462.3000
2 452.3375.
Here's a screenshot of ProScan with how it's programmed:
I don't have any SDSx00 or BCDx36HP scanners. I've always wished I could try the BCD996P2 side-by-side with another exact same model and/or other models to see if they all behave the same. I do have a discriminator tap mod done on the BCD996P2. I will work on posting a debug log as I have more time to figure out how to do it (never knew about this).
CanesFan95
Active Member
So I went ahead and grabbed that "Tera Term" program you mentioned and got it working. Here's 3 different log files all recorded at the exact moment I could see (and hear) an active TG keyed up on DSD+ while the scanner still scrolled ID SEARCH.
CanesFan95
Active Member
This system uses Restricted Access To System (RAS). Almost all the Cap+ sysetms in my area use RAS. But for contrast, here's another (longer) log file on a different system that is non-RAS (attached): https://www.radioreference.com/apps/db/?sid=8562 . The log file has a lot of dead air, but there should be about 15 or so transmissions that happened all on TG 176. The RF frequency of the rest channel and voice calls never changed and stayed on just 451.9750. But here's the thing. On this system (the non-RAS one), the scanner DID stop on the TG (176) every time and unmuted properly, right along with DSD+. So for some reason, it seems to work on this system, but not the first one above. "Tera Term" doesn't seem to record anything during voice calls, only before and after.
Hmm. Those log files aren't showing any Cap+ channel grants. So, either they are using RAS and we're not catching it or they are sending some unsupported op codes. Can you take a DSD log side-by-side w/scanner log?
CanesFan95
Active Member
DSD+ logging has always been confusing. There's a number of different log files, but most of 'em are blank, even though I have -v4 in both command lines for the voice and control channel instances. I can see gobs of stuff scrolling in the DOS-style console windows, but it's not getting saved anywhere even though I have >CC.log and >VC.log in the command lines. Both those files are blank.
CanesFan95
Active Member
And how do I know what serial port speed (and other settings) I should be using in "Tera Term"?
The settings would be the same your GPS speed setting is under settings then set GPS Baudrate
CanesFan95
Active Member
Thanks. The scanner was set to the fastest speed at 115200, but "Tera Term" was set to 9600 when I did the logs. Now I've gottem both at 115200. So I wonder if my logs above could have missed some data with the speeds being different. I also figured out some other settings in "Tera Term" and got it to put each piece of data on a new line with a date/timestamp in the log which makes it much easier to read. Now the "Tera Term" logs looks a lot neater instead of being a jumbled mess. So If/when I do any more logs, this should help. But I still can't figure out how to get the DSD+ log.
Code:
[2019-04-12 19:03:21.430]
[2019-04-12 19:03:21.430] DMR,BE10E200000000000000
[2019-04-12 19:03:21.492] DMR,BE10E200000000000000
[2019-04-12 19:03:21.523] DMR,BE10C200000000000000
[2019-04-12 19:03:21.555] DMR,0F18223804012D730000,PN,UN,UN
[2019-04-12 19:03:21.586] DMR,BE26390558A7913C07E1,PN
[2019-04-12 19:03:25.408] DMR,BEC0A200000000000000,PN
[2019-04-12 19:03:25.408] DMR,0647346C2F12E67CB395,PN
[2019-04-12 19:03:25.486] DMR,6358285F4D49C8E78D1B,PN
[2019-04-12 19:03:25.517] DMR,207B5E6F816636ECE1B8,PN
[2019-04-12 19:03:26.235] DMR,3200C10070A84708D504,PN
[2019-04-12 19:03:26.406] DMR,BE10E100009040087700CanesFan95
Active Member
The issue with DSD+ logging has been figured out in this thread. I was able to get a log from DSD+ and "Tera Term" both at the same time while TG 17 (in decimal) was keyed up about 4-5 times. The scanner never stopped on it. Here are the files (attached). The DSD+ file is a log of the control channel console DOS-style window and is lengthy because I had the verbose setting set to the max -v4. Both files have date & time stamps which should allow for an exact line-by-line comparison. The DSD+ log starts earlier than the "Tera Term" log.
CanesFan95
Active Member
I do notice that sometimes the BCD996P2 has a hard time finding and locking on to the rest channel. You can see the little frequency indicator on ProScan flipping around to all the frequencies but not stopping on the rest channel. The scanner display will quickly flash all the signal strength bars every so often as it keeps searching for the rest channel. Despite a full signal strength on both systems, sometimes the scanner will keep flipping through the system frequencies and won't lock on for a while.
- Status
