Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Neil Zampella]

Ken,

did you read the Quick Start guide.  Release Candidates 4 & 5 (released 
today) are only 77bit, they will NOT decode 75 bit FT8, which is 
probably why you're not seeing decodes on a normal FT8 frequency.   The 
Quick Start advises that you use the standard FT8 frequency, but use the 
audio range above 2000 for 77 bit work until the General Release in 
December.


Neil, KN3ILZ

On 11/26/2018 6:15 PM, Ken Myers wrote:

Hi
I have been successfully been using RSC3 then changing to RSC4 there 
was no decode of waterfall content. FT8 mode.


2 installations -
1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) - 
non decode,

2  HP Allinone with FT897/Singnalink. - non decode,
(both setups using HRD (up to date) for CAT control)

For all:
1.9.1 works great
2.0 RC3 works great
2.0 RC4  good waterfall (therefore good audio present) - NO decode.

uninstalling/reinstalling forward and back through versions gives the 
same result.


i have concluded:
1  I must be holding my mouth wrong - OR
2  I have missed a new setting.
3  When I have been looking/testing RC4, no RC4 (77 bit) 
transmissions. Not sure here as I have been especially been looking 
top band.


2 probably!!

In the words of the rich young ruler to Jesus - "What must I do to be 
saved?"


The other problem is occasionally the FT897 does not let go of 
transmit after sending.
Solved by closing WSJTX.  Have tried 2 soundcards, Signalink and 
Rigblaster P, - persistent intermittent. MIGHT be my aging FT897 - 
haven't ruled that out.


Great Program Great work.

Thanks
--
Cheers

Ken Myers
VK4GC

Sunnybank Hills QLD AUS
M   +61 414 487 004




---
This email has been checked for viruses by AVG.
https://www.avg.com
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RC.4 and RC.5 problem

[Ken Myers]

Problem is down this end of the world VK VU unless there are others using
it we can only get frustrated.
VK3VM fired up this morning and we did it, Also JA9PHV twenty minutes ago.

What i did was have pskreporter running on the internet, and I transmitted,
and looked for who received my FT8 signal.  It shows up with a time flag.
if you have reception indications then you are decoded by a RC4/5 station.
maybe unmanned but is auto reporting. (Settings>Reporting check enable PSK
Reporting.)
 what band is good for VU to VK3 or VK4.  Could  arrange to try a test
transmission.  Or get another ham you can communicate with to install RC5
as well.  until you get ONE QSO, you doubt yourself.. It's not you.

On Tue, 27 Nov 2018 at 14:32, Unni Tharakkal 
wrote:

> Thank you Ken . Will try and see.
> 73s and regards
> Unni - VU2TE
>
> On Tue, Nov 27, 2018 at 9:54 AM Ken Myers 
> wrote:
>
>> Hi Unni
>>
>> I had the same problem.  On HF many switched back to 1.9  to make qsos.
>> I installed RC4/5 in separate folder and can use either. (renamed the
>> shortcuts)
>>
>> I could see the waterfall but no decode. Transmissions must be from RC4/5
>> stations to decode. 77bit.
>>
>> I have made a few contacts on RC5 now.  Stick with it
>>
>> Build it and they will come!
>>
>> Ken
>>
>> On Tue, 27 Nov 2018 at 13:17, Unni Tharakkal 
>> wrote:
>>
>>> Hai
>>>
>>> I tried the new RC.4 and. latest RC.5 upgrades. On both there is no RX
>>> decode how to solve it
>>>
>>> VU2TE
>>> Unni
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>>
>>
>> --
>> Cheers
>>
>> Ken Myers
>>
>> Sunnybank Hills QLD AUS
>> M   +61 414 487 004
>>
>> ___
>> 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
>


-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RC.4 and RC.5 problem

[Unni Tharakkal]

Thank you Ken . Will try and see.
73s and regards
Unni - VU2TE

On Tue, Nov 27, 2018 at 9:54 AM Ken Myers  wrote:

> Hi Unni
>
> I had the same problem.  On HF many switched back to 1.9  to make qsos.
> I installed RC4/5 in separate folder and can use either. (renamed the
> shortcuts)
>
> I could see the waterfall but no decode. Transmissions must be from RC4/5
> stations to decode. 77bit.
>
> I have made a few contacts on RC5 now.  Stick with it
>
> Build it and they will come!
>
> Ken
>
> On Tue, 27 Nov 2018 at 13:17, Unni Tharakkal 
> wrote:
>
>> Hai
>>
>> I tried the new RC.4 and. latest RC.5 upgrades. On both there is no RX
>> decode how to solve it
>>
>> VU2TE
>> Unni
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
>
> --
> Cheers
>
> Ken Myers
>
> Sunnybank Hills QLD AUS
> M   +61 414 487 004
>
> ___
> 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

Re: [wsjt-devel] RC.4 and RC.5 problem

[Ken Myers]

Hi Unni

I had the same problem.  On HF many switched back to 1.9  to make qsos.
I installed RC4/5 in separate folder and can use either. (renamed the
shortcuts)

I could see the waterfall but no decode. Transmissions must be from RC4/5
stations to decode. 77bit.

I have made a few contacts on RC5 now.  Stick with it

Build it and they will come!

Ken

On Tue, 27 Nov 2018 at 13:17, Unni Tharakkal 
wrote:

> Hai
>
> I tried the new RC.4 and. latest RC.5 upgrades. On both there is no RX
> decode how to solve it
>
> VU2TE
> Unni
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Ken Myers]

thanks Steve

What about 6m.  My antenna is pointing south.  I note in the blurb sheet
that there is a suggestion of 50.260  not 50.313.

Ken

On Tue, 27 Nov 2018 at 11:03, Stephen Ireland  wrote:

> Ken,
>
>
>
> I am working on driving it up a bit as you can gather without upsetting
> those who have bugs to report... Yet as I state we are in “far away” lands
> to many and therefore rely heavily on propagation and its vagrancies.
>
>
>
> I am running a second instance here of 1.9.2 in parallel – sniffing the
> same Rx data; The machine used is an I7 (3770) with 16Gb RAM so it should
> handle both.
>
>
>
> Some sigs are coming back on the same frequency and are not V1 and are not
> decoding.
>
> Upgrading now to “Deep” decoding with RC5.
>
>
>
> 73
>
>
>
> Steve I
>
>
>
> Sent from Mail  for
> Windows 10
>
>
> --
> *From:* Ken Myers 
> *Sent:* Tuesday, November 27, 2018 11:49:46 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8
>
> You are the only 77bit. plenty of old format.
>
> On Tue, 27 Nov 2018 at 10:48, Ken Myers  wrote:
>
>> Thanks Steve Sanity regained!!!
>>
>> On Tue, 27 Nov 2018 at 10:43, Stephen Ireland  wrote:
>>
>>> Ken (and others),
>>>
>>>
>>>
>>> I am actually sending now (27/11/18 UTC 00:30) main band 20m at 1550 Hz.
>>>
>>> Everyone so no screaming about operating above 2K in offset as I am
>>> interested in the interaction between v1 and v2 sigs.
>>>
>>>
>>>
>>> I have been doing so for around 5 mins on a rather active band ... I
>>> will do so for around another hour or so.
>>>
>>>
>>>
>>> 73
>>>
>>>
>>>
>>> Steve I
>>>
>>>
>>>
>>> Sent from Mail  for
>>> Windows 10
>>>
>>>
>>> --
>>> *From:* Ken Myers 
>>> *Sent:* Tuesday, November 27, 2018 11:31:14 AM
>>> *To:* wsjt-devel@lists.sourceforge.net
>>> *Subject:* Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8
>>>
>>> 1 decode on 20m - frq 383 ?? seems to work.  Like fishing - have to wait
>>> quietly or NOISILY  sent out string of CQ - no fish.  Checking 6m
>>>
>>> THanks
>>>
>>>
>>> On Tue, 27 Nov 2018 at 09:53, Ken Myers 
>>> wrote:
>>>
 Thanks - shall persist

 Cheers Ken
 VK4GC

 On Tue, 27 Nov 2018 at 09:42, Bill Somerville 
 wrote:

> Hi Ken,
>
> comments in line below.
>
> On 26/11/2018 23:15, Ken Myers wrote:
> > 2 installations -
> > 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB)
> -
> > non decode,
> > 2  HP Allinone with FT897/Singnalink. - non decode,
> > (both setups using HRD (up to date) for CAT control)
> This combination of rig and interface requires a specific setup. The
> FT-817/857/897(D) series of rigs do not accept CAT commands while
> transmitting. You must *not* check the settings option
> "Settings->General->Allow Tx frequency changes while transmitting" and
> you must set the SignaLink delay knob to minimum. You should set the
> WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX"
> although
> some have found it necessary to use the CAT PTT Method to avoid any
> CAT
> commands while the rig is in Tx mode.
> >
> > For all:
> > 1.9.1 works great
> > 2.0 RC3 works great
> > 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
> >
> > uninstalling/reinstalling forward and back through versions gives
> the
> > same result.
> >
> > i have concluded:
> > 1  I must be holding my mouth wrong - OR
> > 2  I have missed a new setting.
> > 3  When I have been looking/testing RC4, no RC4 (77 bit)
> > transmissions. Not sure here as I have been especially been looking
> > top band.
> >
> > 2 probably!!
> >
> Almost certainly 3, there has been a relatively low usage to 77-bit
> FT8
> on the normal HF FT8 sub-bands. It seems that most users of RC4 have
> reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
> couple of days after a beta release. It would be good if users of RC5
> could stick with it and try to drive up the level of activity so that
> issues can be discovered before the final GA release.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


 --
 Cheers

 Ken Myers

 Sunnybank Hills QLD AUS
 M   +61 414 487 004


