Confused About How To Figure Out LCNs

[natedawg1604]

So, if a Cap+ site has different color codes on different frequencies, does it make any difference to radio users? Is this done intentionally to force certain radios to always use certain frequencies or something? Or, do color codes make no difference on Cap+ systems?

 

[Voyager]

Is it possible that a system can skip LCNs and just have no frequency? Like, can you have 1 system with a 3/4 frequency and a 5/6 frequency, but no 1/2 frequency?

Yes. I've seen one system that had interference issues, so they just disable that TX or put it on the lowest priority (it only gets used if no other slots are available).

 

[Voyager]

So, if a Cap+ site has different color codes on different frequencies, does it make any difference to radio users? Is this done intentionally to force certain radios to always use certain frequencies or something? Or, do color codes make no difference on Cap+ systems?

It makes no difference to the radios whatsoever. Each frequency is programmed with a color code. The radio only cares that it matches the transmitter, and not what code it is.

 

[CanesFan95]

Can 1 Cap+ system have each frequency be a different site number? Fast lane shows the site number. Most of them show Site 1. But a couple show Site 2 or 3. So I'm wondering if I'm safe to assume that all repeaters on the same system have to have the same site number.

 

[natedawg1604]

Can 1 Cap+ system have each frequency be a different site number? Fast lane shows the site number. Most of them show Site 1. But a couple show Site 2 or 3. So I'm wondering if I'm safe to assume that all repeaters on the same system have to have the same site number.

Actually I noticed the exact same thing recently. It appears the event log in 2.10 automatically displays Site#=1 for all non-linked Cap+ systems by default, even though the terminal output does not show any site#, which suggests there is no actual site# being broadcast in the CSBK messages. Regardless, I'm guessing they did this to have a placeholder field for monitoring Linked Cap+ systems. However, as a result it appears that in order to monitor a non-linked Cap+ system in cc trunk following mode, you must specify a dummy site# of 1 in the frequency file. Does that all sound correct?

 

[CanesFan95]

I've seen a couple Cap+ frequencies that don't display any site number, but it's rare.

 

[CanesFan95]

Sometimes Cap+ frequencies send their callsign in Morse Code. If there was a way to decode the callsign, that might help piecing systems together.

 

[slicerwizard]

Actually I noticed the exact same thing recently. It appears the event log in 2.10 automatically displays Site#=1 for all non-linked Cap+ systems by default, even though the terminal output does not show any site#, which suggests there is no actual site# being broadcast in the CSBK messages. Regardless, I'm guessing they did this to have a placeholder field for monitoring Linked Cap+ systems. However, as a result it appears that in order to monitor a non-linked Cap+ system in cc trunk following mode, you must specify a dummy site# of 1 in the frequency file. Does that all sound correct?

Makes sense to me. I use the Cap+ site number that DSD+ displays at the bottom of the event log window for all .frequency file entries.

 

[CanesFan95]

So how do we know if we're listening to linked Cap+ or not?

 

[natedawg1604]

So how do we know if we're listening to linked Cap+ or not?

I believe you have to look at the terminal output available with the -v[1-4] flag, and check whether you see a site number appearing in the CSBK messages.