GRD

Global Frequency Database

Thursday, May 16, 2024

Ham Radio - House Bill changes to keep things running for Hams.

AG03 QST de W1AW 

ARLB003 >From ARRL Headquarters Newington CT 
May 15, 2024 


To all radio amateurs SB QST ARL ARLB003 ARLB003 Senate Bill S.3690 Introduced to Eliminate Private Land Use Restrictions on Amateur Radio On January 30, 2024, US Senators Roger Wicker (MS) and Richard Blumenthal (CT) introduced S.3690, the Senate companion bill to H.R.4006, introduced last June. 

Both bills reflect the Congressional campaign efforts by the ARRL to eliminate homeowner association land use restrictions that prohibit, restrict, or impair the ability of an Amateur Radio Operator to install and operate amateur station antennas on residential properties they own. The text of bill S.3690 can be found at, https://www.congress.gov/bill/118th-congress/senate-bill/3690/text . 

Amateur Radio Operators repeatedly are relied upon to provide essential communications when disaster strikes, but their ability to do so is being impaired by the exponential growth of residential private land use restrictions that hinder their ability to establish stations in their homes with which to train and provide emergency communications when called upon. 
 In announcing the introduction of S.3690, Senator Wicker said: 'Because communication during natural disasters is often hindered, we should be making every attempt to give folks more options. <br>Reliable access can make the difference between life and death in an emergency. Our legislation removes roadblocks for amateur radio operators looking to help their friends, families, and neighbors.' 


In a similar announcement, Senator Blumenthal stated: 'Our measure will help clarify the rules so ham radio enthusiasts can successfully continue their communications. In the face of emergency or crisis, they help provide vital, life-saving information that allow listeners to properly and safely respond, but prohibitive home association rules and confusing approval processes for installing antennas have been an unnecessary impediment. 

The Amateur Radio Emergency Preparedness Act resolves these bottlenecks and ensures that radio operators can function successfully.' ARRL President Rick Roderick, K5UR, and Director John Robert Stratton, N5AUS, Chair of the ARRL's Government Affairs Committee, both extended on behalf of ARRL, its Members, and the Amateur Radio community their thanks and appreciation for the leadership of Senator Wicker and Senator Blumenthal in their continuing efforts to support and protect the rights of all Amateur Radio Operators.

Tuesday, October 4, 2016

Using Vagrant for Virtual Machines for Ham Radio or Radio Listening software SDR Radio

https://www.vagrantup.com/docs/getting-started/boxes.html USING A BOX Now that the box has been added to Vagrant, we need to configure our project to use it as a base. Open the Vagrantfile and change the contents to the following: Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" end The "hashicorp/precise64" in this case must match the name you used to add the box above. This is how Vagrant knows what box to use. If the box was not added before, Vagrant will automatically download and add the box when it is run. You may specify an explicit version of a box by specifying config.vm.box_version for example: Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" config.vm.box_version = "1.1.0" end You may also specify the URL to a box directly using config.vm.box_url: Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" config.vm.box_url = "http://files.vagrantup.com/precise64.box" end WHY VAGRANT? Vagrant provides easy to configure, reproducible, and portable work environments built on top of industry-standard technology and controlled by a single consistent workflow to help maximize the productivity and flexibility of you and your team. To achieve its magic, Vagrant stands on the shoulders of giants. Machines are provisioned on top of VirtualBox, VMware, AWS, or any other provider. Then, industry-standard provisioning tools such as shell scripts, Chef, or Puppet, can be used to automatically install and configure software on the machine. HOW VAGRANT BENEFITS YOU If you are a developer, Vagrant will isolate dependencies and their configuration within a single disposable, consistent environment, without sacrificing any of the tools you are used to working with (editors, browsers, debuggers, etc.). Once you or someone else creates a single Vagrantfile, you just need to vagrant up and everything is installed and configured for you to work. Other members of your team create their development environments from the same configuration, so whether you are working on Linux, Mac OS X, or Windows, all your team members are running code in the same environment, against the same dependencies, all configured the same way. Say goodbye to "works on my machine" bugs. If you are an operations engineer, Vagrant gives you a disposable environment and consistent workflow for developing and testing infrastructure management scripts. You can quickly test things like shell scripts, Chef cookbooks, Puppet modules, and more using local virtualization such as VirtualBox or VMware. Then, with the same configuration, you can test these scripts on remote clouds such as AWS or RackSpace with the same workflow. Ditch your custom scripts to recycle EC2 instances, stop juggling SSH prompts to various machines, and start using Vagrant to bring sanity to your life. If you are a designer, Vagrant will automatically set everything up that is required for that web app in order for you to focus on doing what you do best: design. Once a developer configures Vagrant, you do not need to worry about how to get that app running ever again. No more bothering other developers to help you fix your environment so you can test designs. Just check out the code, vagrant up, and start designing.

