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] 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] 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] 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] 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] Pulled back on 73

[James Shaver (N2ADV)]

Thanks, Bill!  I typically keep the box unchecked myself when calling CQ but I 
know there are folks who find it handy. 

Appreciate the peek!

Jim S. 
N2ADV

> On Aug 3, 2017, at 9:32 PM, Bill Somerville <g4...@classdesign.com> wrote:
> 
>> On 04/08/2017 02:22, James Shaver (N2ADV) wrote:
>> I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he 
>> responded to me, we went through the sequence, he sent his 73 and then moved 
>> off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his TX 
>> back to where I was causing him to accidentally start calling CQ where he 
>> had just answered me. Would it be simple to have the TX not be pulled back 
>> upon receipt of the 73?  I know he could have unchecked "Call 1st" and 
>> avoided being pulled back but then if someone had answered him after calling 
>> CQ, he would have to manually answer.
> 
> Hi Jim,
> 
> I can reproduce that behaviour if I have him with "Lock Tx=Rx" checked. The 
> more use cases I test with auto-sequencing the more I am growing to dislike 
> "Lock Tx=Rx".
> 
> I will see if I can work out how to stop this sort of thing happening.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

[wsjt-devel] Pulled back on 73

[James Shaver (N2ADV)]

I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he 
responded to me, we went through the sequence, he sent his 73 and then moved 
off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his TX back 
to where I was causing him to accidentally start calling CQ where he had just 
answered me. Would it be simple to have the TX not be pulled back upon receipt 
of the 73?  I know he could have unchecked "Call 1st" and avoided being pulled 
back but then if someone had answered him after calling CQ, he would have to 
manually answer. 

Just curious. :)

73!
Jim S. 
N2ADV

--
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] About qrm

[James Shaver (N2ADV)]

There is a long standing myth that power by itself creates "poor signals" which 
has, unfortunately, created a vast legion of "power cops" who have taken it 
upon themselves to chastise everyone on their waterfall with a strong signal, 
assuming that everyone that is strong or has what appears to be a "bad signal" 
are automatically running "too much power."  

I received an email from one such individual just a few weeks ago chastising me 
for being a "lid running a linear and wrecking the band" along with other 
choice phrases and showing me a screen shot of my JT9 signal at +18dB. 

I was running 10 milliwatts and had an IMD of -35dB. 

Power is only the tiniest fraction of the equation.  

If ops spent more time adjusting their receive settings instead of worrying 
about how much power someone else is running, there would be a lot more happy 
operators out there.  

Remember that the difference between 5 watts and 100 watts is only about 16 dB 
assuming an ideal antenna in free space.  It's actually far less in real world 
applications.  

Don't misunderstand: you should only run as much power needed to make the 
desired contact (I seem to recall that being a question on my Technician Class 
License exam) and if you're calling CQ, make sure your reach does not exceed 
your grasp lest you become an "alligator" with more mouth than ears. 

73,

Jim S. 
N2ADV

> On Aug 3, 2017, at 3:29 PM, jarmo  wrote:
> 
> Seems, that these modes are more and more becoming
> HIGH power modes, what consumes lots of qrm.
> 
> Could there be possibility to add, when someone
> opens WSJTX, first window shows you "FORGET LINEAR"
> and you have to agree, before wsjtx opens.
> 
> That does not help much, but shows those guys
> with linears, that, linear means QRM...
> 
> Seen signals from abt 2000 km, with rprt +17...
> That's not propagation...
> 
> 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] 72-Bit Contest Mode, Rover support

[James Shaver (N2ADV)]

Yep that's what Neil and I were seeing when we tested it yesterday. We kept 
exchanging call and grid in an endless loop :)

Jim S
N2ADV 

> On Aug 2, 2017, at 10:08 AM, Joe Taylor  wrote:
> 
> Thanks, Charlie.  We'll need to look at that.  -- Joe, K1JT
> 
>> On 8/2/2017 10:03 AM, char...@sucklingfamily.free-online.co.uk wrote:
>> Hi Joe
>> On a loop-back test it looks to me like the autoseq does not kick in until
>> it has received a [call call R grid message]. Then it progresses to RRR
>> and 73 messages. The only way I could trigger that was to switch off
>> autoseq on the sending instance and manually send the R message.
>> Else for me it sticks at sending [call call grid].
>> Not sure if this was what Neil was seeing.
>> Charlie
>>  > Hi Neil,
>>> 
 On 8/1/2017 4:23 PM, Neil Zampella wrote:
 Hi Joe,
 
 I was testing with in r7976 and was wondering if the contest mode was
 auto sequence enabled.  Apparently it isn't ??  Is that right.   Just
 want to make sure, as the exchange had to be manually advanced.
 
 Neil, KN3ILZ
>>> 
>>> Please follow instructions in the User Guide and address queries about
>>> WSJT-X to wsjtgroup or wsjt-devel.  I am copying this reply to wsjt-devel.
>>> 
>>> I have not yet had a chance to test the 72-bit contest mode of FT8 on
>>> the air.  However, I had thought that auto-sequencing should work as
>>> expected.  Please elaborate on why you think it does not.
>>> 
>>> As always, if you think you have uncovered a bug, it's best to provide a
>>> series of steps that will reproduce the bug.
>>> 
>>>-- 73, Joe, K1JT
>>> 
> On 7/28/2017 1:33 PM, Joe Taylor wrote:
> Hi all Beta Testers,
> 
> In code revision r7969 the WSJT-X development branch supports "Contest
> Mode" in FT8 as well as MSK144.  This mode is designed for NA VHF+
> contests in which the required exchange is a 4-character grid locator.
> 
> Contest Mode is enabled by checking the box labeled "FT8 and MSK144
> Contest Mode" on the *Settings -> Advanced* tab.  When that has been
> done by both QSO partners, QSOs in the following formats are supported:
> 
> 
> 
> Please note that these features do not (yet) take advantage of the
> enhanced 75-bit messages possible in FT8.  We are currently working on
> uses for the extra 3 bits that will provide support for other contest
> types, perhaps including RTTY-like  and EU VHF+ contests, as well as
> improved support for messaged containing compound callsigns.
> 
> If you are able to build WSJT-X r7969 and to find a partner with whom
> you can test these new features, please send reports to this list.
> 
> -- 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
> 
> --
> 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] AutoSeq Question

[James Shaver (N2ADV)]

Hi, Tim - it prevents endless sending of "73" - someone could inadvertently 
forget to disable their TX and get up to get a cup of coffee (or, uh, get rid 
of said coffee), pet the cat, feed the kids, etc and keep sending 73 over and 
over. I disable Auto after my report goes out and switch to manual to prevent 
the situation you describe :)

73!
Jim S. 
N2ADV