>>>
>>> --
>>> Cheers
>>>
>>> Ken Myers
>>>
>>> Sunnybank Hills QLD AUS
>>> M   +61 414 487 004
>>>
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> 

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Jim Shorney]

On Mon, 26 Nov 2018 16:54:20 -0500
Joe Taylor  wrote:

> A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for 
> download and use by beta testers.


Compiled from source with no issues, Kubuntu 18.04 LTS. Made three contacts on 
40M, including one rare DX from across town with my buddy K0NEB.

73

-Jim
NU0C

--
The universe we're in will reach absolute zero in three hours. Safe is 
relative. - Idris, "The Doctor's Wife"


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

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Gary McDuffie]

> On Nov 26, 2018, at 16:53, Ken Myers  wrote:
> 
> Thanks - shall persist

I monitor (unattended) 17m during daylight hours and 160m during the night.  
160m produces extremely few stations decoded with RC4.  There are a few more on 
17m during the day, but it isn’t a crowd by any means.

Gary - AG0N

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

Re: [wsjt-devel] RC5 problem with new grids on the band?

[Don Hill AA5AU]

More on this... 

When I run RC3 and reset colors, then run RC5, the colors are correct. But
when I reset colors in RC5, then it stops working and stations worked before
show up as either new grids or new stations on the band.

Don

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, November 26, 2018 9:15 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] RC5 problem with new grids on the band?

On 27/11/2018 02:35, Don Hill AA5AU wrote:
> It's not just grid squares that are not working. TG9ANF just showed up as
a new DXCC on 40 meters but I have worked him four times previously on
40-meter FT8.
>
Hi Don,

thanks for the sample ADIF, I think the problem is the band field which 
has an uppercase M in 80M for example. The ADIF specification uses uses 
lowercase in band names but WSJT-X needn't be that picky since there are 
no ambiguities.

I will send you a patched version off list to test.

73
Bill
G4WJS.



___
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

Re: [wsjt-devel] RC5 problem with new grids on the band?

[Bill Somerville]

On 27/11/2018 02:35, Don Hill AA5AU wrote:

It's not just grid squares that are not working. TG9ANF just showed up as a new 
DXCC on 40 meters but I have worked him four times previously on 40-meter FT8.


Hi Don,

thanks for the sample ADIF, I think the problem is the band field which 
has an uppercase M in 80M for example. The ADIF specification uses uses 
lowercase in band names but WSJT-X needn't be that picky since there are 
no ambiguities.


I will send you a patched version off list to test.

73
Bill
G4WJS.



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

[wsjt-devel] RC.4 and RC.5 problem

[Unni Tharakkal]

Hai

I tried the new RC.4 and. latest RC.5 upgrades. On both there is no RX
decode how to solve it

VU2TE
Unni
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RC5 problem with new grids on the band?

[Don Hill AA5AU]

It's not just grid squares that are not working. TG9ANF just showed up as a new 
DXCC on 40 meters but I have worked him four times previously on 40-meter FT8.

I'm not overly concerned about this since I use JTAlertX for all my alerting 
needs but I understand some aren't using Windows. I just thought the team 
should know.

-

The only differences I see between the WSJT-X entries and the DXKeeper entries 
in the wsjtx_log.adi file are that most of the DXKeeper grid entries are six 
figures with the first two letters capitalized and the last two letters lower 
case. The WSJT-X entries in wsjtx_log.adi are all four figure grid squares 
(with capital letters of course).

Here is an example of a DXKeeper adif entry:

80M NJ8G K 291 
3.574217 FT8 AA5AU R 
20180908 113300 113100 -04 
-13 100.0 NA 6 3 
DM33vo NJ8 AZ AZ,Maricopa 
AA5AU AA5AU 2133.0 
N033 36.250 W112 12.500 3.574309 80M 
Y Y A 
Y Y 20180910 
20180909 Y Y 
20180908 20180908 AZ 
4000-01-01 00:00:00 
GMSZ AA5AU-LA 

Here is an example of a WSJT-X adif entry:

WD5EED EM44 FT8 -06 -06 
20181127 021515 20181127 
021631 40m 7.076014 AA5AU 
EL49xu 

I switched back to v2.0.0-rc3 and all colors are correct there.

Don AA5AU



-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, November 26, 2018 7:36 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] RC5 problem with new grids on the band?

On 27/11/2018 01:26, Don Hill AA5AU wrote:
> Could the fact that the ADIF is from DXKeeper be the problem? I've been
> using the DXKeeper export for many months now and it's always worked. I have
> to use the DXKeeper export in order to keep the logs correct for both
> instances of WSJT-X I run (two radios).

Hi Don,

I can see one potential issue, if he grid squares in your ADIF export 
are lowercase they will  not be correctly matched. That is a defect that 
I will correct. Can you check your ADIF file for a suspect grid and 
confirm if it is in lowercase for the first two characters?

73
Bill
G4WJS.



___
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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5 (on CentOS 7.5)

[Richard Shaw]

On Mon, Nov 26, 2018 at 7:11 PM Mark Klein  wrote:

> Builds OK from source and I was successful in a quick QSO on 20m.
>
> I tried the Fedora RPM, but the shared library dependency versions are
> different between Fedora and CentOS, so the resulting install wouldn’t load.
>

I have been building the release candidates here:

https://copr.fedorainfracloud.org/coprs/hobbes1069/WSJT/

Once 2.0 general release happens I'll do Fedora and CentOS 7 / EPEL builds.

Thanks,
Richard
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Marco Calistri]

Il 26/11/18 19:54, Joe Taylor ha scritto:
> A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for
> download and use by beta testers.  RC5 is stable, works well, and fixes
> the known problems in RC4.  It is likely that the General Availability
> (GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be
> nearly identical to RC5.
> 
> Changes in RC5 relative to RC4 include the following:
> 
>  -  Make the "Auto Seq" checkbox sticky, again
>  -  Remove the 5-minute mouse timer
>  -  Correct the "worked before" logic for color highlighting
>  -  Add "No own call decodes" checkbox in WSPR mode
>  -  Display and log UTC (not local time) in contest operations
>  -  Validate contest QSO details before allowing logging
>  -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
>  -  Move Fox log Reset action to Fox log window context menu
>  -  Improve layout of Working Frequencies and Station Information tables
>  -  Allow deletes and editing in Fox and Contest log windows
>  -  Add Tool Tips for Fox and Contest log windows
>  -  Fix a bug causing false AP decodes in JT65 VHF+ operation
>  -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode
> 
> You may need to invoke "Settings | General | Colors | Reset
> Highlighting" on your first program start with this version.
> 
> The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read
> this entire guide before using RC5:
> http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
> 
> We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the
> conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher.
> Inevitably the necessary transition from v1.x to v2.0 protocols for FT8
> and MSK144 will cause some confusion and cross-protocol interference.
> Users of v1.9.1 and earlier are unable to decode transmissions from
> users of RC4 and later, and vice-versa.
> 
> As more users upgrade their software to WSJT-X 2.0 -- and particularly
> after the General Availability (GA) release on December 10 -- the new
> protocol should start to dominate the conventional FT8 sub-bands.  As
> soon as possible after December 10, everyone should upgrade to WSJT-X 2.0.
> 
> Download links for RC5 on Windows, Linux, and macOS can be found on the
> WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> A final FT8 "practice contest" will be held on Saturday, December 1,
> 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a
> separate announcement with more details.
> 
> If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a
> detailed report to the wsjt-devel email list,
> wsjt-devel@lists.sourceforge.net. You must subscribe to the list in
> order to post there.
> 
> The first serious FT8 contest is scheduled for the weekend of December
> 1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details
> and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits
> and encourages FT8 as well as traditional RTTY operation.
> 
> 
> ONCE MORE: As soon as possible after December 10, and certainly by
> January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible
> v2.0 version of derivative programs such as JTDX or MSHV.  As of today,
> PSKreporter statistics show roughly 3000 users of WSJT-X versions older
> than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please,
> everyone, help us to spread the word that upgrading to v2.0 after
> December 10 is very important.  There will be no looking back!
> 
>     -- 73, Joe, K1JT (for the WSJT Development Group)

Mni Tnx Joe,

To you and all the involved people!

-- 

73 de Marco, PY1ZRJ


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

Re: [wsjt-devel] RC5 problem with new grids on the band?

[WB5JJJ]

I'm finding the Grid part is almost always showing a new grid even though
that station/grid has been worked numerous times.  I just unchecked the
Grid and Grid on Band as I've found them inaccurate.  I can go the the
wstjx_log.adi and find the call/grid/band/mode logged correctly, but still
showing as "new".

Also unchecked the ITU, CQ and Continent selections.  Don't like the LoTW
showing users, I preferred it when it was the opposite, as it made the non
users stand out, so It's unchecked as well.

On Mon, Nov 26, 2018 at 7:30 PM Don Hill AA5AU  wrote:

> I did a color reset on RC5 startup (also had to disable contest mode as
> WSJT-X started in contest mode.) and read the new Quick Start Guide. Then
> all CQ decodes from stations I have already worked on the band showed they
> were all new grids on the band. This seems to not be working since all of
> the stations calling CQ at the time were already in my log on that band
> except one which showed as a new call on the band.
>
> I did work a station that was calling CQ (showing as a new grid on the band
> despite being in the log on that band already) and after the contact was
> logged, the station called CQ again and the call highlighted green as it is
> supposed to. So not sure what to make of it. My wsjtx_log.adi is an export
> of all 21,376 FT8 contacts from my DXKeeper log.
>
> Could the fact that the ADIF is from DXKeeper be the problem? I've been
> using the DXKeeper export for many months now and it's always worked. I
> have
> to use the DXKeeper export in order to keep the logs correct for both
> instances of WSJT-X I run (two radios).
>
> Yes, I did restart the program a few times.
>
> Is this is a bug? Or am I doing something wrong?
>
> Don AA5AU
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
George Cotton, WB5JJJ
PO Box 1025
Russellville, AR  72811

479.968.7737 Home
479.857.7737 Cell

DMR K5CS (Local Repeater) - 310515, CC1, TS2
DMR Arkansas - 3105

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

Re: [wsjt-devel] RC5 problem with new grids on the band?

[Bill Somerville]

On 27/11/2018 01:26, Don Hill AA5AU wrote:

Could the fact that the ADIF is from DXKeeper be the problem? I've been
using the DXKeeper export for many months now and it's always worked. I have
to use the DXKeeper export in order to keep the logs correct for both
instances of WSJT-X I run (two radios).


Hi Don,

I can see one potential issue, if he grid squares in your ADIF export 
are lowercase they will  not be correctly matched. That is a defect that 
I will correct. Can you check your ADIF file for a suspect grid and 
confirm if it is in lowercase for the first two characters?


73
Bill
G4WJS.



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

[wsjt-devel] Not much activity in the DFW area on 77 bit

[Chuck Furman]

I loaded RC5 this afternoon. I went to 40m and almost immediately made five
contacts. I got great signal reports. Then. nothing.  The waterfall has
been completely full of strong signals, but nothing was decoding. No 77 bit
signals.  I called CQ on and off for three hours. No responses. So I
checked the PSK Reporter. I’m in Dallas, Texas. My signal was being
received in four European countries, two South American countries and all
over NA. Many people were receiving me at over +10db SNR. Obviously, a lot
of people are monitoring for 77 bit signals. Did I already work all these
people? Are all these stations unattended? I suspect it’s a combination of
these things.

My conclusion so far is that RC5 is working very well. It’s just very
lonely limiting myself to 77 bits.

Chuck
KG6PH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] RC5 problem with new grids on the band?

[Don Hill AA5AU]

I did a color reset on RC5 startup (also had to disable contest mode as
WSJT-X started in contest mode.) and read the new Quick Start Guide. Then
all CQ decodes from stations I have already worked on the band showed they
were all new grids on the band. This seems to not be working since all of
the stations calling CQ at the time were already in my log on that band
except one which showed as a new call on the band.

I did work a station that was calling CQ (showing as a new grid on the band
despite being in the log on that band already) and after the contact was
logged, the station called CQ again and the call highlighted green as it is
supposed to. So not sure what to make of it. My wsjtx_log.adi is an export
of all 21,376 FT8 contacts from my DXKeeper log. 

Could the fact that the ADIF is from DXKeeper be the problem? I've been
using the DXKeeper export for many months now and it's always worked. I have
to use the DXKeeper export in order to keep the logs correct for both
instances of WSJT-X I run (two radios).

Yes, I did restart the program a few times.

Is this is a bug? Or am I doing something wrong?

Don AA5AU



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

[wsjt-devel] Candidate release WSJT-X 2.0.0-rc5 (on CentOS 7.5)

[Mark Klein]

Builds OK from source and I was successful in a quick QSO on 20m.

I tried the Fedora RPM, but the shared library dependency versions are 
different between Fedora and CentOS, so the resulting install wouldn’t load.


73 de km6aow
---
Mark Klein






signature.asc
Description: Message signed with OpenPGP
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Ken Myers]

PSK reporter is saying 2 VK2s and some JAs are hearing me so I'm happy.
Cheers

On Tue, 27 Nov 2018 at 10:50, Stephen Ireland  wrote:

> Ken,
>
>
>
> Gotcha ... First as well ... but first sig was on a “hint”...
>
> 003930 Tx 1550 ~ CQ VK3VM QF11
>
> 003945 1 0.2 1551 ~ VK3VM VK4GC QG62 a2
>
> 004000 Tx 1550 ~ VK4GC VK3VM +01
>
> 004015 3 0.2 1551 ~ VK3VM VK4GC R+02
>
> 004030 Tx 1550 ~ VK4GC VK3VM RR73
>
> 004045 4 0.2 1551 ~ VK3VM VK4GC 73
>
> 004100 Tx 1550 ~ CQ VK3VM QF11
>
> 004115 6 0.2 1551 ~ 1ST ON RC5 TN
>
> Try setting “Enable AP” if not set. I am moving to “Deep Decode” now.
>
>
>
> If others can hear Ken and I please come out and respond. Propagation into
> K is reasonable for Rx for me here in Warrnambool, SW Victoria, VK.
>
>
>
> 73
>
>
>
> Steve I
>
> Vk3VM / VK3SIR
>
>
>
> Sent from Mail  for
> Windows 10
>
>
> --
> *From:* Ken Myers 
> *Sent:* Tuesday, November 27, 2018 11:31:14 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8
>
> 1 decode on 20m - frq 383 ?? seems to work.  Like fishing - have to wait
> quietly or NOISILY  sent out string of CQ - no fish.  Checking 6m
>
> THanks
>
>
> On Tue, 27 Nov 2018 at 09:53, Ken Myers  wrote:
>
>> Thanks - shall persist
>>
>> Cheers Ken
>> VK4GC
>>
>> On Tue, 27 Nov 2018 at 09:42, Bill Somerville 
>> wrote:
>>
>>> Hi Ken,
>>>
>>> comments in line below.
>>>
>>> On 26/11/2018 23:15, Ken Myers wrote:
>>> > 2 installations -
>>> > 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
>>> > non decode,
>>> > 2  HP Allinone with FT897/Singnalink. - non decode,
>>> > (both setups using HRD (up to date) for CAT control)
>>> This combination of rig and interface requires a specific setup. The
>>> FT-817/857/897(D) series of rigs do not accept CAT commands while
>>> transmitting. You must *not* check the settings option
>>> "Settings->General->Allow Tx frequency changes while transmitting" and
>>> you must set the SignaLink delay knob to minimum. You should set the
>>> WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although
>>> some have found it necessary to use the CAT PTT Method to avoid any CAT
>>> commands while the rig is in Tx mode.
>>> >
>>> > For all:
>>> > 1.9.1 works great
>>> > 2.0 RC3 works great
>>> > 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>>> >
>>> > uninstalling/reinstalling forward and back through versions gives the
>>> > same result.
>>> >
>>> > i have concluded:
>>> > 1  I must be holding my mouth wrong - OR
>>> > 2  I have missed a new setting.
>>> > 3  When I have been looking/testing RC4, no RC4 (77 bit)
>>> > transmissions. Not sure here as I have been especially been looking
>>> > top band.
>>> >
>>> > 2 probably!!
>>> >
>>> Almost certainly 3, there has been a relatively low usage to 77-bit FT8
>>> on the normal HF FT8 sub-bands. It seems that most users of RC4 have
>>> reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
>>> couple of days after a beta release. It would be good if users of RC5
>>> could stick with it and try to drive up the level of activity so that
>>> issues can be discovered before the final GA release.
>>>
>>> 73
>>> Bill
>>> G4WJS.
>>>
>>>
>>>
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>>
>>
>> --
>> Cheers
>>
>> Ken Myers
>>
>> Sunnybank Hills QLD AUS
>> M   +61 414 487 004
>>
>>
>
> --
> Cheers
>
> Ken Myers
>
> Sunnybank Hills QLD AUS
> M   +61 414 487 004
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Ken Myers]

Thanks Steve Sanity regained!!!

On Tue, 27 Nov 2018 at 10:43, Stephen Ireland  wrote:

> Ken (and others),
>
>
>
> I am actually sending now (27/11/18 UTC 00:30) main band 20m at 1550 Hz.
>
> Everyone so no screaming about operating above 2K in offset as I am
> interested in the interaction between v1 and v2 sigs.
>
>
>
> I have been doing so for around 5 mins on a rather active band ... I will
> do so for around another hour or so.
>
>
>
> 73
>
>
>
> Steve I
>
>
>
> Sent from Mail  for
> Windows 10
>
>
> --
> *From:* Ken Myers 
> *Sent:* Tuesday, November 27, 2018 11:31:14 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8
>
> 1 decode on 20m - frq 383 ?? seems to work.  Like fishing - have to wait
> quietly or NOISILY  sent out string of CQ - no fish.  Checking 6m
>
> THanks
>
>
> On Tue, 27 Nov 2018 at 09:53, Ken Myers  wrote:
>
>> Thanks - shall persist
>>
>> Cheers Ken
>> VK4GC
>>
>> On Tue, 27 Nov 2018 at 09:42, Bill Somerville 
>> wrote:
>>
>>> Hi Ken,
>>>
>>> comments in line below.
>>>
>>> On 26/11/2018 23:15, Ken Myers wrote:
>>> > 2 installations -
>>> > 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
>>> > non decode,
>>> > 2  HP Allinone with FT897/Singnalink. - non decode,
>>> > (both setups using HRD (up to date) for CAT control)
>>> This combination of rig and interface requires a specific setup. The
>>> FT-817/857/897(D) series of rigs do not accept CAT commands while
>>> transmitting. You must *not* check the settings option
>>> "Settings->General->Allow Tx frequency changes while transmitting" and
>>> you must set the SignaLink delay knob to minimum. You should set the
>>> WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although
>>> some have found it necessary to use the CAT PTT Method to avoid any CAT
>>> commands while the rig is in Tx mode.
>>> >
>>> > For all:
>>> > 1.9.1 works great
>>> > 2.0 RC3 works great
>>> > 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>>> >
>>> > uninstalling/reinstalling forward and back through versions gives the
>>> > same result.
>>> >
>>> > i have concluded:
>>> > 1  I must be holding my mouth wrong - OR
>>> > 2  I have missed a new setting.
>>> > 3  When I have been looking/testing RC4, no RC4 (77 bit)
>>> > transmissions. Not sure here as I have been especially been looking
>>> > top band.
>>> >
>>> > 2 probably!!
>>> >
>>> Almost certainly 3, there has been a relatively low usage to 77-bit FT8
>>> on the normal HF FT8 sub-bands. It seems that most users of RC4 have
>>> reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
>>> couple of days after a beta release. It would be good if users of RC5
>>> could stick with it and try to drive up the level of activity so that
>>> issues can be discovered before the final GA release.
>>>
>>> 73
>>> Bill
>>> G4WJS.
>>>
>>>
>>>
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>>
>>
>> --
>> Cheers
>>
>> Ken Myers
>>
>> Sunnybank Hills QLD AUS
>> M   +61 414 487 004
>>
>>
>
> --
> Cheers
>
> Ken Myers
>
> Sunnybank Hills QLD AUS
> M   +61 414 487 004
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Stephen Ireland]

Ken,

Gotcha ... First as well ... but first sig was on a “hint”...


003930 Tx 1550 ~ CQ VK3VM QF11

003945 1 0.2 1551 ~ VK3VM VK4GC QG62 a2

004000 Tx 1550 ~ VK4GC VK3VM +01

004015 3 0.2 1551 ~ VK3VM VK4GC R+02

004030 Tx 1550 ~ VK4GC VK3VM RR73

004045 4 0.2 1551 ~ VK3VM VK4GC 73

004100 Tx 1550 ~ CQ VK3VM QF11
004115 6 0.2 1551 ~ 1ST ON RC5 TN

Try setting “Enable AP” if not set. I am moving to “Deep Decode” now.

If others can hear Ken and I please come out and respond. Propagation into K is 
reasonable for Rx for me here in Warrnambool, SW Victoria, VK.

73

Steve I
Vk3VM / VK3SIR

Sent from Mail for Windows 10


From: Ken Myers 
Sent: Tuesday, November 27, 2018 11:31:14 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

1 decode on 20m - frq 383 ?? seems to work.  Like fishing - have to wait 
quietly or NOISILY  sent out string of CQ - no fish.  Checking 6m

THanks


On Tue, 27 Nov 2018 at 09:53, Ken Myers 
mailto:kenmyersglo...@gmail.com>> wrote:
Thanks - shall persist

Cheers Ken
VK4GC

On Tue, 27 Nov 2018 at 09:42, Bill Somerville 
mailto:g4...@classdesign.com>> wrote:
Hi Ken,

comments in line below.

On 26/11/2018 23:15, Ken Myers wrote:
> 2 installations -
> 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
> non decode,
> 2  HP Allinone with FT897/Singnalink. - non decode,
> (both setups using HRD (up to date) for CAT control)
This combination of rig and interface requires a specific setup. The
FT-817/857/897(D) series of rigs do not accept CAT commands while
transmitting. You must *not* check the settings option
"Settings->General->Allow Tx frequency changes while transmitting" and
you must set the SignaLink delay knob to minimum. You should set the
WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although
some have found it necessary to use the CAT PTT Method to avoid any CAT
commands while the rig is in Tx mode.
>
> For all:
> 1.9.1 works great
> 2.0 RC3 works great
> 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>
> uninstalling/reinstalling forward and back through versions gives the
> same result.
>
> i have concluded:
> 1  I must be holding my mouth wrong - OR
> 2  I have missed a new setting.
> 3  When I have been looking/testing RC4, no RC4 (77 bit)
> transmissions. Not sure here as I have been especially been looking
> top band.
>
> 2 probably!!
>
Almost certainly 3, there has been a relatively low usage to 77-bit FT8
on the normal HF FT8 sub-bands. It seems that most users of RC4 have
reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
couple of days after a beta release. It would be good if users of RC5
could stick with it and try to drive up the level of activity so that
issues can be discovered before the final GA release.

73
Bill
G4WJS.



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


--
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004



--
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004

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

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Stephen Ireland]

Ken (and others),

I am actually sending now (27/11/18 UTC 00:30) main band 20m at 1550 Hz.

Everyone so no screaming about operating above 2K in offset as I am interested 
in the interaction between v1 and v2 sigs.

I have been doing so for around 5 mins on a rather active band ... I will do so 
for around another hour or so.

73

Steve I

Sent from Mail for Windows 10


From: Ken Myers 
Sent: Tuesday, November 27, 2018 11:31:14 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

1 decode on 20m - frq 383 ?? seems to work.  Like fishing - have to wait 
quietly or NOISILY  sent out string of CQ - no fish.  Checking 6m

THanks


On Tue, 27 Nov 2018 at 09:53, Ken Myers 
mailto:kenmyersglo...@gmail.com>> wrote:
Thanks - shall persist

Cheers Ken
VK4GC

On Tue, 27 Nov 2018 at 09:42, Bill Somerville 
mailto:g4...@classdesign.com>> wrote:
Hi Ken,

comments in line below.

On 26/11/2018 23:15, Ken Myers wrote:
> 2 installations -
> 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
> non decode,
> 2  HP Allinone with FT897/Singnalink. - non decode,
> (both setups using HRD (up to date) for CAT control)
This combination of rig and interface requires a specific setup. The
FT-817/857/897(D) series of rigs do not accept CAT commands while
transmitting. You must *not* check the settings option
"Settings->General->Allow Tx frequency changes while transmitting" and
you must set the SignaLink delay knob to minimum. You should set the
WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although
some have found it necessary to use the CAT PTT Method to avoid any CAT
commands while the rig is in Tx mode.
>
> For all:
> 1.9.1 works great
> 2.0 RC3 works great
> 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>
> uninstalling/reinstalling forward and back through versions gives the
> same result.
>
> i have concluded:
> 1  I must be holding my mouth wrong - OR
> 2  I have missed a new setting.
> 3  When I have been looking/testing RC4, no RC4 (77 bit)
> transmissions. Not sure here as I have been especially been looking
> top band.
>
> 2 probably!!
>
Almost certainly 3, there has been a relatively low usage to 77-bit FT8
on the normal HF FT8 sub-bands. It seems that most users of RC4 have
reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
couple of days after a beta release. It would be good if users of RC5
could stick with it and try to drive up the level of activity so that
issues can be discovered before the final GA release.

73
Bill
G4WJS.



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


--
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004



--
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004

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

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Ken Myers]

1 decode on 20m - frq 383 ?? seems to work.  Like fishing - have to wait
quietly or NOISILY  sent out string of CQ - no fish.  Checking 6m

THanks


On Tue, 27 Nov 2018 at 09:53, Ken Myers  wrote:

> Thanks - shall persist
>
> Cheers Ken
> VK4GC
>
> On Tue, 27 Nov 2018 at 09:42, Bill Somerville 
> wrote:
>
>> Hi Ken,
>>
>> comments in line below.
>>
>> On 26/11/2018 23:15, Ken Myers wrote:
>> > 2 installations -
>> > 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
>> > non decode,
>> > 2  HP Allinone with FT897/Singnalink. - non decode,
>> > (both setups using HRD (up to date) for CAT control)
>> This combination of rig and interface requires a specific setup. The
>> FT-817/857/897(D) series of rigs do not accept CAT commands while
>> transmitting. You must *not* check the settings option
>> "Settings->General->Allow Tx frequency changes while transmitting" and
>> you must set the SignaLink delay knob to minimum. You should set the
>> WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although
>> some have found it necessary to use the CAT PTT Method to avoid any CAT
>> commands while the rig is in Tx mode.
>> >
>> > For all:
>> > 1.9.1 works great
>> > 2.0 RC3 works great
>> > 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>> >
>> > uninstalling/reinstalling forward and back through versions gives the
>> > same result.
>> >
>> > i have concluded:
>> > 1  I must be holding my mouth wrong - OR
>> > 2  I have missed a new setting.
>> > 3  When I have been looking/testing RC4, no RC4 (77 bit)
>> > transmissions. Not sure here as I have been especially been looking
>> > top band.
>> >
>> > 2 probably!!
>> >
>> Almost certainly 3, there has been a relatively low usage to 77-bit FT8
>> on the normal HF FT8 sub-bands. It seems that most users of RC4 have
>> reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
>> couple of days after a beta release. It would be good if users of RC5
>> could stick with it and try to drive up the level of activity so that
>> issues can be discovered before the final GA release.
>>
>> 73
>> Bill
>> G4WJS.
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
>
> --
> Cheers
>
> Ken Myers
>
> Sunnybank Hills QLD AUS
> M   +61 414 487 004
>
>

-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Edfel Rivera]

Hi Again:

Typo in previous message, I mean LOTS!!!

73'

Edfel
KP4AJ

On Mon, Nov 26, 2018 at 7:20 PM Edfel Rivera  wrote:

> Hi All:
>
> Thank you very much development team.  RC5 stable and decoding as used
> too.  Worked Alabama, California, Poland, Slovenia from Caribbean on 40m.
> Los of signals decoding.  Congratulations! I consider this a Christmas
> present!
>
> 73'
>
> Edfel
> KP4AJ
>
> p.d.
> One "bug" if can be called in that way (and I think it happens with 1.9.1
> too) when PPT is active and a Windows window is open, cursor moves until
> PPT stops.  It can be also a Windows "thing".
>
>
> On Mon, Nov 26, 2018 at 6:52 PM Edfel Rivera  wrote:
>
>> Hi All:
>>
>> Just to remind to operate beyond 2 hz.
>>
>> 73'
>>
>> Edfel
>> KP4Aj
>>
>> On Mon, Nov 26, 2018 at 6:30 PM Krzysztof Krzemiński 
>> wrote:
>>
>>> Hello,
>>> already done first contacts using RC5.
>>> SUPER
>>> Kris, SP5NOH
>>>
>>> pon., 26 lis 2018 o 22:58 Joe Taylor  napisał(a):
>>>
 A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for
 download and use by beta testers.  RC5 is stable, works well, and fixes
 the known problems in RC4.  It is likely that the General Availability
 (GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be
 nearly identical to RC5.

 Changes in RC5 relative to RC4 include the following:

   -  Make the "Auto Seq" checkbox sticky, again
   -  Remove the 5-minute mouse timer
   -  Correct the "worked before" logic for color highlighting
   -  Add "No own call decodes" checkbox in WSPR mode
   -  Display and log UTC (not local time) in contest operations
   -  Validate contest QSO details before allowing logging
   -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
   -  Move Fox log Reset action to Fox log window context menu
   -  Improve layout of Working Frequencies and Station Information
 tables
   -  Allow deletes and editing in Fox and Contest log windows
   -  Add Tool Tips for Fox and Contest log windows
   -  Fix a bug causing false AP decodes in JT65 VHF+ operation
   -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode

 You may need to invoke "Settings | General | Colors | Reset
 Highlighting" on your first program start with this version.

 The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read
 this entire guide before using RC5:
 http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

 We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the
 conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher.
 Inevitably the necessary transition from v1.x to v2.0 protocols for FT8
 and MSK144 will cause some confusion and cross-protocol interference.
 Users of v1.9.1 and earlier are unable to decode transmissions from
 users of RC4 and later, and vice-versa.

 As more users upgrade their software to WSJT-X 2.0 -- and particularly
 after the General Availability (GA) release on December 10 -- the new
 protocol should start to dominate the conventional FT8 sub-bands.  As
 soon as possible after December 10, everyone should upgrade to WSJT-X
 2.0.

 Download links for RC5 on Windows, Linux, and macOS can be found on the
 WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

 A final FT8 "practice contest" will be held on Saturday, December 1,
 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a
 separate announcement with more details.

 If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a
 detailed report to the wsjt-devel email list,
 wsjt-devel@lists.sourceforge.net. You must subscribe to the list in
 order to post there.

 The first serious FT8 contest is scheduled for the weekend of December
 1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details
 and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits
 and encourages FT8 as well as traditional RTTY operation.


 ONCE MORE: As soon as possible after December 10, and certainly by
 January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible
 v2.0 version of derivative programs such as JTDX or MSHV.  As of today,
 PSKreporter statistics show roughly 3000 users of WSJT-X versions older
 than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please,
 everyone, help us to spread the word that upgrading to v2.0 after
 December 10 is very important.  There will be no looking back!

  -- 73, Joe, K1JT (for the WSJT Development Group)


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

>>>
>>>
>>> --
>>> Kris, SP5NOH
>>>
>>> 

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Edfel Rivera]

Hi All:

Thank you very much development team.  RC5 stable and decoding as used
too.  Worked Alabama, California, Poland, Slovenia from Caribbean on 40m.
Los of signals decoding.  Congratulations! I consider this a Christmas
present!

73'

Edfel
KP4AJ

p.d.
One "bug" if can be called in that way (and I think it happens with 1.9.1
too) when PPT is active and a Windows window is open, cursor moves until
PPT stops.  It can be also a Windows "thing".


On Mon, Nov 26, 2018 at 6:52 PM Edfel Rivera  wrote:

> Hi All:
>
> Just to remind to operate beyond 2 hz.
>
> 73'
>
> Edfel
> KP4Aj
>
> On Mon, Nov 26, 2018 at 6:30 PM Krzysztof Krzemiński 
> wrote:
>
>> Hello,
>> already done first contacts using RC5.
>> SUPER
>> Kris, SP5NOH
>>
>> pon., 26 lis 2018 o 22:58 Joe Taylor  napisał(a):
>>
>>> A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for
>>> download and use by beta testers.  RC5 is stable, works well, and fixes
>>> the known problems in RC4.  It is likely that the General Availability
>>> (GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be
>>> nearly identical to RC5.
>>>
>>> Changes in RC5 relative to RC4 include the following:
>>>
>>>   -  Make the "Auto Seq" checkbox sticky, again
>>>   -  Remove the 5-minute mouse timer
>>>   -  Correct the "worked before" logic for color highlighting
>>>   -  Add "No own call decodes" checkbox in WSPR mode
>>>   -  Display and log UTC (not local time) in contest operations
>>>   -  Validate contest QSO details before allowing logging
>>>   -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
>>>   -  Move Fox log Reset action to Fox log window context menu
>>>   -  Improve layout of Working Frequencies and Station Information tables
>>>   -  Allow deletes and editing in Fox and Contest log windows
>>>   -  Add Tool Tips for Fox and Contest log windows
>>>   -  Fix a bug causing false AP decodes in JT65 VHF+ operation
>>>   -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode
>>>
>>> You may need to invoke "Settings | General | Colors | Reset
>>> Highlighting" on your first program start with this version.
>>>
>>> The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read
>>> this entire guide before using RC5:
>>> http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
>>>
>>> We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the
>>> conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher.
>>> Inevitably the necessary transition from v1.x to v2.0 protocols for FT8
>>> and MSK144 will cause some confusion and cross-protocol interference.
>>> Users of v1.9.1 and earlier are unable to decode transmissions from
>>> users of RC4 and later, and vice-versa.
>>>
>>> As more users upgrade their software to WSJT-X 2.0 -- and particularly
>>> after the General Availability (GA) release on December 10 -- the new
>>> protocol should start to dominate the conventional FT8 sub-bands.  As
>>> soon as possible after December 10, everyone should upgrade to WSJT-X
>>> 2.0.
>>>
>>> Download links for RC5 on Windows, Linux, and macOS can be found on the
>>> WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>>>
>>> A final FT8 "practice contest" will be held on Saturday, December 1,
>>> 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a
>>> separate announcement with more details.
>>>
>>> If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a
>>> detailed report to the wsjt-devel email list,
>>> wsjt-devel@lists.sourceforge.net. You must subscribe to the list in
>>> order to post there.
>>>
>>> The first serious FT8 contest is scheduled for the weekend of December
>>> 1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details
>>> and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits
>>> and encourages FT8 as well as traditional RTTY operation.
>>>
>>>
>>> ONCE MORE: As soon as possible after December 10, and certainly by
>>> January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible
>>> v2.0 version of derivative programs such as JTDX or MSHV.  As of today,
>>> PSKreporter statistics show roughly 3000 users of WSJT-X versions older
>>> than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please,
>>> everyone, help us to spread the word that upgrading to v2.0 after
>>> December 10 is very important.  There will be no looking back!
>>>
>>>  -- 73, Joe, K1JT (for the WSJT Development Group)
>>>
>>>
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>>
>>
>> --
>> Kris, SP5NOH
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
___
wsjt-devel mailing list

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Rebecca Milligan]

 

 

From: Edfel Rivera [mailto:edfelj...@gmail.com] 
Sent: Monday, November 26, 2018 6:53 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

 

Hi All:

 

Just to remind to operate beyond 2 hz. 

 

73'

 

Edfel

KP4Aj 

 

On Mon, Nov 26, 2018 at 6:30 PM Krzysztof Krzemiński  wrote:

Hello,

already done first contacts using RC5.

SUPER

Kris, SP5NOH

 

pon., 26 lis 2018 o 22:58 Joe Taylor  napisał(a):

