Date   

Re: Member comment period - 146.74_K7KFL_Packwood_3237

Kenny Richards
 

Update on the questions Andrew raised about the 146.74 / K7KFM coordination.
  • The input frequency on the TDS was recorded wrong and it unfortunately wasn't caught during all the review process. The system is correctly using 146.14 Mhz input, which is the expected 0.60 offset) I have fixed the entry in the database.
  • This particular coordination is a little special, since the trustee is co-channeling with their own coordination, which is why there are two entries in the database for almost the same system. 
  • The system has completed the coordination process, but I mistakenly didn't flip the coordination to approved in the database after the public comment period. This has been also fixed now.

Thanks!
Kenny 


Re: Member comment period - 146.74_K7KFL_Packwood_3237

Kenny Richards
 

Andrew,

Lets take this offline to discuss and figure out. We can report back...

Thanks

Kenny


Re: Member comment period - 146.74_K7KFL_Packwood_3237

andrew@...
 

Hi Rob,

In the database, this is still shown as pending, but it also has a wrong input frequency of 146.6600 (wrong offset -0.08).
It matches a no longer pending entry with a different callsign K7KFM which also shows the same wrong input / offset, but shows a different location and different input tone.

Kind regards,
Andrew Jorgensen - KC7RBW


WWARA General Meeting this Saturday 2/25 at 10am

Doug Kingston
 

Scott's subject line is misleading - this meeting is in February on the Saturday, 25th.

On Tue, Feb 21, 2023 at 11:44 PM Scott Honaker <scott.n7ss@...> wrote:
WWARA General Member Virtual Meeting is this Saturday at 10am.

The agenda can be found at 2023 February General Meeting Agenda.docx

See you Saturday,

Scott Honaker, N7SS

Topic: WWARA Quarterly Meeting
Time: Feb 25, 2023 10:00 PM Pacific Time (US and Canada)

Join Zoom Meeting
https://us02web.zoom.us/j/84390986498?pwd=cmwyMzBZWUFKNGtPMEpUV0wvamQvdz09

Meeting ID: 843 9098 6498
Passcode: 146920
One tap mobile
+12532050468,,84390986498#,,,,*146920# US
+12532158782,,84390986498#,,,,*146920# US (Tacoma)

Dial by your location
        +1 253 205 0468 US
        +1 253 215 8782 US (Tacoma)
        +1 669 900 6833 US (San Jose)
        +1 719 359 4580 US
        +1 346 248 7799 US (Houston)
        +1 669 444 9171 US
        +1 507 473 4847 US
        +1 564 217 2000 US
        +1 646 931 3860 US
        +1 689 278 1000 US
        +1 929 436 2866 US (New York)
        +1 301 715 8592 US (Washington DC)
        +1 305 224 1968 US
        +1 309 205 3325 US
        +1 312 626 6799 US (Chicago)
        +1 360 209 5623 US
        +1 386 347 5053 US
Meeting ID: 843 9098 6498
Passcode: 146920
Find your local number: https://us02web.zoom.us/u/kdRM86DS7g


WWARA General Meeting this Saturday 3/25 at 10am

Scott Honaker
 

WWARA General Member Virtual Meeting is this Saturday at 10am.

The agenda can be found at 2023 February General Meeting Agenda.docx

See you Saturday,

Scott Honaker, N7SS

Topic: WWARA Quarterly Meeting
Time: Feb 25, 2023 10:00 PM Pacific Time (US and Canada)

Join Zoom Meeting
https://us02web.zoom.us/j/84390986498?pwd=cmwyMzBZWUFKNGtPMEpUV0wvamQvdz09

Meeting ID: 843 9098 6498
Passcode: 146920
One tap mobile
+12532050468,,84390986498#,,,,*146920# US
+12532158782,,84390986498#,,,,*146920# US (Tacoma)

Dial by your location
        +1 253 205 0468 US
        +1 253 215 8782 US (Tacoma)
        +1 669 900 6833 US (San Jose)
        +1 719 359 4580 US
        +1 346 248 7799 US (Houston)
        +1 669 444 9171 US
        +1 507 473 4847 US
        +1 564 217 2000 US
        +1 646 931 3860 US
        +1 689 278 1000 US
        +1 929 436 2866 US (New York)
        +1 301 715 8592 US (Washington DC)
        +1 305 224 1968 US
        +1 309 205 3325 US
        +1 312 626 6799 US (Chicago)
        +1 360 209 5623 US
        +1 386 347 5053 US
Meeting ID: 843 9098 6498
Passcode: 146920
Find your local number: https://us02web.zoom.us/u/kdRM86DS7g


Re: 2M Band Plan

Tony Brocato-AE7WZ
 

Thanks to you to Kenny for all the work on the plan.


On Mon, Jan 2, 2023 at 11:10, Kenny Richards
<kenny@...> wrote:
Thanks Stephen, I'll just add a little more context to your great response.

