|
Bill Somerville
Mike,
Hamlib is of no relevance here, at
least not for the original issue I am trying to investigate. N1MM
Logger+ emulates the DX Lab Suite Commander rig control server.
73
Bill
G4WJS.
On 14/09/2021 16:06, Michael Black via
groups.io wrote:
toggle quoted message
Show quoted text
FYI...the fix I put in
hamlib for this was to query mode and don't set it unless it
is changing.
That avoids the Icom filter
problem except for the first mode set if the rig isn't
already in the desired mode.
If you start the rig in
USB-D then the filter won't change at all.
Mike W9MDB
On Tuesday, September 14, 2021, 09:55:41 AM CDT, Bill
Somerville <g4wjs@...> wrote:
Hi
Bob,
that
would appear to be an issue with N1MM Logger+. So I
can be sure please put the attached file into the log
files directory of the WSJT-X instance that is using
N1MM Logger+ for rig control ("Menu->File->Open
log directory"), quit WSJT-X, restart WSJT-X,
replicate the issue with the minimum number of steps,
then quit WSJT-X. It will have created a log file
called WSJT-X_RigControl.log on your Desktop. Send me
(g4wjs <at> classdesign <dot> com) that
log file for analysis please?
Once
you have sent me the log file you can delete it and
the log configuration file to return to normal
operation.
73
Bill
G4WJS.
On
14/09/2021 15:47, Bob Turner wrote:
Bill,
I
stand corrected. I was running in non-contest
config when I answered that. I went back to
N1MM then launched WSJTx from within N1MM. The
correct answer is Mode=None.
I
start my test with rig manually set to USB-D and
Fil1. I am RX on VFO-A. Split on light on rig
is off. During TX on VFO-B rig split light
comes on. After TX, rig split light goes out,
I’m back on VFO-A and on Fil2.
Bob
OK,
so if you change that to Mode->None does the
issue you initially reported go away?
On
14/09/2021 15:33, Bob Turner wrote:
Mode=Data/Packet.
Not sure how I ended up with that setting.
73 Bob
N2SCJ
I
asked about the "Settings->Radio->Mode"
option. You stated you set the rig mode
manually. I asked if you had the
"Settings->Radio->Mode->None" option
checked. I asked that because with that
configuration WSJT-X should not be making any
mode or filter changes on you rig. I am trying
to determine if there is a defect where using
the "Settings->Radio->Mode->None"
option is somehow causing the filter settings
to change on your rig.
On
14/09/2021 15:25, Bob Turner wrote:
Bill,
Non
contest I use HRD Logger. HRD is not
involved with rig control. In addition HRD
Logger is on a different network PC. I let
WSJTX deal directly with IC-9700. Win4ICOM
is port sharing. All is ok in this
configuration.
Contest I
use N1MM for logging and rig control.
WSJTx asks N1MM to do what it needs. WSJTx
needs to use DXL Commander as the rig. My
intention was to let WSJTx do full control
with Split=Rig. I want WSJTx to change
frequency as needed to as to cut
off/minimize any birdies I may generate.
Then I noticed I can’t RX on Filter 1 /
Wide. I can set it to that for one RX
cycle, then after TX ends, RX goes to Filter
2 and stays there. I changed to Split=Fake
It. Problem went away. This is an
acceptable workaround for me. I never
tried Split=None as I assume that would
leave my TX frequency unchanged. I could be
wrong with this assumption.
I
recently worked with Mike W9MDB on a can’t
use Filter1 for RX issue with IC-7610. If
you need me to do any further testing or
have info for me, please let me know.
7 3 Bob
N2SCJ
On
14/09/2021 05:13, Bob Turner wrote:
While
using N1MM for rig control which I
understand emulates DX Labs Commander I ran
into the following issue with WSJTx. WSJTx
uses DX Labs Commander Suite as the rig.
For the rig I am using Rig=Split. I
manually set mode to USB-D, then set VFO-A
and VFO-B to Filter 1 (wide). Starting on
VFO-A. When WSJTx TX it tx on VFO-B with
Filter 1. So far so good. When TX ceases
I’m back on VFO-A on Filter 2. I wish to
remain on Filter 1 for RX as there are more
signals to decode. This may be a defect.
My
workaround is to set Split Operation to
rig=fake it. This allows me to stay on
Filter 1 for RX.
Assuming
my understanding of this issue is correct,
I’m hoping it can be addressed at some
point.
7
3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode
then I assume you have
"Settings->Radio->Mode->None" checked
in WSJT-X. With that setting WSJT-X should not
be making any changes to the rig's mode or
filter settings. Please confirm that if that
is not the case.
73
Bill
G4WJS.
|
|
|
FYI...the fix I put in hamlib for this was to query mode and don't set it unless it is changing. That avoids the Icom filter problem except for the first mode set if the rig isn't already in the desired mode.
If you start the rig in USB-D then the filter won't change at all.
Mike W9MDB
On Tuesday, September 14, 2021, 09:55:41 AM CDT, Bill Somerville <g4wjs@...> wrote:
Hi Bob,
that would appear to be an issue with
N1MM Logger+. So I can be sure please put the attached file into
the log files directory of the WSJT-X instance that is using N1MM
Logger+ for rig control ("Menu->File->Open log directory"),
quit WSJT-X, restart WSJT-X, replicate the issue with the minimum
number of steps, then quit WSJT-X. It will have created a log file
called WSJT-X_RigControl.log on your Desktop. Send me (g4wjs
<at> classdesign <dot> com) that log file for analysis
please?
Once you have sent me the log file you
can delete it and the log configuration file to return to normal
operation.
73
Bill
G4WJS.
On 14/09/2021 15:47, Bob Turner wrote:
Bill,
I
stand corrected. I was running in non-contest config when I
answered that. I went back to N1MM then launched WSJTx from
within N1MM. The correct answer is Mode=None.
I
start my test with rig manually set to USB-D and Fil1. I am
RX on VFO-A. Split on light on rig is off. During TX on
VFO-B rig split light comes on. After TX, rig split light
goes out, I’m back on VFO-A and on Fil2.
Bob
OK, so if you change that to Mode->None
does the issue you initially reported go away?
On 14/09/2021 15:33, Bob Turner wrote:
Mode=Data/Packet.
Not sure how I ended up with that setting.
73
Bob
N2SCJ
I
asked about the "Settings->Radio->Mode" option. You
stated you set the rig mode manually. I asked if you had the
"Settings->Radio->Mode->None" option checked. I
asked that because with that configuration WSJT-X should not
be making any mode or filter changes on you rig. I am trying
to determine if there is a defect where using the
"Settings->Radio->Mode->None" option is somehow
causing the filter settings to change on your rig.
On
14/09/2021 15:25, Bob Turner wrote:
Bill,
Non
contest I use HRD Logger. HRD is not involved with rig
control. In addition HRD Logger is on a different
network PC. I let WSJTX deal directly with IC-9700.
Win4ICOM is port sharing. All is ok in this
configuration.
Contest
I use N1MM for logging and rig control. WSJTx asks N1MM
to do what it needs. WSJTx needs to use DXL Commander as
the rig. My intention was to let WSJTx do full control
with Split=Rig. I want WSJTx to change frequency as
needed to as to cut off/minimize any birdies I may
generate. Then I noticed I can’t RX on Filter 1 / Wide.
I can set it to that for one RX cycle, then after TX
ends, RX goes to Filter 2 and stays there. I changed to
Split=Fake It. Problem went away. This is an acceptable
workaround for me. I never tried Split=None as I assume
that would leave my TX frequency unchanged. I could be
wrong with this assumption.
I
recently worked with Mike W9MDB on a can’t use Filter1 for
RX issue with IC-7610. If you need me to do any further
testing or have info for me, please let me know.
7
3 Bob
N2SCJ
On
14/09/2021 05:13, Bob Turner wrote:
While
using N1MM for rig control which I understand emulates DX
Labs Commander I ran into the following issue with WSJTx.
WSJTx uses DX Labs Commander Suite as the rig. For the
rig I am using Rig=Split. I manually set mode to USB-D,
then set VFO-A and VFO-B to Filter 1 (wide). Starting on
VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So
far so good. When TX ceases I’m back on VFO-A on Filter
2. I wish to remain on Filter 1 for RX as there are more
signals to decode. This may be a defect.
My
workaround is to set Split Operation to rig=fake it. This
allows me to stay on Filter 1 for RX.
Assuming
my understanding of this issue is correct, I’m hoping it
can be addressed at some point.
7
3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume
you have "Settings->Radio->Mode->None" checked in
WSJT-X. With that setting WSJT-X should not be making any
changes to the rig's mode or filter settings. Please confirm
that if that is not the case.
73
Bill
G4WJS.
|
|
|
Locked
Re: WSJT-x 2.5.0-rc6 in FST4W mode I can only select 2M band and above
#WSPR
#FST4W
Hi Bill,
Thanks, that right click wasn't obvious to me.
However, now when I select FST4W mode I get only three bands: 2200, 630 and 160 and I thought that FST4W is now the preferred mode on all bands.
Also, the 160M FST4W band is 200 Hz higher than the WSPR band. Is that correct and if so what is the logic behind it?
Unless 'jt9' will decode 1600-1800 Hz signals, specifying separate FST4W will complicate simultaneous decoding of WSPR and FST4W from one wav file recording.
73,
Rob
|
|
|
In N1MM+, what are the settings in the Configurer under the Mode Control tab, right-hand side, "Mode sent to radio" in the DIGI row? If you don't want N1MM+ to issue mode and filter commands to the radio when it switches bands, modes or VFOs, you may want to set these to "No change".
73,
Rich VE3KI
toggle quoted message
Show quoted text
On Tue, Sep 14, 2021 at 10:55 AM, Bill Somerville wrote:
Hi Bob,
that would appear to be an issue with N1MM Logger+. So I can be sure please put the attached file into the log files directory of the WSJT-X instance that is using N1MM Logger+ for rig control ("Menu->File->Open log directory"), quit WSJT-X, restart WSJT-X, replicate the issue with the minimum number of steps, then quit WSJT-X. It will have created a log file called WSJT-X_RigControl.log on your Desktop. Send me (g4wjs <at> classdesign <dot> com) that log file for analysis please?
Once you have sent me the log file you can delete it and the log configuration file to return to normal operation.
73
Bill
G4WJS.
On 14/09/2021 15:47, Bob Turner wrote:
Bill,
I stand corrected. I was running in non-contest config when I answered that. I went back to N1MM then launched WSJTx from within N1MM. The correct answer is Mode=None.
I start my test with rig manually set to USB-D and Fil1. I am RX on VFO-A. Split on light on rig is off. During TX on VFO-B rig split light comes on. After TX, rig split light goes out, I’m back on VFO-A and on Fil2.
Bob
OK, so if you change that to Mode->None does the issue you initially reported go away?
On 14/09/2021 15:33, Bob Turner wrote:
Mode=Data/Packet. Not sure how I ended up with that setting.
73 Bob
N2SCJ
I asked about the "Settings->Radio->Mode" option. You stated you set the rig mode manually. I asked if you had the "Settings->Radio->Mode->None" option checked. I asked that because with that configuration WSJT-X should not be making any mode or filter changes on you rig. I am trying to determine if there is a defect where using the "Settings->Radio->Mode->None" option is somehow causing the filter settings to change on your rig.
On 14/09/2021 15:25, Bob Turner wrote:
Bill,
Non contest I use HRD Logger. HRD is not involved with rig control. In addition HRD Logger is on a different network PC. I let WSJTX deal directly with IC-9700. Win4ICOM is port sharing. All is ok in this configuration.
Contest I use N1MM for logging and rig control. WSJTx asks N1MM to do what it needs. WSJTx needs to use DXL Commander as the rig. My intention was to let WSJTx do full control with Split=Rig. I want WSJTx to change frequency as needed to as to cut off/minimize any birdies I may generate. Then I noticed I can’t RX on Filter 1 / Wide. I can set it to that for one RX cycle, then after TX ends, RX goes to Filter 2 and stays there. I changed to Split=Fake It. Problem went away. This is an acceptable workaround for me. I never tried Split=None as I assume that would leave my TX frequency unchanged. I could be wrong with this assumption.
I recently worked with Mike W9MDB on a can’t use Filter1 for RX issue with IC-7610. If you need me to do any further testing or have info for me, please let me know.
7 3 Bob
N2SCJ
On 14/09/2021 05:13, Bob Turner wrote:
While using N1MM for rig control which I understand emulates DX Labs Commander I ran into the following issue with WSJTx. WSJTx uses DX Labs Commander Suite as the rig. For the rig I am using Rig=Split. I manually set mode to USB-D, then set VFO-A and VFO-B to Filter 1 (wide). Starting on VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So far so good. When TX ceases I’m back on VFO-A on Filter 2. I wish to remain on Filter 1 for RX as there are more signals to decode. This may be a defect.
My workaround is to set Split Operation to rig=fake it. This allows me to stay on Filter 1 for RX.
Assuming my understanding of this issue is correct, I’m hoping it can be addressed at some point.
7 3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you have "Settings->Radio->Mode->None" checked in WSJT-X. With that setting WSJT-X should not be making any changes to the rig's mode or filter settings. Please confirm that if that is not the case.
73
Bill
G4WJS.
|
|
|
Try this patch
diff --git a/rigs/dummy/flrig.c b/rigs/dummy/flrig.c index d5864d92..96b226f2 100644
--- a/rigs/dummy/flrig.c
+++ b/rigs/dummy/flrig.c
@@ -144,7 +144,7 @@ const struct rig_caps flrig_caps =
RIG_MODEL(RIG_MODEL_FLRIG),
.model_name = "FLRig",
.mfg_name = "FLRig",
- .version = "202100911",
+ .version = "202100914",
.copyright = "LGPL",
.status = RIG_STATUS_STABLE,
.rig_type = RIG_TYPE_TRANSCEIVER,
@@ -796,12 +796,12 @@ static int flrig_open(RIG *rig)
if (retval != RIG_OK)
{
- rig_debug(RIG_DEBUG_ERR, "%s: get_version failed: %s\n", __func__,
+ rig_debug(RIG_DEBUG_ERR, "%s: get_version failed: %s\nAssuming version < 1.3.54", __func__,
rigerror(retval));
- RETURNFUNC(retval);
+ // we fall through and assume old version
}
- int v1, v2, v3, v4;
+ int v1=0, v2=0, v3=0, v4=0;
sscanf(value, "%d.%d.%d.%d", &v1, &v2, &v3, &v4);
On Tuesday, September 14, 2021, 07:58:10 AM CDT, Bill Somerville <g4wjs@...> wrote: Hi Mike, I have built the latest flrig sources but that doesn't seem to work with flrig configured for Rig=NONE as it gives this error: Ignoring that I get this error from WSJT-X on pressimg "Test CAT": Hamlib error: Protocol error flrig.c(604):flrig_transaction return(8) flrig.c(907):flrig_open return(8) rig.c(1026):rig_open return(8) while opening connection to rig So I guess flrig is not working enough to even start testing this. 73 Bill G4WJS.
On 14/09/2021 13:04, Bill Somerville wrote:
>
> Hi Mike,
>
>
>
>
> trying this anyway. The first issue I hit using WSJT-X v2.5.0 RC6 and the version of flrig in the Raspberry Pi OS repos, which is 1.3.42, is this error on initialization ("Settings->Radio->Test CAT"):
>
> Hamlib error: Feature not available
> flrig_open: get_version failed: Feature not available
> flrig.c(511):read_transaction return(0)
> flrig.c(594):flrig_transaction return(11)
> flrig.c(594):flrig_transaction return(11)flrig.c(801):flrig_open return(11)
> rig.c(1026):rig_open return(11) while opening connection to rig
>
>
> 73
> Bill
> G4WJS.
>
>
>
>
> On 14/09/2021 12:36, Bill Somerville wrote:
>
>
>>
>> Hi Mike,
>>
>>
>>
>>
>> I assume this issue is as yet unresolved. Can I do anything to help? I have Raspberry Pi systems but not connected to any rig. Is it sufficient to install flrig and run it in some sort of dummy rig configuration to reproduce this issue?
>>
>>
>>
>>
>> 73
>> Bill
>> G4WJS.
>>
>>
>>
>>
>> On 14/09/2021 04:30, Michael Black via groups.io wrote:
>>
>>
>>>
>>>
>>>
>>> Yes I need a debug log. All that error says is the network open failed.
>>>
>>>
>>>
>>>
>>> What do you have for the PTT settings in WSJTX?
>>>
>>>
>>>
>>>
>>> Mike W9MDB
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Monday, September 13, 2021, 10:24:27 PM CDT, S Johnson <cascadianroot@...> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> OK, I compiled Hamlib4.4 and changed WSJTX radiio to Hamlib NET rigctl. I also had updated WSJTX to the experimental version 2.5.0 RC6 version.
>>>
>>> The behavior is now different, but still not usable. Now, I can change modes and wide-graph "goalposts" and WSJTX does not crash. WSJTX is receiving and decoding. But when I try to transmit the radio does not respond -- it continues to receive an displays this error message:
>>>
>>>
>>> Hamlib error: IO error
>>>
>>> network.c(298):network_open return(-6)
>>>
>>> iofunc.c(177):port_open return(-6)
>>> rig.c(795):rig_open return(-6) while opening connection to rig.
>>>
>>> There may be some other Hamlib rigctl setting I am missing as I am not familiar with this setup. I had been using "rigctl rigctl" in my WSJTX configuration.
>>>
>>> Do you still need a debug or log file from this software configuration?
>>>
>>>
>>>
>>>
>>>
>>
>
|
|
|
Bill Somerville
Hi Bob,
that would appear to be an issue with
N1MM Logger+. So I can be sure please put the attached file into
the log files directory of the WSJT-X instance that is using N1MM
Logger+ for rig control ("Menu->File->Open log directory"),
quit WSJT-X, restart WSJT-X, replicate the issue with the minimum
number of steps, then quit WSJT-X. It will have created a log file
called WSJT-X_RigControl.log on your Desktop. Send me (g4wjs
<at> classdesign <dot> com) that log file for analysis
please?
Once you have sent me the log file you
can delete it and the log configuration file to return to normal
operation.
73
Bill
G4WJS.
On 14/09/2021 15:47, Bob Turner wrote:
toggle quoted message
Show quoted text
Bill,
I
stand corrected. I was running in non-contest config when I
answered that. I went back to N1MM then launched WSJTx from
within N1MM. The correct answer is Mode=None.
I
start my test with rig manually set to USB-D and Fil1. I am
RX on VFO-A. Split on light on rig is off. During TX on
VFO-B rig split light comes on. After TX, rig split light
goes out, I’m back on VFO-A and on Fil2.
Bob
OK, so if you change that to Mode->None
does the issue you initially reported go away?
On 14/09/2021 15:33, Bob Turner wrote:
Mode=Data/Packet.
Not sure how I ended up with that setting.
73
Bob
N2SCJ
I
asked about the "Settings->Radio->Mode" option. You
stated you set the rig mode manually. I asked if you had the
"Settings->Radio->Mode->None" option checked. I
asked that because with that configuration WSJT-X should not
be making any mode or filter changes on you rig. I am trying
to determine if there is a defect where using the
"Settings->Radio->Mode->None" option is somehow
causing the filter settings to change on your rig.
On
14/09/2021 15:25, Bob Turner wrote:
Bill,
Non
contest I use HRD Logger. HRD is not involved with rig
control. In addition HRD Logger is on a different
network PC. I let WSJTX deal directly with IC-9700.
Win4ICOM is port sharing. All is ok in this
configuration.
Contest
I use N1MM for logging and rig control. WSJTx asks N1MM
to do what it needs. WSJTx needs to use DXL Commander as
the rig. My intention was to let WSJTx do full control
with Split=Rig. I want WSJTx to change frequency as
needed to as to cut off/minimize any birdies I may
generate. Then I noticed I can’t RX on Filter 1 / Wide.
I can set it to that for one RX cycle, then after TX
ends, RX goes to Filter 2 and stays there. I changed to
Split=Fake It. Problem went away. This is an acceptable
workaround for me. I never tried Split=None as I assume
that would leave my TX frequency unchanged. I could be
wrong with this assumption.
I
recently worked with Mike W9MDB on a can’t use Filter1 for
RX issue with IC-7610. If you need me to do any further
testing or have info for me, please let me know.
7
3 Bob
N2SCJ
On
14/09/2021 05:13, Bob Turner wrote:
While
using N1MM for rig control which I understand emulates DX
Labs Commander I ran into the following issue with WSJTx.
WSJTx uses DX Labs Commander Suite as the rig. For the
rig I am using Rig=Split. I manually set mode to USB-D,
then set VFO-A and VFO-B to Filter 1 (wide). Starting on
VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So
far so good. When TX ceases I’m back on VFO-A on Filter
2. I wish to remain on Filter 1 for RX as there are more
signals to decode. This may be a defect.
My
workaround is to set Split Operation to rig=fake it. This
allows me to stay on Filter 1 for RX.
Assuming
my understanding of this issue is correct, I’m hoping it
can be addressed at some point.
7
3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume
you have "Settings->Radio->Mode->None" checked in
WSJT-X. With that setting WSJT-X should not be making any
changes to the rig's mode or filter settings. Please confirm
that if that is not the case.
73
Bill
G4WJS.
|
|
|
Bill,
I stand corrected. I was running in non-contest config when I answered that. I went back to N1MM then launched WSJTx from within N1MM. The correct answer is
Mode=None.
I start my test with rig manually set to USB-D and Fil1. I am RX on VFO-A. Split on light on rig is off. During TX on VFO-B rig split light comes on. After
TX, rig split light goes out, I’m back on VFO-A and on Fil2.
Bob
toggle quoted message
Show quoted text
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io]
On Behalf Of Bill Somerville
Sent: Tuesday, September 14, 2021 10:36 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Possible DXL Commander defect with IC-9700 and WSJTx #Cat_RigControl
OK, so if you change that to Mode->None does the issue you initially reported go away?
On 14/09/2021 15:33, Bob Turner wrote:
Mode=Data/Packet. Not sure how I ended up with that setting.
73 Bob
N2SCJ
I asked about the "Settings->Radio->Mode" option. You stated you set the rig mode manually. I asked if you had the "Settings->Radio->Mode->None" option checked. I asked that because
with that configuration WSJT-X should not be making any mode or filter changes on you rig. I am trying to determine if there is a defect where using the "Settings->Radio->Mode->None" option is somehow causing the filter settings to change on your rig.
On 14/09/2021 15:25, Bob Turner wrote:
Bill,
Non contest I use HRD Logger. HRD is not involved with rig control. In addition HRD Logger is on
a different network PC. I let WSJTX deal directly with IC-9700. Win4ICOM is port sharing. All is ok in this configuration.
Contest I use N1MM for logging and rig control. WSJTx asks N1MM to do what it needs. WSJTx needs
to use DXL Commander as the rig. My intention was to let WSJTx do full control with Split=Rig. I want WSJTx to change frequency as needed to as to cut off/minimize any birdies I may generate. Then I noticed I can’t RX on Filter 1 / Wide. I can set it
to that for one RX cycle, then after TX ends, RX goes to Filter 2 and stays there. I changed to Split=Fake It. Problem went away. This is an acceptable workaround for me. I never tried Split=None as I assume that would leave my TX frequency unchanged.
I could be wrong with this assumption.
I recently worked with Mike W9MDB on a can’t use Filter1 for RX issue with IC-7610. If you need me
to do any further testing or have info for me, please let me know.
7 3 Bob
N2SCJ
On 14/09/2021 05:13, Bob Turner wrote:
While using N1MM for rig control which I understand emulates DX Labs Commander I ran into the following issue with WSJTx. WSJTx uses DX Labs Commander Suite as the rig. For the
rig I am using Rig=Split. I manually set mode to USB-D, then set VFO-A and VFO-B to Filter 1 (wide). Starting on VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So far so good. When TX ceases I’m back on VFO-A on Filter 2. I wish to remain on Filter
1 for RX as there are more signals to decode. This may be a defect.
My workaround is to set Split Operation to rig=fake it. This allows me to stay on Filter 1 for RX.
Assuming my understanding of this issue is correct, I’m hoping it can be addressed at some point.
7 3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you have "Settings->Radio->Mode->None" checked in WSJT-X. With that setting WSJT-X should not be making any changes to the rig's mode or filter settings. Please confirm that if that is not the case.
73
Bill
G4WJS.
|
|
|
Bill Somerville
Hi Bob,
OK, so if you change that to
Mode->None does the issue you initially reported go away?
73
Bill
G4WJS.
On 14/09/2021 15:33, Bob Turner wrote:
toggle quoted message
Show quoted text
Mode=Data/Packet.
Not sure how I ended up with that setting.
73
Bob
N2SCJ
I asked about the
"Settings->Radio->Mode" option. You stated you set the
rig mode manually. I asked if you had the
"Settings->Radio->Mode->None" option checked. I asked
that because with that configuration WSJT-X should not be
making any mode or filter changes on you rig. I am trying to
determine if there is a defect where using the
"Settings->Radio->Mode->None" option is somehow
causing the filter settings to change on your rig.
On 14/09/2021 15:25, Bob Turner wrote:
Bill,
Non
contest I use HRD Logger. HRD is not involved with rig
control. In addition HRD Logger is on a different network
PC. I let WSJTX deal directly with IC-9700. Win4ICOM is
port sharing. All is ok in this configuration.
Contest
I use N1MM for logging and rig control. WSJTx asks N1MM to
do what it needs. WSJTx needs to use DXL Commander as the
rig. My intention was to let WSJTx do full control with
Split=Rig. I want WSJTx to change frequency as needed to
as to cut off/minimize any birdies I may generate. Then I
noticed I can’t RX on Filter 1 / Wide. I can set it to that
for one RX cycle, then after TX ends, RX goes to Filter 2
and stays there. I changed to Split=Fake It. Problem went
away. This is an acceptable workaround for me. I never
tried Split=None as I assume that would leave my TX
frequency unchanged. I could be wrong with this assumption.
I
recently worked with Mike W9MDB on a can’t use Filter1 for
RX issue with IC-7610. If you need me to do any further
testing or have info for me, please let me know.
7
3 Bob
N2SCJ
On
14/09/2021 05:13, Bob Turner wrote:
While
using N1MM for rig control which I understand emulates DX
Labs Commander I ran into the following issue with WSJTx.
WSJTx uses DX Labs Commander Suite as the rig. For the rig
I am using Rig=Split. I manually set mode to USB-D, then
set VFO-A and VFO-B to Filter 1 (wide). Starting on VFO-A.
When WSJTx TX it tx on VFO-B with Filter 1. So far so
good. When TX ceases I’m back on VFO-A on Filter 2. I wish
to remain on Filter 1 for RX as there are more signals to
decode. This may be a defect.
My
workaround is to set Split Operation to rig=fake it. This
allows me to stay on Filter 1 for RX.
Assuming
my understanding of this issue is correct, I’m hoping it can
be addressed at some point.
7
3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you
have "Settings->Radio->Mode->None" checked in WSJT-X.
With that setting WSJT-X should not be making any changes to
the rig's mode or filter settings. Please confirm that if that
is not the case.
73
Bill
G4WJS.
|
|
|
Mode=Data/Packet. Not sure how I ended up with that setting.
73 Bob
N2SCJ
toggle quoted message
Show quoted text
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io]
On Behalf Of Bill Somerville
Sent: Tuesday, September 14, 2021 10:30 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Possible DXL Commander defect with IC-9700 and WSJTx #Cat_RigControl
I asked about the "Settings->Radio->Mode" option. You stated you set the rig mode manually. I asked if you had the "Settings->Radio->Mode->None" option checked. I asked that because with that configuration WSJT-X should not be making any
mode or filter changes on you rig. I am trying to determine if there is a defect where using the "Settings->Radio->Mode->None" option is somehow causing the filter settings to change on your rig.
On 14/09/2021 15:25, Bob Turner wrote:
Bill,
Non contest I use HRD Logger. HRD is not involved with rig control. In addition HRD Logger is on
a different network PC. I let WSJTX deal directly with IC-9700. Win4ICOM is port sharing. All is ok in this configuration.
Contest I use N1MM for logging and rig control. WSJTx asks N1MM to do what it needs. WSJTx needs
to use DXL Commander as the rig. My intention was to let WSJTx do full control with Split=Rig. I want WSJTx to change frequency as needed to as to cut off/minimize any birdies I may generate. Then I noticed I can’t RX on Filter 1 / Wide. I can set it
to that for one RX cycle, then after TX ends, RX goes to Filter 2 and stays there. I changed to Split=Fake It. Problem went away. This is an acceptable workaround for me. I never tried Split=None as I assume that would leave my TX frequency unchanged.
I could be wrong with this assumption.
I recently worked with Mike W9MDB on a can’t use Filter1 for RX issue with IC-7610. If you need me
to do any further testing or have info for me, please let me know.
7 3 Bob
N2SCJ
On 14/09/2021 05:13, Bob Turner wrote:
While using N1MM for rig control which I understand emulates DX Labs Commander I ran into the following issue with WSJTx. WSJTx uses DX Labs Commander Suite as the rig. For the
rig I am using Rig=Split. I manually set mode to USB-D, then set VFO-A and VFO-B to Filter 1 (wide). Starting on VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So far so good. When TX ceases I’m back on VFO-A on Filter 2. I wish to remain on Filter
1 for RX as there are more signals to decode. This may be a defect.
My workaround is to set Split Operation to rig=fake it. This allows me to stay on Filter 1 for RX.
Assuming my understanding of this issue is correct, I’m hoping it can be addressed at some point.
7 3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you have "Settings->Radio->Mode->None" checked in WSJT-X. With that setting WSJT-X should not be making any changes to the rig's mode or filter settings. Please confirm that if that is not the case.
73
Bill
G4WJS.
|
|
|
Bill Somerville
Bob,
I asked about the
"Settings->Radio->Mode" option. You stated you set the rig
mode manually. I asked if you had the
"Settings->Radio->Mode->None" option checked. I asked
that because with that configuration WSJT-X should not be making
any mode or filter changes on you rig. I am trying to determine if
there is a defect where using the
"Settings->Radio->Mode->None" option is somehow causing
the filter settings to change on your rig.
73
Bill
G4WJS.
On 14/09/2021 15:25, Bob Turner wrote:
toggle quoted message
Show quoted text
Bill,
Non
contest I use HRD Logger. HRD is not involved with rig
control. In addition HRD Logger is on a different network
PC. I let WSJTX deal directly with IC-9700. Win4ICOM is
port sharing. All is ok in this configuration.
Contest
I use N1MM for logging and rig control. WSJTx asks N1MM to
do what it needs. WSJTx needs to use DXL Commander as the
rig. My intention was to let WSJTx do full control with
Split=Rig. I want WSJTx to change frequency as needed to as
to cut off/minimize any birdies I may generate. Then I
noticed I can’t RX on Filter 1 / Wide. I can set it to that
for one RX cycle, then after TX ends, RX goes to Filter 2 and
stays there. I changed to Split=Fake It. Problem went away.
This is an acceptable workaround for me. I never tried
Split=None as I assume that would leave my TX frequency
unchanged. I could be wrong with this assumption.
I
recently worked with Mike W9MDB on a can’t use Filter1 for RX
issue with IC-7610. If you need me to do any further testing
or have info for me, please let me know.
7
3 Bob
N2SCJ
On 14/09/2021 05:13, Bob Turner wrote:
While
using N1MM for rig control which I understand emulates DX Labs
Commander I ran into the following issue with WSJTx. WSJTx
uses DX Labs Commander Suite as the rig. For the rig I am
using Rig=Split. I manually set mode to USB-D, then set VFO-A
and VFO-B to Filter 1 (wide). Starting on VFO-A. When WSJTx
TX it tx on VFO-B with Filter 1. So far so good. When TX
ceases I’m back on VFO-A on Filter 2. I wish to remain on
Filter 1 for RX as there are more signals to decode. This may
be a defect.
My
workaround is to set Split Operation to rig=fake it. This
allows me to stay on Filter 1 for RX.
Assuming
my understanding of this issue is correct, I’m hoping it can
be addressed at some point.
7
3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you
have "Settings->Radio->Mode->None" checked in WSJT-X.
With that setting WSJT-X should not be making any changes to the
rig's mode or filter settings. Please confirm that if that is
not the case.
73
Bill
G4WJS.
|
|
|
Bill,
Non contest I use HRD Logger. HRD is not involved with rig control. In addition HRD Logger is on a different network PC. I let WSJTX deal directly with IC-9700.
Win4ICOM is port sharing. All is ok in this configuration.
Contest I use N1MM for logging and rig control. WSJTx asks N1MM to do what it needs. WSJTx needs to use DXL Commander as the rig. My intention was to let
WSJTx do full control with Split=Rig. I want WSJTx to change frequency as needed to as to cut off/minimize any birdies I may generate. Then I noticed I can’t RX on Filter 1 / Wide. I can set it to that for one RX cycle, then after TX ends, RX goes to
Filter 2 and stays there. I changed to Split=Fake It. Problem went away. This is an acceptable workaround for me. I never tried Split=None as I assume that would leave my TX frequency unchanged. I could be wrong with this assumption.
I recently worked with Mike W9MDB on a can’t use Filter1 for RX issue with IC-7610. If you need me to do any further testing or have info for me, please let
me know.
7 3 Bob
N2SCJ
toggle quoted message
Show quoted text
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io]
On Behalf Of Bill Somerville
Sent: Tuesday, September 14, 2021 6:09 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Possible DXL Commander defect with IC-9700 and WSJTx #Cat_RigControl
On 14/09/2021 05:13, Bob Turner wrote:
While using N1MM for rig control which I understand emulates DX Labs Commander I ran into the following issue with WSJTx. WSJTx uses DX Labs Commander Suite as the rig. For the
rig I am using Rig=Split. I manually set mode to USB-D, then set VFO-A and VFO-B to Filter 1 (wide). Starting on VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So far so good. When TX ceases I’m back on VFO-A on Filter 2. I wish to remain on Filter
1 for RX as there are more signals to decode. This may be a defect.
My workaround is to set Split Operation to rig=fake it. This allows me to stay on Filter 1 for RX.
Assuming my understanding of this issue is correct, I’m hoping it can be addressed at some point.
7 3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you have "Settings->Radio->Mode->None" checked in WSJT-X. With that setting WSJT-X should not be making any changes to the rig's mode or filter settings. Please confirm that if that is not the case.
73
Bill
G4WJS.
|
|
|
Locked
Re: WSJT-x 2.5.0-rc6 in FST4W mode I can only select 2M band and above
#WSPR
#FST4W
Bill Somerville
On 14/09/2021 14:29, Rob Robinett wrote: I have found WSJT-X->Settings->Frequencies includes no FST4* Modes. However can't find any 'Reset' control anywhere.
Deleting WSJT-x and reinstalling it didn't fix the problem.
Thanks 73 Hi Rob, go to "Settings->Frequencies", then *right-click* the body of the Working Frequencies table, and press the Reset button. 73 Bill G4WJS.
|
|
|
Locked
Re: WSJT-x 2.5.0-rc6 in FST4W mode I can only select 2M band and above
#WSPR
#FST4W
I have found WSJT-X->Settings->Frequencies includes no FST4* Modes. However can't find any 'Reset' control anywhere.
Deleting WSJT-x and reinstalling it didn't fix the problem.
Thanks 73
|
|
|
Bill Somerville
Hi Mike,
I have built the latest flrig sources
but that doesn't seem to work with flrig configured for Rig=NONE
as it gives this error:
Ignoring that I get this error from
WSJT-X on pressimg "Test CAT":
Hamlib error: Protocol error
flrig.c(604):flrig_transaction return(8)
flrig.c(907):flrig_open return(8)
rig.c(1026):rig_open return(8) while opening connection to rig
So I guess flrig is not working enough
to even start testing this.
73
Bill
G4WJS.
On 14/09/2021 13:04, Bill Somerville
wrote:
toggle quoted message
Show quoted text
Hi Mike,
trying this anyway. The first issue I
hit using WSJT-X v2.5.0 RC6 and the version of flrig in the
Raspberry Pi OS repos, which is 1.3.42, is this error on
initialization ("Settings->Radio->Test CAT"):
Hamlib error: Feature not available
flrig_open: get_version failed: Feature not available
flrig.c(511):read_transaction return(0)
flrig.c(594):flrig_transaction return(11)
flrig.c(594):flrig_transaction return(11)flrig.c(801):flrig_open return(11)
rig.c(1026):rig_open return(11) while opening connection to rig
73
Bill
G4WJS.
On 14/09/2021 12:36, Bill Somerville
wrote:
Hi Mike,
I assume this issue is as yet
unresolved. Can I do anything to help? I have Raspberry Pi
systems but not connected to any rig. Is it sufficient to
install flrig and run it in some sort of dummy rig
configuration to reproduce this issue?
73
Bill
G4WJS.
On 14/09/2021 04:30, Michael Black
via groups.io wrote:
Yes I need a debug
log. All that error says is the network open failed.
What do you have for
the PTT settings in WSJTX?
Mike W9MDB
OK, I compiled Hamlib4.4 and changed WSJTX radiio
to Hamlib NET rigctl. I also had updated WSJTX to
the experimental version 2.5.0 RC6 version.
The behavior is now different, but still not
usable. Now, I can change modes and wide-graph
"goalposts" and WSJTX does not crash. WSJTX is
receiving and decoding. But when I try to transmit
the radio does not respond -- it continues to
receive an displays this error message:
Hamlib error: IO error
network.c(298):network_open return(-6)
iofunc.c(177):port_open return(-6)
rig.c(795):rig_open return(-6) while opening connection to rig.
There may be some other Hamlib rigctl setting I am
missing as I am not familiar with this setup. I had
been using "rigctl rigctl" in my WSJTX
configuration.
Do you still need a debug or log file from this
software configuration?
|
|
|
You are using the same workaround that I use. I never found that "split" worked very well, on any radio that I own or owned - with or without the N1MM software. Fake it works just perfectly fine.
Buddy WB4OMG
-----Original Message-----
From: Bob Turner <n2scj-lists@...>
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Sent: Tue, Sep 14, 2021 12:13 am
Subject: [WSJTX] Possible DXL Commander defect with IC-9700 and WSJTx #Cat_RigControl
While using N1MM for rig control which I understand emulates DX Labs Commander I ran into the following issue with WSJTx. WSJTx uses DX Labs Commander Suite as the rig. For the rig I am using Rig=Split. I manually set mode to USB-D,
then set VFO-A and VFO-B to Filter 1 (wide). Starting on VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So far so good. When TX ceases I’m back on VFO-A on Filter 2. I wish to remain on Filter 1 for RX as there are more signals to decode. This may
be a defect.
My workaround is to set Split Operation to rig=fake it. This allows me to stay on Filter 1 for RX.
Assuming my understanding of this issue is correct, I’m hoping it can be addressed at some point.
7 3 Bob
N2SCJ
|
|
|
Bill Somerville
Hi Mike,
trying this anyway. The first issue I
hit using WSJT-X v2.5.0 RC6 and the version of flrig in the
Raspberry Pi OS repos, which is 1.3.42, is this error on
initialization ("Settings->Radio->Test CAT"):
Hamlib error: Feature not available
flrig_open: get_version failed: Feature not available
flrig.c(511):read_transaction return(0)
flrig.c(594):flrig_transaction return(11)
flrig.c(594):flrig_transaction return(11)flrig.c(801):flrig_open return(11)
rig.c(1026):rig_open return(11) while opening connection to rig
73
Bill
G4WJS.
On 14/09/2021 12:36, Bill Somerville
wrote:
toggle quoted message
Show quoted text
Hi Mike,
I assume this issue is as yet
unresolved. Can I do anything to help? I have Raspberry Pi
systems but not connected to any rig. Is it sufficient to
install flrig and run it in some sort of dummy rig configuration
to reproduce this issue?
73
Bill
G4WJS.
On 14/09/2021 04:30, Michael Black
via groups.io wrote:
Yes I need a debug log.
All that error says is the network open failed.
What do you have for the
PTT settings in WSJTX?
Mike W9MDB
OK, I compiled Hamlib4.4 and changed WSJTX radiio
to Hamlib NET rigctl. I also had updated WSJTX to the
experimental version 2.5.0 RC6 version.
The behavior is now different, but still not usable.
Now, I can change modes and wide-graph "goalposts" and
WSJTX does not crash. WSJTX is receiving and
decoding. But when I try to transmit the radio does
not respond -- it continues to receive an displays
this error message:
Hamlib error: IO error
network.c(298):network_open return(-6)
iofunc.c(177):port_open return(-6)
rig.c(795):rig_open return(-6) while opening connection to rig.
There may be some other Hamlib rigctl setting I am
missing as I am not familiar with this setup. I had
been using "rigctl rigctl" in my WSJTX configuration.
Do you still need a debug or log file from this
software configuration?
|
|
|
Bill Somerville
Hi Mike,
I assume this issue is as yet
unresolved. Can I do anything to help? I have Raspberry Pi systems
but not connected to any rig. Is it sufficient to install flrig
and run it in some sort of dummy rig configuration to reproduce
this issue?
73
Bill
G4WJS.
On 14/09/2021 04:30, Michael Black via
groups.io wrote:
toggle quoted message
Show quoted text
Yes I need a debug log.
All that error says is the network open failed.
What do you have for the
PTT settings in WSJTX?
Mike W9MDB
OK, I compiled Hamlib4.4 and changed WSJTX radiio to
Hamlib NET rigctl. I also had updated WSJTX to the
experimental version 2.5.0 RC6 version.
The behavior is now different, but still not usable.
Now, I can change modes and wide-graph "goalposts" and
WSJTX does not crash. WSJTX is receiving and decoding.
But when I try to transmit the radio does not respond --
it continues to receive an displays this error message:
Hamlib error: IO error
network.c(298):network_open return(-6)
iofunc.c(177):port_open return(-6)
rig.c(795):rig_open return(-6) while opening connection to rig.
There may be some other Hamlib rigctl setting I am
missing as I am not familiar with this setup. I had
been using "rigctl rigctl" in my WSJTX configuration.
Do you still need a debug or log file from this software
configuration?
|
|
|
Bill Somerville
On 14/09/2021 05:13, Bob Turner wrote:
While using N1MM for rig control which I
understand emulates DX Labs Commander I ran into the following
issue with WSJTx. WSJTx uses DX Labs Commander Suite as the
rig. For the rig I am using Rig=Split. I manually set mode to
USB-D, then set VFO-A and VFO-B to Filter 1 (wide). Starting on
VFO-A. When WSJTx TX it tx on VFO-B with Filter 1. So far so
good. When TX ceases I’m back on VFO-A on Filter 2. I wish to
remain on Filter 1 for RX as there are more signals to decode.
This may be a defect.
My workaround is to set Split Operation to
rig=fake it. This allows me to stay on Filter 1 for RX.
Assuming my understanding of this issue is
correct, I’m hoping it can be addressed at some point.
7 3 Bob
N2SCJ
Hi Bob,
if you are manually setting the rig's mode then I assume you have
"Settings->Radio->Mode->None" checked in WSJT-X. With
that setting WSJT-X should not be making any changes to the rig's
mode or filter settings. Please confirm that if that is not the
case.
73
Bill
G4WJS.
|
|
|
Bill Somerville
Hi Phil,
yes the log is buffered in memory for
efficiency reasons. You can override that but that itself involves
a small performance penalty that we would not recommend for normal
day to day operation.
73
Bill
G4WJS.
On 14/09/2021 07:04, Philip Rose via
groups.io wrote:
toggle quoted message
Show quoted text
It only appears after I close WSJT-X. It
looks like a buffering issue.
Phil.
Sent from Mail for Windows
Bill,
I was looking on my laptop I use for my
logger development. It maybe different on my shack desktop.
Sorry.
73 Phil GM3ZZA
Sent from Mail for Windows
it should be there, a line looking
something like this:
[RIGCTRL][2021-05-22 16:27:31.757882][00:00:00.773225][info] Hamlib version: Hamlib 4.2 Mon May 17 02:40:24 2021 +0000 SHA=cdad07
appearing a few lines after a line
looking something like this one:
[SYSLOG][2021-05-22 16:27:30.991620][00:00:00.007251][info] WSJT-X v2.4.0 c19d62 by K1JT, G4WJS, K9AN, and IV3NWV - Program startup
On 13/09/2021 19:41, Philip Rose via
groups.io wrote:
Hi
Bill, I didn’t see it with 2.4.0
Phil
Sent
from Mail for Windows
On
13/09/2021 16:00, Philip Rose via groups.io wrote:
>
Would it be possible to include the version of hamlib
built in displayed in the About WSJT-X window, please.
>
>
-- 73 Phil GM3ZZA
Hi
Phil,
that
information is available in the wsjtx_syslog.log file in
the WSJT-X
log
files directory ("Menu->File->Open log directory").
Scroll to near
the
end to see the application startup log messages which
include the
Hamlib
version being used.
73
Bill
G4WJS.
--
73 Phil GM3ZZA
--
73 Phil GM3ZZA
--
73 Phil GM3ZZA
|
|
|
Locked
Re: WSJT-x 2.5.0-rc6 in FST4W mode I can only select 2M band and above
#WSPR
#FST4W
Running in FST4W mode on Mac OSX High Sierra 10.13.6 I am only offered 2M and above in the pulldown list
If I switch to WSPR, all bands are listed.
This was a clean install on a Mac on which (I think) I never had previously installed WSJT-x
FST4W decoding works fine, but I can't upload 2200M spots as coming on 2M ;=) Hi Rob, Have you already tried to reset frequencies? Go to File – Settings – Frequencies and click on the list to get a menu and select Reset.
If you have some special frequencies added, you may first use Save as .. to keep the current version of your frequencies for later recovering. 73, Reino OH3mA
|
|
|
