Black Michael via wsjt-devel kirjoitti 14.5.2020 klo 7.42:
There is a bug in setting the frequency with rigctld which has been
fixed and should be in the next release.
Either today's hamlib snapshot or tomorrow's will also have the fix.
I'm not sure if the patch made it in to today's
Saku kirjoitti 14.5.2020 klo 7.25:
Hi!
Just compiled 2.2.0-rc1 and started it. (Fedora 31, 64-bit no
prebuild package)
Another test:
If i set rig as icom7300, device /dev/icom7300 (that is my symlinked
serial port) and serial settings ok wsjtx 2.2.0rc1 works.
But if I connect to
There is a bug in setting the frequency with rigctld which has been fixed and
should be in the next release.
Either today's hamlib snapshot or tomorrow's will also have the fix. I'm not
sure if the patch made it in to today's snapshot.
http://n0nb.users.sourceforge.net/
de Mike W9MDB
Hi!
Just compiled 2.2.0-rc1 and started it. (Fedora 31, 64-bit no prebuild
package)
Found out that after a short while I get error message:
Rig Failure Hamlib error: Feature not available while getting current vfo.
If I start wsjt-x 2.1.2 again it works ok, no Hamlib errors. 2.1.2 and
Hi Bill,
Yes this is with v2.2.0-rc1, Win 10 64 bit.
As I recall, it only occurred when there was just one late decode, and no
decodes in the following period. It happened several times in quick
succession, but I failed to get a screenshot or any more clues; and I
haven't seen it again. I
I installed the latest WSJT-X release candidate WSJT-X 2.2.0-rc0 and it seems
to be less resource hungry. I am now able to run 8 bands instead of 3 in FT8 on
the same computer. I am using a RP16 bit SDR with Aggregator.exe and
FT#Start.exe. The older version would also run, but would stop
On 14/05/2020 03:01, Dave K1SX wrote:
Hi Bill & all,
In years of using WSJT-X I've asked for a couple features, but never posted a
bug, much less a rig control issue. But I think I have one.
With my setup, on 2.2 RC1 operation of PTT via virtual serial port RTS control is
intermittent. Some
Hi Bill & all,
In years of using WSJT-X I've asked for a couple features, but never posted a
bug, much less a rig control issue. But I think I have one.
With my setup, on 2.2 RC1 operation of PTT via virtual serial port RTS control
is intermittent. Some transmit cycles work fine, while on
On 13/05/2020 23:02, Josh Rovero wrote:
On Windows 10 64-bit I am running 8 instances of 2.2.0-RC1 in FT8
mode. All are the same executable with different configurations.
About half of them have both text windows (Band Activity and Rx
Frequency), and the others have only the Band Activity
On 13/05/2020 23:02, Jesús Gutiérrez Rodríguez wrote:
I have downloaded and updated the new version of WSJT-X 2.2.0-rc1, but
note that it does not open the program.
I have created a new directory on an external disk and I still cannot
run the program nor show any possible error windows.
I have
On Windows 10 64-bit I am running 8 instances of 2.2.0-RC1 in FT8 mode.
All are the same executable with different configurations.
About half of them have both text windows (Band Activity and Rx Frequency),
and the others have only the Band Activity window. I have read (and
re-read) the manual
I have downloaded and updated the new version of WSJT-X 2.2.0-rc1, but note
that it does not open the program.
I have created a new directory on an external disk and I still cannot run
the program nor show any possible error windows.
I have gone back to the previous version, 2.1.2 and it works
Hi Tom,
the saved .WAV files go to the directory specified in "Settings->Audio"
panel the default is the "save" directory below the WSJT-X log files
directory (up one level from where you are looking).
73
Bill
G4WJS.
On 13/05/2020 19:47, n...@comcast.net wrote:
The save/samples dir is
The save/samples dir is empty.
Sent from Xfinity Connect Application
-Original Message-
From: g4...@classdesign.com
To: wsjt-devel@lists.sourceforge.net
Sent: 2020-05-13 1:36:01 PM
Subject: Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1
On 13/05/2020 18:29, n...@comcast.net wrote:
>
Hi Bill and Uwe,
I seen this once on wsjtx-2.2.0-rc1-win64.exe on PC running
Windows 10 Pro 1909 . I know the incoming signals were good as when i
switched backwards and forwards between WSJT-X and MSHV , MSHV
decoded correctly. WSJT-X showed signals on waterfall but no
decodes. .
Hi all
All this is using FT4, NA VHF - I haven't tried it in other modes.
If you are in a contest mode, you can change "TEST" to be something
else - I've been using HQP for the RSGB Hope QSO parties.
In previous versions this "stuck" until a reload.
In RC1 double clicking to reply, or hitting
Mike,
sending VFOA after the frequency makes it work, I'll do some testing with
fldigi etc and then include it in my next release. I'm not currently setup
to build hamlib and wsjtx but will get that going.
Thanks very much for that.
73 Alan M0NNB
On Wed, May 13, 2020 at 6:51 PM Black Michael via
Oops...make that code this instead...still have to parse the frequency.
CHKSCN1ARG(num_sscanf(buf, "%"SCNfreq, freq));
#if 0
ret = read_string(>state.rigport, buf, BUF_MAX, "\n", 1);
if (ret <= 0) { return (ret < 0) ? ret : -RIG_EPROTO; }
*vfotmp =
As a test try changing dummy/netrigctl.c line 622 and block out the code that
expects another argument from "f".
With the new code all you should need to do in spark is also provide the VFO
along with the frequency.So f is now is expected to answer like this to say
which VFO the frequency came
Hi Bill,
this is how spark currently works with a connection per virtual
transceiver, eliminating the need for virtual audio cables would be the
next level of simple. If I were to create a Hamlib module it would probably
just use the rigctl protocol which does not make much sense :), I'd prefer
to
On 13/05/2020 18:29, n...@comcast.net wrote:
Installed on pi4 after uninstall of previous version.
Used sudo dpkg with no errors.
Wsjtx is showing audio waveforms in wide graph.
But no decode.
Clock is correct. Mode is correct.
DE N2LO~>
Hi OM,
please enable "Menu->Save->Save All" and send us
Installed on pi4 after uninstall of previous version.
Used sudo dpkg with no errors.
Wsjtx is showing audio waveforms in wide graph.
But no decode.
Clock is correct. Mode is correct.
DE N2LO~>
Sent from Xfinity Connect Application
-Original Message-
From: j...@princeton.edu
To:
Hi Bill,
I have observed at least ten times that the decode button suddenly keeps its
turquoise color and the decoding seems to hang somehow. It is automatically
reset at the next decoding time. I saw this with the official file
wsjtx-2.2.0-rc1-win64.exe from the WSJT home page as well as with
Hi Alan,
there are already network capabilities that Hamlib back ends can access,
it is not tied to serial port connections by design, reference the Flex
6xxx one for example. Using individual connections per Rx must be the
way to go, then a client can open as many rig connections using the
On 13/05/2020 15:02, aso...@netvision.net.il wrote:
Dear WSJT-Devel
Is there a way, on multiple instance WSJT-X, to prevent more then one
instance from going into TX?
Yours sincerely
Amos Sobel 4X4MF
Hi Amos,
not within the software, there is no communications channel between
separate
Mike,
thanks very much, If there is anything I can do to help/test or change in
my software please let me know. I've been looking through the dump_state
source and that part is a bit of a reverse engineering job:) but if that is
the cause of the problem I'll dive in if it will fix it in the short
I'm going to see about fixing the backwards compatibility. Hopefully today...
Mike
On Wednesday, May 13, 2020, 09:27:48 AM CDT, Alan Hopper
wrote:
Hi Bill and Michaelthanks very much for your reply. I added the response to
'q' but as expected no magic fix. The error message from
Hi Bill and Michael
thanks very much for your reply. I added the response to 'q' but as
expected no magic fix. The error message from wsjtx is 'Hamlib error:
Communicatons timed out while getting current VFO frequency'.
If the protocol has not been published then it has been at least well
Dear WSJT-Devel
Is there a way, on multiple instance WSJT-X, to prevent more then one
instance from going into TX?
Yours sincerely
Amos Sobel 4X4MF
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Mike,
I gave it a go. I assume the 'master' branch is the one you want - I saw your
commits :-)
I installed it in a local dir, not in /usr or /opt:
./configure --prefix=/Users/dtiller/hamlib-master-prefix
--exec-prefix=/Users/dtiller/hamlib-master-eprefix
Here's the output:
WITH CACHE SET
On 13/05/2020 13:22, David Tiller wrote:
Thanks for the info, Bill and Mike!
I added the cache param and tried it with and without the -m parameter
- with the -m 3027 it failed, without it the command 'worked', but DID
NOT KEY THE RIG.
Hi David,
unfortunately it has not worked, the result
Are you able to compile hamlib?
de Mike W9MDB
On Wednesday, May 13, 2020, 07:48:25 AM CDT, David Tiller
wrote:
Thanks for the info, Bill and Mike!
I added the cache param and tried it with and without the -m parameter - with
the -m 3027 it failed, without it the command 'worked',
Thanks for the info, Bill and Mike!
I added the cache param and tried it with and without the -m parameter - with
the -m 3027 it failed, without it the command 'worked', but DID NOT KEY THE RIG.
WITHOUT -m 3027
dtiller$ ./Applications/wsjtx.app/Contents/MacOS/rigctl-wsjtx -p
On 13/05/2020 12:37, David Tiller wrote:
Bill,
Thanks for the speedy reply!
I see that the command specifies a rig - like I said, I only use the
given serial port for PTT, not for CAT commands. I'm not sure if that
changes anything.
The CAT port is /dev/cu.usbserial-1412*00*, but I set the
The internal protocol has never been published.The method to integrate is to
use the hamlib client interface.As it is your emulation doesn't do the
dump_state correctly for example.
Since SparkSDR is emulating a rig it's much more logical to write a backend for
SparkSDR or have SparkSDR emulate
On 13/05/2020 11:43, Alan Hopper wrote:
Hi Bill,
I'm the developer of SparkSDR, spark does indeed pretend to be rigctld
and is not the only one, QUISK also does the same thing. To my mind It
makes good sense to use a published proven network protocol rather
than invent yet another and then
Hi Bill,
I'm the developer of SparkSDR, spark does indeed pretend to be rigctld and
is not the only one, QUISK also does the same thing. To my mind It makes
good sense to use a published proven network protocol rather than invent
yet another and then have to write further software to use it.
This
On 13/05/2020 00:37, David Tiller wrote:
Dear devs,
I began using the latest release candidate today and love the early
decodes, but I noticed a few things that seemed to be not working
reliably under OSX.
My Setup: OSX 10.13.6, Icom 756PRO, and a RigExpert Standard. This
setup works
Hi Bill,
WSJT-X v.2.2.0-rc1 really works well. The new ft8 decoder is great! WSJT-X
now even beats JTDX in terms of the number of decodings. Huge improvement!
However, I (still) observe two minor bugs / unwanted behaviors:
1.) When coming back from hound mode Hold Tx Freq box is always
Hi Bill,
10.12 issue:
Thanks for pointing me to the project web-site
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
On 13/05/2020 10:11, John Nelson via wsjt-devel wrote:
Hi Bill,
I can confirm that rigctld embedded in 2.2.0-rc1 works as expected.
The only slight glitch is that rig numbers have changed. Whereas Kenwood
TS-870s and TS-790 used to be rigs: 210 and 207 respectively, riglist has been
On 13/05/2020 10:06, John Nelson via wsjt-devel wrote:
Hi Bill,
A problem reported to me that 2.2.0-rc1 will not load on MacOS 10.12.6. I
confirm that there is a problem with QtGui which was built for Mac OS X 10.13.
This error is from my version of 10.12
— John G4KLA
Process:
On 13/05/2020 08:09, DG2YCB, Uwe wrote:
Hi Bill,
I like to slightly change position of the "number of decodes" box, so
that it’s also visible when windows of two wsjt-x instances overlap
(see screenshot below). Where can I find specifications for position
of that box in the source code?
Hi Bill,
I can confirm that rigctld embedded in 2.2.0-rc1 works as expected.
The only slight glitch is that rig numbers have changed. Whereas Kenwood
TS-870s and TS-790 used to be rigs: 210 and 207 respectively, riglist has been
changed so that these are rigs 2010 and 2007 respectively.
Hi Bill,
A problem reported to me that 2.2.0-rc1 will not load on MacOS 10.12.6. I
confirm that there is a problem with QtGui which was built for Mac OS X 10.13.
This error is from my version of 10.12
— John G4KLA
Process: wsjtx [42790]
Path:
Hi Bill
Consider my last post obsolete. I found it. It is in mainwindow.cpp in under
void MainWindow::createStatusBar() . (lines 2235 - 2273). Move it one
position to the left. Now it looks like that:
73 de Uwe, DG2YCB
___
wsjt-devel mailing list
Hello Joe,
I send to jour e-mail adress the translated version of the manuel WSJT-X main
v2.2.0-rc1 in dutch.
Please confirm whether you have received it correctly.
Kind regards
ON4CKT Rudy
___
wsjt-devel mailing list
47 matches
Mail list logo
