I agree John. But I'd like to wait until rc2 comes out next week. Then after 
kicking the tires we can try a mock trial Special Operating Activity as you 
suggest.

 

Don AA5AU

 

From: John Zantek [mailto:j...@zantek.net] 
Sent: Wednesday, September 19, 2018 3:23 PM
To: 'Don AA5AU'; 'WSJT software development'
Subject: RE: [wsjt-devel] Cabrillo File Generation

 

Don, et al,

 

As mentioned in the Quick Start Guide, I think it would be wise to set up a 
mock trial  Special Operating Activity and check out any issues with rc1 before 
we plunge into changing existing contests so that they open the door for 2.0.   
I’m among that eager bunch and would be willing to participate in such testing 
at any time.  I just finished Salmon Run and would have loved to run with 2.0.  

 

Speaking as a WWDX Club board member and sponsor of the Salmon Run contest: 
next year, we’re willing to change the Salmon Run exchange (if needed) and cut 
the WA County abbreviations to 3 char from the existing 3 & 4 character set to 
accommodate 2.0.

 

Anyone to wants to try some testing soon, I’m here.  How about a Mock Field Day 
in October, then run for real during the Winter Field Day,  January 26/27 2019?

 

Best 73

John W7CD

 

From: Don AA5AU [mailto:aa...@bellsouth.net] 
Sent: Wednesday, September 19, 2018 1:04 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Cabrillo File Generation

 

Ed, W0YK, and I are thinking of changing our Ten-Meter RTTY Contest, which 
normally takes place the first weekend in December, to an all-band FT8 contest.

 

If you think it might be done before then, we can certainly wait. Our thinking 
is that there may be some operators who would like to use it for the ARRL RTTY 
Roundup. An FT8 contest, with ARRL RTTY Roundup rules, in December could be a 
way to test the setup before January's contest.

 

I just wanted to see how it's done.

 

Has there been any discussion as to what frequencies would be good for FT8 
contesting on HF?

 

Thanks!

Don AA5AU

 

  _____  

From: Joe Taylor <j...@princeton.edu>
To: WSJT software development <wsjt-devel@lists.sourceforge.net> 
Sent: Wednesday, September 19, 2018 2:41 PM
Subject: Re: [wsjt-devel] Cabrillo File Generation

 

Hi Don,

On 9/19/2018 2:53 PM, Don AA5AU wrote:
>  From the 2.0 Quick Start guide "A basic Cabrillo log is generated in 
> the log directory, but it does not yet include the heading information 
> needed when submitting a contest log."
> 
> How is a Cabrillo log generated in this version?
> 
> When do you expect Cabrillo output to be full-featured?
> 
> Thanks,
> Don AA5AU

A file cabrillo.log appears automatically (in the same directory as 
wsjtx.log and wsjtx_log.adi) when you activate any of the contest modes.

You can clear the log (to start afresh, say just before a contest 
starts) by selecting *File | Erase cabrillo.log*.

File cabrillo.log is updated every time you log a QSO.

At present the file contains only "QSO:" records.  For submissioin to a 
contest sponsor it will need stuff like this at the start:

START-OF-LOG: 3.0
CREATED-BY: WSJT-X
LOCATION: SNJ
CONTEST: ARRL-VHF-JUN
CALLSIGN: K1JT
CATEGORY-ASSISTED: NON-ASSISTED
CATEGORY-MODE: MIXED
CATEGORY-OPERATOR: SINGLE-OP
CATEGORY-POWER: HIGH
CATEGORY-STATION: FIXED
CATEGORY-TRANSMITTER: ONE
CLAIMED-SCORE: 5640
OPERATORS: K1JT
CLUB: Mt Airy VHF Radio Club
NAME: Joe Taylor
EMAIL: k...@arrl.net
ADDRESS: Joe Taylor, K1JT
ADDRESS: 272 Hartley Ave
ADDRESS: Princeton, NJ  08540

... and one like this at the end:

END-OF-LOG:

We'll get to this, in due course.  In the meantime, if you're in a rush, 
it's not that hard to add the necessary lines with a text editor.

Do you have some deadline in mind?

    -- 73, Joe, K1JT




_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to