Official Uniden BC246T Scanner Thread

[redfox355]

DaveIN, Gommert Buysen claims that the UBC3300 is modelled off the BC250D. So that probably means that the addition of a BCi96/25D card will likely only allow 3600 capability. Seeing as that is the only major difference between the 250D and the 296D.

I can't wait until Uniden brings out a small digital scanner... i literally can't wait, so I think I'm going to buy the Pro-2096 when it comes out.

 

[DaveIN]

UPM: Are the released pictures just mock-up photos made on computer?

Do you have any actual product photographs? Those volume/squelch knobs look a little long.

It is hard to visualize this radio as 4-1/2 x 2-3/4, x 1-1/4 and have an antenna attached to it. Sort of like a larger Icom R-5 I suppose. The display looks large in the picture as well.

How about a picture of the battery compartment and controls/ports?

The antenna has BNC connector right?

 

[UPMan]

They are 3D rendered from the same data used to make the tool (caveat: a few minor adjustments were made for tooling after the renderings were made).

I'd take a photo, but you would be disappointed, as most of the sticky lables indicating button function have peeled off. Working sample was made from SLA plastics, rub-on labels, and hot glue. Not pretty.

As to the ports, that was one detail added after the rendering was made. Power jack is located below the data port on the right-hand side. Knobs were tweaked slightly, but still about the same length.

BNC: Yes.

Battery compartment: Slide-on door on the bottom/back case. Nothing I can take a picture of, yet and we didn't render the back view.

 

[DaveIN]

OK, has anyone tested the RF rejection. The smaller units by AOR, Yaesu, and Icom are more prone to RF intermod and desensitizing in metro areas and propellerhead computer meets/hamfests/air shows. Sheilding and grounding is a major problem for a radio that size.

I am looking forward to testing the Close Call near-field counter. Is it able to catch and play the audio during scan/search as mentioned?

Someone in Europe was asking if the repeater offset is programmable to use with Close Call. My guess was that it would not and that the reverse feature/repeater offset would be according to the current US bandplan.

Great idea, by the way, adding Nascar to the label of the race scanners. 5 new models :!: I guess they are selling well at races 8)

 

[Voyager]

As for the BC296D, the things I like over the PRO-96: It has wider frequency coverage including the mil-air band, LTR, I-Calls, activity Id, computer control, Motorola control channel only trunking from search, a better/easier to read display, better scan lists, user/feild upgradable CPU firmware, and more EDACS features.

A slight correction to your information: The PRO-96 has MilAir with a simple click of the mouse and the 296D only has I-calls on 3600 baud systems.

As has been said in many threads, neither is better. Each has features the other doesn't. (see list here: http://www.radioreference.com/modules.php?name=Forums&file=viewtopic&t=12413 )

Joe M.

 

[UPMan]

Close Call checks for a hit every 2 seconds while scanning/searching/monitoring a channel. You can also turn the feature off or set it to continuously check for CC hits and nothing else.

In regard to the West Coast info, I've changed the rating to 2500 channels (1600 typical). Some additional overhead was necessary for memory shuffles that weren't originally anticipated.

Related note: 75% of the memory space will contain preloaded data from the factory to cover PD, FD, SD, and EMS dispatch channels for the top 25 counties by population (comes out to a little over 400 cities/towns/counties; most entities use multiple channels/frequencies). So, until you delete the info you don't need, you'll only have about 400 channels to play with.

 

[DaveIN]

Thanks, Voyager. I guess the point about the mil-air band is that you don't need additional software to open the frequency range on a radio that has some users vary in saying that they can hear traffic, no reception can be heard, or only hear very close to the source, i.e. Air-Show. My opinion only, as I own both radios and prefer the BC296D/BC796D for Mil-air and the various trunking features and the PRO-96 for others, but thanks for the list.

I also use the GRE PRO-92 version 1.0 for an alternate method (Subaudible trunking) to monitor analog 3600 buad Motorola and a PRO-92B for 400MHz/800 MHz Regular LTR systems and GRE/Optocom for those same reasons. If my PRO-96 was out for upgrade at Fort Worth for a talkgroup and memory bug would I be happy?!? So, do you think the PRO-2096 will be bug proof with version 1.4 :?: :lol: There was even a PRO-2067"A".

As for 9600 baud motorola systems I guess I didn't know that I-calls were used. Do you know if they are? I haven't heard if I-call is used in ASTRO. Guess I need to run the *secret feature* PRO-96 control channel dump on a system and see.

It would be great if the BC246T would include the Mil-air band, but then that may be included in the next digital version. It will take long enough to figure out all the features the 246 will have as it stands. After all Uniden is listening to the end user/consumer. So if it is within reason, I think Uniden will try to put it in the next model, or if it's a firmware bug they try to fix it in a software patch available via the internet. Just think, as improvents can be made to the CPU firmware, such as hexidecimal id, or active radio id display for Motorola systems. Up to date preprogrammed state/city frequencys could be changed in a patch, providing the CPU memory was available. Not saying GRE couldn't do this, but it looks like they don't or won't. If you have to return the radio to the factory, then it is most likely a hardware change.

