BCT15: BCT15 firmware update fails

[R2]

I have a BCT15 I got ~15 years ago, decided to 'finally' update firmware from 1.01.00 to the current.
Running BC VUP3 v3.03, get the message 'Does Not Match Firmware..."
'Scanner BCT15'
'Firmware BCT15'
Not sure why it doesn't upgrade...
FreeScan does read & write to the scanner
Upgraded my 246T last week no issues, using the same USB-1 cable
And no issues with Sentinel and the database scanners
Running on an Alienware R9 with Windows 10 Home Build 19041.1038
Thanks!
Bill

 

[chill1971]

The last firmware update for the BCT15 is
1.06.00. You probably accidentally got the update for the newer BCT15X.

 

[R2]

The software shows the BCT15 as the target model, and firmware 1.06.00...
Even tried the BCT15x but no match their either

 

[trp2525]

I have a BCT15 I got ~15 years ago, decided to 'finally' update firmware from 1.01.00 to the current.
Running BC VUP3 v3.03, get the message 'Does Not Match Firmware..."
'Scanner BCT15'
'Firmware BCT15'
Not sure why it doesn't upgrade...

You might want to try using BC_VUP_v2.0.0.7.zip along with BCT15_V1_06_00.zip to update your BCT15 as outlined in these detailed step-by-step instructions from Uniden: BCT15FirmwareUpdate < UnidenMan4 < TWiki

 

[R2]

Tried using v2.0.0.7, fails with a Comm error.

 

[JoeBearcat]

Tried using v2.0.0.7, fails with a Comm error.

That is probably the issue - a communication issue that cannot determine the scanner model.

Windows is known for 'breaking' older USB-1 cables.

 

[R2]

So getting a newer USB-1 cable should do the trick?

 

[SteveSimpkin]

So getting a newer USB-1 cable should do the trick?

Except you were able to use the same USB-1 cable on the same computer to update your 246T. That implies that the cable works with that computer. Can you look in Device Manager to see what serial port number Windows assigned to the cable? If it is a high port number maybe you could change it to a lower number (like COM1 or COM2) to see if it helps.

 

[R2]

Update, still unable to update firmware.
New USB-1 cable doesn't see the scanner, so need to workout the driver issue with that
So back to the Uniden USB-1 cable, and am able to see the 15 with Freescan, and read & write with Freescan, so not really sure what is happening here.
Public Safety systems here are 450-470, the 15 does pick up 'most' of what the 536 and 200 do

 

[JoeBearcat]

Could another program be claiming the port (cable) and not releasing it?

 

[dispatch235]

Comm port issues can be tricky: Freescan usually will autodetect a port for you, while the updater program you have to select the port... while you have the cord plugged into the scanner and the computer open up the updater program... then open device manager and look at what port it is showing for the usb serial adapter. Select the same comm port on the updater if it is available in the drop down box for the comm port. Sometimes you run into a problem where the port shown in device manager is not shown in the program drop down box. In that case you will have to go into the properties for the usb serial adapter and change the comm port to one that will match a port number shown in the program ...

 

[R2]

Success!
Not sure exactly what I did, but after using Device Manager to confirm the port, tried a couple of times with v3, got the same error message, then back to v2, and it update successfully
There was a baud rate mismatch, the port said 9600, set the scanner to 9600 but v2 would only go down to 38000, but it did update
Thanks to everyone for their suggestions!!