Re: [wsjt-devel] AGC affecting SuperFox decoding #FH

[James Shaver (N2ADV) via wsjt-devel]

This, IMO, is the best answer. I know that humans like one-size-fits-all/blanket answers but, realistically, the only one-size-fits-all answer is: it depends. 73,Jim S. N2ADVOn Sep 28, 2024, at 10:16 AM, Bill Barrett via wsjt-devel  wrote:Perhaps a message to the user:"Consider experimenting with AGC settings for best SF decoding"BillW2PKYOn Sat, Sep 28, 2024 at 10:07 AM 5p1kzx via wsjt-devel  wrote:Hi all Sometimes AGC is usefull and other times AGC off is better. It has to decided by the user and not by the software. So far I haven't had any problems in decoding any SF signals if they  were over -16dB in snr. Condx ain't static It's dynamic so one have to play with AGC/Preamp/Filter/ATT/Notch/Band-Pass to get the best decode. No settings will work every time. One has to take the time to learn what ones radio does with different settings. I spend a lot of times playing with the settings when k8k was operating from American Samoa and that experience came handy when hunting N5J🙂73 de 5p1kzx Sendt fra min Galaxy Oprindelig besked Fra: Christoph Berg via wsjt-devel  Dato: 28.09.2024  14.29  (GMT+01:00) Til: Black Michael , WSJT software development  Cc: Christoph Berg  Emne: Re: [wsjt-devel] AGC affecting SuperFox decoding #FH Re: Black Michael via wsjt-devel> We need to do some testing but I'm considering changing Hamlib to put all rigs on FAST AGC (if AGC is not OFF) for WSJT-X operation.  So a setting of medium or slow would get changed to fast.That sounds like it should be done by wsjtx, not hamlib.73,Christoph DF7CB___wsjt-devel mailing listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___wsjt-devel mailing listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Power level dropping

[James Shaver via wsjt-devel]

Mike, this has been driving me crazy on one of my Win 10 machines for 
some time - Thanks for this!


Jim S.

N2ADV

On 7/26/2024 10:24 AM, Black Michael via wsjt-devel wrote:
If anybody is seeing the power output dropping when transmitting I 
just found somebody having this problem and we solved it.
Is the Sound Control Panel ensure you have "Disable all enhancements" 
checked.  We were able to duplicate this problem when checking and 
unchecking that box (and clicking Apply in between).

Mike W9MDB

Inline image





___
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 SuperFox Verification is flawed

[James Shaver via wsjt-devel]

+1 to Hasan - nobody is forcing anyone to use SF.  You're spending more 
time splitting hairs about this than any useful output and wasting 
everyone's time and bandwidth - the Dev list is becoming less useful as 
a result.


Go ahead and develop your own thing if all you are going to do is point 
out things like this or go use one of the dozens of other digital modes 
(including the ones that exist in the GA version of WSJTX) that already 
exist out there.


Good grief.

On 7/24/2024 7:59 AM, Hasan N0AN via wsjt-devel wrote:

Jonathon,
Then don't use SuperFox
Hasan


On Wed, Jul 24, 2024 at 5:25 AM Jonathan McComb via wsjt-devel 
 wrote:


https://sprocketfox.io/xssfox/2024/07/24/superflawed/

The Superfox mode uses security by obscurity, (which is never a
good thing) by failing to publish any source code for the
dedicated superfox binaries to allow for peer review. It is
exceptionally misguided.

Amateur Radio should be available to everyone to use, without
having software functions/features hidden behind a gatekeeping
organisation (Northern California DX Foundation).  A more cynical
person would surmise that this is a first step to making the
feature a paid one.

Jonathan, GI3JMC


___
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] SuperFox Practice Session

[James Shaver (N2ADV) via wsjt-devel]

Oh no!  Best wishes for a speedy recovery to your wife!

73,
Jim S. 
N2ADV

> On Jul 22, 2024, at 9:24 PM, Joe Taylor via wsjt-devel 
>  wrote:
> 
> I am very sorry to report that I cannot run a SuperFox Practice Session 
> tomorrow, after all.  My wife was hospitalized yesterday with a broken knee, 
> and my priorities will obviously be elsewhere.
> 
>-- Joe, K1JT
> 
>> On 7/21/2024 3:24 PM, Joe Taylor via wsjt-devel wrote:
>> Hi all,
>>> Would it be possible to have a practice session(s) where a SuperFox in NA 
>>> would operate as a test station for modest stations like mine to try their 
>>> SuperFox setups? Something like a practice session often offered for 
>>> contests?
>> I will conduct a SuperFox practice session on Tuesday, July 23, starting at 
>> 1300 UTC.  Look for W2ZQ or K1JT, or possibly both, operating as SuperFox on 
>> 21.091 or 14.091 as conditions allow.  I should have a good signal in EU and 
>> much of NA.  Please make this special effort worthwhile -- and take note 
>> that I have zero experience as a Fox operator. :-)
>>   -- 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Mint 21.3 Virginia

[James Shaver via wsjt-devel]

This may be hit or miss - I upgraded one machine to 21.3 and did a fresh 
install on another machine of 21.3 and both had NTP, however, another 
machine that I upgraded (that was identical to the other machine I 
upgraded) no longer had NTP installed.  Quite odd but definitely 
something to look out for.


Jim S.

N2ADV

On 1/15/24 05:31, Pino Zollo via wsjt-devel wrote:

FYI:

After upgrading to Mint 21.3 no digimode will work any more.

The reason is that NTP in not installed and the time will shift.

The solution is to install NTP again.

73

Pino ZP4KFX



___
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] callsigns in <>

[James Shaver via wsjt-devel]

This is outlined in section 7.5 “non-standard callsigns” - specifically the 
last sentence in that section: “  offers no support for two nonstandard 
callsigns to work each other.”


> On Dec 27, 2023, at 10:43 AM, Bruce Dagel via wsjt-devel 
>  wrote:
> 
> WSJT-X version 2.6.1
> 
> My mistake, I was going from memory.
> The actual problem comes with a longer call.  WB0GAG/1  R+11 
> transmits as WB0GAG 
> 
> 73,
> Bruce, WB0GAG
> 
> 
> ___
> 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 73 allowed after RR73?

[James Shaver (N2ADV) via wsjt-devel]

Agree 100%. The number of ops who refuse to be control operators and just log and move on because, “the software didn’t tell me the QSO is complete” is staggering.On Oct 22, 2023, at 1:06 AM, Ed W0YK via wsjt-devel  wrote:+173,Ed W0YK Original message From: Ron WV4P via wsjt-devel  Date: 10/21/23  13:02  (GMT-08:00) To: WSJT software development  Cc: Ron WV4P  Subject: Re: [wsjt-devel] No 73 allowed after RR73? I wish this was THE way, the useless final 73 should have never existed and is the bain of the mode.  Ron, WV4P On Sat, Oct 21, 2023 at 2:55 PM Andy Durbin via wsjt-devel  wrote:






WSJT-X ver 2.6.1, Win 8.1.




I have observed several times that I could not complete a QSO by sending 73 after I had received an RR73.  This is expected operation with F/H active but not when F/H is not active.  I suspect that something is latched in software if F/H mode has been used
 but is then exited and WSJT-X is not re-started.




Has anyone else seen this or have an explanation?




73,

Andy, k3wyc


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

___wsjt-devel mailing listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X close the QSO unilaterally (?)

[James Shaver (N2ADV) via wsjt-devel]

I am not sure I understand this statement: 
“Hams have to do what the software dictates in it's design to get a qso logged. 
”

The software doesn’t determine what gets logged, the control operator makes 
that call. 

Don’t mistake the convenience feature of the logging box popping up for a 
replacement for the control operator’s requirements. 

Jim S. 
N2ADV

> On Jul 15, 2022, at 10:11 AM, Neil Zampella via wsjt-devel 
>  wrote:
> 
> Hams have to do what the software dictates in it's design to get a qso logged.



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

Re: [wsjt-devel] Bill Somerville, G4WJS, SK

[James Shaver (N2ADV) via wsjt-devel]

I had the pleasure of taking to Bill over Skype a few times during the 
development of 1.7 and later 1.8 to chase down some CAT control gremlins with 
several radios I happen to own. His patience and intelligence was incredible. 
Such a huge loss to us all. 

My sincerest condolences to his family and friends. 

He will definitely be missed but his contributions to the advancement of 
amateur radio will live on indefinitely. 

73,

Jim S. 
N2ADV

> On Dec 4, 2021, at 4:27 PM, Joe Taylor via wsjt-devel 
>  wrote:
> 
> I am very sorry to convey the sad news that Bill Somerville, G4WJS, died 
> suddenly and unexpectedly a few days ago.  He was only about 65 years old.
> 
> Bill was a dear friend and very close colleague, though (as is often the case 
> with worldwide ham radio friendships) we had met in person only a few times.  
> In 2013 he was the first to join me in forming a core development group for 
> WSJT-X, which at that time was at program version 0.99.  Bill has been 
> closely involved with WSJT-X and related software projects ever since.
> 
> Our free, open-source software could not have achieved its extensive 
> worldwide popularity and influence in ham radio without Bill's essential 
> contributions.  In addition to writing code for important portions of the 
> Qt-based user interface for WSJT-X, Bill helped to bring the overall program 
> structure more nearly up to professional standards.  Moreover, he devoted 
> countless hours to program support, patiently answering user's questions on 
> WSJT-related forums.
> 
> I have only started to think about the many ways in which I will miss Bill -- 
> not no mention how we all will miss his immense and positive impact on WSJT-X 
> and related projects.  For more than eight years Bill and I communicated 
> closely and regularly on ham radio topics, sometimes many times per day.  
> Perhaps I will be able to write more about it in the near future.
> 
> Rest in peace, dear friend G4WJS.
> 
>-- 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

Re: [wsjt-devel] FT8 issues

[James Shaver (N2ADV) via wsjt-devel]

Double click the TX4 button as noted in the manual. 

> On Oct 27, 2021, at 2:32 PM, Greg Sieckman via wsjt-devel 
>  wrote:
> 
> 
> Hi,
> I upped the software not too long ago to 2.4 & have now gone to 2.5.1. 
> Running win 10.
>  
> I suddenly have the sequence of transmissions going from my RRR to CQ. I have 
> to manually back track to send the 73. It was functioning ok before updates: 
> but also, at that time I had the RR73 represented there vs the RRR.  
> Thoughts?
>  
> I’d like to have the RR73 instead of the RRR.  I have tried to type it early 
> in the qso, but it won’t take it at that point, defaults back to RRR
>  
>  
> Thanks,& 73 Greg wa9tba
>  
> ___
> 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] Feature Request: Hound Mode

[James Shaver (N2ADV) via wsjt-devel]

“ Neil and James don't believe a clear frequency matters based on past 
conversations I have had with them.”

Not sure where in fantasy land you had these conversations but the dev list 
isn’t the place to float personal issues. 



> On Oct 11, 2021, at 12:22 AM, Grant Willis via wsjt-devel 
>  wrote:
> 
> Neil and James don't believe a clear frequency matters based on past 
> conversations I have had with them.



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

Re: [wsjt-devel] Feature Request: Hound Mode

[James Shaver (N2ADV) via wsjt-devel]

The check box used to be on the main screen of the UI and people kept checking 
it by mistake and causing all sorts of issues and questions so it was moved to 
the menu and those questions and issues ceased to be replaced by a less 
frequent request to put it back where it was. The needs of the many and all 
that…

> On Oct 10, 2021, at 10:14 PM, Neil Zampella via wsjt-devel 
>  wrote:
> 
> 
> Grant,
> 
> as F/H specifically requires you to reply to a Fox CQ above 1000 hz, and 
> since the decoder decodes the entire passband based on the base frequency 
> set, you would not need any 'waterfall history' to determine where to Tx your 
> reply.
> 
> Maybe I'm missing the point.
> 
> That said, my reply was specifically to Dennis who was saying he would forget 
> to switch back to normal FT8 mode after using one of the 'special' modes.
> 
> Neil, KN3ILZ
> 
> On 10/10/2021 8:49 PM, Grant Willis wrote:
>> Neil,
>> 
>> I wish to take a moment please to outline what I see is the problem with the 
>> configuration options as a solution that everyone keeps answering with when 
>> this comes up. I dont think the case why the configuration mode changes 
>> annoy many has ever been clearly articulated.
>> 
>> If I am tuning around the band and see some FT8, dial my receiver onto it 
>> and see what is happening. If I see they are running in F/H mode - then if I 
>> use configurations to change to that mode,  I need to often a) add a 
>> frequency to the config, b) reselect the frequency I was just on and c) 
>> loose the waterfall history I would want to use to pick where to drop my 
>> transmitter to start calling.
>> 
>> In quick fire DX Chasing that is all lost time and multiplication of effort 
>> that to be frank is a PITA.
>> 
>> The reason people keep asking for a button to switch to hound mode and back 
>> on the main screen is so they can do what people should more naturally be 
>> doing - that is spin the dial of their radio, look at what's on the band, 
>> and then pick the right mode to work what they hear quickly and efficiently. 
>> Sure the work arounds work - but they are clunky and kludgy to a DX operator.
>> 
>> The alternative solutions might be - preserve the 
>> frequency/band/sub-frequency settings across a configuration settings change 
>> and get the waterfall not to be reset when you swap configurations. I 
>> believe that would be much more work for the programming team than having a 
>> simple tick switch linked to hound mode on / off on the main page. Having 
>> said that, the developers have made it clear they are not interested - so 
>> yes it is also a lost cause.
>> 
>> Oh and to those that say "grab the source and roll your own" - not everyone 
>> can or has the time to write software and roll their own. 
>> 
>> Regards,
>> Grant VK5GR
>> 
>> 
>> 
>> 
>> 
>> On Mon, Oct 11, 2021 at 11:55 AM Neil Zampella via wsjt-devel 
>>  wrote:
>>> In your case I would suggest create a separate CONFIGURATION for each mode 
>>> you're using.You can setup one for regular use, then one for other 
>>> special modes such as the NA VHF contest, Field Day, Fox & Hound, etc. 
>>> 
>>> All you need to do is switch over to the mode you're going to use by 
>>> selecting the configuration. 
>>> 
>>> I've been using this feature since it was first created.
>>> 
>>> Neil, KN3ILZ
>>> 
>>> On 10/10/2021 6:12 PM, Dennis Younker NE6I wrote:
 Put me down for also wishing to have that on the main screen. Or more 
 accurately in my case, having a check box or link on the main screen that 
 is linked to Special Operating Activity. Yes, handy to quickly go to and 
 from F/H mode but also convenient at the start and end of one of the 
 contests listed on the Advanced tab. I have, for example, operated an NA 
 VHF Contest over a weekend and then forgot to uncheck the box after the 
 contest. And then been bitten for a moment later in the week when 
 operating normal FT8 or MSK.
 
  
 
 I am not a programmer and not interested in becoming one (again). It’s 
 great that the source code is available for anyone to modify to their 
 heart’s content but I’m not interested in doing that. I did a lot of 
 programming and compiling of code several decades ago, and spent MANY an 
 all nighter doing that. That ship has now sailed for me, and I’m not 
 interested in getting on board again.
 
  
 
 I am hugely appreciative of K1JT and the entire WSJT-X team for their 
 work. I for one know how much time and effort goes into this. It’s truly a 
 labor of love.
 
  
 
 --Dennis NE6I
 
  
 
 From: Jeff Stillinger via wsjt-devel  
 Sent: Sunday, October 10, 2021 9:53 AM
 To: WSJT software development 
 Cc: Jeff Stillinger 
 Subject: Re: [wsjt-devel] Feature Request: Hound Mode
 
  
 
 Not exactly a secret.  For building on Microsoft virus, the sdk is located 
 here: 
 
>>

Re: [wsjt-devel] Fork for SSB ??

[James Shaver via wsjt-devel]

Are you all thinking something similar to how RDS works with broadcast signals 
or are you thinking something more robust due to the weak signal 
characteristics of FT8?  I can definitely think of some applications for 
disabled ops to allow them to augment other appliances helping them on the air. 

Jim S. 
N2ADV

> On Sep 23, 2021, at 2:18 PM, Glenn M-H via wsjt-devel 
>  wrote:
> 
> Maybe a sound processing system can analyze the sound signal and place the 
> FT8 signal between the lowest human harmonic frequencies greater than 300Hz.
> 
> After a compressor/clipper a bandwidth (50-100Hz?) with some center frequency 
> automatically chosen above, should be notched out - and the FT8 signal 
> inserted here. The FT8 signal must be inserted, after the non-linear 
> compressor/clipper, so the FT8 signal is not subjected to non-linearity.
> 
> OZ1HFT
> 
> -
> 
>> Den 23. sep. 2021 kl. 19.27 skrev Philip Gladstone 
>> :
>> 
>> I think that it would be an interesting experiment to transmit voice on SSB 
>> with a continuous FT8 transmission (maybe at around the 1kHz offset) and see 
>> whether there is a combination of offset & volume difference that makes the 
>> FT8 decodable if the SSB is barely understandable or better, and yet have 
>> the FT8 transmission be essentially inaudible.
>> 
>> I'd like the FT8 transmission to just send the sender's callsign and locator 
>> and not much else. This could be entirely automated by the 
>> radio/microphone/speech processor/whatever. 
>> 
>> Philip
>> 
> 
> 
> 
> 
> ___
> 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 Program hung and not responding

[James Shaver (N2ADV)]

To put Gary’s response another way: Imagine you’re taking to someone standing 
on front of you and, mid-conversation, the person to whom you’re speaking 
suddenly disappears without a trace. I think you’d throw an error code, too. :)