> On Jul 18, 2017, at 10:56 AM, Tim Carlson  wrote:
> 
> Hi All,
> 
> I have a general question about Auto Seq when answering a CQ call.
> 
> Out of 78 completed QSO’s with FT8 and Auto Seq, at least a dozen of them 
> (when I’m answering a CQ) end with me sending “73” which disables my Auto Tx, 
> then receiving another “RRR”.  I have to then scramble and click “Enable Tx” 
> again, which usually isn’t very timely because I’m in my logbook, looking up 
> the QRZ page of my QSO partner, or looking at a map of their location.
> 
> Is there a reason that Auto Tx is disabled on my “73” rather than on receipt 
> of the other person’s “73”?  I don’t want to leave my partner endlessly 
> calling “RRR”.
> 
> Thanks!
> 
> -Tim KD0GYG
> --
> 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 and "Call 1st"

[James Shaver (N2ADV)]

That's built into the wetware (brain matter) of the person controlling the 
program :)

> On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:
> 
> One feature I'd like to see is if you answer a CQ, and the station comes back 
> to someone else, halt tx...
> 
> 73, Ross N4RP
> 
>> On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
>> As Jim said, its a nice AID to us old timers that cant click the red in 1 
>> second
>> 
>> -- Original Message --
>> From: "Jim - N4ST" 
>> To: "'WSJT software development'" 
>> Sent: 7/11/2017 4:07:40 PM
>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>> 
>>> Please keep "Call 1st".  It is a great aid to us old timers.
>>> If people don't like it, don't click the box.
>>> 
>>> 
>>> 73,
>>> Jim - N4ST
>>> 
>>> 
>>> -Original Message-
>>> From: Erik - [mailto:erikcarl...@live.com]
>>> Sent: Tuesday, July 11, 2017 12:02
>>> To: WSJT software development 
>>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>>> 
>>> 
>>> "We are interested in feedback from users on the question of partial QSO
>>> automation.  Should "Call 1st" be changed or removed?"
>>> 
>>> I like it as it is. One thing though, it gets broken by callsigns such as
>>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
>>> big deal since reciprocal calls such as this one are not too common. My
>>> over-riding request is to not remove "Call 1st".
>>> 
>>> Erik EI4KF.
>>> 
>>> 
>>> 
>>>  
>>> -- 
>>> 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
> 
> 
> -- 
> FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
> transmitter power necessary to carry out the desired communications.”
> 
> 
> --
> 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] Suggestions for three extra bits in FT8

[James Shaver (N2ADV)]

If you throw attenuation at the signal and the issue goes away, the cause is 
most likely on the receive side.  It also helps to have a panadapter available 
(something that isn't tied into the AF chain).  The waterfall itself should not 
be used to determine signal quality.  

73,

Jim S. 
N2ADV

> On Jul 11, 2017, at 2:45 PM, Bill Somerville  wrote:
> 
>> On 11/07/2017 19:12, Tim Carlson wrote:
>> Would you consider that the first signal on the left is being overdriven 
>> somewhat?  Or is that just a consequence of a stronger signal?  Or is it 
>> some atmospheric condition causing the signal to spread?
>> 
> Hi Tim,
> 
> hard to tell but it is all too common for the Tx audio level fed to the rig 
> to be too high. This causes non-linearity and will almost certainly widen the 
> transmitted signal. The main product of clipping is harmonics but if the 
> sender is using the split operating facility that is largely innocuous due to 
> the harmonics being above 3000 Hz and attenuated by the rig's Tx SSB filter 
> low pass cut off. Still there is no excuse for over driving the audio input 
> to the rig and there is a secondary consequence. At each frequency shift of 
> the modulation there is a minimal phase discontinuity, we shift the phase 
> without a glitch but nevertheless it is a discontinuity. These small 
> discontinuities fractionally widen the signal when the audio is correctly 
> matched through to the transmitter but over drive widens them considerably. 
> This is what you are seeing, a horizontal spike on the waterfall at each tone 
> shift.
> 
> You must also be careful about attributing blame in these situations, all of 
> the above can happen on the receiving side too, so check your own house is in 
> order before accusing another of having a poor signal.
> 
> 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] FT8 and "Call 1st"

[James Shaver (N2ADV)]

I think the fact that it's user selectable is important and I agree it should 
be kept because the turnaround time to respond to an inbound message is very 
short (this is especially noticeable for those of us that do 99% of our 
operating remotely where internet connections may prevent successful replies in 
such a short amount of time).  Purists can certainly choose to not enable the 
feature but I think it's a nice feature.  I also agree with disabling the TX 
once the user hits the "73" in the cycle - user intervention is still required 
which is still important in my opinion.  

My 2 cents. :)

73,

Jim S. 
N2ADV

> On Jul 11, 2017, at 12:07 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> I did send the patch that fixes that...did you see it?
> 
> de Mike W9MDB
> 
> 
> From: Erik - 
> To: WSJT software development  
> Sent: Tuesday, July 11, 2017 11:04 AM
> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
> 
> 
> "We are interested in feedback from users on the question of partial QSO 
> automation.  Should "Call 1st" be changed or removed?"
> 
> I like it as it is. One thing though, it gets broken by callsigns such as 
> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a big 
> deal since reciprocal calls such as this one are not too common. My 
> over-riding request is to not remove "Call 1st".
> 
> Erik EI4KF.
> 
> 
> 
> --
> 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

[wsjt-devel] Distribution

[James Shaver (N2ADV)]

Please be advised that there are some enterprising souls sharing links directly 
to Sourceforge distributing the Release Candidate files. There have been posts 
all over Facebook so far and people are downloading like crazy. 

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

[wsjt-devel] Distribution

[James Shaver (N2ADV)]

Please be advised that there are some enterprising souls sharing links directly 
to Sourceforge distributing the Release Candidate files all over social media. 
Seeing posts crop up everywhere. 


--
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] K3S Going Split???

[James Shaver (N2ADV)]

Yep I had the same issue. If memory serves, HRD was not reporting back to the 
K3 to not go into Split mode. 

73,

Jim S. 
N2ADV

> On Jul 10, 2017, at 3:51 PM, Jim - N4ST <newsgr...@jimpricejr.com> wrote:
> 
> It may well be an "HRD thing", but it only happens when I tell WSJT-X to
> "FAKE IT".  With this not selected the K3 doesn't go split on WSJT-X
> initialization.
> 
>  
> 73, 
> Jim - N4ST
> 
> -Original Message-
> From: James Shaver (N2ADV) [mailto:n2...@windstream.net] 
> Sent: Monday, July 10, 2017 14:30
> To: WSJT software development <wsjt-devel@lists.sourceforge.net>
> Subject: Re: [wsjt-devel] K3S Going Split???
> 
> I had this happen last year sometime with my K3.  Bill and I were on Skype a
> couple times trying to track down the cause - ultimately we determined it
> was an HRD thing.  My solution was to dump HRD. 
> 
> Not very helpful, I know (sorry) - maybe you'll have better luck tracking it
> down. 
> 
> Jim S. 
> N2ADV
> 
>> On Jul 10, 2017, at 2:18 PM, Jim - N4ST <newsgr...@jimpricejr.com> wrote:
>> 
>> I have the issue that when I start WSJT-X, or change configurations, it
> puts my Elecraft K3S in split mode.  That causes the WSJT-X CAT comms to
> fail because I have "FAKE IT" selected and that mode cannot initiate when
> the rig is already in split mode.  WSJT-X is setup to communicate with HRD
> 6.4.x as the controller for the K3S.  A quick push of a macro button on the
> K3S cancels the split mode allows WSJT-X CAT comms to initiate properly.
>> Anybody else seen this?
>> 
>> Windows 10, WSJT-X  r7838, HRD 6.4.0.659
>> 
>> P.S. - It would be totally awesome if WSJT-X configurations changes could
> optionally send out user defined macros over the CAT channel.
>> 
>> ___
>> 73,
>> Jim - N4ST
>> 
> 
> 
> --
> 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] K3S Going Split???

