Re: [wsjt-devel] FT8 DXpedition Mode

Joe et. Al. Your “how to” write-up is great. Are you ready to tell us some details about how it works internally and how it is different from conventional FT8? Dave / NX6D From: Joe Taylor Sent: Friday, February 2, 2018 09:56 To: wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] Flex Radio 6400/6600 support in WSJT-X needs Hamlib updating

Bill Could it be that you made the change to the integration branch yesterday (Saturday)? When I pulled the sources yesterday (my time) and built the 1.8.0 GAR, I did not get the patch. Dave De Coons and I had a conversation about it, and I tried again today (Sunday, my time) and I got the

Re: [wsjt-devel] Diversity Reception

Flex Radios definitely support diversity reception. The 6600, 6600M and 6700 have the necessary dual receivers. In conventional use, we expect the user to route one signal to one ear (via stereo headphones), and the other signal to the other ear. It would be common for phase and timing diff

Re: [wsjt-devel] Space pad for readability

That would be VERY useful. I hope you can get it into the code. Does it involve changes to JTAlertX? Dave / NX6D From: Black Michael via wsjt-devel Sent: Wednesday, February 28, 2018 9:00:29 AM To: wsjt-devel@lists.sourceforge.net Cc: Black Michael Subject: Re

Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

I’m curious to know what will happen when someone wanders into these tests, without RC2, and tries to send one of the messages not used in these abbreviated sequences. Will those callers be ignored? Dave / NX6D From: Joe Taylor Sent: Sunday, March 4, 201

Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

-- From: Joe Taylor [mailto:j...@princeton.edu] Sent: Monday, March 5, 2018 2:02 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7 On 3/4/2018 8:12 PM, David Fisher NX6D wrote: > I’m curious to know what will happen when someone wander

Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

probably not. That's precisely why we are doing more testing! -- 73, Joe, K1JT On 3/5/2018 3:33 PM, David Fisher wrote: > Jim has made the point I was heading towards. Even when 1.9 is released > publically, there will be plenty of users of older versions and some >

[wsjt-devel] FT8 DXPedition mode test

Do you guys want reports of odd things seen during the DXPedition test today on this list? Dave / NX6D -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.lin

[wsjt-devel] DXPedition test results

Joe and everyone: Thanks for the summary of what worked and didn’t last night. The bug in the RR73 logic explains a lot. Here are a few things I noticed: Apart from our friend in Mexico, who simply made a mistake, I noticed a few other instances of people transmitting on top of the Fox’s tran

Re: [wsjt-devel] Premature use of FT8 DXpedition Mode

It has been said that the current dust-up over the use of the DXP mode is the result, in part, of use of the program before its official release. How is making the release of the feature official going to change anything? If making the release official is a matter of tidying up a few last minu

Re: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: early results

If we have another test, I’d like to see each of the Fox stations with rotatable antennas spend part of their hour pointing to various quadrants of the sky. Granted, some directions are not going to be very productive, but if the antenna was turned 30 degrees every 5 minutes, the Fox would be a

Re: [wsjt-devel] WSJT-X at Dayton Hamvention

I have a set of slides that I presented at Quartzfest on “Getting started with FT8”. I’ll be at Dayton. You’ll have to decide for yourself if I qualify. I have about 1500 FT8 QSOs in the log. Dave Fisher / NX6D From: Joe Taylor Sent: Wednesday, April 2

[wsjt-devel] Transmitting at the wrong time in Hound mode

I worked KH1/KH7Z yesterday on a couple of bands successfully, in Hound mode. But before I was successful, I had the following happen: I set Hound mode, then shut the program down. I restarted it, watched messages go by for a while, then started transmitting my call. After a bit I got a mess

Re: [wsjt-devel] Transmitting at the wrong time in Hound mode

