S
scanner1man
Guest
Does anyone in / near Port Jervis, know if the EMS still use 46.04 ?
- Status
S
scanner1man
Guest
157.45 and 153.86 I know about. I was just wondering about 46.04,since they are licensed on 155.13 also.
I'm not in that area that much,like years ago. Thanks for the reply.
I'm not in that area that much,like years ago. Thanks for the reply.
KC2zZe
Member
It's channel 12 in their VHF-low band radios (after the County fire VHF-low band ten channel plan, and Port Jervis Fire's F11). It is rarely used as an interop frequency between PJFD and PJVAC. 155.130 is for internal PJVAC use. It was their F3, but I'm not sure if it's still there as I'm sure their VHF-high band channel plan changed after Sullivan County upgraded their FD/EMS communications systems.
S
scanner1man
Guest
Ok.Thank you
S
scanner1man
Guest
I just found info on the FCC page,that it expired 8/3/14. Would this give me permission to have it deleted from
database?, being it's hardly used?
No.
We don't delete entries from the database because a licensed expired. There are countless agencies who operate daily on frequencies that are unlicensed due to a license not being renewed, or never existing in the first place.
If someone were to confirm that 46.04 is no longer programmed in any of their radios, then we'd delete it from the database.
S
scanner1man
Guest
.Being KC2zZe stated that it's not used that much anymore, I thought it should be deleted. Thanks.
Unfortunately, the database is full of seldom used frequencies. It's the nature of the beast, especially when it costs little to nothing for public safety to license frequencies and perpetually renew them. It's not unusual for an agency to license multiple frequencies after formulating a grand plan for their usage, only to wind up using them once in a blue moon even if they're programmed in every radio.
As far as the RRDB is concerned, unless there's convincing evidence that a frequency is not capable of being used anymore (i.e. no longer programmed and/or no hardware to support such frequencies), we leave them alone. That's our official policy.
I have no issue with removing dead entries from the RRDB if they can be confirmed per the above criteria. Otherwise, it's best to just leave them be. Users of the database are free to lock out, delete, or simply not program anything they don't care to scan.
See, the thing is, while PJ VAC may only use 46.04 once every couple of years, the minute we remove it from the database and they use it, we'll get complaints that we removed a valid frequency. :roll:
There's a guy in a neighboring state who is always gung ho about getting every entry he feels is no longer useful removed from the RRDB. He's made it his crusade on this site, and frankly, it gets old fast. He seems to believe that the day an agency starts using a trunked system, for example, that they must've completely abandoned all of their conventional frequencies. Those of us who operate in the real world know that's hardly ever the case, and while old frequencies may hardly ever be used, if the potential exists then there's really no harm in leaving them in the database. You never know what might pop up one day that will surprise you. :wink:
As far as the RRDB is concerned, unless there's convincing evidence that a frequency is not capable of being used anymore (i.e. no longer programmed and/or no hardware to support such frequencies), we leave them alone. That's our official policy.
I have no issue with removing dead entries from the RRDB if they can be confirmed per the above criteria. Otherwise, it's best to just leave them be. Users of the database are free to lock out, delete, or simply not program anything they don't care to scan.
See, the thing is, while PJ VAC may only use 46.04 once every couple of years, the minute we remove it from the database and they use it, we'll get complaints that we removed a valid frequency. :roll:
There's a guy in a neighboring state who is always gung ho about getting every entry he feels is no longer useful removed from the RRDB. He's made it his crusade on this site, and frankly, it gets old fast. He seems to believe that the day an agency starts using a trunked system, for example, that they must've completely abandoned all of their conventional frequencies. Those of us who operate in the real world know that's hardly ever the case, and while old frequencies may hardly ever be used, if the potential exists then there's really no harm in leaving them in the database. You never know what might pop up one day that will surprise you. :wink:
- Status
Similar threads
BCD325P2/BCD996P2:
HELP: BCD996P2 after power failure during firmware update