A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for 
download and use by beta testers.  RC5 is stable, works well, and fixes 
the known problems in RC4.  It is likely that the General Availability 
(GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be 
nearly identical to RC5.

Changes in RC5 relative to RC4 include the following:

  -  Make the "Auto Seq" checkbox sticky, again
  -  Remove the 5-minute mouse timer
  -  Correct the "worked before" logic for color highlighting
  -  Add "No own call decodes" checkbox in WSPR mode
  -  Display and log UTC (not local time) in contest operations
  -  Validate contest QSO details before allowing logging
  -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
  -  Move Fox log Reset action to Fox log window context menu
  -  Improve layout of Working Frequencies and Station Information tables
  -  Allow deletes and editing in Fox and Contest log windows
  -  Add Tool Tips for Fox and Contest log windows
  -  Fix a bug causing false AP decodes in JT65 VHF+ operation
  -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode

You may need to invoke "Settings | General | Colors | Reset 
Highlighting" on your first program start with this version.

The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read 
this entire guide before using RC5:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the 
conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher. 
Inevitably the necessary transition from v1.x to v2.0 protocols for FT8 
and MSK144 will cause some confusion and cross-protocol interference. 
Users of v1.9.1 and earlier are unable to decode transmissions from 
users of RC4 and later, and vice-versa.

As more users upgrade their software to WSJT-X 2.0 -- and particularly 
after the General Availability (GA) release on December 10 -- the new 
protocol should start to dominate the conventional FT8 sub-bands.  As 
soon as possible after December 10, everyone should upgrade to WSJT-X 2.0.

Download links for RC5 on Windows, Linux, and macOS can be found on the 
WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

A final FT8 "practice contest" will be held on Saturday, December 1, 
0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a 
separate announcement with more details.

If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a 
detailed report to the wsjt-devel email list,
wsjt-devel@lists.sourceforge.net. You must subscribe to the list in 
order to post there.

The first serious FT8 contest is scheduled for the weekend of December 
1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details 
and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits 
and encourages FT8 as well as traditional RTTY operation.


ONCE MORE: As soon as possible after December 10, and certainly by 
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible 
v2.0 version of derivative programs such as JTDX or MSHV.  As of today, 
PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after 
December 10 is very important.  There will be no looking back!

 -- 73, Joe, K1JT (for the WSJT Development Group)


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



-- 

Kris, SP5NOH

 

___
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

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Ken Myers]

Thanks - shall persist

Cheers Ken
VK4GC

On Tue, 27 Nov 2018 at 09:42, Bill Somerville  wrote:

> Hi Ken,
>
> comments in line below.
>
> On 26/11/2018 23:15, Ken Myers wrote:
> > 2 installations -
> > 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
> > non decode,
> > 2  HP Allinone with FT897/Singnalink. - non decode,
> > (both setups using HRD (up to date) for CAT control)
> This combination of rig and interface requires a specific setup. The
> FT-817/857/897(D) series of rigs do not accept CAT commands while
> transmitting. You must *not* check the settings option
> "Settings->General->Allow Tx frequency changes while transmitting" and
> you must set the SignaLink delay knob to minimum. You should set the
> WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although
> some have found it necessary to use the CAT PTT Method to avoid any CAT
> commands while the rig is in Tx mode.
> >
> > For all:
> > 1.9.1 works great
> > 2.0 RC3 works great
> > 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
> >
> > uninstalling/reinstalling forward and back through versions gives the
> > same result.
> >
> > i have concluded:
> > 1  I must be holding my mouth wrong - OR
> > 2  I have missed a new setting.
> > 3  When I have been looking/testing RC4, no RC4 (77 bit)
> > transmissions. Not sure here as I have been especially been looking
> > top band.
> >
> > 2 probably!!
> >
> Almost certainly 3, there has been a relatively low usage to 77-bit FT8
> on the normal HF FT8 sub-bands. It seems that most users of RC4 have
> reverted to v1.9.1 so the volume of 77-bit traffic is low except for a
> couple of days after a beta release. It would be good if users of RC5
> could stick with it and try to drive up the level of activity so that
> issues can be discovered before the final GA release.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Edfel Rivera]

Hi All:

Just to remind to operate beyond 2 hz.

73'

Edfel
KP4Aj

On Mon, Nov 26, 2018 at 6:30 PM Krzysztof Krzemiński 
wrote:

> Hello,
> already done first contacts using RC5.
> SUPER
> Kris, SP5NOH
>
> pon., 26 lis 2018 o 22:58 Joe Taylor  napisał(a):
>
>> A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for
>> download and use by beta testers.  RC5 is stable, works well, and fixes
>> the known problems in RC4.  It is likely that the General Availability
>> (GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be
>> nearly identical to RC5.
>>
>> Changes in RC5 relative to RC4 include the following:
>>
>>   -  Make the "Auto Seq" checkbox sticky, again
>>   -  Remove the 5-minute mouse timer
>>   -  Correct the "worked before" logic for color highlighting
>>   -  Add "No own call decodes" checkbox in WSPR mode
>>   -  Display and log UTC (not local time) in contest operations
>>   -  Validate contest QSO details before allowing logging
>>   -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
>>   -  Move Fox log Reset action to Fox log window context menu
>>   -  Improve layout of Working Frequencies and Station Information tables
>>   -  Allow deletes and editing in Fox and Contest log windows
>>   -  Add Tool Tips for Fox and Contest log windows
>>   -  Fix a bug causing false AP decodes in JT65 VHF+ operation
>>   -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode
>>
>> You may need to invoke "Settings | General | Colors | Reset
>> Highlighting" on your first program start with this version.
>>
>> The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read
>> this entire guide before using RC5:
>> http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
>>
>> We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the
>> conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher.
>> Inevitably the necessary transition from v1.x to v2.0 protocols for FT8
>> and MSK144 will cause some confusion and cross-protocol interference.
>> Users of v1.9.1 and earlier are unable to decode transmissions from
>> users of RC4 and later, and vice-versa.
>>
>> As more users upgrade their software to WSJT-X 2.0 -- and particularly
>> after the General Availability (GA) release on December 10 -- the new
>> protocol should start to dominate the conventional FT8 sub-bands.  As
>> soon as possible after December 10, everyone should upgrade to WSJT-X 2.0.
>>
>> Download links for RC5 on Windows, Linux, and macOS can be found on the
>> WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>>
>> A final FT8 "practice contest" will be held on Saturday, December 1,
>> 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a
>> separate announcement with more details.
>>
>> If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a
>> detailed report to the wsjt-devel email list,
>> wsjt-devel@lists.sourceforge.net. You must subscribe to the list in
>> order to post there.
>>
>> The first serious FT8 contest is scheduled for the weekend of December
>> 1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details
>> and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits
>> and encourages FT8 as well as traditional RTTY operation.
>>
>>
>> ONCE MORE: As soon as possible after December 10, and certainly by
>> January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible
>> v2.0 version of derivative programs such as JTDX or MSHV.  As of today,
>> PSKreporter statistics show roughly 3000 users of WSJT-X versions older
>> than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please,
>> everyone, help us to spread the word that upgrading to v2.0 after
>> December 10 is very important.  There will be no looking back!
>>
>>  -- 73, Joe, K1JT (for the WSJT Development Group)
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
>
> --
> Kris, SP5NOH
>
> ___
> 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

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Bill Somerville]

Hi Ken,

comments in line below.

On 26/11/2018 23:15, Ken Myers wrote:

2 installations -
1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) - 
non decode,

2  HP Allinone with FT897/Singnalink. - non decode,
(both setups using HRD (up to date) for CAT control)
This combination of rig and interface requires a specific setup. The 
FT-817/857/897(D) series of rigs do not accept CAT commands while 
transmitting. You must *not* check the settings option 
"Settings->General->Allow Tx frequency changes while transmitting" and 
you must set the SignaLink delay knob to minimum. You should set the 
WSJT-X PTT configuration "Settings->Radio->PTT Method" to "VOX" although 
some have found it necessary to use the CAT PTT Method to avoid any CAT 
commands while the rig is in Tx mode.


For all:
1.9.1 works great
2.0 RC3 works great
2.0 RC4  good waterfall (therefore good audio present) - NO decode.

uninstalling/reinstalling forward and back through versions gives the 
same result.


i have concluded:
1  I must be holding my mouth wrong - OR
2  I have missed a new setting.
3  When I have been looking/testing RC4, no RC4 (77 bit) 
transmissions. Not sure here as I have been especially been looking 
top band.


2 probably!!

Almost certainly 3, there has been a relatively low usage to 77-bit FT8 
on the normal HF FT8 sub-bands. It seems that most users of RC4 have 
reverted to v1.9.1 so the volume of 77-bit traffic is low except for a 
couple of days after a beta release. It would be good if users of RC5 
could stick with it and try to drive up the level of activity so that 
issues can be discovered before the final GA release.


73
Bill
G4WJS.



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

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[WB5JJJ]

Ken, if you would read the Quick Start Guide or the Release Notes, all is
explained.  Your operation is 100% normal once you understand operation.


On Mon, Nov 26, 2018 at 5:32 PM Ken Myers  wrote:

> Just tried RC5 - Same problem.
>
> On Tue, 27 Nov 2018 at 09:15, Ken Myers  wrote:
>
>> Hi
>> I have been successfully been using RSC3 then changing to RSC4 there was
>> no decode of waterfall content. FT8 mode.
>>
>> 2 installations -
>> 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) -
>> non decode,
>> 2  HP Allinone with FT897/Singnalink. - non decode,
>> (both setups using HRD (up to date) for CAT control)
>>
>> For all:
>> 1.9.1 works great
>> 2.0 RC3 works great
>> 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>>
>> uninstalling/reinstalling forward and back through versions gives the
>> same result.
>>
>> i have concluded:
>> 1  I must be holding my mouth wrong - OR
>> 2  I have missed a new setting.
>> 3  When I have been looking/testing RC4, no RC4 (77 bit) transmissions.
>> Not sure here as I have been especially been looking top band.
>>
>> 2 probably!!
>>
>> In the words of the rich young ruler to Jesus - "What must I do to be
>> saved?"
>>
>> The other problem is occasionally the FT897 does not let go of transmit
>> after sending.
>> Solved by closing WSJTX.  Have tried 2 soundcards, Signalink and
>> Rigblaster P, - persistent intermittent.  MIGHT be my aging FT897 -
>> haven't ruled that out.
>>
>> Great Program Great work.
>>
>> Thanks
>> --
>> Cheers
>>
>> Ken Myers
>> VK4GC
>>
>> Sunnybank Hills QLD AUS
>> M   +61 414 487 004
>>
>>
>
> --
> Cheers
>
> Ken Myers
>
> Sunnybank Hills QLD AUS
> M   +61 414 487 004
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2RSC3 > 2RSC4 decoding disappeared FT8

[Ken Myers]

Just tried RC5 - Same problem.

On Tue, 27 Nov 2018 at 09:15, Ken Myers  wrote:

> Hi
> I have been successfully been using RSC3 then changing to RSC4 there was
> no decode of waterfall content. FT8 mode.
>
> 2 installations -
> 1  MSSurface Win10 up to date, 2 radios (FT991a & FTdx3000 both USB) - non
> decode,
> 2  HP Allinone with FT897/Singnalink. - non decode,
> (both setups using HRD (up to date) for CAT control)
>
> For all:
> 1.9.1 works great
> 2.0 RC3 works great
> 2.0 RC4  good waterfall (therefore good audio present) - NO decode.
>
> uninstalling/reinstalling forward and back through versions gives the same
> result.
>
> i have concluded:
> 1  I must be holding my mouth wrong - OR
> 2  I have missed a new setting.
> 3  When I have been looking/testing RC4, no RC4 (77 bit) transmissions.
> Not sure here as I have been especially been looking top band.
>
> 2 probably!!
>
> In the words of the rich young ruler to Jesus - "What must I do to be
> saved?"
>
> The other problem is occasionally the FT897 does not let go of transmit
> after sending.
> Solved by closing WSJTX.  Have tried 2 soundcards, Signalink and
> Rigblaster P, - persistent intermittent.  MIGHT be my aging FT897 -
> haven't ruled that out.
>
> Great Program Great work.
>
> Thanks
> --
> Cheers
>
> Ken Myers
> VK4GC
>
> Sunnybank Hills QLD AUS
> M   +61 414 487 004
>
>

-- 
Cheers

Ken Myers

Sunnybank Hills QLD AUS
M   +61 414 487 004
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] First test rc5

[SKI W4PPC]

Looking good on Windows 7 Pro, made contact with EA1YR on 40 meters...along
with KV8S..

Sincerely:
Stephen Duncheskie W4PPC Ryland Alabama.

On Mon, Nov 26, 2018 at 5:00 PM Jesús Gutiérrez Rodríguez <
jesuslua...@gmail.com> wrote:

> Good afternoon / nights from Spain
>
> A few minutes ago I just installed the new version rc5 ... no problem in
> its installation - windows 10 -
> I decoded four stations> 2000 and I worked two,, I KS, with the speed of
> before ... I think we are in luck with this version ... at least in the
> first contacts ...
> Although it does not affect anything, and as a simple comment, I noticed
> that the tab that manages Pwr control, without changing anything in the
> transceiver, I had to go down almost to maintain the same output power that
> was operating in the previous version.
> The program has been running for about thirty minutes, without any
> problem, I'm happy with your work, I think we're on the right track now ...
>
> Cordially,
> Jesus, EA1YR
> ___
> 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

[wsjt-devel] Fwd: Candidate release WSJT-X 2.0.0-rc5

[vk4qg]

FYI.worth a read, particularly the last paragraph.Allan
 Original message From: Joe Taylor  Date: 
27/11/18  7:54 am  (GMT+10:00) To: WSJT software development 
 Subject: [wsjt-devel] Candidate release 
WSJT-X 2.0.0-rc5 A fifth candidate release ("RC5") of WSJT-X 2.0 is now 
available for download and use by beta testers.  RC5 is stable, works well, and 
fixes the known problems in RC4.  It is likely that the General Availability 
(GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be nearly 
identical to RC5.Changes in RC5 relative to RC4 include the following:  -  Make 
the "Auto Seq" checkbox sticky, again  -  Remove the 5-minute mouse timer  -  
Correct the "worked before" logic for color highlighting  -  Add "No own call 
decodes" checkbox in WSPR mode  -  Display and log UTC (not local time) in 
contest operations  -  Validate contest QSO details before allowing logging  -  
Force Aqua theme on macOS to avoid issues with Mojave dark theme  -  Move Fox 
log Reset action to Fox log window context menu  -  Improve layout of Working 
Frequencies and Station Information tables  -  Allow deletes and editing in Fox 
and Contest log windows  -  Add Tool Tips for Fox and Contest log windows  -  
Fix a bug causing false AP decodes in JT65 VHF+ operation  -  Fix a bug that 
could switch unexpectedly from JT65 to JT9 modeYou may need to invoke "Settings 
| General | Colors | Reset Highlighting" on your first program start with this 
version.The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read 
this entire guide before using 
RC5:http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdfWe 
recommend using RC5 (and therefore the v2.0 FT8 protocol) in the conventional 
FT8 sub-bands at audio Tx frequencies 2000 Hz and higher. Inevitably the 
necessary transition from v1.x to v2.0 protocols for FT8 and MSK144 will cause 
some confusion and cross-protocol interference. Users of v1.9.1 and earlier are 
unable to decode transmissions from users of RC4 and later, and vice-versa.As 
more users upgrade their software to WSJT-X 2.0 -- and particularly after the 
General Availability (GA) release on December 10 -- the new protocol should 
start to dominate the conventional FT8 sub-bands.  As soon as possible after 
December 10, everyone should upgrade to WSJT-X 2.0.Download links for RC5 on 
Windows, Linux, and macOS can be found on the WSJT-X web page 
http://physics.princeton.edu/pulsar/k1jt/wsjtx.htmlA final FT8 "practice 
contest" will be held on Saturday, December 1, 0200-0300 UTC (that's Friday 
evening, Nov 30, NA time).  Watch for a separate announcement with more 
details.If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a 
detailed report to the wsjt-devel email list,wsjt-devel@lists.sourceforge.net. 
You must subscribe to the list in order to post there.The first serious FT8 
contest is scheduled for the weekend of December 1-2.  See 
https://www.rttycontesting.com/ft8-roundup/ for full details and contest rules. 
 The ARRL RTTY Roundup (January 5-6, 2019) permits and encourages FT8 as well 
as traditional RTTY operation.ONCE MORE: As soon as possible after December 10, 
and certainly by January 1, 2019, everyone should be using WSJT-X 2.0 or a 
compatible v2.0 version of derivative programs such as JTDX or MSHV.  As of 
today, PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after December 10 
is very important.  There will be no looking back! -- 73, Joe, K1JT (for 
the WSJT Development 
Group)___wsjt-devel mailing 
listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Sam W2JDB via wsjt-devel]

Thank you Bill. Made one more contact with RC5. First one on 40M, second one on 
20M.Not many decodes one either band. Will try more tomorrow morning.  Great 
job and fast turn around on the bug fixes. 73, Sam W2JDB
  -Original Message-
From: Bill Somerville 
To: wsjt-devel 
Sent: Mon, Nov 26, 2018 5:47 pm
Subject: Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

 On 26/11/2018 22:41, Sam W2JDB via wsjt-devel wrote:
  
 Quick question, Free Text msg - still limited to 13 char? if not, the pop up 
hint when the cursor hovers over that input field still shows 13 Char limit. 
 Hi Sam, no, moving from 75 to 77 bits does leave a bit more room but still not 
enough for a 14th character in free text messages. 73
 Bill
 G4WJS.
  ___
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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Bill Somerville]

On 26/11/2018 22:41, Sam W2JDB via wsjt-devel wrote:

Quick question, Free Text msg - still limited to 13 char?
if not, the pop up hint when the cursor hovers over that input field 
still shows 13 Char limit.


Hi Sam,

no, moving from 75 to 77 bits does leave a bit more room but still not 
enough for a 14th character in free text messages.


73
Bill
G4WJS.

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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Bill Somerville]

On 26/11/2018 21:54, Joe Taylor wrote:
Download links for RC5 on Windows, Linux, and macOS can be found on 
the WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html


Hi Joe,

a small update for the project web page. Fedora Linux has moved on to 
version 29 and the RPM packages are built for that version.


73
Bill
G4WJS.



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

[wsjt-devel] "FT8 Roundup" mock contest

[Joe Taylor]

Hi all,

Another one-hour "practice contest" is scheduled for Saturday, December 
1, 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  This session 
will serve as a final tune-up opportunity for those planning to operate 
in the "FT8 Roundup" on December 1-2 (more details below).


DIAL FREQUENCIES


The practice event will use dial frequencies 7.080-7.100 and 
14.130-14.150 MHz in 2 kHz increments -- the same as recommended for the 
FT8 Roundup and the ARRL RTTY Roundup (January 5-6, 2019).  Start at the 
low end, dial frequency 7.080 or 14.130.  If/when the lower sub-bands 
fill up, QSY upward in 2 kHz increments (7.082, 7.084, etc.).  (Use 
keyboard shortcuts Ctrl+Shift+F11 and Ctrl+Shift+F12 to move dial 
frequency down/up by 2 kHz.)


Everyone works everyone.  Do not use a compound or nonstandard callsign 
in this event.


To participate you must use WSJT-X 2.0 RC5 (or RC4, but RC5 is 
preferred).  Installation packages for RC5 in Windows, Linux, and macOS 
can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

