Re: [wsjt-devel] (no subject)

[John Zantek]

Tried that.  Can't recover the PW to log in.

-Original Message-
From: Neil Zampella [mailto:ne...@techie.com] 
Sent: Friday, February 5, 2021 11:38 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] (no subject)

That's not going to work, you have to go to the URL shown at the bottom of
each message.

Neil, KN3ILZ

On 2/5/2021 11:30 AM, John Zantek wrote:
> unsub
>
>
>
>


___
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] (no subject)

[John Zantek]

unsub




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

Re: [wsjt-devel] iNVALIDE DATA

[John Zantek]

The Sent Exchange field is empty, which is why it objects.  It didn't get 
populated during the session when NA5D sent an R (Tx3), which  pushed your 
session into a premature RR73.  BUTwhy should that field ever be empty 
while in a contest mode?  

-Original Message-
From: Morris Wideman via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Sunday, June 28, 2020 10:51 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Morris Wideman
Subject: [wsjt-devel] iNVALIDE DATA

While trying to log a FD FT4 contact twice now I have been unable to log 
contacts due to getting this type error. Both time using FT4 mode and both 
stations were late calling or responding to my answer of their CQ FD.
I had to manually enter each QSO what am I doing wrong why will this not log. 
Using JTAlert and latest HRD.
Thanks 73 Morris WA4MIT



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

Re: [wsjt-devel] FD FT4 crashing

[John Zantek]

Done and restarted.  Since it seems to only crash when the bands busy, I 
reduced Decode to Normal.  No effect.

 

I’ve never seen the bands so busy with FT8/4 sigs.  That’s wonderful to see.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Sunday, June 28, 2020 7:58 AM
To: WSJT software development; Roy Gould
Cc: Black Michael
Subject: Re: [wsjt-devel] FD FT4 crashing

 

You have to edit the wsjt-x adi file and replace the "" with ""

 

Mike W9MDB

 

 

 

 

 

 

On Sunday, June 28, 2020, 09:56:30 AM CDT, Roy Gould mailto:roygou...@gmail.com> > wrote: 

 

 

I also had crashes on FT4 all the way out and had to restart the program. I got 
a message about invalid header in the log. I wish I had written down exactly 
what it said. Eventually it would not read the log at all so all of my contacts 
showed as not being previously worked.

 

On Sun, Jun 28, 2020 at 8:49 AM James Brown mailto:email.jabr...@gmail.com> > wrote:

Also suffered through many crashes. Restarts brought it back to life, but 
several QSOs were lost.

 

On Sun, Jun 28, 2020 at 9:36 AM Black Michael via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

Decided to work some FT4 Field Day operators and about 4 times so far WSJT-X 
2.2.2 has crashed.

Seems to be when it's in a Tx/Rx cycle but not sure about that.

It's not the WAV file causing it as a replay works just fine.

 

I had a friend reporting the same problem.

 

Mike W9MDB

___
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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FD FT4 crashing

[John Zantek]

Hate to say it, but ME TOO.  Same with some others out here in WWA.  Will 
troubleshoot after the event…after the heat of battle.  

73 John W7CD

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Sunday, June 28, 2020 7:32 AM
To: WSJT Software Development
Cc: Black Michael
Subject: [wsjt-devel] FD FT4 crashing

 

Decided to work some FT4 Field Day operators and about 4 times so far WSJT-X 
2.2.2 has crashed.

Seems to be when it's in a Tx/Rx cycle but not sure about that.

It's not the WAV file causing it as a replay works just fine.

 

I had a friend reporting the same problem.

 

Mike W9MDB

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

Re: [wsjt-devel] WSJT-X v2.2.0-rc2 Problem

[John Zantek]

Darn it, forgot the :5002 port ID.  My bad.
Tnx for reminding me, Bill.
73 John W7CD

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Sunday, May 24, 2020 6:21 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X v2.2.0-rc2 Problem

On 25/05/2020 02:06, John Zantek wrote:
> Bill,
> FWIW, rc2 won't accept the Flex6xxx rig selection here.  Tried various 
> None, Rig, FakeIt.
>
> Rig Failure
> Hamlib error: IO error while opening connection to rig
>
> It does work FB with the Kenwood TS-2000 emulation.  Win10Pro (Build 
> 18363), Flex 6400, SmartSDR v3.1.12
> 73 John W7CD

Hi John,

are you specifying the correct network address and port in the WSJT-X
"Settings->Radio->Network Server" field?

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] WSJT-X v2.2.0-rc2 Problem

[John Zantek]

Bill,
FWIW, rc2 won't accept the Flex6xxx rig selection here.  Tried various None,
Rig, FakeIt.

Rig Failure
Hamlib error: IO error while opening connection to rig

It does work FB with the Kenwood TS-2000 emulation.  Win10Pro (Build 18363),
Flex 6400, SmartSDR v3.1.12
73 John W7CD


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Sunday, May 24, 2020 5:44 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X v2.2.0-rc2 Problem

On 25/05/2020 01:40, Jim Charboneau wrote:
> This version has dropped the connection to my radio 5 time in 30 minutes.
>
> Radio --- Flex 6300
> SDR Software -- SmartSDR v. 1.11.12
>
> Thought you should know.
>
> 73
> Jim
> KC1BB

Hi Jim,

are you using the TS-2000 CAT emulation or the Flex6xxx networked CAT
connection in WSJT-X? Do you get an error message when the connection fails,
if yes then what is it including the details?

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] (no subject)

[John Zantek]

Bill,

Many new 101MP owners in the PNW have been experiencing some setup issues, 
resulting in lots of phone calls.  

Have you been able to talk to the rig with any other S/W via USB and with what 
virtual settings?

Is the PC using USB 2.0 or 3.x ?  The 101MP is unfortunately persnickety in 
that regard.

No hubs, right?

73 John W7CD

 

From: Bill [mailto:brightl...@gmail.com] 
Sent: Saturday, May 23, 2020 3:59 PM
To: WSJT software development
Subject: Re: [wsjt-devel] (no subject)

 

Hi,

 

Thanks for the quick response. I just tried HandShake = NONE and I have the 
same result - Rig Failure - HamLib Error.

 

   Any other suggestions?

 

Thanks!

 

Bill - AK6A

 

On Sat, May 23, 2020 at 3:32 PM Bill Somerville mailto:g4...@classdesign.com> > wrote:

On 23/05/2020 23:16, Bill wrote:

I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able 
to get the receive Audio Codec to work properly and I can see decodes but I get 
a “Rig Failure - Hamlib Error - Invalid configuration while opening connection 
to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish 
control communications with the radio. I’ve seen online suggestions that say 
use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I 
am also just using a USB cable from the radio to the Mac which is running High 
Sierra. I am using the following settings:

 

WSJT-X

 

RADIO TAB

 

Rig: Yaesu FT-991

 

Serial Port: /dev/cu.SLAB_USBtoUART1 

Note: Installed latest Silicon Labs Drivers - Also Available selections:

/dev/tty.SLAB_USBtoUART1

/dev/cu.SLAB_USBtoUART

/dev/tty.SLAB_USBtoUART

 

Baud Rate: 38400

Polling Interval: 1S

Data Bits: Eight

Stop Bits: Two

Handshake: Hardware

Force Control Lines: Both Empty

 

PTT Method: CAT

Mode: None

Split: Rig

 

AUDIO Tab

 

Input - USB AUDIO CODEC
Output - USB AUDIO CODEC

FTDX101MP Menu

 

FUNC --> Operation Settings
General
232C RATE - 38400
CAT RATE - 38400

FUNC --> RADIO SETTINGS
MODE SSB
SSB MOD SOURCE - REAR
REAR SELECT - USB
RPORT GAIN - 10
DATA MODE SOURCE - REAR (This is the default)
REAR SELECT - USB
DATA OUT LEVEL - 10
RPORT GAIN - 10

RADIO MAIN PANEL & DISPLAY

 

 

R.FIL - 3kHz
WIDTH - 4000Hz


APPLE COMPUTER

 

USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz
USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz

 

 

 

Any ideas what might be the issue in getting this going? Has anyone else been 
able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer 
version of HamLib for this new radio?

 

Thanks!

 

Bill - AK6A

Hi Bill,

try with "Settings->Radio->Handshake->None".

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

[wsjt-devel] F/H Feedback from a Fox

[John Zantek]

I’m relaying this for Grant/KZ1W and Rob/N7QT.  Please don’t shoot the 
messenger. 73 –John W7CD

 

-

I see on M0URX web page that VP8PJ is experiencing 10% drop of FT8 RR73 logged 
calls.  I was hopeful this was fixed for them.  We had the same problem at 
H40TT.

 

Overall, using WSTJ as a Fox is a miserable experience.  It is not a N1MM or DX 
Labs quality product.  I would encourage the WSTJ team to achieve that quality 
level asap as their first priority.  New features should not be on the list 
until then.

 

I wrote this after H40 but was reluctant to post it.  Now 4 months later it 
seems appropriate.

 

Urgent Priority bugs

 

Fox Log is missing some RR73 sent QSOs.  Called station isn't asking for a 
repeat.  These are logging ok in N1MM via udp (which saved us).  5 found in 150 
calls 11/18.  1 found in 250 calls 11/19.  Some well known calls made this 
obvious when they didn't log in Fox Log but are there in N1MM when checked 
later.

The odd format of Fox Log makes it essentially a useless database. We could 
find no way to translate it into ADIF, the standard for interchange.

 

Crashes -

1. leaving WSJT running idle for several hours (eg overnight) causes it to 
crash 2. sometimes it is necessary to use the Free Message to instruct the pile 
up.  If the message is not cleared, random characters appear in the CQ.  If it 
is cleared and then the Advanced tab is selected, WSJT crashes. Always.

 

"Slots" control is ambiguous and erratic 1. "Slots" is ambiguous- is it number 
or Tx frequencies or encoded messages?  Encoding RR73 when possible is great.

2. I could not discover why or when WSJT decided to change the number of Tx 
frequencies (streams?) up and down.  I have many screen shots to show this 
erratic and Q-rate killing behavior.

3. My goal is to modulate the number of Tx frequencies/streams being used to 
maximize the number of stations I am calling so they have a readable S/N of me. 
 This depends on many factors, including how much power I have available 
(amplifier and mains), what I know about the stations calling, their noise 
environment, who are my priorities to get into the log and Q rate.

 

Bugs that hinder Q rate

 

1. Random font changes in calling stack

2. caller window repopulates with old callers after erasing after long idle.

3. often reports two time slots at the same time 4. a blank message screen 
inhibits Enable TX, any character allows TX 5. often get a blank settings 
screen, need to restart 6. some TX drops in middle of 3rd RR response 7. 
inconsistent reporting of in process transactions in working window 8. calling 
pane has calls not selected.  they just show up.  RR sent to stations I haven't 
selected or on my caller screen.

9. to self spot in the normal band is a TOTAL PITA when running F/H. 

Frequency shifts are killers to reset after any action.  Sending a "Free Msg"  
only sends once then resets to "Gen Msg" AFTER the start of the repeat. BRAIN 
DEAD.  All this takes too long 10. reloads prior band callers after a band 
change even after several erases.  Had to restart to make them go away.

11. Free msg and Gen msg logic is screwed up.  Should stay selected for several 
repeats (N=3?)  Messages like "H40 QSY 21091" need repeats.

12. Fox Log logs by start time which makes it difficult to see if Q's are 
actually logged.  It requires scrolling around to find them. Logging should be 
at last RR73 sent time.