[James Shaver (N2ADV)]

I had this happen last year sometime with my K3.  Bill and I were on Skype a 
couple times trying to track down the cause - ultimately we determined it was 
an HRD thing.  My solution was to dump HRD. 

Not very helpful, I know (sorry) - maybe you'll have better luck tracking it 
down. 

Jim S. 
N2ADV

> On Jul 10, 2017, at 2:18 PM, Jim - N4ST  wrote:
> 
> I have the issue that when I start WSJT-X, or change configurations, it puts 
> my Elecraft K3S in split mode.  That causes the WSJT-X CAT comms to fail 
> because I have "FAKE IT" selected and that mode cannot initiate when the rig 
> is already in split mode.  WSJT-X is setup to communicate with HRD 6.4.x as 
> the controller for the K3S.  A quick push of a macro button on the K3S 
> cancels the split mode allows WSJT-X CAT comms to initiate properly.
> Anybody else seen this?
> 
> Windows 10, WSJT-X  r7838, HRD 6.4.0.659
> 
> P.S. - It would be totally awesome if WSJT-X configurations changes could 
> optionally send out user defined macros over the CAT channel.
> 
> ___ 
> 73,
> Jim - N4ST
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

[wsjt-devel] Auto sequence intermittent issue

[James Shaver (N2ADV)]

I sent this a couple days ago but it got rejected due to image size and I 
hadn't seen it again so I didn't resend as I thought it was resolved but I see 
this very intermittently (1 in 25 or so):

The auto sequencer won't always recognize that the other station has sent "73" 
and will resend the "RRR" part of the sequence. It appears to be because it 
decodes after the TX period begins which I thought was my machine (though it 
was only showing about 15% CPU usage at the time) but this is on another 
machine (also running Win 7 Home Premium with no other programs running in the 
background other than JTAlert and Dimension 4 and Log4OM). 

I still figure this may be on my end but just in case it isn't I wanted to put 
feelers out and see if others have seen it. 

73,

Jim S. 
N2ADV

--
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] Little request - 1.7.1 gain slider

[James Shaver (N2ADV)]

Hey George - when using SSDR, sure, but that doesn't work if I'm using my KX3, 
K3, FT817, or any of the other 6 transceivers I use to play on digital modes. 

73,

Jim S. 
N2ADV

> On Jul 8, 2017, at 12:00 PM, George J Molnar <geo...@molnar.com> wrote:
> 
> Jim, shouldn’t you be able to make a SSDR profile for each digi app, using a 
> different DAX channel with the appropriate levels?
> 
> 
> George J Molnar
> Nevada, USA
> KF2T  @GJMolnar
> 
> 
> 
> 
> 
>> On Jul 8, 2017, at 8:55 AM, James Shaver (N2ADV) <n2...@windstream.net> 
>> wrote:
>> 
>> (Had to ask as the sound card controls are rough to mess with unless I'm 
>> using my Flex and the DAX control panel when I'm on a tiny screen) :)
>> 
>> 
>> 
>> 73,
>> 
>> Jim S. 
>> N2ADV
>> 
>>> On Jul 8, 2017, at 11:51 AM, James Shaver (N2ADV) <n2...@windstream.net> 
>>> wrote:
>>> 
>>> Understood. 
>>> 
>>> 73,
>>> 
>>> Jim S. 
>>> N2ADV
>>> 
>>>>> On Jul 8, 2017, at 11:44 AM, Bill Somerville <g4...@classdesign.com> 
>>>>> wrote:
>>>>> 
>>>>> On 08/07/2017 16:37, James Shaver (N2ADV) wrote:
>>>>> If that slider could be mapped to act like a mic volume control to adjust 
>>>>> the incoming audio up or down similar to the "pwr" slider on the opposite 
>>>>> side adjusts the outgoing audio volume that would do the trick
>>>> 
>>>> Hi James,
>>>> 
>>>> that is exactly what we are trying to avoid. The operating system mic. 
>>>> slider is just another digital level control that can only reduce the 
>>>> digital audio quality if it is anywhere other than 0dB FS (full scale).
>>>> 
>>>> If anything we would take over that control and set it to 0dB all the time.
>>>> 
>>>> 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
>> --
>> 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] Little request - 1.7.1 gain slider

[James Shaver (N2ADV)]

Understood. 

73,

Jim S. 
N2ADV

> On Jul 8, 2017, at 11:44 AM, Bill Somerville <g4...@classdesign.com> wrote:
> 
>> On 08/07/2017 16:37, James Shaver (N2ADV) wrote:
>> If that slider could be mapped to act like a mic volume control to adjust 
>> the incoming audio up or down similar to the "pwr" slider on the opposite 
>> side adjusts the outgoing audio volume that would do the trick
> 
> Hi James,
> 
> that is exactly what we are trying to avoid. The operating system mic. slider 
> is just another digital level control that can only reduce the digital audio 
> quality if it is anywhere other than 0dB FS (full scale).
> 
> If anything we would take over that control and set it to 0dB all the time.
> 
> 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] Little request - 1.7.1 gain slider

[James Shaver (N2ADV)]

If that slider could be mapped to act like a mic volume control to adjust the 
incoming audio up or down similar to the "pwr" slider on the opposite side 
adjusts the outgoing audio volume that would do the trick 

73 and thanks for responding!

Jim S. 
N2ADV

> On Jul 8, 2017, at 11:20 AM, Bill Somerville <g4...@classdesign.com> wrote:
> 
>> On 08/07/2017 16:16, James Shaver (N2ADV) wrote:
>> I know that the digital gain slider functionality was deliberately updated 
>> but rather than changing it or removing it, can it just become an actual 
>> audio input adjustment rather than digital gain?
> 
> Hi Jim,
> 
> how do you propose that to be implemented?
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

[wsjt-devel] Little request - 1.7.1 gain slider

[James Shaver (N2ADV)]

