Re: [wsjt-devel] Response to CQ ignored

> On Jan 30, 2024, at 04:45, Uwe, DG2YCB via wsjt-devel > wrote: > > At the moment, I have no explanation why it doesn't work with the "231202" i+ > version. What I can say is that it definitely works well with the current > "240106" code, as well as with the new "240202" version that will

Re: [wsjt-devel] Error with Watchdog Timer in FT8 Mode

> On Dec 3, 2023, at 09:22, Tim Goeppinger via wsjt-devel > wrote: > > In the band activity window "3B8CW N6GP DM13" was highlighted in red.When > I hit the "Enable Tx" button, my rig would not go into transmit mode. Had to > restart WJST-x to try again. Sounds normal. The timer has

Re: [wsjt-devel] FT8 on 160m with Beverage antenna

> On Nov 13, 2023, at 14:38, Dennis W1UE via wsjt-devel > wrote: > > beverage antenna will often produce weaker signals than, say, an inverted L. > However, it will decrease the noise on the signal, and make it easier to > copy, which > should make it easier to decode. Going a step

Re: [wsjt-devel] CQ Hound mode

> On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel > wrote: > > Just an idea: > > When in Hound mode the DX station should call as: > > CQH DX0CALL GRID > > or > > CH DX0CALL GRID But why? He should only be hound if he is on his published frequency (which you can determine

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

> On Oct 21, 2023, at 16:04, Andrew Neumeier via wsjt-devel > wrote: > > If I am working a very weak station, and that station chooses to use RR73 > instead of 73, there > is a good chance that I have not received it, especially if I am waiting for > a qsb peak on the signal. And that’s

Re: [wsjt-devel] Hamlib 4.5.2 test #hamlib

Sorry for the omission, Mike. Same version as previous. Running RC5 since it came out. > On Dec 20, 2022, at 21:23, Black Michael via wsjt-devel > wrote: > > What version of WSJT-X do you have? I'm running 2.6.0-rc5 and can switch > from FT8 to FT4 and back without a problem. > > Hamlib

Re: [wsjt-devel] Hamlib 4.5.2 test #hamlib

> On Dec 20, 2022, at 17:13, Dennis Younker NE6I via wsjt-devel > wrote: > > Hamlib 4.5.2 is due to be released this week. > All known bugs have been fixed. I don’t remember if this was Hamlib problem, or something else, but the decode problem has risen its head again on my system. I

Re: [wsjt-devel] RC4 crashes

> On Nov 23, 2022, at 21:58, Black Michael via wsjt-devel > wrote: > > Would that switch to FT4 be occurring while decodes are still appearing on > the screen? Probably while or before decodes are happening, since they come so fast with heavy activity. Gary - AG0N

Re: [wsjt-devel] RC4 crashes

> On Nov 23, 2022, at 13:54, Michael Black via wsjt-devel > wrote: > > Known bug if you are using max dust or call first. It’s fixed for RC5. > Mike W9MDB One more confirmation from my station, Mike. As previously stated, it is very repeatable. Go up on 17, 12, or 10 meters (probably

Re: [wsjt-devel] Program crash

> On Oct 24, 2022, at 11:46, Tony ZL3HAM via wsjt-devel > wrote: > >> I'm running Ver 2.6.0-rc4 on Windows 11 Pro and the program has just crashed >> for the second time and it needed a PC reboot to restore. At the time I was >> on 20m FT4 after having a few QSO's and it crashed whilst in

Re: [wsjt-devel] Possible RC4 issue

> On Sep 18, 2022, at 22:32, Reino Talarmo via wsjt-devel > wrote: > > This may be irrelevant, but how you returned from FT4 to FT8 to work the > single station? Reino, Sorry, I forgot to respond to this. I was only doing the mode change with the new mode buttons, not the mode drop

Re: [wsjt-devel] Possible RC4 issue

> On Sep 18, 2022, at 22:32, Reino Talarmo via wsjt-devel > wrote: > > This may be irrelevant, but how you returned from FT4 to FT8 to work the > single station? > >> When I tried to restart WSJT-X, it failed, giving me the following error: > Sub Process Error > Failed to

Re: [wsjt-devel] Possible RC4 issue

> On Sep 18, 2022, at 21:25, Black Michael via wsjt-devel > wrote: > > About how long were you running when this happened? If by “running” you mean the program was loaded and running, it runs 24/hrs a day. Since we are in lightning storm season, it was probably shut down and restarted the

[wsjt-devel] Possible RC4 issue

I seldom report problems that I might have because I don’t usually have enough notes on all the details, but this one seemed serious enough that I’ll tell you what I know about it. Can I duplicate? Of course not, yet. I’ve been using RC4 since it came out, so it's likely a one-off event.

Re: [wsjt-devel] Linux alert woes

> On Sep 7, 2022, at 13:29, Jody Barefoot via wsjt-devel > wrote: > > So I was wondering if the developers of WSJT-X would consider incorporating > the same kind of simple beep alerts that JTDX has. Sorry, brain didn’t register the Linux comment. I’ll crawl back in the hole. Apologies.

Re: [wsjt-devel] Linux alert woes

> On Sep 7, 2022, at 13:29, Jody Barefoot via wsjt-devel > wrote: > > So I was wondering if the developers of WSJT-X would consider incorporating > the same kind of simple beep alerts that JTDX has. That way we can add more beeps and boops to the Windows garbage that people are spewing

Re: [wsjt-devel] Watchdog timer for F/H?

> On Jul 28, 2022, at 14:04, Richard V Zwirko via wsjt-devel > wrote: > > Comments? You’re talking about defeating the timer, which is there for a reason. If you aren’t getting a response from the other station, give it a break and let someone else have a bit of a chance before you

Re: [wsjt-devel] SUGGESTION

> On Mar 6, 2022, at 02:56, Alan via wsjt-devel > wrote: > > it's an important feature because many XCVR's do not offer this function in > a simple manner. Put the radio in CW mode and lock the key. Simple. Gary - AG0N ___ wsjt-devel mailing

Re: [wsjt-devel] SUGGESTION

> On Mar 5, 2022, at 21:19, Gavin ZL3GAV via wsjt-devel > wrote: > > With the TUNE button, can this be limited to timeout at 10 seconds maximum > please? > > From experience, we all make silly mistakes, whilst tuning my FT-991A I got > distracted, with the result, I nuked the radio (since

Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!

> On Feb 19, 2022, at 14:51, Grant VK5GR via wsjt-devel > wrote: > > As for how to ID exactly what mode they are running…. Let’s be clear. You’re not talking about MODEs here. Logged mode is till FT8. You’re talking about protocol or format. The mode is still FT8. Gary - AG0N

Re: [wsjt-devel] Question FT8

> On Oct 4, 2021, at 13:09, Andrew Neumeier via wsjt-devel > wrote: > > This is a different situation than working strong signals on HF, where I > rarely operate FT8, so my experience is different. So, when another station > sends 73, and my station does not automatically respond, I'll

Re: [wsjt-devel] Question, FT8

> On Oct 4, 2021, at 07:18, Neil Zampella via wsjt-devel > wrote: > > When you send RR73, when the Tx Enable turns off, the operator has the OPTION > to click it back on, select the Tx5 message, and have it go out. > > See ... already implemented. Just takes TWO clicks. Yep, takes

Re: [wsjt-devel] Possible feature request, time skew notification?

> On Jul 18, 2021, at 09:26, Carey Fisher via wsjt-devel > wrote: > > If you simply look at the waterfall, it's clearly obvious whether your clock > is off or not. You and George are correct. Simply looking at the waterfall will get you within the two seconds required. After that, the df

Re: [wsjt-devel] Message Bit to Request Other Station to QSY to your Frequency

> On Jul 9, 2021, at 19:11, Jim Shorney wrote: > > I would like to see a defined DX window also. Despite the WSJT-X magic > ability to separate signals the DX is often buried under the "locals”. I suppose the “locals” aren’t working DX? JA and EU both prefer to be 1st, so I would assume

Re: [wsjt-devel] Message Bit to Request Other Station to QSY to your Frequency

> On Jul 9, 2021, at 9:54 AM, Al Pawlowski wrote: > > Though my rig can go to Hz rx BW and WSJTx v2.4.0 set to 6000Hz, 4500kHz > is all I can get - above that, decodes stop and the waterfall fills with > noise. I wonder if the limit is due to my CPU speed (usage increases with BW > and

Re: [wsjt-devel] WSJT-X - 2.4.0 startup screen handling

On Jul 8, 2021, at 4:51 AM, Bill Somerville wrote:you are the first to report that behaviour. What should happen, and does when I start WSJT-X, is a message about the number of worked before records discovered in your WSJT-X ADIF log is written to the status bar *in place*

Re: [wsjt-devel] Message Bit to Request Other Station to QSY to your Frequency

> On Jul 7, 2021, at 9:07 PM, Tim Goeppinger via wsjt-devel > wrote: > > On future releases of FT4 or FT8, if there is ever a spare bit in the message > formats, I propose adding a "please QSY to my tx audio frequency" bit. > There would be a "Pse QSY: button on the user interface that

Re: [wsjt-devel] Call for information about PC systems being used for WSJT-X

> On Jun 10, 2021, at 11:07 PM, Reino Talarmo wrote: > > You need to dig out the number after "i7-". That tells the actual > capabilities of the CPU. I got a feeling that the numbers below 1000 means no > AVX support, but higher numbers may also not support. So you need to check it > on

Re: [wsjt-devel] Call for information about PC systems being used for WSJT-X

Bill, I looked into what I’m running here and found it is a Gen 1 i7 2.67GHz from Intel. Basically says no features on the Intel site, and no mention of AVX or similar on that processor. Gary - AG0N ___ wsjt-devel mailing list

Re: [wsjt-devel] RC4 Watchdog anomaly

> On May 16, 2021, at 10:37, Rich - K1HTV wrote: > > Next, I tested the watchdog timer , calling the BD station using the Tx1 > message, By that time that station was much weaker. As I continued calling, > after about 2 minutes the WD counter decremented to 5. After another 2 > minutes,

Re: [wsjt-devel] WST4W-300 2.4.0-rc4

> On May 7, 2021, at 7:47 AM, Thomas Mills wrote: > > When I transmit on FST4W-300, wsjt-x only keys the radio for 180 seconds but > the RX/Tx box is still yellow in the transmit mode. I have even turned off > CAT and used VOX, but WST4W still sends an un-key to the radio after 180 >

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

> 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

Re: [wsjt-devel] WSJT-x Icom CI-V Issue?

> On Apr 22, 2021, at 6:56 PM, John Deegan wrote: > > In this environment, I am using a Tarheel antenna and a “TennaTronix” Tenna > Tuner-2 antenna tuner. I’m curious - why are you using an antenna tuner with a Tarheel? The antenna should be tunable to the exact frequency you are

Re: [wsjt-devel] dB report and actual bandwidth

> On Apr 11, 2021, at 8:30 PM, Andy Durbin wrote: > > This seems to imply that the noise being considered is the noise in the > actual receiver passband and not the total noise in a 2.5 kHz bandwidth. Andy - How is the program going to consider a frequency that isn’t being passed to it from

Re: [wsjt-devel] WSJT-X option request - RX Frequency

On Apr 8, 2021, at 17:24, Andy Durbin wrote:Yes,  ALL the stations who are calling me are RED. OK, I see where you are!  Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X option request - RX Frequency

> On Apr 8, 2021, at 8:09 AM, Andy Durbin wrote: > > I use the RX frequency pane to track the progress of my current QSO. Having > multiple callers who are attempting to interrupt my QSO also appear in the RX > Frequency pane is sometimes a significant distraction from tracking and >

Re: [wsjt-devel] JT65 message sequencing

> On Mar 25, 2021, at 8:22 AM, Andy Durbin wrote: > > My messages had to be manually selected for each transmission and there was > no "Auto Seq" selection displayed. Is this by design? My recollection is > that auto sequencing used to be possible with JT65. Hi Andy, JT65 has never had

Re: [wsjt-devel] Click on a CQ and Get the Wrong Station

> On Mar 5, 2021, at 18:32, Dennis Younker NE6I wrote: > > I am clicking on the station I want in the left pane (Band Activity). I assume you are DOUBLE clicking, not single clicking as you seem to be saying? Gary - AG0N ___ wsjt-devel mailing

Re: [wsjt-devel] Icom 7300 Split weirdness with 2.3.0 Oc42df

On Mar 4, 2021, at 19:55, David Garnier wrote:I solved my problem, by going into the Split Operation box and uncheck Rig to None.Just be sure that you always operate somewhere between 1500 and 2000 Hz with your transmitter.  There’s a reason for running “split”, and you have defeated it by saying

Re: [wsjt-devel] clock offset / fudge adjustment, automatic/manual

> On Mar 4, 2021, at 14:34, Sam W2JDB via wsjt-devel > wrote: > > Just as an FYI, one of the programs that I wrote and posted in the same > location as the Alltext.exe program > allows you to sync to internet time when the internet is available or to > manually adjust the time by user >

Re: [wsjt-devel] clock offset / fudge adjustment, automatic/manual

> On Mar 4, 2021, at 14:34, Sam W2JDB via wsjt-devel > wrote: > > Just as an FYI, one of the programs that I wrote and posted in the same > location as the Alltext.exe program > allows you to sync to internet time when the internet is available or to > manually adjust the time by user >

Re: [wsjt-devel] clock offset / fudge adjustment, automatic/manual

> On Mar 4, 2021, at 08:47, David Smith wrote: ... > 2) I'm not suggesting at all that WSJT modify the system clock. In fact, my > suggestion is that WSJT leave the system clock alone, and that we add a > feature that allows offset to the system clock. But why are you interested in working

Re: [wsjt-devel] WSJT-x2.3.0 Anwser problem

> On Feb 16, 2021, at 12:00, Adrian wrote: > > The problem I am having with v2.3.0 is the auto log popup sometimes not > working on the RR73 or 73, and a need to rework the station to get the > logging popup. The effect is random and not often. I started to notice mine doing the same, three

Re: [wsjt-devel] Green RX Mark

> On Dec 22, 2020, at 17:20, Pino Zollo wrote: > > Green RX Mark can not be set lower than 200Hzbut decodes a station at > 161Hz You have your waterfall control set to 200, so that’s as low as it goes. Gary - AG0N ___ wsjt-devel mailing list

Re: [wsjt-devel] Audio oddity

> On Dec 12, 2020, at 06:53, Black Michael via wsjt-devel > wrote: > > So all that's being done is turning off Monitor (by clicking the Stop button) > overnight and then enabling Monitor in the morning and it behaves like this > until restart. This won’t answer your questions, but I’m

Re: [wsjt-devel] "Tune" prevents "Tx Next" from transmitting in next cycle

> On Oct 9, 2020, at 07:36, Gene wrote: > > To reproduce: > - Select FT8 mode > - Press and release "Tune" > - Activate Tx 6 message that displays "CQ callsign grid" and then click > either "Next" or "Now" > -> It will not transmit in the immediate transmit cycle and has to wait a > cycle

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

> On Aug 19, 2020, at 02:21, Stephen VK3SIR wrote: > > > -- > > Why has the stream been decoded (good) and the logic allowed it to be > identified – displayed - as coming

Re: [wsjt-devel] FT8: Double Click, sometimes wrong CallSign

> On Jun 29, 2020, at 11:25, Reino Talarmo wrote: > > Sometimes I try to answer a CQ with a double click in the Band Activity Part > - but not the station is used, which I had selected. More than likely, you are a victim of the multiple decoding cycles per 15 second sequence. The screen

Re: [wsjt-devel] Field Day Frequencies

> On Jun 23, 2020, at 20:09, Matthew Miller wrote: > > For ARRL Field Day 2019, I recall there was a different set of frequencies > used for FT8. > > Does anyone know if there will be a de-facto set of frequencies to use for > Field Day 2020 for FT8, and also for FT4? Or the default

Re: [wsjt-devel] wsjt-devel Digest, Vol 76, Issue 93

> On Jun 9, 2020, at 07:39, Steven Franke via wsjt-devel > wrote: > > What are your typical DT values, i.e. what is the median DT value for a cycle > that has a good number of decodes? Normally, we expect to see the bulk of > the decodes produced by the first decoding segment (say, 80%)

Re: [wsjt-devel] FT8: Double Click on entry in Rx Frequency only set the own Rx frequency

> On May 30, 2020, at 07:53, roland.hartm...@web.de wrote: > > In all other cases where I was not named as receiver Rx and Tx frequency are > changed. You should check the HOLD TX box so the transmitter does NOT shift. You should not call on the other station’s frequency. Pick a clear

Re: [wsjt-devel] FT8 with click anomaly

> On May 28, 2020, at 12:33, Andy Durbin wrote: > > The linked WAV file was captured by, and edited in, Audacity. It does not > replay in WSJT-X. > > https://tinyurl.com/y8ehtrkd I don’t have a definitive answer, Andy, but have heard that myself now and then. I sometimes chalk that sort

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

> On May 20, 2020, at 10:28, Neil Zampella wrote: > > The 73 from you is a courtesy ... the RR73 is saying "Roger Roger - > BYE'"basically ... we're good.This is why the program then > switches to the Tx6 to send the next CQ call. If you call letting him know that you got his

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

> On May 19, 2020, at 10:05, Neil Zampella wrote: > > .. someone sending an RR73 does not expect a reply, the last 73 is a > courtesy from you the answering station. I certainly do, in order to let him know I got his RR73 and he needs to sen nothing else. If I don’t send 73, I expect him

Re: [wsjt-devel] 2.2.0 RC1 PTT issue

> On May 18, 2020, at 12:39, Joe Taylor wrote: > > Since we're trying to avoid confusion, let's get this right. > > The "Wide Graph" -- also called the Waterfall -- is used for FT8 and other > slow modes. The "Fast Graph" is used for MSK144 and other fast modes. THANKS, Joe! Boy, that

Re: [wsjt-devel] 2.2.0 RC1 PTT issue

> On May 18, 2020, at 10:21, Dave K1SX wrote: > > Hoping to try it on 6 meters soon, awaiting decent propagation. Forgot to mention, six has been open almost every day. Early afternoon there’s a lull, but still some signals. Picks back up again late afternoon and has been running right up

Re: [wsjt-devel] 2.2.0 RC1 PTT issue

> On May 18, 2020, at 10:21, Dave K1SX wrote: > > I'm trying to get a handle on occasional cycles with no decodes at all > (plenty of clean signals on wide graph). To avoid confusion, know that the wide graph is used on MSK144 but not on FT8. FT8 uses the waterfall display, which is

Re: [wsjt-devel] Green goalie not moving to the RX freq

> On Apr 25, 2020, at 15:19, Andy Durbin wrote: > > Shouldn't the RX frequency cursor move to the caller's frequency as soon as > WSJT-X has decided this is the "first caller" and starts to auto-sequence the > QSO?” No, you’re right. I didn’t follow the link. I happen to agree with you on

Re: [wsjt-devel] Green goalie not moving to the RX freq

> On Apr 25, 2020, at 11:43, Andy Durbin wrote: > > "When I CQ and someone calls me the Green goalie does not auto move to his > freq " > > I think I reported this a long time ago. The anomaly has certainly been > there for a long time. It does not seem to be consistent though and perhaps

Re: [wsjt-devel] Green goalie not moving to the RX freq

> On Apr 24, 2020, at 16:42, Edward stallman wrote: > > Shouldn't the Green Goalie move to there QRG when they call me ? I believe the answer to that is “only if you double click on them to respond to them”. I may be wrong on that. I’m not sure what difference there might be if Call 1st

Re: [wsjt-devel] JA will operate on 160m and 80m at WSJT Default Frequency from Today

> On Apr 21, 2020, at 01:54, Tsutsumi Takehiko wrote: > > Today, Japanese radio regulation authority officially published the expansion > of 160m and 80m That’s great news, Take! Thank you for passing it along to us. Gary - AG0N ___ wsjt-devel

Re: [wsjt-devel] Optimum computer for WSJT-X?

> On Feb 8, 2020, at 08:25, Alex wrote: > > Quite impressive for such a little computer. I have a model 4 with 4GB but > haven't tried that one yet. What does it do on MSK144 with FTOL 200 and Decode set to Deep? Gary - AG0N ___ wsjt-devel

Re: [wsjt-devel] K1JT?

> On Jan 1, 2020, at 05:59, Joe Taylor wrote: > > Alive and well, here Happy New Year to your and yours, Joe. 73, Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split mode settings

> On Dec 23, 2019, at 04:43, Tom Ramberg via wsjt-devel > wrote: > > I have used this way of doing it with FT1000MP, FT1000MP MarkV and FTdx3000 > operating as JW6VDA, and a similar setup also works with my IC7300 from my > home station, OH6VDA. Originally I was put on the right track by

Re: [wsjt-devel] 160m

> On Dec 18, 2019, at 10:49, OG55W wrote: > > However QSOs with JA-stations are going OK. > Every now and then RX will jump to 1840. That’s why I have a specific CONFIGURATION for 160/JA that takes care of it. Configure it and don’t worry about it anymore. When wanting to return to

Re: [wsjt-devel] Callsign lockout

> On Dec 2, 2019, at 19:57, Carey Fisher wrote: > > That's ridiculous. A "block" wouldn't keep a station from transmitting, just > from being displayed. Can't you just ignore it? Exactly. Blocking your program from showing him won’t do a thing about the way his signal affects your receiver

Re: [wsjt-devel] Problem with radio's audio input

> On Dec 2, 2019, at 10:06, Paul Randall wrote: > > It may be unrelated but a station very local to me on 2m transmits a huge > wideband splat of noise at the start of his FT8 transmissions. I think what I > am hearing is all the noise in his shack, the fan in his qro linear etc, all >

Re: [wsjt-devel] Callsign lockout

> On Nov 30, 2019, at 15:15, Black Michael via wsjt-devel > wrote: > > What is needed is the ability to block a callsign for an adjustable time out > period defaulting perhaps to 15 minutes. I’m curious why you use Call 1st anyway. I never use it and have never found a use for it. I want

Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator

> On Nov 21, 2019, at 16:55, Carl Buehler wrote: > > How long does it take, after making the request, to be taken off this list? > K9ZA Should be immediate right after you REMOVE YOURSELF. Gary ___ wsjt-devel mailing list

Re: [wsjt-devel] Rx Frequency window

> On Aug 4, 2019, at 14:41, Gary McDuffie wrote: > > However, I would make a modification to the above idea so that it would only > not show calling stations while not in QSO. Hopefully you understand that the double negative should not be ther

Re: [wsjt-devel] Rx Frequency window

> On Aug 4, 2019, at 08:32, Al Pawlowski wrote: > > This has not been a problem for me, but I can see where it might be for > others. Seems like a good candidate for a user selectable preference - only > show QSO partner calls. If the preference were added, however, it would > probably be

Re: [wsjt-devel] GMSK waveform generation details

> On Jul 17, 2019, at 07:33, Joe Taylor wrote: > > The second plot shows examples of FSK and GFSK versions of FT8, captured from > on-the-air signals. Congratulations, Joe. I’m watching 17m signals right now on FT4 and they are MUCH cleaner looking than what we’ve seen on FT8. Good

Re: [wsjt-devel] WSJT Audio Input Loss

> On Jul 3, 2019, at 15:52, Hasan al-Basri wrote: > > Any further ideas are most welcome (TS-590sg, running from headphone jack for > rx audio) Audio sounds perfect to the ear. Levels are right... > Most peculiar! Hasan - As you probably remember, when you uninstall and reinstall, the old

Re: [wsjt-devel] AF Mute

> On May 12, 2019, at 10:05, Black Michael via wsjt-devel > wrote: > > I am referring to RIG_LEVEL_AF and though it may not be implemented on all > would be a nice feature for those rigs that can which is quite a few. I’m still at a loss to understand what you want to mute. X doesn’t

Re: [wsjt-devel] JTDX Audio Input 100 %

> On May 10, 2019, at 09:04, Jason Peardon wrote: > > Lower it until the scale in WSJT-X is around 60% consistently. That should be 30 on the audio meter in WSJT-X when tuned to a clean frequency and just listening to white noise. Gary - AG0N

Re: [wsjt-devel] Suggestion for Additional Checkbox

> On Apr 20, 2019, at 15:46, Frank Kirschner wrote: > > Between the Hold Tx Freq checkbox and the Call 1st checkbox, there is room > for several more checkboxes. One I would suggest is Fox/Hound mode. I would > also suggest this automatically set Split to either Rig or Fake It, which >

Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

> On Apr 3, 2019, at 13:28, Gary Hinson wrote: > > [In just a few years when propagation is better and the FT8 frequencies > become crowded, auto-responding to the weakest callers first will make even > more sense.] I’ve wanted this feature for a long time. Not necessarily the

Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

> On Mar 31, 2019, at 17:02, Jim Shorney wrote: > > The guy seems to be on the air making FT8 contacts just about every time I > turn it on Must be CO8LY (I think that’s his suffix). I see him on the air every time I walk into the shack. I suspect that the Antarctic station that was

Re: [wsjt-devel] Cosmetic request on frequencies list

> On Mar 25, 2019, at 15:00, Don AA5AU wrote: > > Making default frequencies bold type so they can be easily found when > scrolling through the list would be a nice addition. As previously mentioned, you should be using configurations to manage this. There should be NO frequencies listed

Re: [wsjt-devel] PWR slider & TUNE

> On Mar 16, 2019, at 12:25, Black Michael via wsjt-devel > wrote: > > That should depend on what you have selectedsounds like you have Tune > selected but not Transmit. What happened to the idea that the TX Level should always be left at maximum (top). That was drummed into us at

Re: [wsjt-devel] Automatic QSY on 160m!!

> On Mar 6, 2019, at 14:05, Bill wrote: > > I'm sure this must be a useful feature somewhere but it seems a bit dangerous. Indeed, it IS a feature. However, I believe it should be disabled when operating on HF. It is used “daily” on VHF, where a station may call CQ on a busy frequency

Re: [wsjt-devel] F/H, hound unable to transmit on even times!

> On Mar 4, 2019, at 14:03, Bill Frantz wrote: > > If there are not significant problems, then I suggest wsjt-x do just that. Better yet, they should be on a separate frequency, not operating the normal FT8 segment. They are taking up just as much space and causing just as much confusion

Re: [wsjt-devel] VFO-B behavior

> On Mar 3, 2019, at 13:52, Black Michael via wsjt-devel > wrote: > > On ICOM rigs hamlib assumes split is always on VFOB to cover rigs without > status commands...as does FLRig (and perhaps others). Kenwood is the same way, and I’m not sure I would want to alter that. Gary - AG0N

Re: [wsjt-devel] PJ4P Operation

> On Jan 23, 2019, at 13:34, John Zantek wrote: > > Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe I’m > missing something obvious, but…. > > It LOOKS they’re operating as a Fox, but on the conventional FT8 frequencies. Saw the same thing this afternoon. I think

Re: [wsjt-devel] Required duplication feature

> On Jan 22, 2019, at 14:32, Hasan al-Basri wrote: > > If it turns out to be "safe" to do the Admin install, I'll give it a try. Hasan: For what it’s worth, every computer I’ve ever had has been used completely as administrator, except my IRLP node (Linux), and my MacBook. I don’t have

Re: [wsjt-devel] Short Tx inhibits decode...

> On Jan 21, 2019, at 13:19, Paul Kube wrote: > > yes; but letting auto seq run works just fine most of the time. Toggling > Enable off only to toggle it on at the beginning of the next cycle is very > often superfluous. Don’t forget - it is fine to start several seconds late in the

Re: [wsjt-devel] Short Tx inhibits decode...

> On Jan 17, 2019, at 15:04, Paul Kube wrote: > > Which might be easier than modifying the decode code to handle starting late > in a cycle, I don't know. I’ve tested and know that you can miss the first 5 seconds of an incoming transmission and still decode it fine if they have a decent

Re: [wsjt-devel] Short Tx inhibits decode...

> On Jan 17, 2019, at 13:57, Paul Kube wrote: > > For example, say I'm CQing on even cycles. After a couple, I decide I want to > stop CQing if I don't get any replies, so I hit Halt Tx as soon as I see the > list of decodes from a just-finished odd cycle. Maybe I am transmitting for a >

Re: [wsjt-devel] Operation below 200 Hz

> On Jan 16, 2019, at 05:34, Chris Deacon wrote: > > As a matter of interest, Bill, why has the software been written not to allow > TX below 200 Hz? I've always wondered. There’s a setting on the waterfall controls that sets the lower limit. I have mine set at 100 and don’t seem to have

Re: [wsjt-devel] RTTY RU Contest Name FT8-RU

> On Jan 6, 2019, at 23:13, Edfel Rivera wrote: > > Seems I missed resetting title. Any idea how to change Contest name and what > is the correct contest name. Previous to the contest I reset log but name of > previous contest is still there. I’m not sure the title change is all it needs.

Re: [wsjt-devel] fyi

If you want someone to click that link, you should put some explanation for what it is to convince people that it is legit. I know very few people who would click such a link without knowing what to expect to see there. Wouldn’t touch it with YOUR ten foot pole, much less mine. Gary - AG0N

Re: [wsjt-devel] Possible bug in V2 GA ?

> On Dec 31, 2018, at 15:06, Chris Getman wrote: > > And why would I want stations to queue up on his frequency? Actually, no one should be transmitting on his frequency, but some insist on it anyway. Lock the TX, find a clear frequency, and call him there. Gary - AG0N

Re: [wsjt-devel] Unwanted response (bug)

No explanation for this I guess. Gary - AG0N > On Dec 24, 2018, at 06:25, Gary McDuffie wrote: > > As previously mentioned, I almost always call directional CQ. This morning > on 160m, I was calling CQ DX when a stateside station called me. Happens all > the time. What d

[wsjt-devel] Unwanted response (bug)

As previously mentioned, I almost always call directional CQ. This morning on 160m, I was calling CQ DX when a stateside station called me. Happens all the time. What doesn’t normally happen is I return his call and send him a report. I did NOT instigate that call to him. The receive

Re: [wsjt-devel] grid square & nonstandard callsign

> On Dec 21, 2018, at 09:44, DX Jami via wsjt-devel > wrote: > > can extra bits be obtained by omitting the worked station's call sign? This can really cause problems when trying to confirm that the report is from the station you think it is from. The idea is to make sure you don’t get a

Re: [wsjt-devel] grid square & nonstandard callsign

> On Dec 21, 2018, at 10:27, Bill Somerville wrote: > > nevertheless sending a grid without the /W4 suffix may still be the best > option if it is legal to do so. And, as others have done, sending free text occasionally with the added info for those who bother to read would help. Gary -

Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

On Dec 13, 2018, at 19:26, Bill Somerville wrote:this is not correct, don;t do that. The Rx offset goes your QSO partners frequency for two reasons, firstly because that directs messages decoded at that offset to the Rx Frequency decodes window, and more importantly the decoder tries first and

Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

> On Dec 13, 2018, at 18:52, Bill Somerville wrote: > > The Rx audio offset is automatically moved to a station you choose to answer > when you double-click their decoded message. I’ve been thinking of commenting on this action myself. I’m glad someone else brought it up. While my desires

Re: [wsjt-devel] Calling CQ then selecting dB

> On Dec 9, 2018, at 14:18, WB5JJJ wrote: > > He's flying kinda blind by using Tab 2 apparently. The attachment showed he was using Tab 1. Agree everyone should be using Tab 1 (I know, I know). :) Gary - AG0N ___ wsjt-devel mailing list

Re: [wsjt-devel] Calling CQ then selecting dB

> On Dec 9, 2018, at 10:33, SKI W4PPC wrote: > > When calling CQ and a station sends their call sign plus grid, I select dB > button and the system replies to the station I had contact with > previously...only until I select the caller's call sign in the Band Activity > window the reply

  1   2   3   >