13. I understand there will be a fix for repeatedly hit Tx Enable when calls 
remain in the calling list.

 

 

Features for increasing FH Q rate

 

1. widen calling stack, when Fox log and N1MM log are on screen there isn't 
enough space.  Can't see signal reports.  Left side of screen is a waste of 
pixels for little useful information.

2. resets of freq is a real pain FH > normal > FH.  Often need to look at the 
usual band and then resets happen more than once.

3. enable changing priorities of calling stack.  I want to group S/N so I can 
shift 1, 2, 3 TX streams so need similar S/N together.

4. enable Erasing individual calling stations.

5. block callers <1000Hz in the working screen that I am not working.

6. big change - change working list pane to 1 to 5 streams of vertical stations 
being worked for better understanding of what is going on. (or some better way 
to display multi Tx Streams) 7. show stats of number of R and RR repeats in 
past 10 minutes, 1, 2, 3 repeats, # of fails.  Enables optimizing Tx streams 8. 
show a bold red line in events if no responses between time slots, remind op 
that nothing happened.

9. Many ops world wide using FT8 don't understand F/H mode.  A surprising 
number think our two radios are good to a combined dozen hertz master clock 
differential - ie they call on exactly their 1000Hz. 

They forget that is 21,075,000 and that ±10Hz is 0.5ppm combined frequency 
difference on 15m.  WSJT should advise - Tx above 1050Hz or set the decode 
limit at 950Hz.

10. enable selecting number of R 

[wsjt-devel] Fox N-Slots

[John Zantek]

The H40TT team is reporting an issue and has asked 'how to lock the number of 
N-slots as a Fox'.  They are observing the number of slots auto-decreasing, 
even when the queue is loaded with strong signals.  This makes the pileup 
worse, extending the queue rather than working to reduce it.

What would make the N-slots value change dynamically other than the length of 
the queue?

They have no internet access on Pigeon Island, but we can back-channel via 
InReach.

73 John W7CD





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

Re: [wsjt-devel] State QSO Parties

[John Zantek]

> the source code you are referring to is the validation for GUI input when 
> entering one's state or province, it has no bearing on what is packed into 
> transmitted messages other than the selected value is used. 

Ahagot it.  Understood now, thank you, Bill.

> it might be possible for one or maybe two QSO Party formats but who decides 
> which QSO Parties get support and which ones are excluded?

Am I standing out on a dangerous limb (NPI), if each QP sponsor decides, then 
compiles a branch that supports their QP, and distributes it on their QP web 
site?  As a Salmon Run sponsor, I know the desire is significant here (from 
inquiries to salmon...@wwdxc.org), even if some other states may have said NTY. 
 

Pending a more global solution/new protocol payload, I'm simply looking for 
answers in behalf of our contestants.  You KNOW that the ARRL Radiosport folks, 
as well as many noobs entering the contesting community, et al, would love to 
see it.  I also eagerly await the Dec QST to see what's said about FT8 in the 
2019 FD results.

Thank you & 73
John W7CD




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

Re: [wsjt-devel] State QSO Parties

[John Zantek]

*  The bottom line is that there are still a handful of selectors available in 
the FT4/FT8/MSK144 message payload bits that could be used for new message 
schemes but nowhere near the number that would be needed to support a series of 
county based QSO parties or similar.

But Bill, isn’t the FD message structure just that, with a lookup table that 
doesn’t exceed the payload ceiling?

What’s the difference between the existing QRegularExpression 
field_day_exchange_re with a table of ARRL/RAC Sections and a proposed 
QRegularExpression WA_QSO_party_exchange_re of WA counties  as I had suggested 
at the start of this thread?

73 John W7CD

 

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

Re: [wsjt-devel] State QSO Parties

[John Zantek]

> index into a table of 64 values (48 states + 14 provinces + DC + DX) takes a 
> mere 7 bits to store.

Hi Bill,

Yes, I initially saw that and it's why I attempted to clone the FD table, 
substituting the 39 WA counties for 58 ARRL Sections.  That table obviously 
fits, right?

I'm guessing it wouldn't be wise to have 50 or 60 other tables for the various 
QSO parties.  Texas' table would be the basic 64 values & 254 counties; a 
resultant 9 bits requirement?  

Be gentle.  My Reptilian brain is being stretched. 

73 John W7CD





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

[wsjt-devel] State QSO Parties

[John Zantek]

AKA "All I want for Christmas is something big for WSJT-X 2.2"

I just finished the 2019 Washington Salmon Run (our state QSO party), both as a 
contestant and a coordinator.  My DX Club sponsors the event.  See 
www.wwdxc.org/salmonrun

This year, we were inundated with inquiries of "Can we use FT8 or FT4?", all of 
which I had to answer "No, sorry, not this year".  I see Nebraska supported 
WSJT-X for their QSO party, but it required a totally separate log.  Our Board 
felt the Salmon Run is too big and popular to create a whole separate category 
and scoring system, and I didn't want to see the use of FreeMsg frames being 
blasted blindly into the ether with unacknowledged County exchanges.  I felt it 
was just abusive and counter to the vision of WSJT-X's smart design.

I do believe that adding direct support to all the State QSO Parties could be 
the 'next big thing' for WSJT-X.  Adding FD last year was a step in that 
direction.  So rather than just ask, I thought "well, what would it require?"

CQ WAQP W7CD CN87
   W7CD K7ABC SPO(Spokane County)
K7ABC W7CD R KITS   (Kitsap County)
   W7CD K7ABC RR73

Thus, I submit a blind start:

//  QRegExp message_alphabet {"[- A-Za-z0-9+./?]*"};
  QRegularExpression message_alphabet {"[- @A-Za-z0-9+./?#<>]*"};
  QRegularExpression WA_QSO_party_exchange {
R"(
(
   AL|AZ|AR|CA|CO|CT|DE|FL|GA  # 48 contiguous states
  |ID|IL|IN|IA|KS|KY|LA|ME|MD
  |MA|MI|MN|MS|MO|MT|NE|NV|NH|NJ
  |NM|NY|NC|ND|OH|OK|OR|PA|RI|SC
  |SD|TN|TX|UT|VT|VA|WA|WV|WI|WY
  |NB|NS|QC|ON|MB|SK|AB|BC|NWT|NF  # VE provinces
  |LB|NU|YT|PEI
  |DC  # District of Columbia
  |DX  # anyone else outside WA
  |ADA|ASO|BEN|CHE|CLAL|CLAR|COL   # 39 WA counties
  |COW|DOU|FER|FRA|GAR|GRAN|GRAY
  |ISL|JEFF|KING|KITS|KITT|KLI
  |LEW|LIN|MAS|OKA|PAC|PEND|PIE
  |SAN|SKAG|SKAM|SNO|SPO|STE|THU
  |WAH|WAL|SHA|WHI|YAK 
)
  )", QRegularExpression::CaseInsensitiveOption | 
QRegularExpression::ExtendedPatternSyntaxOption};

  
Of course, it's not just that simple, I knowbut I feel strongly enough 
about the subject that I'm willing to try my hand at coding, something I've not 
done since my FORTRAN77 and PDP-11 school days.

True, there are some arguments against putting in the effort.
- Texas has 254 Counties.  My fingers ache just thinking about it.
- Not every State has a QSO Party.  Out west, those states without the support 
resources for their own QP (OR, MT, WY, etc) created the 7th Area QSO Party 
(7QP), which is wildly popular.  It's exchange field requires a field of 5 
characters (2-ltr-State + 3-ltr County).
-Instead of a QRegExp for each QP, a matrix of A through Z would 
support any 5-ltr combo a particular State QP sponsor might devise.  Of course, 
that leaves it to the end user to populate them in Settings/Advanced.  Texans 
would think that insane.  7QP'ers would call it cruel and unusual punishment.

Am I the only Voice in the Wilderness that thinks this would be worth it?  WA 
is happily willing to shift from 4 letter County abbreviations to 3 letter if 
it helps!

73 John W7CD







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

Re: [wsjt-devel] FT8/FT4 frequency change bug?

[John Zantek]

*  I noticed that while using the FT8 mode on a standard FT8 frequency, when 
when the FT4 mode is selected from the "Mode" pull down list, the frequency is 
changed to the correct  FT4 frequency for that band. 

 

*  However, after using FT4, when the user selects the FT8 mode from the "Mode" 
pull down menu, the mode changes, but WSJT-X does NOT change to the correct FT8 
frequency for that band. It remains on the FT4 frequency. This holds true for 
all bands. 

 

I’m not experiencing that here, Rich.  When I shift back to FT8 after working 
some FT4 stations, it does revert to the correct FT8 frequency for that band.  
Sorry.

 

73 John W7CD

 

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

Re: [wsjt-devel] WSJT-X 2.1.0 64-bit GA release: TX audio level has changed

[John Zantek]

Same here, on a Flex with Win10 x64 Pro.  Knowing that there were issues with 
the RC’s, I wasn’t surprised to see that.

 

I quickly downloaded 2.1.0 32-bit GA and tested.  Yes, the expected higher 
output is restored when running the 32-bit GA release.

 

73 John W7CD

 

From: Paul Kube [mailto:paul.k...@gmail.com] 
Sent: Monday, July 15, 2019 9:19 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJT-X 2.1.0 64-bit GA release: TX audio level has 
changed

 

>  Anyone else experiencing that with the 64-bit version?

 

Yes. 

 

Tune power also.

 

IC-7300, Win 10 x64 Pro.

 

73, Paul K6PO

 

 

On Mon, Jul 15, 2019 at 8:52 AM DG2YCB, Uwe mailto:dg2...@gmx.de> > wrote:

Many thanks for the new GA version! Works well so far here on my computer
(64-bit Windows).
One observation: With the new 64-bit GA version I needed to increase PWR
slider from around 50 % to now nearly 100 % to get sufficient audio level at
my FT-991. Old settings resulted in a few mW TX output. Will do some further
tests, but seems to be reproducible.
Anyone else experiencing that with the 64-bit version?

73 de Uwe, DG2YCB



___
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] Just Dupes, or Autodupes?

[John Zantek]

While everything functioned normally at my end of the world during this
evening's FT8 RU mock, I was puzzled by the number of dupes directed my way.

I was playing the role of a RUN station, transmitting at :00 and :30, and
had 3 stations who worked me, then turned around immediately and called me
again after our exchange was complete. E.g, he sent RR73, I sent 73, and
they would start over with a W7CD W1AA 579 MA.  In this particular case, the
call and state are only an example, not one of the actual three stations.

I'd write it off to simple testing by one operator, maybe even 2, but three?
Did anyone else experience this?  Has there been a contest mode exchange
condition that would cause this?  

Was I hallucinating?  :-)

73 John W7CD




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

[wsjt-devel] RC5 Test

[John Zantek]

Took RC5 for a run late this afternoon on 40M.  6 quick Q's, including 1 DX.
Other than the need to Reset Highlighting at the start (previously
reported), there were no issues.  Very smooth and stable.  Very grateful to
Joe, Steve, Bill for this latest.

Look forward to the FT8 Roundup this weekend.

73 John W7CD




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

Re: [wsjt-devel] RTTY roundup dups

[John Zantek]

I, too, was running JTAlertX last night for the ‘test, but for a different 
reason than to check dupes.  JTAlertX and Log4OM are my regularly day-to-day 
system.  N1MM+ is only launched during contests.  Since JTAlertX is basing dupe 
declaration on my big log and not the contest, I’m very happy to hear that RC5 
will report dupes independently, based on a contest-by-contest effort.  

 