Jim S. 
N2ADV

> On May 3, 2021, at 12:32 AM, Gary McDuffie  wrote:
> 
> 
> 
>> On May 2, 2021, at 8:28 PM, Bill Frantz  wrote:
>> 
>> I had been operating FT8 on 15M and 40M. I powered down my K3 (upgraded with 
>> the internal sound card) and got the "Rig Control Error" message.
> 
> This is normal for every computer I’ve had.  That’s the error message when 
> the port goes away (by powering down the K3).  Sounds normal.  It can’t 
> communicate with the rig when it is shut down so it gives you an error.  I 
> always shut down the program before unplugging the USB cable to the radio.  
> It runs across my desk for easy access in case of T-Storm.  The program still 
> closes when I tell it to ignore, but works fine when I plug the USB cable 
> back in and reload the program.  You should be fine as soon as you turn the 
> radio back on and restart the program.  Just don’t shut the rig down without 
> unloading WSJT-X.
> 
> Gary - - AG0N
> ___
> 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] External OM feature request for UI main window.

[James Shaver (N2ADV)]

It used to be on the main page but people kept checking the box by accident and 
complaining about the program not working correctly so it was placed in the 
settings. 

As Bobby notes, just create a DXPedition Mode configuration and it will make 
switching simple. 

Jim S. 
N2ADV 

> On Mar 25, 2021, at 3:31 PM, Bobby Chandler  wrote:
> 
> Mario,
> 
> Just have him set up a configuration for F/H.
> 
> Bobby/N4AU
> 
>> On 3/25/2021 1:32 PM, Marco Calistri wrote:
>> Hello dev's team,
>> 
>> I received an UI feature request by an old friend of mine: I5MXX, Marzio who 
>> is asking if possible to have the F/H switches on the main window of WSJT-X, 
>> instead to have it inside the Settings/Advanced window.
>> 
>> I'm just doing a sort of "POSTMAN" service :-)...
>> 
>> Thanks for your kind attention.
>> 
>> Best regards,
>> ---
>> *73 de Marco, PY1ZRJ (former IK5BCU)*
>> **
>> 
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> -- 
> n...@outlook.com
>  n...@arrl.net
> 
> 
> 
> ___
> 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] Question about QRZ Integration

[James Shaver (N2ADV)]

The developers have always carefully weighed what has been asked vs what the 
positive or negative impacts would be.  Just because you don’t like the 
responses does not automatically make it QRM.  Feel free to ignore whatever you 
do not like but as many of us happily work on testing and providing feedback to 
the developers, the responses of those same users are indeed relevant.  

Have a nice day and happy DX’ing.  

73,

Jim S. 
N2ADV

> On Dec 3, 2020, at 4:48 PM, Hasan N0AN  wrote:
> 
> 
> It is not qrm'ing the list to take issue with a proposed developmental issue 
> that may negatively impact the program. If implemented, it will impact ALL of 
> us, not just you. If that impact is deleterious, we suffer for your so-called 
> enhancement, so we have every right to voice our opinions and recommendations 
> to the developers. ...and you have every right to ignore or dispute our 
> assertions. 
> 
> ...and the developers can decide what best suits their intentions, after due 
> consideration of your requests, and our feedback. (Both of which are 
> appropriate on this list)
> 73, N0AN
> Hasan
> 
> 
>> On Thu, Dec 3, 2020 at 3:32 PM Dave Slotter, W3DJS  
>> wrote:
>> Just curious -- how many of the people responding to my original message -- 
>> directed at Bill and Joe -- are actually going to be coding anything? Not to 
>> be an ass here, but this was not an open invitation to send QRM to the 
>> mailing list.
>> 
>> If you have code to contribute, great, otherwise, please stop the QRM about 
>> irrelevant stuff.
>> 
>> I am working on a solution for a particular use case. If this doesn't work 
>> for you, that's totally ok. It will work for me and quite a few other people.
>> 
>> --
>> Dave Slotter, W3DJS
>> 
>> 
>>> On Thu, Dec 3, 2020 at 4:25 PM Hasan N0AN  wrote:
>>> Please do not ask the developers to turn WSJT-X into Bloatware. Focus on 
>>> the core functions and let 3rd party apps do the rest. They are out there. 
>>> The interface to them already exists. Don't recreate the wheel and 
>>> negatively impact the decoding of weak signals by trying to make WSJT-X 
>>> into a Swiss Army Knife.
>>> 73, N0AN
>>> Hasan
>>> 
>>> 
>>>> On Thu, Dec 3, 2020 at 2:11 PM Adam Bartlett  wrote:
>>>> I want to agree with Jim N2ADV here - WSJT-X is a great application for 
>>>> weak signal work.  ACLog/Log4OM/RUMLog are great loggers that will tie to 
>>>> QRZ/HamQTH/a database of US Hams from the FCC's dump/etc, and two of the 
>>>> three are free (plus CQRLog and other tools).  In information systems 
>>>> we're moving away from monolithic services/software toward microservice 
>>>> architectures - I see WSJT-X as a weak signal microservice that talks to 
>>>> my logging microservice that might also talk to FLDigi or a SSTV tool.
>>>> 
>>>> 73,
>>>> Adam Bartlett
>>>> N5YHF
>>>> 
>>>>> On Thu, Dec 3, 2020 at 1:38 PM James Shaver (N2ADV) 
>>>>>  wrote:
>>>>> So many users have so many different tastes that the UI really should be 
>>>>> dedicated to decoding functions vs what are “quality of life” functions.  
>>>>> If you try to sharpen a hammer to make it a knife, you’ll have a mediocre 
>>>>> knife and a terrible hammer. 
>>>>> 
>>>>> Just my 2 cents... 
>>>>> 
>>>>> 73,
>>>>> 
>>>>> Jim S. 
>>>>> N2ADV
>>>>> 
>>>>>>> On Dec 3, 2020, at 2:27 PM, Neil Zampella  wrote:
>>>>>>> 
>>>>>> 
>>>>>> There are many for Windows, and I'm fairly sure that Gridtracker does a 
>>>>>> lookup also, and its available for Linux.  
>>>>>> As far as modifying the wsjtx_log file, why?Again, you're adding 
>>>>>> complexity to the program that is not really needed, and would add to 
>>>>>> the support issues seen here.
>>>>>> 
>>>>>> Neil, KN3ILZ
>>>>>> 
>>>>>> On 12/3/2020 11:37 AM, Dave Slotter, W3DJS wrote:
>>>>>>> You said, "there are plenty of third-party bridge, programs that do 
>>>>>>> this as do many logging programs"
>>>>>>> 
>>>>>>> Please support your statement with specific examples

Re: [wsjt-devel] Question about QRZ Integration

[James Shaver (N2ADV)]

So many users have so many different tastes that the UI really should be 
dedicated to decoding functions vs what are “quality of life” functions.  If 
you try to sharpen a hammer to make it a knife, you’ll have a mediocre knife 
and a terrible hammer. 

Just my 2 cents... 

73,

Jim S. 
N2ADV

> On Dec 3, 2020, at 2:27 PM, Neil Zampella  wrote:
> 
> 
> There are many for Windows, and I'm fairly sure that Gridtracker does a 
> lookup also, and its available for Linux.  
> As far as modifying the wsjtx_log file, why?Again, you're adding 
> complexity to the program that is not really needed, and would add to the 
> support issues seen here.
> 
> Neil, KN3ILZ
> 
> On 12/3/2020 11:37 AM, Dave Slotter, W3DJS wrote:
>> You said, "there are plenty of third-party bridge, programs that do this as 
>> do many logging programs"
>> 
>> Please support your statement with specific examples.
>> 
>> I would like to know which of these run under Linux and directly modify the 
>> file "wsjtx_log.adi" file.
>> 
>> Thank you. Regards
>> 
>> --
>> Dave Slotter, W3DJS
>> 
>> 
>> On Thu, Dec 3, 2020 at 11:29 AM Neil Zampella  wrote:
>>> FWIW ... there are plenty of third-party bridge, programs that do this
>>> as do many logging programs.  Adding something that requires Internet
>>> access both ways, rather than the PSK Reporter's feed only, may cause
>>> other issues, as well as add on to the support issues often seen here.
>>> 
>>> Neil, KN3ILZ
>>> 
>>> On 12/3/2020 8:38 AM, John Nelson wrote:
>>> > Dave,
>>> >
>>> > Scheme to populate name field in log:   good idea but —  you suggest 
>>> > “full names” where it seems to me “first name” would be sufficient and 
>>> > appropriate.  Comment?
>>> >
>>> > — John G4KLA
>>> 
>>> 
>>> ___
>>> 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] FST4/W

[James Shaver]

“Code-parrots” is totally being added to my lexicon going forward lol 


73,
N2ADV

> On Aug 27, 2020, at 11:36 AM, Fons Adriaensen  wrote:
> 
> On Thu, Aug 27, 2020 at 12:01:53PM +0100, Bill Somerville wrote:
> 
>> you are ignoring those that would take the unfinished work in progress,
>> despite protocols not being finalized, and copy the code parrot fashion into
>> their so-called derivative products, which they then release as "complete"
>> before the original authors have even made a public release. All this
>> despite being politely asked not to do just that until the protocols are
>> fixed.
> 
> That is indeed a problem with most open source software, it has hit me
> as well as developer of audio-related applications.
> 
> But IIRC the OP asked for a description of the protocols, i.e. a design
> document, not for ready-to-use code. Surely such documentation does exist,
> and I doubt very much it would help the code-parrots who probably don't
> even understand the basics.
> 
> Ciao,
> 
> -- 
> FA
> 
> 
> 
> ___
> 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

[James Shaver (N2ADV)]

For what it’s worth, I’ve used both the TS2000 and the Flex6xxx options and 
have had zero issues with my 6300 using SmartSDR’s latest version.  

73,

Jim S. 
N2ADV

> On May 24, 2020, at 8:45 PM, Bill Somerville  wrote:
> 
> 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] Callsign lockout

[James Shaver]

Same - I figure the automation functions are an operator aid, not an operator 
replacement. 

Jim S. 
N2ADV

> On Dec 2, 2019, at 4:37 PM, David Gilbert  wrote:
> 
> 
> I have the same opinion.  I almost never use "Call 1st" and I find it trivial 
> to operate without it no matter how many callers I get.
> 
> Even FT8 should be able to handle some degree of operator proficiency.
> 
> 73,
> Dave AB7E
> 
> 
> 
>> On 12/2/2019 1:00 PM, Jim Brown wrote:
>>> On 12/2/2019 2:54 AM, Martin Davies G0HDB wrote:
>>> In summary, I don't see any need whatsoever for any modification of the 
>>> 'Call 1st' capability
>>> to include any forms of queuing or callsign lockout
>> 
>> Agreed. This is an operator issue, not a software one.
>> 
>> 73, Jim K9YC
>> 
> 
> 
> 
> ___
> 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] Illegal auto mode?

[James Shaver]

These discussions are making the Dev list almost unusable; there’s way more 
noise than signal, here. 

This appears to be more of a philosophical debate maybe more suited to the 
WSJTGroup list instead... each one of these messages produces an email to a 
massive audience who then has to wade through the chaff to get the wheat so to 
speak... either way, it’s painful to watch the back and forth on the Dev list. 

For what it’s worth, it has already been stated here that it has never been 
intended that WSJTX be an “automatic QSO machine” and that puts the topic to 
rest in this forum at least for me. 

Jim S. 
N2ADV

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

Re: [wsjt-devel] Contest confusion

[James Shaver]

Well, the people who went off-reservation and decided to take outside steps to 
make it fully automated despite it being said over and over that making an 
“automated QSO machine” was never the intention certainly did not help that 
cause. I know more than one disabled ham who has been able to play in contests 
for the first time in decades because of FT8 and they’ll be the ones getting 
hurt in the end. And before this becomes a back and forth, I’ll head some of it 
off by saying that making “separate categories” is not acceptable. 

> On Jul 24, 2019, at 7:45 PM, "rjai...@gmail.com"  wrote:
> 
> From all indications they're out with the torches and pitchforks to
> ban FT8 from "serious" contesting anyway. So you won't have to put up
> with this for too long.
> 
> I really don't get it... FT8 has brought many more out to play radio
> on a contest weekend (and other times). Maybe some people just love
> hearing dead air.
> 
> Ria
> N2RJ
> 
>> On Wed, 24 Jul 2019 at 19:16, John Kludt  wrote:
>> 
>> Folks,
>> 
>> I just work'em.  Most don't seem to mind.  I have an exchange of calls and 
>> grids.  Yes, I suppose if for some reason somebody not in the contest where 
>> to decide to send in a log and they hadn't logged me because they didn't get 
>> a signal report - why would they send in a log as they are not in the 
>> contest - I could get dinged.  In this weekends contest I did not have a 
>> single person persist in sending R-xx.  They just seemed to move on, too.  
>> If they didn't, I did and let it go.
>> 
>> The real answer is to move to FT4.  From the ground up, a contest mode.  
>> Using 6 as an example let the non-contesters have FT8 and 50.313 and move 
>> the contesters to FT4 and 50.318.  If you can run FT8 you can run FT4.  The 
>> upgrade is a no-brainer.  And FT4 is really, really fast and you have to pay 
>> attention - actually very cool!
>> 
>> How much more kvetching we going to have about this?  It's a  hobby.
>> 
>> John
>> 
>>> On Wed, Jul 24, 2019 at 6:34 PM Bill Frantz  wrote:
>>> 
 On 7/22/19 at 4:03 PM, _vk3a...@vkdxer.net (Laurie, VK3AMA) wrote:
 
> On 22/07/2019 7:16 am, Jim Brown wrote:
> so I quickly switched out of contest mode to work him. :)
> 
> What I WOULD like is to able to do this without going to
> Settings Advanced. All those clicks loses a TX cycle.
> 
> 73, Jim K9YC
 
 Simple and only requires a single mouse click. Setup two
 configurations in WSJT-X, one for you desired contest and the
 other non-contest. Once setup, it is a single click using the
 "Configuration" menu to switch between contest and non-contest.
 
 de Laurie VK3AMA
>>> 
>>> I'm sorry to disagree Laurie. On my Mac (10.14.6 with wsjt-x
>>> v2.1.0 24fcd1), when I switch between my F&H configuration and
>>> my plain QSO one, I lose all my waterfall history, and my two
>>> windows become top left justified on top of each other. They
>>> also return to their default sizes. There's a big cost to get
>>> things back to a workable configuration and refill the
>>> waterfall. It may just be better to pay the mouse clicks to go
>>> to the Advanced menu.
>>> 
>>> Does anyone else see this behavior?
>>> 
>>> 73 Bill AE6JV
>>> 
>>> ---
>>> Bill Frantz| When an old person dies, a   | Periwinkle
>>> (408)356-8506  | library burns. - Joe McGawon | 16345
>>> Englewood Ave
>>> www.pwpconsult.com | Irish Ethnographer   | Los Gatos,
>>> CA 95032
>>> 
>>> 
>>> 
>>> ___
>>> 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


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

Re: [wsjt-devel] Please remove me from your mailing list.

[James Shaver]

You need to click on the link at the bottom of every email from this list to 
unsubscribe. 

73,

Jim S. 
N2ADV

> On Jun 25, 2019, at 1:58 PM, James Buffington  wrote:
> 
> j...@jimbuffington.com 
> ___
> 
> IN GOD WE TRUST
> 
> "The Ultimate in Website Design for Exceptional Clients"
> 
> Thorns may hurt you, men desert you, sunlight turn to fog; but you're never 
> friendless ever, if you have a dog. - Douglas Malloch
> 
> 662-813-3145
> j...@jimbuffington.com
> 
> CONFIDENTIALITY DISCLAIMER 
> This email (including attachments) is confidential information protected by 
> the Electronic Communications Privacy Act 18 U.S.C. §2510-2521 and any other 
> applicable law, and may not be opened or forwarded without consent of the 
> named recipient(s). It is intended only for the use of the individual or 
> entity named herein. If the reader of this message is not the intended 
> recipient, or the employee or agent responsible to deliver it to the intended 
> recipient, you are hereby notified that any retention, dissemination, 
> distribution or copying of this communication is strictly prohibited. If you 
> have received this communication in error, please immediately notify us by 
> return email. Thank you.
> ___
> 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] FT8 decoding sensitivity: WSJT-X vs. JTDX

[James Shaver]

.wav files are pretty big and it may cause issues for people with limited 
bandwidth internet connections who participate via email.  Perhaps host the 
.wav files via a third party site like SoundCloud, DropBox, or the like?

73,

Jim S. 
N2ADV (ex KD2BIP)

