[wsjt-devel] rc7 and Call 1st - Yes, it's still active

Field Day Configuration. Still checking out rc7 since it hasn't locked out so far. So why not run with it? For some reason in FT8 and calling CQ, even though Call 1st is UNCHECKED, about every other sequence an automatic response will be generated to a random station calling me. Sometimes this

Re: [wsjt-devel] rc7 Band Activity layout with AP decode of CQ

On 6/16/19 at 2:06 AM, rich...@lamont.me.uk (Richard Lamont) wrote: Ubuntu MATE 18.04 amd64 WSJT-X 2.1.0-rc7 d03900 When a CQ gets AP decoded, the country gets shifted to the right of the AP message. So it says something like "a1 Norway". See attached screenshot. Is this supposed to happen?

Re: [wsjt-devel] rc7: Highlight by Mode not remembered

On 11/06/2019 08:57, DG2YCB, Uwe wrote: Hi, Just made the following observation: With v2.1.0-rc7 “Highlight by Mode” is not remembered. Checked that box, closed and started WSJT-X again, and the box is always unchecked. Error is reproducible here at my computer. Someone else having this

[wsjt-devel] rc7: Highlight by Mode not remembered

Hi, Just made the following observation: With v2.1.0-rc7 "Highlight by Mode" is not remembered. Checked that box, closed and started WSJT-X again, and the box is always unchecked. Error is reproducible here at my computer. Someone else having this issue? 73 de Uwe, DG2YCB

Re: [wsjt-devel] RC7 Contest "Lockout"

ia wsjt-devel Sent: Sunday, June 9, 2019 6:57 AM To: WSJT-Devl Cc: David Kaplan Subject: [wsjt-devel] RC7 Contest "Lockout" I think you have several choices for future versions: 1) Ignore the fact that people don’t read and just click through the existing splash screen. Downside is t

[wsjt-devel] RC7 Contest "Lockout"

I think you have several choices for future versions: 1) Ignore the fact that people don’t read and just click through the existing splash screen. Downside is the many messages of people who think the software is malfunctioning. 2) During the “lockout” period either replace the splash screen

Re: [wsjt-devel] RC7 - STOPPED FUNCTIONING.

Sun, 9 Jun 2019 11:10:26 +0200 Luigi Casari kirjoitti: > I just downloaded yesterday and today stop to work. Hi ! 73, Luis > HB9CXZ This shows, that manuals and popup winows are NOT Needed! Next time Joe, make splas cover full window and small ACCEPT point what to mark, before OK is functional

Re: [wsjt-devel] RC7 - STOPPED FUNCTIONING.

I just downloaded yesterday and today stop to work. Hi ! 73, Luis HB9CXZ > Il giorno 9 giu 2019, alle ore 02:40, Yoshi,I ha scritto: > > and popup window said > > By design it will be nonfunction during the 2019 ARRL June VHF contest(June > 8-10) and Field day (June 22-23) weekend. > > So,I

Re: [wsjt-devel] RC7 - STOPPED FUNCTIONING.

and popup window said By design it will be nonfunction during the 2019 ARRL June VHF contest(June 8-10) and Field day (June 22-23) weekend. So,I think it will start after that period. de JH8XVH On Sun, 09 Jun 2019 08:20:18 +0900 "Yoshi,I" さんは書きました。: > Hi > > I'm too. in Japan. > > 73 >

Re: [wsjt-devel] RC7 - STOPPED FUNCTIONING.

Hi I'm too. in Japan. 73 de JH8XVH Yoshi On Sun, 9 Jun 2019 10:27:34 +1200 ZL3GAV wrote. : > Hello > > Software rc-7 closes down when you click OK on the splash screen. Tried > reinstalling, no success. Release version works correctly. > > I am running Windows 10 Pro 64 ver 1903, on Dell

Re: [wsjt-devel] RC7 - STOPPED FUNCTIONING.

Ignore last, I have just trad the prior post Thanks Gavin ZL3GAV visit my website https://ZL3GAV.com From: ZL3GAV Sent: Sunday, 9 June 2019 10:28 To: wsjt-devel@lists.sourceforge.net Subject: RC7 - STOPPED FUNCTIONING. Hello Software rc-7 closes

Re: [wsjt-devel] RC7 - STOPPED FUNCTIONING.

This version (according to the opening splash screen) is also timed, but it waited until 1800 UCT and the contest start. I was running rc7 for about 5 or 6 hours today and even into the contest. All was good till I decided to shut it down and restart rc7. As EXPECTED, it died per notice. Went

[wsjt-devel] RC7 - STOPPED FUNCTIONING.

Hello Software rc-7 closes down when you click OK on the splash screen. Tried reinstalling, no success. Release version works correctly. I am running Windows 10 Pro 64 ver 1903, on Dell Inspiron i7. The earlier release candidate was time-bombed for 8 June. It happens to be 9 June in

Re: [wsjt-devel] rc7 Subprocess Error ... exit code 2

> On Jun 7, 2019, at 8:32 AM, Bill Somerville wrote: > > On 07/06/2019 14:29, Derek Turner via wsjt-devel wrote: >> This just happened with FT4. >> >> I accidentally got into two QSOs simultaneously and the program did not send >> 73 to the second station so I triggered it manually with

