Wi-Fi Support Update Released

[UPMan]

Don't use SEARCH. Manually input the IP address of the scanner and press OK.

 

[dispatcher812]

Don't use SEARCH. Manually input the IP address of the scanner and press OK.

Thanks UPMan.

Wow this is great. Looking forward to whats ahead.

 

[Guardian24]

Just tried the new manual firmware update process for dongles that are at v0.00 using the BC_WF1_V7_28.bin file on three different Windows 7 computers and the updater program hangs up not responding. Dongle plugged directly into USB port, and all programs installed and running as administrator. Have also tried rebooting and trying again. Dongle is properly recognized as a COM port. What next Upman? I'll try anything

 

[unpltd]

Just tried the new manual firmware update process for dongles that are at v0.00 using the BC_WF1_V7_28.bin file on three different Windows 7 computers and the updater program hangs up not responding. Dongle plugged directly into USB port, and all programs installed and running as administrator. Have also tried rebooting and trying again. Dongle is properly recognized as a COM port. What next Upman? I'll try anything

I'm in the same boat, be patient and wait for the fix.

 

[noaim]

I got the dongle to the correct firmware because I updated it without the scanner. I then was able to update my scanner it seems to be working. Looking forward to having an app of my phone.


I do have a side question. I have a vpn connection which I'm able to access my home network from my phone. Will the scanner be able to run over the Internet or will the bandwidth be to low. In other words do I have to be on the same wifi network inside the house

 

[glenknyc]

Same Here, updater hangs up will not update. stb driver installed fine. ran as administrator on 2 computers.


Sent from my iPad using Tapatalk

 

[UPMan]

Guardian24 and others who said "me, too":

If you already attempted the update from 5.01 (and are receiving error 0004 or the Dongle firmware version reports as 0.00), unplug the wifi dongle and delete the file "BC-WF1..." from the "firmware" directory on your scanner. Leave the dongle unplugged until we issue an update.

 

[MidTNScanDude]

This Diversion has been Fun... but has the App been submitted for approval yet UPMan ? were working on Mid Feb.

 

[garys]

I've been running RH536 and VLC for 8 hours without a hitch. VLC has to be relaunched if the scanner is turned off, but RH536 picks the WiFi right back up.

 

[Guardian24]

Guardian24 and others who said "me, too":

Sorry, kind of confusing since it says to unplug and wait for update but also says that that was the process if the dongle was at v.0.00. Figured that the only way it would show that was if you had unsuccessfully tried the earlier update and failed because it was at v5.01.

FOLLOW THESE STEPS IF YOUR WI-FI DONGLE IS v5.01 or v0.00!!!
Check the version by MENU --> WIFI SETUP --> SHOW WI-FI INFORMATION.
If you already attempted the update from 5.01 (and are receiving error 0004 or the Dongle firmware version reports as 0.00), unplug the wifi dongle and delete the file "BC-WF1..." from the "firmware" directory on your scanner. Leave the dongle unplugged until we issue an update. Otherwise, follow the below steps:
Download Wi-Fi-Updater.zip.
Unzip the files downloaded in Step 1. Then, unzip the files in STM_VCP.zip.
Navigate to the STM_VCP directory and run either VCP_V1.3.1_Setup.exe or VCP_V1.3.1_Setup_x64.exe depending on whether you are running a 32-bit or 64-bit OS.
Plug the Wi-Fi dongle directly into a USB port on your PC and allow it to install.
Unzip and install BC-WF1_FirmwareUpdater_Version0.00.03.zip from the zip file you downloaded in Step 1.
Run the program you installed in Step 5 by navigating to the Uniden --> BCDx36HP --> BC_Wifi_Updater application launcher in your programs list.You might have to run this as administrator by either:
Right clicking on the file, and selecting Run as Administrator;
Or, pressing and holding Ctrl+Shift while opening the program.
When prompted, point the updater to the BC_WF1_V7_28.bin file, select the com port that was assigned to the dongle, then press OK to apply the update.
Now, click the below link to update the scanner's firmware.
CLICK HERE ONLY AFTER VERIFYING YOUR WIFI MODULE IS NOT AT V5.01 OR V0.0

 