It just keeps getting better.  :)

 

From: John Kludt [mailto:johnnykl...@gmail.com] 
Sent: Tuesday, November 20, 2018 8:54 AM
To: WSJT-Dev 
Subject: Re: [wsjt-devel] RTTY roundup dups

 

David,

 

Actually I found JTAlters very useful for exactly that reason - dup checking.  
But see Joe's note - already handled in RC5 or the GA release.

 

John

 

On Tue, Nov 20, 2018 at 11:19 AM David Kjellquist mailto:d...@kjellquist.com> > wrote:

Has anyone come up with ideas for avoiding dups when using FT8 in a 
large contest? JTAlert checks B4 but its display matrix is limited and 
not really designed for contest use. N1MM log integration works well but 
I don't see that it checks for dups prior actual log entry (not much 
help). But, I'm not really N1MM literate so I may be missing something.

JTAlert does preload a call into AClog but I can't check N3FJP contest 
logs since N3FJP integration is AClog only.

-- 
Dave, WB5NHL
5BDXCC, 308 countries confirmed
206 wrkd FT8, 159 confirmed



___
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] RTTY RU Test Results

[John Zantek]

Everything worked marvelously here, though I noticed the WSJT-X Contest Log was 
recording local times.  Moot for me since N1MM+ was doing the primary 
logging/tracking mults/etc.  Happy camper here; tnx so very much to all the 
WSJT-X team.

73 John W7CD

 

ARRLRTTY Summary Sheet

  Start Date : 2018-11-17

CallSign Used : W7CD

  Operator(s) : W7CD

 

Operator Category : SINGLE-OP

Assisted Category : ASSISTED

 Band : ALL

Power : LOW

 Mode : DIGITAL

Overlay Category : OVER-50

Default Exchange : WA

   Gridsquare : CN87PS

 ARRL Section : WWA

Club/Team : Western Washington DX Club

 Software : N1MM Logger+ 1.0.7342.0

 

Band   Mode  QSOs Pts  Sec  DXC  Pt/Q

   7  FT8 42  42   204   1.0

   Total  Both42  42   204   1.0

 

Score : 1,008

  Rig : Flex 6400 w/SteppIR DB-18e

 

 

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

[wsjt-devel] 2.0rc4 Auto Seq & N1MM+

[John Zantek]

Two small items.

I keep tripping over the new default of Auto Seq (and thereby Call 1st) being 
OFF when I launch the application.  It’ll take a few more embarrassing moments 
before I build the new habit, but I’m really curious why the change?  Was it 
because of the negative feedback from those claiming WSJT-X is an auto-QSO 
machine?  Well, “haters are still gonna hate”, and changing the default won’t 
change their disdain.

Thanks for working out the contest logging and I’m looking forward to the next 
public test.  However, maybe I’ve created my own in-house problem with dupe 
logging as I’ve previously experienced.  I’ve normally used JTAlert-X and 
Log4OM for my regular operation.  For the ‘tests, I simply launched N1MM+ 
additionally, and perhaps somehow created my own dupes in N1MM+.  Should I be 
NOT be using JTAlert-X during the contests?

I am still very, very appreciative of all the continued work going into the 
development of WSJT-X; it brought me back to the hobby after decades away.  
Adding both the RTTY RU and FD ability is a quantum leap that will now allow 
hams with modest stations to play in the tall weeds with the big dogs 
(borrowing the quote from the movie Wall Street).  How WSJT-X/FT8 will grow to 
contain more complex contest exchanges (7QP comes to mind) is anyone’s guess.  
I’ll be working with the Salmon Run committee (WA State QSO Party) to ensure 
both the SR’s exchange and WSJT-X’s report capabilities are a match next 
September.

73 John W7CD

 

___
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-rc4

[John Zantek]

Two thumbs up from the west coast.
73 John W7CD


-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Tuesday, November 13, 2018 6:17 AM
To: WSJT software development 
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

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

Changes in RC4 relative to RC3 include the following:

  -  Fix the "cannot open file fort.81" bug
  -  Avoid too many redirect loops related to openSSL support
  -  Fix the auto-generated messages for nonstandard callsigns
  -  Remove all support for the legacy FT8 protocol
  -  Disallow selecting MSK144 with RTTY or Field Day messages active
  -  Correct and expand support for color highlighting decoded messages
  -  ESC key aborts a QSO, clears DX Call, and selects Tx6
  -  Disable "nextCall" procedure for RTTY contest; it still needs work
  -  Correct a flaw in handling MSK144 Sh messages
  -  Prevent Fox from inadvertently toggling Tx 1st/Even
  -  Re-organize the Fox/Hound/Contest selection boxes
  -  Improve the validators for contest exchange boxes
  -  Disable Tx after 5 minutes of no mouse movement
  -  Remove end-of-line AP info when using contest messages
  -  Fix the Sent and Rcvd exchanges sent to N1MM+ and ADIF log
  -  Don't auto-log a QSO with incomplete exchange info
  -  Fix two sequencing flaws after double-clicks on a decoded msg
  -  New facilities for Contest and Fox-mode logging

Be sure 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 revised and extended.  If Be 
sure to read this entire guide before using RC4:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

As described in the Quick-Start Guide, at this time we recommend moving
MSK144 activity back to the standard 6-meter working frequencies: 50.360 MHz in 
IARU Region 1, 50.260 in Regions 2 and 3. We recommend also starting to use the 
v2.0 FT8 protocol in the conventional FT8 sub-bands — for example, dial 
frequencies 7.074 and 14.074 MHz on 40 and 20 meters. Inevitably this will 
cause some initial confusion: users of
v1.9.1 and earlier will be unable to decode transmissions from users of 
v2.0.0-rc4, and vice-versa. To minimize this cross-protocol interference we 
suggest initially using the RC4 release at audio Tx frequencies 2000 Hz and 
higher. As more users upgrade their software to RC4 or later, activity can 
gradually move downward in audio frequency. By December 10 or very soon 
afterward, everyone should upgrade to the full WSJT-X 2.0 general availability 
(GA) release.

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

A one-hour "FT8 mock contest" will be held next week: November 20,
0200-0300 UTC (that's Monday evening, Nov 19, NA time).  Watch for a separate 
announcement with more details.

We look forward to your feedback on WSJT-X 2.0-rc4.  Reports should be sent to 
the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You must subscribe 
to the list in order to post there.

 -- 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



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

Re: [wsjt-devel] VP6D on wrong time slot

[John Zantek]

I just worked him on 40M, George, and he was transmitting on EVEN.  I’m 
assuming there’s only one operator and he’s running two stations.

 

John W7CD

 

From: WB5JJJ [mailto:wb5...@gmail.com] 
Sent: Monday, October 22, 2018 7:02 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] VP6D on wrong time slot

 

Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
half of the callers are on EVEN and the others on ODD.  How is the happening?  
He's using DX Fox according to what I'm seeing from him.  



-- 

George Cotton, WB5JJJ

 

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

[wsjt-devel] DXpedition Mode 2.0 v 1.9.1

[John Zantek]

I just finished working ZL7X as a Hound with 2.0rc3 while he was a Fox with
1.9.1.  Just as a test, I selected Hound on my settings, but then unchecked
the 77-bit message types.  No problem, though I suspect that will be changed
in rc4, since the authors want only the new protocol in the GA.

 

Looking forward to the next public test for RTTY RU.

 

73 John W7CD

 

 

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

Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

[John Zantek]

Did it really take from 12:43 to 16:08 for my post to make it through the 
reflector?  Talk about a pileup! :)

 

From: John Zantek [mailto:j...@zantek.net] 
Sent: Wednesday, October 17, 2018 12:43 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

 

Implemented Option 4, as suggested.  Issue fixed.  Thank you, Bill.

 

73 John W7CD

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, October 17, 2018 12:26 PM
To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
Subject: Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

 

On 17/10/2018 18:23, Bill Somerville wrote:

Open a Command prompt window (*not* Administrator mode), 

type the following command at the prompt: 

where libeay32.dll 

and report back the results printed. 

Thanks all for the reports. As expected the problem is that some users have no 
OpenSSL libraries installed and others have a variety of versions supplied with 
various other packages.

There is no perfect solution to this, for example:

1) It would be great to package the right OpenSSL libraries with WSJT-X but US 
state and local legislation about strong cryptography software prevents us from 
doing that easily.

2) We could recommend that users install the OpenSSL libraries separately and 
copy them into the WSJT-X bin directory but this will cause problems for the 
WSJT-X uninstaller when later upgrading.

3) We could recommend that users install the OpenSSL libraries separately and 
add their location to the PATH environment variable but other applications are 
likely to undo that by doing the same with the version of OpenSSL they need.

4) We could recommend that users install the OpenSSL libraries separately and 
let the installer copy them to the system directory, this is not usually 
recommended as it may break other applications.

So I am going to go with the least bad of the above options which I think is 
(4). Instructions below.

By the way, the reason OpenSSL is required is that the ARRL web server will not 
respond to insecure requests (http) and only serves secure URLs (https). If an 
http request is made then it redirects to an https equivalent.

Those experiencing LotW download errors can try the following:

Download the OpenSSL installer for Windows from here: 
https://slproweb.com/products/Win32OpenSSL.html , specifically the "Win32 
OpenSSL v1.0.2p Light" version. Note that this is the right version even if you 
are running 64-bit Windows. Download link is 
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2p.exe .

Run the downloaded installer taking default options and accept the option to 
install the libraries into the Windows system directory.

Please report back on if this solves the issues? You will probably need to 
restart WSJT-X.

For those that have tried copying random OpenSSL DLLs into their WSJT-X bin 
directory, you will need to remove them as well.

73
Bill
G4WJS.

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

Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

[John Zantek]

Implemented Option 4, as suggested.  Issue fixed.  Thank you, Bill.

 

73 John W7CD

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, October 17, 2018 12:26 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

 

On 17/10/2018 18:23, Bill Somerville wrote:

Open a Command prompt window (*not* Administrator mode), 

type the following command at the prompt: 

where libeay32.dll 

and report back the results printed. 

Thanks all for the reports. As expected the problem is that some users have no 
OpenSSL libraries installed and others have a variety of versions supplied with 
various other packages.

There is no perfect solution to this, for example:

1) It would be great to package the right OpenSSL libraries with WSJT-X but US 
state and local legislation about strong cryptography software prevents us from 
doing that easily.

2) We could recommend that users install the OpenSSL libraries separately and 
copy them into the WSJT-X bin directory but this will cause problems for the 
WSJT-X uninstaller when later upgrading.

3) We could recommend that users install the OpenSSL libraries separately and 
add their location to the PATH environment variable but other applications are 
likely to undo that by doing the same with the version of OpenSSL they need.

4) We could recommend that users install the OpenSSL libraries separately and 
let the installer copy them to the system directory, this is not usually 
recommended as it may break other applications.

So I am going to go with the least bad of the above options which I think is 
(4). Instructions below.

By the way, the reason OpenSSL is required is that the ARRL web server will not 
respond to insecure requests (http) and only serves secure URLs (https). If an 
http request is made then it redirects to an https equivalent.

Those experiencing LotW download errors can try the following:

Download the OpenSSL installer for Windows from here: 
https://slproweb.com/products/Win32OpenSSL.html , specifically the "Win32 
OpenSSL v1.0.2p Light" version. Note that this is the right version even if you 
are running 64-bit Windows. Download link is 
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2p.exe .