avoid exactly what I wound up doing. Dave / NX6D From: Joe Taylor Sent: Friday, June 29, 2018 7:12:28 PM To: WSJT software development; David Fisher Subject: Re: [wsjt-devel] Transmitting at the wrong time in Hound mode On 6/29/2018 8:26 PM, David Fisher wrote

Re: [wsjt-devel] Observation on Expedition Mode

I would amend this to say that the Hound needs to hear a signal from the Fox first. KH1/KH7Z is seldom calling CQ when things get busy. Lots of people are going to tailgate his transmissions to get into the chase. Dave / NX6D From: Black Michael via wsjt-devel

Re: [wsjt-devel] Observation on Expedition Mode

That ain’t happening at KH1/KH7X. Not on 20M anyway. Dave / NX6D From: Black Michael via wsjt-devel Sent: Saturday, June 30, 2018 8:39:05 AM To: 'WSJT software development' Cc: Black Michael Subject: Re: [wsjt-devel] Observation on Expedition Mode WSJT-X has

Re: [wsjt-devel] Observation on Expedition Mode

One would think that it would be reasonable to at least skim the very ample instructions that have been put out. But no, it is not about to happen. Nope, and there is little you can do to change it. As a person who spends a fraction of his time writing documentation, I can tell you from persona

Re: [wsjt-devel] Observation on Expedition Mode

types of callers to see if the band was open which I doubt. de Mike W9MDB On Sunday, July 1, 2018, 7:52:05 PM CDT, David Fisher wrote: That ain’t happening at KH1/KH7X. Not on 20M anyway. Dave / NX6D From: Black Michael via wsjt-devel Se

Re: [wsjt-devel] Observation on Expedition Mode

/2018 8:56 PM, Jim Brown wrote: > On 7/4/2018 4:40 PM, David Fisher wrote: >> Later when I uploaded to ClugLog, I was reminded that I logged the >> wrong callsign. Easily fixed in ClubLog, but for LOTW, all I could do >> was log the contacts again as KH1/KH7X. > > I also

Re: [wsjt-devel] Contest mode CQVHF

Sometimes stations would call “CQ WW ”. In that case, it was easy to select contest mode and return the call. But in many other cases, the other station would give no hint he was in contest mode until his mangled grid square was received. In those cases I got the pop up that prompted

[wsjt-devel] Dialog box deadlock

I was trying to work an FT8 contact on the Isle of Man on 20M (at ATNO for me) a few minutes ago when the following happened: At the same time that the dialog box came up to log the contact (from JTAlertX), another dialog box came up about the “Should you be in NA Contest Mode”. That box came

Re: [wsjt-devel] Dialog box deadlock

18:28, "Laurie, VK3AMA" <_vk3a...@vkdxer.net> wrote: On 28/07/2018 10:07 AM, David Fisher wrote: I was trying to work an FT8 contact on the Isle of Man on 20M (at ATNO for me) a few minutes ago when the following happened: At the same time that the dialog box came up to log the co

Re: [wsjt-devel] Bug? WSJT-X locks sound card to 44.1k

I’ll point out that Windows 7 only has 18 months of support left. In January 2020, it goes out of support. Dave / NX6D From: Bill Somerville Sent: Sunday, July 29, 2018 12:46:58 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Bug? WSJT-X lock

Re: [wsjt-devel] A strange signal seen on the air

Flex radio users routinely do not use “Fake It” mode, as the TX audio signal never exists in analog form from the point where it created by WSJT-X until the RF signal is synthesized. I’m not aware of any cases of audio harmonics appearing in Flex generated FT8/JT65/JT9 signals. I run with a 4K

Re: [wsjt-devel] A strange signal seen on the air

I am having helped at least one Flex user who was generating noise. You can still trigger the ALC on a Flex radio (or any other SDR) with too much audio for the power setting. de Mike W9MDB On Thursday, August 2, 2018, 2:27:04 AM CDT, David Fisher wrote: Flex radio users routinely do no

Re: [wsjt-devel] LoTW error

