Date   

Locked Re: WSJT-X 2.2.0-rc1

Bill Somerville
 

On 14/05/2020 5:28, K7GQ@... wrote:
I am hoping that, with the Mac OS version, that the wrong screen object library was included as the Mac version looks like it's straight from Windows 3.1.

Thanks for the superb product and support!

Harry  K7GQ
Hi Harry,

thanks for the issue report, we are aware of the problem with a rather clunky looking UI on macOS. This is due to a packaging error, a file is missing in the application bundle, it is fixed for the next release.

73
Bill
G4WJS.


Locked Re: pskreporter

neil_zampella <neilz@...>
 

The reason its probably not showing up is that those callsigns are 'non standard' and as such, do not send a GRID along when calling CQ.   Thus PSKReporter cannot properly map those callsigns.   

Neil, KN3ILZ

On 5/13/2020 6:38 PM, 5w1sa.oc097@... wrote:

Hi All,

I'm Atsu/5W1SA, just joined to this group to search topic and submit one question.
I recently started 5W1STAYSAFE special event station also I have operated 5W20SAMOA before.
During FT8 operation using WSJT-X, I'm keep watching pskreporter to see what area, how far my signal is travelling to.
While working with 5W1SA, no problem at all.
But 5W1STAYSAFE (and 5W20SAMOA), almost no report upload or shows on pskreporter except I saw redpitaya does.
So it seems not a problem on pskreporter but I guess WSJT-X or possibly JTDX and other similar software based on WSJT-X have limitation of send report to pskreporter?
It won't affect QSO. Just want to know why no report showing to pskreporter? I have checked other xxxSTAYHOME, some shows up, some not.

73 and stay safe all.
Atsu
5W1SA/5W1STAYSAFE



    

Virus-free. www.avg.com


Locked Re: Can't use WSJT-X 2.2.Rc1

Tom Melvin
 

Morning

What is the error message you receive?

Tom

--
73

Tom
GM8MJV (IO85)

On 14 May 2020, at 10:11, F8RZ <f8rz@...> wrote:

Hello.

For me, RC1 is unusable.

Excellent reception and decoding.

Unfortunately,

On transmit, normal shift occurs (Fake it ON). BUT...

When the program returns to Rx, no shift back to the reception freq, but it remains stuck on the tx freq.

If I insist, an error message is displayed. (NOT a matter of RFI, power is set to zero)

The settings are exactly the same as for v 2.1.2 which works flawlessly.

Any ideas ?

FLEX 6300

JTAlert 2.16.5-

plenty of PC horsepower

Thank you for reading

73 JR F8RZ






Locked Re: Managing Internal Contest Log

Roger
 

On 14/05/2020 00:38, Steven Rutledge wrote:
Bill, having a little trouble with this.  Forgive me.  I not good with software.  I guess the contest log is started automatically when you go into contest mode?  Is it only in Cabrillo?  Reason I ask is that I would like to import the contest log into DXBASE which would require an ADI file.  I think.  So, I send the log off to the ARRL in Cabrillo, I'm not sure how to convert it, save it, etc.  I guess it isn't supposed to show up under logs?
Steve, N4JQQ
There's two ways I deal with this.

1. I manually extract the entries I want from WSJTX's wsjtx_log.adi .
2. I rename wsjtx_log.adi so that a new file is started for the contest. Afterwards I rename the new log file and the old one back again. Then the contest log can be added to the original one.

The advantage of the renaming is that you can use the colour coding to identify those who you are pouncing on. Beware if you are calling CQ as the duplicates can catch you out.

Roger, G4HZA


Locked Can't use WSJT-X 2.2.Rc1

F8RZ
 

Hello.

For me, RC1 is unusable.

Excellent reception and decoding.

Unfortunately,

On transmit, normal shift occurs (Fake it ON).            BUT...

When the program returns to Rx, no shift back to the reception freq, but it remains stuck on the tx freq.

If I insist, an error message is displayed. (NOT a matter of RFI, power is set to zero)

The settings are exactly the same as for v 2.1.2 which works flawlessly.

Any ideas ?

FLEX 6300

JTAlert 2.16.5-

plenty of PC horsepower

Thank you for reading

73 JR F8RZ


Locked pskreporter

Atsu_5W1SA
 

Hi All,