Tony - The term 'weak signal' is a common definition for communication efforts which occur over a great distance, it refers to the signal being received, not sent. As Stephen pointed out, it is VERY common for hams engaged in this type of VHF/UHF activities to use very high power. For reference, here is a great ARRL definition/article for VHF/UHF Weak Signal communication. http://www.arrl.org/weak-signal-vhf-dx-meteor-scatter-eme-moonbounce

Thanks
Kenny


Re: 2M Band Plan

Tony Brocato-AE7WZ
 

Thanks for the great explanation.Stephen.


On Mon, Jan 2, 2023 at 11:03, Stephen W9SK
<stephen@...> wrote:

QRO is typically used for “weak signal” as that is required for EME, often Aurora, DX, etc, in order for the Rx end to hear what is inevitably a very weak signal.  Typically, weak signal VHF/UHF is SSB phone, CW, and certain digital modes (eg inc in WSJT-X).  More on all that can be found among the weak signal enthusiasts at PNW VHF Society (PNWVHFS.org), whose members are typically not your typical FM repeater users.

 

Stephen W9SK

 

 

From: wwara@groups.io <wwara@groups.io> On Behalf Of Tony Brocato-AE7WZ via groups.io
Sent: Sunday, January 01, 2023 10:16 PM
To: wwara@groups.io
Subject: Re: [wwara] 2M Band Plan

 

Hi Everyone and Happy New Year.
Just a comment- Preface first-The xls file shows 144.0-144.3 to be "weak signal", for which I did not find a definition.
Part 97 designates 144.0-144.1 for CW use exclusively and I did not see any transmitter power restrictions. I would not consider 1500 watts CW to be "weak signal". It might burn a hole in my roof LOL.
I think this area of the plan needs a little clarification regarding use.
If I am missing something here, I can stand correction.
Thank you,
Tony
AE7WZ


Re: 2M Band Plan

Scott Honaker
 

This is a good question and I have seen quite a bit of confusion on various forums.  Part of our issue is that we only coordinate repeater sub bands so there are areas of the band that are beyond our scope.  We don't want to appear to be regulating or defining it in any restrictive way.  Is there a good definition of "weak signal" we could add as a footnote?

Scott N7SS

On Mon, Jan 2, 2023 at 11:03 AM Stephen W9SK <stephen@...> wrote:

QRO is typically used for “weak signal” as that is required for EME, often Aurora, DX, etc, in order for the Rx end to hear what is inevitably a very weak signal.  Typically, weak signal VHF/UHF is SSB phone, CW, and certain digital modes (eg inc in WSJT-X).  More on all that can be found among the weak signal enthusiasts at PNW VHF Society (PNWVHFS.org), whose members are typically not your typical FM repeater users.

 

Stephen W9SK

 

 

From: wwara@groups.io <wwara@groups.io> On Behalf Of Tony Brocato-AE7WZ via groups.io
Sent: Sunday, January 01, 2023 10:16 PM
To: wwara@groups.io
Subject: Re: [wwara] 2M Band Plan

 

Hi Everyone and Happy New Year.
Just a comment- Preface first-The xls file shows 144.0-144.3 to be "weak signal", for which I did not find a definition.
Part 97 designates 144.0-144.1 for CW use exclusively and I did not see any transmitter power restrictions. I would not consider 1500 watts CW to be "weak signal". It might burn a hole in my roof LOL.
I think this area of the plan needs a little clarification regarding use.
If I am missing something here, I can stand correction.
Thank you,
Tony
AE7WZ


Locked Re: 14 Day comment period for three 220 Mhz repeater applications

Kenny Richards
 

The public comment period is closed, these systems will now be coordinated.

Thanks

Kenny


Re: 2M Band Plan

Kenny Richards
 

Thanks Stephen, I'll just add a little more context to your great response.

Tony - The term 'weak signal' is a common definition for communication efforts which occur over a great distance, it refers to the signal being received, not sent. As Stephen pointed out, it is VERY common for hams engaged in this type of VHF/UHF activities to use very high power. For reference, here is a great ARRL definition/article for VHF/UHF Weak Signal communication. http://www.arrl.org/weak-signal-vhf-dx-meteor-scatter-eme-moonbounce

Thanks
Kenny


Re: 2M Band Plan

Stephen W9SK
 

QRO is typically used for “weak signal” as that is required for EME, often Aurora, DX, etc, in order for the Rx end to hear what is inevitably a very weak signal.  Typically, weak signal VHF/UHF is SSB phone, CW, and certain digital modes (eg inc in WSJT-X).  More on all that can be found among the weak signal enthusiasts at PNW VHF Society (PNWVHFS.org), whose members are typically not your typical FM repeater users.

 

Stephen W9SK

 

 

From: wwara@groups.io <wwara@groups.io> On Behalf Of Tony Brocato-AE7WZ via groups.io
Sent: Sunday, January 01, 2023 10:16 PM
To: wwara@groups.io
Subject: Re: [wwara] 2M Band Plan

 