Run the downloaded installer taking default options and accept the option to 
install the libraries into the Windows system directory.

Please report back on if this solves the issues? You will probably need to 
restart WSJT-X.

For those that have tried copying random OpenSSL DLLs into their WSJT-X bin 
directory, you will need to remove them as well.

73
Bill
G4WJS.

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

Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

[John Zantek]

Did that, including a reboot.  No change.

"Error Loading LotW User Data" "Network Error: SSL handshake failed"

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Wednesday, October 17, 2018 12:00 PM
To: 'WSJT software development' 
Cc: Black Michael 
Subject: Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

 

If you're still getting the redirect error copy these two files into 
\wsjt\wsjtx\bin and the problem should be solved.

 

libeay32.dll

ssleay32.dll

 

de Mike W9MDB

 

 

 

On Wednesday, October 17, 2018, 1:57:38 PM CDT, John Zantek < 
<mailto:j...@zantek.net> j...@zantek.net> wrote: 

 

 

Where libeay32.dll
C:\Program Files (x86)\Intel\iCLS Client\libeay32.dll
C:\Program Files\Intel\iCLS Client\libeay32.dll

Windows 10 Pro 64 v1809 (OS Build 17763.55)

-Original Message-
From: Bill Somerville [mailto: <mailto:g4...@classdesign.com> 
g4...@classdesign.com] 
Sent: Wednesday, October 17, 2018 10:24 AM
To: WSJT software development < <mailto:wsjt-devel@lists.sourceforge.net> 
wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

Hi All,

I need some help from the community to try and diagnose these issue. I
suspect it is an OpenSSL problem with old version of the OpenSSL DLLs being
used. It would be nice to package the OpenSSL libraries with WSJT-X but fro
legal reasons that is not possible so we are somewhat at the mercy of what
is installed on your systems.

Can those of you having LotW User Data file download errors on Windows, that
are easily repeatable, please do the following:

Open a Command prompt window (*not* Administrator mode),

type the following command at the prompt:

where libeay32.dll

and report back the results printed.

73
Bill
G4WJS.



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





___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> 
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] WSJT-X v2.0.0 RC3 LotW Users Data File errors

[John Zantek]

Where libeay32.dll
C:\Program Files (x86)\Intel\iCLS Client\libeay32.dll
C:\Program Files\Intel\iCLS Client\libeay32.dll

Windows 10 Pro 64 v1809 (OS Build 17763.55)

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, October 17, 2018 10:24 AM
To: WSJT software development 
Subject: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors

Hi All,

I need some help from the community to try and diagnose these issue. I
suspect it is an OpenSSL problem with old version of the OpenSSL DLLs being
used. It would be nice to package the OpenSSL libraries with WSJT-X but fro
legal reasons that is not possible so we are somewhat at the mercy of what
is installed on your systems.

Can those of you having LotW User Data file download errors on Windows, that
are easily repeatable, please do the following:

Open a Command prompt window (*not* Administrator mode),

type the following command at the prompt:

where libeay32.dll

and report back the results printed.

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

[wsjt-devel] 2.0.0-rc2 N1MM+ Logging

[John Zantek]

Followup from last night’s RU and logging issues.  The Cabrillo log generated 
by WSJT-X is accurate, but as others have also noted is what N1MM+ logged and 
produced is incorrect and unscorable since it can only take what the UDP 
broadcast from WSJT-X has offered it.  The native WSJT-X ADIF file also had 
neither contest exchange info nor conventional dB signal reports.

 

Another observation, although not of particular concern for the Development 
Team, but offered to others on the list: I saw a lot of newbies participating 
in the test, e.g., callsigns I’d not previously seen in the past 20 months of 
FT8 history.  That’s wonderful, and I assume that many of them are from the 
traditional contest community.  However, I was also troubled to see so many 
terrible signals, with many of them very strong as well as overdriven.  We 
really need to remind those coming to the WSJT-X world that they need to pay 
attention to their OS audio device settings and to look at their ALC meters.  
This is particularly true for those who are going to run with amplifiers.  
There were obvious QRO stations who were pounding me in WA with +dB sigs and 
getting 579 reports from my end.  BTW, what’s the scale and range that 2.0 is 
using to determine the RST?   I had a station work me who was decoded at +11 
(and was 20 over S-9 on the radio), but my response was only 579.  I’d pour 
through the tarball, but I normally use Git (and previously SVN) to build my 
WSJT-X, and 2.0 hasn’t been shared in that manner yet.

 

The RU test was the most fun I’ve had with WSJT-X since FT8 capability arrived 
in my shack last July.  55 contacts and I didn’t have to S, only call CQ once 
a while and move only as a courtesy when the waterfall was getting too crowded 
and overlapping.  Can’t wait to unleash this at Winter Field Day in January 
with the logging solved!

 

 



cabrillo.log
Description: Binary data


W7CD.log
Description: Binary data


wsjtx.log
Description: Binary data
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 Mock Contest Findings

[John Zantek]

Bob,
Thus far, you're the ONLY person to report no issues with logging the
correct exchanges, and Joe says that WSJT-X 2.0 doesn't report those
exchanges.  Can you share a K4DJG.log Cabrillo from N1MM with us?
73 John W7CD

-Original Message-
From: Bob VanFossen [mailto:bob.vanfos...@gmail.com] 
Sent: Thursday, September 27, 2018 2:24 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] FT8 Mock Contest Findings

I too logged to both N1MM and DXKeeper. I was using JTAlert to check Dups
and also to log to DXK.

I encountered no errors with either log, and contents of the logs were as
expected. Operated the entire hour, and logged 23 contacts.

Looking forward to another test, and hoping for a similar set of tests for
the FD procedures.


Bob, K4DJG





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

Re: [wsjt-devel] FT8 Mock Contest Findings

[John Zantek]

   > 1. In  contest it might be best not to require clicking "OK" to log each 
QSO.  Instead, log the contact automatically when we receive or transmit RR73 
or 73.

YES, but optional in Files/Settings/Advanced (or perhaps a whole new Contests 
tab).  Isn't that what 'Prompt me to log' is supposed to already accomplish?

   > 2. We need to implement a simple way for a "Run" station to queue up the 
next station to be called, during a QSO already in progress.  This could double 
the maximum possible QSO rate.

YES!  That was *really* slowing my rate last night.

   > 3. Activity during a real contest will not fit into a single 3 kHz 
sub-band.  We need to seek the best possible way to organize use of a wider 
band, say 20 or 30 kHz, perhaps with dial frequencies spaced at
3 kHz intervals.

Concur, although there may be some additional whining from the combined crowd 
of those who are anti-digital and those who complain that they can't chew the 
rag on contest weekends.  20-30kHz might be bit too aggressive.  Oh, well.  
Remember poet John Lydgate's "You can please some of the people..."

   > 4. Would it be helpful to filter decoded messages so that transmissions 
from already-worked stations don't appear in the left window?

B4 colored white on white and thus blanked for only that contest?  Another 
optional setting, but only on that particular band, of course.  I want P49X on 
each band as a multiplier.  (Hi, Ed!)

   >  5. Should there be a convention that "Run" stations transmit in the 1st 
sequence, S+P stations in the 2nd?

Hmmm.  That would be an interesting thing for the next public test, with rc3.  
With only the existing 3-4kHz window, the definitions of Run and S are 
blurred in my mind.

Best 73,
John W7CD






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

[wsjt-devel] 2.0-rc2 N1MM+ Logging

[John Zantek]

Great fun on the 1st 2.0 contest ‘test’, but I’m not seeing the complete 
exchange coming through and being logged by N1MM+.  Instead of, for example, 

 

559 TX

 

I’m only getting



59

 

I am listening on the correct port. 2333 is listed on both WSJT-X and N1MM+.

 

Any comment?

 

73 John W7CD

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

Re: [wsjt-devel] Cabrillo File Generation

[John Zantek]

Don, et al,

 

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

 

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

 

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

 

Best 73

John W7CD

 

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

 

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

 

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

 

I just wanted to see how it's done.

 

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

 

Thanks!

Don AA5AU

 

  _  

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

 

Hi Don,

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

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

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

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

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

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

... and one like this at the end:

END-OF-LOG:

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

Do you have some deadline in mind?

-- 73, Joe, K1JT




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

 

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

[wsjt-devel] FW: Candidate release WSJT-X 2.0-rc1

[John Zantek]

Belay my last!
I only needed to close the application and relaunch after making the changes
after the download/installation/overwrite of my previous 1.9.2-devel.  This
might still be considered a minor bug, however.  Win10Pro/1803.
73 John W7CD

-Original Message-
From: John Zantek [mailto:j...@zantek.net] 
Sent: Monday, September 17, 2018 11:28 AM
To: 'WSJT software development' 
Subject: RE: [wsjt-devel] Candidate release WSJT-X 2.0-rc1

Immediately, I'm drawn to test the new operating activity features.  I've
moved to 14.078, found a partner for OTA testing, but the 'Enable Tx'
doesn't engage.
Advanced Tab has both 77-bit choices (Generate/Decode) checked, as well as
'ARRL FD' selected and the Exch field populated (1A WWA in my case).
'Generate Std Msgs' does not produce anything in the Tx1-Tx5 fields,
although Tx6 does show CQ FD W7CD CN87.

Have I overlooked something obvious?  I didn't see anything in the Quick
Start guide precluding such testing.  (Yes, Test CAT is working fine).  How
do I enable the Tx?

73 John W7CD

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Monday, September 17, 2018 9:27 AM
To: WSJT software development 
Subject: [wsjt-devel] Candidate release WSJT-X 2.0-rc1

WSJT-X 2.0 will be a major program release with many new features.

The first candidate release, WSJT-X 2.0-rc1, is now available for download
and use by beta testers.  This candidate release is your first chance to
test the new features and provide feedback to the WSJT Development Group.

New features and enhancements since Version 1.9.1 are summarized here:

http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt


The WSJT-X User Guide has not yet been upgraded for Version 2.0.  If you
plan to use the beta-test release candidate, be sure to read the "Quick
Start Guide to WSJT-X 2.0" first:

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


Further details and a download link to the Windows installation package can
be found on the WSJT-X web site:

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

Installation packages for Linux and macOS should be available in a few days.

We look forward to your feedback on WSJT-X 2.0-rc1.  Reports should be sent
to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. 
You must subscribe to the list to post there.

-- 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



___
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-rc1

[John Zantek]

Immediately, I'm drawn to test the new operating activity features.  I've
moved to 14.078, found a partner for OTA testing, but the 'Enable Tx'
doesn't engage.
Advanced Tab has both 77-bit choices (Generate/Decode) checked, as well as
'ARRL FD' selected and the Exch field populated (1A WWA in my case).
'Generate Std Msgs' does not produce anything in the Tx1-Tx5 fields,
although Tx6 does show CQ FD W7CD CN87.

Have I overlooked something obvious?  I didn't see anything in the Quick
Start guide precluding such testing.  (Yes, Test CAT is working fine).  How
do I enable the Tx?

73 John W7CD

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Monday, September 17, 2018 9:27 AM
To: WSJT software development 
Subject: [wsjt-devel] Candidate release WSJT-X 2.0-rc1

WSJT-X 2.0 will be a major program release with many new features.

The first candidate release, WSJT-X 2.0-rc1, is now available for download
and use by beta testers.  This candidate release is your first chance to
test the new features and provide feedback to the WSJT Development Group.

