Hi Lance
Its there already, labelled as Delay.
73
Charlie DL3WDG
On Tue, 19 Oct 2021 at 00:30, Lance Collister, W7GJ via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> As I am currently on an EME DXpedition without any access to internet or
> a reliable GPS puck that runs on Windows 1
Baddah-bim, baddah-boom! You da man Bill! Many thanks, all is well now. This
also resolved the other problem of the brackets around calls that seemed
normal. I still haven’t resolved why I couldn’t completely uninstall the old
version which might have resolved the issue when reentering the d
As I am currently on an EME DXpedition without any access to internet or
a reliable GPS puck that runs on Windows 10, it occurred to me that it
should be very easy to add a very helpful item to the Astronomical Data
table. If the correct DT were shown, I could make computer clock
adjustments us
Hello Charlie and Bill.
So, this behaviour in no way impacts FO/W7GJ’s ability to decode my final
rogers? These are very marginal signal levels as you know. I expected that his
decoder would be looking for FO/W7GJ PA5Y RRR, it seems that the current
situation is OK. I don’t understand the decod
On 10/18/2021 12:10 PM, Conrad PA5Y via wsjt-devel wrote:
Well typically Lance asks that if you decode him you start with TX2.
To conserve battery/generator fuel, Lance does not call CQ on
expeditions, directing callers to call blind, and answering those he
copies. In that situation, callers
Well typically Lance asks that if you decode him you start with TX2. But only
if you decode him, this enables him to reply to those who are hearing him on
the previous TX sequence. For 6m EME I think that this is a good idea.
So
ON4GG FO/W7GJ R-21
I TX2
FO/W7GJ PA5Y -27 probably for 2 periods.
Il 17/10/21 19:03, Bill Somerville via
wsjt-devel ha scritto:
On 17/10/2021 21:38, Marco Calistri
via wsjt-devel wrote:
Il 17/10/21 17:31, Bill Somerville
via wsjt-devel ha scritto:
On 17/10/202
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
Hi Conrad,
it is already fixed for the next release. I'm not sure I understand what
why you think it is so urgent, please detail a typical QSO sequence
where you think there is a problem?
73
Bill
G4WJS.
On 18/10/2021 17:03, Conrad PA5Y via wsjt-devel wrote:
Thanks Bill, you can imagine for
Hi Conrad
I'm not sure there is any need to change the program with urgency. If you
take the messages that are generatied automatically and don't manually
change them, then the RRR and 73 messages are transmitted with base calls
and the program recognises this and decodes the RRR and 73 with full
Thanks Bill, you can imagine for marginal QSOs such as this when Lance is
expecting RRR it could be an issue, he is there right now. Any chance that this
can be fixed as a matter of some urgency please
73
Conrad PA5Y
From: Bill Somerville via wsjt-devel
Sent: 18 October 2021 15:02
To: wsjt-de
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.
On 18/10/2021 11:09, Conrad PA5Y via wsjt-devel wrote:
Hello team.
Last night I was attempting to work FO/W7GJ on Q65-60A. My question is
about the population of TX4 and TX5.
When I Generate standard messages, I see TX1-3 are correct.
TX1 PA5Y JO21
TX2 PA5Y -27
TX3
Hello team.
Last night I was attempting to work FO/W7GJ on Q65-60A. My question is about
the population of TX4 and TX5.
When I Generate standard messages, I see TX1-3 are correct.
TX1 PA5Y JO21
TX2 PA5Y -27
TX3 PA5Y R-27
However, the compound call is omitted from TX4
19 matches
Mail list logo