> On May 2, 2019, at 4:27 PM, Topher Petty  wrote:
> 
> I tried to post wav files and a screenshot to back up my observations, but 
> the message was rejected by the moderator.
> I do hope someone will look at the files, and they didn't just get lost to 
> the aether. I'd hate to think the information I attempted to provide would go 
> unused.
> 
> 
>> On Thu, May 2, 2019 at 1:12 PM Rebecca Milligan 
>>  wrote:
>> Hi, is it possible that the clock is off on the pc generating those signals 
>> by enough to cause this same issue?  The example sent earlier showed a .8 
>> second difference.  When it takes several times for my pc to decode a strong 
>> signal, it is usually due to their clock being off or two signals on top of 
>> each other. 
>> 
>>  
>> 
>> From: Topher Petty [mailto:ai8...@gmail.com] 
>> Sent: Thursday, May 2, 2019 12:53 PM
>> To: WSJT software development
>> Subject: Re: [wsjt-devel] FT8 decoding sensitivity: WSJT-X vs. JTDX
>> 
>>  
>> 
>> I've noted situations similar to this.. though I'm not running JTDX. There 
>> have been multiple times where a reply was strongly visible in the 
>> waterfall, yet nothing was decoded on that AF, and it took another TX/RX 
>> cycle to get the reply to decode a message.
>> At first, I thought it was because I was operating on an RPI (Pi 3B), so I 
>> copied the configs over to my T410 (twin Xeon X5670s with 64G RAM), and the 
>> same behavior occurs. even at less than 10% CPU utilization.
>> 
>> I don't believe it's available processor power, or RAM availability. With 
>> only WSJT-X, TQSL, and Chrome (six tabs open) running, the T410 has more 
>> than enough processor (24 threads) to handle these decodes, yet they're not 
>> being decoded.
>> 
>> I'm not judging, here. I'm only bringing information to the discussion.
>> 
>>  
>> 
>> 73 de AI8W, Chris
>> 
>>  
>> 
>> On Thu, May 2, 2019 at 11:09 AM Bill Somerville  
>> wrote:
>> 
>> On 02/05/2019 15:56, Black Michael via wsjt-devel wrote:
>> > Well yeahbut I would assume somebody would want to look at a 
>> > signal that seems to have sufficient SNR to decode.  Not enough info 
>> > in his snapshot to tell where JTDX decoded it or what else may have 
>> > happened.
>> >
>> > Seems to me a worthwhile exercise to ensure something pathological 
>> > isn't going on...all the reports of "loops" could just be overlaps, 
>> > fading, whateverbut worth a check isn't it to determine cause of a 
>> > few examples?
>> >
>> > de Mike W9MDB
>> >
>> >
>> Hi Mike,
>> 
>> absolutely agree, but I just wanted to make it clear to all that that 
>> signal strength is not the only parameter that determines successful 
>> decodes.
>> 
>> With respect to apparent anomalies, yes .WAV files are indeed valuable 
>> when linked to specific issues. For example your files provided 
>> Yesterday have highlighted a potential issue with transmissions of 
>> changed messages with respect to how quickly WSJT-X currently starts 
>> rendering the new message in the audio stream. This is something that is 
>> particularly critical with FT4 due to the transmission duration and 
>> thinking time approaching the limits of operator mental and manual agility.
>> 
>> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Might be off topic...

[James Shaver]

Probably more a question for the WSJTGroup list rather than the Dev list - for 
what it’s worth, there are dozens of threads on this topic there already that 
are searchable.  :)

73,

Jim S. 
N2ADV

> On May 2, 2019, at 9:40 AM, Topher Petty  wrote:
> 
> I'm simply curious about one thing...
> 
> What TX power levels does everyone run while working FT-8?
> 
> I don't own an amplifier, and generally run at around 50W output on an 
> IC-718. I know I *CAN* push it to 100W (50% duty cycle) but I like to leave 
> some "headroom" to keep the radio cool while working digital modes.
> 
> I do this by setting the rig's TX power to maximum ("H"), and only pushing 
> the audio until I hit around 50 Watts.
> 
> What power levels are considered "acceptable" for FT-8, and what are 
> considered best-practices for limiting power output?
> 
> Thanks in advance for any insight.
> 
> 73 de AI8W, Chris
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

Re: [wsjt-devel] RC5 TX output level - 64 bit

[James Shaver]

For what it’s worth, I’m not seeing any difference with my 6300 and DAX/SSDR 
3.0.19 between 2.0.1 and 2.1.0 RC5.  ‘

Your 6600 must be defective - send it to me for, uh, proper disposal.  ;). 

73,

Jim S. 

> On May 2, 2019, at 8:16 AM, Bill Somerville  wrote:
> 
>> On 02/05/2019 12:55, Al wrote:
>> (Flex 6600, SSDR&DAX 3.0.19, Wsjt 2.1.0-rc5, Win10 )
>> I have noted the the TX output level from WSJT-x v2.1.0-rc5 64bit ( all 
>> modes ) is 8db lower than in v2.0.1.  The 32 bit version of 2.1.0-rc5 
>> produces the same TX output level as v2.0.1.
>> 
>> It's not an operational problem form me as I can compensate else where. It 
>> just different.
>> 
>> AL, K0VM
> Hi Al,
> 
> that is surprising as I was not aware of any changes. How are you measuring 
> that, and are you certain that you have all level controls set equally? I ask 
> because some o/s audio level settings are remembered per application.
> 
> One possibility may be a difference in the mapping of the internal level 
> control to the PCM stream level (log/lin/something else), are you running 
> with the WSJT-X Pwr slider at maximum? If not, do you see the same level 
> difference if you do set it to maximum?
> 
> 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] Log QSO Window -> OK and Cancel buttons odd behavior

[James Shaver]

There’s already a thread on this with 50+ responses...

> On Apr 30, 2019, at 10:10 PM, Edfel Rivera  wrote:
> 
> --541e5a0587ca073c
> Content-Type: text/plain; charset="UTF-8"
> 
> Hi:
> 
> I noticed sometimes the popup window to log QSO shows OK at the left
> (expected) and sometimes the button shown at left is CANCEL.   Minor issue
> but for consistency should be verified.
> 
> 73'
> 
> Edfel
> KP4AJ
> 
> --541e5a0587ca073c
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
> 
> Hi:I noticed sometimes the =
> popup window to log QSO shows OK at the left (expected) and sometimes the b=
> utton shown at left is CANCEL.=C2=A0=C2=A0 Minor issue but for consistency =
> should be verified.73' iv>EdfelKP4AJ
> 
> --541e5a0587ca073c--


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

Re: [wsjt-devel] The FT4 Protocol for Digital Contesting - more on frequencies

[James Shaver]

I am headed to 17 myself - maybe I’ll see you there :)

> On Apr 30, 2019, at 11:02 AM, Hasan al-Basri  
> wrote:
> 
> Hi Jim, and tnx 20m FT4 qso.
> 
> I have been spotted on 40m, 20m, 30m in the last 10 min or so. I have not 
> seen any spots from my 17m signal, nor have I seen any sigs. 
> 
> I'll try a few CQs on 15 and 10 to see if any spots show up.
> 
> 73, N0AN
> Hasan
> 
> 
>> On Tue, Apr 30, 2019 at 9:50 AM James Shaver  wrote:
>> I watched one CW signal on 40 intentionally move until it was zero beat with 
>> it signal.  Not a single QSO was disrupted by them. Hilariously, their 
>> attempt to QRM gave me great data about how easily the protocol will reject 
>> DQRM of that nature. The irony is delicious. 
>> 
>> Jim S. 
>> N2ADV
>> 
>>> On Apr 30, 2019, at 7:43 AM, Gary Kohtala - K7EK via wsjt-devel 
>>>  wrote:
>>> 
>>> It's already happening. Just a few minutes ago on the current 40m FT4 
>>> frequency I am hearing multiple
>>> attempts at jamming and harassment. People tuning up and swishing their 
>>> VFO's, sending unidentified
>>> CW messages such as "Go away", etc. They have to be very optimistic 
>>> thinking that (m)any of the folks on
>>> JT modes are able to hear them and/or be expected to respond to CW 
>>> messages. Absolutely hilarious. 
>>> The jammers don't know that the software will just see their attempts at 
>>> disruption as very insignificant
>>> bumps in the road. FT4 will just keep on sending until the message is 
>>> received, just like the other JT
>>> modes. Very entertaining. I seem to remember something similar when FT8 
>>> exploded onto the scene in a similar manner. Let's revisit this in six 
>>> months and see where we stand.
>>> 
>>> Best regards,
>>> 
>>> Gary, K7EK
>>> 
>>> ---
>>> 
>>> 
>>> On Tuesday, April 30, 2019, 7:32:44 AM EDT, James Shaver  
>>> wrote:
>>> 
>>> 
>>> 60 is never included because people don’t read before they transmit (I know 
>>> that’s a shocker) and were transmitting out of band or illegally because of 
>>> the vast differences between 60 meter rules. 
>>> 
>>> > On Apr 30, 2019, at 7:25 AM, Christoph Berg  wrote:
>>> > 
>>> > Re: Bill Somerville 2019-04-29 
>>> > <6c16f722-5577-e692-e1a3-78a3c38b9...@classdesign.com>
>>> >> In summary WSJT-X v2.1.0 RC5 will have the following FT4 suggested
>>> >> frequencies (the Iter1 column):
>>> >> 
>>> >> Band Iter0  Iter1  Notes
>>> >> -
>>> >> 8035953575  (plus 3568 Region 3)
>>> >> 4070907047
>>> > 
>>> > Shouldn't 60m be included here as well? (Also FT8)
>>> > 
>>> > (My assumption is that FT4 will take much of the existing FT8 traffic,
>>> > because people hate waiting. Judging by the amount of FT4 on the first
>>> > day, that might happen very soon.)
>>> > 
>>> > Christoph
>>> > 
>>> > 
>>> > ___
>>> > 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
>> ___
>> 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] The FT4 Protocol for Digital Contesting - more on frequencies

[James Shaver]

*my. Not “it”

Auto correct on iOS hates me. 

> On Apr 30, 2019, at 10:47 AM, James Shaver  wrote:
> 
> I watched one CW signal on 40 intentionally move until it was zero beat with 
> MY signal.  Not a single QSO was disrupted by them. Hilariously, their 
> attempt to QRM gave me great data about how easily the protocol will reject 
> DQRM of that nature. The irony is delicious. 
> 
> Jim S. 
> N2ADV
> 
>> On Apr 30, 2019, at 7:43 AM, Gary Kohtala - K7EK via wsjt-devel 
>>  wrote:
>> 
>> It's already happening. Just a few minutes ago on the current 40m FT4 
>> frequency I am hearing multiple
>> attempts at jamming and harassment. People tuning up and swishing their 
>> VFO's, sending unidentified
>> CW messages such as "Go away", etc. They have to be very optimistic thinking 
>> that (m)any of the folks on
>> JT modes are able to hear them and/or be expected to respond to CW messages. 
>> Absolutely hilarious. 
>> The jammers don't know that the software will just see their attempts at 
>> disruption as very insignificant
>> bumps in the road. FT4 will just keep on sending until the message is 
>> received, just like the other JT
>> modes. Very entertaining. I seem to remember something similar when FT8 
>> exploded onto the scene in a similar manner. Let's revisit this in six 
>> months and see where we stand.
>> 
>> Best regards,
>> 
>> Gary, K7EK
>> 
>> ---
>> 
>> 
>> On Tuesday, April 30, 2019, 7:32:44 AM EDT, James Shaver  
>> wrote:
>> 
>> 
>> 60 is never included because people don’t read before they transmit (I know 
>> that’s a shocker) and were transmitting out of band or illegally because of 
>> the vast differences between 60 meter rules. 
>> 
>> > On Apr 30, 2019, at 7:25 AM, Christoph Berg  wrote:
>> > 
>> > Re: Bill Somerville 2019-04-29 
>> > <6c16f722-5577-e692-e1a3-78a3c38b9...@classdesign.com>
>> >> In summary WSJT-X v2.1.0 RC5 will have the following FT4 suggested
>> >> frequencies (the Iter1 column):
>> >> 
>> >> Band Iter0  Iter1  Notes
>> >> -
>> >> 8035953575  (plus 3568 Region 3)
>> >> 4070907047
>> > 
>> > Shouldn't 60m be included here as well? (Also FT8)
>> > 
>> > (My assumption is that FT4 will take much of the existing FT8 traffic,
>> > because people hate waiting. Judging by the amount of FT4 on the first
>> > day, that might happen very soon.)
>> > 
>> > Christoph
>> > 
>> > 
>> > ___
>> > 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
> ___
> 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] The FT4 Protocol for Digital Contesting - more on frequencies

[James Shaver]

I watched one CW signal on 40 intentionally move until it was zero beat with it 
signal.  Not a single QSO was disrupted by them. Hilariously, their attempt to 
QRM gave me great data about how easily the protocol will reject DQRM of that 
nature. The irony is delicious. 

Jim S. 
N2ADV

> On Apr 30, 2019, at 7:43 AM, Gary Kohtala - K7EK via wsjt-devel 
>  wrote:
> 
> It's already happening. Just a few minutes ago on the current 40m FT4 
> frequency I am hearing multiple
> attempts at jamming and harassment. People tuning up and swishing their 
> VFO's, sending unidentified
> CW messages such as "Go away", etc. They have to be very optimistic thinking 
> that (m)any of the folks on
> JT modes are able to hear them and/or be expected to respond to CW messages. 
> Absolutely hilarious. 
> The jammers don't know that the software will just see their attempts at 
> disruption as very insignificant
> bumps in the road. FT4 will just keep on sending until the message is 
> received, just like the other JT
> modes. Very entertaining. I seem to remember something similar when FT8 
> exploded onto the scene in a similar manner. Let's revisit this in six months 
> and see where we stand.
> 
> Best regards,
> 
> Gary, K7EK
> 
> ---
> 
> 
> On Tuesday, April 30, 2019, 7:32:44 AM EDT, James Shaver  
> wrote:
> 
> 
> 60 is never included because people don’t read before they transmit (I know 
> that’s a shocker) and were transmitting out of band or illegally because of 
> the vast differences between 60 meter rules. 
> 
> > On Apr 30, 2019, at 7:25 AM, Christoph Berg  wrote:
> > 
> > Re: Bill Somerville 2019-04-29 
> > <6c16f722-5577-e692-e1a3-78a3c38b9...@classdesign.com>
> >> In summary WSJT-X v2.1.0 RC5 will have the following FT4 suggested
> >> frequencies (the Iter1 column):
> >> 
> >> Band Iter0  Iter1  Notes
> >> -
> >> 8035953575  (plus 3568 Region 3)
> >> 4070907047
> > 
> > Shouldn't 60m be included here as well? (Also FT8)
> > 
> > (My assumption is that FT4 will take much of the existing FT8 traffic,
> > because people hate waiting. Judging by the amount of FT4 on the first
> > day, that might happen very soon.)
> > 
> > Christoph
> > 
> > 
> > ___
> > 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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] The FT4 Protocol for Digital Contesting - more on frequencies

[James Shaver]

60 is never included because people don’t read before they transmit (I know 
that’s a shocker) and were transmitting out of band or illegally because of the 
vast differences between 60 meter rules. 

> On Apr 30, 2019, at 7:25 AM, Christoph Berg  wrote:
> 
> Re: Bill Somerville 2019-04-29 
> <6c16f722-5577-e692-e1a3-78a3c38b9...@classdesign.com>
>> In summary WSJT-X v2.1.0 RC5 will have the following FT4 suggested
>> frequencies (the Iter1 column):
>> 
>> Band Iter0   Iter1   Notes
>> -
>> 8035953575   (plus 3568 Region 3)
>> 4070907047
> 
> Shouldn't 60m be included here as well? (Also FT8)
> 
> (My assumption is that FT4 will take much of the existing FT8 traffic,
> because people hate waiting. Judging by the amount of FT4 on the first
> day, that might happen very soon.)
> 
> Christoph
> 
> 
> ___
> 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] 7047 Khz QRM to/from Who??

[James Shaver]

One tiny CW frequency in a 3kHz passband should not be much of an issue if you 
have a notch filter - try to notch it out and see if that helps. 

> On Apr 29, 2019, at 7:58 PM, Rich Zwirko - K1HTV  wrote:
> 
> Well,
>Guess what station is on 7047 KHz, the new 40 Meter FT4 frequency and what 
> are they doing? Would you believe W1AW transmits CW Bulletins on 7047 MHz. 
> And they are 30dB over 9 here in VA this evening.   Oooops. Not a good 
> frequency!  Back to the drawing board for another 40M FT4 frequency.
> 
> 73,
> Rich - K1HTV
> ___
> 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] Bugies in 2.1.0

[James Shaver]

I can read between the lines and I think it’s fantastic. 

> On Apr 29, 2019, at 5:58 PM, Jim Nuytens via wsjt-devel 
>  wrote:
> 
> There's always a more determined LID. ;-)
> 
>> On 4/29/2019 17:29, Bill Somerville wrote:
>> Christoph,
>> 
>> not disagreeing but there are reasons for this that I can't reveal. Let's 
>> just say it is to deter LIDs. Sorry.
>> 
>> 73
>> Bill
>> G4WJS.
>> 
> 
> 
> ---
> This email has been checked for viruses by AVG.
> https://www.avg.com
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

Re: [wsjt-devel] Sometimes difficult to get FT4 QSOs completed

[James Shaver]

I’ve been in the RR73 loop quite a bit 

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 3:07 PM, DG2YCB, Uwe  wrote:
> 
> Hi, just made a couple of FT4 QSOs. Works well. However, sometimes it’s 
> somewhat difficult to get the QSOs completed. Endless exchange of reports but 
> no 73 or RR73 message. Is anyone else experiencing this?
>  
> 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

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

I’m in the correct configuration of FT4.  It is only my Win7 32 bit machine.  
My Win 7 Pro 64 Bit and my Win 10 machines don’t have any issue after selecting 
FT4 as the mode.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 3:08 PM, Bill Somerville  wrote:
> 
>> On 29/04/2019 20:05, James Shaver wrote:
>> Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will 
>> remain in FT8 mode until I close WSJTX down and reopen it.
>> 
>> 73,
>> 
>> Jim S.
>> N2ADV
> 
> Hi Jim,
> 
> that seems unlikely. Are you sure you are not looking at the configuration 
> name, perhaps you have a configuration selected on that machine called "FT8".
> 
> 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 2.1.0-rc5

[James Shaver]

Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will remain 
in FT8 mode until I close WSJTX down and reopen it.  

