Il 28/07/24 12:24, Black Michael ha scritto:
VFOB should update frequency and mode when you change bands or transmit.
What rig do you have?
Mike W9MDB
Then,
It works as expected,
I've just verified: if I switch the band on WSJT-X selector, then VFOB
is changing to DIG mode correctly.
Th
Il 28/07/24 12:24, Black Michael ha scritto:
VFOB should update frequency and mode when you change bands or transmit.
What rig do you have?
Mike W9MDB
Hi Mike!
YAESU FT-100.
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
On Sunday, July 28, 2024 at 10:10:37 AM CDT, Marco Calistri via
ws
VFOB should update frequency and mode when you change bands or transmit.
What rig do you have?
Mike W9MDB
On Sunday, July 28, 2024 at 10:10:37 AM CDT, Marco Calistri via wsjt-devel
wrote:
Hello,
This behavior is not related to a specific WSJT-X version.
I use the hamlib rigct
Many fewer harmonics generators now than in the past.
WA1SXK and I went on the war path for the last several years contacting
everybody we saw and getting them fixed.The FT8Noise paper on my QRZ page is
the result of testing with numerous rigs and explains it all.
Mike W9MDB
On Tuesday, S
TNX Mike! I am amazed how many people I keep seeing on the air who are
transmitting audio harmonics and don't understand that they need to have
the XMTR frequency changed if they want to select XMIT offsets lower
than 1500 Hz. They insist that they have checked their audio and it is
not overdr
No -- the target is not good quality of signals -- that's misleading
tooit's all about shifting the audio (actually shifting the suppressed
carrier).
#1 Avoid transmit band edges (rigs can actually transmit outside of their
bandpass)#2 Avoid harmonics#3 Avoid non-linear power behavior (some
Hi Jim
I agree - it is a very frustrating situation, especially for foreign users
with English language problems.
The target is the good quality of signals. So the title:
"Split Operation" is bad. Split operation is one of the ways to get it.
"None" is OK.
"Rig" is not OK, it should be "Rig SPLIT
Hi Jim and all,
I support this proposal. I know that on the rig's point of view the
functionality is the same as in the classical "split". What is seen on the
band may or may not be the same depending how the user selects the
transmission frequency.
In addition some words could be added to note t
I disagree with the progam/documentation change request.
Split is the radio function invoked for 'rig split', and it is
documented well online,
how the system uses rig split to control the audio frequency best use
window.
I feel; 'TX Shift' would cause more confusion, as it still does not
Greetings; if you've compiled the current software, you'll probably note
that doing so generates quite a few separate applications. Two of these
applications are wsjtx and jt9 -- wsjtx *is* the UI on top of the jt9
application.
-Brian N9ADG
On Wed, Apr 26, 2023 at 4:56 AM Daniel Uppström via wsj
Will this version 4.4 be easily distinguishable from the version 4.4 of hamlib
that is included in the latest release of wsjt-x? Or is that a problem that the
wsjt-x folks have created?
#WeDemandRigidlyDefinedAreasOfDoubtAndUncertainty 😁
73, Willie N1JBJ
>
> On Dec 2, 2021, at 8:32 AM, Black
Dave,
Please contact me off-listmdblac...@yahoo.com
Mike W9DMB
On Wednesday, December 1, 2021, 11:25:58 PM CST, Dave J Barnes via
wsjt-devel wrote:
So a new version of wsjtx is coming in a few days?
On 12/1/21 10:49 PM, Black Michael via wsjt-devel wrote:
You sho
No.
There is no scheduled date for the next release.
Mike W9MDB
On Wednesday, December 1, 2021, 11:25:58 PM CST, Dave J Barnes via
wsjt-devel wrote:
So a new version of wsjtx is coming in a few days?
On 12/1/21 10:49 PM, Black Michael via wsjt-devel wrote:
You should
So a new version of wsjtx is coming in a few days?
On 12/1/21 10:49 PM, Black Michael via wsjt-devel wrote:
You should be able to build it yourself from the tar.gz file.
Just be sure to remove the hamlib package you already have installed
as it installs in /usr/local
Or you can configure it
You should be able to build it yourself from the tar.gz file.
Just be sure to remove the hamlib package you already have installed as it
installs in /usr/local
Or you can configure it this way
./configure --prefix=/usr
Mike W9MDB
On Wednesday, December 1, 2021, 10:24:03 PM CST, Dave J Barn
Any help for Linux users?
On 12/1/21 10:16 PM, Black Michael via wsjt-devel wrote:
Please try the latest dll.
This version is due to be 4.4 to be released in the next few days.
New hamlib for Windows installation directions
#1 Shut down WSJTX
#2 Download either the 32-bit or 64-bit DLL -- hopef
Please try the latest dll.This version is due to be 4.4 to be released in the
next few days.
New hamlib for Windows installation directions#1 Shut down WSJTX#2 Download
either the 32-bit or 64-bit DLL -- hopefully your browser doesn't block it but
may warn you multiple times.If you can do a "Sav
On 18/10/2021 18:39, Barry Jackson via wsjt-devel wrote:
/OT
All is working fine now with wsjtx and klog, however I am puzzled as
to why automatic logging is "(contest only)"?
It would be excellent (with klog) if that worked without the reminder
dialogue, as klog can be used to tweak qso reco
On 18/10/2021 14:42, Bill Somerville via wsjt-devel wrote:
Hi Bill,
It seems we are all as confused as each other although your suggestion
would work.
Mike just suggested:
[baz@localhost ~]# rigctld -v -Z -v -m 2003 -s 4800 -r /dev/ttyUSB0
-t 4532 --set-conf=serial_handshake=None --write
I updated the man page.
This was changed to maintain combability with older versions.
So the new way is the correct way.
Mike W9MDB
On Monday, October 18, 2021, 11:30:45 AM CDT, Saku via wsjt-devel
wrote:
There is something to do with man pages. For example:
[saku@hamtpad ~]$ r
There is something to do with man pages. For example:
[saku@hamtpad ~]$ rigctld --version
rigctl Hamlib 4.4~git ke loka 13 21:02:40 2021 + SHA=16a879
-
chk_vfo
Returns “CHKVFO 1\n” (single line only) if rigctld was
invoked
On 18/10/2021 14:29, Bill Somerville via wsjt-devel wrote:
On 18/10/2021 14:21, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 16:18, Black Michael wrote:
Try this
rigctld -v -Z -v -m 2003 -s 4800 -r /dev/ttyUSB0 -t 4532
--serial_handshake=None --write_delay=5
Hi Mike,
Going back to
On 18/10/2021 14:21, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 16:18, Black Michael wrote:
Try this
rigctld -v -Z -v -m 2003 -s 4800 -r /dev/ttyUSB0 -t 4532
--serial_handshake=None --write_delay=5
Hi Mike,
Going back to this command of yours with syntax that does not work, is
th
On 15/10/2021 16:18, Black Michael wrote:
Try this
rigctld -v -Z -v -m 2003 -s 4800 -r /dev/ttyUSB0 -t 4532
--serial_handshake=None --write_delay=5
Hi Mike,
Going back to this command of yours with syntax that does not work, is
there a current up-to-date ridctld documentation somewhere.
Got it...thanks Bill.
Mike W9MDB
On Friday, October 15, 2021, 01:13:21 PM CDT, Bill Somerville via
wsjt-devel wrote:
On 15/10/2021 19:05, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 18:37, Black Michael via wsjt-devel wrote:
What's the title of that manual? I'd hope it wo
On 15/10/2021 19:09, Bill Somerville via wsjt-devel wrote:
Hi Barry,
I have already sent Mike a copy of that document.
Great - thanks for letting me know :)
Have a good evening!
Cheers,
Barry
G4MKT
___
wsjt-devel mailing list
wsjt-devel@lists.
On 15/10/2021 19:05, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 18:37, Black Michael via wsjt-devel wrote:
What's the title of that manual? I'd hope it would be available
on-line.
Do you have a scanner on your printer?
Also...are you able to checkout the master repo and test the fix I
On 15/10/2021 18:37, Black Michael via wsjt-devel wrote:
What's the title of that manual? I'd hope it would be available on-line.
Do you have a scanner on your printer?
Also...are you able to checkout the master repo and test the fix I just
posted?
Mike W9MDB
It's called:
"TS-450S TS-690S
What's the title of that manual? I'd hope it would be available on-line.
Do you have a scanner on your printer?
Also...are you able to checkout the master repo and test the fix I just posted?
Mike W9MDB
On Friday, October 15, 2021, 12:29:17 PM CDT, Barry Jackson via wsjt-devel
wrote:
On 15/10/2021 18:25, Barry Jackson via wsjt-devel wrote:
I do have the paper one. Maybe the bits you need are not too big?
TS-450S that is.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w
On 15/10/2021 18:25, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 17:46, Black Michael via wsjt-devel wrote:
I'll have a fix for this shortlyI put in a split check for
Elecraft rigs and that is doing the "FT" query which isn't supported
as Bill notes.
Bill...do you know of a CAT manu
On 15/10/2021 17:46, Black Michael via wsjt-devel wrote:
I'll have a fix for this shortlyI put in a split check for Elecraft
rigs and that is doing the "FT" query which isn't supported as Bill notes.
Bill...do you know of a CAT manual for the TS590/690? I can't seem to
find one.
Mike W9
On 15/10/2021 17:46, Black Michael via wsjt-devel wrote:
I'll have a fix for this shortlyI put in a split check for Elecraft
rigs and that is doing the "FT" query which isn't supported as Bill notes.
Bill...do you know of a CAT manual for the TS590/690? I can't seem to
find one.
Mike W9
I turned it into a generic "don't set unless necessary". Was causing power
problems on the K4 too.Hopefully it's fixed now and applies to all rigs that
can get split status and trying to set split on again. Split off will always
run a command.
Mike W9MDB
On Friday, October 15, 2021, 11
via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 15. lokakuutata 2021 19:47
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] Split-RIG broken with hamlib-4.3.1 with TS-450S (4.2
is fine)
I'll have a fix for this shortlyI put in a split
Subject: Re: [wsjt-devel] Split-RIG broken with hamlib-4.3.1 with TS-450S (4.2
is fine)
I'll have a fix for this shortlyI put in a split check for Elecraft rigs
and that is doing the "FT" query which isn't supported as Bill notes.
Bill...do you know of a CAT manual f
I'll have a fix for this shortlyI put in a split check for Elecraft rigs
and that is doing the "FT" query which isn't supported as Bill notes.
Bill...do you know of a CAT manual for the TS590/690? I can't seem to find one.
Mike W9MDB
On Friday, October 15, 2021, 11:30:50 AM CDT, Bill
On 15/10/2021 17:21, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 15:57, Bill Somerville via wsjt-devel wrote:
the TS-450S and TS-690S use RTS/CTS hardware handshake flow control.
I have never see a rig with a serial CAT interface that uses XON/XOFF
flow control, RTS/CTS is ubiquitous on
On 15/10/2021 17:19, Bill Somerville via wsjt-devel wrote:
On 15/10/2021 16:57, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 16:18, Black Michael wrote:
Since you're not getting any answer with hardware flow it sounds
like you have a 3-wire RS232 cable. So how are your cable pinouts
conn
On 15/10/2021 15:57, Bill Somerville via wsjt-devel wrote:
the TS-450S and TS-690S use RTS/CTS hardware handshake flow control. I
have never see a rig with a serial CAT interface that uses XON/XOFF flow
control, RTS/CTS is ubiquitous on Kenwood rigs with the exception of
some handhelds that o
On 15/10/2021 16:57, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 16:18, Black Michael wrote:
Since you're not getting any answer with hardware flow it sounds like
you have a 3-wire RS232 cable. So how are your cable pinouts connected?
Try this
rigctld -v -Z -v -m 2003 -s 4800 -r /de
Actually a few rigs with xon/xoff including the old Kenwood THD74 according to
our defaults.
.serial_handshake = RIG_HANDSHAKE_XONXOFF,./kenwood/thd74.c
.serial_handshake = RIG_HANDSHAKE_XONXOFF,./aor/ar8200.c
.serial_handshake = RIG_HANDSHAKE_XONXOFF,./aor/sr2200.c
.serial_h
Since you're not getting any answer with hardware flow it sounds like you have
a 3-wire RS232 cable. So how are your cable pinouts connected?
Try this
rigctld -v -Z -v -m 2003 -s 4800 -r /dev/ttyUSB0 -t 4532
--serial_handshake=None --write_delay=5
See if that write_delay helps in your situ
On 15/10/2021 15:43, Black Michael wrote:
Now please test 4.4 without the stopbits and serial_handshake options (let
rigctld use the defaults).
The difference is the commands are now being stacked and it's possible the lack
of hardware flow control is causing this problem.Just let those two opt
On 15/10/2021 15:49, Barry Jackson via wsjt-devel wrote:
On 15/10/2021 15:02, Black Michael wrote:
I noticed you have serial_handshake=XONXOFF and stopbits=1
Just let those two items default to stopbits=2 and
serial_handshake=Hardware which what I show is the setup for the TS-450.
And you shou
On 15/10/2021 15:02, Black Michael wrote:
I noticed you have serial_handshake=XONXOFF and stopbits=1
Just let those two items default to stopbits=2 and serial_handshake=Hardware
which what I show is the setup for the TS-450.
And you should be able to just check all the Default labels in WJST-X'
I noticed you have serial_handshake=XONXOFF and stopbits=1
Just let those two items default to stopbits=2 and serial_handshake=Hardware
which what I show is the setup for the TS-450.
And you should be able to just check all the Default labels in WJST-X's rig
control tab too (which, by the way, s
On 14/10/2021 20:50, Black Michael wrote:
That should be fixed in the master branch now.
Can you please try that?
Hi Mike,
Thanks for your quick reply.
I rebuilt hamlib package from git master (da34930) and rebuilt a new
wsjtx-2.5 package against it. (Not sure if that was strictly necessary?)
That should be fixed in the master branch now.Can you please try that?
Mike W9MDB
On Thursday, October 14, 2021, 02:36:33 PM CDT, Barry Jackson via
wsjt-devel wrote:
There seems to be a regression in hamlib-4.3.x which I have been testing
for our dev branch.
I maintain the wsjtx p
Hi Bill,
Thank you for prompt reply.
I understand your explanation.
I am using Q65A mode with 6mb usually, but I want the split operation to
be normal. Is there any inconvenience with disabled "VHF and submode
features", though Q65 quick start quide recommends it should be active?
Current RC all
On 22/08/2021 15:35, Yukio JG1APX via wsjt-devel wrote:
Hi development teams
I apologize my report if it is already known issue and discussed before.
OS : Windows 10 pro 21H1
Wsjtx : 2.5.0rc5
Rig : IC-9700, FT-991A, FTDX-3000, FTDX-101
Split operations (Rig and Fake It) are not working properl
Hi Om's
This is the way I'm doing split operation on 160m for JA. Now doing FT8
with an IC-7300 and it's a bit different from the IC-775 I was using B4.
First off all go into wsjt-x settings/radio and mark None in the Split
Operation section. Then go to the Frequencies Tab and insert 1,908 Mh
> 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 Mic
Hi Claude!
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 Michael 5P1KZS.
To operate SPLIT (to work JA) on 160 meters:
In WSJT
On 23/12/2019 10:37, Claude Frantz wrote:
Hi all,
Please allow me to ask about the split mode in the sense of a
necessity resulting from different frequency assignments in different
countries, i.e. a sort of special form of multi-band operation. The
typical situation is the QSO between a Japa
On 13/12/2018 08:17, Tom Ramberg via wsjt-devel wrote:
NB! Don't mark the "Split setting" in WSJT-X as RIG or FAKE. Mark as "None" in
settings.
Hi Tom,
I am surprised that works and it is certainly not a good suggestion for
all users. I would expect WSJT-X to disable SPLIT on your rig if you
Bill, I’ve discussed this with Keijo, and this method of working split also
worked fine, at least with the FT-1000Mp and FTdx3000. I see no reason why it
shouldn’t work on any radio with dual vfos:
To operate SPLIT (to work JA) on 160 meters:
In WSJT-X set freq. to 1,908 Mhz - will set ur VFO A
teven Greer
> Sent: Wednesday, December 12, 2018 7:52 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Split operation
>
> Just check the keep TX frequency that way when you transmit you will be
> transmitting where you set yourself, and the rx will goto t
FB! Thanks Bill!
I am not the only one on TOP band, so the info was very welcome!
Keijo
-Alkuperäinen viesti-
From: Bill Somerville
Sent: Wednesday, December 12, 2018 8:10 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split operation
On 12/12/2018 17:45, OG55W
On 12/12/2018 17:45, OG55W wrote:
I have tried to find how to operate with split..
JA-stations are calling me in 1908 as I am transmitting in 1840, and I
do not hear them as my RX or TX change the frequency.
I am not allowed to transmit in 1908.
Hi Keijo,
WSJT-X does not support this using C
Steven! The waterfall is only 3500 Hz wide and it should be more than 68000 Hz
wide to hear 1908 kHz.
Keijo
From: Steven Greer
Sent: Wednesday, December 12, 2018 7:52 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split operation
Just check the keep TX frequency that way
Just check the keep TX frequency that way when you transmit you will be
transmitting where you set yourself, and the rx will goto the calling
station. Thats how I do it. Not sure if I'm allowed to comment to the
mailing to help others if not just let me know and I won't help out
anymore on ea
I do the same transmit filter on my ANAN 100 at 1450-2050.Don't see any reason
we couldn't do a split adjustment at offset-25 for FT8 and run a 100Hz filter.
That's the minimum filter size PowerSDR will take.So for a 1900 offset you
would get split at 1875m, your signal at 1900-1950, and the up
This was not obvious to me from reading the manual or noting that the dial
frequency was moved up or down. It is key that the audio frequency is also
moved opposite the dial frequency an equal amount and both should be mentioned
in the manual - for slow heads like me at least. Anyway, I get it n
Doh! Understood what it purpose is for 😃 and will leave it enabled.
Thanks Bill
Mark
Sent from BlueMail
On 8 Apr 2018, 20:01, at 20:01, Bill Somerville wrote:
>On 07/04/2018 23:31, Mark Rutherford wrote:
>> Morning Guys,
>>
>> Regarding testing Apr7th 1400-1600 from OZ I was able to some ho
On 07/04/2018 23:31, Mark Rutherford wrote:
Morning Guys,
Regarding testing Apr7th 1400-1600 from OZ I was able to some hound
activity in the first 30min or so last night but not neither "KH7Z"
stations.
That said, this morning I've noticed that once I deactivated "hound"
mode, so its now i
Wed, 21 Mar 2018 18:00:38 -0400
"James Shaver" kirjoitti:
> And the “normal” 17 meter frequency as well with the same results…
I was on 17m calling too... Twice got report, but never rr73.
Saw that happened some others too. Think we all need much more
practice, so fox as hounds
Jarmo
And the “normal” 17 meter frequency as well with the same results…
From: James Shaver [mailto:n2...@windstream.net]
Sent: Wednesday, March 21, 2018 5:59 PM
To: 'WSJT software development'
Subject: RE: [wsjt-devel] Split mode ft 8
Unfortunately, they’re using the DXPedition m
Unfortunately, they’re using the DXPedition mode on the “normal” 15 meter
frequency and ops are inadvertently stomping all over several QSO’s in
progress. I witnessed several busted contacts and had a few myself as a
result.
From: Ray Jacobs [mailto:rjacobs...@verizon.net]
Sent: Wednesday
Rich --
On 3/15/2018 11:39 AM, Rich - K1HTV wrote:
If at all possible, I'd recommend that a 4-digit (160 thru 40M) or
5-digit (30M thru 6M) number in a CQ text message be interpreted as the
frequency to set VFO-B. It is harder to misinterpret an exact frequency,
especially once the DXpedition
If at all possible, I'd recommend that a 4-digit (160 thru 40M) or 5-digit (30M
thru 6M) number in a CQ text message be interpreted as the frequency to set
VFO-B. It is harder to misinterpret an exact frequency, especially once the
DXpedition mode starts being used and DX stations use Rx frequen
OK...so it added the 1st 3 digits as 190kHz to 1MHz to come up with 1.190
So what do we want to do with a 4 or 5 digit QSY like this?
#1 Ignore it?#2 Change to it and handle it differently than the 3-digit QSY?
de Mike W9MDB
On Thursday, March 15, 2018, 9:59:33 AM CDT, Rich - K1HTV
wrote:
Hi Rich,
Apparently H40YM transmitted "CQ 1908 H40YM", indicating that he was
hoping to raise JAs in a higher part of the band. That's a free text
message, so double-clicking on it will *not* put H40YM into your DX Call
box. Of course, you can do this manually, however.
Double-clicking on
Mike, yes a QSY message was seen:
>From the Band Activity window:
--- 160m
112315 10 0.2 700 ~ CQ N9MB EN70 K
112315 4 1.4 864 ~ CQ WB9JOX EN61 K
112315 -18 0.7 1957 ~ CQ 1908 H40YM !where?
>From the Rx Frequency
That's almost a QSY request but that format is expecting a 3-digit frequency so
would've thought you'd see a 190kHz movement
Did you see a QSY message in your Rx window?
de Mike W9MDB
On Thursday, March 15, 2018, 6:49:15 AM CDT, Rich - K1HTV
wrote:
This morning, a few minutes be
Very cool Mike. Thanks
__
Dan – K4SHQ
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, November 25, 2017 6:55 AM
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Split frequency logging
That change is in beta
7;ll continue manual corrections. Not a big deal, but was
curious.
__
Dan – K4SHQ
-Original Message-
From: Claude Frantz [mailto:claude.fra...@bayern-mail.de]
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency lo
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging
On 11/22/2017 02:25 PM, Dan Malcolm wrote:
Hi Dan & all,
> WSJT-X is pretty good at running QSO’s with ‘split’ frequency
> operation. JTAlert is essential fo
On 11/22/2017 02:41 PM, Karl Barth wrote:
Hi Charly & all,
> I got a radio licence, not my PC -
But my PC has really better ears than myself.
Best wishes,
Claude (DJ0OT)
--
Check out the vibrant tech community on one
On 11/22/2017 02:25 PM, Dan Malcolm wrote:
Hi Dan & all,
> WSJT-X is pretty good at running QSO’s with ‘split’ frequency
> operation. JTAlert is essential for smooth QSO tracking and logging.
> What I am missing is logging the separate frequencies for a split QSO.
> I suspect that most ops don
.
From: Karl Barth [mailto:df5...@darc.de]
Sent: Wednesday, November 22, 2017 8:42 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging
Dear all,
it is not too long ago and we commonly used to run our qso's in person
(cw/ssb) and log on paper.
Do we re
Dear all,
it is not too long ago and we commonly used to run our qso's in person (cw/ssb) and log on paper.
Do we realy need to get all radio contacts fully automated?
Just go to the shack in the morning and activate the PC with all add-on automated software?
I got a radio licence, not my PC
Thanks for the good wishes, Morris! I am gradually feeling better...this was my
first "high-dose" flu shot and probably my last! The amount of antigen is four
times a standard flu shot.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Friday, September 29, 2017, 2:22:29 PM EDT, Morris Wideman via
Gary,
I agree that people should notice the red line, but I think they tend to get
tuned-in to the right-hand window when looking for a response. I know that I
have missed a couple myself.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Friday, September 29, 2017, 2:37:26 PM EDT, Gary McDuffie
> On Sep 29, 2017, at 12:21 PM, Morris Wideman via wsjt-devel
> wrote:
>
> This is where more and better filters would also be useful when the left
> screen is full of calls that have nothing to do with your call or QSO. Hope
> you get to feeling better Ed.
If the text has your call in it, i
This is where more and better filters would also be useful when the left
screen is full of calls that have nothing to do with your call or QSO. Hope you
get to feeling better Ed.73 Morris wa4mit
On Friday, September 29, 2017, 11:03:39 AM CDT, Ed Wilson via wsjt-devel
wrote:
I have bee
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 st
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 tha
On 11-Jul-16 0841, Bill Somerville wrote:
> I suggest that you set the "PTT Method" in WSJT-X "Settings->Radio"
> to "VOX".
Hello Bill.
Yes, RR on the VOX. Per your instructions, probably the last time a fwew
weeks ago where I was frustrated with this, I already have PTT set to VOX.
. And I have
On 11/07/2016 12:38, Bob KD7YZ wrote:
> If I select Split-Rig in WSJTx; setup K3 to Split; Set DxCommander to
> Split, then when either I press "Tune On in WSJTx OR I run a CQ
> sequence, the K3 TX-LED comes on, Rx Audio goes away, the PTT-LED on the
> SignaLink soundcard comes on . briefly the
On 09/03/2016 14:32, Michael Black wrote:
> New patch with doc and help modifications -- only thing that changes
> is the shift-click behavior.
Committed with some minor documentation amendments. Thanks Mike.
73
Bill
G4WJS.
-
On 09/03/2016 14:32, Michael Black wrote:
> Looking at the double-click though it appears to me that the Rx freq
> is NOT being set and it just decodes at whatever the current Rx
> setting is.
> Do we want the double-click to set the Rx frequency too which is what
> the help says? Or change the he
Arrghhh...forgot to save the last change I made before diffing. I had
switched behavior while testing. Sorry 'bout that. Not enough
caffeine this morning.
New patch with doc and help modifications -- only thing that changes
is the shift-click behavior.
Looking at the double-click though it app
On 09/03/2016 13:25, Michael Black wrote:
> This patch adds shift-click to set the TX offset
> Made the code a bit more straightforward while I was at it.
Hi Mike,
the patch doesn't do what you imply above. It seems to change the
existing CTRL+click behaviour from move Tx and Rx to just moving Tx
On 09/03/2016 13:25, Michael Black wrote:
> Still wondering what all the n+=100 is for in this function and the
> double-click function. Looks like dead code to me.
Hi Mike,
the n+100 indicates that the CTRL key was pressed to receivers of the
signal. It is a bit of clunky way of passing an extr
rom: Joe Taylor
To: WSJT software development
Sent: Sunday, January 3, 2016 7:41 PM
Subject: Re: [wsjt-devel] Split audio frequency
Hi Mike,
One of the advantages of open source software is that anyone with
special needs or desires can study the code and learn enough to make the
changes neede
Hi Mike,
One of the advantages of open source software is that anyone with
special needs or desires can study the code and learn enough to make the
changes needed to implement them. You have done the hard work and
evidently have solutions that suit your purposes (which, if I've
understood cor
I'm sure it's not just me. I know some tuners like SG's can take 20+
seconds to autotune a frequency.
So when responding to a CQ waiting for the tuner to do it's thing can make
your transmit message loss more likely. My LG is typically 5 seconds or
less. I was noticing the system retuning freque
On 03/01/2016 19:28, Michael Black wrote:
> At least for my autotuner and rig (Omni TenTec VII and SG-237 the 10Hz
> works quite well...the 100Hz still causes some retuning on a few bands.
Hi Mike,
I am still struggling with this. If you shift your DF by 1Hz from 1500
to 1499 then the Tx VFO is
At least for my autotuner and rig (Omni TenTec VII and SG-237 the 10Hz
works quite well...the 100Hz still causes some retuning on a few bands.
But why not 1Hz too? Is that going to harm something? Seems to me if the
step size doesn't work for your rig...don't use it. Lowest common
denominator sh
1 - 100 of 102 matches
Mail list logo
