ka3jjz
Wiki Admin Emeritus
I've been trying to build a form based on a wiki template to display frequencies, slots, color codes and other data for Mototrbo trunked systems that have multiple color code data in the database.
However it seems I've been doing something wrong. I've been copying the database freqs where needed, and it appears that it's using a LCN as a place holder for the slot number, instead of an actual channel number.
Case in point:
Communication Specialists (Capacity Plus) Trunking System, Various, Virginia - Scanner Frequencies
Note the Fredericksburg site. It repeats frequencies twice to, I assume, represent slots 1 and 2. However when you start getting more than 1 set of channels, that representation falls apart like wet tissue paper.
Fortunately my template is pretty easy to edit, and I'm going to have to go back and fix the articles I've written (not too many). But the database is another matter; this representation is incorrect, if I understand how TRBO works. Granted that no scanner can handle TRBO, but it's really unnecessarily confusing to the newcomer. and as for programming a real TRBO radio, would they actually have to repeat the frequency twice just because of the 2nd slot? Seems unnecessarily sloppy and prone to errors...
How about just listing the frequencies 1 time, and add a notation that each frequency occupies 2 logical slots? Or are you guys planning to add a new form to the db to correctly display TRBO data?
Mike
However it seems I've been doing something wrong. I've been copying the database freqs where needed, and it appears that it's using a LCN as a place holder for the slot number, instead of an actual channel number.
Case in point:
Communication Specialists (Capacity Plus) Trunking System, Various, Virginia - Scanner Frequencies
Note the Fredericksburg site. It repeats frequencies twice to, I assume, represent slots 1 and 2. However when you start getting more than 1 set of channels, that representation falls apart like wet tissue paper.
Fortunately my template is pretty easy to edit, and I'm going to have to go back and fix the articles I've written (not too many). But the database is another matter; this representation is incorrect, if I understand how TRBO works. Granted that no scanner can handle TRBO, but it's really unnecessarily confusing to the newcomer. and as for programming a real TRBO radio, would they actually have to repeat the frequency twice just because of the 2nd slot? Seems unnecessarily sloppy and prone to errors...
How about just listing the frequencies 1 time, and add a notation that each frequency occupies 2 logical slots? Or are you guys planning to add a new form to the db to correctly display TRBO data?
Mike
Last edited: