Saw mention of this issue, with newbies calling a DX target on same
timeslot by just enabling a call without clicking
a received report from the target.
If a sent call can be detected in software to be on same timeslot as the
target, then could a auto stop possibly
with error message be
On 10/15/2022 2:13 AM, Saku via wsjt-devel wrote:
Linux has Wine, but I do not have any need to run Windoze programs via it.
It seems that you might need it. You're asking for features to be added
to WSJT-X that are in Windows software. An operating system is a tool,
not a religion. Or
HI Larry!
I am a Linux user.
I worked last 15 years with Windoze servers and clients versions up to
W7. When retired I do not have any need to touch them any more. Linux
has Wine, but I do not have any need to run Windoze programs via it.
Cqrlog has it all. And what it does not have I can
You might want to take a look at the WSJT-X_IMPROVED version by DG2YCB - you can
label the contest names however you want. GL and VY 73, Lance
On 10/14/2022 08:29:59, Saku via wsjt-devel wrote:
Hi!
Sorry if this feature exist. I did not find a mention about it from user guide.
There are now
Hi Saku,
It is much easier to use a proper contest logging program. There are
many out there. I use the programs from N3FJP -- they are easy to set
up and use. They do everything you need.
Larry / W1DYJ
On 10/14/2022 4:29, Saku via wsjt-devel wrote:
Hi!
Sorry if this feature exist. I
There is a CONTEST_ID ADIF field. But NAC-6M is not one of the enumerations.
Does is need to be added or is there another name for
it?https://adif.org/313/ADIF_313.htm#Contest_ID
As for date doesn't the QSO date do the job?
Mike W9MDB
On Friday, October 14, 2022 at 03:39:13 AM CDT, Saku
What incorrect name is being sent? Can you show an example?
Mike W9MDB
On Friday, October 14, 2022 at 05:41:48 AM CDT, Saku via wsjt-devel
wrote:
HI Jim!
No Windozes in house.
I use Cqrlog for logging and at the moment WSJT-X is sending a contest
name in UDP logging frame to
HI Jim!
No Windozes in house.
I use Cqrlog for logging and at the moment WSJT-X is sending a contest
name in UDP logging frame to Cqrlog that can not be defined.
That's why I always need to fix contest names of FT8 qsos afterwards
with Cqrlog's group edit to be similar with all other modes
Hi Saku,
There are logging programs that keep track of contests. I log contests
with N1MM+ (Freeware), export the log to DXKeeper (FREEware), choose
from a dropdown menu in the DXKeeper Import screen what contest it's
from and choose the log file. That's all it takes! And when you're ready
Hi!
Sorry if this feature exist. I did not find a mention about it from user
guide.
There are now several contests that use WSJT-X contest modes. It would
be nice to have user defined contest name to logging window.
That way name logged (also via UDP message) could be set by contest. And
Hi Jim,
On 7/28/22 22:54, Jim Shorney via wsjt-devel wrote:
> I've never had to use shift. Just prtsc by itself brings up Spectacle and
> I've never had issues with it.
For whatever reason, that doesn't work when the save menu is open...
73
Stan
KM4HQE
I've never had to use shift. Just prtsc by itself brings up Spectacle and I've
never had issues with it.
73
-Jim
NU0C
On Fri, 29 Jul 2022 03:41:00 +
Stan Gammons via wsjt-devel wrote:
> No idea why I
> can't do a shift print screen to do a screen capture with the save menu
> open in
Windows key Shift S
On Thu, Jul 28, 2022, 10:45 PM Stan Gammons via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hi Jim,
>
> Welcome.
>
> I found out the reason a screen capture seem to jack up my Kubuntu 20.04
> machine it was due to a low battery in my wireless mouse. No idea why I
Hi Jim,
Welcome.
I found out the reason a screen capture seem to jack up my Kubuntu 20.04
machine it was due to a low battery in my wireless mouse. No idea why I
can't do a shift print screen to do a screen capture with the save menu
open in WSJT-X...
73
Stan
KM4HQE
On 7/28/22 22:26, Jim
Thanks Stan.
73, Jim
On 7/28/2022 5:12 PM, Stan Gammons via wsjt-devel wrote:
On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:
Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file grows so
To: WSJT software development
Cc: Jim Brown
Sent: Thu, Jul 28, 2022 7:38 pm
Subject: [wsjt-devel] Feature Request
Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file grows so large that it cannot
be active while WSJT-X is active
and can display a selected number of records from the All.txt file while WSJT-X
is appending to it.
73,
Sam W2JDB
-Original Message-
From: Jim Brown via wsjt-devel
To: WSJT software development
Cc: Jim Brown
Sent: Thu, Jul 28, 2022 7:38 pm
Subject: [wsjt-devel
On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:
> Please provide an option to start a new ALL.TXT for each calendar month,
> keeping each month's file and naming it by the month. Without that
> option, the file grows so large that it cannot be opened by any software
> on my computer.
>
> 73, Jim
Jim,
That feature is in the new release candidate and works well..
—Dennis NE6I
> On Jul 28, 2022, at 4:40 PM, Jim Brown via wsjt-devel
> wrote:
>
> Please provide an option to start a new ALL.TXT for each calendar month,
> keeping each month's file and naming it by the month. Without
Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file grows so large that it cannot be opened by any software
on my computer.
73, Jim K9YC
___
WSJT-X is a GREAT program and I tremendously enjoy it! However, one small
change in FT-4 and FT-8 (and potentially other modes) would make it easier to
pick out desired callsigns.
In the display of FT-4 and FT-8 signals, the callsign of the intended station
is shown first, as it should be,
Thank you Bill, Neil, and James for helping make my earlier point. Open
source code allows a station to completely customize the U.I. for their
style of operations. So for those that are on the fox/hound hunt and
desire the checkbox in a specific location for their operations, simply
move it
Grant,
I have no idea where you got the idea that I said a 'clear frequency'
doesn't matter, not sure that James said anything of the sort
either. You always check for a clear spot to Tx from, no matter
what mode or special contest activity you're using. For Fox/Hound,
you wait one
-Original Message-
From: James Shaver (N2ADV) [mailto:n2...@windstream.net]
Sent: Monday, 11 October 2021 11:58 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Feature Request: Hound Mode
"Not sure where in fantasy land you had these conversations but the dev list
“ 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
>
On 10/11/2021 2:22 AM, Bill Somerville via wsjt-devel wrote:
that space is basically an illusion. The reason is that the main window
layout is largely shared by all modes and variants, the exceptions to
that are WSPR, FST4W, Frequency calibration, and EME Echo mode. What
appears to be empty
On 11/10/2021 08:45, Jim Brown via wsjt-devel wrote:
On 10/10/2021 11:02 PM, Peter Sumner via wsjt-devel wrote:
Rather than extra buttons / tick boxes on the existing busy screen
I hardly see the FT8/FT4 main screen as "busy" -- indeed, I see plenty
of empty real estate for these two tick
Jon,
that was an attempt to defeat some of the more trivial robot stations,
unfortunately the mass opinion was that it was a misfeature so perhaps
everyone is quite happy for the FT8 sub-bands to gradually fill with
unattended robot operations?
73
Bill
G4WJS.
On 11/10/2021 03:48, Jon
On 10/10/2021 11:02 PM, Peter Sumner via wsjt-devel wrote:
Rather than extra buttons / tick boxes on the existing busy screen
I hardly see the FT8/FT4 main screen as "busy" -- indeed, I see plenty
of empty real estate for these two tick boxes with labels (or buttons
with labels within the
for the F/H - Contest brigade
Rather than extra buttons / tick boxes on the existing busy screen for a
dedicated group of users, would a small pop-out window like that used for
the Astronomical data display be a better proposal?
I know its a bit of a radical shift of thinking and of course would
Jim,
FYI - Neil and James don't believe a clear frequency matters based on past
conversations I have had with them. I contend they have never tried chasing
DX where every path starts at 8000 miles (ie out of VK). The standard FT8
channels are so congested these days that trying to target working
On 10/10/2021 7:12 PM, Neil Zampella via wsjt-devel wrote:
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.
Well said, Grant. From where I sit, very active on 6M, and both DX
chasing and contesting on HF and MF, the only poor decisions made by by
the design team are based on their lack of broad experience below VHF.
That's the only possible explanation for how 40M FT4 ended up where it did.
Your
This seems like similar logic to that that led to the ill-conceived "move
the log-it button randomly" feature.
On Sun, Oct 10, 2021 at 10:45 PM James Shaver (N2ADV) via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> The check box used to be on the main screen of the UI and people kept
>
d 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.
>>>>
>>>>
WSJT software development
<mailto:wsjt-devel@lists.sourceforge.net>
*Cc:* Jeff Stillinger
<mailto:kb6...@zohomail.com>
*Subject:* Re: [wsjt-devel] Feature Request: Hound Mode
Not exactly a secret. For building on Microsoft virus, the sdk
is located here:
t;
> --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
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
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:
https://sourceforge.net/projects/jtsdk/
It is my understanding that it's going through some updates
Not exactly a secret. For building on Microsoft virus, the sdk is
located here:
https://sourceforge.net/projects/jtsdk/
It is my understanding that it's going through some updates, but what is
posted should work. Last time I played with it was back in version
1.7. I haven't kept up with
Hi Jeff,
Yes, I agree - I am a contributor to some other open source projects.
Thanks for your helpful suggestion.
I've given that some thought, but at least the last time I looked the build
process / toolkit for building WSJT-X on Windows is like top secret or
something, and I haven't spent any
How about an alternative to your prediction. WSJT-X is open source.
You have complete access to the source code, and one of the wonderful
conveniences of the package is the ability to customize the software to
a specific style of station operations.
That is the fancy and PC way to say, if
I know that this is going to get ignored, or I'm going to be told to "make
a configuration" to "solve" this problem, but I'll again put in a vote to
have a Hound mode checkbox on the main screen to switch in and out of that
mode.
There are several DXPeditions right now, some running Fox/Hound
Sorry for multiple emails, but I meant to add: this would highlight any
decodes from that callsign, not just CQs.
Thanks & 73
On Tue, May 25, 2021 at 11:42 AM Jon Anhold wrote:
> I think it would be useful if there was a way to configure highlighting of
> decodes matching the callsign
I think it would be useful if there was a way to configure highlighting of
decodes matching the callsign currently in the DX Call box.
For example, you see a spot for KM8V on 18.100 so you tune to that
frequency. You pop KM8V into the DX Call box, and in the Band Activity
window, if you are
at 12:01 AM
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Feature request: Rx level input slider
Have you tried this setting? Seesms reducing this should work.
LIN OUT NOR 010
Sets the LINE OUT level. LINE OUT connections go to PC soundcard inputs.
Settings
On 3/14/2021 9:58 PM, Black Michael via wsjt-devel wrote:
Sets the LINE OUT level. LINE OUT connections go to PC soundcard inputs.
Settings above 10 may result in overdrive of the soundcard or saturation
of the
KIO3’s isolation transformers; monitor signals using the PC to avoid this.
Great
Have you tried this setting? Seesms reducing this should work.
LIN OUT NOR 010 Sets the LINE OUT level. LINE OUT connections go to PC
soundcard inputs.Settings above 10 may result in overdrive of the soundcard or
saturation of theKIO3’s isolation transformers; monitor signals using the PC to
On 3/14/21 at 12:32 PM, g4...@classdesign.com (Bill Somerville) wrote:
>the only input level WSJT-X has access to is in the digital
>domain, i.e. after the soundcard ADC, that means it cannot make
>any useful adjustment if the level is too high. The level
>adjustment must be made in the analog
You wrote:
“Tx slider seems unnecessary because every radio (correct me if wrong) allows a
Tx or drive level reduction on the radio itself).”
That is very much not the case. Many rigs require a different drive level per
band, something that WSJTX handles perfectly.
> On Mar 14, 2021, at
On 14/03/2021 16:25, David Schmocker wrote:
Dear WSJT-X development team:
Feature request:
Could we eliminate the Tx Power slider (lower right of main screen)
and replace it with an Rx input level slider (far lower left of screen
immediately adjacent to the Rx dB level) to allow attenuation
Re: David Schmocker
> Tx slider seems unnecessary because every radio (correct me if wrong) allows
> a Tx or drive level reduction on the radio itself).
By that argument, you could as well put an attenuator into your
antenna line to have the RX level reduced to what you wanted.
Christoph
Dear WSJT-X development team:
Feature request:
Could we eliminate the Tx Power slider (lower right of main screen) and replace
it with an Rx input level slider (far lower left of screen immediately adjacent
to the Rx dB level) to allow attenuation of input Rx signal please?
More
Hello Frank,
JTalert is apparently Windows only...so doesn't work for me
jeff, wa1hco
On Sun, Feb 14, 2021 at 12:43 PM Frank Birch wrote:
> If you use helper JTalert
> View mode activity window F9
> All responses scroll through continuously. You can adjust the size of the
> window to
If you use helper JTalert
View mode activity window F9
All responses scroll through continuously. You can adjust the size of the
window to acclimate many cycles Of decode - continuously.
I use this all the time.
Of course JTalert has many other useful features.
Frank
VE3FBZ
> On Feb 14, 2021,
Hello Alan,
WSJT knows what is in the log, but...
- doesn't know if the grid is confirmed, about 20% of my logged grids
are not confirmed, so still needed
- only highlights stations calling CQ.
- More and more I need to "tail end" a station after is finishes an
ongoing QSO
-
Hi, use the colour highlighting settings? There are options in there for
grids not already in the log, and also grids not in the log by band.
Alan G0TLK
On 14/02/2021 16:48, jeff millar wrote:
Hello all,
Sometimes I need to search the Band Activity list for a specific
station who is known
Hello all,
Sometimes I need to search the Band Activity list for a specific station
who is known to be on the air. That is not easy to do.
- the list scrolls a lot every 15 seconds
- the transmitting station callsign is not aligned in columns and hard
to visually search
My current "thing"
February 9, 2021 at 5:00 AM
*To: *
*Subject: *Re: [wsjt-devel] #Feature request. 2.4.0
On 09/02/2021 03:54, Hattori, Yoshihisa wrote:
Hi all.
I am testing Q65 and realized that we are missing Short hand
indicator on waterfall display, which is provided for JT65. (three
yellow lines
: [wsjt-devel] #Feature request. 2.4.0
On 09/02/2021 03:54, Hattori, Yoshihisa wrote:
Hi all.
I am testing Q65 and realized that we are missing Short hand indicator on
waterfall display, which is provided for JT65. (three yellow lines suggesting
the RO/RRR/73 tones.) While less Q65/QRA64
On 09/02/2021 03:54, Hattori, Yoshihisa wrote:
Hi all.
I am testing Q65 and realized that we are missing Short hand indicator
on waterfall display, which is provided for JT65. (three yellow lines
suggesting the RO/RRR/73 tones.) While less Q65/QRA64 users are using
shorthand, it is good to
Hi all.
I am testing Q65 and realized that we are missing Short hand indicator on
waterfall display, which is provided for JT65. (three yellow lines suggesting
the RO/RRR/73 tones.) While less Q65/QRA64 users are using shorthand, it is
good to have those since Sh will not be decoded and users
I used FT4 over the RU weekend contest when RTTY dropped down and found it
fun -- EXCEPT for one thing. It kept calling a station that was only
calling CQ and very seldom answering any calls when Best S+P was
activated. I had no way to ignore this station (and others) except to turn
off Best S+P
Hi,
a feature request - maybe as function which can be deactivated for enhanced
OMs :
In FT4/FT8 stay on Tx5 if a call is answered. As least if Tx-Frequency is
the same than Rx-Frequency.
Think they are new users of WSJT-X who are answering a CQ and pressing
directly afterwards "Enable Tx".
If
Monday, July 20, 2020 12:46:50 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Feature Request
Thank you Bill (And Bill) - that worked great and does exactly what I was
looking for! (In fact, I can feed it to Python's simple webserver and watch
for DX from anywhere... :)
I'm also
it can drive my network aware antenna switches etc. 73, and thanks! --al WB1BQE
Original Message
Subject: Re: [wsjt-devel] Feature Request
From: Bill Somerville <g4...@classdesign.com>
Date: Mon, July 20, 2020 12:59 pm
To: wsjt-devel@lists.sourceforge.net
On 20/07/2
On 7/20/20 at 12:59 PM, g4...@classdesign.com (Bill Somerville) wrote:
On 20/07/2020 17:29, alaw...@mudhawk.com wrote:
...> >
2) My second feature request is to allow certain callsigns
to be excluded from the list of stations that are displayed
during decode. The use case here is that on
On 20/07/2020 17:29, alaw...@mudhawk.com wrote:
HI Folks,
I've been lurking in read-only mode for a while here, and just
upgraded to 2.2.2 up on my Atomic-Pi. Building the code was simple
and all works well.
I was wondering if I could ask for 2 feature requests as time
permits, please?
HI Folks, I've been lurking in read-only mode for a while here, and just upgraded to 2.2.2 up on my Atomic-Pi. Building the code was simple and all works well. I was wondering if I could ask for 2 feature requests as time permits, please?1) user_hardware: (I understand this is currently
On 29/06/2020 03:47, Jim Brown wrote:
There are times when it could be quite helpful to be able to switch
special operating features on and off from the main operating window.
One of those times occurred this weekend, when I wanted to be able to
switch between FD messages to work FD stations
There are times when it could be quite helpful to be able to switch
special operating features on and off from the main operating window.
One of those times occurred this weekend, when I wanted to be able to
switch between FD messages to work FD stations and normal mode to work
DX stations. My
Hello Development team,
while I know any QSO automation features are out of the question I would
like to ask that a 'dead band beacon' be considered for some future release
of WSJT-X.
My thought process sort of goes along these lines.
Enable Deadband beacon option tick box, and set "enable.
In the Band Activity window, I have the option set to insert a separator
line between decode periods.
Working the VHF contest this weekend, I've come across something that I
think would be a "nice to have".
The separator line only appears when there are actual decodes to display in
the band
It seems that having WSJT-X send the the new RX frequency to both VFOs
when a band change happens would be the simplest solution. The user could
then hit the TUNE button while still in split mode, get a match, then set
up the split TX freq on the other VFO...
Another option would be for the user
Well I found what was preventing me from building wsjtx (qt5-5.14.0 on Arch
seems to have introduced the issue, rolling it back to qt5-5.13.2 got me
back in business)
But that change I thought might implement the behavior I'm hoping for
didn't do the trick. I'll keep poking at it, but I'm not
Unfortunately something broke my build toolchain so I can't poke around at
testing a change myself until I have time to find out what broke it, but I
suspect this might have something to do with setting next_state_.split in
PollingTransceiver::do_post_frequency (PollingTransceiver.cpp:80)
On
Re: W5MMW Matt Manjos 2020-01-07
> - User chooses to QSY to 160m band via the drop-down in WSJT. Their 40m
> antenna will not tune to 160m, so they need their rig to be ready to send
> RF on 1.840 MHz in order for their antenna switcher/tuner to operate
I'm seeing the same problem with IC706,
Apologies in advance if this has been discussed before - I tried searching
the list archives and couldn't find anything.
Would it be possible upon requesting a band change, while operating in
"Split: Rig" mode, for WSJT to send the appropriate hamlib/rigctl commands
to either re-configure the
Personally, I'd like to see some improvement to the "Coffee Brew" code...
The coffee my WSJT-X makes isn't nearly strong enough.
Happy 1 April!
73 de AI8W
On Mon, Apr 1, 2019 at 3:28 PM Frank Kirschner
wrote:
> George,
>
> I believe you've explained the anomaly.
>
> LOL
>
> 73,
> Frank
> KF6E
George,
I believe you've explained the anomaly.
LOL
73,
Frank
KF6E
On Mon, Apr 1, 2019, 12:33 George J Molnar wrote:
> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has
> been revealed. On April 1st, of all days.
>
> Whine mode is exotic code that scans the operator’s
Ha! I have experienced this so often lol
> On Apr 1, 2019, at 12:27 PM, George J Molnar wrote:
>
> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has
> been revealed. On April 1st, of all days.
>
> Whine mode is exotic code that scans the operator’s brainwaves for
KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has been
revealed. On April 1st, of all days.
Whine mode is exotic code that scans the operator’s brainwaves for signs of
frustration, and just as he/she is about to give up (afterwards on slower
computers) permits a DX
Hello Frank and Mike
I believe Mike is correct in suspecting an audio dropout. He helped me
understand the complex power-use issues in Windows 10 (made even more
complicated when running Parallels on a Mac).. instead of using the Halt button
(which I never tried} I have to leave the WSJT FT8
: [wsjt-devel] Feature Request
This can also be a symptom of audio dropouts.
Here is a version of WSJT-X that shows you when you have audio problems. You
get a few messages at startup that are expected as the audio syncs up and then
you should never see them again unless you have problems. Catchup
This can also be a symptom of audio dropouts.
Here is a version of WSJT-X that shows you when you have audio problems. You
get a few messages at startup that are expected as the audio syncs up and then
you should never see them again unless you have problems. Catchup messages
indicate audio
Re: Frank Kirschner 2019-04-01
> Almost every time I'm trying to work a DX station, I call and call with no
> success, until I hit Halt TX. As soon as I do that, the DX station comes
> back to me.
>
> Could you write some software that would get the DX station to respond
> sooner? This would
Almost every time I'm trying to work a DX station, I call and call with no
success, until I hit Halt TX. As soon as I do that, the DX station comes
back to me.
Could you write some software that would get the DX station to respond
sooner? This would help everyone, including the DX station.
Also,
There are plenty of stations from 100 Hz up to 3500 Hz.
You should turn Your VFO to find all of them..
Keijo
EA5/OG55W
From: Richard Shaw
Sent: Thursday, February 21, 2019 2:49 PM
To: k...@arrl.net ; WSJT software development
Subject: Re: [wsjt-devel] Feature Request - xmit below 200 hz
On Wed, Feb 20, 2019 at 5:59 PM Jim Brown
wrote:
> On 2/20/2019 3:48 PM, Ken Miller wrote:
> > I like to utilize the lower portion of the FT8 bands down to 0 hz.
>
> When transmitting that low, your signal is outside the RX bandwidth of
> many transceivers that are tuned to the standard
Understand, I do not care if the thundering herd can not hear me. I TX
on the lower band edge to avoid QRM. Savvy DX operators and especially
SDR operators will hear me, just trying to make my live a tiny bit
easier. I already tune down 200hz, it works, seems a bit clunky though. TNX
On
On 2/20/2019 3:48 PM, Ken Miller wrote:
I like to utilize the lower portion of the FT8 bands down to 0 hz.
When transmitting that low, your signal is outside the RX bandwidth of
many transceivers that are tuned to the standard frequency. If you want
to do that anyway, simply tune your RX to
Hi,
This is some great software, I have been enjoying it for years. I do
have a suggestion.
I like to utilize the lower portion of the FT8 bands down to 0 hz. I
usually VFO down 200 hz so as to bypass the 200hz lower TX limit. Since
I now own a SDR that has an adjustable TX bandwidth that
Hi Bill,
On Sat, 1 Dec 2018 13:41:48 +
Bill Somerville wrote:
> congratulations on the 4W ATNO!
Thanks!
> What rig do you use? Is CAT control simply not available for it or is
> there some other reason why you don't have it?
Vintage Drake 7-Line twins, circa 1980. CAT is not available.
On 01/12/2018 04:43, Jim Shorney wrote:
I scored 4W for ATNO on 20M Fox/Hound today, pretty easily at that. Thanks to
the JT/FT developers once again for helping my DXCC count!
This bring up something I had been thinking about before. It would be nice for
those of us who do not use CAT for
I scored 4W for ATNO on 20M Fox/Hound today, pretty easily at that. Thanks to
the JT/FT developers once again for helping my DXCC count!
This bring up something I had been thinking about before. It would be nice for
those of us who do not use CAT for whatever reason to have an option to limit
I often forget that I have "Hold Tx Freq" checked. Then, I accidentally
call someone or call CQ on top of another station. I know... I should watch
the waterfall more carefully.
I suggest highlighting the "Hold Tx Freq" text with a bright color, so it
is obvious when the box is checked.
Example:
Hi Edfel
There really are only two ways to implement this:
1. in hardware
- devise some way to split off a tiny portion of your TX signal from
your antenna feed, feed it to a second rig (SDR?), second audio
interface, and second instance of WSJT-X
2. like Barry suggests, by sending
Hi:
I work most of the time (when is its time), the 6 meter band.. Other bands
are 40 and 80m. 20m is relatively easy (IMO) to get QSO.
73'
Edfel
KP4AJ
On Fri, Jun 29, 2018 at 9:33 AM, Barry Smith wrote:
> In message mail.com>
> Edfel Rivera wrote:
>
> > My own experience at my
In message
Edfel Rivera wrote:
> My own experience at my location, 95 watts are normally required to
> complete QSO (Puerto Rico - Caribbean). Under better conditions maybe less
> power could be used.
I'm in the UK running 40 watts to a simple end-fed antenna. On 20m
I've worked
You can do that with a Screen Capture program now. Windows 10 includes
one, and Gadwin Print Screen is free for the download in 32 & 64 bit
versions.
Neil, KN3ILZ
On 6/27/2018 5:50 PM, Bill Turner wrote:
Most FT8 users have email addresses in QRZ, so you can send them a
screen shot. In my
1 - 100 of 199 matches
Mail list logo