New features and enhancements since Version 1.9.1 are summarized here:

http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt


The WSJT-X User Guide has not yet been upgraded for Version 2.0.  If you
plan to use the beta-test release candidate, be sure to read the "Quick
Start Guide to WSJT-X 2.0" first:

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


Further details and a download link to the Windows installation package can
be found on the WSJT-X web site:

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

Installation packages for Linux and macOS should be available in a few days.

We look forward to your feedback on WSJT-X 2.0-rc1.  Reports should be sent
to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. 
You must subscribe to the list to post there.

-- 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



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

[wsjt-devel] TX5T in DXpedition Mode

[John Zantek]

Just wanted to share some pleasing observations of the TX5T team’s first night 
of FT8 operation on 40M.  It’s all good.

 

The team’s published Plan was to be on 7056kHz, so I set my rig on 7056, and 
moved my antenna to the needed azimuth before going to bed.  I happened to wake 
up ~0800 UTC (old guys have a tendency to wake up in the middle of the night 
for various reasons, hi hi) but checking my screen, saw TX5T up at the TOP end 
of my waterfall, not the bottom.  On another screen (I have 3 in my shack), I 
saw that TX5T was just showing up on pskreporter.info about that time, but 
apparently on 7058kHz.  No problem, so I quickly added 7058 to my frequency 
list in WSJT-X and clicked to QSY to the new selection.

 

The waterfall was wonderfully full!  TX5T had up to 5 channels running at the 
low end of the waterfall, there was the expected empty DMZ, and then about 
20-24 stations north of the 1k mark, overwhelmingly JA and HL.  There was no 
confusion, misadventures, or DQRM.  It was very crowded, but everyone seemed to 
find a tight but clean spot to call.  A few US stations were valiantly trying 
but, initially, not getting answered, myself included.  TX5T was knocking out 
Asian stations at a rate I never saw with the Baker team last month, and they 
had only just arrived on the air.

 

Suddenly, TX5T started exclusively answering the US stations and within 4 
minutes, had cleared the whole North American queue.  Bravo, I thought, the Fox 
is paying attention to his backlog and responded directionally.  Now clear, the 
op went back to the endless hoard of JA callers.  Despite very noisy conditions 
(A-index was 16 at the time), I was seeing almost NO repeats….just dozens and 
dozens of stations being worked and logged.  

 

I’d like to think that there are many good things happening as use of 
DXpedition mode becomes more common.  First, having the docs in languages other 
than English is huge.  It was apparent the JA crowd had gotten the message and 
read the instructions this time around.  Second, the TX5T team had both 
practiced and better understood the role and management features of the Fox AND 
didn’t suffer from PC hangups as in the earlier workups of some other Foxes.  
TX5T didn’t skip a beat for two straight hours last night, and probably kept 
sailing after I went back to bed.  Finally, of course, credit to the 
development team for 1.9.2.

 

I’d really like to see those first night’s logs after they get posted.  It 
should tell a wonderful story.

 

Oh, and one other thing I thankfully DIDN’T see: monster signals at +05 and 
beyond, or harmonic signals bracketing others.  Yep, there weren’t any 
amplifiers in evidence.

 

73 John W7CD

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Icom and Yaesu CAT USB Interface

[John Zantek]

Tnx Bill!

John

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, July 4, 2018 12:58 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Icom and Yaesu CAT USB Interface

 

On 04/07/2018 01:18, John Zantek wrote:

Sorry if it sounds like I’m demanding, Bill.  Please substitute ‘disappointed’ 
that I’ve not stumbled into the solution, or found anyone who’s worked on 
ic7700.c and has a IC-7700 to explain the architecture they used when they 
coded it.  It’s copyrighted 2010 by Stephane Fillod, but I’ve not found a way 
to contact him.

Hi John,

the Hamlib project has it's own mailing list that you can find on their 
SourceForge project page: 
https://sourceforge.net/projects/hamlib/?source=directory .

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X

[John Zantek]

Not daft at all, Tom.  While we're still pursuing a completely
LAN-transported audio/CAT solution, I now have a borrowed Icom USB-CT17 FTDI
(USB type-A to miniplug) cable enroute in order to affect a HW workaround.
Film at 11, as the newscasters say.

 

I'm having to add a Y-cable, since the CAT port on the rig also provides the
source for the SteppIR controller, needed for autotracking/tuning.

 

From: Tom Melvin [mailto:t...@tkrh.co.uk] 
Sent: Tuesday, July 3, 2018 5:54 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X

 

John

 

Sorry if this is a daft question - the link you gave shows an RS232 port on
the back - why not just hook that up to a PC - it looks like the optional
CT17 is only required if you connect to the 'Remote' port.

 

You indicated you had the audio working fine just the cat needed - use the
RS232 port?

 

73's

Tom 

 

 

On 4 Jul 2018, at 00:55, John Zantek mailto:j...@zantek.net> > wrote:





Neil.there's no bidirectional USB type-B port on a 7700.  The DX Commander
doc doesn't include the 7700. 

The two type-B connections on the back of the rig are 'borrowed' by the Icom
engineers for audio connections only.

 
<http://www.icom.co.jp/world/support/download/manual/pdf/IC-7700_ENG_IM_6.pd
f>
http://www.icom.co.jp/world/support/download/manual/pdf/IC-7700_ENG_IM_6.pdf

 

We have the audio working via the Icom Remote Utility app.  We don't have
CAT control with anything OTHER than Icom's Remote RS-BA1 console.

 

John

 

From: Neil Zampella [mailto:ne...@techie.com] 
Sent: Tuesday, July 3, 2018 4:39 PM
To: wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net> 
Subject: Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X

 

John,

I don't think that Hamlib or Omnirig uses UDP packets to control the rig,
its more a bidirectional serial interface, sending ascii or hex.That
said, I know that DX Commander can control the IC-7700 using a USB
conection.

Check this url:
<http://www.dxlabsuite.com/dxlabwiki/ConnectingIcom72007600>
www.dxlabsuite.com/dxlabwiki/ConnectingIcom72007600

Neil, KN3ILZ

 

On 7/3/2018 3:52 PM, John Zantek wrote:

Tnx, Neil, and I agree that there are HW workarounds to accomplish the goal.
I'm just still amazed that additional HW would be needed, given that the
IC-7700 has a fully functional LAN port and firmware server.  I've even
found some Youtube videos "claiming" that third party apps like FLDigi,
etc., should work via the LAN (UDP 50001-50003) for both CAT and audio, but
none have demonstrated it successfully. 

 

Quite maddening for a top level rig with built-in RTTY and PSK and
manufacturer-supplied networking tools (Remote Utility app) and full remote
capability, albeit only with their software.  I can't believe Icom is
proprietary with its IP stack, as some say.

 

From: Neil Zampella [ <mailto:ne...@techie.com> mailto:ne...@techie.com] 
Sent: Tuesday, July 3, 2018 11:18 AM
To:  <mailto:wsjt-devel@lists.sourceforge.net>
wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

 

John,

I was using my IC-718 with full CAT control without the CT-17 using a cable
from XGGCOMMS.com <http://XGGCOMMS.com>  ... this one looks like the one you
need:

Icom CAT IC-Cable-7-USB-ISO

The interface offers full USB CAT Control and 600:600 Ohm transformer
isolated audio interfacing of your Icom Transceiver allowing you to fully
utilise software such as Ham Radio Deluxe, PSK31, DM780, N1MM Logger, MixW
and many more. 

The USB CAT part of the interface uses the highly reliable FTDI Chipset. The
audio cable uses high quality Bourns 600:600 Ohm transformers to
galvanically isolate the audio circuits to reduce the chance of ground loops
and induced mains hum and is terminated in the 8 pin Din Accessory
connector. See the radio compatibility list below.

With this interface, you will be up and running on PSK31, SSTV, Pactor,
Packet or any mode that requires CAT control and Tx/Rx Audio Interfacing
between your PC Soundcard and Radio within minutes. 

Full CAT control with PTT and Isolated TX/Rx Audio on these Icom
tranceivers.

IC-746, IC-746 Pro, IC-756 Pro, IC-756 Pro 2, IC-756 Pro3, IC-910H, IC-7400,
IC-7600, IC-7700, IC-7800

* The standard cable length is 1.8m




$46

(+ postage: $12)

    

 

Hope this helps.

Neil

On 7/3/2018 10:16 AM, John Zantek wrote:

You would think it's that simple, but no.  Icom's required CT-17
level-converter, at $139, only works with an RS-232 connection on the PC.
USB-9pin converters are evidently not supported.

 

Very frustrating.  This was a top of the line rig not too long ago.
Built-in Ethernet.  Built-in RTTY and PSK.

 