73,

Jim S. 
N2ADV 

> On Apr 29, 2019, at 2:57 PM, Bill Somerville  wrote:
> 
> Hi Jim,
> 
> in what way doesn't it work on the 32-bit version? Are you saying that the 
> "Menu->Mode->FT4" button is not functioning?
> 
> 73
> Bill
> G4WJS.
> 
>> On 29/04/2019 19:54, James Shaver wrote:
>> Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 
>> bit) machine, it won’t resolve for me unless I restart.  
>> 
>> 73,
>> 
>> Jim S. 
>> N2ADV (ex KD2BIP)
>> 
>>>> On Apr 29, 2019, at 2:49 PM, Bill Somerville  wrote:
>>>> 
>>>> On 29/04/2019 19:38, James Shaver wrote:
>>>> Follow up - mode gets changed back to FT8 if I got into the settings and 
>>>> change anything (for example, checking the box “Alternate F1-F6 bindings” 
>>>> and clicking OK returns the mode to FT8 and FT4 mode, even if selected, 
>>>> won’t work until the program is closed and restarted.
>>> Hi Jim,
>>> 
>>> thanks for the issue report, I can confirm this is a defect. Clicking the 
>>> "OK" button to leave the Settings dialog will take the mode out of FT4 and 
>>> set FT8. You can work around this by selecting FT4 mode again.
>>> 
>>> 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 2.1.0-rc5

[James Shaver]

Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 bit) 
machine, it won’t resolve for me unless I restart.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:49 PM, Bill Somerville  wrote:
> 
>> On 29/04/2019 19:38, James Shaver wrote:
>> Follow up - mode gets changed back to FT8 if I got into the settings and 
>> change anything (for example, checking the box “Alternate F1-F6 bindings” 
>> and clicking OK returns the mode to FT8 and FT4 mode, even if selected, 
>> won’t work until the program is closed and restarted.
> 
> Hi Jim,
> 
> thanks for the issue report, I can confirm this is a defect. Clicking the 
> "OK" button to leave the Settings dialog will take the mode out of FT4 and 
> set FT8. You can work around this by selecting FT4 mode again.
> 
> 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 2.1.0-rc5

[James Shaver]

Hey, Bill - thanks.  See my last note re: same :)

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:38 PM, Bill Somerville  wrote:
> 
>> On 29/04/2019 19:30, James Shaver wrote:
>> Also, I’m already seeing quite a few people that have skipped step 8 in the 
>> setup instructions.
> 
> Hi Jim,
> 
> that is consistent with Joe's release announcement, see the last sentence 
> here:
> 
> "FT4 is designed for contesting, but it will likely find some use for normal 
> QSOs as well, especially during the beta test period. In the coming month we 
> hope to receive useful feedback on the user interface, message sequencing, 
> interaction with logging programs, etc.  Probably it's best to use "normal" 
> (non-contest) messages except during the mock-contest practice sessions 
> scheduled for  - 0100 UTC on May 9 and May 14, and (if needed) June 5."
> 
> 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 2.1.0-rc5

[James Shaver]

Follow up - mode gets changed back to FT8 if I got into the settings and change 
anything (for example, checking the box “Alternate F1-F6 bindings” and clicking 
OK returns the mode to FT8 and FT4 mode, even if selected, won’t work until the 
program is closed and restarted.  

Also as a follow up to my below about step 8 - looks like the release email has 
a slight conflict with the PDF - perhaps the PDF with the setup instructions 
should be modified?  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:30 PM, James Shaver  wrote:
> 
> I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
> getting changed back to FT8 and my frequency is jumping to 14.074.  This 
> appears to be random (though it still shows the “FT4” configuration as being 
> selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
> closing the program and reopening brings me back to where I need to be. A 
> reboot appears to have cured this but FYI in case anyone else is 
> experiencing a similar issue.  
> 
> Also, I’m already seeing quite a few people that have skipped step 8 in the 
> setup instructions.  
> 
> 73,
> 
> Jim S. 
> N2ADV (ex KD2BIP)
> 
>> On Apr 29, 2019, at 2:05 PM, Joe Taylor  wrote:
>> 
>> To:   Users of WSJT-X -- especially those interested in radio contesting
>> From: WSJT Development Group
>> 
>> By now most of you know about the FT4 protocol under development for 
>> eventual release in WSJT-X 2.1.0.  The new mode is particularly optimized 
>> for use in radio contesting.
>> 
>> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, and 
>> is 4.6 dB less sensitive.  Many other details are summarized in "The FT4 
>> Protocol for Digital Contesting", available here:
>> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
>> Links to translations in other languages are available on the WSJT-X web 
>> page:
>> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>> 
>> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through June 
>> 7, 2019.  Please note that the FT4 mode should NOT be used in the ARRL June 
>> VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
>> 
>> We have done our best to provide suggested operating frequencies for the 
>> test period consistent as far as possible with world-wide band plans and 
>> existing usage.  Please note that thanks to good user feedback, some of 
>> these frequencies are different from those suggested in the document linked 
>> above.
>> 
>> Default frequencies currently recommended for FT4 are as follows:
>> 
>> Band   MHzNotes
>> -
>> 803.575   (3.568 MHz in Region 3)
>> 407.047
>> 30   10.140
>> 20   14.080
>> 17   18.104
>> 15   21.140
>> 12   24.919
>> 10   28.180
>> 6   50.318
>> 2  144.170
>> 
>> FT4 is designed for contesting, but it will likely find some use for normal 
>> QSOI’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the 
>> mode getting changed back to FT8 and my frequency is jumping to 14.074.  
>> This appears to be random (though it still shows the “FT4” configuration as 
>> being selected).  Selecting FT4 as the mode does not put me back to 14.080 
>> but closing the program and reopening brings me back to where I need to be. 
>> A reboot appears to have cured this but FYI in case anyone else is 
>> experiencing a similar issue.  
> 
> Also, I’m already seeing quite a few people that have skipped step 8 in the 
> setup instructions.  
> 
> 73,
> 
> Jim S. 
> N2ADV (ex KD2BIP)
> 
>> On Apr 29, 2019, at 2:05 PM, Joe Taylor  wrote:
>> 
>> To:   Users of WSJT-X -- especially those interested in radio contesting
>> From: WSJT Development Group
>> 
>> By now most of you know about the FT4 protocol under development for 
>> eventual release in WSJT-X 2.1.0.  The new mode is particularly optimized 
>> for use in radio contesting.
>> 
>> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, and 
>> is 4.6 dB less sensitive.  Many other details are summarized in "The FT4 
>> Protocol for Digital Contesting", available here:
>> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
>> Links to translations in other languages are available on the WSJT-X web 
>> page:
>> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>> 
>> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through June 
>> 7, 2019.  Please note that the FT4 mode should

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
getting changed back to FT8 and my frequency is jumping to 14.074.  This 
appears to be random (though it still shows the “FT4” configuration as being 
selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
closing the program and reopening brings me back to where I need to be. A 
reboot appears to have cured this but FYI in case anyone else is 
experiencing a similar issue.  

Also, I’m already seeing quite a few people that have skipped step 8 in the 
setup instructions.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:05 PM, Joe Taylor  wrote:
> 
> To:   Users of WSJT-X -- especially those interested in radio contesting
> From: WSJT Development Group
> 
> By now most of you know about the FT4 protocol under development for eventual 
> release in WSJT-X 2.1.0.  The new mode is particularly optimized for use in 
> radio contesting.
> 
> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, and is 
> 4.6 dB less sensitive.  Many other details are summarized in "The FT4 
> Protocol for Digital Contesting", available here:
> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
> Links to translations in other languages are available on the WSJT-X web page:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through June 
> 7, 2019.  Please note that the FT4 mode should NOT be used in the ARRL June 
> VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
> 
> We have done our best to provide suggested operating frequencies for the test 
> period consistent as far as possible with world-wide band plans and existing 
> usage.  Please note that thanks to good user feedback, some of these 
> frequencies are different from those suggested in the document linked above.
> 
> Default frequencies currently recommended for FT4 are as follows:
> 
> Band   MHzNotes
> -
> 803.575   (3.568 MHz in Region 3)
> 407.047
> 30   10.140
> 20   14.080
> 17   18.104
> 15   21.140
> 12   24.919
> 10   28.180
> 6   50.318
> 2  144.170
> 
> FT4 is designed for contesting, but it will likely find some use for normal 
> QSOs as well, especially during the beta test period.  In the coming month we 
> hope to receive useful feedback on the user interface, message sequencing, 
> interaction with logging programs, etc.  Probably it's best to use "normal" 
> (non-contest) messages except during the mock-contest practice sessions 
> scheduled for  - 0100 UTC on May 9 and May 14, and (if needed) June 5.
> 
> Downloadable installation packages for WSJT-X 2.1.0-rc5 under Windows, Linux, 
> and macOS are available on the WSJT-X web page:
> 
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> Windows users will discover that WSJT-X v2.1.0 has been made available as a 
> 64-bit MS Windows build for 64-bit versions of Windows since Vista. This 
> veraion has one known defect. The audio input device level will be reset to 
> 100% when WSJT-X is started, when the input audio device is changed, and when 
> switching to a new configuration. This is a Qt framework defect that we have 
> reported and is being fixed in a future release; until then users should take 
> care to set the device audio level back to 0dB or lower depending on 
> requirements. Note that many sound cards and chips have real gain ahead of 
> the ADC, as much as 14dB, which will be turned to the maximum due to this 
> defect and is usually undesirable when using WSJT-X.
> 
> Despite this annoying defect, we recommend the 64-bit version of WSJT-X on MS 
> Windows as it has significant advantages in decoding speed.
> 
>-- 73 from Joe, K1JT; Steve, K9AN; and 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] FT4 Frequencies

[James Shaver]

FWIW: I still use JT9 regularly using milliwatts of power for experiments and 
get stomped on by JS8 constantly.

> On Apr 28, 2019, at 11:51 AM, Bill Somerville  wrote:
> 
>> On 28/04/2019 16:07, Richard Solomon wrote:
>> Since roll-out is imminent, have we an agreement on which 
>> frequencies to use ?
>> 
>> 73, Dick, W1KSZ
> Hi Dick,
> 
> not yet. There are many claims on the frequencies we have proposed, a few 
> with suggested alternatives but mostly just asking us to go elsewhere. 
> Getting to an acceptable set of suggested frequencies for FT4 even for 
> occasional contest periods is difficult and it is made even harder if we 
> assume, not unreasonably, that FT4 may be used for general DXing as well.
> 
> One option is not to recommend any frequencies and let the community sort it 
> out, then add the resulting frequencies to the default recommendations later 
> as/if they converge. Unfortunately I don't think that will achieve the 
> desirable global coordination, nor is it likely to converge on the best 
> choices. The only good attribute would be that the developers can say "we 
> didn't choose that frequency, don't blame us for QRM" which is a bit of a cop 
> out, and we will still be blamed anyway.
> 
> Another option is to sacrifice the JT9 slots in favour of FT4. Clearly that 
> is not straightforward given that JS8CALL has made a claim on that bandwidth 
> too. Personally I would love to see JT9 get more use, it is a great mode for 
> HF and I miss working the world with a few mW on the HF bands.
> 
> Given the lack of truly free globally available slots in the narrow band 
> digital mode band plans, I suspect that no more than one 2 kHz slot per band 
> for FT4 should be an aim. By that I mean that if there is a contest using FT4 
> then it should use those frequencies and non-contest participants should 
> defer. This is based on the premiss that FT4 has been designed with contests 
> in mind. This would need somewhat smarter logic in WSJT-X to try and avoid 
> chaos when non-contest participants inadvertently get involved in contest 
> QSOs. Of course each contest's organizers can elect to suggest different 
> slots which may be acceptable if the traffic volumes are low enough.
> 
> Suggestions are still welcome, nothing is set in stone just yet.
> 
> 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] False Decodes

[James Shaver]

You can turn off AP decoding but, of course, you no longer have the advantage 
of AP decoding (whether that’s a loss is up to you).  

Or, you could ignore them since you’re aware they’re false decodes random 
patterns in the static can make the program spit out a false decode and it is 
just something that happens.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 26, 2019, at 11:04 AM, Mike Oakley  wrote:
> 
> I continue to get false decodes everyday even when I am not transmitting, for 
> example today I cut my rig on and loaded the software and then I got a false 
> decode before anything even popped on my screen. Can someone tell me why I am 
> getting these and how do I stop them?
> ___
> 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] Suggestion for Additional Checkbox

[James Shaver]

No CAT control with this old rig (picture attached) and it holds its own ;)



> On Apr 25, 2019, at 5:07 PM, Jim Shorney  wrote:
> 
> 
> The point was that CAT is not essential in any case. The notion that CAT is 
> *required* to use FT/JT modes is a myth propagated by those who don't know 
> any better. There are those of us who do not use CAT for whatever reason and 
> we appreciate the ability to operate this way. To successfully to so requires 
> a level of knowledge and skill a bit above the plug-and-play appliance level. 
> Try it sometime. :D
> 
> 73
> 
> -Jim
> NU0C
> 
> 
> On Thu, 25 Apr 2019 09:19:16 -0400
> Frank Kirschner  wrote:
> 
>>> Actually, no it (rig split via CAT) is not at all essential. However,
>>> using the software without CAT control requires actual radio knowledge.
>>> 
>> Actually, it's pretty easy if you have the right equipment. The Flex Radio  
>> 6600 and Maestro combination allow control without the usual CAT
>> functionality. They communicate via TCP ports. There is a CAT program
>> provided, but I don't even run it when using the Maestro to control the rig.
> 
> 
> 
> ___
> 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] FT4 Beta download

[James Shaver]

Helps to read the PDF and the announcement fully. The answer is there. 

> On Apr 22, 2019, at 5:32 PM, Enrique Scheuer  
> wrote:
> 
> Hello all 
> 
> Just coming in and also wanting to give my contribution..
> 
> May I ask where to download the FT4 beta version?
> 
> 73 de Enrique 
> PY2CP
> ___
> 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] Suggestion for Additional Checkbox

[James Shaver]

At one point the controls for F/H were on the main part of the GUI and the 
group was flooded with questions asking why they were receiving and 
transmitting “funny” because they were inadvertently checking the box when it 
was on the main page. That went away when the box was moved into the settings. 

> On Apr 21, 2019, at 3:31 PM, Jim Shorney  wrote:
> 
> 
> F2 is your friend. If 'Advanced" was the last active tab you you will be 
> right there. That's a single key stroke! What's so hard about that?
> 
> 73
> 
> -Jim
> NU0C
> 
> 
> On Sun, 21 Apr 2019 13:38:24 -0400
> Frank Kirschner  wrote:
> 
>>> On Sat, Apr 20, 2019 at 10:53 PM WB5JJJ  wrote:
>>> 
>>> F/H is not something you would normally select on a frequent basis,
>>> 
>> 
>> Yes it is. I mostly do DX hunting, and around 10 to 15% of my QSOs have
>> been in F/H mode. Normally, I never respond to CQs from band-entities that
>> I already have confirmed on LoTW. If someone calls me while I'm working DX,
>> I will respond, but that requires turning off F/H mode before doing so. A
>> checkbox would make that easier. I certainly select or unselect F/H mode
>> more often than Hold Tx Freq or Call 1st, and there are checkboxes for
>> those.
>> 
>>> so a check box cluttering the main screen is not necessary.
>>> 
>> 
>> As I pointed out, it wouldn't clutter the screen. There is ample room for
>> several more checkboxes.
>> 
>>> 
>>> As previously suggested setting a Configuration for that mode (and others)
>>> are just 2 clicks away and totally customizable.  This procedure is
>>> outlined in the User Manual.  It's simple and effective.
>>> 
>>> Yes, that's an adequate workaround. But there are several selections  
>> available on the screen that I don't normally change, and these could be
>> accessed through different configurations. Yet, they are on the main
>> screen. It's just a difference in operating style.
>> 
>> 
>>> WB5JJJ - George
>>> 
>> 
>> It was just a suggestion. Some people are not open to suggestions.
>> 
>> Thanks for your input.
>> 
>> 73,
>> Frank
>> KF6E
>> 
>>> 
>>> On Sat, Apr 20, 2019 at 7:44 PM Frank Kirschner 
>>> wrote:
>>> 
 Good idea. I'm not familiar enough with the program to have thought of
 that. Thanks.
 
 73,
 Frank
 KF6E
 
> On Sat, Apr 20, 2019 at 6:16 PM N3SL  wrote:
> 
> Just a suggestion - works for me:  Create a F/H "configuration" and
> toggle to it.  Two mouse clicks.
> 
> On Sat, Apr 20, 2019 at 4:50 PM Frank Kirschner <  
> frank.kirsch...@gmail.com> wrote:  
> 
>> Between the Hold Tx Freq checkbox and the Call 1st checkbox, there is
>> room for several more checkboxes. One I would suggest is Fox/Hound mode. 
>> I
>> would also suggest this automatically set Split to either Rig or Fake It,
>> which could be selected somewhere else.
>> 
>> If the menus are turned off, it takes a while to turn them on and
>> navigate to the correct spot to set fox/hound and split mode. This
>> sometimes is long enough to miss a weak one. A checkbox would not only 
>> make
>> it faster, but it would encourage using that mode for those who are still
>> learning FT8 operation.
>> 
>> 73,
>> Frank
>> KF6E
>> ___
>> 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
>>> 
> 
> 
> 
> ___
> 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] People are rude at times

[James Shaver]