Window 10, 1809 File was not found using “where libeay32.dll”. Dave / NX6D From: Bill Somerville Sent: Wednesday, October 17, 2018 8:54:29 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] LoTW error On 17/10/2018 16:51, Chuck Furman wro

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

I’m going to ask the unasked question: Why are we doing this at all? LOTW and EQSL status are provided by JTAlertX, and a simple, easy to use update mechanism is available for that. It seems to me that having LOTW status in WSJT-X is an unnecessary duplication of features, and one that is now

Re: [wsjt-devel] 5 minute mouse timeout

I agree it is time for the developers to explain their reasoning about this change. To my knowledge, they have explained all other changes of this sort that have been made, so the fact they have remained silent on this only leads to speculation on our part. That will end badly. And, in the

Re: [wsjt-devel] WSJT-X Dupe Checking in ARRL RTTY Roundup

When we demonstrate a real FT8 contesting mode, and plenty of operators interested in it, then we can talk to N1MM about providing the needed interface. This is the road we followed in the Flex Radio world, and it worked out very nicely. N1MM now feeds the spot information it gathers to the ra

Re: [wsjt-devel] Version 2.0 rc5

This raises the interesting question: Do you expect to create a 2.0.1 version after the dust settles and small number of bugs appear that need swatting? This would be bug fixes only, not new features. Just wondering about your point of view on this. Dave / NX6D

[wsjt-devel] "New Call", working?

Am I right in thinking that the “new call” color coding is not working? When I enable this option, I never see any calls highlighted this way. Dave / NX6D ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/list

Re: [wsjt-devel] Invalid QSO - Solution

FWIW, Bill, it’s not particularly obvious that there is a horizontal association between the Field Day / RTTY Roundup options and the “Exch” fields. They are pretty far apart horizontally from the options they are associated with. Lots of mistakes will be made in this configuration. Dave /

Re: [wsjt-devel] "New Call", working?

No, I didn’t. Thanks. Dave / NX6D From: Bill Somerville Sent: Saturday, December 1, 2018 4:33:52 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] "New Call", working? On 02/12/2018 00:17, David Fisher wrote: Am I right in thinkin

Re: [wsjt-devel] Feedback: Contest Log and Colors

Greg, and others: As a DXLabs user myself you might be interested in how I ran the contest. I started with empty WSJT logs. I keep all of my day to day FT8 logs in DXKeeper, fed by JTAlertX. For everyday use, the WSJT logs are only useful to resolve errors. In fact, I empty them from time to

Re: [wsjt-devel] Feedback: Contest Log and Colors

, 2018 12:59:58 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Feedback: Contest Log and Colors On 03/12/2018 20:48, David Fisher wrote: > No ADIF, No All.txt, etc. Hi Dave, I strongly recommend hanging on to your ALL.TXT file. Archive it once a year or something if you must bu

Re: [wsjt-devel] Very few decodes during contest

The gold standard for time keeping on Windows is the Meinberg NTP implementation. This program implements a conventional NTP daemon as found in Linux, etc. As far as I know, it responds to the usual NTP configuration settings. It is a well tested, well integrated and well supported program th

Re: [wsjt-devel] FW: [rttydigital] FT8 Roundup Logs Received Page

Do you have a way for an operator to learn his/her score? I have no idea what my score was. I realize you don’t want to publish scores publicly before you make the results official. Is there a scoring tool or something? Dave / NX6D From: Ed Muns Sent:

Re: [wsjt-devel] EOL Date For Ver1.9

I think 1.9.1 is fully deprecated after 10 Dec (next Monday). Dave / NX6D From: Richard Solomon Sent: Monday, December 3, 2018 5:01:51 PM To: wsjt-devel Subject: [wsjt-devel] EOL Date For Ver1.9 I may have missed this, but has a date been set for the end of usin

Re: [wsjt-devel] use of NTP with WSJT-X disrupted by Windows 10 updates