New Hams. passing test like its nothing. By studying only the answer. NOT the why!! FRS/CB?

It bothers me the way new hams are memorizing the answers and have no idea why or what anything means. When I took my General I studied for a few weeks, Didnt look at the questions, just studied the material. Soaked it in, then new bands, 60m wanted to know why it was channelized who we were sharing it with. Stuff like that. I just barely passed the test. But some kid behind be was so excited he passed not missing one. He used hamstudy basiclly he memorized all the answers and that was ok. Its ok with every ham out there. Know one cares, we just want our numbers up. Come one come all, we dont care how you pass. Why even make them take the test? Just pay fee and get a callsign. It is really frustrating to me. Todays Rant

Monday, June 24, 2013

The Utah VHF Society provides Frequency Coordination within the state of Utah and is also a member of the National Frequency Coordination Committee (NFCC) - an organization that provides a framework of standards and practices referenced by local frequency coordination entities.  The frequency coordinator in Utah is an elected position, chosen at the meeting associated with the VHF Society Swap meet.

The purpose of a frequency coordination body is to facilitate reasonable usage of the VHF, UHF, and microwave-band amateur frequencies.  The frequency coordinator acts as a clearinghouse for information pertaining to repeaters (their frequencies and locations) as well as radio links, interference issues, and other technical information.

It is the strong recommendation of the FCC (refer for part 97.201 for an example,) the ARRL, and many other organizations, that amateurs follow the recommendations of the frequency coordinators in their areas.  Doing so allows for better utilization of our valuable spectrum, prevents problems before they arise, and provides a vehicle for the resolution of disputes and other problems should they arise.  Recently, the FCC reaffirmed the importance of frequency coordination on our increasingly congested frequencies:  Read about the FCC's statements - and several follow-ups - here.

If you wish to put up something like a repeater, an autopatch, or do some other sort of operation on our VHF, UHF, or Microwave bands that is "out of the ordinary" (i.e. not the usual repeater ragchew or simplex operation) then it is strongly suggested that you contact the frequency coordinator.  The frequency you choose may already be in use as a link, a repeater input, or something else and unconsidered operation on that frequency could adversely impact operations in your area, or an adjacent area into which your signals may overlap.


Please note:  The online repeater directory does not include link, control, auxiliary, as well as other frequencies that are not in the public database.  If you are considering using a frequency, please contact the frequency coordinator prior to commencing operation.  Just because a frequency does not appear to be used in your area, that doesn't mean that operation on that frequency in your area will not cause interference!


For further reference, please refer to the following  pages: 

Coordinating coordination with other coordinators:

Radio signals do not respect state boundaries.  Therefore, if you are putting together a system that has coverage in an adjacent state(s), or if you are in an adjacent state and your system is going to cover at least a portion of Utah then the coordinators in the relevant areas of Wyoming, Idaho, Nevada, Arizona, New Mexico and/or Colorado need to be notified.

When someone requests coordination of a Utah repeater that has the potential of causing interference with a repeater in a bordering state, the Frequency Coordinator will always check with the coordinator(s) in the state(s) that may be affected:  The person doing the coordination need not contact them as well - in fact, keeping a "single point of contact" may eliminate some confusion and possible coordination delays