And speaking of S/N, I just realized this is the “devel” reflector and not the 
generic WSJT Group reflector.  This really isn’t a topic suitable for the 
development side, to be honest... 

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 18, 2019, at 4:34 PM, James Shaver  wrote:
> 
> It never ceases to amaze me how so many hams instantly jump to the conclusion 
> that what they witness on the air is automatically attributed to intentional 
> “rudeness” or ill intent. 
> 
> His s/n is not really relevant - it’s very possible that even if propagation 
> was, to coin a phrase, putting this person in your lap, that does not mean 
> you’re even a weak trace on his/her end. That person may have a very high 
> local noise floor due to an indoor antenna or a lot of noisy consumer 
> electronics around them or it could even be as simple as plain old 
> propagation differences or it could be someone who has just jumped into 
> digital modes for the very first time and is not yet familiar with the 
> interface. 
> 
> If it bothers you that much, look up their email on QRZ and send them a 
> screen shot and *politely* ask if they even heard/saw you. If they didn’t, 
> offer to help them track down local noise generators or help them optimize 
> their receive setup. 
> 
> It pays to give people the benefit of the doubt. If they turn out to be a 
> jerk, then you can at least walk away with the satisfaction that you tried 
> your best to be an “Elmer” and are, at the end of the day, the better person. 
> 
> And relax. It’s just ham radio. Nobody died on the table. This is supposed to 
> be fun. 
> 
> Jim S. 
> N2ADV
> 
> ___
> 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] People are rude at times

[James Shaver]

It never ceases to amaze me how so many hams instantly jump to the conclusion 
that what they witness on the air is automatically attributed to intentional 
“rudeness” or ill intent. 

His s/n is not really relevant - it’s very possible that even if propagation 
was, to coin a phrase, putting this person in your lap, that does not mean 
you’re even a weak trace on his/her end. That person may have a very high local 
noise floor due to an indoor antenna or a lot of noisy consumer electronics 
around them or it could even be as simple as plain old propagation differences 
or it could be someone who has just jumped into digital modes for the very 
first time and is not yet familiar with the interface. 

If it bothers you that much, look up their email on QRZ and send them a screen 
shot and *politely* ask if they even heard/saw you. If they didn’t, offer to 
help them track down local noise generators or help them optimize their receive 
setup. 

It pays to give people the benefit of the doubt. If they turn out to be a jerk, 
then you can at least walk away with the satisfaction that you tried your best 
to be an “Elmer” and are, at the end of the day, the better person. 

And relax. It’s just ham radio. Nobody died on the table. This is supposed to 
be fun. 

Jim S. 
N2ADV

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

Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each transmission?

[James Shaver]

Hi Paul,

Good info (and similar to my own line of thinking in the response I just sent 
on ALC Overshoot) but I’d recommend one minor change: 

Your statement “The best way to avoid spikes in any rig using FT8...” - I’d be 
cautious with the “any rig” generalization.  Some of the popular radios on the 
market with a closed loop power system like the Elecraft K-line and KX-line 
will actually “power hunt” if the ALC meter is not showing 3-4 bars of activity 
on the ALC meter.  The first 4 bars of the ALC meter on the K/KX-line radios 
function like a vu meter and not necessarily indicate ALC action.  The radio 
itself may actually overmodulate the signal in order to get the power output 
set by the power output control and cause a transmitted signal to be quite 
poor.  I was able to test this using my K3 and KX3 into a dummy load and 
viewing the signal output with a spectrum analyzer and the term for the signal 
produced with “0” bars of “ALC” showing was “icky” at best (very technical, I 
know :) ).  

Just a word of caution for anyone following this thread.  

73,

Jim S. 
N2ADV 

> On Apr 12, 2019, at 2:06 PM, Paul Randall  wrote:
> 
> Start-of- transmission power spikes will almost certainly occur on any radio 
> which is using traditional alc to control output power. Spike severity is 
> directly linked to the amount of gain reduction the alc is giving. For 
> example,  a 100w rig with power output reduced to 5w using a power control 
> which operates via the alc system can be almost relied upon to produce 100w 
> spikes at start of transmission. No brainer. 
> 
> The best way to avoid spikes in any rig using FT8 is to carefully adjust 
> audio drive level in the software until desired power output is obtained 
> without the rig applying any alc at all. In this way overall system gain is 
> only sufficient to produce desired power and no more - so spikes are 
> eliminated and you get a cleaner transmission.
> 
> That said, I say again that I can exactly  reproduce this problem at will on 
> 160m where my antenna system clearly puts large voltage onto the cable 
> between the pc and the rig. My interface uses industrial quality logic 
> isolators for civ and ptt together with audio isolation transformers and 
> dozens of ferrite rings on tuner - rig - pc cables.  RFI still gets through 
> and kills the usb connection on 160m.  To cure this I will rethink the 160m 
> antenna which I suspect is the easiest way. 
> 
> Regards Paul G3NJV
> 
> Sent from my Samsung Galaxy smartphone.
> 
> 
>  Original message 
> From: Bill Barrett 
> Date: 12/04/2019 18:11 (GMT+00:00)
> To: fr...@fkirschner.net, WSJT software development 
> 
> Subject: Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each 
> transmission?
> 
> From W8JI.com, maybe 5000 has similar adjustments. If the IF Transmit Gain 
> was too high the 1000 would exhibit huge power spikes on key down or pressing 
> the mike PTT button.
> 
> Transmit Gain Menus
> 
> The FT-1000 MK V  has hidden transmit gain menus. They are accessed by 
> pushing and holding FAST and LOCK while turning the POWER switch on. Both of 
> my MK V's  and every MK V serviced here has had the TX IF gain set too high. 
> This causes first character clicks on CW and spits and splatter on SSB.  Here 
> is how to correct the IF gain to prevent ALC clipping on leading edges of CW 
> and voice:
> 
> Press and hold FAST and LOCK before and during initial POWER on.
> 
> Press FAST and ENT at the same time. You are now in the MENU's and the 
> display should say "0-1 GrPI-cH".
> 
> Turn the VRF/MEM CH counter-clockwise to 9-2. The display should say "t iF - 
> GA in" This is the transmit IF gain menu.
> 
> Turn the SUB VFO knob clockwise one position to  " t iF - 018". This is the 
> 1.8MHz transmit IF gain.
> 
> Press the ALC/COMP meter selector until the bar graph says "ALC".  Set RF PWR 
> knob to full power.
> 
> With the radio on CW and a 50 ohm dummy load connected, close the key and 
> adjust the MAIN VFO-A knob until the ALC display is about 75-85% of full 
> scale on the illuminated bar marked "ALC".
> 
> Press the next band button (3.5), make sure the radio is still  on CW, and 
> turn the SUB VFO-B knob clockwise one band to "t iF - 035".
> 
> Again adjust MAIN VFO-A until ALC is at 75-85% of full scale.
> 
> Repeat this process through all bands.
> 
> Most radios I have tested require a setting of 2 to 4 on TX IF gain, with 3 
> being the most common setting.
> 
> This change will reduce SSB bandwidth and distortion. It will also reduce 
> keyclicks and annoying thumps on the leading edge of each Morse character.
> 
>  Hope this helps;
> 
> Bill W2PKY
> 
> 
>> On Fri, Apr 12, 2019 at 12:38 PM Frank Kirschner  
>> wrote:
>> Some rigs, even high-end rigs including the FTdx5000, exhibit a spike on 
>> initial transmit. I noticed it mostly with the amp. The power would surge 
>> briefly, and then return to the dial value.
>> 
>> I suspect the combinatio

Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each transmission?

[James Shaver]

This almost sounds partially like ALC Overshoot that is more of a problem with 
some radios than with others (it was really nasty on a TS590 that a friend had 
sent to me to test out). The pure 8-tone FSK signal does seem to make this more 
obvious on some of my radios than others.  Some of my radios have a delay 
function that will curb this a bit.  Not sure about the FTDX5000 or about how 
easily those functions would be accessed remotely but it may be worth a look. 

Jim S. 
N2ADV

> On Apr 12, 2019, at 12:38 PM, Frank Kirschner  
> wrote:
> 
> Some rigs, even high-end rigs including the FTdx5000, exhibit a spike on 
> initial transmit. I noticed it mostly with the amp. The power would surge 
> briefly, and then return to the dial value.
> 
> I suspect the combination of the surge and a bit of RFI is causing the 
> problem. I suggest an opto-isolator on both ends of your CAT cable. They are 
> available for RS-232 and USB. That, plus some ferrites along the run should 
> help with the problem. Also, if you're using a desktop, try running several 
> ground straps to the case of the computer. Consumer-grade computers aren't 
> very resistant to RFI, and there is no bonding between the pieces of sheet 
> metal.
> 
> 73,
> Frank
> KF6E
> ___
> 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] One small suggestion...

[James Shaver]

A quick press of F4 clears the call. Retention of the call between band changes 
is useful if you’re chasing a DXPedition on multiple bands. 

Jim S. 
N2ADV

> On Apr 12, 2019, at 10:59 AM, Svend Aage Jessen  wrote:
> 
> Would be nice, though not nessersary, to clear dx call also after
> exit the programme, and changing the band.
> Of course in those cases where there still is a dx call present in the dx 
> call field.
> Could this be an idea?
> 
> -- 
> 73 de LA6YJA
> la6...@savednet.com
> 
> 
> 
> ___
> 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] Fwd: FT8 calling CQ

[James Shaver]

Double clicking on TX1 skips sending the grid. This is done to maximize QSO 
completion rates during short openings. Grid is entirely optional and 
superfluous on HF. 

More info is available in the user manual on this function. 

Jim S. 
N2ADV

> On Apr 10, 2019, at 2:13 PM, Timothy Hickman  
> wrote:
> 
> I have noticed lately that when I send CQ on FT8 A few stations start their 
> respond with the signal report not their grid square.
> 
> Is there something here I do not understand?
> 
> Tim
> 
> N3JON
> 
> 
> 
> ___
> 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] FT8 calling CQ

[James Shaver]

Double clicking on TX1 will skip the grid. This is useful when band conditions 
are unstable. Grid is optional anyhow and not useful for much other than 
turning your antenna toward the station. 

More info on skipping TX1 is available in the user manual (press F1). 

Jim S. 
N2ADV

> On Apr 9, 2019, at 2:29 PM, Timothy Hickman  
> wrote:
> 
> I have noticed lately that when I send CQ on FT8 A few stations respond with 
> the signal report not their grid square.
> 
> Is there something here I do not understand?
> 
> Tim
> 
> N3JON
> 
> 
> 
> ___
> 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] Bug: transmit watchdog timeout leads to receiving own message

[James Shaver]

I’ve experienced this since 1.7 but it’s not consistently reproducible. 

> On Apr 5, 2019, at 7:15 AM, Darren Freeman  
> wrote:
> 
> Hi all,
> 
> I believe I found a bug, but sadly I can't reproduce it now that I've
> restarted the application. It was happening consistently at the time.
> 
> wsjtx 2.0.1 compiled from source on Ubuntu 18.10
> 
> Letting the watchdog timer timeout, a new message will begin
> transmission and then abort immediately. This creates an annoying
> logged transmission in the UI, but I can live with it.
> 
> What really surprised me, is how at the end of the 15s cycle, I would
> then receive this same message, as if it were another station calling
> me! It was highlighted in red, it had the same timestamp as what I had
> failed to transmit.
> 
> IIRC this fake transmission appeared in the waterfall window, also. It
> seems like the audio output was being looped back into the decoder.
> 
> I wish I knew how to reproduce this one, sorry :D
> 
> Have fun,
> Darren
> 
> 
> 
> ___
> 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] Feature Request

[James Shaver]

Ha!  I have experienced this so often lol


> On Apr 1, 2019, at 12:27 PM, George J Molnar  wrote:
> 
> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has 
> been revealed. On April 1st, of all days.
> 
> Whine mode is exotic code that scans the operator’s brainwaves for signs of 
> frustration, and just as he/she is about to give up (afterwards on slower 
> computers) permits a DX decode. Otherwise, only calls from your ITU region 
> are displayed. 
> 
> If you’re calling CQ DX, the software also generates multiple callers from 
> your DXCC entity. Only when you give up and/or answer one will the 
> application unlock DX decoding.
> 
> There are variants on this mode for VHF/UHF, described in the supplemental 
> operators’ guide, chapter 42.
> 
> George J Molnar
> KF2T - Virginia, USA
> 
> 
> 
> 
> ___
> 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] Someone released an Auto CQ mod - my 2 cents

[James Shaver]

Add me to that list. Well said, as always, Bill. 

Jim S. 
N2ADV 

> On Mar 31, 2019, at 2:11 PM, Bobby Chandler  wrote:
> 
> Bravo Bill! I agree 100%.
>  
> Bobby/N4AU
>  
> From: Bill Somerville
> Sent: Sunday, March 31, 2019 11:53 AM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents
>  
>> On 31/03/2019 17:12, Carey Fisher wrote:
>> All I have to say, and I've been saying for some time now, is that maybe 
>> developers will now think twice before releasing software such as this as 
>> Open Source.
> Carey,
> 
> that shows a major misunderstanding of both Open Source software and the 
> complexity of WSJT-X. WSJT-X uses two major components provided by 
> third-party teams that are themselves Open Source. There are no other free 
> equivalent components of sufficient quality and scope and writing our own 
> would take many man-years of effort and ongoing maintenance. These components 
> give us an essential leg up to providing a portable cross-platform 
> application of the highest quality with reasonable development timescales. 
> There are reasons why many closed source applications are Windows only and 
> these factors are high on  the list.
> 
> Aside from that, of the latest two "robot" offerings being touted, one does 
> not require any changes to WSJT-X source code and the other is being offered 
> as a contribution with the contentious robotic parts removed. Either way the 
> WSJT team have no interest in WSJT-X being used as a QSO robot and the 
> automation that has been provided already is only in response to large scale 
> user demand. For example auto-sequencing and "Call 1st" were deemed necessary 
> for FT8 because the small thinking time between decodes completing and the 
> next transmission period requires super-human concentration and reaction 
> times. For QSO modes like FT8 we have a basic user interface rule that each 
> QSO must be initiated by some operator action, e.g. calling CQ or replying to 
> a CQ. At the end of a QSO for normal DX contacts the user has the final say 
> on whether a completed QSO is logged, WSJT-X will prompt the user to log a 
> QSO but they must take further action to confirm a good contact or reject a 
> bad one. There are other operator aids for high QSO rate situations, like 
> contest operating and running a rare and popular DX operation, related to 
> logging QSOs but the requirement for an operator action to initiate each QSO 
> is always maintained.
> 
> What is worth noting is that the small WSJT development team expends a lot of 
> thought and time on how to combat rogue patched versions and add-on tools 
> that attempt to exceed the levels of automation we deem sufficient. These are 
> either misguided or malicious. This detracts from core development and 
> maintenance and we would rather not have to give up that effort.
> 
> On a personal note; my opinion on QSO robots, aside from their questionable 
> legality in many countries, is that most Amateur Radio operators would not 
> consider a QSO with a machine to be worthwhile and to find out that they had 
> done so unknowingly would be very annoying. For those that attempt to deploy 
> such robots, I suggest they go a step further and dispense with the radio 
> equipment and use their PC skills to mock up the certificates and awards and 
> print them directly, that way no one else is being disappointed and they can 
> save themselves a whole lot of cost and time building, operating, and 
> maintaining an Amateur Radio station.
> 
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Incorrect switch from tx3 to tx1

[James Shaver]

The auto sequence is an operator assistance tool, not an operator replacement 
tool - as the control operator it’s a good idea to closely watch the exchange 
and be ready to change on the fly if the other operator acts unpredictability. 
The auto sequence can’t do everything...

> On Mar 1, 2019, at 4:18 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Friend of mine saw this.
> CO2VDD replied to WA1SXK R+07 but then decided to finish a QSO with IZ6AAW 
> and WJST-X then decided to send TX1 when it should have sent TX3 again.
> 
> 
> <1551474981769blob.jpg>
> 
> de Mike W9MDB
> 
> 
> 
> <1551474981769blob.jpg>
> ___
> 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] Error Loading LotW Users Data

[James Shaver]

Nope it can be done post install of 2.0 without issues. 

Jim S. 
N2ADV

> On Dec 11, 2018, at 10:26 PM, R SCHMAHL  wrote:
> 
> The fix for the LotW error: Does that have to be done before you download Ver 
> 2.0 or can it be done after download?  I upgraded to ver2.0 and ignored all 
> warnings and pronouncements and it worked fine. I turned on Monitor and was 
> shocked how many decodes there were (80m). Every CQ I answered someone came 
> back. I called CQ and there were many replys. Maybe I am imagining things but 
> my FT8 success rate seems to be higher then normal. Maybe everyone who 
> upgraded is anxious to try Ver2 out as much as possible because it is new?
> 
> 
> I use DX keeper for logging ( I input the data manually) and it uploads to 
> LotW ok.)  Am I missing something here? Is there and automatic way to get 
> data into DX Keeper that gets screwed up if you don't download the fix? I am 
> little shy about adding this extra file to my system for fear it will break 
> something else.
> 
> 
> I am always perplexed about different operating styles with FT8. Some only 
> reply with signal reports. Some use auto sequence, some don't answer with my 
> report until the 3rd time or never. What gives?
> Thanks-Great job Team
> .
> Ron K2PSD 
> 
> 
>> On Tue, Dec 11, 2018 at 02:53 PM, Joe Taylor wrote:
>> 
>>> On 12/11/2018 2:25 PM, Greg Gilbert KN4APC wrote:
>>> What is the fix for this?
>>> 
>>> Thanks,
>>> Greg KN4APC
>> 
>> New Year's Resolution:
>> 
>> "Before posting a question on setup or usage of WSJT-X I will check the 
>> WSJT-X 2.0 User Guide and look for similar queries on the same reflector."
>> 
>> In this particular case, an installation problem under Windows, try looking 
>> at Section 3.1, "Installation: Windows":
>> 
>> http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html#INSTALL
>> 
>>--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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt rc5