From: Black Michael via wsjt-devel [
<mailto:wsjt-devel@lists.sourceforge.net>
mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 3, 2018 5:59 AM
To: WSJT software development  <mailto:wsjt-devel@lists.sou

Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X

[John Zantek]

Neil…there’s no bidirectional USB type-B port on a 7700.  The DX Commander doc 
doesn’t include the 7700.  

The two type-B connections on the back of the rig are ‘borrowed’ by the Icom 
engineers for audio connections only.

http://www.icom.co.jp/world/support/download/manual/pdf/IC-7700_ENG_IM_6.pdf

 

We have the audio working via the Icom Remote Utility app.  We don’t have CAT 
control with anything OTHER than Icom’s Remote RS-BA1 console.

 

John

 

From: Neil Zampella [mailto:ne...@techie.com] 
Sent: Tuesday, July 3, 2018 4:39 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X

 

John,

I don't think that Hamlib or Omnirig uses UDP packets to control the rig, its 
more a bidirectional serial interface, sending ascii or hex.That said, I 
know that DX Commander can control the IC-7700 using a USB conection.

Check this url:  www.dxlabsuite.com/dxlabwiki/ConnectingIcom72007600 
<http://www.dxlabsuite.com/dxlabwiki/ConnectingIcom72007600> 

Neil, KN3ILZ

 

On 7/3/2018 3:52 PM, John Zantek wrote:

Tnx, Neil, and I agree that there are HW workarounds to accomplish the goal.  
I’m just still amazed that additional HW would be needed, given that the 
IC-7700 has a fully functional LAN port and firmware server.  I’ve even found 
some Youtube videos “claiming” that third party apps like FLDigi, etc., should 
work via the LAN (UDP 50001-50003) for both CAT and audio, but none have 
demonstrated it successfully.  

 

Quite maddening for a top level rig with built-in RTTY and PSK and 
manufacturer-supplied networking tools (Remote Utility app) and full remote 
capability, albeit only with their software.  I can’t believe Icom is 
proprietary with its IP stack, as some say.

 

From: Neil Zampella [mailto:ne...@techie.com] 
Sent: Tuesday, July 3, 2018 11:18 AM
To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
Subject: Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

 

John,

I was using my IC-718 with full CAT control without the CT-17 using a cable 
from XGGCOMMS.com ... this one looks like the one you need:

Icom CAT IC-Cable-7-USB-ISO

The interface offers full USB CAT Control and 600:600 Ohm transformer isolated 
audio interfacing of your Icom Transceiver allowing you to fully utilise 
software such as Ham Radio Deluxe, PSK31, DM780, N1MM Logger, MixW and many 
more. 

The USB CAT part of the interface uses the highly reliable FTDI Chipset. The 
audio cable uses high quality Bourns 600:600 Ohm transformers to galvanically 
isolate the audio circuits to reduce the chance of ground loops and induced 
mains hum and is terminated in the 8 pin Din Accessory connector. See the radio 
compatibility list below.

With this interface, you will be up and running on PSK31, SSTV, Pactor, Packet 
or any mode that requires CAT control and Tx/Rx Audio Interfacing between your 
PC Soundcard and Radio within minutes. 

Full CAT control with PTT and Isolated TX/Rx Audio on these Icom tranceivers.

IC-746, IC-746 Pro, IC-756 Pro, IC-756 Pro 2, IC-756 Pro3, IC-910H, IC-7400, 
IC-7600, IC-7700, IC-7800

* The standard cable length is 1.8m




$46

(+ postage: $12)



 

Hope this helps.

Neil

On 7/3/2018 10:16 AM, John Zantek wrote:

You would think it’s that simple, but no.  Icom’s required CT-17 
level-converter, at $139, only works with an RS-232 connection on the PC.  
USB-9pin converters are evidently not supported.

 

Very frustrating.  This was a top of the line rig not too long ago.  Built-in 
Ethernet.  Built-in RTTY and PSK.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 3, 2018 5:59 AM
To: WSJT software development  <mailto:wsjt-devel@lists.sourceforge.net> 

Cc: Black Michael  <mailto:mdblac...@yahoo.com> 
Subject: Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

 

According to the manual there is a DB-9 connector for CAT control.

Just need a USB adapter since the 7700 is already in WSJT-X with serial port 
control.

 

de Mike W9MDB

 

 

 

 

 

 

On Tuesday, July 3, 2018, 2:17:38 AM CDT, John Zantek mailto:j...@zantek.net> > wrote: 

 

 

Has ANYONE successfully deployed WSJT-X on an Icom IC-7700, using the Icom

RS-BA1 software for the virtual serial porting via the ethernet port on the

rig?  For those not aware, the 7700 has no conventional bidirectional USB

ports to couple a PC; the only way to allow a PC app to interface via the

LAN.

 

While I'm successful with the audio, there's no CAT control...and thus, no

DXpedition Mode capability.  

 

TIA & 73,

John KE7B

 

 

 

 

 

--

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___

wsjt-devel mailing list

wsjt-devel@lists.sourceforge.net <ma

Re: [wsjt-devel] IC-7700 Serial Over LAN - The untold story (well, it WAS untold)

[John Zantek]

Yep, did exactly that before I came to the WSJT-X group, where I’ve subscribed 
for a long time and always knew the correct answer would be forthcoming.  If 
you’ll notice, George also failed to establish CAT control with a 3rd party 
application.  In his case, he was attempting with FLDigi.  He never does 
explain, even in the screen shots later down the page, what additional things 
were necessary to make it work.  

 

I sent him an email last week.  I’m hoping to find someone who actually has an 
IC-7700 v2.0 firmware where we can step though the litany of configuration 
items to find the missing “Oh, yeah, I forgot to mention that one.”

 

Flex does TCP, which makes it oh-so-easy.  Icom is UDP.  Icom debugging is Hex 
dumps, unlike the other manufacturers.

 

Time to take this one off-line and go PM or SMS (360-434-2512), rather than 
consume more valuable developer bandwidth on the listserv.

 

73 John KE7B

 

From: Rick [mailto:n...@triad.rr.com] 
Sent: Tuesday, July 3, 2018 3:41 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] IC-7700 Serial Over LAN - The untold story (well, it WAS 
untold)

 

Good evening John,

(BTW, I tried to respond to your posted e-mail address, and the entire internet 
sneezed. It's a mess I tell you)

 

I used to explain to people that search engines such as Google could offer them 
some needed information much faster than asking a group of people on a news 
group. I should start doing that again.

 

Enter the following search term into Google without the square brackets as 
shown in the next line

[ ic-7700 serial over lan ]

and then hit enter.

 

My first hit was 

 


Icom IC7700 and Digital Modes via LAN 
<https://www.george-smart.co.uk/radio/icom_ic7700_and_digital_modes_via_lan/> 


By George Smart M1GEO

... the link is: 
https://www.george-smart.co.uk/radio/icom_ic7700_and_digital_modes_via_lan/

scroll past the Youtube Links (beware of cat videos), and the third item down 
is George's settings from the Icom Remote Utility screen.

 

Take some time and read the entire article, and then, if you have questions, 
you MAY wish to communicate with George, as it appears he's already 
accomplished the goal you seek.

Good luck with your interface quest, and for the snipping impaired, please note 
I only copied the relevant portion of the digest containing reference material 
for the answer at hand.

 

73 and Happy 4th of July

Rick

NM3G

<<<<<< begin massive snipping campaign >>>>>>>>

Message: 2
Date: Tue, 3 Jul 2018 12:52:09 -0700
From: "John Zantek"  <mailto:j...@zantek.net> 
To: "'WSJT software development'"  <mailto:wsjt-devel@lists.sourceforge.net> 

Subject: Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X
Message-ID:  <mailto:003301d41307$5458edc0$fd0ac940$@zantek.net> 
<003301d41307$5458edc0$fd0ac940$@zantek.net>
Content-Type: text/plain; charset="utf-8"
 
Tnx, Neil, and I agree that there are HW workarounds to accomplish the goal.  
I?m just still amazed that additional HW would be needed, given that the 
IC-7700 has a fully functional LAN port and firmware server.  I?ve even found 
some Youtube videos ?claiming? that third party apps like FLDigi, etc., should 
work via the LAN (UDP 50001-50003) for both CAT and audio, but none have 
demonstrated it successfully.  
 
 
 
Quite maddening for a top level rig with built-in RTTY and PSK and 
manufacturer-supplied networking tools (Remote Utility app) and full remote 
capability, albeit only with their software.  I can?t believe Icom is 
proprietary with its IP stack, as some say.
 
<<<<<<<< snipping is complete - please return your trays and seat backs in the 
upright position >>>>>>>
 
 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

[John Zantek]

True, but with a rig that has an Ethernet port, more hardware shouldn't be necessary.  I know the Flex 6xxx works well with WSJT-X via the network.  I guess we need someone to clone the code so that it uses Icom's CAT commands and IP ports. It's not a Fortran thing, so I don't have that talent.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X

[John Zantek]

Tnx, Neil, and I agree that there are HW workarounds to accomplish the goal.  
I’m just still amazed that additional HW would be needed, given that the 
IC-7700 has a fully functional LAN port and firmware server.  I’ve even found 
some Youtube videos “claiming” that third party apps like FLDigi, etc., should 
work via the LAN (UDP 50001-50003) for both CAT and audio, but none have 
demonstrated it successfully.  

 

Quite maddening for a top level rig with built-in RTTY and PSK and 
manufacturer-supplied networking tools (Remote Utility app) and full remote 
capability, albeit only with their software.  I can’t believe Icom is 
proprietary with its IP stack, as some say.

 

From: Neil Zampella [mailto:ne...@techie.com] 
Sent: Tuesday, July 3, 2018 11:18 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

 

John,

I was using my IC-718 with full CAT control without the CT-17 using a cable 
from XGGCOMMS.com ... this one looks like the one you need:

Icom CAT IC-Cable-7-USB-ISO

The interface offers full USB CAT Control and 600:600 Ohm transformer isolated 
audio interfacing of your Icom Transceiver allowing you to fully utilise 
software such as Ham Radio Deluxe, PSK31, DM780, N1MM Logger, MixW and many 
more. 

The USB CAT part of the interface uses the highly reliable FTDI Chipset. The 
audio cable uses high quality Bourns 600:600 Ohm transformers to galvanically 
isolate the audio circuits to reduce the chance of ground loops and induced 
mains hum and is terminated in the 8 pin Din Accessory connector. See the radio 
compatibility list below.

With this interface, you will be up and running on PSK31, SSTV, Pactor, Packet 
or any mode that requires CAT control and Tx/Rx Audio Interfacing between your 
PC Soundcard and Radio within minutes. 

Full CAT control with PTT and Isolated TX/Rx Audio on these Icom tranceivers.

IC-746, IC-746 Pro, IC-756 Pro, IC-756 Pro 2, IC-756 Pro3, IC-910H, IC-7400, 
IC-7600, IC-7700, IC-7800

* The standard cable length is 1.8m




$46

(+ postage: $12)



 

Hope this helps.

Neil

On 7/3/2018 10:16 AM, John Zantek wrote:

You would think it’s that simple, but no.  Icom’s required CT-17 
level-converter, at $139, only works with an RS-232 connection on the PC.  
USB-9pin converters are evidently not supported.

 

Very frustrating.  This was a top of the line rig not too long ago.  Built-in 
Ethernet.  Built-in RTTY and PSK.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 3, 2018 5:59 AM
To: WSJT software development  <mailto:wsjt-devel@lists.sourceforge.net> 

Cc: Black Michael  <mailto:mdblac...@yahoo.com> 
Subject: Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

 

According to the manual there is a DB-9 connector for CAT control.

Just need a USB adapter since the 7700 is already in WSJT-X with serial port 
control.

 

de Mike W9MDB

 

 

 

 

 

 

On Tuesday, July 3, 2018, 2:17:38 AM CDT, John Zantek mailto:j...@zantek.net> > wrote: 

 

 

Has ANYONE successfully deployed WSJT-X on an Icom IC-7700, using the Icom

RS-BA1 software for the virtual serial porting via the ethernet port on the

rig?  For those not aware, the 7700 has no conventional bidirectional USB

ports to couple a PC; the only way to allow a PC app to interface via the

LAN.

 

While I'm successful with the audio, there's no CAT control...and thus, no

DXpedition Mode capability.  

 

TIA & 73,

John KE7B

 

 

 

 

 

--

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___

wsjt-devel mailing list

wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 

https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

[John Zantek]

You would think it’s that simple, but no.  Icom’s required CT-17 
level-converter, at $139, only works with an RS-232 connection on the PC.  
USB-9pin converters are evidently not supported.

 

Very frustrating.  This was a top of the line rig not too long ago.  Built-in 
Ethernet.  Built-in RTTY and PSK.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 3, 2018 5:59 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

 

According to the manual there is a DB-9 connector for CAT control.

Just need a USB adapter since the 7700 is already in WSJT-X with serial port 
control.

 

de Mike W9MDB

 

 

 

 

 

 

On Tuesday, July 3, 2018, 2:17:38 AM CDT, John Zantek mailto:j...@zantek.net> > wrote: 

 

 

Has ANYONE successfully deployed WSJT-X on an Icom IC-7700, using the Icom

RS-BA1 software for the virtual serial porting via the ethernet port on the

rig?  For those not aware, the 7700 has no conventional bidirectional USB

ports to couple a PC; the only way to allow a PC app to interface via the

LAN.

 

While I'm successful with the audio, there's no CAT control...and thus, no

DXpedition Mode capability.  

 

TIA & 73,

John KE7B

 

 

 

 

 

--

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___

wsjt-devel mailing list

wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 

https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

[John Zantek]

Has ANYONE successfully deployed WSJT-X on an Icom IC-7700, using the Icom
RS-BA1 software for the virtual serial porting via the ethernet port on the
rig?  For those not aware, the 7700 has no conventional bidirectional USB
ports to couple a PC; the only way to allow a PC app to interface via the
LAN.

While I'm successful with the audio, there's no CAT control...and thus, no
DXpedition Mode capability.  

TIA & 73,
John KE7B





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Observation on Expedition Mode

[John Zantek]

Wholly concur with #2, but not necessarily #1, Mike.  Yes, lots of folks are 
calling in the blind.  That’s not limited to FT8, guys.  

 

But…

 

Depending on who’s running the digital tent (Don/Ned/?), rates of CQ vary from 
every 10 minutes to generate some traffic down to NONE, because there are 
stations calling.  I have a pretty ideal QTH to work Baker on any band, and I’m 
observing too much of the latter pattern.  I know there are lots of new folks 
sitting at their keyboards, waiting for the CQ, not seeing one, then walking 
away.  That’s not good, as it just reduces the rate for Baker, and frustrates 
the new ham who’s a potential DXer and digital apostle.

 

The QSB on 17M has been horrendous, with Baker’s sig, regardless of mode, 
varying wildly here.  On 17M, they were working the usual wall of JA but I 
never did see a CQ, so I entered it manually and generated the Std Msgs to work 
them successfully.  

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Saturday, June 30, 2018 7:15 AM
To: 'WSJT software development' 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Observation on Expedition Mode

 

I have some observations too.

 

#1 Tons of ops calling KH7Z when they can't see them.  I assume this only 
causes problems as it's quite possible KH7Z with their honker antennas and can 
see them but not the other way round.  So KH7Z will put them in the queue and 
try to process them taking up the limited slots they are using right now (2 
from what I've seen).  IMHO the solution to this is pretty simplewhen you 
turn on Hound or switch bands you should be PREVENTED FROM TRANSMITTING UNTIL 
YOU GET CQ FRO THE DX STATION.So, you would be required to double-click on 
a CQ to allow transmitting.  I noticed the the Baker team gave a lukewarm 
endorsement of FT8 on their news update quite likely due to this problem.

 

#2 We need to turn on spotting for the DX station so that PSKReporter and 
Hamspots can work and also so JTAlert can produce alerts when the DX station is 
received.  Don't need to spot the hounds of course.  Trying to figure out what 
band is good for local ops would be much improved with automatic spotting for 
us and for the DX team who could then see where their signal is going as more 
teams use internet on site via satellite links.

 

de Mike W9MDB

 

 

 

 

 

On Saturday, June 30, 2018, 8:13:39 AM CDT, Grant Willis mailto:vk...@bigpond.com> > wrote: 

 

 

Joe,

 

An observation if I may about expedition mode. I see with KH1/KH7Z that the 
number of Fox TX channels varies – I presume as they place more stations in the 
queue. As expected, the power per channel drops the more channels running so 
that the amplifiers can keep up. However, this has an unintended consequence 
perhaps of potentially breaking QSOs. A few times now I have started calling 
KH1/KH7Z on 20m when I am receiving them around -09 (but with pretty low 
S-meter  signal strength). Usually this is with 1-2 channels running on their 
downlink. If they go to 3 channels I can still receive but it falls to say -15. 
If they bring up channel 4 and 5 I loose them. There just isn’t the link budget 
left to receive them when the power is split between more than 3 channels in 
this example.

 

Now the issue is, if they answer me by adding the 4th channel – I wont hear 
them under those conditions. If I am part way through a QSO I can loose the 
RR73 for the same reason if they answer someone else on the 4th channel– simply 
because the link runs out of steam.

 

Now if I couldn’t hear them in the first place I wouldn’t have tried calling. 
In this case however, they can disappear under load effectively and I loose 
them mid QSO.

 

For future consideration perhaps is to have the setting of number of channels 
vs the number of active channels maintain a constant PER CHANNEL TX power 
rather than the variable situation we have now. Ie I enable my fox station to 
run say 4 channels, but only reply on 1 channel, then the output power should 
be the equivalent of the power that would be in that channel if all 4 were in 
fact on air but aren’t. At least that way I have a constant link budget I am 
working with on my comms channel with the fox station rather than one that can 
have them drastically cut power mid QSO without reference to the conditions on 
the path I am working them via.

 

If what I am describing is not how it is supposed to work already then there is 
another factor at work somewhere in the chain to be explored. I would be happy 
to discuss this further and use the KH1/KH7Z expedition to observe and learn 
more about how the multi-channel nature of the mode works.

 

Regards,

Grant VK5GR

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel 

Re: [wsjt-devel] Audio issue(s) with Win10 April 2018 update

[John Zantek]

Windows updates are always a PITA when comes to audio, often to point of reinstalling 3rd party drivers. Redmond thinks the world is only MP3 tunes.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] tx4 RR73 patch

[John Zantek]

Yay!

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, March 27, 2018 11:54 AM
To: WSJT Software Development 
Cc: Black Michael 
Subject: [wsjt-devel] tx4 RR73 patch

 

Allow user to shift-double-click TX4 to make RR73 last across band changes.

 

https://www.dropbox.com/s/qav6d92gllu9ktc/tx4.patch?dl=1

 

de Mike W9MDB

 

 

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] DXpedition Mode Test Results

