Hi Joe,
The HF pileup QSO sequence that you suggested in your email is perfect for the normal case, when both parties copy each other
without problems, but some edge cases need to be discussed in more detail. The communication channel can fail at any stage
during the QSO, in one direction or an
Every time that I run WSJT-X 1.8.0-rc1 I find that the volume of input
has been reset to a very high level ...100%
... I have to lower it to "no amplification"
(running on Linux Mint 18.2)
...1.7... on Mint 17.3 had not this behavior.
73 Pino ZP4KFX
---
Hi John and all,
On 8/8/2017 12:19 PM, John Zantek KE7B wrote:
This past weekend, I attended the Pacific NW DX Convention, where the buzz
of JT/FT was tangible. ... The
biggest news for me was the talk about the upcoming DXpedition to Mellish
Reef (VK9MA) and the stated intention to try JT65 a
On 16/08/2017 11:30, Bill Somerville wrote:
On 16/08/2017 12:02, Philip Gladstone wrote:
I'm getting a bunch of strange packets sent to pskreporter that (I
think) are coming from wsjt implementations. For example:
AD BC CB DA 00 00 00 01 00 00 00 00 00 00 00 04 4D 53 48 56 00 00 00
01 00 00
I think this behavior works pretty well. Double-click on TX6 makes the message
sticky (I call it "locked" in the tooltip) and disables the textbox for a
visual indication. Double-clicking again enables and resets the CQ message.Any
protocol with the freq offset message turns it off too and doe
On 16/08/2017 12:02, Philip Gladstone wrote:
I'm getting a bunch of strange packets sent to pskreporter that (I
think) are coming from wsjt implementations. For example:
AD BC CB DA 00 00 00 01 00 00 00 00 00 00 00 04 4D 53 48 56 00 00 00
01 00 00 00 04 31 2E 34 32
I think that this is wsjt
Thanks Bill for the software fix for this issue and for all that you do as part
of the WSJT-X Development team.
73,
Rich - K1HTV
PS I'm now up to 116 DX countries worked on FT8 with low power. FT8 is
GREAT!
= = =
From: Bill Somerville mailto:g4...@classdesign.com >
To: wsjt-devel
On 16/08/2017 13:54, Black Michael via wsjt-devel wrote:
Should we ask if anybody expects to reset on band change? What mode
of operations would that be that has a band-sensitive CQ format? And
is that common enough to make that the default case? Or is it much
more common to do the "CQ XX" n
This patch still updates the CQ NNN.
Should we ask if anybody expects to reset on band change? What mode of
operations would that be that has a band-sensitive CQ format? And is that
common enough to make that the default case? Or is it much more common to do
the "CQ XX" no matter the band?
Or
On 16/08/2017 13:17, Black Michael via wsjt-devel wrote:
Is there any reason we can't leave TX6 alone once filled with
anything? Improved patch here with tooltip.
TX6 only gets auto-set if empty or using Tx CQ 280 option . Which
normally happens once after startup of WSJT-X and, as far as I kn
Decoding the bytes (come on guys) it says MSHV 1.42 -- the latest version.
http://lz2hv.org/mshv
de Mike W9MDB
From: Chuck Yahrling
To: WSJT software development
Sent: Wednesday, August 16, 2017 6:41 AM
Subject: Re: [wsjt-devel] Strange packets being received by pskreporter
wsjt it
Thanks Bill. Running Ubuntu 16.04 here. If you want, feel free to send over a
patch file with the instrumentation too. I can apply it to my local copy and
build myself.
Best,
Jordan
On Aug 16, 2017, 6:17 AM -0400, Bill Somerville , wrote:
> On 15/08/2017 18:05, Jordan Sherer wrote:
> > Thanks f
On 16/08/2017 04:47, Rich - K1HTV wrote:
While using FT8 I noticed this anomaly.
031330 -14 0.1 1769 ~ CQ E51 W3BTX !S. Cook Is.
With the "Show DXCC entity and worked before status" box under the "
General" tab checked, instead of W3BTX being flagged as U.S.A. it used
the E51 prefix in th
Is there any reason we can't leave TX6 alone once filled with anything?
Improved patch here with tooltip.TX6 only gets auto-set if empty or using Tx CQ
280 option . Which normally happens once after startup of WSJT-X and, as far
as I know, never again unless using the Tx CQ.
Is there any opera
The message is NOT a standard message as shown the Protocol
Specifications in the User Guide. In order to target specific
countries, you must use the format:
CQ xx KN3ILZ FN00 (CQ location Callsign Grid), heres the specific
paragraph:
"Finally, the message compression algorithm supports m
On 16/08/2017 12:02, Philip Gladstone wrote:
I'm getting a bunch of strange packets sent to pskreporter that (I
think) are coming from wsjt implementations. For example:
AD BC CB DA 00 00 00 01 00 00 00 00 00 00 00 04 4D 53 48 56 00 00 00
01 00 00 00 04 31 2E 34 32
I think that this is wsjt
wsjt itself or maybe wsjt-x, which is currently undergoing a lot of rework
regarding format of exchanges?
On Wed, Aug 16, 2017 at 7:02 AM, Philip Gladstone <
pjsg-w...@nospam.gladstonefamily.net> wrote:
> I'm getting a bunch of strange packets sent to pskreporter that (I think)
> are coming from
I'm getting a bunch of strange packets sent to pskreporter that (I
think) are coming from wsjt implementations. For example:
AD BC CB DA 00 00 00 01 00 00 00 00 00 00 00 04 4D 53 48 56 00 00 00 01
00 00 00 04 31 2E 34 32
I think that this is wsjt because of the adbccbda header (which google
On 15/08/2017 18:05, Jordan Sherer wrote:
Thanks for reaching out. I have the KX2 connected to the PC via a
KXUSB cable. I have K3/KX3 rig selected since the KX2 operates the
same rig control serial commands. This configuration provides rig
control with CAT and PTT. Everything seems fairly stra
Title: Re: [wsjt-devel] Wrong countrty
additional to my previous message:
"CQ OE SM4DHF JN88" (as an example, but can happen) is a 'Std. msg',
because there are only two letters behind the CQ.
Wonder if this becomes flaged with '!Austria' or '~Austria' ?
Will check this with my portable rig +
20 matches
Mail list logo