[James Shaver]

Take a peek at the quick start guide as well as the large splash screen that 
comes up when you open RC5… 

 

(you’ll find there that RC4 and RC5 are not backwards compatible with the older 
versions). 

 

Jim S. 

N2ADV

 

From: w...@frontier.com [mailto:w...@frontier.com] 
Sent: Friday, November 30, 2018 6:28 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] wsjt rc5

 

wsjt 2.0.0.5c5  install rc5 and I can not get anything in the band activity 
water fall is ok rc4 and rc5 is the same . I run rc3 and it work great but rc 4 
rc5 

can not work any one I can not see. I run win 7 pro. can I get some help.I 
am not the only one there is 4 of us when I install rc4 it stop my logging

program n3fjp.  any help please   WW8O Gary

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

Re: [wsjt-devel] Expanding FT8 spectrum usage

[James Shaver]

We are free to use these different modes anywhere the band plans allow them.   
The major issue is that there are still users of the other modes that “live” in 
those areas about which you speak.  For example, there are quite a few 
experimenters still using JT65 using QRPP levels who may not be sending spots 
to PSKReporter.  Just because you don’t see them, doesn’t mean they are not 
there.  

 

For those that have been using FT8 since the beginning, I’m sure you’ll recall 
the issues with even using the watering holes that exist currently – the OLIVIA 
and users of other exotic modes were none-too-happy when FT8 moved in.  We want 
to be good neighbors and courteous amateurs as much as possible.  

 

I think a lot of folks forget that there are other bands outside of 20 and 40 
meters.  

 

Jim S. 

N2ADV

 

From: Frederic Beaulieu [mailto:frederic.beaul...@trilliant.com] 
Sent: Thursday, November 29, 2018 1:06 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Expanding FT8 spectrum usage

 

Is it something that has been discussed? My recent experience on 20m seems to 
support this overcrowded problem. There is a lot of CQers but it is really hard 
to actually get the bandwidth to complete contacts.

 

Fred, VE2WFB

 

De : Roy Gould  
Envoyé : 29 novembre 2018 11:26
À : wsjt-devel@lists.sourceforge.net
Objet : [wsjt-devel] Expanding FT8 spectrum usage

 

Now that the cat is out of the bag and FT8 has begun to use dial frequencies 
other than xx.074, when will it be permissible to move up 2KHz when 20 or 40 
meters is very busy and overcrowded?

 

Roy, W7IDM

 

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

Re: [wsjt-devel] State of the Art Weak Signal Modes vs. State of the Art Issue Tracking

[James Shaver]

Brian, it appears you don't understand email reflectors vs email lists.
There has never been an expectation that anyone read all the emails that
come via the reflector. 

 

There is a search function right on the Dev List page that anyone who is
reporting bugs should check first to see if what they're reporting has
already been discussed.  There's a reason every email you get via the
reflector has the URL at the bottom.

 

Jim S. 

N2ADV

 



 

 

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] RC4 Unexpected Behavior of RR73

[James Shaver]

The other person needs to check to see if NA Contest Mode is selected in the 
menu.  

 

From: m...@handgunrepairshop.com [mailto:m...@handgunrepairshop.com] 
Sent: Sunday, November 18, 2018 7:30 PM
To: 'WSJT software development'
Subject: [wsjt-devel] RC4 Unexpected Behavior of RR73

 

As requested in 2.0 Quick Start Guide, a report of unexpected behavior in rc4.

 

214715 Tx 2617 ~ CQ KV4ZY EN91 

214730 -4 0.3 2401 ~ KV4ZY W5PF EM20

214745 Tx 2617 ~ W5PF KV4ZY -04 

214800 -2 0.3 2401 ~ KV4ZY W5PF R EM20

214815 Tx 2617 ~ W5PF KV4ZY RR73 

214845 Tx 2617 ~ CQ KV4ZY EN91 

214830 -2 0.3 2401 ~ KV4ZY W5PF 73

 

Auto seq sent RR73 prior to receiving a signal report in the above QSO, the 
wsjtx.log entry with empty rcvd field;

 

2018-11-18,21:47:30,2018-11-18,21:48:15,W5PF,EM20,14.076617,FT8,-04,,20,TS-2000 
& H-6BTV,

 

Additional observation, the move to 2.0 is slowly gaining users, I had to use 
JTAlert text message to help 2 QSO attempts with me, one was still using rc3 
and the other his very first rc4 QSO today.

 

73 de Doug KV4ZY

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

Re: [wsjt-devel] Problems with RC4

[James Shaver]

Bob, repeated (read: CONSTANT) feedback about things like non standard call 
signs not being compatible with the “older” version of the FT8 Protocol among 
other things as well as the demand to use FT8 in things like Field Day or 
contests is driving it. In short, this is what the users have been asking for 
and this is how they’ll get it. There are other reasons related to decode 
ability and whatnot as well that can be explained by those way more intelligent 
than myself. 

73,
Jim S. 
N2ADV

> On Nov 16, 2018, at 8:13 PM, Bob via wsjt-devel 
>  wrote:
> 
>   My question is why we are making this radical change?  I have been using 
> the WSJT-x for the  past year and have rejuvenated my interest in Ham Radio.  
> Why then are you changing everything to go to a different format and 
> frequency?  Many still have bugs such as my version which I have reloaded  
> several  of 1.9.1  and will now not distinguish colors as to new or worked 
> and limitations as to color modes on the band.  I tried the new release of  
> RCR4 and found I looked at an empty screen most of the time.  Why the change?
>  
> Bob AA7CT
>  
> Sent from Mail for Windows 10
>  
> From: M Lewton
> Sent: Friday, November 16, 2018 4:39 PM
> To: WSJT software development
> Subject: Re: [wsjt-devel] Problems with RC4
>  
> Hello
>  
> I find this version the most sensitive vs. the older versions.  I am also
> using a IC-7300 with only a vertical antenna.
> I just worked JR3GPP calling CQ at -21 we completed the QSO with his -24
> RR73.
>  
> RC4 has other problems that most people have already commented on.
> For me I miss the "Already Worked" the most.
>  
> Maurice
> WA6PHR
>  
> -Original Message-
> From: Giuseppe Molinaro via wsjt-devel
> Sent: Friday, November 16, 2018 9:38 AM
> To: wsjt-devel@lists.sourceforge.net
> Cc: Giuseppe Molinaro
> Subject: [wsjt-devel] Problems with RC4
>  
>  
> I would like to bring to your attention that I had to reinstate version RC3
> because for some unknown reason the RX sensitivity is extremely low when
> using RC4 (about 90% less station decoded as compared to version RC3) on a
> Icom 7300 transceiver.
>  
> I reinstalled RC4 twice with identical results both times
>  
> 73 Giuseppe KE8FT
>  
>  
>  
>  
>  
>  
>  
>  
>  
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C7f49fd6c8bb24a07430d08d64beadd3d%7C84df9e7fe9f640afb435%7C1%7C0%7C636779869479520310&sdata=gpvP%2B%2F%2BNVgS%2Fv4mzd5afNx4OCKs3SfEvhRRpmLBwSuA%3D&reserved=0
>  
>  
>  
> ___
> 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] ESC Key New Feature on rc4 and future v 2.0 NOT A Good Idea!

[James Shaver]

If you do a search of the group, a number of people REQUESTED the functionality 
that was added to the ESC key. So far, it’s come in extremely handy for myself 
and a number of others with whom I’ve spoken. 

Jim S. 
N2ADV

> On Nov 15, 2018, at 5:24 PM, George Hall  wrote:
> 
> Greetings wsjt-devel Group,
> 
> In the recently released Quick-Start Guide to WSJT-2.0 manual by Joe Taylor, 
> K1JT dated November 12, 2018 there is a new feature regarding the ESC key 
> (listed as #7 on page 6) which in my opinion is a very bad idea.
> 
> First of all, the ESC key is “all by itself in left field” on the top left 
> side of the keyboard.  Due to its physical location, this key can be very 
> easily and unintentionally be hit or pressed; especially in the “heat of the 
> moment” during a contest, working a ATNO or your “Second Op” (in my case my 
> cat) happens to visit you and strolls across your keyboard!
> 
> In my opinion, any key stroke intended to create such a multi-function effect 
> like aborting a QSO, clearing the DX Call and selecting Tx6 has planned by 
> pressing the ESC key; should be very carefully re-examined before permanently 
> placed into action in wsjt-x 2.0.
> 
> Perhaps a much better way to execute this aborting QSO multi-function feature 
> would be to utilized the Control key plus simultaneously pressing a letter 
> key, i.e. like pressing the Control (“Ctrl”) key plus pressing the letter 
> “A”.  By doing this fully intentional two keystroke procedure; this should 
> help prevent errors of unintentionally aborting a QSO.  Additionally, has a 
> fail-safe a drop-down window should appear asking “do you really want to 
> about this QSO?” and the ability to select your desired action by selecting a 
> “Yes” or “No” box.
> 
> Finally, again in my opinion; the Escape (“Esc”) key should be dead and 
> non-functional in all wsjt-x software programs because its just too easy to 
> hit by mistake.  If for some reason the need of the Escape key must be used; 
> then a fail-safe drop-down message should follow allowing the user to select 
> their desired action.
> 
> 
> 73,  George  N2CG
> 
> 
> ___
> 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] Auto sequence RC4 TX6 to TX5 and back

[James Shaver]

I tried a search but came up dry on this particular issue with this level of 
detail: using FT8 when calling CQ, if I switch from TX6 to TX5 to send FFT 
(such as “QRM PSE AGN?” or “SRI NO DECODE”) and then for the next cycle I 
return to TX6 to return to calling CQ, if I get a decode in any subsequent 
cycle that should trigger my Auto Sequence to respond (  
, for example) it won’t trigger the auto sequence like expected. I have 
“Call 1st” checked. 

Thanks,

Jim S. 
N2ADV

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

Re: [wsjt-devel] New release RC-4 not decoding anything.

[James Shaver]

Doing ok for me. Made several contacts on 20 meters with no issues that we’re 
not operator error. :)

Jim S 
N2ADV 

> On Nov 13, 2018, at 2:01 PM, John Kludt  wrote:
> 
> Folks,
> 
> Likewise here, loaded right up, making Q's above 2000 Hz no issues to report.
> 
> John K4SQC
> 
>> On Tue, Nov 13, 2018 at 11:26 AM Ed Wilson via wsjt-devel 
>>  wrote:
>> Working great for me...made several contacts above 2000 Hz.
>> 
>> Ed, K0KC
>> 
>> k...@arrl.net
>> http://k0kc.us/
>> 
>> 
>> On Tuesday, November 13, 2018, 10:45:36 AM EST, WB5JJJ  
>> wrote:
>> 
>> 
>> If you read the release notes, support for legacy FT8 has been removed.  
>> Only 77bit operation is available.
>> 
>> On Tue, Nov 13, 2018 at 9:36 AM Bob via wsjt-devel 
>>  wrote:
>> Just downloaded the new Beta RC4 and no signals are showing decoded.  Answer?
>> 
>>  
>> 
>> Bob
>> 
>> AA7CT
>> 
>>  
>> 
>> Sent from Mail for Windows 10
>> 
>>  
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> 
>> -- 
>> George Cotton, WB5JJJ
>> PO Box 1025
>> Russellville, AR  72811
>> 
>> 479.968.7737 Home
>> 479.857.7737 Cell
>> 
>> DMR K5CS (Local Repeater) - 310515, CC1, TS2
>> DMR Arkansas - 3105
>> 
>> 4
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> ___
>> 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] Fox at 7074 ?

[James Shaver]

They’re running knock off software that bastardizes the F/H code. All they’re 
doing is causing confusion instead. 

> On Nov 8, 2018, at 4:25 PM, Pino Zollo  wrote:
> 
> Wasn't it disabled on standard frequencies ?
> 
> 73 ZP4KFX
> 
> 212100 Tx 752 ~ KH2F ZP4KFX GG14
> 212045 -13 0.1 2493 ~ ZP4KFX UN3GX MN83
> 212115 -12 0.4 695 ~ ZP4KFX KH2F -25
> 212130 Tx 752 ~ KH2F ZP4KFX R-12
> 212115 -10 0.1 2493 ~ ZP4KFX UN3GX MN83
> 212145 -9 0.3 695 ~ ZP4KFX RR73; SP9HZW  -22
> 212200 Tx 752 ~ KH2F ZP4KFX R-12
> ___
> 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] Frequencies list

[James Shaver]

Just create a different profile for DXPedition Mode use only. Details on that 
are in the manual. 

Jim S. 
N2ADV

> On Oct 31, 2018, at 7:34 AM, Pino Zollo  wrote:
> 
> Hi,
> 
> Having used F/H DXpedition mode a few times I feel the need to have two
> frequencies listsone for the normal operations and one for the
> DXpeditions.
> 
> In alternative we could have the mode renamed to FT8FH so, when
> selected, the program could go straight in H mode with a different
> frequencies list.
> 
> best 73
> 
> Pino ZP4KFX
> 
> 
> 
> ___
> 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] Question

[James Shaver]

This is people using JT65HF Image Controller. Google “easypal” - not my cup of 
tea and I think it’s silly but different strokes...

> On Oct 19, 2018, at 7:08 PM,   wrote:
> 
> I’m running RC#3 and I’m seeing this for the first time. Not sure if it is 
> unique to Ver 3.0 or just something ‘ve newer ran across in  earlier versions
>  
> 230415 -18 -2.2 2962 ~ W7QQF/IMAGE
>  
> 73
> Jim Parks  NY0J
>  
>  
> 
>   Virus-free. www.avast.com
> ___
> 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] Why73 - RRR or RR73 ---isn't it a waste of time ?

[James Shaver]

Yes, please. The whole “what constitutes a QSO” has been beaten to a bloody 
pulp -
The search function will uncover plenty on the subject from all sides. 

Jim S. 
N2ADV

> On Oct 15, 2018, at 7:47 PM, Gary  wrote:
> 
> End this NOW or I will drop off of this list.
> 
> Gary - W9BS
> 
> 
> -Original Message-
> From: W0MU Mike Fatchett [mailto:w...@w0mu.com] 
> Sent: Monday, October 15, 2018 7:38 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Why73 - RRR or RR73 ---isn't it a waste of time ?
> 
> That  is your opinion.  All that needs to happen is both sides receive 
> some data.  A confirmation is never required.  I never get that when 
> working DXpeditions so why would I expect it on FT8.  I never get 
> confirmations on my 60k contest contacts either.  Not sure what contests 
> you have been in.  CQ WW 599 04.  Done and gone, the DX does not and 
> does not have to send back anything. Stop trying to force your way on 
> others.  Thanks.
> 
> 
>> On 10/15/2018 2:58 PM, Bill Somerville wrote:
>>> On 15/10/2018 21:30, W0MU Mike Fatchett wrote:
>>> I don't need to see rr73 or 73.  I prefer making contacts instead of 
>>> finding reasons not to have contacts.  On CW or SSB working rare dx 
>>> you never get a 73 so why do you need it here? You don't!  Have fun 
>>> and log it.
>>> W0MU
>> 
>> Mike,
>> 
>> if you don't wait for an RR73 or RRR message (they serve the same 
>> purpose as conformations or receipt of a key piece of QSO information) 
>> then you don't know that your report to your QSO partner has been 
>> received, that is not a complete two-way QSO by any reckoning. No 
>> contest rules or award rules would accept such a QSO as valid. A 73 
>> message is not the same as a RR73 message, they are very different.
>> 
>> 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 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)

[James Shaver]

Can someone please block this user?  This is the 5th blank note from this 
person. 

> On Sep 25, 2018, at 6:25 AM, Анатолий  wrote:
> 
> ___
> 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)

[James Shaver]

Please stop sending empty messages to the dev list. 

> On Sep 23, 2018, at 11:15 AM, Анатолий  wrote:
> 
> ___
> 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 and disable TX after sending 73

[James Shaver]

Had that other ham read the documentation that goes along with the DXPedition 
Mode, he would realize that for “Hounds,” the transmit cycles is automatically 
disabled after a few cycles no matter what the operator selects as options. 

Jim S. 
N2ADV 

> On Sep 22, 2018, at 8:42 PM, DeYoung James via wsjt-devel 
>  wrote:
> 
> Greetings,
> 
> Thanks to Joe for taking his valuable time to respond. 
> 
> I didn't realize that the Enable TX should stop after each QSO.  Apparently 
> it does in V2.0.0-rc1.  However, tonight I am back running V.1.9.1.  I have 
> made 5 QSOs in a row on 160m with out having to do anything other than select 
> TX6 CQ after each QSO--the ENABLE TX glows red all the time just fine.  I am 
> that good! I guess I broke the software! I don't see a problem, however.  
> 
> "An automated QSO machine" I'm not even sure what that means I guess.  The 
> software user still has to perform functions to get things to dance.  If 
> there is a problem with user abuse of the software limiting the software/user 
> interface isn't the solution IMHO.  
> 
> Another HAM in my region suggested a potential abuse of the DXpedition mode 
> that I hadn't considered.  DXpedition is on say 30m and it is after midnight 
> local time.  HAM starts calling the DX and goes off to bed.  Wakes up fresh 
> in the morning and sees DXpedition in his log.  This could be a "problem". 
> 
> If I am sitting in the chair, interacting via the interface screen (could be 
> tested for) then don't turn the ENABLE TX button off after each QSO. 
> 
> My biggest interest is using WSJT-X and my stations equipment to make 
> contacts over circuits that are on "dead" bands, or where my antenna is a 
> compromise, etc.   
> 
> Thanks to the WSJT-X team for their efforts.
> 
> 73, Jim, N8OQ
> 
> 
> 
> 
> ___
> 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] WSJTX 2 RC1 - Feedback and Question

