Re: [wsjt-devel] SuperFox Practice Session

Oh no! Best wishes for a speedy recovery to your wife! 73, Jim S. N2ADV > On Jul 22, 2024, at 9:24 PM, Joe Taylor via wsjt-devel > wrote: > > I am very sorry to report that I cannot run a SuperFox Practice Session > tomorrow, after all. My wife was hospitalized yesterday with a broken

Re: [wsjt-devel] No 73 allowed after RR73?

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

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

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

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

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

Re: [wsjt-devel] FT8 issues

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

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

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

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

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

Re: [wsjt-devel] wsjt-x Program hung and not responding

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

Re: [wsjt-devel] External OM feature request for UI main window.

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,

Re: [wsjt-devel] Question about QRZ Integration

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 sig

Re: [wsjt-devel] Question about QRZ Integration

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 >

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

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

Re: [wsjt-devel] Test

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

Re: [wsjt-devel] Mystique?

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

Re: [wsjt-devel] Pulled back on 73

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 (

[wsjt-devel] Pulled back on 73

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

Re: [wsjt-devel] About qrm

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

Re: [wsjt-devel] 72-Bit Contest Mode, Rover support

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

Re: [wsjt-devel] AutoSeq Question

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

Re: [wsjt-devel] FT8 and "Call 1st"

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

Re: [wsjt-devel] Suggestions for three extra bits in FT8

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

Re: [wsjt-devel] FT8 and "Call 1st"

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

[wsjt-devel] Distribution

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.

[wsjt-devel] Distribution

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

Re: [wsjt-devel] K3S Going Split???

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

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.

[wsjt-devel] Auto sequence intermittent issue

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

Re: [wsjt-devel] Little request - 1.7.1 gain slider

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&

Re: [wsjt-devel] Little request - 1.7.1 gain slider

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

Re: [wsjt-devel] Little request - 1.7.1 gain slider

1: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 >&

[wsjt-devel] Little request - 1.7.1 gain slider

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

Re: [wsjt-devel] Distributing builds of devel software

> 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

[wsjt-devel] Distributing builds of devel software

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

[wsjt-devel] Colors - FT8

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

Re: [wsjt-devel] Missing menu bar

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

Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

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

Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

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

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

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

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

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

Re: [wsjt-devel] JT65 HF bands capacity, spectra allocation and software support

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.

Re: [wsjt-devel] JT65 HF bands capacity, spectra allocation and software support

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

Re: [wsjt-devel] WSJT-X Version 1.7 feedback

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,

Re: [wsjt-devel] r7329 breaks JTAlert

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.

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

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

Re: [wsjt-devel] Lock TX=RX

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

[wsjt-devel] Odd behavior

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

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

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

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

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

Re: [wsjt-devel] Rig control issue v6596

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

Re: [wsjt-devel] Rig control issue v6596

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

Re: [wsjt-devel] Gravitational Waves

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,

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

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

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

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

Re: [wsjt-devel] RR73 message button

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.

Re: [wsjt-devel] RR73 message button

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

Re: [wsjt-devel] [SPAM] Re: Re: RR73 message button

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