I've been running rig split mode for a LONG time. Works fine in Fake It right
now.
The only thing that changed was updating g4wjs-hamlib and WSJT-X. I typically
update at least once a week if not more often thought it's been a week or two
since I updated hamlib.
The popup says "Hamlib error: Invalid parameter while getting current VFO
frequency".
So it's referring to the request for VFO_RIG_SUB which is not implemented and
never has been and really shouldn’t' be requested since VFO_A & B are
defined….just not in vfo_list.
wsjtx-rigctl caps says:
VFO list: VFOA VFOB
So that looks correct.
I added a couple of debug statements and indeed rig_->state.vfo_list appears to
be empty in WSTX now so that's why it's trying to set VFO_RIG_SUB.
I'm going to investigate some more to see why it's being filled/emptied or
whatever.
Mike W9MDB
From: Bill Somerville [mailto:[email protected]]
Sent: Thursday, April 23, 2015 7:51 AM
To: [email protected]
Subject: Re: [wsjt-devel] WSJT-X v1.5-rc1 (Release Candidate 1) PTT problem
On 23/04/2015 05:32, Michael Black wrote:
Hi Mike,
I'll add to the PTT complaints but for a different reason. Running the latest
g4wjs-hamlib and R5272
I have a TenTec OMNI VII.
PTT via CAT
Passes "Test" but won't stay keyed for transmit for more than 1 second and gets
a rig error.
Nothing showed up in release version in the trace log (no file at all…I thought
errors were supposed to show up there now?)
I think you are referring to Hamlib errors there, they will show up but the
failure is not a Hamlib error as such - it is a failure return from a Hamlib
function. The error_check() function below traps them and causes WSJT-X to pop
up an error message box. In that case the "Show details..." button explains
what went wrong.
So I compiled in trace debug which is attached.
Burps on this request:
// we can only probe current VFO unless rig supports reading
// the other one directly because we can't glitch the Rx
#if WSJT_TRACE_CAT && WSJT_TRACE_CAT_POLLS
qDebug () << "HamlibTransceiver::poll rig_get_freq other VFO";
#endif
error_check (rig_get_freq (rig_.data ()
, reversed_
? (rig_->state.vfo_list & RIG_VFO_A ?
RIG_VFO_A : RIG_VFO_MAIN)
: (rig_->state.vfo_list & RIG_VFO_B ?
RIG_VFO_B : RIG_VFO_SUB)
, &f), tr ("getting current VFO
frequency"));
Seems it's trying to read RIG_VFO_SUB now which it's never done before.
Looks like it wants the backend to have this:
rig->state.vfo_list=RIG_VFO_A | RIG_VFO_B;
But that setting of vfio_list is hardly in any backends that I can find so that
doesn't seem like a good solution.
Hmmm, that code hasn't changed recently. OTOH that looks like the rig polling
code, specifically the poll that gets done if the rig/WSJT-X are in split mode
- maybe split mode hasn't been tried before on that rig?
As for the Hamlib vfo_list variable, that is pretty fundamental, if that's not
set up then all sorts of problems will happen. But I am sure it is set as the
front end gathers the VFOs from the rig backend frequency ranges - see
src/rig.c line 379 for how that happens.
What is the error message detail from the pop up message box?
Mike W9MDB
73
Bill
G4WJS.
From: Bill Somerville [mailto:[email protected]]
Sent: Wednesday, April 22, 2015 8:42 PM
To: [email protected]
Subject: Re: [wsjt-devel] WSJT-X v1.5-rc1 (Release Candidate 1) PTT problem
On 23/04/2015 00:47, Allan Downie wrote:
Hi Allan & All
Yes to both questions Bill. Win 7 and usual USB 4 port. I have just heard from
a friend VK4ZB, he has the same issue. He is using Win 7 also.
OK, I have tracked down the main issue with this PTT problem. You can work
around it for now by changing the CAT serial port to something other than the
PTT serial port.
Change the "Rig" temporarily to something that enables the CAT serial port
field then change the CAT serial port field, blank is a good choice, then
change "Rig" back to "None". That should get the PTT signal going again until I
sort it out properly.
Allan
73
Bill
G4WJS.
_____
From: Bill Somerville <mailto:[email protected]>
Sent: 23/04/2015 9:16
To: [email protected]
Subject: Re: [wsjt-devel] WSJT-X v1.5-rc1 (Release Candidate 1) PTT problem
On 23/04/2015 00:06, Allan Downie wrote:
> Hi Gents,
Hi Allan,
>
> I appear to have a problem with this latest version regarding the PTT. I
> don't have any!
>
> I am not using CAT control. The transceiver uses a hard-wired PTT from
> the RTS pins to a real com port i.e. no USB adapters
> My PTT settings have worked on all previous versions (1.4, 1.5 and 1.6)
>
> I have un-installed the programme and reinstalled it resulting in no change.
>
> I notice Larry W7IUV on the WSJT users group has the same issue.
Interesting! It is beginning to look like a change to resolve an issue
on Linux systems make have caused a regerssion on Windows :(
Can you confirm that you are using MS Windows and you have selected the
correct serial port for PTT in the "Settings->Radio" page? I ask the
last because there is a minor fault in v1.5.0-rc1 such that it doesn't
report not being able to open the PTT serial port.
>
> Allan
> VK4QG
73
Bill
G4WJS.
>
>
>
> On 23/04/2015 2:05 AM, Joe Taylor wrote:
>> Dear development Colleagues,
>>
>> FYI, the message copied below has been sent to the "wsjtgroup" reflector.
>> -- Joe, K1JT
>>
>> ############################################################################
>> -------- Original Message --------
>> Subject: [wsjtgroup] WSJT-X v1.5-rc1 (Release Candidate 1)
>> Date: Wed, 22 Apr 2015 12:03:48 -0400
>> From: Joe [email protected] [wsjtgroup]
>> <mailto:[email protected]>
>> <[email protected]>
>> Reply-To: Joe Taylor <mailto:[email protected]> <[email protected]>
>> To: WSJT Group <mailto:[email protected]> <[email protected]>
>>
>> The WSJT Development Group is pleased to announce the availability of
>> Release Candidate 1 for WSJT-X Version 1.5. Installation packages for
>> Windows, Linux, and OS X can be downloaded from the WSJT web site:
>> http://physics.princeton.edu/pulsar/K1JT/wsjtx.html
>>
>> Version 1.5 offers many advantages including faster and better decoding
>> performance, more convenient handling of messages with compound
>> callsigns, and further improvements in rig control. For details see the
>> v1.5 Release Notice:
>> http://physics.princeton.edu/pulsar/K1JT/Release_Notice_v1.5.txt
>> and the full programmer's log of changes since v1.4:
>> http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.5.0.log
>> Upgrading from any v1.4 installation will be seamless; there is no need
>> to uninstall a previous version or move any files.
>>
>>
>> For those interested in the very latest advances: Version 1.6 is
>> progressing nicely. It will be the first WSJT-X version to support
>> VHF-UHF-Microwave-oriented modes from WSJT, including JT4, JT65B, and
>> JT65C.
>>
>> -- 73 from Joe, K1JT, for the WSJT Development Group
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