[kruser]

The Scanner wifi dongle will work with WEP................

I replied to a poster much earlier in this thread about the possibility that there may be an issue with WEP encryption being as that same user has several other devices that connect to his router or WAP without issue but his Uniden dongle will not.
Going on the assumption that the user was entering his WEP key correctly is what made me type the post.
I also pointed out that WEP is no longer secure and can be cracked in seconds with tools freely available on the internet. Many people are not aware of that fact at all even though WPA2 has been the encryption standard for several years now.

Since my post, several others have found the same as I suspected and their dongles also will not connect using a WEP based key.
Some will however which makes me think it may be a combination of router or WAP that does not like the dongle when using WEP.

I ran some tests with more commercial grade WiFi routers and WAPS from Cisco (pre Linksys days) as well as 3COM, Motorola and some older Linksys WAPs plus both old and new D-Link models.
I found that several will not connect to an upgraded or non upgraded dongle when using WEP for encryption. I also found that the dongle will not connect to several model WiFi routers and WAPs when the SSID is hidden regardless if using WEP or WPA(2).
My dongles connect just fine using WEP, WPA or WPA2 to my main D-Link DIR-825 router using its original 1.00 firmware that I use around the house. But the dongle would not connect to a Cisco or 3COM WAP using WEP or if the SSID was hidden. I also had mixed results with older and newer Linksys routers and WAPS, both those now made under the Cisco name and those from pre-Cisco/Linksys days.
I've had other devices that had similar issues and those devices were made before Uniden ever released a dongle and likely before Uniden's dongle was even planned on paper.

This just shows that there are a lot of incompatibilities amongst the thousands of hardware devices out there and not everything is going to play nicely with Uniden's dongle.
I have a wireless dongle for my old Wii console that will not connect to several WAPS I own that are current models but a hardwired Ethernet dongle will connect to a switch or hub with no problems.

So, just because WEP will work with Uniden's dongle for some, it will also not work for some others.
In a perfect world, everything would work but things are not perfect so there are going to be those users that will blame Uniden even though the problem may lie in the wireless router or WAP or in its firmware.
Even Apple Mac has its problems with its Airport line of wireless devices.
There are simply too many combinations of devices out there that it would be impossible to test all.
The USB stack for some devices could be responsible for some of the failures being seen with WEP and various manufacturers wireless routers or WAPS. With all the wireless stuff out there both past and present, there is likely 10's of thousands of different possibilities and I doubt anyone has the resources to test all those possible combinations. So yes, there is going to be problems. Throw in an overcrowded band of frequencies into the mix in a highly populated area and you will have even more problems.

Most people have no way of identifying the problem or the knowledge to even try.
In the end, you really don't know it this WEP problem is a Uniden problem or one (or more) of the endless other possibilities.

I just know one thing and that is the fact that the Uniden dongle will not connect when using WEP and certain wireless devices made by others.
I've not compiled a list of bad devices nor have I sat down with RF test equipment or wireless analyzers to try and determine the cause nor am I going too. It's just the nature of the beast in most cases and in many cases, it's nobody's fault. It could be your neighbors microwave oven or the starter in the HID lamp outside your window that is flooding the 2.4 GHz band with trash.
But most with problems will be the first in line to blame the problem on Uniden.
Is Uniden perfect, no. Is Uniden trying to work around the problems, yes.
Will Uniden succeed, maybe but probably not for everyone.

I've seen the dongle problem of not connecting via WEP encryption and it is a true problem. Many that have it working will never report it as that is human nature but at the same time, those that do have problems will do everything they can to lay the blame on someone even if they don't have the tools or knowledge to figure out the real cause. Also human nature.

Luckily this WEP issue is a small issue as most people do have modern wireless routers and WAPS that support WPA or WPA2. Those people may run into problems though if they need to back off on encryption to WEP in order to support old devices made before WPA was invented and WEP had not been cracked yet.

 

[AA6IO]

