View Single Post
Old June 17th, 2013, 19:21   #1
2 Cent Tactical
Cobrajr122's Avatar
Join Date: Apr 2006
Location: NB
Send a message via MSN to Cobrajr122
Comms 'Bleeding' and 'sub' channels

So at the latest big game, Nightfall 2, there was a lot of comms traffic on channels where it should not have been.

This has been a large issue in the past but we could work around it, but with such a high volume of people and chatter it was hard to work around and it became a largely talked about issue throughout the game.

Many people do not understand why this was happening so I thought I would post this up to try and explain why this happens and how to avoid it.

Comms 'Bleeding'
-What is it
-Why it happens
-How to prevent it

What is it
I am sure by now that just about everybody has heard it. You are listening to your radio and somebody else starts to talk who obviously does not belong on that channel. You can hear them but they cannot hear you.

Why it happens
FRS/GMRS radios operate using a 25KHz bandwidth.
For Ch 1-14 (FRS) this spacing is fine and does not cause any issue between any of them.
When you add Ch 15-22 (GMRS) this causes an issue.

Ch 15-22 operate very closely with Ch 1-7

Bandwidth - A channel uses more then one single frequency to work. To effectively transmit voice(or anything really) a chunk of frequencies are used with the carrier being the main one that it programmed into the radios.
This chunk of frequencies for FRS/GMRS is split in half and the carrier is the middle frequency.

For a 25KHz bandwidth, this means that a frequency of 462.5625 (Ch1) actually uses from 462.550 to 462.5750
462.550 and 462.5750 are the carriers for ch 15 and 16, which have their own 25KHz bandwidths as well.

This means that the channels have 12.5KHz overlaps with each other. Ch 1-7 and 15-22 all overlap with each other.

I have tried to illustrate this with a couple channels.

As seen, 1 overlaps with 15 and 16, and 2 overlaps with 16 and 17(not shown)


There are many options to avoid this from happening. I will cover 3.

1. -Do not use Ch 15-22 or 1-7.
Instead restrict comms to 1-14 or 8-22

This ensures that there will be no bleeding and blister pack radios can still be used.
Limits the amount of ch that can be used, not good for very large games.

2. -Change your bandwidth settings to 12.5KHz instead of 25KHz on Ch 1-7 and 15-22 (This does not always work)
Not to be confused with the Channel STEPPING setting.
Also known as Narrow band. (Narrow - 12.5KHz, Wide - 25 KHz)
This will eliminate all overlapping, but slightly degrade audio quality.

This ones only works if everybody has non blister pack radios, which, as anybody who has read my game comms briefs knows I advocate.

I know this is possible on the Lintons and Puxings I own, but not sure about any other brand. It seems to be a popular option to add to these radios so I would assume most have it.

I am sure there are a few other things that can be done, but these are just a couple options that will work just fine.

I have not covered the difference between the CDN and US frequencies because we all use the US ones anyways. It also seems that no matter how hard I try, Blister pack radios will still be at massive mil sims like this, and you can ONLY get those with US frequencies.


'Sub' Channels

Sub channels are bad and they should feel bad.

-What are they
-How do they work
-Why are they bad

What are they

Sub channeling is a method used to block all incoming traffic on a particular channel that does not contain a specific squelch tone.

How do they work

These sub channels operate using a squelch tone.

Squelch - Without squelch, you would constantly hear noise. Squelch turns off your receive circuit until it is triggered either by a specific signal, or a signal with X strength. At this point, it opens up your receive circuit until the tone/signal stops.

While the squelch is open, you can hear EVERYTHING on the frequency you are tuned into.

With FRS/GMRS there are two different technologies used to create 'sub channels' using squelch.
2. DCS

They are both quite different in their nitty gritty operation, but achieve the same result.

With CTCSS ch 1 (67 Hz) enabled, your radios squelch will only open up your receive circuit when it receives a 67 Hz tone.

Why are they bad

They are bad because it gives you the false illusion that you are on a private channel and can talk whenever you want without interfering with anybody else.

For this example I will be using CTCSS squelch tones.


-You are allotted FRS Ch 2.
-You want to have 3 nets
- Sect 1
- Sect 2
- Sect 3

FRS - 2 - Sub 1 = Sect 1
FRS - 2 - Sub 2 = Sect 2
FRS - 2 - Sub 3 = Sect 3

Radios will be programmed as such.

Sect 1 = 462.5875 MHz CTCSS 1 (67 Hz)
Sect 2 = 462.5875 MHz CTCSS 2 (71.9 Hz)
Sect 3 = 462.5875 MHz CTCSS 3 (74.4 Hz)

A member of sect 1 keys up to talk. All member of sect ones radios are activated and all sect 1 members can hear. Sect 2 and 3 do not hear this traffic.

Because members of Sect 2 and 3 do not hear sect 1 traffic, they do not know that there is traffic being passed. Therefor they do not know that the net is in use and not to key up.

A member of sect 2 keys up. All Sect 2 radios are activated.
A member of sect 3 keys up. All sect 3 radios are activated.
All members of sect 2 and 3 can now hear all traffic - This is a collision - bad.

A member of sect 1, 2 and 3 all end up keying up during the same transmission.
More collisions, more bad.

Because the transmitting stations can't hear the net, they do not know that they are talking at the same time as others. 2 people attempting to talk on the net at the same time is incoherent.


Feel free to add to this or ask questions.

Last edited by Cobrajr122; April 6th, 2014 at 13:18..
Cobrajr122 is offline   Reply With Quote