I know that the digital gain slider functionality was deliberately updated but 
rather than changing it or removing it, can it just become an actual audio 
input adjustment rather than digital gain?  That will be particularly handy for 
those of us that run several digital mode programs at the same time as changing 
the soundcard setting themselves can impact those other programs as well (also 
helps those of us who have to do a lot of our operating remotely where I can be 
cumbersome to go into the sound settings directly). 

Thanks a bunch!

73,

Jim S. 
N2ADV

--
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] Distributing builds of devel software

[James Shaver (N2ADV)]

Mostly little things like FT8 being greyed out or getting random errors when 
starting the program. 

Once I walk them through compiling the program themselves, the issues disappear 
and they only see what's already been reported to the list. 

Thanks, Bill (and thx QSO btw)
73,
Jim S. 
N2ADV

> On Jul 8, 2017, at 8:27 AM, Bill Somerville <g4...@classdesign.com> wrote:
> 
>> On 08/07/2017 13:19, James Shaver (N2ADV) wrote:
>> Udo, I know you read this mailing list.
>> 
>> Please stop distributing builds of 1.7.1 devel.
>> 
>> My inbox is full of people who have used your builds who are having issues 
>> and have told me you gave them the install file. I know you mean well but 
>> please don't.
> 
> HI Jim,
> 
> unfortunately leopards don't change their spots!
> 
> Apart from the obvious problem, what are the issues being reported to you?
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

[wsjt-devel] Distributing builds of devel software

[James Shaver (N2ADV)]

Udo, I know you read this mailing list. 

Please stop distributing builds of 1.7.1 devel. 

My inbox is full of people who have used your builds who are having issues and 
have told me you gave them the install file. I know you mean well but please 
don't. 

Not looking to get into an argument here and no response is requested or 
needed. 

Jim S. 
N2ADV

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

[wsjt-devel] Colors - FT8

[James Shaver (N2ADV)]

Running r7775 (Win 7) I've noticed and others have brought to my attention that 
the colors for new DXCC and new call aren't showing up in the RX window.  CQ in 
Message and My Call in message are working.  

73,

Jim S. 
N2ADV

--
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] Missing menu bar

[James Shaver (N2ADV)]

Thanks, Joe!  I had to walk a few people through getting their menu back today 
lol

73,

Jim S. 
N2ADV

> On Jul 1, 2017, at 3:15 PM, Joe Taylor  wrote:
> 
> Hi all,
> 
> Far too many unwary users are being bitten by the "CTRL+M" bug.  In general, 
> it seems like bad policy to hide screen controls and leave no visible way to 
> get them back.
> 
> In r7769 I added a checkbox labeled "Menus" on the main window, and one 
> labeled "Controls" on the Wide Graph.  These do essentially what CTRL+M does. 
>  For now I left the oprion to use CTRL+M in place, but it should probably be 
> removed.
> 
> There may well be better ways to place and/or configure the new checkboxes.  
> Please feel free to suggest changes.
> 
>-- Joe
> 
> --
> 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: Potential new mode for fast QSOs

[James Shaver (N2ADV)]

Also compiled and running without issues. Decoded NV0O on 17 meters (I was 
working on the honeydo list around the house so wasn't able to respond) but am 
back on 17 now and calling CQ. 

73,

Jim S. 
N2ADV

> On Jun 29, 2017, at 2:32 PM, George J Molnar  wrote:
> 
> Compiled and run without incident on Mac OS 10.12.6 (beta). Monitored signal 
> quality seems good. 
> 
> No contacts… yet!
> 
> 
> George J Molnar
> Nevada, USA
> KF2T  @GJMolnar
> 
> 
> 
> 
> --
> 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: Potential new mode for fast QSOs

[James Shaver (N2ADV)]

I'm compiling now - count me in!

73,

Jim S. 
N2ADV

> On Jun 29, 2017, at 1:43 PM, Bill Somerville  wrote:
> 
>> On 29/06/2017 18:37, char...@sucklingfamily.free-online.co.uk wrote:
>> Built and running - no on-air tests yet.
> 
> Hi Charlie,
> 
> if you want a test QSO I'm sure we can find a band we can work on.
> 
> 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] What in the world is "JT10"

[James Shaver (N2ADV)]

Silly me I was concerned about the "JT" series of names being used in a way 
that wasn't authorized. 

> On Apr 10, 2017, at 5:39 PM, Joe Taylor <j...@princeton.edu> wrote:
> 
>> On 4/10/2017 5:09 PM, James Shaver (N2ADV) wrote:
>> Not necessarily WSJT-X related (but maybe?).  I just saw a Facebook post 
>> touting "the new JT10 mode" which is part of JTDX - I have to admit that I'm 
>> confused.  Can someone enlighten me?
> 
> This email list is concerned with WSJT(-X), MAP65, and WSPR; it's not 
> the place to ask about JTDX.
> 
> Aside from having written most of the code that was copied to make JTDX, 
> we know next to nothing about that program.  Exchange of information is 
> essentially one-way, WSJT-X ==> JTDX.
> 
> For what it's worth, I'd guess that your Facebook poster is simply 
> misinformed.
> 
>-- 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

[wsjt-devel] What in the world is "JT10"

[James Shaver (N2ADV)]

Not necessarily WSJT-X related (but maybe?).  I just saw a Facebook post 
touting "the new JT10 mode" which is part of JTDX - I have to admit that I'm 
confused.  Can someone enlighten me?  

73,

Jim S. 
N2ADV

--
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] JT65 HF bands capacity, spectra allocation and software support

[James Shaver (N2ADV)]

With all due respect "weak signal" does not always equal "low power" (most of 
the time, sure, but a signal can be pretty weak even at 1.5 KW in poor 
conditions). 

Can you supply actual data to support your supposition that "high power usage 
is a common behavior" in the PSK areas (i.e. Something OTHER than just what is 
based on what you see on the spectral display)?  Case in point here, the last 
time I worked PSK31, I received a severely worded email from another op who 
probably had the best of intentions dressing me down for "running too much 
power" saying that he could "tell I was pushing close to legal limit"based on 
"what he saw" and going on about how rude I was being, etc... I politely 
responded with a picture of my station at that time which was an Elecraft KX3 
running on a battery on my picnic table set to 0.5 watts into a home brewed 
vertical antenna next to an IMD meter monitoring my outgoing signal.  

The saying "a picture paints a thousand words" isn't always applicable to what 
you see on the waterfall. A lot less ops are "running power" than current 
common perception seems to state. 

Again, this is with all due respect. 

Jim S. 