I'm Atsu/5W1SA, just joined to this group to search topic and submit one question.
I recently started 5W1STAYSAFE special event station also I have operated 5W20SAMOA before.
During FT8 operation using WSJT-X, I'm keep watching pskreporter to see what area, how far my signal is travelling to.
While working with 5W1SA, no problem at all.
But 5W1STAYSAFE (and 5W20SAMOA), almost no report upload or shows on pskreporter except I saw redpitaya does.
So it seems not a problem on pskreporter but I guess WSJT-X or possibly JTDX and other similar software based on WSJT-X have limitation of send report to pskreporter?
It won't affect QSO. Just want to know why no report showing to pskreporter? I have checked other xxxSTAYHOME, some shows up, some not.

73 and stay safe all.
Atsu
5W1SA/5W1STAYSAFE


Locked Re: WSJTX_2-2-0-RC1 dont start ---

Haris SV1GRB
 

Now there is a pattern for the developers to investigate.
This is how groups works, someone remarks an idea and others try changing relevant settings hi.


Haris
SV1GRB



on my other PC was the "," WSJTx = startet
here on the 1st PC was the "." - WSJTx = not startet

so, that was the problem :-)

@Haris
i*m abt 2 weeks in the middle of september near PortoHelios, take a boat and came over, there are waiting 1 or 2 beer for you   hihi


Locked Re: 2.2.0-rc1 WOW !!

Bill, WB6JJJ
 

Hello Joe,

I noticed that 1 Hz separation decode today… On 6 Meters with two very very strong fairly local stations answering my CQ, they were both decoded – just unbelievable considering the high signal levels (>25 dB) and only 1 Hz apart.

 

The only issue, other than my slow computer causing missing decode sessions, is that with “Blank lines between decoding periods” checked, I very seldom get that blank line that includes the current band information.

 

Also, is there a way to get the country name for each line? Currently, it is displayed only on lines with CQ.

 

Thanks for a fantastic program.

 

Bill

WB6JJJ/7

 

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Joe
Sent: Tuesday, May 12, 2020 13:36
To: WSJTX@groups.io
Subject: Re: [WSJTX] 2.2.0-rc1 WOW !!

 

Hi Mike,

Yes, subtraction of already-decoded signals in WSJT-X v2.2.0 is even better than in earlier versions.  We're delighted that you noticed!

  -- 73, Joe, K1JT


Locked Re: WSJT-X 2.2.0-rc1

K7GQ
 

Joe & the  WSJT Development Group

Reluctantly, I agree that it is a bit harder to click on the decoded (CQ) message of choice with the small screen movements following early decode.  

However, perhaps an unwelcome byproduct is that it "appears" that the loudest stations are decoded first, followed by the weaker, perhaps unintentionally giving preference to the louder stations.

I am hoping that, with the Mac OS version, that the wrong screen object library was included as the Mac version looks like it's straight from Windows 3.1.

Thanks for the superb product and support!

Harry  K7GQ


Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

JP Tucson, AZ
 

Well Jim, 

I am tight on $, being poor, etc.
I would love to have a 7610... it would be great to have a waterfall on a 50" monitor... then I wouldn't need to wear my glasses. 

Unfortunately, the tooth fairy isn't handing those out, and anyway, I haven't lost a tooth in nearly 50 years.

Any of the rich folks wanna get together and offer up a donation wouldn't be turned away...





73 - John - N7GHZ

On Wed, May 13, 2020, 9:02 PM Jim Brown <k9yc@...> wrote:
On 5/13/2020 6:06 PM, JP Tucson, AZ wrote:
> ONLY for those who own/have access to a Kenwood TS-440S...

If you're not tight on money, it's a great time to buy a new radio. The
Kenwood TS590SG is a pretty decent rig for under $1400. Lots of things
have been improved since the mid-'80s.

I use Elecraft rigs now, and 2008-vintage rigs are selling off because
newer models have been introduced. They're generally regarded as one of
the better radios.

73, Jim K9YC




Locked Re: WSJT-X 2.2.0-rc1

va7qi
 

Forgot to mention that I really like the early decode feature.

73 de va7qi,                ....Erik.


Locked Re: WSJT-X 2.2.0-rc1

va7qi
 

Upgraded to this version last night.  Computer is a HP AMD-based running Win10 Home.  8GB of RAM.
 Two anomalies to report:

1. If I click on TX on decoding will sometimes drag on well into the next sequence and the new sequence will then only show one or a few decodes.  Perhaps some state is changed when some buttons are changed?

2. On a couple of occasions I have seen a duplicate decode of a station - on the same frequency.

CPU usage as reported by another program was around 30%, which I believe includes all cores.

73 de va7qi,                ....Erik.


Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

Jim Brown
 

On 5/13/2020 6:06 PM, JP Tucson, AZ wrote:
ONLY for those who own/have access to a Kenwood TS-440S...
If you're not tight on money, it's a great time to buy a new radio. The Kenwood TS590SG is a pretty decent rig for under $1400. Lots of things have been improved since the mid-'80s.

