Rangecast FAQ
[FAQ-1116] How to add a custom channel (not from RCDB) to a hub


Page Type: REFERENCE


OVERVIEW

Channels not in the master nationwide channel database (RCDB) can be added to a hub's scanner reception. Such extra "custom" channels must be tied into the system/group/channel hierarchy.


METHOD

Custom channels must be placed into the system/group/channel hierarchy. Therefore, the first step is to identify an existing group (present in the available list of channels in the HTML5 programmer) into which this channel can reasonably be placed. Within this group, find a channel that is fairly similar, at least to the extent that the existing channel's geographic coordinates are not unreasonable for the custom channel. The more similarities, the better, since we will borrow the existing channel's database properties for the custom channel, and will need to explicitly set any properties that are different (so these differences should be minimized.)

When a channel is found, create a line of text like this (without quotation marks):

"CX10200:c=C028297,f=154.3850,p=127.3,u=F1,r=16,n=Fire Department 154.385,a=GLOUCESTER/FIRE"

CUSTOM CHANNEL SYNTAX -- The value before the colon will be the CID of the custom channel. Conventional custom channels must start CX, trunked custom channels TX. The five-digit number following must be unique among custom channels that may be received together by a player (note: in addition to being unique within this hub, the number must also be unique within any group of hubs that may be brought together in a player.) It is recommended that a numbering policy be adopted to ensure this uniqueness.

--> c= CID OF CHANNEL -- The value in the 'c' parameter is the CID of the channel on which you are basing the database properties of the custom channel (including system/group membership.) For custom trunked channels, this must evidently be a talkgroup in the same trunked system.

--> f= FREQUENCY OR TALKGROUP -- The value in the 'f' parameter is the frequency or talkgroup of the custom channel.

--> p= PL CODE -- The value of the 'p' parameter is the PL code of the custom channel, expressed in the same format shown in the HTML5 programmer for PL codes. This parameter should always be included for conventional channels, else the PL value of the channel listed in the 'c' para FUNCTION TYPE -- The value of the 'u' parameter is the function type (e.g. F1 for fire dispatch) in the same format shown in the HTML5 programmer.

--> r= FEEDSITE ID -- The value of the 'r' parameter is the feed site ID where you want the custom channel to be received. If the feed site value is below 10, a leading zero must be included.

--> n= HTML5 CHANNEL NAME -- The value of the 'n' parameter is the name of the channel in the HTML5 format (maximum 64 characters.) Note that this will supplement the existing system/group text tags, this field is the additional information describing the particular channel.

--> a= JAVA CHANNEL NAME -- The value of the 'a' parameter is the name of the channel in the Java format (up to three fields of 16 characters.) This parameter is optional, and may be omitted. If used, the special character forward slash "/" is used to separate the three fields (so this character may not be used as part of the text.)

OTHER PARAMETERS -- Other available parameters are 's' (for short name, e.g. button name) and 'i' for broadcast tower in a trunked system.

Note: If there is no appropriate group into which the custom channel may be entered, it is possible to create custom groups or systems, but this is a more advanced process.

Note: A custom channel added in this manner is a property of this hub, and is not available for programming into the RCHANs of other hubs.

Note: Custom channels do not appear in the list of channels in the HTML5 programmer. The channels in these lists are solely drawn from the master channel database. When a custom channel is added to a hub, it will only appear in the Hub Overrides list, where you will later copy/paste the line you have written.

Note: For retaining this custom channel in future updates to the RCHAN, it is essential that the CID from which the database properties are copied remain available (e.g. in the channel list shown in the HTML5 programmer.) This does not mean that the reference channel must be selected for reception, only that it be known about by the programmer. In particular, note that the reference channel may be lost in the future if the entry screen parameters are changed in a way that excludes that channel.

After creating the line describing a custom channel in the correct syntax, go to Save Options, select "Edit Hub Overrides", copy and paste the text into the text entry box, and press Apply Changes.


CITATIONS

SOLUTION

INDEX


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