Hi Everyone and Happy New Year.
Just a comment- Preface first-The xls file shows 144.0-144.3 to be "weak signal", for which I did not find a definition.
Part 97 designates 144.0-144.1 for CW use exclusively and I did not see any transmitter power restrictions. I would not consider 1500 watts CW to be "weak signal". It might burn a hole in my roof LOL.
I think this area of the plan needs a little clarification regarding use.
If I am missing something here, I can stand correction.
Thank you,
Tony
AE7WZ


Re: 2M Band Plan

Tony Brocato-AE7WZ
 

Hi Everyone and Happy New Year.
Just a comment- Preface first-The xls file shows 144.0-144.3 to be "weak signal", for which I did not find a definition.
Part 97 designates 144.0-144.1 for CW use exclusively and I did not see any transmitter power restrictions. I would not consider 1500 watts CW to be "weak signal". It might burn a hole in my roof LOL.
I think this area of the plan needs a little clarification regarding use.
If I am missing something here, I can stand correction.
Thank you,
Tony
AE7WZ


Re: 2M Band Plan

Rob Chatham
 

Hurray and Congratulations!
Believe it or not it has been over ten years and finally we have a revised two meter band plan.
Thank You for all of the hard work and performing a monumental task.
Rob
AF7PR


On Dec 26, 2022, at 9:34 PM, Kenny Richards <kenny@...> wrote:

Scott,

I finally had a chance to step through the latest version of the 2m band plan spreadsheet, here are my few notes.

1) Question about how to handle the wide-band shared non-protected pairs?
My recommendation is that we convert one of them to SNP narrowband immediately, creating another opportunity for narrowband systems. Then be sure to incorporate the remaining wide-band SNP into the final plans for when the final migration to narrowband occurs down the road.

2) Can we incorporate the two commonly used packet radio frequencies used in WWA into the band plan? I never figured out how 144.39 was OK since it is in the middle of the OSCAR sub-band, but that is the accepted 1200 baud frequency in the US. I'd also request adding 144.35 for 9600 baud.

3) Since we ditched the Ultra Narrowband Digital pair #1 (146.005 / 146.605) due to the overlap with the cross-band linking frequency (146.600), I'd relabel the Special Ultra-Narrowband Prt pair #2, dropping the #2. Can we also be sure to label the Ultra-Narrowband Digital pair as being 6.25 kHz wide though?

Unless more feedback comes in, I'd recommend putting this to a vote at the next general meeting and making it official. I think it is a big improvement over the current band plan. I hope someone will volunteer to tackle the remaining bands.

Thanks
Kenny


Re: 2M Band Plan

Kenny Richards
 

Scott,

I finally had a chance to step through the latest version of the 2m band plan spreadsheet, here are my few notes.

1) Question about how to handle the wide-band shared non-protected pairs?
My recommendation is that we convert one of them to SNP narrowband immediately, creating another opportunity for narrowband systems. Then be sure to incorporate the remaining wide-band SNP into the final plans for when the final migration to narrowband occurs down the road.

2) Can we incorporate the two commonly used packet radio frequencies used in WWA into the band plan? I never figured out how 144.39 was OK since it is in the middle of the OSCAR sub-band, but that is the accepted 1200 baud frequency in the US. I'd also request adding 144.35 for 9600 baud.

3) Since we ditched the Ultra Narrowband Digital pair #1 (146.005 / 146.605) due to the overlap with the cross-band linking frequency (146.600), I'd relabel the Special Ultra-Narrowband Prt pair #2, dropping the #2. Can we also be sure to label the Ultra-Narrowband Digital pair as being 6.25 kHz wide though?

Unless more feedback comes in, I'd recommend putting this to a vote at the next general meeting and making it official. I think it is a big improvement over the current band plan. I hope someone will volunteer to tackle the remaining bands.

Thanks
Kenny


Locked Re: Member comment period - 441.500_AF7UX_Monroe_5775

Kenny Richards
 

Due to an oversight, this coordinations public comment period was never officially closed. Having no issues raised, the public comment period is now closed and the coordination will be issued.

Thanks
Kenny


Locked Re: Member comment period - 224.18_W7SKY_Sultan_4103

Kenny Richards
 

The issue Stan-K7DKK brought up was resolved offline, the public comment period is now closed and the coordination will be issued.

Thanks
Kenny


Locked Re: Member comment period - 441.225_K7SLB_Seattle_5762

Kenny Richards
 

There was an offline discussion with Karl and his concerns were addressed. The public comment period is now closed and this system will be coordinated.

Thanks
Kenny


Locked Re: Member comment period - 443.300_W7PLU_PacificCollege_5781

Kenny Richards
 

The public comment period is closed, this system will now be coordinated.

Thanks


Locked Re: Member comment period - 442.0750_K7NWS_TigerMntWest_5774

Kenny Richards
 

The public comment period is closed, this system will now be coordinated.

Thanks


Locked Re: Member comment period - 147.4625_NW7DR_Kingston_3235

Kenny Richards
 

The public comment period is closed, this system will now be coordinated.

Thanks
Kenny