I use Elecraft rigs now, and 2008-vintage rigs are selling off because newer models have been introduced. They're generally regarded as one of the better radios.

73, Jim K9YC


Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

Joe Subich, W4TV
 

Bill,

The goal here is to duplicate exactly the N1MM+ configuration.
That configuration explicitly sets DTR and RTS high.

73,

... Joe, W4TV

On 2020-05-13 9:56 PM, Bill Somerville wrote:
On 14/05/2020 02:51, Joe Subich, W4TV wrote:
Please set Handshake in WSJTX to *NONE* not *HARDWARE* then set
"Force Control Lines" to DTR=High and RTS=High to match N1MM+.

73,

   ... Joe, W4TV
Hi Joe,
you are correct on the handshaking option but the RTS and DTR lines do not need forcing high, that is a Red Herring as proven with the Hamlib rigctl test tool which did not need either of those lines forced high to make a good CAT connection. They are probably unconnected so their setting is irrelevant here, but best to leave them unset on the principle that with some interfaces they might be connected to PTT, CW, or FSK keying lines. They should only be forced high (or low) with the small subset of interface hardware that derives power from those lines.
73
Bill
G4WJS.


Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

JP Tucson, AZ
 

Ok, just to humor some...

Here are 2 more snips...

Wanna guess the outcomes? 

No guys... REALLY, I really have tried every combination you can think of!  Literally hundreds of iterations.  Somewhere, I had actually used a couple of sheets of paper to keep track... just like a truth table. Here's the final outcome of those hours of work...



On Wed, May 13, 2020 at 6:56 PM Bill Somerville <g4wjs@...> wrote:
On 14/05/2020 02:51, Joe Subich, W4TV wrote:
> Please set Handshake in WSJTX to *NONE* not *HARDWARE* then set
> "Force Control Lines" to DTR=High and RTS=High to match N1MM+.
>
> 73,
>
>    ... Joe, W4TV

Hi Joe,

you are correct on the handshaking option but the RTS and DTR lines do
not need forcing high, that is a Red Herring as proven with the Hamlib
rigctl test tool which did not need either of those lines forced high to
make a good CAT connection. They are probably unconnected so their
setting is irrelevant here, but best to leave them unset on the
principle that with some interfaces they might be connected to PTT, CW,
or FSK keying lines. They should only be forced high (or low) with the
small subset of interface hardware that derives power from those lines.

73
Bill
G4WJS.




--
73 - John - N7GHZ



Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

Bill Somerville
 

On 14/05/2020 02:51, Joe Subich, W4TV wrote:
Please set Handshake in WSJTX to *NONE* not *HARDWARE* then set
"Force Control Lines" to DTR=High and RTS=High to match N1MM+.

73,

   ... Joe, W4TV
Hi Joe,

you are correct on the handshaking option but the RTS and DTR lines do not need forcing high, that is a Red Herring as proven with the Hamlib rigctl test tool which did not need either of those lines forced high to make a good CAT connection. They are probably unconnected so their setting is irrelevant here, but best to leave them unset on the principle that with some interfaces they might be connected to PTT, CW, or FSK keying lines. They should only be forced high (or low) with the small subset of interface hardware that derives power from those lines.

73
Bill
G4WJS.


Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

Joe Subich, W4TV
 

Here ya go, they both 'look' the same... one works (N1MM), the other,
not so much!
They are *very different* ... as I suspected, you have WSJTX set for
hardware handshake and N1MM+ set to assert RTS (RTS Always On).

Please set Handshake in WSJTX to *NONE* not *HARDWARE* then set
"Force Control Lines" to DTR=High and RTS=High to match N1MM+.

73,

... Joe, W4TV


On 2020-05-13 8:21 PM, JP Tucson, AZ wrote:
Ok Joe & Bill,
Here ya go, they both 'look' the same... one works (N1MM), the other, not
so much!
Joe, in case you didn't pick up on last night's exchange with Bill & I;
We got the rigctl, to function and give back some readings... one way
worked & gave false & nonsense reports, the other did not (gave the proper
frequency readout) & Bill said he needed to review the situation further to
understand why my rig seems to operate not as expected.
At some point, Kenwood apparently changed the length of the IF command
response from 29 to 38 characters... I don't know if that is an issue
here...
On Wed, May 13, 2020 at 4:45 PM Joe Subich, W4TV <lists@...> wrote:


Now, that leaves the question still as to why it works in N1MM,
appears to respond according to the rigctl tests last night, but
won't do a thing during wsjt-x ops...
Please post screen shots of N1MM+ Config -> Configure Ports ->
<Radio Port> -> Set and WSJTX File -> Settings -> Radio