Software patchs from Uniden looks to be the trend. The BCT-8 had a firmware bug that was fixed with a software patch. Saved time, made the consumer happy, and the problem was solved in the next production build as well. That way you won't have an endless thred about what version of firmware fixes what problem, is it warrenty work, who do I send it to, and how long will it take to be done.

If you think the current BC246T model looks great, just think what the next generation Uniden Trunktrackers will be like next year adding the APCO-25 features and wider frequency range. 8)

 

[DaveIN]

UPM: I think I'll like the ability to use Close Call during scan and even better as a stand alone feature :!: A two second delay during scan/search/monitor, can the delay be adjusted?

Now that is good thinking being able to delete un-used frequency from memory. More room for system setups. :shock:

So can I set up a block of memory with trunked frequencies, id's, conventional frequencies as an emergency setting. Then have an additional block for normal everyday monitoring using some of the same frequencies and Id's, and say a block for GMRS/FRS/MURS/itinerant frequencies so that I can select them like a bank?

How do you handle the EDACS and LTR logical channel numbers? Wouldn't you have to start from location 1 for EDACS and from LCN: 1 to 20 in LTR?

 

[UPMan]

Answer doesn't exactly match your question, because your question is premised somewhat on Banked scanners or PRO-96 methods. All will become clearer in time (I'm working hard on getting the O/M in shape to post, but it'll still be a couple of weeks).

The 2-second check interval is not adjustable (but the frequency hold time is adjustable from 1-5 seconds).

All memory is just a pool to draw from. As you create systems, it uses memory from the common pool. If system A uses 10 channels and System B uses 30, system A will use 1/3 the memory space of B.

You could program FRS/GMRS as a conventional system if you wanted to be able to scan for those and other systems at the same time. It won't simultaneously search and scan, though.

As to LCN, this is an attribute of a EDACS or LTR system frequency, and you will be prompted to enter then LCN when you enter the frequency. There are no channel numbers, plus the trunked system frequencies are not channels...they are a system attribute, just like in the RW; TG ID's and their associated attributes comprise trunked channels.

 

[AZScanner]

I'm working hard on getting the O/M in shape to post, but it'll still be a couple of weeks; up to 3,500 pages -- the 1,000-page version just didn't include the detail you need to do everything.

Did you just say 3500 pages of Owner's Manual? :shock:
-AZ

 

[UPMan]

Um, I don't see that in my post. But, sometimes my evil twin takes over the keyboard. :twisted:

Actual page count is TBD.

 

[AZScanner]

Um, I don't see that in my post. But, sometimes my evil twin takes over the keyboard. :twisted:

Actual page count is TBD.

You edited the post! I swear it was there a minute ago... What's this? Here comes two guys wearing black suits and sunglasses. One is holding what looks like a pen...

"Jay" and "Kay" from Uniden pay me a little visit.

<ZZZZAP!!!>

...there was no post.... I was mistaken.... I need to buy a BC246T when it comes out...

-AZ

 

[DaveIN]

I see, so the LCN is included in the frequency/trunked data for each memory block. Hmmm.. I think software will be needed for easier programming. :wink: Sounds good although. The Pro-96 V-scanner feature would be similar to what I was thinking of before.

Now when you program a trunked bank, do you enter all the frequencies into a list, and then the system attributes, and then the id scanlist, as well as the alpha tags, in one memory location, or is each frequency in a separate memory block linked somehow?

If so, in the case of Motorola control channel only tracking, would this be less memory used by only entering the four possible rotated control channel frequencies, in place of all the system frequencies?

Could id talkgroup lists be linked with other trunked frequencies for multi-cell site systems or just to the set of trunked frequencies in one system?

Are conventional frequencies and CTCSS/DCS tone information saved in one group in a memory block or individual block for each frequency?

 

[DaveIN]

8) Now AZ don't be wavin' that flashy thing around. Remember what happened to that web page full of pictures with next years digital model. That's funny, I can't recall what the model number was BC3 something *FLASH*, there it goes again :!: Guess I'll eat some pie... 8)

:idea: Maybe Uniden will put MIB TrunkTracker III on the label, MIBC246T :idea:

 

[crayon]

As to LCN, this is an attribute of a EDACS or LTR system frequency, and you will be prompted to enter then LCN when you enter the frequency. There are no channel numbers, plus the trunked system frequencies are not channels...they are a system attribute, just like in the RW; TG ID's and their associated attributes comprise trunked channels.

This is HUGE leap forward in scanner technology! If you wanted to monitor a large EDACS system, (like AEP here in Oklahoma) you only could load ten sites at a time .. anything past that .. was a scanner reload from your laptop.

So very sweet.


AZScanner, props on the comedy. Well done.

 

[UPMan]

Still not sure what you refer to as "block."

Here is a sample hierarchy for an EDACS System