It sounds like you are making a good argument for running Pro rather than Home. I run Pro only. Checking this system, the Windows Time service is disabled and NTP is enabled and running. It makes sense for a Home system to make changes like this in order to keep things running for users who p

[wsjt-devel] DT, exactly what does it mean?

I see “DT” values that range from about 0.0 to about 0.5 in my system. Does this mean that, on average, my system clock is a little slow, or a little fast? I’ve searched the documentation. It explains that the column of numbers show the difference between the signal and the system’s time, but

Re: [wsjt-devel] DT, exactly what does it mean?

2:25:51 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] DT, exactly what does it mean? On 04/12/2018 22:11, David Fisher wrote: I see “DT” values that range from about 0.0 to about 0.5 in my system. Does this mean that, on average, my system clock is a little slow, or a little

[wsjt-devel] Windows 10 Pro time test

Since I apparently put the match to this issue, I’m going to run an experiment. I normally run my Win 10 Pro (homebuilt) computer with the Meinberg NTP service. It has worked extremely well. But, it has also been said that the Windows service may be fine. So, let’s find out. I’ve disabled Me

Re: [wsjt-devel] TX function lost, then have Task Manager problem

I run a FLEX 6600 and I see it too. This problem has been around for a while; it is not due to the WSJT protocol change. Since the transmitter engages we know that the transmit command is getting through the CAT system to the radio. I’m not aware of any evidence of a problem like this occurri

Re: [wsjt-devel] Experimental changes in r8146

Hello everyone You guys haven’t heard from me before – I’m David Fisher, NX6D. I’ve been watching this reflector for a couple of weeks, building and testing the program as the versions roll out. I have hundreds of FT8 QSOs in my log and am close to a multi-band WAS in FT8. I’m also an

Re: [wsjt-devel] Experimental changes in r8146

That would do the job. On the surface it seems inconvenient to reconfigure the program in a case like this. My normal mode of operation jumps around from a mode like I’ve described, to the more conventional “transmit on his frequency”. But, I’ll give it a try. Thanks for listening. 73

[wsjt-devel] Why was the R+05 selected instead of 73?

Attached are a couple of screen shots. One shows a QSO I logged a few minutes ago, the other shows the program options that were in effect at the time. The program version is R8150. KD0ZZ called CQ on 15 meters. I answered and the QSO started up. You’ll see some bouncing back a forth a coup

Re: [wsjt-devel] Why was the R+05 selected instead of 73?

This time, with the images. From: David Fisher Sent: Thursday, October 5, 2017 1:56:29 PM To: WSJT Software Development Subject: Why was the R+05 selected instead of 73? Attached are a couple of screen shots. One shows a QSO I logged a few minutes ago, the

Re: [wsjt-devel] Why was the R+05 selected instead of 73?

want to start a new QSO. -- 73, Joe, K1JT On 10/5/2017 5:55 PM, David Fisher wrote: > This time, with the images. > > -------- > *From:* David Fisher > *Sent:* Thursday, October 5, 2017 1:56:29 PM > *To:* WSJT

Re: [wsjt-devel] Stale Lock

It’s in the “bin” directory along side WSJT-x. Dave / NX6D From: Phil Theis Sent: Wednesday, October 11, 2017 9:08:32 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Stale Lock Where will I find rigctld-wsjtx? Remember, the driver for Flex 6

Re: [wsjt-devel] Stale Lock

I ran your example and found that the code for the Flex radio is 236. I have a TCP port configured for the radio on port 5002. Assuming the IP address is 127.0.0.1, and copying your example, this is what I get. (Does the -v mean “really verbose”?) PS C:\wsjt\wsjtx_d\bin> ./rigctld-wsjtx.ex

Re: [wsjt-devel] Stale Lock

I ran it with the wrong rig number. Should have been 236. Ignore. From: David Fisher Sent: Wednesday, October 11, 2017 10:59:00 PM To: Black Michael; WSJT software development Subject: RE: [wsjt-devel] Stale Lock I ran your example and found that the code for