> On Feb 18, 2017, at 2:12 PM, Игорь Ч  wrote:
> 
> Hello All,
> 
> There is simple answer why users prefer operate JT65 on the overloaded HF 
> bands while there is underused  JT9 subband.
> .
> Anyone from DX location, let's say for instance from New Zealand, have 
> frequently met scenario where multiple signals coming back to his CQ call.
> .
> Due to the nature of JT9 protocol neither one of two JT9 signals 
> on the same frequency will be decoded in most cases, things getting worse if 
> there are more than two signals on the same frequency. To make QSO possible 
> experienced JT9 users call DX stations with frequency split and DX station in 
> response has to use split operation or frequency hopping.
> .
> Now one could imagine if there is propagation open between Europe and New 
> Zealand and at least 10 operators calling one DX station using frequency 
> split, this way JT9 spectral benefit versus JT65 is almost eliminated.
> .
> Multipass decoding will only work if at least one JT9 signal is decoded on 
> the frequency, otherway there is nothing to subtract.
> .
> Now back to JT65 HF subband capacity, for evenly distrubuted JT65 signals 
> between -01 and -26dB SNR to the Gaussian noise, maximum JT65 current subband 
> capacity is around 100...110 decoded signals if tested with 200 simulated 
> signals in the .wav file. These decoded signals have SNR to the Gaussian 
> noise in range from -01 to -14 dB, week signals gone unless DX operator using 
> 1kW power to try getting through.
> .
> For last 45 days number of JT65 HF users raised 25% up, and it is now usual 
> event to get 35..40 decoded JT65 messages for single RX interval. Going with 
> such increase rate monthly we will get out of the current JT65 HF bands 
> capacity within 6 months, and similar to PSK modes, high power usage will 
> became as common behaviour.
> .
> Hence there no other way to save HF JT weak signal communication but an 
> increase of the occupied bandwidth and it should be good idea to act now, 
> until we got to QRO JT communication instead of the weak signal one. 
> .
> 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
--
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] JT65 HF bands capacity, spectra allocation and software support

[James Shaver (N2ADV)]

To add to Bill's very well written response, there are many pre-established 
operations on 40 meters around the JT mode watering hole. Using my Flex 6300, I 
can see many SSB Phone QSO's going on on 7.072-3 and 7.080 from Canadian and 
some other ITU Region 1 entities. Even though the band may seem dead in one 
place, the HF bands are already quite crowded (this is less evident to those 
with compromise antennas who may not be receiving these other stations but rest 
assured, they're there). The increasing popularity of JT65 means we need to be 
agile operators who change our operation style to move around with band 
conditions which also includes how crowded the band is at any given time). 

Weak signal operation is still very much alive!  

73,

Jim S. 
N2ADV

> On Feb 18, 2017, at 8:16 AM, Bill Somerville  wrote:
> 
>> On 18/02/2017 07:47, Игорь Ч wrote:
>> Due to the current explosive growth of HF activity in JT65a mode we 
>> are getting close to a date when existing JT65 bandwidth will be fully 
>> utilized leaving no possibility for weak signal communication but 
>> local contacts.
>> .
>> It might be right time now to act towards the new concept for JT65 HF 
>> usage and spectra allocation, considering latest SDR technology for 
>> handling 20kHz bandwidth in the software.
> 
> HI Igor,
> 
> although this is technically possible with average PC sound card sample 
> rates it would tend to exclude those with SSB only rigs who would have 
> to move around just to see which stations are active. I believe this 
> would create a DX cluster type herd mentality with most stations landing 
> on the band segment that has the rare station on. One of the things I 
> really like about JT modes on HF is that QSOs are almost exclusively 
> initiated from on air calls, the ability of everyone to potentially copy 
> everyone is fantastic. Even though it is all about computers and  the 
> Internet adds huge benefits, the fundamental principles of listening on 
> air for QSO partners is one reason for the success of the JT modes on HF 
> IMHO.
> 
> Another matter to consider is that on most HF bands there is simply not 
> enough bandwidth available to spread the JT modes out by a factor of 
> five. Take 40m for example, here in the EU we are operating in the phone 
> band which itself is busy as the solar minimum is approaching (a solar 
> minimum that is forecast to be longer and deeper than most operators 
> have experienced), pressures on spectrum space will undoubtedly increase 
> if the hobby is to succeed and proposals to grab more for any operating 
> mode will not be well received.
> 
> If a few more stations shifted to JT9 on HF, the potential spectrum 
> utilization gains are similar without requiring many to buy new rigs. 
> Admittedly JT65A on HF has reasonably good overlapping signal decoding 
> which is greatly enhanced by two pass decoding. This is an area that has 
> not been taken advantage of for JT9 yet, when the utilization of JT9 
> becomes high enough to justify it I'm sure that a win is there to be had 
> by using two pass decoding.
> 
> Perhaps the near capacity JT65A utilization at times will encourage more 
> to experiment with new bands and JT9 on HF. There is still a lot of 
> space for us all within a conventional SSB bandwidth (plus a bit if you 
> have 4 or 5kHz Rx capability) on each band. Imagine what might happen if 
> everyone who uses JT65A on HF switched to JT9, I doubt we would be 
> looking for more spectrum space for some time.
> 
> Just my 2c
> 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 Version 1.7 feedback

[James Shaver (N2ADV)]

Just to add to Bill's answer to issue 3, you will also get better results with 
the 7300 if you run with the AGC "OFF" as that can also cause issues as your 
receiver automatically reduces the gain and can lose weaker signals in the 
presence of a stronger one. 

73,

Jim S. 
N2ADV

> On Jan 6, 2017, at 11:23 AM, Bill Somerville  wrote:
> 
> Hi Neil,
> 
> some comments in line below.
> 
>> On 06/01/2017 15:25, Neil W3NTP wrote:
>> 1. Version 1.7 is downloaded as a .exe file which is deleted by Norton 
>> Security Suite. Suggest you use a proper installer program to get 
>> around antivirus programs deleting the software. This can be a pain to 
>> those not familiar with disabling the security software.
> I suggest you replace Nortin Security Suite with a more reliable AV 
> product. The issue is not that our installer, and it is a "proper 
> installer", is being matched with some generic virus signature and the 
> resulting false positive is worse than worthless.
>> 
>> 2. Better handling of ICOM-7300 driver communications. I get COM port 
>> conflicts on occation with the new release. When using version 1.6, I 
>> configured the software for a ICOM-7100 and it handled the COM ports 
>> fine. With the ICOM-7300, Ver 1.7 will display communication error to 
>> Rig can not communicate. To fix, I power cycle Rig and restart WSJT-X. 
>> This can be a pain, but did not have this problem with vrsion 1.6
> Please report the exact error message received including the details 
> shown in the "Show Details" box. Do not use auto baudrate detection on 
> your rig, it is not reliable. Turn off "CI-V Transceive" mode on your 
> rig as it causes unsolicited CAT transmission from the rig which 
> interferes with traffic from WSJT-X.
>> 
>> 3. Very strong JT9 signals can overload the inputs to the receiver and 
>> I can not receive very strong JT9 signal,where as +5 and below I can 
>> decode down to about -15 or so. I wonder is JT9 has a problem syncing 
>> with the signal. Also responding to JT9 signals always works, whereas 
>> calling CQ and getting a strong response never works. Not sure the 
>> problem.
> 
> Try reducing the RF gain on your rig if it is being overloaded. Once 
> overloaded clipped signals get into the digital domain there is 
> virtually nothing that can be done to accurately recover the strong 
> signal or any other signal in the passband. You should be able to decode 
> JT9 signals between about +40dB (I doubt you will ever see a signal this 
> strong unless your Rx noise is virtually nil and your front end can 
> withstand several volts!) and -27dB, if you are not able to do that then 
> perhaps you need to adjust your gain profile between the aerial and the 
> PC such that no stage overloads.
> 
> What you are describing sound like a possible combination of one or more 
> of mis-adjusted gain levels, RFI, and time synchronization errors.
> 
> 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] r7329 breaks JTAlert