Since the rigctrl debug appears to work with handshake turned
off, it would appear that rig control is not configured the same
in N1MM+ and WSJTX.

73,

... Joe, W4TV


On 2020-05-13 4:00 PM, JP Tucson, AZ wrote:
Hi Bill,

For the record...

I was wrong!

I called Kenwood U.S.A. this morning for some clarifications.

My rig; which s/n starts with 711xxxx - was manufactured in 1986.
Production of the TS-440 ended in 1990.

Where we all got bad info from, there was only 1 TS-440 in production;
and
they were ALL TS-440S's - - - apparently some lazy folks who just left
off
the "S" in software & websites, magazines, etc.

So since they started production in 1982, that would put mine at around
the
midline of production.

Hopefully this info helps.

I really hate it when people give us all bad info, leading to confusion.


So really, the wsjt-x rig selection should read 440S...

Now, that leaves the question still as to why it works in N1MM, appears
to
respond according to the rigctl tests last night, but won't do a thing
during wsjt-x ops...

It's a head scratcher...

Thanks,



73 - John - N7GHZ

On Tue, May 12, 2020, 8:23 PM Bill Somerville <g4wjs@...>
wrote:

On 13/05/2020 04:18, JP Tucson, AZ wrote:

Ok, there is it... grrrgh!

Here is what I got: be ready to get dizzy...

d:\HAM RADIO stuff\WSJT-X\WSJT-X 2.2.0-rc (beta)\wsjtx\bin>rigctl-wsjtx
-m
2002 -r COM7 -s 4800 -Cserial_handshake=Hardware -vvvvv -Z f

Hi John,

thanks for that. Now try it again with this command:

rigctl-wsjtx -m 2002 -r COM7 -s 4800 -vvvvv -Z f

The difference being that hardware handshaking may not be needed with
your
CAT interface. Some loop RTS/CTS at the rig end to free up both DTR and
RTS
for switching PTT etc.

73
Bill
G4WJS.




Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

JP Tucson, AZ
 

Hello again Bill,

I guess you are the night owl type... thanks...

Ok, attached is what I got... fail...  hmmm, looks oddly familiar... 

Next...



On Wed, May 13, 2020 at 6:21 PM Bill Somerville <g4wjs@...> wrote:
On 14/05/2020 01:21, JP Tucson, AZ wrote:
> Ok Joe & Bill,
>
> Here ya go, they both 'look' the same... one works (N1MM), the other,
> not so much!
>
> Joe, in case you didn't pick up on last night's exchange with Bill & I;
> We got the rigctl, to function and give back some readings... one way
> worked & gave false & nonsense reports, the other did not (gave the
> proper frequency readout) & Bill said he needed to review the
> situation further to understand why my rig seems to operate not as
> expected.

John,

let's start from the WSJT-X settings you have there. To make them
equivalent to the settings we used Yesterday with the rigctl tool, when
it successfully read the rig's frequency, you need to do the following:

1) check the "Settings->Radio->Data Bits->Default" option,
2) check the "Settings->Radio->Stop Bits->Default" option,
3) check the "Settings->Radio->Handshake->None" option,
4) change the "Settings->Radio->Force Control Lines" "DTR" and "RTS"
options to blank.

I'm not necessarily saying that will work as there may be a problem with
the TS440 Hamlib driver, but nevertheless the above changes are the
correct ones. Once you have made all of those changes press the "Test
CAT" button and report back what error you get please?

73
Bill
G4WJS.




--
73 - John - N7GHZ



Locked Re: Z5stayhome Logging Issue

Stan Galonski <sgalonski1@...>
 

Bill,

Thanks, I must have missed the notice in the group, I'll upgrade ASAP.


73,

Stan
KK3KK

In a message dated 5/13/2020 6:23:38 PM Pacific Standard Time, g4wjs@... writes:

On 14/05/2020 01:14, Stan Galonski via groups.io wrote:
Worked a ZW5STAYHOME station and it logged as RR73, anyone else have this problem?

Stan
KK3KK

Stan,

the currently supported official general availability version of WSJT-X is v2.1.2.

73
Bill
G4WJS.


Locked Re: Z5stayhome Logging Issue

Bill Somerville
 

On 14/05/2020 01:14, Stan Galonski via groups.io wrote:
Worked a ZW5STAYHOME station and it logged as RR73, anyone else have this problem?

Stan
KK3KK

Stan,

the currently supported official general availability version of WSJT-X is v2.1.2.

73
Bill
G4WJS.