开云体育

Team: I received everyone's ADIF uploaded logs via the ARRL tool. Thank You! Y'all got them to me in record time. I was able to process them all and upload to ARRL and received a confirmation! They should be logged into LoTW soon (I dunno how long that takes). You can check the leaderboard periodically at: https://vota.arrl.org/leaderboard.php . We are the W1AW/4 with the big #'s - 16,832 from February and 6,189 from July for a total of 23,021 QSO's! These #'s are slightly different from our raw #'s on our summary page - maybe "raw" QSO's without dupes removed (?). Thanks again for all the contributions and participation to make this a successful effort for W1AW/4 SC. I'm sure Marc N4UFP (SK), our previous Section Manager who originally reached out to me and the Swamp Fox Contest Group to coordinate the event for SC, would be very pleased. 73, Ed K3DNE

Team W1AW/4 SC, After the END OF OUR EVENT (ends at 2359z = 7:59EDT) tonight (Tuesday 7/25), you need to upload your ADIF log(s) ASAP (within a day or two please!) PLEASE (!) only upload the JULY event file (you may see your February event in your list of logs - don't upload that one!). I just completed the upload of my ADI file using this ARRL supplied tool: https://contests.arrl.org/votalogutility.php?p=votalog Very easy and straight forward - took less than 5 minutes. It prompted me to enter state, county, grid square, CQ Zone and ITU zone. I think we are all CQ Zone 5 and ITU Zone 8. If you are not sure of your grid square you can look it up on QRZ.com via your callsign and it is within the Detail tab. Kevan N4XL prepared this document to assist with the process (file naming is not crucial unless you're submitting 2 logs): https://www.swampfoxcontestgroup.com/How%20to%20Submit%20W1AW4%20VOTA%20Log%20v2(2)-1.pdf If you used a separate logging program for digital AND are uploading 2 logs please name one W1AW4phcw.adi (non digital log) and the other as W1AW4digi.adi so they don't overwrite each other. I can see on the subsequent tool on my end who submitted the logs (both personal call and email address) and when submitted (timestamped) so your personal callsign and date are not needed in that naming convention. BTW N1MM named my file as W1AW4.adi. Your program may do different which is okay or you may rename it to the naming convention N4XL suggested in his document below (just add phcw.adi or digi.adi if sending 2 logs per above). I left mine as is: W1AW4.adi and it uploaded fine and I was able to see who uploaded it on my end). Apparently naming the file is not as crucial as we thought prior to the event! You don't need to email me your log unless I specifically ask you for it! Please let me know if you have any questions or problems with this process. Thanks! 73, Ed K3DNE