[James Shaver]

Lock TX and RX was removed back in the evolution of 1.8 (RC2 if memory serves). 
 

 

Jim S. 

N2ADV

 

From: Edfel Rivera [mailto:edfelj...@gmail.com] 
Sent: Wednesday, September 19, 2018 12:26 PM
To: WSJT software development
Subject: [wsjt-devel] WSJTX 2 RC1 - Feedback and Question

 

Hi:

 

Have tried FT8 2 and achieved QSO 20m.  Seems to work fine.  Some observations, 
notice lock TX and RX buttom no longer available?  Tried MSK144 but I know 
there is a fix so will wait RC2 to test more.  

 

Finally, I left program monitoring - open (was not present because upset 
stomach) and got the info below at band activity:

152900 -24 -0.1 1699 ~ 5W8NZS FZ3CJN R 25E AK

 

73'

 

Edfel

KP4AJ

 

p.d.

Thank you for keeping improving this formidable tool.

 

 

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

Re: [wsjt-devel] wsjt-X2 Crash report oh2fqv

[James Shaver]

>From Joe’s post yesterday about known bugs:

 

“1. If a message's first callsign contains only characters 0-9 and A-F it 

will be interpreted as a hexadecimal number.  The message will be 

transmitted and decoded as if the first callsign were telemetry data; 

the remaining parts are lost.  (Apologies to holders of all such 

callsigns... we'll fix this very soon.)

 

Jim S.

N2ADV

 

From: Jari A [mailto:oh2...@gmail.com] 
Sent: Wednesday, September 19, 2018 11:21 AM
To: WSJT software development
Subject: [wsjt-devel] wsjt-X2 Crash report oh2fqv

 

14.078

 

af4fa tx at 1496Hz , no locator with the call sign.

Tried to double click to the call AF4FA at band activity window, not copied.

I type call manually to DX Call field, set manually locator and I made Generate 
Std Msgs, it move it to TX1-5 fields.

This cause WSJT-X2 to transmit AF4FA only, no locator. I tried this 2 full 
times and at third I interrupt the Tx.
I find DC0HD calling CQ ( new call on band color )
DC0HD JO30 1523Hz 

Double click to hes call and immediate crash with short beep.

Windows 7, 64 bit - ts-590sg via CAT control

Best regards,

: Jari / oh2fqv

___
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

[James Shaver]

First thing I noticed was that when using the "RR73" in TX4 on 7.078 using
2.0, I haven't once had to repeat that part of the sequence in a couple
dozen contacts.  What a remarkable difference!

Jim S. 
N2ADV

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Monday, September 17, 2018 12:27 PM
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] WSJT-X FT-8 B v2.0-rc1 bug

[James Shaver]

Anything so new is going to flag on a lot of anti-virus programs.  

Us end-users need to be on our toes because we are still smarter than our
machines (for now).  

:)

Jim S. 
N2ADV

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, September 17, 2018 3:32 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X FT-8 B v2.0-rc1 bug

On 17/09/2018 20:24, Charles Otnott via wsjt-devel wrote:
> I have detected a bug installing
> the v2.0-rc1 software.
>
> After successful downloading of the
> v2.0-rc1 software the following problem
> was encountered:
>
> Problem: Firewall/virus software AVG free
> version reports v2.0-rc1 is a virus and
> will not allow installation.
>
> Solution: Halted AVG free version. The
> installation of v2.0-rc1 continued without
> incident. Restarted computer to allow
> AVG free edition to resume protection.

Hi Charles,

that is not a defect in the WSJT-X installer or software. AV products 
use many generic heuristics to flag potential malware, they normally 
have Gen or Generic in the so-called virus name. This is certainly a 
false positive and should be reported to AVG so they can update their 
malware signatures. There's nothing we can do about these annoying 
false-positives I'm afraid, it is the lot of low volume non-commercial 
software providers to suffer from these false accusations.

You should be able to flag the installer as safe (white list) with your 
AV software rather than completely disabling it during the install.

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 2.0 possible new mode/protocol

[James Shaver]

Agreed.  I’m baffled as to how such a comparison could even be attempted.  
Honestly, the comparison is more like apples to dairy cattle.  

 

People can (and do) operate without using a DX Spotting network and get along 
just fine.  Other than a DX Cluster being used to possibly know who the DX is 
at the other end in advance (which has been a “thing” since even before Packet 
Clusters”), there is no part of a an actual signal ever depending on the 
Internet.  Even using a Spotting Network for having a preview of who the op is 
chasing on the other end of a pileup requires listening first to make sure the 
spot was correct, legitimate, and that the DX was able to be heard when 
factoring in propagation.  Or, put another way, any “dependency” on the 
Spotting Network ends as the op still has the responsibility for listening 
first to make sure they can hear the spotted DX.  

 

If you want something that requires the Internet as part of these modes, might 
I suggest using that “IMAGE” and “HTML” silliness already going on.  

 

Jim S. 

N2ADV

 

From: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
Sent: Monday, September 10, 2018 6:16 AM
To: c_i...@inbox.ru; WSJT software development
Subject: Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

 

Igor,

If you believe that DX-Spotting is equivalent to internet assisted sensitivity 
enhancement, then there is no point in further discussion.

 

Apples and oranges, at the very least.

N0AN

Hasan

 

 

On Mon, Sep 10, 2018 at 12:58 AM Игорь Ч via wsjt-devel 
 wrote:

Hello Laurie,
.
DX cluster usage is an Internet dependant DX-ing and contesting, it is accepted 
by community and organizers.
.
73 Igor UA3DJY

Date: Mon, 10 Sep 2018 08:39:13 +1000
From: "Laurie, VK3AMA" <_vk3a...@vkdxer.net>
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol
Message-ID: 
Content-Type: text/plain; charset=windows-1252; format=flowed

IMO, it is very likely that an Internet dependant mode will not be 
accepted for award purposes or by Contest organisers.

de Laurie VK3AMA

___
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 2.0 possible new mode/protocol

[James Shaver]

One more concern I have in addition to the increasing popularity of portable 
operations outside of the reach of an Internet connection is the fact that 
while it may be easy to forget, there are still a significant number of Amateur 
Radio ops world-wide for whom Internet is either unreliable, prohibitively 
expensive, or both.  Anything that relies on the Internet will also, by 
default, exclude them from full use.  

 

Jim S.

N2ADV

 

From: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
Sent: Saturday, September 8, 2018 7:32 PM
To: WSJT software development
Subject: Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

 

Bravo, George!

 

Internet help with the decode? That's downright silly. If we are going to use 
the internet to replace even a portion of  the performance of rf, heck why 
bother with rf at all, and we can have infinite sensitivity?

 

Hasan

 

On Sat, Sep 8, 2018, 6:13 PM George J Molnar  wrote:

While it probably is a remote possibility that the WSJT-X team is contemplating 
adding internet-based linkages, I want to agree with N2ADV and emphatically say 
“no!” to any ham radio communications protocol that relies on anything but ham 
radio to work effectively. 

 

Even in this day of skimmers and spotting networks, automatic rotators, and 
auto-sequenced contacts, the contact itself is still a radio contact, and 
should remain so in its entirety.

 

 

George J Molnar

Arlington, Virginia, USA

KF2T   -   FM18lv

 

 

 

 





On Sep 8, 2018, at 6:38 PM, James Shaver  wrote:

 

Yes but my previous question about Internet usage still stands: When I am 
sitting in a park or out on a snowmobile trail with my KX3 and my laptop using 
a GPS for time sync since there’s no cell reception there, anything that relies 
on the Internet will be basically useless to me.  Why would we aim to exclude a 
growing number of such users like me?  Perhaps I’m misunderstanding.  

 

Jim S. 

N2ADV

 

___
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 2.0 possible new mode/protocol

[James Shaver]

Yes but my previous question about Internet usage still stands: When I am 
sitting in a park or out on a snowmobile trail with my KX3 and my laptop using 
a GPS for time sync since there’s no cell reception there, anything that relies 
on the Internet will be basically useless to me.  Why would we aim to exclude a 
growing number of such users like me?  Perhaps I’m misunderstanding.  

 

Jim S. 

N2ADV

 

From: Игорь Ч via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Saturday, September 8, 2018 3:51 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Игорь Ч
Subject: Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

 

Hello Joe and all,
.
Most of questions raised on this subject can be solved via HLR/VLR database 
server usage, where visitor location register can match to the specific HF band 
where callsign, frequency, hash of the message being transmitted, protocol and 
code rate can be stored, callsign hash can be calculated from callsign in the 
VLR server. 
.
Hash conflict of two or more callsigns on the same band can be solved as well 
via VLR connection using frequency window and other possible criteria.
.
Users who have not Internet connection can still operate FT8 via default 
coder/decoder with limited sensitivity to the current FT8 decoder value, while 
users who have connection to the VLR can get maximum performance via variable 
protocol and code rate.
.
Current implementation of the FT8 special messages(i3bit==1) does not allow to 
decode callsign from the hash if this callsign was not decoded in the previous 
message. Special messages are being used in MSHV software as effective way to 
increase QSO rate in the common FT8 bands, with extended FT8+ protocol the gap 
in software compatibility may increase and VLR server connection would let us 
to resolve such issues.
.
The best way to go forward is a sharing FT8+ flexibility to the Internet 
connection and limiting radio interface traffic to callsign and report 
transmission, the same QSO radio exchange protocol have been in use for a while 
in DXpeditions and contests where in CW callsign 'hash' can be recognized by 
human brain from multiple signals per frequency, speed and timing criteria.
.
73 Igor UA3DJY

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

Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

[James Shaver]

When I am sitting in a park or out on a snowmobile trail with my KX3 and my 
laptop using a GPS for time sync since there’s no cell reception there, 
anything that relies on the Internet will be basically useless to me.  Why 
would we aim to exclude a growing number of such users like me?  Perhaps I’m 
misunderstanding.  

 

Jim S. 

N2ADV

 

From: Игорь Ч via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Friday, August 31, 2018 6:33 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Игорь Ч
Subject: Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

 

Hello Joe,
.
It was excellent example with the WSPR QSO, just thought we can get additional 
FT8 gain if some messages at QSO will be transmitted as 'hash hash' / 'call 
hash' / 'hash call'   instead of callsigns.
.
Yes, there is a trade off between the sensitivity and protocol flexibility. 
Probably we can add more flexibility if some information will be passed over 
Internet, for instance free text messages and GRID, it will spare more bits 
toward sensitivity on the radio interface.
.
Other option is to pass some message's hash over Internet while transmitting 
this message via radio interface, it will also spare some bits toward 
sensitivity.
.
Proposed by Take JA5AEA variable code rate: we can pass information on the code 
rate over Internet at the QSO, hence appropriate decoder can be used per each 
message. The same approach can be implemented with the variable protocol where 
protocol details, for instance i3bit, can be broadcasted over Internet.
.
Leaving callsigns(hash) and report to the radio interface and combining radio 
interface messages and traffic over Internet in the FT8+ protocol we can marry 
JT65/JT9 sensitivity and FT8 rate of QSO.
.
I do not believe any new mode outside WSJT-X is a good idea, it would be more 
efficient to keep going in the common direction.
.
73 Igor UA3DJY

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

[James Shaver]

I’ve literally only heard them with FT8 (still haven’t gotten them in the log 
because I could only hear them for about an hour on 20 and an hour on 30 at -20 
and below) – I’ve heard the pileup for CW and SSB but can’t hear Baker at all.  
If that trend continues, my ONLY chance of getting them in the log will be FT8. 
 To me, that’s pretty darn cool as I otherwise would not have a shot.  

 

Jim S. 

N2ADV

 

From: Glen Brown [mailto:210g...@gmail.com] 
Sent: Saturday, June 30, 2018 6:49 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Observation on Expedition Mode

 

In my opinion FT8 has been working great in its first outing.  And it's proven 
robust enough to keep working when some operators are not set up correctly.  
Just RTFM and you'll do well.  

And don't be threatened by a new way of operating.  As Joe points out, work 
them CW and SSB when you can, FT8 when you can't.  This is a great opportunity 
for low power and antenna-limited stations to get a new one.  

Kudos to the FT8 development team.

73, Glen W6GJB

 

On Sat, Jun 30, 2018 at 11:56 AM, Joe Taylor  wrote:

On 6/30/2018 10:14 AM, Black Michael via wsjt-devel wrote:

... I noticed the the Baker team gave a lukewarm endorsement of FT8 on their 
news update ...


I do not consider their endorsement of FT8 to be lukewarm, at all.

Currently they have uploaded 12,319 QSOs to ClubLog:

CQ   4,735
SSB  4,507
FT8  3,077
---
12,319

One of their intentions was to run CW amd SSB when band conditions are good, 
when QSO rates can be highest.  FT8 works well even in poorer conditions.  I 
believe they are happy with their decision to use FT8 and its DXpedition Mode.

They would be even happier if more people used the correct software and 
followed the Hound operating instructions, preferably with a dollop of common 
sense.

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

Re: [wsjt-devel] Observation on Expedition Mode

[James Shaver]

There are several people who have outright said they refuse to use 1.9.1 (or 
WSJTX in general) and/or that they refuse to use DXPedition Mode because they 
“don’t agree with being forced to use it.”  I’m willing to bet some of the 
people causing QRM fall into that category, as well, for some odd reason.  

 

Jim S.

N2ADV

 

From: Gary Kohtala - K7EK via wsjt-devel 
[mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Saturday, June 30, 2018 2:26 PM
To: 'WSJT software development'; John Zantek; Black Michael
Cc: Gary Kohtala - K7EK
Subject: Re: [wsjt-devel] Observation on Expedition Mode

 

The Baker Island DXpedition has brought out the very worst:  Stations calling 
blind for hours when KH7Z is not even on FT8, incessant calling below 1000 hz, 
calling the wrong call sign (KH7V), calling in the wrong time slot, etc. 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. I came 
close to completing for an ATNO on 30m but sadly, I never got his RR73 and did 
not go into their log. So, I continue to fight the 

uninformed and apparently clueless hoards that have descended upon the bands. 
And of course throw in bad propagation, low power, 

and a less than ideal antenna system and the odds of making the Q are even 
lower. Oh well. There is still time. I'd love to get

KH1 for that ATNO on any mode, any band.  

 

Best regards,

 

Gary, K7EK

 

Radcliff, KY (EM77at)

 

--
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] Ft 8 in Exhibition Mode

[James Shaver]

Hey Jim – happy to post it there if someone has it handy to provide.  

 

Jim S. 

N2ADV

 

From: W4TMO via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Thursday, March 22, 2018 8:44 PM
To: WSJT software development; Richard Stanley
Cc: W4TMO
Subject: Re: [wsjt-devel] Ft 8 in Exhibition Mode

 

There's over 7K members on the Facebook group.  Maybe post upcoming DXpeditions 
under the "Events" heading along with dates and frequency(s) that'll be used.  
The "Events" heading is always at the top (on the left) so users won't have to 
search thru all the postings.

 

Maybe a link to any webpage posted by  DXpedition too.

 

Probably a good idea to go thru periodically and delete events that have passed 
so upcoming events are more evident.

 

73

Jim

 

W4TMO

USAF Retired

 

 

On Thursday, March 22, 2018, 6:51:18 AM EDT, Richard Stanley via wsjt-devel 
 wrote: 

 

 

 

Anybody could see this was going to happen I would be surprised if anybody is 
shocked Smile

 

Richard G7OED

 

From: Ray Jacobs 

Sent: Wednesday, March 21, 2018 10:16 PM

To: wsjt-devel@lists.sourceforge.net 

Subject: [wsjt-devel] Ft 8 in Exhibition Mode

 

You were right they were on the same frequency as regular ft 8 instead of 
another frequency, somehow they will have to announce what frequency they are 
on. But how do they get the word out?

Sent from AOL Mobile Mail

  _  

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

 

 


 

 

Virus-free.  

 www.avast.com

--
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] Split mode ft 8

[James Shaver]

And the “normal” 17 meter frequency as well with the same results… 

 

From: James Shaver [mailto:n2...@windstream.net] 
Sent: Wednesday, March 21, 2018 5:59 PM
To: 'WSJT software development'
Subject: RE: [wsjt-devel] Split mode ft 8

 

Unfortunately, they’re using the DXPedition mode on the “normal” 15 meter 
frequency and ops are inadvertently stomping all over several QSO’s in 
progress.  I witnessed several busted contacts and had a few myself as a 
result. 

 

From: Ray Jacobs [mailto:rjacobs...@verizon.net] 
Sent: Wednesday, March 21, 2018 4:11 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Split mode ft 8

 

Just worked PJ-5/SP9FIH in the hound mode!  Tuned up past 1000 he was on 274 .
Now I put my rig on fake it.  The program says it advised me it should be in dx 
 exbition mode! 
So it worked for me and others  no problem. 

Sent from AOL Mobile Mail

--
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] Split mode ft 8

[James Shaver]

Unfortunately, they’re using the DXPedition mode on the “normal” 15 meter 
frequency and ops are inadvertently stomping all over several QSO’s in 
progress.  I witnessed several busted contacts and had a few myself as a 
result. 

 

