HP-2: Trailing beep with EDACS Standard

[Hit_Factor]

Ingham County Public Safety, Michigan

It has a long beep at EOT. I searched the forums and it looks like the 436/536 had this problem until the firmware update back in March (or so).

Is there anything I can do besides waiting for a firmware update?

I have AGC set to on.

 

[W8RMH]

I monitor the next county over who uses EDACS and don't have a problem with the tones (but it is not a simulcast system), I just get a quick "patink" at the end of a transmission.

I have read where some recommend changing the site's modulation from NFM to FM, you may want to give that a try.

 

[jonwienke]

If the beep is actually being transmitted, there's nothing you can do to eliminate it, and firmware isn't going to fix it.

 

[Voyager]

It's sent after the EOT data and is on the tail. It was originally designed to keep scanners from scanning the system quickly, and was originally the "GE jingle" (GE - we bring good things to life) until the FCC made them stop transmitting "music". Firmware could fix it if the mode change does not work (it may).

 

[Hit_Factor]

I'll look and see if I can change it. I was running the full database at the time. This system is typically not in range unless I'm driving to/from Detroit.

I've been thinking about creating a FL just for this drive.