[James Shaver (N2ADV)]

It's helpful to be able to click on a CQ in JTAlert rather than in the decode 
window in WSJT-X when the band is very busy. It is frustrating when you go to 
click on a CQ and the decodes keep scrolling the target station away (more than 
once I've ended up clicking on the wrong station). 

Jim S. 
N2ADV

> On Nov 22, 2016, at 7:05 PM, Joe Taylor  wrote:
> 
> Why would I want JTAlert to start a QSO?
> 
>> On 11/22/2016 6:23 PM, Black Michael wrote:
>> The change in r7329 to fix the Autoseq disables JTAlert's ability to
>> start the QSO. Clicking in JTAlert will show the CQ message in the
>> receive window but no longer enables "Enable Tx".
>> r7328 works fine.
>> 
>> 
>> de Mike W9MDB
>> 
>> 
>> 
>> --
>> 
>> 
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

Re: [wsjt-devel] Lock TX=RX greyed out

[James Shaver (N2ADV)]

Uncheck "Enable VHF/UHF/Microwave Features" in the settings menu (General tab) 
and the lock option will return. 

73,

Jim S. 
N2ADV

> On Oct 16, 2016, at 11:29 AM, David Tiller  
> wrote:
> 
> All,
> 
> I noticed that sometime between r6353 and r7028 the option "Lock RX=TX" seems 
> permanently greyed out in all the modes that support it (JTx, ISCAT, etc). 
> It's still greyed out in r7184. Was this a design choice, or is it a bug?
> 
> I don't use hamlib to control my rig, so I have the CAT control set to None, 
> but I'd still like to be able to work 'split' in the given 3kHz band.
> 
> Thanks!
> 
> --
> David Tiller
> Sr. Architect/Lead Consultant | CapTech
> (804) 304-0638 | dtil...@captechconsulting.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] Lock TX=RX

[James Shaver (N2ADV)]

Disable VHF/UHF/Microwave Features and the Lock TX/RX functionality returns. 



> On Aug 8, 2016, at 8:21 PM, Pino Zollo  wrote:
> 
> Version 1.7.0 rc1 Linux mode JT9+JT65
> 
> Lock TX=RX is gray  ...can not be disabled, while TX<-RX  and RX<-TX are
> black...but useless ..
> 
> Whats the problem ?
> 
> 
> 73
> 
> Pino ZP4KFX
> 
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity 
> planning reports. http://sdm.link/zohodev2dev
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Odd behavior

[James Shaver (N2ADV)]

Not sure if I'm the only one experiencing this, but every once in a while, when 
the transmit function will not enable but I'll show a trace and subsequent 
decode on the screen that ends up being my CQ... Screen shot attached to show 
you what I mean.  I've run into this randomly with all builds and it happens 
regardless of what radio I'm using and whether I'm using CAT control via HRD or 
directly to the radio.  Just curious if anyone else has seen this?

73,

Jim S. 
N2ADV

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

Re: [wsjt-devel] Split-Mode and Elecraft K3

[James Shaver (N2ADV)]

Not sure if it helps but I use "fake it" with my K3 and it works quite well. 

Jim S. 
N2ADV

> On Jul 12, 2016, at 6:39 AM, Bill Somerville  wrote:
> 
>> On 11/07/2016 12:38, Bob KD7YZ wrote:
>> If I select Split-Rig in WSJTx; setup K3 to Split; Set DxCommander to
>> Split
> 
> HI Bob,
> 
> the statement you made above is confusing me, it implies that you are 
> manually setting split on your K3 and also in DX Lab Suite Commander. 
> You should not need to do that if you have "Settings->Split Operation" 
> set to "Rig" in WSJT-X, it should all be automatic.
> 
> Can you confirm that if you set WSJT-X "Settings->Split Operation" to 
> "Rig" then both the rig and DX Lab Commander indicate the SPLIT is 
> enabled. You may need to cause a Tx frequency change or transmission for 
> this flow right through to the rig, the simplest way to trigger the 
> synchronization is to CTRL+Click on the waterfall at least 500Hz away 
> from the current Tx cursor (the red one).
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Urgently needed feature - Control of Tx signal to radio from WSJT-X

[James Shaver (N2ADV)]

I'd be curious to see these as well - and it would need to be more than just a 
screen shot of the built in spectrograph tied into the AF stage - please 
provide something tied into the IF stage as well such as a screen grab from a 
panadapter... You aren't just relying on the "waterfall" display as your sole 
measure of signal quality... Are you?

Jim S. 
N2ADV

> On Apr 28, 2016, at 9:04 AM, Joe Taylor  wrote:
> 
> Hi Steve,
> 
> VK3VM wrote:
>> ... a number of elements are doing quite a bit of damage in
>> the general AR Community with WSJT-X and bad practises...
> 
> When you see a signal you think is "doing damage", how do you conclude 
> that operator was using WSJT-X ?
> 
>> ... I am seeing a considerable number of very wide, very dirty
>> signals emanating from a number of Amateurs locally in my parts
>> (i.e. SE Asia and Oceania).
> 
> Please send me two or three examples of .wav files showing the signals 
> you consider "very wide, very dirty".
> 
>-- 73, Joe, K1JT
> 
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rig control issue v6596

[James Shaver (N2ADV)]

Will do when I get home

73,

Jim S. 
N2ADV

> On Apr 7, 2016, at 7:16 AM, Bill Somerville <g4...@classdesign.com> wrote:
> 
>> On 07/04/2016 11:53, James Shaver (N2ADV) wrote:
>> Bill, my K3/HRD6 gremlin is back now too (when split mode = "fake it" 
>> WSJT-X sends commands through HRD and tries to throw the rig into 
>> "split" which causes rig control to fail)
> Hi Jim & Rob,
> 
> looks like I have messed up the HRD rig control capability a bit. So I 
> can see what is happening here is an instrumented version of WSJT-X:
> 
> https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.7.0-devel-win32-r6596-CAT-trace.exe
> 
> install it and run a minimal session that demonstrates the issue then 
> quit WSJT-X. It will have created a trace file:
> 
>   %TEMP%\WSJT-X_trace.log
> 
> send me that file, off the list, for analysis please?
> 
> 73
> Bill
> G4WJS.
> 
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rig control issue v6596