From: Ray Jacobs [mailto:rjacobs...@verizon.net] 
Sent: Wednesday, March 21, 2018 4:11 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Split mode ft 8

 

Just worked PJ-5/SP9FIH in the hound mode!  Tuned up past 1000 he was on 274 .
Now I put my rig on fake it.  The program says it advised me it should be in dx 
 exbition mode! 
So it worked for me and others  no problem. 

Sent from AOL Mobile Mail

--
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: dissapointed somehow

[James Shaver]

Hi Bill - they're not just "testing" they're trouncing on existing digital
mode watering holes without any real regard to anyone around them.  The lack
of consideration to others is simply astounding.  

I've said my peace on this. 

Jim S. 


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, March 14, 2018 8:13 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] DXpedition mode: dissapointed somehow

On 14/03/2018 10:24, James Shaver (N2ADV) wrote:
> TY7C should not have even been using DXPedition Mode. 

Hi Jim,

why not?

https://ty2018dx.wordpress.com/

and check their QRZ.COM page.

They are not some random OM playing with FT8 DXpedition mode on the normal
FT8 sub-bands. Benin may not be in the top 10 most wanted list but that's
fine. If a DXpedition team want to try out FT8 DXpedition mode and are fully
aware of the caveats about making sure that callers know how to work them
etc. then their brave attempt to try out an as yet unpolished feature of
WSJT-X is fine. They may lose some QSOs as a result but they may well
provide valuable feedback. It is a little unfortunate that their operation
dates coincide with a version of WSJT-X
(v1.9.0-rc2) that has several known defects, picked up in the public tests
recently, that have been fixed but not yet released.

With respect to Uwe's disappointment, I'm not sure if the F6KOP team have
limited power or are just starting cautiously with only one Tx slot. They
can still potentially complete 120 QSOs/hr with one slot. 
Note that using N slots greater than one means reduced power per QSO with
signals being ~14dB down with N slots equal to five. I note in their blog
post that they are having success with FT8 DXpedition mode but find they are
hearing callers better than they are being heard, possibly as a result of
trying N slots > 1.

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

Re: [wsjt-devel] DXpedition mode: dissapointed somehow

[James Shaver]

Besides the fact that it has been stated at least a dozen times by the
Development Team that the functionality is not yet ready for use, the
reasons are clearly outlined here in this group.  Search the group for the
past week and you'll have your answer.  Also, take a look at the laundry
list of issues you noted in your original e-mail, many of which were
discussed at length after the public test of the DXPedition Mode and these
all point to the fact that the DXPedition Mode is not ready for use beyond
just the occasional public tests.  

Jim S. 
N2ADV

-Original Message-
From: jarmo [mailto:oh1...@nic.fi] 
Sent: Wednesday, March 14, 2018 7:24 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] DXpedition mode: dissapointed somehow

Wed, 14 Mar 2018 06:24:30 -0400
"James Shaver (N2ADV)"  kirjoitti:

> TY7C should not have even been using DXPedition Mode. 
> 
> Jim S. 
> N2ADV. 
And why not?

For me TY is quite DX...

Jarmo


--
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] FT8 DX-ped mode

[James Shaver]

Is there a reason TY7C chose a well known PSK watering hole for this "test"?
That probably made the PSK users quite angry...

Jim S.
N2ADV

-Original Message-
From: jarmo [mailto:oh1...@nic.fi] 
Sent: Monday, March 12, 2018 4:39 AM
To: WSJT software development
Subject: [wsjt-devel] FT8 DX-ped mode

Today got first tests from TY7C. They worked "some" qsos with pedition mode.
Seems, that there is big need to tell people how it does work.
Was quite mess with stations, who tried from same Hz. Most of those stations
were trying under 1000Hz. TY7C told that they are FOX, still mess... And
TY7C was working 14070, so all callers should have known.

So, translations to several languages, how this work is must.
Google translator works quite well, so might be good idea add link there.
My first HOUND qso, shows that I need some more practice :) too.

Jarmo


--
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] WSJT-X 1.9.0 rc2 Waterfall

[James Shaver]

It took me a few days to get it the way I wanted it but I like it way better.  

Jim S. 
N2ADV

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, March 7, 2018 11:27 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 1.9.0 rc2 Waterfall

On 07/03/2018 16:21, Ron Schwartz wrote:
> The 1.9.0 rc2 waterfall now appears ‘smeared’ and weak traces are not 
> as visible as earlier versions (see attached).  Is this an intentional 
> change?

Hi Ron,

it has been changed, the intent was to improve the visibility of weak signals. 
Please try adjusting the sliders to your liking. Once you get what appears to 
be a good trace try playing back the recorded .WAV file in version v1.8.0 with 
your old settings and compare. If you still think the new waterfall is worse 
please send us the .WAV file.

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

Re: [wsjt-devel] Timer

[James Shaver]

Thanks, Steve and Joe both - my sleep-deprived brain completely failed to 
register that part.  

Jim S. 

-Original Message-
From: Steven Franke [mailto:s.j.fra...@icloud.com] 
Sent: Wednesday, March 7, 2018 11:13 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Timer

Hi Jim, 

Check out item 12 in the Hound instructions:

“12. After you receive a signal report from Fox, WSJT-X will automatically send 
your next transmission as message Tx 3 (“R+rpt”) at a randomly chosen frequency 
between 300 and 900 Hz. Note that WSJT-X will send this message even if Enable 
Tx is disabled, and even if you have not called Fox for several Tx sequences. 
If you have stopped calling Fox because you will be leaving the rig unattended, 
you should quit WSJT-X or disable Hound mode in order to avoid the possibility 
of unwanted transmissions."

It is important to understand this behavior. It means that, in most cases, you 
should not just leave your rig on and monitoring the DX after you have stopped 
paying attention, as you could be in for a surprise when your rig springs to 
life and starts TXing.

Steve K9AN

> On Mar 7, 2018, at 10:05 AM, James Shaver  wrote:
> 
> Yep, twice the timer had expired on me right as the “Fox” called me and I had 
> to scramble. 
>  
> Jim S. 
> N2ADV
>  
> From: Bill Turner via wsjt-devel 
> [mailto:wsjt-devel@lists.sourceforge.net]
> Sent: Wednesday, March 7, 2018 11:03 AM
> To: WSJT Software Development
> Cc: Bill Turner
> Subject: [wsjt-devel] Timer
>  
> Great job with the test last night.  I did find the 2 minute timer to be a 
> real pain, however. I understand you do not want a robot operation, but a 5 
> or 10 minute timer would be less frustrating.
>  
> When the software shuts off the Enable TX, how do we know that we are still 
> on the correct sequence when we click on Enable TX?  I noticed some comments 
> about folks calling on the wrong sequence last night.
>  
> Again, thanks for the effort in the test.
>  
> Bill Turner, W4WNT
> --
>  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] Timer

[James Shaver]

I missed that in the documentation - thanks for that, Joe!  My cat was very put 
out when I made a mad dash for the mouse ;)

I'll apologize to her later. 

Jim S. 
N2ADV

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Wednesday, March 7, 2018 11:09 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Timer

Jim --

I don't think you had to scramble.  If Fox calls you, your Tx3 message will be 
sent (somewhere in 300-900 Hz), even if Tx Enable is not engaged.
-- Joe


On 3/7/2018 11:05 AM, James Shaver wrote:
> Yep, twice the timer had expired on me right as the “Fox” called me and 
> I had to scramble.
> 
> Jim S.
> N2ADV
> 
> *From:*Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
> *Sent:* Wednesday, March 7, 2018 11:03 AM
> *To:* WSJT Software Development
> *Cc:* Bill Turner
> *Subject:* [wsjt-devel] Timer
> 
> Great job with the test last night.  I did find the 2 minute timer to be 
> a real pain, however. I understand you do not want a robot operation, 
> but a 5 or 10 minute timer would be less frustrating.
> 
> When the software shuts off the Enable TX, how do we know that we are 
> still on the correct sequence when we click on Enable TX?  I noticed 
> some comments about folks calling on the wrong sequence last night.
> 
> Again, thanks for the effort in the test.
> 
> Bill Turner, W4WNT
> 
> 
> 
> --
> 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] Timer

[James Shaver]

Yep, twice the timer had expired on me right as the “Fox” called me and I had 
to scramble. 

 

Jim S. 
N2ADV

 

From: Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Wednesday, March 7, 2018 11:03 AM
To: WSJT Software Development
Cc: Bill Turner
Subject: [wsjt-devel] Timer

 

Great job with the test last night.  I did find the 2 minute timer to be a real 
pain, however. I understand you do not want a robot operation, but a 5 or 10 
minute timer would be less frustrating.

 

When the software shuts off the Enable TX, how do we know that we are still on 
the correct sequence when we click on Enable TX?  I noticed some comments about 
folks calling on the wrong sequence last night.

 

Again, thanks for the effort in the test.

 

Bill Turner, W4WNT

--
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] Public test of FT8 DXpedition mode March 6-7

[James Shaver]

It also might not be a bad thing if some well-meaning but otherwise
uninformed ops running 1.8 wander into the "pileup" as it may help simulate
real-world conditions where this may also happen with more frequency.
Though they may not decode the "fox" I've seen any number of times where
people will start calling a "DX" even though they can't hear them so I'd
expect this will happen during the public test as word spreads.  It'll help
add legitimacy to real-world QRM.  

Just my 2 cents, feel free to keep the change :)

Jim S. 
N2ADV

-Original Message-
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 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?

Only Fox sends a new type of message -- that is, one not supported in WSJT-X
v1.8.0.

I hope it's clear in the FT8 DXpedition Mode User Guide
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

... that Fox will respond only to

1. Initial calls like line 2 in the User Guide's example sequence (top of
page 2).  These messages must be received above 1000 Hz; and

2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
signal report.  These must be received between 300 and 900 Hz.

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

Re: [wsjt-devel] Test

[James Shaver (N2ADV)]

I got the note, Mike. 

> On Feb 17, 2018, at 3:50 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Testing if email group is working yet.
> 
> 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
--
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] WSJT-X issue with Dark QT themes

[James Shaver]

Thanks, Bill! 

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, January 23, 2018 10:11 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X issue with Dark QT themes

On 23/01/2018 15:01, James Shaver wrote:
> Joe, can we use the 1.7.1 dev branch on air?  I've been building along the
1.8.1 branch instead because of an earlier note you had out there.
>
> Thanks!
>
> Jim S.
> N2ADV

Hi Jim,

small changes like this one are being merged to the v1.8 branch fairly
promptly if they are deemed defects, and this one would qualify as without
it the UI is rendered unreadable in some circumstances. Whether a v1.8.1
release will happen or a v1.9.0 from the development branch is yet to be
determined although the latter is looking more likely as there are some
deadlines associated with work in the development branch as yet incomplete.

If you see a change in the development branch that is small and looks
helpful you can always try merging it into you v1,8 branch workspace. 
For example the change Joe has made is r8431 in the development branch, you
can merge that into your v1.8 workspace with the following command from the
root of your svn workspace:

svn merge -c 8431 ^/branches/wsjtx

Just be aware that once the merge is in place you then have locally edited
files that will block further changes from the v1.8 branch synchronizing
unless you resolve the potential conflicts or revert the changes before
updating.

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

Re: [wsjt-devel] WSJT-X issue with Dark QT themes

[James Shaver]

Joe, can we use the 1.7.1 dev branch on air?  I've been building along the 
1.8.1 branch instead because of an earlier note you had out there. 

Thanks!

Jim S. 
N2ADV

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Tuesday, January 23, 2018 9:57 AM
To: WSJT software development; AJ Fite
Subject: Re: [wsjt-devel] WSJT-X issue with Dark QT themes

Hi Al,

Thanks for the good suggestion to improve usability of WSJT-X with dark themes. 
 I've put your changes into the development branch code.

-- 73, Joe, K1JT

On 1/23/2018 2:09 AM, AJ Fite wrote:
> Hello WSJT-X devs!
> 
> This could be considered a bug so I'm going to post this like a bug report:
> 
> Pertinent System Info:
> Program Version: 1.8.0
> OS: Arch Linux (x64) [though this should be universally reproducible]
> DE: KDE Plasma
> QT Theme: Breeze-Dark
> 
> Reproduction:
> Use a dark theme that sets font colors to white, I use the default 
> Breeze-Dark QT theme
> 
> You can evidently see the behavior pretty clearly in this image: 
> https://i.imgur.com/NENfJLj.png 
> 
> It appears that the background for certain text entry box backgrounds 
> are hard coded to white rather than using the defalt theme text box 
> background causing light fonts to be almost unreadable.  Optimally 
> they should be using whatever the QT equivalent of inherit background 
> color is OR if they could be set in a similar way to the other 
> background colors that would also be perfect.
> 
> I've pinpointed the two most troublesome parts of the code, making the 
> changes I outline below impoves usability massively on dark themes, I 
> was working off the WSJT-X 1.8 branch of the SVN:
> 
> displaytext.cpp line 186 changed from:
> QColor bg {Qt::white};
> to:
> QColor bg {Qt::transparent};
> 
> mainwindow.cpp line 4508 changed from:
> p.setColor(QPalette::Base,Qt::white);
> to:
> p.setColor(QPalette::Base,Qt::transparent);
> 
> In theory these changes shouldn't effect light themes as their 
> backgrounds are already white or a light color, they significantly 
> help dark themes.
> 
> 73
> AJ Fite N7AJF
> 
> 
> 
> 
> --
>  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] Mystique?

[James Shaver (N2ADV)]

Several topics on this in the group that can be found via a brief search. 

People are sending images over the internet to each other via JT65HF Image 
Controller and the “/Image” is the prompt to go download the image. 

(This is probably less a development question and one for the WSJT-Group 
reflector BTW)

> On Jan 19, 2018, at 6:34 AM, jarmo  wrote:
> 
> What is this, what I can see decoded, namely some CALL/IMAGE?
> Ie. example xx0xx/image and also sometimes xx0xx/cmd?
> Using wsjtx-1.8,0 in Fedora 26..
> 
> Jarmo
> 
> --
> 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] Split frequency logging

[James Shaver]

It wasn't "too long ago" when the spark people grumbled about CW.  Then the
CW people grumbled about AM Phone.  Then the AM Phone people grumbled about
SSB.  

 

If you don't like it, don't do it - stick with CW and SSB, they aren't going
away anytime soon and a good number of us here enjoy those as well as these
modes.  

 

This isn't really a software development question, however and this list is
for development discussions.  

 

Jim S. 

N2ADV

Proud WSJT-X user, CW user, phone user, and any number of modes without
grumbling about the others. 

 

From: Karl Barth [mailto:df5...@darc.de] 
Sent: Wednesday, November 22, 2017 8:42 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging

 

Dear all,

it is not too long ago and we commonly used to run our qso's in person
(cw/ssb) and log on paper.

Do we realy need to get all radio contacts fully automated?

Just  go to the shack in the morning and activate the PC with all add-on
automated software?

 I got a radio licence, not my PC -

73,
Charly, DF5VAE

--
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] WSJTx ver 1.8-rc3 problem

[James Shaver]

Is there some reason you’re using RC3 and not the latest version?  I’d 
recommend going that path first.

 

Jim S. 
N2ADV

 

From: Unni Tharakkal [mailto:unnitharak...@gmail.com] 
Sent: Saturday, November 18, 2017 7:05 AM
To: WSJT software development
Subject: [wsjt-devel] WSJTx ver 1.8-rc3 problem

 

Dear All

 

I was using the WSJTX ver. 1.8 rc3 peacefully with some problem with Hamlib.

 

So I unstalled everyting and installed again Now my problems are

 

1. the Hamlib doesn't connect  the program. The errors I am getting are

 

2. Hamlib error : I/O error while opening connection  to rig

 

3. Communication timed out while getting current frequency

 

 

I tried resetting the configuration No use

 

Tried to update Ham lib  - could not do it (How hamlib 68bit ver. can be 
updated I am using Win10 68 bit)

Then I tried to get it connected through Omnirig the error report is

 

Omini Rig : Initialization timed out

 

My set up is FT 857D with CH340 (CT62) rig control and a BY make Prolific PTT 
control

 

Using Win 10 Acer i3 lap top computer

 

Where I have gone wrong Please help. There is lot of opening to my side from 
Europe and Russia

 

With regards and 73s

 

Unni

VU2TE

--
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] WSJTx ver 1.8-rc3 problem

[James Shaver]

Is there some reason you’re using RC3 and not the latest version?  I’d 
recommend going that path first.

 

Jim S. 
N2ADV

 

From: Unni Tharakkal [mailto:unnitharak...@gmail.com] 
Sent: Saturday, November 18, 2017 7:05 AM
To: WSJT software development
Subject: [wsjt-devel] WSJTx ver 1.8-rc3 problem

 

Dear All

 

I was using the WSJTX ver. 1.8 rc3 peacefully with some problem with Hamlib.

 

So I unstalled everyting and installed again Now my problems are

 

1. the Hamlib doesn't connect  the program. The errors I am getting are

 

2. Hamlib error : I/O error while opening connection  to rig

 

3. Communication timed out while getting current frequency

 

 

I tried resetting the configuration No use

 

Tried to update Ham lib  - could not do it (How hamlib 68bit ver. can be 
updated I am using Win10 68 bit)

Then I tried to get it connected through Omnirig the error report is

 

Omini Rig : Initialization timed out

 

My set up is FT 857D with CH340 (CT62) rig control and a BY make Prolific PTT 
control

 

Using Win 10 Acer i3 lap top computer

 

Where I have gone wrong Please help. There is lot of opening to my side from 
Europe and Russia

 

With regards and 73s

 

Unni

VU2TE

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