> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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
> 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.
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.
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
> 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
> 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
> 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
> 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
> 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
> 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
23 matches
Mail list logo
