If you're running an older rigctld backwards compatibility was broken and has
been fixed.
For now you should be able to use rigctld-wsjtx in WSJT-X which should always
work together.
de Mike W9MDB
On Wednesday, May 13, 2020, 11:59:32 PM CDT, Saku wrote:
Saku kirjoitti 14.5.2020
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
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
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
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
you
are using rigctld for connecting to a network server, I will check with
M0NNB if we can debug this offline (and put you in email copy).
- Lets maybe keep in mind that this was working in release 2.1.2.
73's and thanks again,
Erik
ON4PB
---
Message: 2
Date: Tue, 12 Ma
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
cting to a network server, I will check with
> M0NNB if we can debug this offline (and put you in email copy).
> - Lets maybe keep in mind that this was working in release 2.1.2.
>
> 73's and thanks again,
> Erik
> ON4PB
>
> ---
> Message: 2
> Date: Tue
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
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.
in mind that this was working in release 2.1.2.
73's and thanks again,
Erik
ON4PB
---
Message: 2
Date: Tue, 12 May 2020 22:34:02 +0100
From: Bill Somerville
To:wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no
lon
02 +0100
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no
longer works
Message-ID: <6bc371e6-9e40-e938-c597-98af91d1d...@classdesign.com>
Content-Type: text/plain; charset=utf-8; format=flowed
On 12/05
On 12/05/2020 22:16, runninge...@gmail.com wrote:
Hi,
thanks one more time for all the dedicated work with yet another big step
forward in decoding weal signals . !
Let me report that I am no longer able to CAT control my SparkSDR with the
"Hamlib NET rigctl" network server.
My settings are :
Hi,
thanks one more time for all the dedicated work with yet another big step
forward in decoding weal signals . !
Let me report that I am no longer able to CAT control my SparkSDR with the
"Hamlib NET rigctl" network server.
My settings are : "localhost:5" for Network server, which should
22 matches
Mail list logo