[James Shaver (N2ADV)]

Bill, my K3/HRD6 gremlin is back now too (when split mode = "fake it" WSJT-X 
sends commands through HRD and tries to throw the rig into "split" which causes 
rig control to fail)

73,

Jim S. 
N2ADV

> On Apr 7, 2016, at 6:22 AM, Bill Somerville  wrote:
> 
>> On 07/04/2016 02:12, Rob Neff wrote:
>> Icom IC-7100, USB Control via HRD6, changes out of data mode *after*
>> transmit when in "None" or "USB" in Settings>Radio>Mode. If set to
>> "Data/PKT" it immediately changes out of data mode (from USB-D to USB)
>> *before* transmitting thus no audio.
> Hi Rob,
> 
> can you send me the file:
> 
>   %LOCALAPPDATA%\WSJT-X\"HRD Interface Information.txt"
> 
> please?
> 
> 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] Gravitational Waves

[James Shaver (N2ADV)]

I'm in agreement with Richard and Dave. I am fascinated by this subject and 
grateful for the additional information. As with anything, the big knob is your 
friend rather than being mean about it. The "big knob"'l in this case is your 
delete button. Or, if you have that much angst about Joe, unsubscribe and all 
of your woes will be solved. 

Or, carry on and the rest of us can simply point and laugh and use you as an 
example of how not to behave once out of primary school. 

73 to all. 

Jim S. 

> On Feb 16, 2016, at 5:09 AM, Richard Bown  wrote:
> 
> 
> I fully Agree with Dave AA6YQ, that was uncalled for and very inaccurate and 
> vindictive
> 
> On Tue, 16 Feb 2016 01:19:53 -0500
> " Dave AA6YQ"  wrote:
> 
> AA6YQ comments below
>> 
>> -Original Message-
>> From: Chase Turner [mailto:ke4...@gmail.com] 
>> Sent: Monday, February 15, 2016 10:31 PM
>> To: WSJT software development
>> Subject: Re: [wsjt-devel] Gravitational Waves
>> 
>> You are a little late to this party, as usual. A lot of the discussion about 
>> this phenomena,
>> which doesn't have anything to do with WSJT (other than your ego that this 
>> is in fact your
>> mailing list) has been happening all over so many mailing lists that your 
>> response is cluttering,
>> off topic and a bit of braggadocio, even for you (who had nothing to do with 
>> the confirmation of
>> an earlier theory). The most fruitful discussions can be found, in the 
>> mailing list world that
>> many here might be interested in, located on the Time Nut's list. There may 
>> be other lists that
>> cross boundaries that many here would find interesting, too. 
>> 
>> Next time, please confine your responses to those who asked you what you 
>> thought, because I know
>> this list doesn't need a lot of off topic mail- your own rule, I think. But 
>> maybe you've changed
>> it in midstream, like you do so many other things.
>> 
>> And while I'm wondering, since Steve did most of the work on the decoder 
>> recently- it will be his
>> name first in the QEX article, right? Or do you actually believe you should 
>> be listed as the lead
>> author for the article- even though you did nothing more than error 
>> checking? 
>> 
> What a nasty, mean-spirited post. If your objective was sincerely 
> behavior change, it's hard
> to imagine a more incompetent attempt at achieving it.
>> 
>>  Dave, AA6YQ
>> 
>> 
>> On Mon, Feb 15, 2016 at 9:31 AM, Joe Taylor  wrote:
>> 
>> 
>>Hi all,
>>
>>After spending a most enjoyable week on the sunny Caribbean island of
>>St. Lucia, I'm home again.  Returning was quite a shock -- the
>>temperature here on arrival was 6 F.
>>
>>Probably you heard last Thursday's announcement about the detection of
>>gravitational waves originating from a pair of colliding black holes,
>>some 1.3 billion light years away, in the southern sky.  This is a major
>>discovery in physics -- it opens a new window on the universe, if you
>>like.
>>
>>Since I've already had off-list queries from several list members about
>>this announcement, I'll share a few links to some of the essentials:
>>
>>Full press release from the LIGO (Laser Interferometer Gravitational
>>Wave Observatory) collaboration:
>>https://www.ligo.caltech.edu/news/ligo20160211
>>
>>The actual detected waveform of the black-hole collision, presented as
>>an audio clip you can listen to:
>>https://www.ligo.caltech.edu/video/ligo20160211v2
>>
>>In case you're interested in more details, I've posted a copy of the
>>full announcement paper as published in Physical Review Letters here:
>>
>>http://physics.princeton.edu/pulsar/K1JT/PhysRevLett.116.061102.pdf
>>
>>-- Joe, K1JT
>>
>>
>> --
>>Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>Monitor end-to-end web transactions and take corrective actions now
>>Troubleshoot faster and improve end-user experience. Signup Now!
>>http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
>>___
>>wsjt-devel mailing list
>>wsjt-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> 
> -- 
> -- 
> Best wishes /73 
> Richard Bown
> 
> Email : rich...@g8jvm.com
> HTTP  :  http://www.g8jvm.com
> nil carborundum a illegitemis
> ##
> Ham Call: G8JVM . QRV: 50-432 MHz + Microwave 23 cms 140W, 13 cms 100W & 3cms 
> 5W
> Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
> QRV VHF 6mtrs 200W, 4 mtrs 150W, 2mtrs 400W, 70cms 200W
> OS: Linux Mint 17.3 x86_64 on a Dell Inspiron 

[wsjt-devel] Rig control issue - HRD/Elecraft K3

[James Shaver (N2ADV)]

I'm hesitant to send this because I'm not sure if it's a bug or just isolated 
to me; I haven't been able to find anyone else with a similar experience.  
Please forgive me if it is not appropriate.  

I just compiled 1.7.0 devel r6418 and I am running Windows 10 Home 64 bit and 
using HRD 6.3.0.466 for CAT Control.  

I'm getting a "Rig Control Error" on startup.  More details as follows:

I usually use "Fake it" for the "Split" setting because that seems to work best 
with my Elecraft K3.  This is because if I use "rig" instead, the K3 hops in 
and out of "Split" mode randomly.  If I select "none" the power delivery is not 
smooth, especially close to the edges of the passband (which you all know :) ). 
 This worked quite well until the recent build where "Fake it" now throws the 
K3 into "split" mode when I start WSJT-X which then causes a "Rig Control 
Error" stating "Emulated split mode requires rig to be in simplex mode" which 
has never happened before.  Usually when "fake it" is selected, the rig remains 
in simplex mode and there are no issues.  

Anyone else getting this?  I didn't have this issue prior to r6418 and it isn't 
happening with 1.6, either.  

Like I said, not sure if this is really a "bug" yet but figured I'd put it out 
there just the same.  

Thanks for all the work being done on this.  

73,

Jim S. 
N2ADV
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X v1.7 r6278

[James Shaver (N2ADV)]

Bill, this is good information and clarification. Thanks for taking the time to 
put this together. 