Re: [wsjt-devel] rc7 Subprocess Error ... exit code 2

On 07/06/2019 14:29, Derek Turner via wsjt-devel wrote: This just happened with FT4. I accidentally got into two QSOs simultaneously and the program did not send 73 to the second station so I triggered it manually with TX6:-. Running: C:\WSJT\wsjtxRC7\bin\jt9 -s WSJT-X -w 1 -m 3 -e

[wsjt-devel] rc7 Subprocess Error ... exit code 2

This just happened with FT4.  I accidentally got into two QSOs simultaneously and the program did not send 73 to the second station so I triggered it manually with TX6:-. Running: C:\WSJT\wsjtxRC7\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtxRC7\bin -a C:\Users\Derek\AppData\Local\WSJT-X -t

[wsjt-devel] rc7 64b multi monitor problem

I have a 3 monitor setup and all the 32bit versions have always remembered WSJTx window positions once set from start to start as well as all configuration and version changes. Just loaded the 64bit version. It always starts up with the windows off the right edge of the right monitor. I have to

Re: [wsjt-devel] RC7 sequence problem

Wouldn't this logic work? #1 is73 -- current logic#2 ignore if has2calls and not mybasecall So that's a standard 73 between two parties not including me.  Is there a 73 that has two calls that would be valid and not contain my call? Mike On Wednesday, June 5, 2019, 6:34:40 AM CDT, Bill

Re: [wsjt-devel] RC7 sequence problem

On 05/06/2019 12:21, Black Michael via wsjt-devel wrote: Was in middle of QSO with K8HC and he had to give a 73 to somebody else. Autosequence moved me to TX1 instead of staying on TX3.  So I had to click TX3. Seems to me that lines that contain a different call then the QSO in progress and

[wsjt-devel] RC7 sequence problem

Was in middle of QSO with K8HC and he had to give a 73 to somebody else.Autosequence moved me to TX1 instead of staying on TX3.  So I had to click TX3.Seems to me that lines that contain a different call then the QSO in progress and not my call should not affect sequencing at all. de Mike

[wsjt-devel] RC7 Mock Contest -- Best S+P, Missing Contest Exchanges and RTTY Roundup

(I re-posted this from the correct email address.) I participated in the FT4 mock contest a bit today and made 68 contacts. Most QSOs went quickly and smoothly. I have some feedback and questions. Sometimes when I was between QSOs I enabled "Best S+P". This is a handy feature. [1]

Re: [wsjt-devel] rc7 ADIF log file

Hello Richard. Also using CQRLOG this way, v. 2.3.0 (216), and at my side logging of FT4 is working fine. Gets logged in CQRLOG as FT4, and in the wsjtx_log.adi as MFSK FT4. I have also added FT4 to the "user defined digital mode" setting on the Modes tab under Preferences. I'm using the

Re: [wsjt-devel] rc7 ADIF log file

On 04/06/2019 09:33, Richard Lamont wrote: Hi all, I see that whereas rc5 logged an FT4 QSO as "FT4", rc7 is logging it as "MFSK FT4". I assume this is intentional and ADIFically correct, but it has confused CQRlog 2.3.0 which is logging the QSO as MFSK. (Yes, I have added FT4 in CQRlog

[wsjt-devel] rc7 ADIF log file

Hi all, I see that whereas rc5 logged an FT4 QSO as "FT4", rc7 is logging it as "MFSK FT4". I assume this is intentional and ADIFically correct, but it has confused CQRlog 2.3.0 which is logging the QSO as MFSK. (Yes, I have added FT4 in CQRlog preferences.) I have reported this to the CQRlog

Re: [wsjt-devel] Rc7

RC7 Is RC7 still a beta development!! Ken.. G0ORH - FT4 rc5 Sent from my iPad > On 3 Jun 2019, at 23:50, VE3FBZ wrote: > > Downloaded RC7 Win 10 64 bit version > Works great. > QSOs On 14.080 > Working with JTALERT 12.13.7 ok. > Logging ok. > Response great. > Thanks a million

[wsjt-devel] Rc7

Downloaded RC7 Win 10 64 bit version Works great. QSOs On 14.080 Working with JTALERT 12.13.7 ok. Logging ok. Response great. Thanks a million Development Team. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca ___ wsjt-devel mailing

Re: [wsjt-devel] RC7 FT4 & JTALert

On 4/06/2019 5:53 am, Al wrote: FYI JTAlert seems to have a strange response to RC7/RC4.  When I am making engaged in a contact on Ft4, JTAlert displays MY call sign for each time the other station sends it. JTAlert correctly displays call signs for FT8. AL, K0VM That's to be expected

Re: [wsjt-devel] RC7 FT4 & JTALert

On 03/06/2019 20:53, Al wrote: FYI JTAlert seems to have a strange response to RC7/RC4.  When I am making engaged in a contact on Ft4, JTAlert displays MY call sign for each time the other station sends it. JTAlert correctly displays call signs for FT8. AL, K0VM Al, Laurie has made it

[wsjt-devel] RC7 FT4 & JTALert

FYI JTAlert seems to have a strange response to RC7/RC4.  When I am making engaged in a contact on Ft4, JTAlert displays MY call sign for each time the other station sends it. JTAlert correctly displays call signs for FT8. AL, K0VM ___ wsjt-devel