System Name
   System Options
      Quick Key
      Lockout
      Hold Time
      Delay Time
      ID Format (AFS/Decimal)
      ID Scan/Search
      Emergency Alert
   System Frequencies
      Freq + LCN
      Freq + LCN
      Freq + LCN etc...
   System Attenuation
   Channel Groups
      Group Name
         Group Quick Key
         Group Lockout
         TGID
            Text Tag
            Priority
            Channel Alert
            Channel Lockout
         TGID
            Text Tag
            Priority
            Channel Alert
            Channel Lockout
         TGID
            Text Tag
            Priority
            Channel Alert
            Channel Lockout

and so on for additional channels and/or multiple groups and/or multiple systems. Each system type has different system and channel attributes available (for example, conventional systems do not have a "System Frequencies" option, their channels start with "Frequency" instead of TGID, and each channel has options that have to do with frequencies, like CTCSS/DCS, modulation method, frequency step, etc)

Looks more complicated than it is, because most default settings don't need to be touched.

So, a system that has only the control channel system frequencies programmed in will use less memory than a system that has all system frequencies programmed in (assuming they both have the same number of TGID channels).

Each system is self-contained, no sharing of TGID's between systems.

 

[DaveIN]

OK, cool :!: Block, as in memory block, or memory location. I guess it would be called a system. When it is conventional it's just a frequency.

So you select what "key" you want the system/frequency memory attached to. Will the Motorola activity Id feature still be available? how about activity icons such as the blocks on the BC898T display to show relative trunked system activity.

Can you still set the trunked system delay? I see you can attenuate a system.

Do you put the coventional frequencies all together on one key or can you put just one frequency on a key? That would be poor memory management I guess, but what if you want to use a key as a hotbutton for one emergency or a hot interest frequency.

Now that the bank/channel limitation (that has been around for so long) is out the window there are many great possibilities.

 

[UPMan]

Last one for today...printing a large document so you caught me at a good time.

When it is conventional, it is still a system with attributes, channel groups, group attributes, channels, and channel attributes. The attributes available, though, are only the ones that apply to the current system type.

Systems are assigned to quick keys (0-9). You can assign as many systems as you want to a quick key. You can mix system types on a quick key. While scanning, press 0-9 to toggle on/off the associated systems.

Within a system, channel groups are assigned to F+Quick Keys (I've got to think of a better name for these) 0-9. While on a system, hold F and press 0-9 to toggle on/off the associated channel groups. You can have up to 20 channel groups per system (200 channels per system total). You can have as many groups within a system assigned to the FQK as you want.

Motorola-exclusive system attributes include band plan, fleet map, status bit, end code, I-call.

I think what you are referring to is what I called "System Hold Time." This defines the maximum amount of time the scanner will sit on a system before moving to the next. After the hold time expires, the current transmission ends, and the current delay expires, the scanner is forced to the next system. This attribute is available for all system types (including conventional) and is defaulted to 2 seconds (for conventional systems, regardless of the setting all channels are scanned at least one time).

 

[DaveIN]

Ah Ha :!: Now that makes a better picture. Ok, thanks. So it is like the PRO-96 V-scanner in a way, but better! You can use it as needed and not have to re-boot to a different set of memory, nor it it limited by channel/talkgroup list restrictions. :twisted:

system: Quick Key (0-9) then;
>F+Quick key: System (trunked or conventional) 0-9;
-->up to 20 channel groups per system (up to 200 channels total)
---->Trunked system atributes and or conventional frequency attributes:
System Name
System Options
Quick Key
Lockout
Hold Time
Delay Time (hang time for trunked?)
ID Format (AFS/Decimal)
ID Scan/Search
Emergency Alert (EDACS)
System Frequencies
Freq + LCN
Freq + LCN
Freq + LCN etc...
System Attenuation
Channel Groups
Group Name
Group Quick Key
Group Lockout
TGID
Text Tag
Priority
Channel Alert
Channel Lockout
TGID
Text Tag
Priority
Channel Alert
Channel Lockout
TGID
Text Tag
Priority
Channel Alert
Channel Lockout

 

[kikito]

Glad to see Uniden stepping up the competition!
The list of features looks promising too!

A few 'practical' things I wonder about so far are:

* How many of the features announced will make it to the production radio and how many will work as advertised?

* Battery life

* Quality and brightness of backlighting

* Quality, size and readability of the display/text

* Very important: quality of audio

* Very important: receiver quality (selectivity, sensitivity, etc.)

* (This one is for the future Digital models)
Very important: VHF/UHF 9600 trunking - Since those systems don't have the limitations of 3600 systems and more are coming out every year; Will we be able to enter Offset values lower than 380 or higher than 759 when needed?, will it have the 'control channel only' option?

* Hopefully, most major bugs will get caught before official release. (The sometimes 'crucial' upgrades/updates with both brands of radios is getting old....)


Some of these items may or may not have been discussed already but even the feedback from "UPM" is 'subject to change at this time'.
By the way, the inside info from "UPM" is greatly appreciated.