Uniden BC296D English Owners Manual - Page 79

User Defined Fleet Maps

Get Uniden BC296D PDF manuals and user guides
UPC - 050633650356
View all Uniden BC296D manuals
Add to My Manuals
Save this manual to your list of manuals

Page 79 highlights

User Defined Fleet Maps Type I Programming Information When a Type I system is designed, the address information for all the IDs are divided into 8 equal sized blocks. When you program your scanner to track a Type I system, you must select a size code for each of these blocks. When you have assigned a size code to all 8 blocks, you have defined the Fleet Map for the system you're tracking. Each size code determines the number of Fleets, Subfleets, and IDs each block will have. For example, a size code of "4" has one Fleet, which is divided into 16 separate Subfleets, and it has a total of 512 individual IDs. When a block is assigned a size code, the Fleet or Fleets created within the block are assigned a Type I ID. The way these IDs display on your scanner depends on the block number and the blocks size code. When a Type I ID displays, the left most digit represents the block which contains the ID. The next two or three digits identify which Fleet is active, and the last digit(s) identifies the Subfleet. Block (1 digit) Subfleet (1 or 2 digits) Which Fleet within the Block (2 or 3 digits) The details concerning how the size codes are selected by a Type I system designer are highly dependent on the specific needs of the systems users. Some organizations may want many subfleets with only a few radios each, while another organization may want only a few subfleets with many radios each. Your task is to program your fleet map with the same size code assignments as the trunked system. If you do this accurately, you'll track all the Fleet-Subfleet combinations used by the system. In other words, you'll hear complete communications while monitoring a trunked system. If you don't already know the size codes used, you'll have to guess at them. But since you don't have to figure out all the blocks at once, this isn't as hard as it seems. Select a size code for a block, and then press SCAN. Now listen to the communications. If you decide you are receiving most of the replies to the conversations with IDs assigned to the block you just programmed, then you've probably selected the right size code and can work on the next block of the map. 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
User Defined Fleet Maps
Type I Programming Information
When a Type I system is designed, the address information
for all the IDs are divided into 8 equal sized blocks. When you
program your scanner to track a Type I system, you must
select a size code for each of these blocks. When you have
assigned a size code to all 8 blocks, you have defined the
Fleet Map for the system you're tracking. Each size code
determines the number of Fleets, Subfleets, and IDs each
block will have. For example, a size code of "4" has one Fleet,
which is divided into 16 separate Subfleets, and it has a total
of 512 individual IDs.
When a block is assigned a size code, the Fleet or Fleets
created within the block are assigned a Type I ID. The way
these IDs display on your scanner depends on the block
number and the blocks size code. When a Type I ID displays,
the left most digit represents the block which contains the ID.
The next two or three digits identify which Fleet is active, and
the last digit(s) identifies the Subfleet.
The details concerning how the size codes are selected by a
Type I system designer are highly dependent on the specific
needs of the systems users. Some organizations may want
many subfleets with only a few radios each, while another
organization may want only a few subfleets with many radios
each. Your task is to program your fleet map with the same
size code assignments as the trunked system. If you do this
accurately, you'll track all the Fleet-Subfleet combinations
used by the system. In other words, you'll hear complete
communications while monitoring a trunked system.
If you don't already know the size codes used, you'll have to
guess at them. But since you don't have to figure out all the
blocks at once, this isn't as hard as it seems. Select a size
code for a block, and then press
SCAN
. Now listen to the
communications. If you decide you are receiving most of the
replies to the conversations with IDs assigned to the block
you just programmed, then you've probably selected the right
size code and can work on the next block of the map.
73
Block
(1 digit)
Subfleet
(1 or 2 digits)
Which Fleet
within the Block
(2 or 3 digits)