For me its all about WPA2 instead of WEP. As posted previously, could not connect in infrastructure mode with WEP encryption no matter what I did. So an easy Google search told me how easy it was to change my FIOS Verizon router to WPA2 encryption. Did so this afternoon. Now all three of my 536HPs and respective dongles on infrastructure mode at 192.168.1.13, 14, and 15. Now time to play with VLC and RH and see how this thing works out.
Steve AA6IO

 

[AA6IO]

Been running RH program on two of my 536HPs. It sees either one or other 536HP at a time, but cannot run two instances of at same time. Seems to work fairly well. This changes the game now in terms of being able to use the 536HP via Wi-Fi without need to tether to a computer. Next will be figuring out how to use VLC software. Thanks UPMan and Uniden, looks like we are moving in the right direction.
Steve AA6IO

 

[dagooch0525]

The BC_Wifi_Updater application hung on me as well, but then I had success when I uninstalled the driver and allowed it to re-install.

More verbose:
I also followed the WiFi firmware instructions (as of 2/11/15). My WiFi dongle was also recognized when I plugged it into the pc. (COM19 as reported by the device manager). I too ran the BC_Wifi_Updater application and it hung.

I then went back to the PC device manager, located the WiFi dongle and uninstalled the driver. I unplugged the dongle. Re-booted the PC. Plugged the dongle back in. It re-installed the driver. It was recognized as COM19. I then re-installed (repaired) BC_Wifi_Updater application and ran it as admin.

This time the application did not hang and I successfully updated the firmware.

 

[Jay911]

The BC_Wifi_Updater application hung on me as well, but then I had success when I uninstalled the driver and allowed it to re-install.

More verbose:
I also followed the WiFi firmware instructions (as of 2/11/15). My WiFi dongle was also recognized when I plugged it into the pc. (COM19 as reported by the device manager). I too ran the BC_Wifi_Updater application and it hung.

I then went back to the PC device manager, located the WiFi dongle and uninstalled the driver. I unplugged the dongle. Re-booted the PC. Plugged the dongle back in. It re-installed the driver. It was recognized as COM19. I then re-installed (repaired) BC_Wifi_Updater application and ran it as admin.

This time the application did not hang and I successfully updated the firmware.

What version was your dongle showing prior to doing the above work?

 

[mikewazowski]

Gentlemen, another reminder that this thread is for dongle troubleshooting ONLY.

It is not for complaints against Uniden. If you feel you must vent, please start a thread in the Uniden Tavern or use an existing Uniden Tavern thread.

If I can find some time, I'll try and separate out the various topics from this thread. There will still be some crossover as some posts cover a few topics.

 

[AA6IO]

VLC and RH, and dongle/536HP working pretty well. Early in the game, but sure looks promising.
Steve AA6IO

 

[AA6IO]

Have another one of my 536HPs about 50 feet away on other side of house near a window where I get better reception on a couple of 800 Mhz trunking systems. VLC and RH running fine. This is going to open up all kinds of possibilities. Can't wait til the IPhone App is ready.

Steve AA6IO

 

[l3333]

For those who have the v0.00 issue (update attempted from 5.01-->7.28 using the scanner), engineering has been able to duplicate the issue and has been able to correct it in a very engineer-centric way (not one that the typical user could do). They will be able to issue a procedure for this, but are studying/developing the fix this week.

For those who have dongle v5.01 and want to update, I'll put instructions up later on the FirmwareUpdate page (that will be similar to what has been posted above).

Have the same 0.00 issue. May be there is a way to make a JTAG programming using FTDI USB to TTL cable? I would solder a couple of wires inside the dongle with pleasure. Just need a piece of software and instructions. Is it possible?

 

[UPMan]

I updated the instructions this morning and changed the updater to version 0.00.05 (from 0.00.03). This version will work with all dongles, including those that have been locked up by attempting to upgrade using the scanner.

If your module is at v4.x, you can skip to the bottom of that page and click the link.
If your module is showing 5.x or 0.00, you must use the steps shown by default when you open that page before proceeding to the link.