If you are unsure as to whether you need to "coordinate" with other coordinators, contact your local frequency coordinator for advice!

  • Go to the Utah Bandplan page to find out what modes are operated where on the VHF/UHF bands.  Please read the notes on this page concerning Utah's implementation of the bandplan.
  • A list of  simplex frequencies and how they are often used may be found online here.    Please read the notice at the top of this page concerning the use of simplex frequencies.
  • The Online Utah Repeater Directory shows what repeaters are currently on the air, those that are temporarily off the air, and those that are being planned.

Questions, updates, or comments pertaining to this web page may be directed to:   uvhfs@utahvfs.org

Return to the  Utah VHF Society home page.
 

The General Mobile Radio Service (GMRS) is a North American land-mobile FM UHF radio service designed for short-distance two-way communication. It requires a license in United States but can be used license-free in Canada. The United States permits use by an adult individual who possesses a valid GMRS license, as well as his or her immediate family members.[1] Immediate relatives of the GMRS system licensee are entitled to communicate among themselves for personal or business purposes, but employees of the licensee, who are not family members, are not covered by the same license. GMRS radios are typically handheld portable devices much like Family Radio Service (FRS) radios, and share the FRS frequency band near 462 and 467 MHz. Mobile and base station-style radios are available as well, but these are normally commercial UHF radios as often used in the public service and commercial land mobile bands. These are legal for use in this service as long as they are GMRS type-approved. They are more expensive than the walkie talkies typically found in discount electronics stores, and are generally considered higher quality.
[00:44:16][FRQ 05732000][SND][ ][TWS][N05 ][AL0] BER 24 SN 05 [00:43:44][FRQ 11494000][SND][ ][TWS][J26 ][AL0] BER 30 SN 06 [00:43:44][FRQ 10242000][SND][ ][TWS][J26 ][AL0] BER 30 SN 05 [00:43:35][FRQ 08912000][SND][ ][TWS][J26 ][AL0] BER 30 SN 06 [00:43:30][FRQ 08912000][SND][ ][TWS][J26 ][AL0] BER 25 SN 04

Tuesday, November 16, 2010

COTHEN Nov 16th

[00:52:27][FRQ 08912000][SND][ ][TWS][J11 ][AL0] BER 27 SN 04 ---> J11 USCG MH-60J #6011 CGAS Cape Cod
[00:52:24][FRQ 08912000][SND][ ][TWS][J11 ][AL0] BER 25 SN 04
[00:49:32][FRQ 08912000][TO ][J26 ][TIS][LNT ][AL0] BER 30 SN 14 --> LNT USCG CAMSLANT Chesapeake, VA
[00:45:13][FRQ 08912000][SND][ ][TWS][N05 ][AL0] BER 22 SN 05
[00:45:00][FRQ 07527000][SND][ ][TWS][N05 ][AL0] BER 23 SN 04 --> N05 USCG HC-144A #2305 ATC Mobile
[00:44:16][FRQ 05732000][SND][ ][TWS][N05 ][AL0] BER 24 SN 05
[00:43:44][FRQ 11494000][SND][ ][TWS][J26 ][AL0] BER 30 SN 06
[00:43:44][FRQ 10242000][SND][ ][TWS][J26 ][AL0] BER 30 SN 05
[00:43:35][FRQ 08912000][SND][ ][TWS][J26 ][AL0] BER 30 SN 06
[00:43:30][FRQ 08912000][SND][ ][TWS][J26 ][AL0] BER 25 SN 04
[00:43:05][FRQ 07527000][SND][ ][TWS][J26 ][AL0] BER 21 SN 06

http://rangerdude.com/drupal/cothen-11-16-2010

Thursday, November 11, 2010

No VOLMET NY... ???

A0667/10 - QXXXX DUE TO TRANSMITTER REPLACEMENT AT THE BARNEGAT, NEW JERSEY, USA SITE, THERE WILL BE NO VOLMET SERVICE AVAILABLE FROM THIS LOCATION BETWEEN OCTOBER 12, AND NOVEMBER 18, 2010. 12 OCT 00:00 2010 UNTIL 18 NOV 23:59 2010. CREATED: 22 SEP 12:10 2010

