Annoying beeping on EDACS system.

[racin06]

I have a Radio Shack Pro-91 trunking scanner. The scanner will only trunk on Motorola systems. The county in which I live (Hamilton County, Indiana) uses the EDACS system. Though I can't trunk on this system, I can still listen to the radio transmissions. When scanning the EDACS system, there are usually 5 loud beeps after each transmission. Is this just a function of the EDACS system? If I had a scanner that could trunk on EDACS would the beeping end?

Also, I discovered last night (after checking out the browser history) that my wife has been visiting web sites that sell scanners. She should have cleared the history. LOL! I told here a couple of weeks ago about Uniden's 296D digital scanner. I believe that I may be getting this scanner for Fathers Day! Perhaps, I should check her email for a purchase confimation. Nah, I won't go that far.

 

[scannerfreak]

Usually when trunking EDACS the "beeps" are a result of poor reception of the control channel. But yes, if you trunk the system and have good CC reception, the "beeps" should disappear. Good luck on getting your 296D.

 

[Dubbin]

I believe that I may be getting this scanner for Fathers Day!

You WAS going to get it until she saw the price

 

[crayon]

Usually when trunking EDACS the "beeps" are a result of poor reception of the control channel. But yes, if you trunk the system and have good CC reception, the "beeps" should disappear.

I think that it would be more correct to say that EDACS beeps are a result of scanning a trunked system's frequencies conventionally.

The reason why I say that is because with all of the trunk-tracking scanners that I have owned .. if the radio loses reception of the control channel .. it simply keeps looking for another control channel until it finds one to lock onto. Everything else is ignored.

Usually people will say that the tones are "anti-scanner" tones. Whilst that may be the effect, this website says the tones serve a function.

After most transmissions, the repeater broadcasts a series of 5 beeps of constant pitch and frequency (a few systems reportedly mimic the "We Bring Good Things to Life" (registered, GE Corp) jingle). In actuality, the first beep is generated by the transmitting radio, to signal the site controller/repeater of the end of the transmission. The next four beeps are generated by the repeater. For transmissions appended with only four beeps, either the first beep wasn't received (in which case there is usually a 1-2 second burst of static before the repeater decides the transmission ended), or the transmission originated at a dispatch console that is wired directly into the site controller, rather than use the repeater inputs.

The only true anti-scanner aspect of an EDACS system that everyone argees on is the buzzsaw. Same website ..

The most-hated distinguishing characteristic of EDACS is the anti-scanner (or scan defeat) tone. Implemented on many systems, this is an obnoxious buzzing sound generated by the site controller and transmitted on many, if not all, repeater channels. There is always a pattern to it; the buzzing lasts a constant amount of time, has a constant period, and usually goes in the opposite direction of the voice assignments (if voice ascends, the buzzing descends through the channels).

 

[scannerfreak]

Usually when trunking EDACS the "beeps" are a result of poor reception of the control channel. But yes, if you trunk the system and have good CC reception, the "beeps" should disappear.

I think that it would be more correct to say that EDACS beeps are a result of scanning a trunked system's frequencies conventionally.

When I had problems montoring the local airport here who is on EDACS, I would still get the beeps at home with only 35-45% decode rate of the CC. When I drove closer to the airport and was gedtting 65-75% decode rate, the beeps disappeared.

I know you hear them when monitoring them conventionaly, but I figured the reason I was getting them in trunked mode was due to poor reception!

 

[Thunderbolt]

Usually when trunking EDACS the "beeps" are a result of poor reception of the control channel. But yes, if you trunk the system and have good CC reception, the "beeps" should disappear. Good luck on getting your 296D.

The first of the so called "anti-scanner" tones, sounded more like a doorbell, which was on their GE-Marc system. When their EDACS system came out under G.E., they used the old song/slogan "We bring good things to light," at the end of each transmission. Nonetheless, when EDACS when over to Ericsson, the tones changed to the current format that you hear now.

73's

Ron

 

[racin06]

I believe that I may be getting this scanner for Fathers Day!

You WAS going to get it until she saw the price

:lol: Actually, I warned her of the $500 price tag. She said that she wasn't surprised because most of my gadgets (she calls me the "gadget geek.") are usually in that price range. I just purchased a Garmin GPSMAP 76CS GPS unit. The price tag for that unit was $609.00. Well worth the price because I wanted a handheld GPS unit that I could use for both hiking, biking and during my travels on the road (performs autorouting). I just sold my old Street Pilot III GPS unit on Ebay; therefore, I only had to pay about $100 out of my pocked for the new GPS unit. I'll admit, I love my gadgets!

 