Re: [wsjt-devel] Stale Lock

Ria I think Tim said that WSJT-X has the problem much more frequently than other programs, but I think he suggested that other programs have it too. Given the popularity of JT, it could be observation bias. DF From: Ria Jairam Sent: Wednesday, October 11, 20

Re: [wsjt-devel] Stale Lock

OK, here’s a test using -m 236 (this time) on my Flex 6500 while it was listening to 21.074. I get a lot of output from the program, then it appears to hang. I waited a few minutes. PS C:\wsjt\wsjtx_d\bin> ./rigctld-wsjtx.exe -m 236 -r 127.0.0.1:5002 -v rigctld, Hamlib 3.2~git Report bugs

[wsjt-devel] My Grid in documentation

I’m proof reading the 1.8 RC 3 document. Here’s something I’ve noticed before that might be helpful. As I understand it (and I’m probably wrong), the “Settings, General, My Grid” field accepts 6 character grid information such as CM97bq (my grid). I discovered this accidentally when I was try

Re: [wsjt-devel] My Grid in documentation

Quite right. Blind, apparently. Sorry for the QRM. From: Joe Taylor Sent: Monday, October 16, 2017 7:06:02 PM To: WSJT software development Subject: Re: [wsjt-devel] My Grid in documentation Hi Dave, On 10/16/2017 7:08 PM, David Fisher wrote: > I’m pr

[wsjt-devel] Seven messages in FT8 QSO

Joe – Here’s something you might want to consider in the documentation. In several places, the documentation describes the conventional 6 message QSO. But in FT8 mode, with Auto Seq on, the QSO is usually 7 messages long. As it says in section 7.3, TX Enable is deactivated at the end of the Q

Re: [wsjt-devel] WSJT 1.8.0 RC3

My concern with all of this is not the change, but how to get the FT8 users to change. Habits have already formed. I’m wondering if we should push harder by inverting the defaults so that a fixed TX frequency is the default, and allowing it to move has to be enabled. In the words of our new L

Re: [wsjt-devel] WSJT 1.8.0 RC3

? I’m sitting here running QSOs one handed, except for moving the red goalpost. All of this is assuming split operation in all QSOs, which I am doing. Dave / NX6D From: David Fisher Sent: Wednesday, October 18, 2017 1:08:09 PM To: WSJT software development

Re: [wsjt-devel] Single handed use of WSJT-X

Or, if one mouse button set the RX frequency, and the other set the TX frequency, each of these steps could be done in a single click. Dave / NX6D From: Saku Sent: Thursday, October 19, 2017 10:51 To: wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] Single handed use of WSJT-X

Saku-san No, they don’t read manuals, or release notes. They do, however, reserve the right to charge right into a new version of software, carefully crafted and tested by a dedicated group of developers and beta users, then complain when it doesn’t turn out to be exactly what they expected it

Re: [wsjt-devel] DXPedition System Clock Sync

The NTP software has a clock mode that will decode an audio stream from WWV and use it as a time source. But, I recall that it takes quite a while for it to sync up and start providing time. All of the various reference clock modes are described here: https://www.eecis.udel.edu/~mills/ntp/html

Re: [wsjt-devel] DXPedition System Clock Sync

Let me propose the following for dealing with a valuable DX whose clock, for whatever reason, is off. In the world of Solar Eclipse Photography, a leading piece of software is Eclipse Orchestrator. When photographing a Total Solar Eclipse, timing is terribly important. Some of the events of

Re: [wsjt-devel] DXPedition System Clock Sync

on's delta-T as your adjusted time value. Again, all of these solutions presuppose that an internal delta-T value is used for framing timing as opposed to the actual wall clock time. > On Nov 12, 2017, at 16:17, David Fisher wrote: > > As I see it WSJT-X could do the same. A knob co