A revised "Quick-Start Guide to WSJT-X 2.0" for RC5 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
Be sure to read this entire document before using WSJT-X 2.0.

PREPARATION FOR THE MOCK CONTEST


Detailed setup instructions for the FT8 Roundup are posted here:
https://www.rttycontesting.com/ft8-roundup/preparation/
They serve equally well for the practice session.

Rules for the FT8 Roundup specify 100 W maximum power output.  We 
recommend the same limit for the practice session.


OPERATING PROCEDURES


Best operating practices for FT8 in contests will surely evolve as users 
gain experience.  As initial suggestions we recommend procedures 
slightly different from those used for everyday FT8 operation.  CQing 
stations ("Run" stations) should check TX EVEN/1ST and HOLD TX FREQ, and 
select audio Tx frequencies 200, 400, 600, ..., integral multiples of 
200 Hz. Search-and-pounce (S+P) stations should uncheck TX EVEN/1ST and 
HOLD TX FREQ and should call a CQing station at 0, 60, or 120 Hz above 
the CQ frequency.  These procedures should help to contain the 
mini-pileups around Run stations to relatively small frequency ranges. 
S+P stations can use Shift+F11 and Shift+F12 to move their Tx frequency 
down/up by 60 Hz.


If a 2 kHz segment becomes too full of stations, users should QSY upward 
in 2 kHz increments, thus establishing new operating sub-bands.  Again, 
you can use Ctrl+Shift+F11 and Ctrl+Shift+F12 to QSY between 
dial-frequency sub-bands.


THE FT8 ROUNDUP, DECEMBER 1-2
-

The FT8 Roundup starts at 1800 UTC on Saturday, December 1 and ends at 
2359 UTC on Sunday, December 2, 2018.  Power limit is 100 W output: no 
high-power amplifiers!  Full contest rules are posted at 
https://www.rttycontesting.com/ft8-roundup/ .


LOOKING TWO WEEKS AHEAD
---

We are planning to make the full General Availability (GA) release of 
WSJT-X 2.0 on or before December 10, 2018.  The necessary transition 
from from WSJT-X v1.9.1 to WSJT-X v2.0 protocols for FT8 and MSK144 
should take place by the end of calendar year 2018.


THEREFORE: As soon as possible after December 10, and certainly by 
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible 
v2.0 version of derivative programs such as JTDX or MSHV.  As of today, 
PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after 
December 10 is very important.  There will be no looking back!


-- 73, Joe, K1JT


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

[wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Joe Taylor]

A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for 
download and use by beta testers.  RC5 is stable, works well, and fixes 
the known problems in RC4.  It is likely that the General Availability 
(GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be 
nearly identical to RC5.


Changes in RC5 relative to RC4 include the following:

 -  Make the "Auto Seq" checkbox sticky, again
 -  Remove the 5-minute mouse timer
 -  Correct the "worked before" logic for color highlighting
 -  Add "No own call decodes" checkbox in WSPR mode
 -  Display and log UTC (not local time) in contest operations
 -  Validate contest QSO details before allowing logging
 -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
 -  Move Fox log Reset action to Fox log window context menu
 -  Improve layout of Working Frequencies and Station Information tables
 -  Allow deletes and editing in Fox and Contest log windows
 -  Add Tool Tips for Fox and Contest log windows
 -  Fix a bug causing false AP decodes in JT65 VHF+ operation
 -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode

You may need to invoke "Settings | General | Colors | Reset 
Highlighting" on your first program start with this version.


The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read 
this entire guide before using RC5:

http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the 
conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher. 
Inevitably the necessary transition from v1.x to v2.0 protocols for FT8 
and MSK144 will cause some confusion and cross-protocol interference. 
Users of v1.9.1 and earlier are unable to decode transmissions from 
users of RC4 and later, and vice-versa.


As more users upgrade their software to WSJT-X 2.0 -- and particularly 
after the General Availability (GA) release on December 10 -- the new 
protocol should start to dominate the conventional FT8 sub-bands.  As 
soon as possible after December 10, everyone should upgrade to WSJT-X 2.0.


Download links for RC5 on Windows, Linux, and macOS can be found on the 
WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html


A final FT8 "practice contest" will be held on Saturday, December 1, 
0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a 
separate announcement with more details.


If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a 
detailed report to the wsjt-devel email list,
wsjt-devel@lists.sourceforge.net. You must subscribe to the list in 
order to post there.


The first serious FT8 contest is scheduled for the weekend of December 
1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details 
and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits 
and encourages FT8 as well as traditional RTTY operation.



ONCE MORE: As soon as possible after December 10, and certainly by 
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible 
v2.0 version of derivative programs such as JTDX or MSHV.  As of today, 
PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after 
December 10 is very important.  There will be no looking back!


-- 73, Joe, K1JT (for the WSJT Development Group)


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

Re: [wsjt-devel] Error loading LotW Users data

[Joe Taylor]

Hi Gorm,

On 11/26/2018 2:10 PM, Gorm Helt-Hansen OZ6GH wrote:


Windows 10 64 bit - WSJT-X RC4.

When starting I get the error msg: Error Loading LotW Users Data Network 
Error - SSL/TLS support not installed, cannot fetch: 
"https://lotw.arrl.org/lotw-user-activity.csv;


This error msg came between RC2 and RC3. In RC2 it worked fine.


Yes.  It has been mentioned about 999 times on this email list, along 
with reasons and work-around.  Lots of places to go for help.  You did 
read the Quick-Start Guide, right?

https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
See under LoTW Download Errors on page 5.

-- 73, Joe, K1JT


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

[wsjt-devel] Error loading LotW Users data

[Gorm Helt-Hansen]

Hi.

Windows 10 64 bit - WSJT-X RC4.

When starting I get the error msg: Error Loading LotW Users Data Network 
Error - SSL/TLS support not installed, cannot fetch: 
"https://lotw.arrl.org/lotw-user-activity.csv;


This error msg came between RC2 and RC3. In RC2 it worked fine.

73 Gorm / OZ6GH.




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

Re: [wsjt-devel] Configuration settings is not stored

[Marco Calistri]

Il 26/11/18 13:31, Bill Somerville ha scritto:
> On 26/11/2018 15:26, Marco Calistri wrote:
>> Hello,
>>
>> I would have a bug or maybe a unexpected behavior to report to devs.
>>
>> I was attempting to decode FT8 using WSJT-X RC4 but I had to switch my
>> previous settings, saved using WSJT-X 1.9.1 with my call-sign - (1.9.1
>> was using hamlib to manage the CAT) - to default settings because I had
>> not "rigctld" process on-line (in fact it is being started automatically
>> by CQRLOG, when I use WSJT-X 1.9.1).
>>
>> The weird thing is that my saved settings are not there anymore!
>>
>> If I click on drop-down Configurations menu, I find several options as:
>>
>> . Default
>> . Default
>> . PY1ZRJ
>> . Default
>> . PY1ZRJ
>> . PY1ZRJ
>> . PY1ZRJ
>>
>> But by selecting everyone of these in turn, I never get back on my saved
>> settings "PY1ZRJ" which were using hamlib CAT and serial cable PTT
>> controls.
>>
>> Regards,
>>
>> -- 73 de Marco, PY1ZRJ
>
> Hi Marco,
>
> which operating system and version is is observed on please?
>
> 73
> Bill
> G4WJS.
>
Hi Bill,

I'm running Linux openSUSE Tumbleweed.


-- 
73 de Marco, PY1ZRJ


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

Re: [wsjt-devel] Configuration settings is not stored

[Bill Somerville]

On 26/11/2018 15:26, Marco Calistri wrote:

Hello,

I would have a bug or maybe a unexpected behavior to report to devs.

I was attempting to decode FT8 using WSJT-X RC4 but I had to switch my
previous settings, saved using WSJT-X 1.9.1 with my call-sign - (1.9.1
was using hamlib to manage the CAT) - to default settings because I had
not "rigctld" process on-line (in fact it is being started automatically
by CQRLOG, when I use WSJT-X 1.9.1).

The weird thing is that my saved settings are not there anymore!

If I click on drop-down Configurations menu, I find several options as:

. Default
. Default
. PY1ZRJ
. Default
. PY1ZRJ
. PY1ZRJ
. PY1ZRJ

But by selecting everyone of these in turn, I never get back on my saved
settings "PY1ZRJ" which were using hamlib CAT and serial cable PTT controls.

Regards,

-- 73 de Marco, PY1ZRJ


Hi Marco,

which operating system and version is is observed on please?

73
Bill
G4WJS.



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

[wsjt-devel] Configuration settings is not stored

[Marco Calistri]

Hello,

I would have a bug or maybe a unexpected behavior to report to devs.

I was attempting to decode FT8 using WSJT-X RC4 but I had to switch my
previous settings, saved using WSJT-X 1.9.1 with my call-sign - (1.9.1
was using hamlib to manage the CAT) - to default settings because I had
not "rigctld" process on-line (in fact it is being started automatically
by CQRLOG, when I use WSJT-X 1.9.1).

The weird thing is that my saved settings are not there anymore!

If I click on drop-down Configurations menu, I find several options as:

. Default
. Default
. PY1ZRJ
. Default
. PY1ZRJ
. PY1ZRJ
. PY1ZRJ

But by selecting everyone of these in turn, I never get back on my saved
settings "PY1ZRJ" which were using hamlib CAT and serial cable PTT controls.

Regards,

-- 

73 de Marco, PY1ZRJ


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