[John Zantek]

Magnificent summary.  Bravo!

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Wednesday, March 7, 2018 12:28 PM
To: WSJT software development 
Subject: [wsjt-devel] DXpedition Mode Test Results

Hi all,

Here are a few highlights of results from last night's public test of
FT8 DXpedition Mode:

  - The overwhelming majority of participating Hounds operated as intended,
and according to instructions.  I copied 190 unique Hound callsigns during
the 2300 hour (when I was acting as Fox on 20m) and 330 unique callsigns
during the whole four hours.  I suppose that we had at least 400-500
participants, maybe more.

- Fox's multi-signal capability worked very well at the tested values,
NSlots = 3, 4, and 5.  This feature is surely a "keeper", and I see no
reason not to use NSlots = 5 -- especially if Fox is running power.

  - In the four test hours the number of "QSOs" logged by Foxes on 20, 30,
40, and 80m was 320, 189, 454, and 351.  However, a regrettable program bug
was preventing deletion of Hound callsigns from Fox's "QSO-in-Progress" list
after a QSO had been logged.  As a result, many repeated "RR73" messages
were sent, many dupe QSOs were logged, and the QSO-in-Progress list kept
growing.  As another consequence, some QSOs took up to ~20 min to complete,
and a number of Hounds who had been sent a report never received their
QSO-confirming "RR73".

- AA7A actually worked 120 unique calls in the 40m hour, and the other Foxes
worked comparable slightly lower numbers.  When this program bug is
corrected, hourly QSO in the 300-400 range should certainly be achievable.

- Of course, some Hounds did not operate as intended.  Several kept trying
to raise Fox by calling below 1000 Hz.  (Most of these that I noticed were
from non-English speaking countries.  We will probably need translations of
the FT8 DXpedition Mode User Guide.)  A few would-be Hounds were not
obviously not using v1.9.0-rc2, and were calling Fox "blind" in 1st
sequence.  A few Hounds tried using compound callsigns, which is not
supported -- and which needs to be made more clear in the instructions.

- Nearly everybody noticed the XE1GK calling CQ on the low-end Fox frequency
and working people these.  Please don't be too hard on
Ignacio: he obviously misunderstood what was supposed to be happening, and
how to operate in the test run.  He sent me an abject apology. 
Anyway, his signal helped us to evaluate how well we can cope with QRM and
DQRM.

Two operating hints that should be used as needed, but in general were not:

  - Hounds should manually reset their Tx frequency as needed to evade QRM.

  - Fox may decide to use the randomizing feature to vary his own Tx
frequency.


I list here some relatively minor bugs and other things that came to 
light during the test run:

  - Spurious "Callsign mismatch" warning messages were displayed to the 
Fox operator.

  - Fox's log window should automatically scroll to the bottom.  Or 
maybe it should simply show the most recent ~10 QSOs logged.

  - I'm not sure that Fox's "Max Calls" parameter worked as designed.

  - Sometimes Fox sent RR73 to the same station in more that one slot, 
in the same transmission.

  - The dreaded "Blue Decode" button was seen by some.

  - Hounds sometimes send a spuriously low signal report to Fox, even 
when Fox is loud.

  - If Hound hits "Enter" with the DX Call box empty, a blank message 
can be transmitted.

  - It a random station (not Fox) calls a Hound, it can trigger a Hound 
transmission just as if Fox had called.

  - Previously decoded Hound calls can sometimes reappear in Fox's left 
window, when they should not.


Finally, let me outline a few new features we may decide to implement.

  - At least for debugging, and possibly as an option, offer a display 
window that shows the Fox operator the contents of all active queues.

  - Limit the number of QSOs in progress to no more than NSlots.

  - Option to suppress display of the waterfall timestamp.

  - Have Fox call CQ in one slot at least once every few (1 or 2?) minutes.

  - Should Hound's Tx3 frequency be re-randomized for each repeat try?

I'm sure there is more to be said, but that will do for now.  Depending 
on programming progress and on my own travel schedule, we may schedule 
another public test within a few weeks.

-- 73, Joe, K1JT


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [wsjt-devel] DXpedition Mode Test Numbers

[John Zantek]

Thank you, Bill.  I agree…reaching 120 Qph will put a serious dent in the armor 
of those who argue that the FT8 rate isn’t worth the effort vs SSB or CW.  I 
know there were some DXpedition vets in the foray last night, and I hope it was 
an eye-opener for them.

 

N0AN’s comment exactly echoes my experience during both the 30M and the 40M 
test.  “After I had been "moved" to the lower freq tier by the Fox, it put me 
in a mess of others. So I watched the rx window for a while and when I saw a  
hole develop, I moved my TX there (still in the lower freq tier area where the 
Fox had put me, but in a clearer spot). Immediately on my next transmission, 
the qso finished out.”  Right on, Hasan!

 

I wonder what the learning curve timeline will be for the ever-expanding FT8 
user community who never reads the docs.  Some brave, real Fox in the near 
future (sooner than Baker?) will have their hands full with non-Hounds braying 
after them.  :)

 

Regardless, it was a magnificent test.  Ready for the next one, with 4 
callsigns (mine, XYL, & 2 clubs) in the local arsenal to enhance the loading!

 

73 John KE7B

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, March 7, 2018 10:10 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] DXpedition Mode Test Numbers

 

On 07/03/2018 17:42, John Zantek wrote:

The OTA tests were a hoot, even with the hound-on-hound nonsense and the 
unfortunate DQRM from XE.

 

Did anyone collect and mention the final numbers for the foxes?  I thought N1DG 
said ~190 for 30M, but I sense the total 40M QSO’s may have been quite 
significant, since my screen was REALLY scrolling during AA7A’s hour.

 

73 John KE7B

Hi John,

the total Fox QSO counts mentioned on PJR included many dupes, this is because 
the Fox mode logs a dupe when a repeated confirmation is received from a Hound. 
This would be ok but a defect lead to signoff messages not always being sent 
again by the Fox so the dupe counts were very high. I don't have exact figures 
but something of the order of 1/5 of the maximum possible unique QSOs for the 
number of Tx slots being used by the Fox. With the defect found and fixed so 
that Hounds that have to repeat their confirmation are very likely to get a 
prompt RR73 response, the throughput should increase significantly.

I would expect that with a suitable sized pileup and reasonably good behaviour, 
a slick Fox operator may be able to get quite close to optimal rates i.e. 
 x 120 QSOs per hour. There are a few tools in the Foxes bag for 
pileup management that were not used such as randomized Tx frequencies (helps 
with DQRM), directional calls (needs thought as currently the Fox has to stop 
and call CQ to ask), working weak callers first, working furthest distances 
first, etc..

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] DXpedition Mode Test Numbers