[crayon]

When I had problems montoring the local airport here who is on EDACS, I would still get the beeps at home with only 35-45% decode rate of the CC. When I drove closer to the airport and was gedtting 65-75% decode rate, the beeps disappeared.

Interesting. What type of radio?

 

[scannerfreak]

My pro-96. This just happened about a month ago. I was tired of getting shotty reception, so the last time I drove by the Airport on I275 I toook it with me just to see and sure enough, the beeps vanished.

 

[jimf]

EDACS beeps

I am not and EDACS expert, but have been listening to one for about 14 years on 5 different scanners. So, I will take a crack at explaining the sounds you are hearing. The five beeps you hear after each transmission end are indeed anti-scanner tones originally put in the system by G.E. I have heard the five beeps, the G.E. jingle, or in some cases have noticed the beeps turned off all together. In any case, they will go away using an EDACS capable scanner provided you have a good copy on the control channel. As for the buzzing sound heard from time to time on an EDACS system, this is a signal sent by the system to notify a user that they do not have access to the system. In other words, when a user keys a radio on an EDACS system, once the system verifys everything and voice transmission is possible, the users radio will emit a short beep notifying him/her to go ahead. If for some reason, the system cannot verify everything (usually when a user is in a dead spot) the system will transmit back an annoying buzzing sound letting the user know he/she has not been recognized by the system and transmission is not possible. The other users on the system will likely see a "busy" light on their radios. Scanner users on the other hand will likely hear the buzzing sound. Hope this helps, Jim.

 

[INDY72]

Almost all scanners when in the fringe area of an EDACS TRS will get the tones when your not getting the full power reception. I have witnessed this on a BC785XLT, PRO-2052, PRO-94B.

 

[Voyager]

When their EDACS system came out under G.E., they used the old song/slogan "We bring good things to light," at the end of each transmission. Nonetheless, when EDACS when over to Ericsson, the tones changed to the current format that you hear now.

No, it happened way before the GE-Ericsson Joint Venture (which was before Ericsson bought out GE). The FCC declaired the tones 'music' and GE was forced to change them.

Joe M.

 

[Cobra_Commander]

Will this annyoing beep happen with a pro-93? if i was following a edacs system with it? :?:

 

[Thunderbolt]

When their EDACS system came out under G.E., they used the old song/slogan "We bring good things to light," at the end of each transmission. Nonetheless, when EDACS when over to Ericsson, the tones changed to the current format that you hear now.

No, it happened way before the GE-Ericsson Joint Venture (which was before Ericsson bought out GE). The FCC declaired the tones 'music' and GE was forced to change them.

Joe M.

Now this makes sense, because Ottawa County Sheriff Dept., in Ohio was one of the last to change it to the plain "beeps," but a while back, I heard one TRS in Canada that was still using the old G.E. jingle. Nonetheless, after trying to listen to an EDACS system before the trunktracker scanners came out was a pain in the butt!


73's

Ron

 

[INDY72]

If you do not have the LCN's in correctly for trunktracking, or if your in a fringe area then yes you will hear the beeps.

 

[ECPD279]

Re: EDACS beeps

... As for the buzzing sound heard from time to time on an EDACS system, this is a signal sent by the system to notify a user that they do not have access to the system.

This buzzing sound you are referring to is not actually transmitted, it is generated by the users radio. If the radio is not allowed to access the system it wouldn't hear a transmitted sound. What everyone is hearing on scanners is something else.

Interestingly enough, the five beeps after each transmission are how trunktracking scanners know when to go back to the CC, so if you are not getting a strong enough signal on the VOICE channel you will hear the beeps because the scanner will not "hear" the tones through the static. I am pretty sure this is also the case for true EDACS radios because I have heard the beeps on our LPE-200's several times after very staticy transmissions.

 

[N_Jay]

Re: EDACS beeps

...
Interestingly enough, the five beeps after each transmission are how trunktracking scanners know when to go back to the CC, . . . I am pretty sure this is also the case for true EDACS radios because I have heard the beeps on our LPE-200's several times after very staticy transmissions.

What? Thay have a real purpose and are not there just to screw with scanner listeners? :twisted:
(sarcasm, in case you can't tell)