In our July event we made (so far - this # may increase but is based on our Summary page). 6,062 QSO's !. Added to our February event of 16,634 QSO's we have a grand total of 22,696 QSO's in the combined weeks! That puts us well above all the other W1AW/x state totals (so far)! February Total QSO's # Operators QSO's per Operator 16634 39 427 July Total QSO's # Operators QSO's per Operator 6062 20 303 July QSO #'s below are based on our Summary page or the # reported in the ARRL upload (if I've received an upload to date) Century Club (>100 QSO's) K6FNV 225 AA4JW 205 N8WRL 137 KY4GS 112 W1MRC 106 1/2 Kilo Club (>500 QSO's) KZ3P 634 KG4IGC 567 N4IQ 562 W4GE 546 Kilo Club (>1000 QSO's) K3DNE 1325 K4QQG 1160 I'd like to thank everyone who participated and contributed! As I'm always ranting about to the Swamp Fox Contest Group: All contributions, large and small are appreciated! Thanks to everyone who also contributed behind the scenes and a special shout-out to Scott KG9V who built and maintained the spreadsheets, schedule and unselfishly offered his time and advice! If you still need to upload your ADIF log, here's the link: https://contests.arrl.org/votalogutility.php?p=votalog 73, Ed K3DNE

Congratulations on passing 1000 QSO's. Great job. Bob KZ3P

Thanks everyone for a successful event! See the email below for log upload info. I see several have already uploaded! I'll send a couple of emails in the next day or two with some individual and team totals. Thanks Again! 73 Ed K3DNE On 07/25/2023 6:40 PM EDT Ed Kucharski (K3DNE) <k3dne@...> wrote: Team W1AW/4 SC, After the END OF OUR EVENT (ends at 2359z = 7:59EDT) tonight (Tuesday 7/25), you need to upload your ADIF log(s) ASAP (within a day or two please!) PLEASE (!) only upload the JULY event file (you may see your February event in your list of logs - don't upload that one!). I just completed the upload of my ADI file using this ARRL supplied tool: https://contests.arrl.org/votalogutility.php?p=votalog Very easy and straight forward - took less than 5 minutes. It prompted me to enter state, county, grid square, CQ Zone and ITU zone. I think we are all CQ Zone 5 and ITU Zone 8. If you are not sure of your grid square you can look it up on QRZ.com via your callsign and it is within the Detail tab. Kevan N4XL prepared this document to assist with the process (file naming is not crucial unless you're submitting 2 logs): https://www.swampfoxcontestgroup.com/How%20to%20Submit%20W1AW4%20VOTA%20Log%20v2(2)-1.pdf If you used a separate logging program for digital AND are uploading 2 logs please name one W1AW4phcw.adi (non digital log) and the other as W1AW4digi.adi so they don't overwrite each other. I can see on the subsequent tool on my end who submitted the logs (both personal call and email address) and when submitted (timestamped) so your personal callsign and date are not needed in that naming convention. BTW N1MM named my file as W1AW4.adi. Your program may do different which is okay or you may rename it to the naming convention N4XL suggested in his document below (just add phcw.adi or digi.adi if sending 2 logs per above). I left mine as is: W1AW4.adi and it uploaded fine and I was able to see who uploaded it on my end). Apparently naming the file is not as crucial as we thought prior to the event! You don't need to email me your log unless I specifically ask you for it! Please let me know if you have any questions or problems with this process. Thanks! 73, Ed K3DNE

I had put myself on the calendar for 40m SSB from 1800 to 2000 tonight but I had to remove myself as something I must deal with has come up and I can’t break away. I’m sorry. -- 73, Jeremy R. Wirtz AA4JW

I was looking at the W1AW/4 summary tab on the spreadsheet and someone has credited me for QSO's I didn't make. On my row, N8WRL, 85 is listed on 7/23. I didn't operate on that day, so I suspect someone entered their QSO's on my line by mistake. Rather than just delete it, I thought I'd throw it out to the group to see if anyone "claims" them :) 73 -Brian n8wrl

7/25/23 10AM 40 CW

Lets see who is recieving this post to see if all is OK with group.io De kg4igc

First: WOW (!) what a big QSO day yesterday! 1,010 QSO's on a Monday! We have exceeded the 5K QSO mark in this week of our activation and shattered our 22K QSO combined weeks goal. Thanks everyone! Second: Our activation week comes to an end this evening (7:59PM EDT, 23:59Z). Lots of operating opportunities today. Third: I will send the ARRL ADIF Upload Tool this evening. Very easy and straight forward. It will prompt you to enter state, county, grid square, CQ Zone and ITU zone. I think (correct me if I'm wrong) we are all CQ Zone 5 and ITU Zone 8 (you can confirm at this site: https://zone-check.eu/). If you are not sure of your grid square you can look it up on QRZ.com via your callsign and it is within the "Detail" tab. Please upload ASAP after the end of the event. There were a couple of "glitches" with some logs after our first week activation and I ended up having to either re-upload or upload for the operator. Usually if N3FJP logger was used for some reason - we weren't able to figure out why. Perhaps that has been remedied since our last activation. Because of this I will also ask some to email me your ADIF - I'll let you know if needed.. Fourth: If you haven't entered your QSO #'s on our Summary Page of the Spreadsheet yet - please do, just to get a more accurate measure of the # of QSO's we actually made. Lastly: A big Thank You to everyone who made this such a successful event! 73, Ed K3DNE

With just 2 days left to go we have many openings on the schedule! We are also approaching the 22K QSO goal (combined weeks) we are just 814 QSO's short of that big number. If any of our team has some time available to operate in the next couple of days - now is the time! Thanks to all who have participated thus far. 73, Ed K3DNE

Congratulations on breaking 1000 QSO's. Great job. Bob KZ3P

I worked a paltry 2 hours on 20 this afternoon and had a very good time. The band was so-so, and QSO's were steady. Many stations were grateful for the activation. Very pleasant. I see on the spreadsheet the comparison between this week's activation and February. We're a looong way from those numbers. I think it's because we just got done with K2L. I do hope we get to do something like this next year. But I hope that we can take thirteen colonies into account when scheduling. I know for me I didn't sign up for too much because I'm a bit burned out from K2L and can't really justify that number of hours away from the family again this soon. Feb was great, perhaps if SC week 2 was in the fall it would be better. I'm sure ops from the other colonies feel the same. 73 team Brian n8wrl

Responses slow on both 15 and 20M although band is open. Maybe more activity/interest later on. Dennis, K2SX

Had a few really cool contacts this evening on 20 meters, I worked W6JPL, K6ICS, WA6OUD & W6VIO who were all at the Jet propultion Labratories in California! https://www.jpl.nasa.gov/ Frank KG4IGC

We are now over the 20K QSO mark with our combined weeks of operation - 20,340 QSO's to be exact as I type this! Congratulations Team! I know I set a "stretch goal" of 25K QSO's but I find that to be unlikely with the time remaining. As I often do when operating a contest, it may be time to reset that goal - how about 22K QSO's? That's an additional 1660 QSO's in the next 3 days (553 QSO's per day) - I think that is achievable but still somewhat of a stretch considering activity levels and conditions. Lets give it a go! With all that being said, I want to say thanks again to all who are participating and if you haven't had the opportunity to jump in yet there's not time like the present! Plenty of open slots on the schedule. If you haven't entered your QSO's on the summary page of the spreadsheet please do. It is also time to start thinking about post contest log uploads. I will be sending instructions out towards the end of the event - QRX on that for another couple of days. 73 Ed K3DNE

Thunderstorm

I see a spot on the cluster for a W1AW/4 on 18070.1 - PLEASE NO WARC Bands allowed in this event!!!

Thanks to all who are participating in our W1AW/4 SC VOTA July event! We will be exceeding 2K QSO's today and I expect there will be lots of opportunities for big QSO #'s over the upcoming weekend. Not much going on this weekend in terms of contests (YOTA and Maidenhead Mayhem contests) so less competition for QSO's! I'd like to set 2 goals (this is the contester in me) for our operating group. In the first week of our activation we worked 16832 QSO's and so far in our second week we are presently at 1906 QSO's. Goal #1 should be relatively easy to obtain: 20K QSO's in the combined 2 weeks (which would require an additional 1262 QSO's). We are almost there! We could achieve that goal by end of day today or tomorrow! Goal #2 (the "stretch" goal) is 25K QSO's in the combined 2 weeks - we are 6262 QSO's away. We need to average 1253 QSO's per day for the rest of the event to hit that goal - I know that's a stretch but I find a stretch goal helps me keep BIC (butt-in-chair). If you haven't had the opportunity to participate yet, please consider some operating time this weekend - plenty of open slots on the schedule! https://docs.google.com/spreadsheets/d/1bKhcnW-2UbAtEhkXw_m_7fo86KUmVUHz7ZAGzdEJONs/edit#gid=2146979454 Just a reminder to continue to honor the schedule (if something comes up and you can't operate please remove yourself from the schedule and visa versa) and to document your QSO #'s on the summary page). Our spreadsheet chat function seems to be working well for handoffs and getting a quick message between operators - thanks for utilizing that functionality! 73, Ed K3DNE