[John Zantek]

The OTA tests were a hoot, even with the hound-on-hound nonsense and the 
unfortunate DQRM from XE.

 

Did anyone collect and mention the final numbers for the foxes?  I thought N1DG 
said ~190 for 30M, but I sense the total 40M QSO’s may have been quite 
significant, since my screen was REALLY scrolling during AA7A’s hour.

 

73 John KE7B

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Diversity Reception

[John Zantek]

But the beauty of diversity reception is that the conditions keep changing,
mid-QSO.  Two instances of WSJT-X would be moot, since the 1st one would
control the session after the QSO starts.

 

I concur with K1JT that it would be a tiny group of users who would benefit
from such a mod.

 

From: David De Coons [mailto:ddeco...@msn.com] 
Sent: Saturday, February 10, 2018 4:37 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Diversity Reception

 

You can run two instances of WSJT-X, each fed with a different DAX channel.
One on Antenna 1 and the other on Antenna 2 (with 6600 & 6700 models only
since they have dual SCUs).

 

You would need to pick the one with stronger signal.


Dave wo2x

 

 

Sent from Mail   for Windows
10

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Diversity Reception

[John Zantek]

Looking through the list archives, I see this topic came up a few years ago
but wasn't answered.

Elecraft (and Flex?) radios enjoy the ability of diversity reception, with
split-phone capability to choose the stronger of the two original signals
from separate antennas.

Can the decoder engine of WSJT-X be modified to harness this, if both the
left and right channels of a stereo signal were fed to it?   What about two,
but separate mono channels?

73 John KE7B


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Why wipe Tx6 message?

[John Zantek]

I will echo Rich’s thought and add to the previous thread of “WSJT on 
DXpedition”.

 

The VK9MA team won’t be on the air from Mellish Reef until early November, but 
equipment will be starting to move in less than a month.  The operators will 
also need time with a publicly-available version in order to establish their 
M.O. and to also publish guidelines on their vk9ma.com web site and at qrz.com.

 

I know that none of this was on the FT8 development team’s original timeline, 
but the exponential growth of this mode’s user community, along with the ARRL’s 
marketing push, has built some pressure.  Just look at the noise about FT8 and 
LOTW for an example.

 

Legacy DXer’s and contesters I know like to make jokes about the JT modes, 
claiming this is a passing fad and will never serve any purpose.   Boy, would I 
love to see them eat their words if/when a DXpedition team can report better 
numbers on JT/FT Q’s than RTTY.

 

73 John KE7B

 

From: Rich - K1HTV [mailto:k1...@comcast.net] 
Sent: Friday, August 11, 2017 8:02 AM
To: WSJT 
Subject: Re: [wsjt-devel] Why wipe Tx6 message?

 

Mike, 

Tnx for responding to this request. Until the modification gets into the 
version downloaded by the masses, this feature won't be able to be used by 
most. I don't believe that this weekend's crew doing the OJ0 (Market Reef) 
DXpedition are building their WSJT-X software and will be using the present RC1 
version.

 

Thanks for the changed code. Hope that it can permanently be implemented in the 
final release for all to use.

 

73,

Rich - K1HTV

--

Message: 1
Date: Fri, 11 Aug 2017 11:13:00 + (UTC)
From: Black Michael  >
To: WSJT software development  >
Subject: Re: [wsjt-devel] Why wipe Tx6 message?
Message-ID: <1301556709.1708692.1502449980...@mail.yahoo.com 
 >
Content-Type: text/plain; charset="utf-8"

Seems to me we just need to fill TX 6 when it's empty and leave it alone after 
that. ?It never changes under normal ops. ?So when you put in your custom CQ it 
never gets touched again.
This simple patch sets TX6 only if it's empty for modes other than JT6 and 
QRA64,
This should get you going for the weekend I think.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT on DXpedition

[John Zantek]

[Prelim: I'm posting this on the Developers reflector instead of the wider
WSJT group since I find this group has a better SNR.  If you feel it needs
the wider distribution of the latter net, please let me know - John/KE7B]

This past weekend, I attended the Pacific NW DX Convention, where the buzz
of JT/FT was tangible.  Mind you, while these folks are very accomplished
hams, as a more "experienced" WSJT operator, I often felt I was visiting
Jurassic Park.  When I mentioned I had worked 240/confirmed 236 on
JT65/JT9/FT8, I was given some creds (most had never tried these modes and
believed our community was tiny and incapable of serious DX work).  The
biggest news for me was the talk about the upcoming DXpedition to Mellish
Reef (VK9MA) and the stated intention to try JT65 and/or FT8 on one of the 5
positions.  Of course, RATE is always the #1 issue with DXpeditioners and
Contesters.  I believe this may be the first great opportunity for WSJT to
succeed for a major DXpedition.   I spent some time talking with the team
leader and others about expectations.  Not surprisingly, we cannot expect
the team to run QSOs conventionally.

Below is the summary of their thoughts.  Again, we can't insist that they
run their Q-exchanges conventionally as WSJT is designed, but they are open
to some moderated feedback.  I promised I would provide their input to the
Developers and get them a summarized response.  

SUMMARY BEGINS (Notes from team to me)

Rate is the number #1 concern as well as a few other issues.  A WSJT
exchange from an expedition perspective is a fast exchange which hams are
typically familiar with, such as CW and or RTTY modes.

Current expedition exchange(s) using CW and/or RTTY normally look like the
following:
VK9MA:  CQ CQ VK9MA {optional UP | DN }
KE7B  replying to VK9MA replies: KE7B 
VK9MA sends:  KE7B 599 
KE7B replies: 599 TU 

at this point the QSO is concluded if VK9MA replies with: 
TU QRZ VK9MA UP 
OR 
continues a bit longer if VK9MA retries/replies with: 
KE7B 599 
if VK9MA didn't receive KE7B initial reply 
at which point KE7B replies with: 
599 TU
and VK9MA sends: TU QRZ VK9MA UP 

JT65/JT9 or FT8 throws us a different curve ball in that:
1.  An FT8 exchange is automated with built in retries. therefore the
exchange is  either successful or not. Therefore we (VK9MA) don't have to
worry about retries, as the exchange will either be successful or not.
2.   JT65/JT9 exchanges can be orchestrated because users have time to
change the exchange.
3.   The users of WSJT application are trained to click on the CQ calling
station. Therefore only the really advanced users know/understand the
concept of calling UP/or DOWN in frequency.  Therefore we can expect almost
all  stations respond to the VK9MA CQ by  clicking on the VK9MA CQ in the
application and effectively responding by TX on the VK9MA  calling
frequency.
4.   WSJT application normally has KE7B initially respond to the exchange
with Grid Square which the DX station doesn't care about. 

Therefore if I would like JT65/JT9/FT8 to follow the normal CW/RTTY
expedition exchange 
1.   An Ideal exchange should follow as close to the following as possible.
VK9MA initially sends: "CQ VK9MA XX87" , note without the UP/DWN
KE7B replies anywhere in the 1-4KHz window: "VK9MA KE7B -01"
VK9MA responds: "KE7B VK9MA R-01" 
At this point the exchange is complete.  If KE7B didn't get the
VK9MA response, then he can then call again with KE7B -01...and VK9MA can
repeat "KE7B R-01". This can be integrated/automated into the WSJT FT8
application. 
VK9MA sends: "TU QRZ VK9MA"
Using this approach will be super efficient and make FT8  the GO TO
digital mode
2.   Using JT65 or JT9 the exchange should be the same, other than the users
will have to manually select the exchange using the "Next" buttons which
might be a challenge to most users. 

END SUMMARY

OK, folks.  This is the Mellish Reef team's intent for 90 days hence.  It's
now your opportunity to tell them what they can reasonably expect, what they
should and should not try, or perhaps consider for future WSJT HF
enhancement.  How Mellish goes may be groundbreaking, since propagation will
be poor, and it is a golden opportunity for WSJT to shine on a
DXer/Contester stage as well as for the newly licensed.  I welcome your
feedback.  I'll assemble and relay your voices to the VK9MA team.

73 John KE7B




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sourceforge Update Error

[John Zantek]

Oh, hallelujah!  Getting to the correct path was the secret!

Thank you, Greg (and Bill, too).

73 John KE7B

-Original Message-
From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Monday, July 10, 2017 11:45 AM
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Sourceforge Update Error

Now ya don't it John, it's busted :-)

You should be able to, from JTSDK-QT: 

cd C:\JTSDK\src\wsjtx
svn cleanup
svn up

or

remove C:\JTSDK\src\wsjtx  then rebuild.

Assuming of course, SF is not actually down.

73's
Greg, KI7MT


-Original Message-
From: John Zantek [mailto:j...@zantek.net]
Sent: Monday, July 10, 2017 12:36 PM
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] Sourceforge Update Error

I was building a new package and, unfortunately, had to interrupt the batch
file.  When I now respond 'y' when asked to Update from SVN Before Building,
I get:

Sourceforge Update Error
Build-wsjtx was unable to update [ wsjtx ] Sourceforge.  The service may be
down or Undergoing maintenance.  Check the following Link for current site
status reports:
http://sourceforge.net/blog/category/sitestatus

There's actually nothing wrong at Sourceforge and I'm assuming I munged
something locally when I interrupted the batch file update from SVN.  Short
of reinstalling the entire JTSDK, is there a QT command or build-wsjtx
argument to overcome this?

TIA, John KE7B



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sourceforge Update Error

[John Zantek]

Not sure if I'm doing that correctly as you've indicated, Bill.  
When I launch QT on my Windoze machine, I get a prompt of
(JTDSK-QT 5.2 ) C:\JTSDK
And not $
Regardless, I entered 'svn cleanup', and it accepted it silently.
Reentering 'build-wsjtx package' or 'build-wsjtx rinstall' still fails with
the same Sourceforge Update Error.

Would the root of the svn working copy source directory be elsewhere than
C:\JTSDK ?

73 John
PS: Haven't complied software since my ANSI C days in college.  Wow, the
tools and scripts have improved!

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, July 10, 2017 11:39 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Sourceforge Update Error

On 10/07/2017 19:36, John Zantek wrote:
> I was building a new package and, unfortunately, had to interrupt the
batch file.  When I now respond 'y' when asked to Update from SVN Before
Building, I get:
>
> Sourceforge Update Error
> Build-wsjtx was unable to update [ wsjtx ] Sourceforge.  The service 
> may be down or Undergoing maintenance.  Check the following Link for 
> current site status reports:
> http://sourceforge.net/blog/category/sitestatus

Hi John,

try

$ svn cleanup

at the root of the svn working copy source directory.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Sourceforge Update Error

[John Zantek]

I was building a new package and, unfortunately, had to interrupt the batch 
file.  When I now respond 'y' when asked to Update from SVN Before Building, I 
get:

Sourceforge Update Error
Build-wsjtx was unable to update [ wsjtx ] 
Sourceforge.  The service may be down or
Undergoing maintenance.  Check the following 
Link for current site status reports:
http://sourceforge.net/blog/category/sitestatus

There's actually nothing wrong at Sourceforge and I'm assuming I munged 
something locally when I interrupted the batch file update from SVN.  Short of 
reinstalling the entire JTSDK, is there a QT command or build-wsjtx argument to 
overcome this?

TIA, John KE7B


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Double entries in Rx list

[John Zantek]

Confirming the fixand the DX window is now opening on the NA west coast.
:-)
John KE7B




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel