Rangecast FAQ
[FAQ-1119] Using Uniden 536 scanners at a Rangecast feed site


Page Type: REFERENCE


OVERVIEW

The Uniden 536 scanner behaves differently from other models of scanner commonly used at Rangecast feed sites. A significant difference is that 536 scanners cannot be programmed by Rangecast software, so the scanner must be programmed with the desired channels in some other way.


REFERENCE

The Uniden 536 scanner is not compatible with the scanner programming software included in the Rangecast feed site software package, so (unlike other scanner models) a 536 will not be automatically programmed to match the list of channels defined in a Rangecast RCHAN file.

However, use of an RCHAN is still important (as this provides a way to associate metadata with received channels, such as HTML5 channel IDs [CIDs], or Java channel codes and alternate text tags.) Channels not listed in a feed site's RCHAN file, even if received by a 536 scanner, will not be distributed to the HTML5 player because there is no channel ID associated with the transmission.

Therefore, the key requirement when using a 536 scanner at a Rangecast feed site is that the scanner must be programmed in some external way (outside Rangecast software) with the same set of channels that are specified in the feed site's RCHAN file. In essence, whereas other scanners are *automatically* programmed in accordance with the RCHAN file, while 536s must be *manually* programmed to achieve this result. (And this must be done every time the RCHAN is modified in a way that changes which channels are listed for the feed site.)

Note: to meet this requirement, all that matters is that the frequency and PL code for each channel be identical to what is specified in the RCHAN to describe the channel. The text tags in the scanner are ignored, and do not need to match the RCHAN.

A minor secondary restriction is that, when using a 536 with Rangecast, it is forbidden to receive the same talkgroup number from two different trunked systems on the same radio. The Rangecast software will not differentiate the two talkgroups correctly, and it is possible that traffic on one channel will be incorrectly reported as being on the other channel. However, this circumstance is very rare.


Rangecast FAQ - ID 1119 - last updated 02 August 2017     Images shown - [block]