New York Volmet shares its frequencies below with Gander NF Volmet.
Frequencies: 3485.0 6604.0 10051.0 13270.0 kHz

Friday, November 5, 2010

11/4 COTHEN ALE

[02:39:40][FRQ 05732000][SND][ ][TWS][D45 ][AL0] BER 26 SN 05
[02:38:29][FRQ 07527000][TO ][LNT ][TWS][J27 ][AL0] BER 29 SN 05
[02:37:43][FRQ 07527000][TO ][LNT ][TIS][J27 ][AL0] BER 27 SN 05
[02:37:34][FRQ 07527000][TO ][LNT LNS ][TIS][J27 ][AL0] BER 17 SN 04
[02:36:26][FRQ 08912000][SND][ ][TWS][D70 ][AL0] BER 0 SN 00
[02:36:26][FRQ 07527000][SND][ ][TWS][D70 ][AL0] BER 26 SN 06
[02:36:25][FRQ 05732000][SND][ ][TWS][D70 ][AL0] BER 27 SN 05
[02:30:25][FRQ 05732000][TO ][J27 ][TIS][LNT ][AL0] BER 22 SN 05
[02:30:23][FRQ 05732000][TO ][LNT ][TIS][J27 ][AL0] BER 30 SN 09
[02:30:21][FRQ 05732000][TO ][J27 ][TIS][LNT ][AL0] BER 29 SN 08
[02:25:47][FRQ 05732000][SND][ ][TWS][VES ][AL0] BER 27 SN 04
[02:25:34][FRQ 05732000][SND][ ][TWS][VES ][AL0] BER 23 SN 07
[02:22:30][FRQ 05732000][SND][ ][TWS][D31 ][AL0] BER 12 SN 04
[02:18:11][FRQ 07527000][SND][ ][TWS][I43 ][AL0] BER 30 SN 06
[02:16:43][FRQ 05732000][SND][ ][TWS][D07 ][AL0] BER 27 SN 05
[02:04:02][FRQ 05732000][TO ][LNT J27 ][TIS][LNT ][AL0] BER 24 SN 08
[02:04:00][FRQ 05732000][TO ][LNT ][TIS][J27 ][AL0] BER 27 SN 10
[02:03:57][FRQ 05732000][TO ][J27 ][TIS][LNT ][AL0] BER 29 SN 06
[01:58:17][FRQ 05732000][TO ][J27 ][TIS][LNT ][AL0] BER 30 SN 05
[01:58:15][FRQ 05732000][TO ][LNT ][TIS][J27 ][AL0] BER 27 SN 07
[01:58:12][FRQ 05732000][TO ][J27 ][TIS][LNT ][AL0] BER 30 SN 11
[01:55:24][FRQ 08912000][SND][ ][TWS][D45 ][AL0] BER 28 SN 09
[01:55:23][FRQ 07527000][SND][ ][TWS][D70 ][AL0] BER 30 SN 08
[01:54:18][FRQ 05732000][SND][ ][TWS][D45 ][AL0] BER 30 SN 05
[01:40:39][FRQ 08912000][SND][ ][TWS][D31 ][AL0] BER 30 SN 05
[01:37:30][FRQ 07527000][SND][ ][TWS][D31 ][AL0] BER 25 SN 04
[01:34:08][FRQ 13312000][SND][ ][TWS][I43 ][AL0] BER 28 SN 03
[01:33:51][FRQ 12222000][SND][ ][TWS][I43 ][AL0] BER 23 SN 03
[01:25:09][FRQ 05732000][SND][ ][TWS][VES ][AL0] BER 30 SN 06
[01:22:52][FRQ 08912000][SND][ ][TWS][VES ][AL0] BER 27 SN 05
[01:22:52][FRQ 07527000][SND][ ][TWS][VES ][AL0] BER 29 SN 04
[01:22:38][FRQ 07527000][SND][ ][TWS][VES ][AL0] BER 17 SN 05