73,
Jim S. 
N2ADV

> On Dec 16, 2015, at 6:47 AM, Bill Somerville  wrote:
> 
>> On 16/12/2015 11:15, Guy G4DWV/4X1LT wrote:
>> Hi,
> Hi Guy,
>> 
>> Does this mean that Joe does not want users to go on the air with the latest
>> builds compiled with JDSDK?
> At present that is the recommendation for the development branch. The 
> intent is that during periods of disruptive development we would like to 
> embargo the development branch for on-air use. We will probably 
> designate revisions that are usable from time to time, such designated 
> revisions should be considered as a technology preview or alpha quality. 
> Between those designated revisions the development branch is no more 
> than a sandpit for developers to exchange ideas and partial implementations.
>> 
>> Does this mean that I can only use the official release in future?
> Not at all, if you build WSJT-X yourself then you can use it on air or 
> to contribute to the development effort by testing or contributing 
> patches. Currently we are making it clear that work in progress is 
> definitely not stable and is not intended for on-air use. What seems not 
> to be getting through is that the development branch is where developers 
> operate, building it and going on air should not be for normal day to 
> day usage. If you are chasing your Amateur Radio goals using the 
> development version, for example working new ones, chasing US states, 
> new grids etc. then you are not contributing. If your goal is to help 
> with the development of WSJT-X by contributing source code changes or 
> testing new features then the development branch is relevant to you.
> 
> The background is that the development team use the SourceForge public 
> source code repository to collaborate on new features, this means that 
> incomplete code is nearly always live on the development branch. It 
> simply is not expected to work.
>> 
>> Sorry for the questions, but I do not know what 'head of the branch' means,
>> but I think that my guess could be close to the mark.
> The HEAD of a branch is the latest revision. A branch in source control 
> is the summation of all previous changes, you can build from the HEAD or 
> any prior revision. There are also multiple branches that represent 
> previous releases, these allow bug fixes to be applied to stable code 
> bases in the event that serious issues are discovered post release. 
> There is a dichotomy with the development branch, if you build prior 
> revisions then we are not prepared to support you, you are on your own; 
> if you build the branch HEAD then you will have non-working software 
> most of the time. So the development branch is not supportable, if you 
> use it you must be able to diagnose and fix problems yourself.
>> 
>> I would like to apologise to Joe for supplying a fellow ham with a compiled
>> installation file in the belief that I was helping a fellow ham in the
>> spirit of the hobby.
> This is reasonably acceptable on a one to one basis, we understand that 
> the modes available in WSJT-X are great fun to use and we all want to 
> demonstrate them to our fellow operators. If you do that then you are 
> also responsible for support if something goes wrong. What is not 
> welcome is wholesale distribution of binary packages without consent and 
> without any intent to offer support, this is simply free loading as I 
> say above and is not in the spirit of the hobby. You should also 
> consider that if an operator is new to the WSJT-X application then they 
> are probably far better off with an official release version which we 
> will gladly help out with if things do not work as advertised.
>> 
>> Merry Christmas and Happy New year to all here.
> Likewise!
>> 
>> 73 de Guy
> 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] RR73 message button

[James Shaver (N2ADV)]

Adding JTAlert gives that without needing to modify WSJT-X further so maybe it 
really is more of a social engineering project. If users get made aware that 
this type of exchange may happen, maybe as an annotation to the user guide or 
something like that, maybe that's all that's needed. 

Obviously that requires users to actually read the manual!

73,

Jim S. 
N2ADV

> On Dec 12, 2015, at 12:21 AM, Игорь Ч  wrote:
> 
> Hi Mike and all,
> 
> I guess there is the solution that would answer any user requirements: user 
> defined macros.
> 
> At the moment there is no enough flexibility in it: what we need is the 
> ability to take callsign from the buffer(which is already used to log QSO) 
> and to trigger the prompt to log QSO, both can be done via usage of the 
> special symbols-references in the macros.
> 
> 73 Igor UA3DJY
> --
> ___
> 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] RR73 message button

[James Shaver (N2ADV)]

I would second Igor's request especially since cutting the additional time has 
come in handy during changing HF conditions where the band could drop out 
quickly during a QSO. It may also have the secondary effect of eliminating some 
of the angst exhibited by some operators out there that I'm sure we've all seen 
in one place or another on the various social media platforms if it's included 
as an "official" part of the software. 

73,

Jim S. 
N2ADV

> On Dec 11, 2015, at 4:15 AM, Игорь Ч  wrote:
> 
> Hi Joe and all,
> 
> I have checked statistics based on the All.txt file: at least every second 
> operator transmit manually generated message RR73 or 'RRR 73' instead of the 
> standard RRR message. File with the summary and raw data in MS Excel format 
> is located there: https://cloud.mail.ru/public/4KBg/UoqJWw6rK
> 
> Summary does not include scenario where some operators use 73 message instead 
> of the RRR one.
> 
> There are three reasons to modify user interface with this message:
> 
> 1. It should reduce spectrum usage and interference on the overcrowded HF 
> bands
> 2. It will make GUI  more user friendly one
> 3. It will save time, both, in terms of the QSO length and manual message 
> generation
> 
> Also possibility to activate prompt for QSO logging on the RR73 message would 
> benefit users. 
> 
> May I ask to consider the code change in some future release, please?
> 
> 73 Igor UA3DJY
> --
> ___
> 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] [SPAM] Re: Re: RR73 message button

[James Shaver (N2ADV)]

RR 73 Neil :) :)

(I've been sending  RRR 73 (with a space between the RRR and 73) and it 
seems to make most of the sticklers happy - obviously there is always that one 
person who will never be happy but you can't please everybody!  

I'm happy either way and really enjoy the discussion!  

73,

Jim S. 
N2ADV

> On Dec 11, 2015, at 9:53 AM, Neil Zampella <ne...@techie.com> wrote:
> 
> James,
> 
> you know I agree with you on many things, but this is not one of them. 
> The original protocol shows that the ending transmission for the station 
> calling CQ is RRR, there is no need to add a 73. It still takes six 
> minutes to do a complete QSO even if you go with the RR73 at the end:
> 
> 1: CQ
> 2: Reply
> 3. Signal Rpt
> 4. Reply Signal Rpt
> 5. RRR (or in your case RR73)
> 6. Reply 73
> 
> At this point I restart with CQ ..
> 
> I say don't mess with what works.
> 
> Neil Zampella
> KN3ILZ
> 
>> On 12/11/15 06:53 am, James Shaver (N2ADV) wrote:
>> I would second Igor's request especially since cutting the additional time 
>> has come in handy during changing HF conditions where the band could drop 
>> out quickly during a QSO. It may also have the secondary effect of 
>> eliminating some of the angst exhibited by some operators out there that I'm 
>> sure we've all seen in one place or another on the various social media 
>> platforms if it's included as an "official" part of the software.
>> 
>> 73,
>> 
>> 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