Locked
Re: TX6 Message in NA Contest Mode V2.2.0
Hi Paul,
agreed I use the wrong contest type,
but the principle is the same as I tried to cover in my follow.
73
Bill G4WJS. On 05/06/2020 21:54, Paul Selwood G3YDY
via groups.io wrote:
Bill, You have missed the point of Tony's query again. Tony was not operating in an EU Contest Mode to be used for EU VHF/UHF 73 Paul G3YDY -----Original Message----- From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville Sent: 05 June 2020 21:46 To: main@WSJTX.groups.io Subject: Re: [WSJTX] TX6 Message in NA Contest Mode V2.2.0 On 05/06/2020 20:43, Tony Collett via groups.io wrote:Thanks Bill, understand the reasoning, and I certainly didn't have so many non-compatible lock ups this session but can you clarify a bit more please? I said I was in NA Contest mode, your reply mentioned EU Contest mode. Not having used the latter are you saying that these two Contest modes will talk to each other OK since they both set Tx6 the same? Personally I think it is nice to identify which contest we are participating in so that others may have a chance to look up the rules and join in if they wish (and you have allowed for it to happen for ARRL Field Day, RU and WW Digi tests) but I bow to your experience. Regards Tony G4NBSHi Tony, we would expect EU Contest Mode to be used for EU VHF/UHF contests, it was specifically designed for the IARU Region 1 type of scoring. Agreed that NA Contest Mode may be better for HF contests. The ARRL FD and WW DIGI distinction, as far as recall, is because two contests may occur on the same bands and at the same time, there are also logic differences in the decoders. It would be a whole lot better if there was no ambiguity since selecting the right contest mode is important. We do try and adapt to different contest requirements but can only fit in a very small number where there is some hope of completing the required exchange in one of the WSJT-X modes. I don't have a perfect answer for this, we are squeezing quite a lot into a very small pot. 73 Bill G4WJS.
|
|
Locked
Re: TX6 Message in NA Contest Mode V2.2.0
Paul Selwood G3YDY
Bill,
toggle quoted message
Show quoted text
You have missed the point of Tony's query again. Tony was not operating in an EU Contest Mode to be used for EU VHF/UHF 73 Paul G3YDY -----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville Sent: 05 June 2020 21:46 To: main@WSJTX.groups.io Subject: Re: [WSJTX] TX6 Message in NA Contest Mode V2.2.0 On 05/06/2020 20:43, Tony Collett via groups.io wrote: Thanks Bill, understand the reasoning, and I certainly didn't have soHi Tony, we would expect EU Contest Mode to be used for EU VHF/UHF contests, it was specifically designed for the IARU Region 1 type of scoring. Agreed that NA Contest Mode may be better for HF contests. The ARRL FD and WW DIGI distinction, as far as recall, is because two contests may occur on the same bands and at the same time, there are also logic differences in the decoders. It would be a whole lot better if there was no ambiguity since selecting the right contest mode is important. We do try and adapt to different contest requirements but can only fit in a very small number where there is some hope of completing the required exchange in one of the WSJT-X modes. I don't have a perfect answer for this, we are squeezing quite a lot into a very small pot. 73 Bill G4WJS. This email has been scanned by BullGuard antivirus protection. For more info visit www.bullguard.com |
|
Locked
Re: New feature option for non-CQ New Call color highlighting
JP Tucson, AZ
I think an even better idea would be to just highlight the callsign with the type color (blue for dxcc, brown for new grid, green already worked, etc.) rather than the entire line. That would quickly & visually differentiate the CQ calls vs. others. 73 - John - N7GHZ
|
|
Locked
Re: TX6 Message in NA Contest Mode V2.2.0
On 05/06/2020 20:43, Tony Collett via groups.io wrote:
Thanks Bill, understand the reasoning, and I certainly didn't have so many non-compatible lock ups this session but can you clarify a bit more please?Hi Tony, we would expect EU Contest Mode to be used for EU VHF/UHF contests, it was specifically designed for the IARU Region 1 type of scoring. Agreed that NA Contest Mode may be better for HF contests. The ARRL FD and WW DIGI distinction, as far as recall, is because two contests may occur on the same bands and at the same time, there are also logic differences in the decoders. It would be a whole lot better if there was no ambiguity since selecting the right contest mode is important. We do try and adapt to different contest requirements but can only fit in a very small number where there is some hope of completing the required exchange in one of the WSJT-X modes. I don't have a perfect answer for this, we are squeezing quite a lot into a very small pot. 73 Bill G4WJS. |
|
Locked
Re: ALL.TXT
Paul Selwood G3YDY
Hi John, Depending on how much operating you do or just leave the system running these files can get large very quickly. I normally archive the file once a month (before I start operations on the first of the next month) and store it in another folder (called WSJT TXT Files) outside of WSJT. Inside the folder WSJT TXT Files Each month is filed as YYYY-MM e.g. 2020-05 for May 2020.
I have found these files most useful when eQSL’s turn and callsign is not in the log turn up the appropriate file and usually find it was an incomplete QSO or station was never seen.
Hope that Helps
73
Paul;
G3YDY
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of JP Tucson, AZ
Sent: 05 June 2020 19:07 To: main@wsjtx.groups.io Subject: Re: [WSJTX] ALL.TXT
Interesting... I always thought that long term data like this might help with the propagation thing...
Ok, thanks!
Btw, what are the names of those software programs?
Thanks again. 73 - John - N7GHZ
On Fri, Jun 5, 2020, 10:57 AM Bill Somerville <g4wjs@...> wrote:
This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com |
|
Locked
Re: Just upgraded to 2.2.0 GA and get hamlib error
Gwen Patton <ardrhi@...>
Did you notice that you have "-m 1035" in the first example, and "-m 135" in the second? Could that be part of the problem? -=-=-=-=-=-=-=-=- 73, Gwen, NG3P On Fri, Jun 5, 2020 at 2:37 PM <david.jennings3@...> wrote: The problem seems to be mainly with retrieving the frequency from the rig: |
|
Locked
Re: ALL.TXT
Sam Birnbaum
Hi Bill,
My program can be searching while WSJT-X is still updating the file.
It will not cause and error message. If your search includes your call sign, the other stations call sign and you know the approximate date range, you can use that in the search and it will only take a few seconds. I can tell you that Rich K1HTV uses it and to find the call sign in question in a 200MB file using the requested call sign and a date range of a couple of days around the date in question took less than 2 seconds.
73,
Sam W2JDB
-----Original Message-----
From: Bill Ahillen <bahillen@...> To: main@wsjtx.groups.io Sent: Fri, Jun 5, 2020 4:04 pm Subject: Re: [WSJTX] ALL.TXT I have problems when file gets large, not because of disk space, but because the app is still writing to the file while the next decode tries to write to the same file.
I have 4 instances running 24/7 and once it gets too large I have to move to archive then it returns to normal. I suspect file contention that throws a message the another user is already using the file. If I am not around at the time, I end up with 20 or 30 error messages and have to click OK 20-30 times.
As related to the ALL file use I recently found a contact I needed to show that I should have been logged with a portion of the file. He then requested my history files that I sent via drop box. 4 slices, 4 files 1.2 Gb of data covering 3 months.
In notes I use the Find to locate a call or a sequence like W9XYZ RR73. Works great. Sometimes I have to search ALL files from 4 instances to locate the contact.
It’s a powerful tool.
73
Bill
On Jun 5, 2020, at 2:39 PM, Sam Birnbaum via groups.io <w2jdb@...> wrote:
|
|
Locked
Re: ALL.TXT
JT Croteau
Crap, didn't realize it was important. Just erased it when I was
toggle quoted message
Show quoted text
cleaning up other things. On Fri, Jun 5, 2020 at 3:05 PM Bill Ahillen <bahillen@...> wrote:
|
|
Locked
Re: ALL.TXT
Bill Ahillen
I have problems when file gets large, not because of disk space, but because the app is still writing to the file while the next decode tries to write to the same file.
toggle quoted message
Show quoted text
I have 4 instances running 24/7 and once it gets too large I have to move to archive then it returns to normal. I suspect file contention that throws a message the another user is already using the file. If I am not around at the time, I end up with 20 or 30 error messages and have to click OK 20-30 times. As related to the ALL file use I recently found a contact I needed to show that I should have been logged with a portion of the file. He then requested my history files that I sent via drop box. 4 slices, 4 files 1.2 Gb of data covering 3 months. In notes I use the Find to locate a call or a sequence like W9XYZ RR73. Works great. Sometimes I have to search ALL files from 4 instances to locate the contact. It’s a powerful tool. 73 Bill On Jun 5, 2020, at 2:39 PM, Sam Birnbaum via groups.io <w2jdb@...> wrote:
|
|
Locked
Re: Logging QSO timing issue in v2.2.0?
Tony Collett
Seems I am alone in catching this oddity.
As an update I've not managed to do it again after maybe another 100Q's but I have been hitting "Log QSO" almost as soon as the window pops up when I'm confident of a good QSO rather than wait for the next period decode (or if not confident wait until the period has completely finished). Perhaps its like the timing "glitch" (for want of a better word) that doesn't stop the transmission when requested and shows up as a decoded signal as well. Done that many a time ocross the various versions. Regards Tony |
|
Locked
Love this bad decode..
JT Croteau
Sorry for the wasted bandwidth but I've been watching 6M all day and
this has been the most entertaining thing I've seen so far. 195030 -19 1.8 3229 ~ OO2NXO UA4LQX R 599 5978 N1ESE (EM47) |
|
Locked
Re: USB Audio - Mic OK in Windows, but no green bar in WSJTX
Peter Cleall
On Thu, 4 Jun 2020 at 03:29, Harold Miller <kb1zq@...> wrote:
|
|
Locked
Re: New feature option for non-CQ New Call color highlighting
Tony Collett
Hi Duane
JTAlert has that functionality if set up for it correctly (assuming windoze installation). Regards Tony G4NBS |
|
Locked
Re: TX6 Message in NA Contest Mode V2.2.0
Tony Collett
Thanks Bill, understand the reasoning, and I certainly didn't have so many non-compatible lock ups this session but can you clarify a bit more please?
I said I was in NA Contest mode, your reply mentioned EU Contest mode. Not having used the latter are you saying that these two Contest modes will talk to each other OK since they both set Tx6 the same? Personally I think it is nice to identify which contest we are participating in so that others may have a chance to look up the rules and join in if they wish (and you have allowed for it to happen for ARRL Field Day, RU and WW Digi tests) but I bow to your experience. Regards Tony G4NBS |
|
Locked
Re: ALL.TXT
Sam Birnbaum
Hi All,
While I wrote the
program AllText.exe for myself and enhanced if for the blind ham
group that uses the WSJT-X companion program QLog program for blind
hams to search the All.txt file, I am more than happy to send it to
anyone that would like to play with it. While the program was
specifically enhanced with audio output for the visually impaired
(blind) ham, it is not requirement for normal operation. It can
display the tail end of the All.txt file up to the last 30,000
records. It can search the entire file looking for specific call
signs or records types. It can analyze signal to noise ratios for
any date range and or specific call signs. It can be run while WSJT-X
is populating the All.Ttxt file. It does not load the entire file
into memory so it can handle extremely large files.
Outside its
functionality with the All.txt file, it can also download PSKReporter
data and display the spots in a summary or detail format.
It does not require
any special installation, it is a 32 bit program as such it will
require the libea32.dll and sslea32.dll if you want to download
PSKReporter data.
I attached some
screen shots of the output.
If you are
interested, let me know and I will be more than happy to send it to
you with some documentation on its use.
73,
Sam W2JDB
-----Original Message-----
From: KD7YZ Bob <kd7yz@...> To: main@WSJTX.groups.io Sent: Fri, Jun 5, 2020 3:12 pm Subject: Re: [WSJTX] ALL.TXT On 6/5/2020 13:57, Bill Somerville wrote:
> I'm sure there are more. Tools already exist, more interesting ones may > come along. It's so easy to keep the data with Today's cheap storage > media costs, So Bill, what's a good program to blend the roughly 40 "ALL.txt' files the computer search engine has come with, so far, on 6 different HDD's ?? Thanks for pointing the uses. -- 73 Bob KD7YZ AMSAT LM #901 |
|
Locked
Settings for Yaesu FTdxx101MP
cschloss@...
Does anyone have the radio settings page info for this rig. Am using CAT control cable from radio to USB port Com 4 of Windows 10 laptop. Had been using FTDX5000 as radio setting with 9600 baud rate, worked OK, but gave “Hamlib” error if I tried 80m FT8. So I’m happy to see FTDX101D now in Hamlib.
Thanks everyone,
Chuck AG0W |
|
Locked
New feature option for non-CQ New Call color highlighting
Duane - N9DG
I searched the mail list and did find any mention of this feature request. I would like to have the ability to turn on New Call color coding for messages from stations that are NOT calling CQ. The New Call color functionality can now only be applied to CQ's. I would like the non CQ traffic in the Band Activity window to also have the option to be highlighted if the person's call who made the transmission is new to me. This would very handy for finding calls that may be new grids that you have not worked before, but when that station has not called CQ. Basically by having that color feature it would easier to tail end a Q that is completing. The color shade should be a lighter shade of cyan to keep the general New Call color choice be consistent, but to also be distinctly different in intensity from highlighted CQs. Duane N9DG |
|
Locked
Re: ALL.TXT
On 6/5/2020 13:57, Bill Somerville wrote:
I'm sure there are more. Tools already exist, more interesting ones may come along. It's so easy to keep the data with Today's cheap storage media costs,So Bill, what's a good program to blend the roughly 40 "ALL.txt' files the computer search engine has come with, so far, on 6 different HDD's ?? Thanks for pointing the uses. -- 73 Bob KD7YZ AMSAT LM #901 |
|
Locked
Re: CAT error, WSJT-X 2.2.0, hamlib 3.1.7build1
David Jennings
The problem seems to be mainly with retrieving the frequency from the rig: Using the wsjtx rigctl: C:\WSJT\wsjtx\bin>rigctl-wsjtx -m 1035 -r com14 -s 38400 f m t get_freq: error = Invalid parameter PKTUSB 3000 0 The current version of rigctl from hamlib 3.3 produces this output: E:\Temp\hamlib-w64-3.3\bin>rigctl -m 135 -r com14 -s 38400 f m t 14074000 PKTUSB 2400 0 On Fri, Jun 5, 2020 at 2:36 PM <klblackw38@...> wrote:
|
|
Locked
Re: Just upgraded to 2.2.0 GA and get hamlib error
David Jennings
The problem seems to be mainly with retrieving the frequency from the rig:
C:\WSJT\wsjtx\bin>rigctl-wsjtx -m 1035 -r com14 -s 38400 f m t
get_freq: error = Invalid parameter PKTUSB 3000 0 The current version of rigctl from hamlib 3.3 produces this output:
E:\Temp\hamlib-w64-3.3\bin> 14074000 PKTUSB 2400 0 |
|