Re: Feedback and comments
My 2 cents:
1. David should be the prototype for 13C coordinators. Always a positive and encouraging attitude and stayed right on top of things. We are very fortunate!
2. Jammers: Many already know this, but the only way to get rid of jammers is to make them realize that they are not being effective. I only ran into serious ones on phone. Fortunately the auto notch in the radio eliminated the carrier. I was able to work several stations even though sensitivity was taking a hit. When I couldn't hear anyone else, I continued making "phantom" QSOs (or were they?) until the idiot moved on to more fertile ground. I never had one hang around more than a minute or two. Bottom line, continue to sound like you're having a great time. That is an almost universal turn-off for such silly people.
3. SSB Pileups: I had quite a few and they were a blast. Almost everyone was respectful and well behaved, which made things really easy and fun. One technique I used when things got too crazy was calling by call area number, especially in conjunction with current beam heading. The key is to manage the pileup so that folks can hear that you realize their time is important to them, and that you know what you're doing. It's possible to be friendly, courteous, and FAST - it just takes some practice. IMO we only exist to hand out QSOs to as many interested folks as possible and I try to operate accordingly. Others have different opinions and I respect them, but that one works for me. It's also the most fun for me (enlightened self-interest?).
4. CW Pileups: They can be more problematic because of the zero beat problem created by the "click and call" gang. When I teach new hams I always stress that you must listen before you transmit, but there are thousands of hams that have not taken one of my classes ?. I was on the verge of going split a couple of times, but I was able to work through the pile.
5. Having fun: most of the folks you work will mimic your attitude. If you are crisp, efficient, polite and just sound happy, most of the folks calling you will feed off that positive energy.
I had a great time this year thanks to David, the whole K2B team, and the hundreds of hams I worked in my shifts.
I'll be back for more next year!
Thanks team!
Rick
N1RM
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of David Wright via groups.io Sent: Friday, July 08, 2022 1:22 PM To: [email protected]Subject: [K2B-13Colonies2022] Feedback and comments Thanks, I wanted to start a separate thread for any comments or suggestions. So this one is fine! Here's what 13 Colonies web site says for exchange: The exchange for this event is: CALL SIGN RS / RST / RSQ STATE / PROVINCE or COUNTRY Sometimes I asked for name; usually, people volunteered it, so I did also. I think the one-hour time slot is a fantastic idea. I was going to recommend that myself. Not because of commitment(s), but because two hours can be physically grueling. On 20 meters, with jammers, guys plopping down 1 Khz away, weak signals fading in and out, DX calling off the back of the beam. Not to mention the pile-ups. Tnxs also on the spreadsheet idea. David, K2WPM K2B Coordinator ¨C 13 Colonies -----Original Message----- From: [email protected] < [email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 12:45 PM To: [email protected]Subject: [K2B-13Colonies2022] Feedback and comments This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David. ---------- TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up. Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy. ---------- SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet. For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible. This is a standard operation in most spreadsheets. Here's an article: <> ---------- SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it? Comments, anyone? -- 73, Mike N4CF Louisa County, VA USA Elecraft K4d / KPA500 / KAT500 Carolina Windom up 45'
|
Not sure if people monitor QRZ. But there's a thread there for 13 Colonies, and an op from SC was complaining about on-air discourtesies for other K2* stations. I wrote:
I found 99.5% courtesy and good old fashioned great hams.
Yeah, there is that .5% ... that's when I turn up the Mercury III a few notches, and they usually go away.
Especially 20 meters, a pretty rough neighborhood.
But I don't like seeing this wonderful special event turning into a contest of state versus state.
And no, I don't give a rat's behind that NC "won." I like to see a nice close bunching, like last year.
Wondering if anyone has suggestions for making this less state versus state, and maybe something more akin to us working together ... like we did at the beginning of this whole experiment called the United States.
By the way, the DX stations are also getting into this. While on 20 SSB with the beam pointed West, I was called by -- and made contacts with -- Norway, Sweden, Latvia, Poland, Belgium, Netherlands, Germany, France, England, Wales, Northern Ireland, Italy, Spain, Portugal, Switzerland, Cyprus, Malta, Mexico, Brazil, Venezuela and Montserrat, Barbados, Trinidad & Tobago, Cuba. Lots more that I couldn't hear ... guys were whining at me "answer the DX." Maybe that's an angle, see if the 13 Colonies can do DXCC in a week?
David, K2WPM
K2B Virginia Coordinator 13 Colonies Special Event
|
N4PD 2022 log attached. Stations with "**" in name column (usually a
13 Colonies station) were worked using my callsign, N4PD.? You can
strip those log entries out. All the rest were worked as K2B.
On 7/8/2022 07:06, David Wright wrote:
toggle quoted message
Show quoted text
Thanks to all for a great week.
Really nice to see folks fill in those slots July 7.
Can you please forward me your logs, at your earliest?? Can you
add your call to file name; adif is easiest, but I can pretty much
do any format.
I have to get the numbers to Ken by Monday.
I will circulate a summary next week, showing how we all did, and
compared to the other colonies.
David, K2WPM
|
Re: Feedback and comments
Definitely not you, Stu. Two weeks ago a storm took down my 80m dipole so I never listened to 80m.?? Next time I will have an 80m antenna up to give you 80m cw ops some help.
73, George K4GM
toggle quoted message
Show quoted text
On 7/8/2022 3:02 PM, Stu2 - W7IY wrote: I might have been the overlapping operator on 80M. When I started the next slot was open so I just kept going after 7-9 shift. Sorry about that, if it was me. I should have stopped and doubled checked that the slot wasn't filled. Oh well - next time.
Band conditions were terrible, which caused me to abandon the whole two hour slot. So perhaps one hour time slots would work better. You can always sign up for two.
Roger on the name issue. I never sent my name.
Good time as usual and I hope to do this next year.
73, Stu2, W7IY
On 7/8/22 14:39, George Marzloff wrote:
I agree with Mike on locking the first row on the spreadsheet.?? I locked it on the second day.?? Then I noticed a day or so later someone had unlocked it (what possible reason????)?? Anyway,? I locked it again.? It is currently locked. Test it to make sure. Possibly the lock is only local? I hope not.
I like 1 hour time slots. I kinda made 'em that way as I worked. Only twice was I able to go two hours straight.? Usually, I worked an hour max. I just entered 10:15-11:00, for example,? in an empty slot.
Not once did I give my name.?? I received names twice...?? I vote thumbs up on NO NAME!!
One cause for concern was duplication of mode/band operation. At least twice and maybe three times I saw an open slot on the Sheet. I entered my call.? I got the log up and was ready to go. Then went to DX Summit to self spot and to my surprise another operator had been spotted. I went to the frequency and sure enough I heard K2B! Almost a big OOPS.?? I am not talking about a 5 minute overshoot on the prior hour but 15-30 minutes into the current block.? Doubt there is a simple answer here. Maybe a mandatory check on DX Summit before beginning operation ??? A big notice to double check DX Summit before operation????? These events occurred during the last 2 or 3 days so might be new inexperienced ops... No big deal in the overall scheme of things.??? I had a great time and look forward to next year.
73, George K4GM
On 7/8/2022 12:44 PM, Mike Dodd wrote:
This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David.
----------
TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up.
Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy.
----------
SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet.
For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible.
This is a standard operation in most spreadsheets. Here's an article: <>
----------
SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it?
Comments, anyone?
--
George- Price-Right Communications
107B East Davis St.
Culpeper, VA 22701
540-617-1177
|
Re: Feedback and comments
David:? thanks for your leadership and mentoring throughout the process!? ? I suggest a ¡°drop box¡± like-capability for everybody ?to drop their ADI files to, such that they can ¡°see¡± that their files ?arrived in the drop box and you then have all the files in one place.? I know that Google has an equivalent to the popular drop box (and easier to use I suspect).? It can be password protected, etc.? Something to consider for next year.? ? Mike WA8AHZ ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Craig Szczutkowski via groups.io Sent: Friday, July 8, 2022 3:44 PM To: [email protected]Subject: Re: [K2B-13Colonies2022] Feedback and comments ? This was my first time operating in 13 Colonies and found it very helpful to use the shared spreadsheet and the group/reflector - agree with one hour slots next time, maybe sign up in advance for a max of two successive slots per band, then first come first serve if next time slot is not filled in by the operating time. Checked the shared sheet a few minutes ago and saw that freezing row 1 worked (it has to be set up on each day's worksheet) - nice touch. Re DX Summit checking, I also used the Reverse Beacon site () to check the frequencies K2B was operating CW on before I got on.? This was a good additional check along with DX Summit.? When I was operating (and responses were slow), I used it to see how my signal was getting out (based on spotters' signal strengths). I also like the idea of a chat room for people to share info / ask questions in real time.? But than again, one more site to monitor!? Wonder if Google Chat / Rooms could be helpful? Thanks again to David for the great job coordinating the event, look forward to next year! I agree with Mike on locking the first row on the spreadsheet.?? I
locked it on the second day.?? Then I noticed a day or so later someone
had unlocked it (what possible reason????)?? Anyway,? I locked it
again.? It is currently locked. Test it to make sure. Possibly the lock
is only local?? I hope not.
I like 1 hour time slots. I kinda made 'em that way as I worked. Only
twice was I able to go two hours straight.? Usually, I worked an hour
max. I just entered 10:15-11:00, for example,? in an empty slot.
Not once did I give my name.?? I received names twice...?? I vote thumbs
up on NO NAME!!
One cause for concern was duplication of mode/band operation.? At least
twice and maybe three times I saw an open slot on the Sheet. I entered
my call.? I got the log up and was ready to go. Then went to DX Summit
to self spot and to my surprise another operator had been spotted. I
went to the frequency and sure enough I heard K2B! Almost a big OOPS.??
I am not talking about a 5 minute overshoot on the prior hour but 15-30
minutes into the current block.? Doubt there is a simple answer here.
Maybe a mandatory check on DX Summit before beginning operation ??? A
big notice to double check DX Summit before operation????? These events
occurred during the last 2 or 3 days so might be new inexperienced
ops...? No big deal in the overall scheme of things.??? I had a great
time and look forward to next year.
73, George K4GM
On 7/8/2022 12:44 PM, Mike Dodd wrote:
> This was my first time participating, and I came away with a few
> thoughts I'd like share with the group, and especially with David.
>
> ----------
> TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up
> sheet. Several times I couldn't commit to two hours due to time
> constraints. One-hour slots provide more flexibility and encourage
> signing up.
>
> Look at it this way: Suppose I can't commit to a two-hour session from
> 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now,
> at 7:50, I discover I CAN operate until 9pm, so I open the sheet to
> see if 8-9 is still available. It is, so I sign up and keep on
> operating. Easy-peasy.
>
> ----------
> SUGGESTION: Modify the sign-up sheet to lock the row and column
> headers so they're always visible. On the current sheet, they scroll
> off the screen as I move around the sheet.
>
> For example, if I want to sign up for 20CW at 7-9pm, the band/mode and
> time headers disappear as I tab from cell-to-cell and row-to-row, so I
> don't know which cell to look at. Hheaders should always be visible.
>
> This is a standard operation in most spreadsheets. Here's an article:
> <>
>
> ----------
> SUGGESTION: I think 13 Colonies should eliminate the Name from the
> exchange. Only a few stations ever sent their name, and I didn't even
> know it was part of the exchange until well into the event (OK, I
> didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why
> have it if no one sends it?
>
>
> Comments, anyone?
>
--
George- Price-Right Communications
107B East Davis St.
Culpeper, VA 22701
540-617-1177
|
Re: Feedback and comments
This was my first time operating in 13 Colonies and found it very helpful to use the shared spreadsheet and the group/reflector - agree with one hour slots next time, maybe sign up in advance for a max of two successive slots per band, then first come first serve if next time slot is not filled in by the operating time.
Checked the shared sheet a few minutes ago and saw that freezing row 1 worked (it has to be set up on each day's worksheet) - nice touch.
Re DX Summit checking, I also used the Reverse Beacon site () to check the frequencies K2B was operating CW on before I got on.? This was a good additional check along with DX Summit.? When I was operating (and responses were slow), I used it to see how my signal was getting out (based on spotters' signal strengths).
I also like the idea of a chat room for people to share info / ask questions in real time.? But than again, one more site to monitor!? Wonder if Google Chat / Rooms could be helpful?
Thanks again to David for the great job coordinating the event, look forward to next year!
73,
Craig? N2DA
On Friday, July 8, 2022 at 02:39:36 PM EDT, George Marzloff <countrypool2019@...> wrote:
I agree with Mike on locking the first row on the spreadsheet.?? I
locked it on the second day.?? Then I noticed a day or so later someone
had unlocked it (what possible reason????)?? Anyway,? I locked it
again.? It is currently locked. Test it to make sure. Possibly the lock
is only local?? I hope not.
I like 1 hour time slots. I kinda made 'em that way as I worked. Only
twice was I able to go two hours straight.? Usually, I worked an hour
max. I just entered 10:15-11:00, for example,? in an empty slot.
Not once did I give my name.?? I received names twice...?? I vote thumbs
up on NO NAME!!
One cause for concern was duplication of mode/band operation.? At least
twice and maybe three times I saw an open slot on the Sheet. I entered
my call.? I got the log up and was ready to go. Then went to DX Summit
to self spot and to my surprise another operator had been spotted. I
went to the frequency and sure enough I heard K2B! Almost a big OOPS.??
I am not talking about a 5 minute overshoot on the prior hour but 15-30
minutes into the current block.? Doubt there is a simple answer here.
Maybe a mandatory check on DX Summit before beginning operation ??? A
big notice to double check DX Summit before operation????? These events
occurred during the last 2 or 3 days so might be new inexperienced
ops...? No big deal in the overall scheme of things.??? I had a great
time and look forward to next year.
73, George K4GM
On 7/8/2022 12:44 PM, Mike Dodd wrote:
> This was my first time participating, and I came away with a few
> thoughts I'd like share with the group, and especially with David.
>
> ----------
> TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up
> sheet. Several times I couldn't commit to two hours due to time
> constraints. One-hour slots provide more flexibility and encourage
> signing up.
>
> Look at it this way: Suppose I can't commit to a two-hour session from
> 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now,
> at 7:50, I discover I CAN operate until 9pm, so I open the sheet to
> see if 8-9 is still available. It is, so I sign up and keep on
> operating. Easy-peasy.
>
> ----------
> SUGGESTION: Modify the sign-up sheet to lock the row and column
> headers so they're always visible. On the current sheet, they scroll
> off the screen as I move around the sheet.
>
> For example, if I want to sign up for 20CW at 7-9pm, the band/mode and
> time headers disappear as I tab from cell-to-cell and row-to-row, so I
> don't know which cell to look at. Hheaders should always be visible.
>
> This is a standard operation in most spreadsheets. Here's an article:
> <>
>
> ----------
> SUGGESTION: I think 13 Colonies should eliminate the Name from the
> exchange. Only a few stations ever sent their name, and I didn't even
> know it was part of the exchange until well into the event (OK, I
> didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why
> have it if no one sends it?
>
>
> Comments, anyone?
>
--
George- Price-Right Communications
107B East Davis St.
Culpeper, VA 22701
540-617-1177
|
Here you go, David.
?
Limited time, but managed 922 contacts.
?
Excellent job running this thing this year!
?
73,
Rick
N1RM
?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]>
On Behalf Of David Wright via groups.io
Sent: Friday, July 08, 2022 7:06 AM
To: [email protected]
Subject: [K2B-13Colonies2022] Thanks, logs please?
?
Thanks to all for a great week.
Really nice to see folks fill in those slots July 7.
Can you please forward me your logs, at your earliest?? Can you add your call to file name; adif is easiest, but I can pretty much do any format.
I have to get the numbers to Ken by Monday.
I will circulate a summary next week, showing how we all did, and compared to the other colonies.
David, K2WPM
|
Re: Feedback and comments
Greetings to all,
I do think one hour shifts are a good idea - especially if something comes up, you are not committed, or if you just run our of steam! ?It is tiring. A great option.
I received names from contacts on several occasions, and was asked for mine on more than one occasion. I gave them my name and personal call sign as well. It's all info that's available on our individual QRZ pages and we were all listed on the K2B page, so I did not see it as an issue. If I were concerned about what other hams might learn about me i.e. privacy, I would not have a QRZ page and would have asked David to leave me off the K2B page.
I agree it's important for us to check the signup spreadsheet before starting a shift, just to make sure no one else has beaten us to the shift. And we should also be careful about going over our time slots as well. ?Someone had suggested we use some sort of communication app - it might have been Discord. I think it would be an excellent idea. For those of us who chose to use it, it would be an excellent way of letting the current operator know you are there and any important info could be shared quickly. It might be hard to keep up with if pileups are happening, but still would give us core communication options.
Finally, I think a big thank you goes to David for his valiant efforts to keep all of us straight! ?I know we have all received encouragement from him at some point during the event. And a big thank you goes to all of you operators that gave of your time and talents! ?I read with interest a number of your comments on how the bands were going - what you were experiencing, and I thought it was so good that we could all communicate and be supportive of each other! Nicely done!
Like many of you, I look forward to next year, and I certainly hope David will continue to coordinate us!
'73 and Blue Skies!
Linwood Campbell
K2LLC
|
Re: Feedback and comments
I might have been the overlapping operator on 80M. When I started the next slot was open so I just kept going after 7-9 shift. Sorry about that, if it was me. I should have stopped and doubled checked that the slot wasn't filled. Oh well - next time.
Band conditions were terrible, which caused me to abandon the whole two hour slot. So perhaps one hour time slots would work better. You can always sign up for two.
Roger on the name issue. I never sent my name.
Good time as usual and I hope to do this next year.
73, Stu2, W7IY
toggle quoted message
Show quoted text
On 7/8/22 14:39, George Marzloff wrote: I agree with Mike on locking the first row on the spreadsheet.?? I locked it on the second day.?? Then I noticed a day or so later someone had unlocked it (what possible reason????)?? Anyway,? I locked it again.? It is currently locked. Test it to make sure. Possibly the lock is only local?? I hope not.
I like 1 hour time slots. I kinda made 'em that way as I worked. Only twice was I able to go two hours straight.? Usually, I worked an hour max. I just entered 10:15-11:00, for example,? in an empty slot.
Not once did I give my name.?? I received names twice...?? I vote thumbs up on NO NAME!!
One cause for concern was duplication of mode/band operation.? At least twice and maybe three times I saw an open slot on the Sheet. I entered my call.? I got the log up and was ready to go. Then went to DX Summit to self spot and to my surprise another operator had been spotted. I went to the frequency and sure enough I heard K2B! Almost a big OOPS.?? I am not talking about a 5 minute overshoot on the prior hour but 15-30 minutes into the current block.? Doubt there is a simple answer here. Maybe a mandatory check on DX Summit before beginning operation ??? A big notice to double check DX Summit before operation????? These events occurred during the last 2 or 3 days so might be new inexperienced ops... No big deal in the overall scheme of things.??? I had a great time and look forward to next year.
73, George K4GM
On 7/8/2022 12:44 PM, Mike Dodd wrote:
This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David.
----------
TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up.
Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy.
----------
SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet.
For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible.
This is a standard operation in most spreadsheets. Here's an article: <>
----------
SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it?
Comments, anyone?
|
Re: Feedback and comments
I agree with Mike on locking the first row on the spreadsheet.?? I locked it on the second day.?? Then I noticed a day or so later someone had unlocked it (what possible reason????)?? Anyway,? I locked it again.? It is currently locked. Test it to make sure. Possibly the lock is only local?? I hope not.
I like 1 hour time slots. I kinda made 'em that way as I worked. Only twice was I able to go two hours straight.? Usually, I worked an hour max. I just entered 10:15-11:00, for example,? in an empty slot.
Not once did I give my name.?? I received names twice...?? I vote thumbs up on NO NAME!!
One cause for concern was duplication of mode/band operation.? At least twice and maybe three times I saw an open slot on the Sheet. I entered my call.? I got the log up and was ready to go. Then went to DX Summit to self spot and to my surprise another operator had been spotted. I went to the frequency and sure enough I heard K2B! Almost a big OOPS.?? I am not talking about a 5 minute overshoot on the prior hour but 15-30 minutes into the current block.? Doubt there is a simple answer here. Maybe a mandatory check on DX Summit before beginning operation ??? A big notice to double check DX Summit before operation????? These events occurred during the last 2 or 3 days so might be new inexperienced ops...? No big deal in the overall scheme of things.??? I had a great time and look forward to next year.
73, George K4GM
toggle quoted message
Show quoted text
On 7/8/2022 12:44 PM, Mike Dodd wrote: This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David.
----------
TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up.
Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy.
----------
SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet.
For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible.
This is a standard operation in most spreadsheets. Here's an article: <>
----------
SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it?
Comments, anyone?
--
George- Price-Right Communications
107B East Davis St.
Culpeper, VA 22701
540-617-1177
|
Re: Feedback and comments
I support the suggestion to incorporate 1hr time segments into the schedule for all the reasons stated so far.
I had no problems using the spreadsheet to assign and change operating time slots. Locking the top row and first column of the spreadsheet would be nice, and if we want to guild the lily, we could shade or color the rows.
I also appreciated the messages shared by operators during the event. The reports on band conditions and your experiences with your contacts were interesting and letting us know when you needed to change your schedule was helpful. I also appreciated the N1MM tips. I did not know one can change CW speed with pgup and pgdn commands before this event. Nor do I know much about self-spotting via telnet commands. I didn't figure it out for this year's event but will investigate it for next year.
Thanks to David for doing a great job organizing the team. My participation was easy and fun because of his diligence and enthusiastic encouragement throughout the event.
73,
Leon
NT8B
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of David Wright via groups.io Sent: Friday, July 8, 2022 13:22 To: [email protected]Subject: [K2B-13Colonies2022] Feedback and comments Thanks, I wanted to start a separate thread for any comments or suggestions. So this one is fine! Here's what 13 Colonies web site says for exchange: The exchange for this event is: CALL SIGN RS / RST / RSQ STATE / PROVINCE or COUNTRY Sometimes I asked for name; usually, people volunteered it, so I did also. I think the one-hour time slot is a fantastic idea. I was going to recommend that myself. Not because of commitment(s), but because two hours can be physically grueling. On 20 meters, with jammers, guys plopping down 1 Khz away, weak signals fading in and out, DX calling off the back of the beam. Not to mention the pile-ups. Tnxs also on the spreadsheet idea. David, K2WPM K2B Coordinator ¨C 13 Colonies -----Original Message----- From: [email protected] < [email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 12:45 PM To: [email protected]Subject: [K2B-13Colonies2022] Feedback and comments This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David. ---------- TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up. Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy. ---------- SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet. For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible. This is a standard operation in most spreadsheets. Here's an article: <> ---------- SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it? Comments, anyone? -- 73, Mike N4CF Louisa County, VA USA Elecraft K4d / KPA500 / KAT500 Carolina Windom up 45'
|
Thanks, I wanted to start a separate thread for any comments or suggestions.
So this one is fine!
Here's what 13 Colonies web site says for exchange:
The exchange for this event is:
CALL SIGN
RS / RST / RSQ
STATE / PROVINCE or COUNTRY
Sometimes I asked for name; usually, people volunteered it, so I did also.
I think the one-hour time slot is a fantastic idea. I was going to recommend that myself.
Not because of commitment(s), but because two hours can be physically grueling.
On 20 meters, with jammers, guys plopping down 1 Khz away, weak signals fading in and out, DX calling off the back of the beam.
Not to mention the pile-ups.
Tnxs also on the spreadsheet idea.
David, K2WPM
K2B Coordinator ¨C 13 Colonies
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 12:45 PM To: [email protected]Subject: [K2B-13Colonies2022] Feedback and comments This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David. ---------- TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up. Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy. ---------- SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet. For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible. This is a standard operation in most spreadsheets. Here's an article: <> ---------- SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it? Comments, anyone? -- 73, Mike N4CF Louisa County, VA USA Elecraft K4d / KPA500 / KAT500 Carolina Windom up 45'
|
Nice work, Mike!
David, K2WPM
K2B Coordinator ¨C 13 Colonies
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 12:05 PM To: [email protected]Subject: Re: [K2B-13Colonies2022] Thanks, logs please? On 7/8/2022 7:06 AM, David Wright wrote: Can you please forward me your logs, at your earliest?? Can you add
your call to file name; My ADIF log is attached, exported from N1MM+. Thanks for the opportunity to participate. 73, Mike N4CF
|
This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David.
----------
TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up.
Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy.
----------
SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet.
For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible.
This is a standard operation in most spreadsheets. Here's an article: <>
----------
SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it?
Comments, anyone?
--
73, Mike N4CF
Louisa County, VA USA
Elecraft K4d / KPA500 / KAT500
Carolina Windom up 45'
|
On 7/8/2022 7:06 AM, David Wright wrote: Can you please forward me your logs, at your earliest?? Can you add your call to file name; My ADIF log is attached, exported from N1MM+. Thanks for the opportunity to participate. 73, Mike N4CF
|
On 7/8/2022 11:54 AM, David Wright wrote: No, I do not find it. I sent it to <dwright@...>. I will post my log here. The email also contained some suggestions for future years, and I will post those here separately under a different subject line. --- Mike
|
David,
I sent my log direct.? Did you receive it?
Chuck K4QS
|
Also, logs do not have to be sent on groups.io.
Private email is fine.
Less spam for all.
David, K2WPM
K2B Coordinator ¨C 13 Colonies
toggle quoted message
Show quoted text
-----Original Message----- From: David Wright Sent: Friday, July 8, 2022 11:54 AM To: ' [email protected]' < [email protected]> Subject: RE: [K2B-13Colonies2022] Thanks, logs please? No, I do not find it. David, K2WPM K2B Coordinator ¨C 13 Colonies -----Original Message----- From: [email protected] < [email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 11:49 AM To: [email protected]Subject: Re: [K2B-13Colonies2022] Thanks, logs please? On 7/8/2022 7:06 AM, David Wright wrote: Can you please forward me your logs, at your earliest? I didn't know I should have put it here. I sent you my log in a private email; did you get it? --- Mike N4CF
|
No, I do not find it.
David, K2WPM
K2B Coordinator ¨C 13 Colonies
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 11:49 AM To: [email protected]Subject: Re: [K2B-13Colonies2022] Thanks, logs please? On 7/8/2022 7:06 AM, David Wright wrote: Can you please forward me your logs, at your earliest? I didn't know I should have put it here. I sent you my log in a private email; did you get it? --- Mike N4CF
|
On 7/8/2022 7:06 AM, David Wright wrote: Can you please forward me your logs, at your earliest? I didn't know I should have put it here. I sent you my log in a private email; did you get it? --- Mike N4CF
|
N1RM - Rick Miller
Linwood Campbell K2LLC
Mike Dodd N4CF
Chuck K4QS