Hi Folks,
The FT-991 now works with WSJTX 2.2.0 with Mike and Nate's latest patches. I
have not fully tested split modes etc. yet though !
I have also a background report, based off my compile, that FT-891 now works.
Some will not directly post here.
Perhaps current packaged releases should be
On 4/06/2020 8:18 am, Bill Somerville wrote:
I think I know what is happening here. Can you confirm that is
behaviour only happen when there is a single decode per period?
73
Bill
G4WJS.
Bill,
I am also observing it with multiple decodes per period. From my live
system...
de Laurie
On 03/06/2020 22:57, Laurie, VK3AMA wrote:
On 2/06/2020 9:17 am, Bill Somerville wrote:
On 01/06/2020 23:36, Laurie, VK3AMA wrote:
Tracked down the JTAlert non-coloring of decodes in the release
candidates.
2.1.2 works correctly, but the -rcs don't (tested both rc2 & rc3)
when the decode strin
On 2/06/2020 9:17 am, Bill Somerville wrote:
On 01/06/2020 23:36, Laurie, VK3AMA wrote:
Tracked down the JTAlert non-coloring of decodes in the release
candidates.
2.1.2 works correctly, but the -rcs don't (tested both rc2 & rc3)
when the decode string contains a positive report. Reports that
On 03/06/2020 18:50, Saku wrote:
Bill Somerville kirjoitti 3.6.2020 klo 14.38:
Please repeat the tests that failed using `rigctld-wsjtx` and report
if they still fail please?
73 Bill G4WJS.
Hi Bill !
Thanks for information.
7876136 3.6. 13:12 /usr/local/bin/rigctld-wsjtx (works) (from
w
Version date has been added to all the utilities in the latest commits.
Mike W9MDB
On Wednesday, June 3, 2020, 12:55:36 PM CDT, Saku wrote:
Bill Somerville kirjoitti 3.6.2020 klo 14.38:
>
> Please repeat the tests that failed using `rigctld-wsjtx` and report
> if they still fail plea
Bill Somerville kirjoitti 3.6.2020 klo 14.38:
Please repeat the tests that failed using `rigctld-wsjtx` and report
if they still fail please?
73 Bill G4WJS.
Hi Bill !
Thanks for information.
7876136 3.6. 13:12 /usr/local/bin/rigctld-wsjtx (works) (from
wsjtx-2.2.0-GA.tgz)
130672 4.4. 1
Hello,
Best way of describing this problem is this:
1) If I kick off WSJT program, the 7300 will turn ON within a couple FT8 cycles.
2) Interestingly, If WSJT was in JT9 mode, the 7300 won't turn ON but the
normal "Rig Control Error" box appears.
3) I haven't investigated any other modes for th
I just pushed a commit that has a new dummy device without set_vfo or get_vfo.
I was able to patch it to work with this situation so this should apply to any
older Icom rigs and Yaesu rigs that don't have set_vfo capability and/or
get_vfo capability.
I'm still waiting for my tester to get a curre
Hi Bill,
Thanks for your prompt reply.
I understand WSJT-X to start with a command line option of
'--language=en'. Unfortunately, user who read a 'Release Note.txt' is
not so much in Japan, I guess. But, Ooba-san will disclose his translated
one to Japanese later and many Japanese people will
On 3 Jun 2020 at 14:02, Bill Somerville wrote:
> Hi Martin,
>
> the ADIF specification treats any characters outside of the specified
> ADIF tags and data as commentary, i.e. it is ignored. I recommend that
> you use an ADIF export from your logging program to replace your damaged
> wsjtx_log.
On 03/06/2020 13:54, Martin Davies G0HDB wrote:
I have a brief query about the format of the ADIF records in the wsjtx_log.adi
file that's
created and updated by WSJT-X.
I appear to have lost the first 1,000 or so entries in my wsjtx_log.adi file; I
occasionally open
the file using the ADIFMas
I have a brief query about the format of the ADIF records in the wsjtx_log.adi
file that's
created and updated by WSJT-X.
I appear to have lost the first 1,000 or so entries in my wsjtx_log.adi file; I
occasionally open
the file using the ADIFMaster utility app and I suspect that sometime in t
On 2 Jun 2020 at 9:53, Joe Taylor wrote:
> The WSJT Development Group is pleased to announce the general
> availability (GA) release of WSJT-X Version 2.2.0. A brief summary of
> new features is provided here; for further details see the Release Notes:
>
> http://physics.princeton.edu/pulsar/k
Hi Mike,
thanks for chasing this down. I have some confusion whether there are
two issues, one with direct rig control and another when using rigctld.
I would be good to test both, let me know if a test version of WSJT-X is
needed with your patch for any platform required? Although in this cas
I've got a patched version that I sent to one of the testers
On Wednesday, June 3, 2020, 06:26:20 AM CDT, Bill Somerville
wrote:
Mike,
I believe it is quite reasonable to implement rig_get_vfo for the FT-891,
FT991, and similar. In this case it may be that a implementation
On 03/06/2020 08:46, Saku wrote:
Joe Taylor kirjoitti 2.6.2020 klo 16.53:
The WSJT Development Group is pleased to announce the general
availability (GA) release of WSJT-X Version 2.2.0. A brief summary
of new features is provided here; for further details see the Release
Notes:
HI!
Is thi
On 03/06/2020 12:27, Saku wrote:
Saku kirjoitti 30.5.2020 klo 6.06:
Hi!
Just jumped from rc1(snap) to rc3. (self compiled source from K1JT
homepage)
Sad to see that the same hamlib error still exist there in rc3 too!!
"Hamlib error: Feature not available while getting current VFO"
Fedora
On Wed, Jun 3, 2020 at 2:51 AM Saku wrote:
> Joe Taylor kirjoitti 2.6.2020 klo 16.53:
>
> The WSJT Development Group is pleased to announce the general availability
> (GA) release of WSJT-X Version 2.2.0. A brief summary of new features is
> provided here; for further details see the Release Not
On 03/06/2020 11:33, nick wrote:
Linux Mint 19.3 x86_64, Qt5.13.0.
Built hamlib-4.0-git and wsjtx-2.2.0 from tarball.
Did not need ./bootstrap for hamlib build.
Worked first time.
73
Nick
Hi Nick,
that's correct. The bundled Hamlib tarball now uses the Hamlib `make
dist` target to produc
Saku kirjoitti 30.5.2020 klo 6.06:
Hi!
Just jumped from rc1(snap) to rc3. (self compiled source from K1JT
homepage)
Sad to see that the same hamlib error still exist there in rc3 too!!
"Hamlib error: Feature not available while getting current VFO"
Fedora 31, icom 7300, rigctld started by
On 03/06/2020 08:51, Yukio JG1APX wrote:
[Resending with the correction]
Hello develop team,
I am using the GA release with Japanese language. I found that there
is no depict of spectrum in the display at the widegraph once the
display method is changed from "Current" to another. To resume t
Mike,
I believe it is quite reasonable to implement rig_get_vfo for the
FT-891, FT991, and similar. In this case it may be that a implementation
that always returns VFO A is correct as I don't believe these rigs use
VFO B for anything other than SPLIT Tx transmit frequency. That aside,
what i
Linux Mint 19.3 x86_64, Qt5.13.0.
Built hamlib-4.0-git and wsjtx-2.2.0 from tarball.
Did not need ./bootstrap for hamlib build.
Worked first time.
73
Nick
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/li
[Resending with the correction]
Hello develop team,
I am using the GA release with Japanese language. I found that there
is no depict of spectrum in the display at the widegraph once the
display method is changed from "Current" to another. To resume the
function, the display method was changed
Joe Taylor kirjoitti 2.6.2020 klo 16.53:
The WSJT Development Group is pleased to announce the general
availability (GA) release of WSJT-X Version 2.2.0. A brief summary of
new features is provided here; for further details see the Release Notes:
HI!
Is this really what it shows?:
Fedora 29
26 matches
Mail list logo
