Re: [wsjt-devel] Not sure if an issue

[jarmo via wsjt-devel]

Wed, 14 Feb 2024 09:44:17 +1100
Alan McDonald via wsjt-devel 
kirjoitti:

> It happens to me frequently. I leave the app running all the time
> (not using it but it sits there).
> 
> Switching CODECs works all the time but curiously I never have to do
> this for MSHV or JTDX. They keep the CODEC.
> 
> What happens is the sound comes out of my radio speaker until I
> switch it back to USB again.
> 
>  
> 
> Alan / VK1AO

Not seen this kind behaviour. Have pretty much wsjtx running 24/7
some years now.
OS Fedora 39 (now)
Just now testing 2.7.1-devel 
Older genetation i7 desktop...

Is this happening with WIN?

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc2

[jarmo via wsjt-devel]

Sat, 8 Jul 2023 15:16:44 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> I guess you must be compiling the latest hamlib from github.
> 
> Please pull the latest and try again.  It  should be fixed.
> 
> Mike W9MDB

Pulled and nope...

Hamlib error: write_block(): TX 9 bytes, method=2
5c 63 68 6b 5f 76 66 6f 0a  \chk_vfo.   
read_string_generic called, rxmax=1024 direct=1, expected_len=1
read_string_generic(): read failed, direct=1 - Connection reset by peer
IO error

netrigctl_open: vfo_mode=0
netrigctl_transaction: called len=12
rig_flush: called for network device
network_flush called
write_block():1076 failed -1 - Broken pipe
  2:netrigctl.c(295):netrigctl_open returning(-6) IO error

  2:rig.c(7555):async_data_handler_stop entered
  2:rig.c(7585):async_data_handler_stop returning(0) 
network_close: close socket ret=0
 1:rig.c(1315):rig_open returning(-6) IO error

IO error
IO error
 while opening connection to rig

Timestamp: 2023-07-09T03:03:10.132Z

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc2

[jarmo via wsjt-devel]

Sat, 8 Jul 2023 15:54:36 +0100
Brian Morrison via wsjt-devel 
kirjoitti:

> On Sat, 8 Jul 2023 16:34:23 +0300
> jarmo via wsjt-devel  wrote:
> 
> > Sri, linux Fedora 38 in use, think DLL's does not
> > suit for it :)  
> 
> Which hamlib rpm do you have installed?
> 

Not rpm, compiled from git

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc2

[jarmo via wsjt-devel]

Sat, 8 Jul 2023 13:08:49 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

Sri, linux Fedora 38 in use, think DLL's does not
suit for it :)

Jarmo

> Try this 64-bit DLL
> 
> https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
> 
> Mike W9MDB
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Saturday, July 8, 2023 at 01:39:11 AM CDT, jarmo via wsjt-devel
>  wrote: 
> 
> 
> 
> 
> 
> Fri, 7 Jul 2023 11:50:06 -0400
> Joe Taylor via wsjt-devel 
> kirjoitti:
> 
> > Dear WSJT-X Users,
> > 
> > We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc2
> > is ready for download by beta testers.  
> 
> Hamlib no worky anymore with TS-890S
> 
> Hamlib error: 
> netrigctl_open: vfo_mode=0
> netrigctl_transaction: called len=12
> network_flush called
> write_block(): TX 12 bytes, method=2
>     5c 64 75 6d 70 5f 73 74 61 74 65 0a
> \dump_state. read_string_generic called, rxmax=1024 direct=1,
> expected_len=1 read_string_generic(1350): retrying read timeout 1/1
> timeout=1 read_string_generic(): Timed out 0.014 seconds after 0
> chars, direct=1 2:netrigctl.c(295):netrigctl_open returning(-5)
> Communication timed out
> 
> 2:rig.c(7811):async_data_handler_stop entered
> 2:rig.c(7844):async_data_handler_stop returning(0) 
> 2:rig.c(7852):morse_data_handler_stop entered
> 2:rig.c(7882):morse_data_handler_stop returning(0) 
> network_close: close socket ret=0
> rig.c(1378):rig_open returning2(-5) Communication timed out
> 
> Communication timed out
> Communication timed out
> while opening connection to rig
> 
> Timestamp: 2023-07-08T06:26:28.196Z
> 
> Jarmo, oh1mrr
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc2

[jarmo via wsjt-devel]

Fri, 7 Jul 2023 11:50:06 -0400
Joe Taylor via wsjt-devel  kirjoitti:

> Dear WSJT-X Users,
> 
> We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc2 is 
> ready for download by beta testers.

Hamlib no worky anymore with TS-890S

Hamlib error: 
netrigctl_open: vfo_mode=0
netrigctl_transaction: called len=12
network_flush called
write_block(): TX 12 bytes, method=2
5c 64 75 6d 70 5f 73 74 61 74 65 0a \dump_state.
read_string_generic called, rxmax=1024 direct=1, expected_len=1
read_string_generic(1350): retrying read timeout 1/1 timeout=1
read_string_generic(): Timed out 0.014 seconds after 0 chars, direct=1
 2:netrigctl.c(295):netrigctl_open returning(-5) Communication timed out

 2:rig.c(7811):async_data_handler_stop entered
 2:rig.c(7844):async_data_handler_stop returning(0) 
 2:rig.c(7852):morse_data_handler_stop entered
 2:rig.c(7882):morse_data_handler_stop returning(0) 
network_close: close socket ret=0
rig.c(1378):rig_open returning2(-5) Communication timed out

Communication timed out
Communication timed out
 while opening connection to rig

Timestamp: 2023-07-08T06:26:28.196Z

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OFF-TOPIC: MTA error for Domain NIC.FI

[jarmo via wsjt-devel]

Thu, 6 Jul 2023 10:08:10 -0300
Marco Calistri via wsjt-devel 
kirjoitti:

> Hello,
> 
> My apologies for this off-topic but I would like to send an e-mail to 
> Saku OH1KH and I get an MTA error reporting a failure (see below).
> 
> Are there here some OH hams which have a secondary e-mail address of
> Saku?
> 
> Many thanks and again sorry for my request on this list!
> 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>sakari.nyl...@nic.fi
>  (generated fromoh...@sral.fi)
>  all hosts for 'nic.fi' have been failing for a long time (and
> retry time not reached)
> 
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **

I'm using nic.fi also, so testing..

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Version 2.7.0-rc1

[jarmo via wsjt-devel]

Have had running now for a while, despite operator errors
seems good, BUT :),
When I choose CQ: NONE, there is no effect, still first/strongest
stn fires up qso...

Fedora 38, rigctl Hamlib 4.6~git touko 13 15:49:08Z 2023 SHA=99baa8
64-bit, Kenwood TS-890S.

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Compile fails

[jarmo via wsjt-devel]

Did git pull for wsjtx, tried to compile, failed...

/home/oh1mrr/wsjtx/qmap/libqmap/q65c.f90:23:39:

   23 |ndepth,ndiskdat,neme,newdat,nfa,nfb,nfcal,nfshift,   
  &
  |   1
Virhe: Symbol ”nfa” at (1) is USE associated from module ”q65” and cannot occur 
in COMMON
gmake[2]: *** [qmap/libqmap/CMakeFiles/qmap_impl.dir/build.make:336: 
qmap/libqmap/CMakeFiles/qmap_impl.dir/q65c.f90.o] Error 1
gmake[2]: *** Odotetaan keskeneräisiä töitä
gmake[1]: *** [CMakeFiles/Makefile2:2109: 
qmap/libqmap/CMakeFiles/qmap_impl.dir/all] Error 2
gmake[1]: *** Odotetaan keskeneräisiä töitä
[ 79%] Linking CXX static library libqcp.a
[ 79%] Built target qcp
gmake: *** [Makefile:156: all] Error 2

Just for info.

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Compiling new hamlib

[jarmo via wsjt-devel]

Sat, 13 May 2023 12:42:20 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:
Hi Mike &

No, I did git pull on to existing hamlib. Renamed it and With clean
git clone, everything went ok. Compiled and is running.

Now BUT...
 When I take wsjtx, git clone etc... Seems to go ok, compilation
and install. Start wsjtx, I see version 2.6.1 still? And what
worse, it does not find my Hamlib net rigctld, my logprog, CqrLog
works ok with new hamlib.

No panic... sure find solution..

jarmo, oh1mrr
> Do you have an old libhamlib sitting around?  Did you uninstall the
> hamlib package?
> 
> Mike W9MDB
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Saturday, May 13, 2023 at 04:35:41 AM CDT, jarmo via wsjt-devel
>  wrote: 
> 
> 
> 
> 
> 
> Just started trying compile hamlib in Fedora 38.
> Got error
> make[1]: Siirrytään hakemistoon ”/home/oh1mrr/Hamlib/c++”
>   CXXLD    libhamlib++.la
> /usr/bin/ld: cannot find
> /usr/lib/gcc/x86_64-redhat-linux/12/../../../../lib64/crti.o: No such
> file or directory /usr/bin/ld: cannot find
> /usr/lib/gcc/x86_64-redhat-linux/12/crtbeginS.o: No such file or
> directory collect2: error: ld returned 1 exit status
> 
> But, find /usr/ -name crti*
> /usr/lib64/crti.o
> 
> find /usr/ -name crtbeginS*
> /usr/lib/gcc/x86_64-redhat-linux/13/crtbeginS.o
> /usr/lib/gcc/x86_64-redhat-linux/13/32/crtbeginS.o
> 
> As known, I don't "speak nerd" well :), if I could get
> easy way out?
> I see that ld is looking first hand /12/, but F38 has /13/.
> 
> Any solution???
> 
> Jarmo, oh1mrr
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Compiling new hamlib

[jarmo via wsjt-devel]

Just started trying compile hamlib in Fedora 38.
Got error
make[1]: Siirrytään hakemistoon ”/home/oh1mrr/Hamlib/c++”
  CXXLDlibhamlib++.la
/usr/bin/ld: cannot find 
/usr/lib/gcc/x86_64-redhat-linux/12/../../../../lib64/crti.o: No such file or 
directory
/usr/bin/ld: cannot find /usr/lib/gcc/x86_64-redhat-linux/12/crtbeginS.o: No 
such file or directory
collect2: error: ld returned 1 exit status

But, find /usr/ -name crti*
/usr/lib64/crti.o

find /usr/ -name crtbeginS*
/usr/lib/gcc/x86_64-redhat-linux/13/crtbeginS.o
/usr/lib/gcc/x86_64-redhat-linux/13/32/crtbeginS.o

As known, I don't "speak nerd" well :), if I could get
easy way out?
I see that ld is looking first hand /12/, but F38 has /13/.

Any solution???

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] F/H mode in wrong period

[jarmo via wsjt-devel]

Mon, 10 Apr 2023 18:58:47 +0200
5p1kzx Michael via wsjt-devel 
kirjoitti:

> Hi Jarmo
> 
> JTDX can't run any kind of Robot-Mode...
> 
> 73 de 5p1kzx Michael

I stand corrected, thanks

Jarmo, Oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] F/H mode in wrong period

[jarmo via wsjt-devel]

Mon, 10 Apr 2023 21:03:42 +1000
Alan McDonald via wsjt-devel 
kirjoitti:

> All correct. I've just emailed T30UN on this very subject. Their QRZ
> page is completely misleading - what they are saying is absolutely
> not possible. It's not F/H if they are on std freq. It's MSHV
> multi-stream. But they say they use WSJT-X. So this all leads to
> total confusion for all operators.

I think, they are using WSJTX-Z, which is clone for WSJT-x.
And that allows use also ROBOT and all kind of abnormalitys.
Also JTDX can do those...

Jarmo, OH1MRR


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 3Y0J strange F/H operation

[jarmo via wsjt-devel]

Wed, 15 Feb 2023 11:04:03 -0500
David Kjellquist via wsjt-devel 
kirjoitti:

> Unlike WSJT-X, JTDX software allows F on either odd or even

I gor answer from pilot Steve...

"Hi Jarmo,

Sorry I could not answer your email sooner. Too many emails and text
messages. They say they were using WSJT-X software. They had a sequence
problem with one of their laptops. It turned out to be a clock issue
which was not obvious to the operator. All settings appeared to be
correct but it was transmitting on the Odd rather than the Even."

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Strance thing

[jarmo via wsjt-devel]

Fri, 10 Feb 2023 04:02:31 -0600
Dave Bernheisel via wsjt-devel 
kirjoitti:

> Hello Jarmo,
> 
> I think I have found the source :
> 
> file>settings>advanced PACC is in the contest name box  
> 
> I removed the PACC from the box and restarted WSJT-X.  PACC was in
> the box after I restarted.
> 
> I also unchecked CQ with individual contest name.
> 
> Now the PACC is not included in the TX6 value
> 
> Windows 10  wsjt-x 2.6.1.
> 
> 73,
> 
> Dave, N2DPF

Dave

Confiming that. But just wonder, where it came there. I don't run
contests and have not set by accident anything there, just used
mainwindows "H" button???

Let's see

jarmo, OH1MRR


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Strance thing

[jarmo via wsjt-devel]

When I toggle into hound mode, same time comes
commented PACC contest mode ?
If I remove that, It stays still there. Means I have all the time
there CQ PACC OH1MRR KP01.
This comes when I toggle "H".???
Fedora 37, WSJTX 2.6.1 Compiled from GIT, Hamlib 4.6~git tammi 07
05:31:18Z 2023 SHA=eb9041.

Kind a bug?

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjtx 2.6.1

[jarmo via wsjt-devel]

Thu, 19 Jan 2023 12:43:28 -0600
Richard Shaw via wsjt-devel 
kirjoitti:


> Yes, and had a few other things I've been working on. I maintain
> about 150 packages between Fedora and RPM Fusion :)
> 
> Thanks,
> Richard
> KF5OIM

No worry, we have time to wait, as said compiled
and working with 2.6.1...

73, Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] wsjtx 2.6.1

[jarmo via wsjt-devel]

So far working here... Compiled from GIT.
Anyone seen Fedora 37 rpm yet?

jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Wsjtx 2.6.0-rc4 Fedora 37

[jarmo via wsjt-devel]

Just for info. Compiled v 2.6.0-rc4 into F37.
All seems to work fine. BUT, I only use FT4 and FT8
modes, so don't have experience others, promising.

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Fox Mode Indication to Hound Users on the Air

[jarmo via wsjt-devel]

Tue, 8 Nov 2022 02:29:50 -0800
Jim Brown via wsjt-devel  kirjoitti:

> On 11/8/2022 1:07 AM, Erik Icket via wsjt-devel wrote:
> > I observed that confusion as well last weekend when F/H was used on
> > the regular FT8 frequencies.  
> 
> Someone failed to study the F/H doc -- WSJT is programmed to NOT use
> F/H on standard FT8 frequencies. If it's on regular frequencies, it's
> NOT F/H. What you experienced might have been multi-stream, but NOT
> F/H.
> 
> 73, Jim K9YC

Anyway it acts like F/H on regular freq. As now example T33T and 5V7RU
uses regulars. T33T writes: https://dxnews.com/t33t/ so it's peditioners
BAD to do that. Ofcourse there are lot's of clones, what to use. Most
saddest is WSJTX-Z what allows robot mode, what seen used during
peditions.
But at the moment, several peditions, all on standart FT freq, meand
huge QRM :(

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

[jarmo via wsjt-devel]

Thu, 13 Oct 2022 19:29:48 +0200
Frode Igland via wsjt-devel 
kirjoitti:

Frode, I don't know what it means. I read that text hastly, so,
apologize.
I stop allways there, where is something mentioned "contest".
Not my thing... :)
We wait now time, when manual is written..

jarmo, oh1mrr

> Hi, Jarmo.
> Does that mean that "CQ: Max Dist" is setup to work *only* with the
> ARRL International Digital Contest?
> Neither the Release Notes nor the -rc4 User Guide say anything about
> "CQ: Max Dist", so it is  difficult to say. "CQ: Max Dist" looks like
> the FT8 version of the "Best S+P" functionality in FT4, which works
> also outside contests, although FT4 was developed primarily for
> contesting. Then I find it strange that similar functionality in the
> general usage FT8 mode should work only in contest, and even only in
> one contest of the year.
> 
> The ARRL International Digital Contest  ran on 4-5 June 2022, whilst
> the WSJT-X 2.6.0-rc1 introducing "CQ: Max Dist"  was published only
> on 20 June, i.e. shortly after this year's contest. If your
> information is correct,  I guess it will not be possible to test this
> functionality until next June. Then it is strange that it was
> introduced almost a year before it was needed or useful.
> 
> The hover-over help text reads "Max* Pts*", not "Max Dist", probably a
> small typo.
> 
> 73, Frode LA6VQ
> 
> tor. 13. okt. 2022 kl. 16:33 skrev jarmo via wsjt-devel <
> wsjt-devel@lists.sourceforge.net>:
> 
> > Thu, 13 Oct 2022 08:34:37 -0400
> > Dennis W1UE via wsjt-devel 
> > kirjoitti:
> >
> > Problem2 in not a problem, hover mouse over text, you can see, that
> > shoud wor with ARRL contest.
> >
> > jarmo, oh1mrr  
> > > I can also confirm problem #1.  It is the same problem that
> > > existed in version 2.6.0 RC1,2,3 and 4.
> > >
> > > Since I use WSJT in combination with N1MM+ for logging, I get a
> > > "TCP Error" when the program closes.
> > > If I'm not using the combo, WSJT just closes.  I have not noticed
> > > that the closing occurs when using
> > > only FT8; it may also occur when using FT4, but there isn't enough
> > > activity on FT4 to see if it happens.
> > >
> > > A couple of additional observations:
> > > 1. At the suggestion of K1JT, I replaced the Hamlib dll of
> > > 2.6.0rc4 with the same dll from 2.5.4.  The closing
> > > seemed to stop.  This only works if your rig is supported by the
> > > earlier dll.
> > > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation
> > > before it closes.  Once it starts closing, it will
> > > continually do it.
> > >
> > > I have not seen the issues with "CQ MAX DIST".  Are you sure it's
> > > not picking the correct call?
> > > 1. Calls without a grid are never selected unless they are the
> > > only reply to your CQ.
> > > 2. Band/Mode dupes are given a score of zero and only selected if
> > > the only caller.
> > > 3. Call selection is based on the point score generated by the
> > > program calculations; I know SP is further than
> > > DL, but if they have the same point total and the DL is before
> > > the SP in the decode window, the WSJT will
> > > select the DL station to call.
> > >
> > > Dennis W1UE
> > >
> > >
> > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel <
> > > wsjt-devel@lists.sourceforge.net> wrote:
> > >  
> > > > I can confirm problem 1, as it happened to me less than an hour
> > > > ago, including the orphaned JT9 decoding application.  Running
> > > > Win 10 on a Lenovo X1 Carbon laptop.  I had been on FT8 for
> > > > about an hour when it happened.
> > > >
> > > >
> > > >
> > > > Ed N4II.
> > > >
> > > >
> > > >
> > > > *From:* Frode Igland via wsjt-devel
> > > >  *Sent:* Thursday, October 13,
> > > > 2022 5:06 AM *To:* WSJT software development
> > > >  *Cc:* Frode Igland
> > > >  *Subject:* [wsjt-devel] WSJT-X
> > > > 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ:
> > > > None" stops working
> > > >
> > > >
> > > >
> > > > I have used -rc4 since it was released and have found it quite
> > > > stable with three notable exceptions:
> > > >
> > > >
> > > >
> &

Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

[jarmo via wsjt-devel]

Thu, 13 Oct 2022 08:34:37 -0400
Dennis W1UE via wsjt-devel  kirjoitti:

Problem2 in not a problem, hover mouse over text, you can see, that
shoud wor with ARRL contest.

jarmo, oh1mrr
> I can also confirm problem #1.  It is the same problem that existed in
> version 2.6.0 RC1,2,3 and 4.
> 
> Since I use WSJT in combination with N1MM+ for logging, I get a "TCP
> Error" when the program closes.
> If I'm not using the combo, WSJT just closes.  I have not noticed
> that the closing occurs when using
> only FT8; it may also occur when using FT4, but there isn't enough
> activity on FT4 to see if it happens.
> 
> A couple of additional observations:
> 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4
> with the same dll from 2.5.4.  The closing
> seemed to stop.  This only works if your rig is supported by the
> earlier dll.
> 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation
> before it closes.  Once it starts closing, it will
> continually do it.
> 
> I have not seen the issues with "CQ MAX DIST".  Are you sure it's not
> picking the correct call?
> 1. Calls without a grid are never selected unless they are the only
> reply to your CQ.
> 2. Band/Mode dupes are given a score of zero and only selected if the
> only caller.
> 3. Call selection is based on the point score generated by the program
> calculations; I know SP is further than
> DL, but if they have the same point total and the DL is before the SP
> in the decode window, the WSJT will
> select the DL station to call.
> 
> Dennis W1UE
> 
> 
> On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> 
> > I can confirm problem 1, as it happened to me less than an hour ago,
> > including the orphaned JT9 decoding application.  Running Win 10 on
> > a Lenovo X1 Carbon laptop.  I had been on FT8 for about an hour
> > when it happened.
> >
> >
> >
> > Ed N4II.
> >
> >
> >
> > *From:* Frode Igland via wsjt-devel
> >  *Sent:* Thursday, October 13,
> > 2022 5:06 AM *To:* WSJT software development
> >  *Cc:* Frode Igland
> >  *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4:
> > Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops
> > working
> >
> >
> >
> > I have used -rc4 since it was released and have found it quite
> > stable with three notable exceptions:
> >
> >
> >
> > *1. Sudden closing in FT8 after extended periods of operation*
> >
> > After an extended period of use in FT8 mode (normally more than two
> > hours), WSJT-X may close down abruptly. The closing happens at the
> > start of an FT8 sequence. I have never experienced closing on FT4,
> > but then I have very rarely worked FT4 for extended periods. To
> > start again, an orphaned JT9 decoding application first has to be
> > terminated in the Task Manager. This issue started with WSJT-X
> > 2.6.0-rc1 and still happens.
> >
> >
> >
> > *2. "CQ: Max Dist" doesn't work*
> >
> > After selecting "CQ: Max Dist", WSJT-X still selects the station
> > first decoded, notwithstanding the distance. It makes no difference
> > whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First"
> > or if "CQ: Max Dist" was selected on start-up before first CQ.
> >
> >
> >
> > *3. "CQ: None" stops working after a while*
> >
> > I often call CQ DX with the "CQ: None" setting, to be able to
> > select which DX station to work. This normally works well, but
> > suddenly WSJT-X may start answering the first station decoded
> > automatically, without being selected manually by me. Sometimes,
> > reselecting "CQ: None" helps, and sometimes I have to close and
> > reopen WSJT-X and select "CQ: None" before calling CQ.
> >
> >
> >
> > These are my experiences with WSJT-X 2.6.0-rc4.
> >
> >
> >
> > 73, Frode LA6VQ
> >
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >  



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Multiple 2.6.0-rc4 Hound bugs

[jarmo via wsjt-devel]

Mon, 12 Sep 2022 18:19:17 -0400
Richard V Zwirko via wsjt-devel 
kirjoitti:


> 
> This same problem had occurred the day before when I worked ZL7/K5WE
> on FT8 20 Meters. I wonder if anyone else has experienced these
> anomalies with 2.6.0-rc4?
> 
> 73,
> Rich - K1HTV

He was not using F/H, propably not WSJTX at all, maybe MSHV
or some other clone.
I worked him just like "normal" FT8.

This have been problem, DX does not much inform, what program
they are using and many RX stations does not know how to work.
Unfortunately...

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Wsjtx-2.6.0-rc3

[jarmo via wsjt-devel]

Seems, that Github is still on 2.6.0-rc2 version...
Compiled and claims to be RC2

jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjtx-2.6.0-rc2

[jarmo via wsjt-devel]

Sat, 23 Jul 2022 19:00:39 +0200
Claude Frantz via wsjt-devel 
kirjoitti:

> On 7/23/22 18:04, Marco Calistri via wsjt-devel wrote:
> 
> > I read a note by Saku here on this list regarding differences among
> > the source availables in Github and in the Website.  
> 
> The git repo at https://git.code.sf.net/p/wsjt/wsjtx seems to be
> still at rc1.

And I used that, that's why I asked, why my update
showed RC1.
Compiled from TGZ, now shows RC2..

jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] wsjtx-2.6.0-rc2

[jarmo via wsjt-devel]

Don't know, if anyone else have this, but compiled wsjtx
from wsjtx-2.6.0-rc2.tgz.
Still, when starting wsjtx I get wsjtx-2.6.0-rc1???
What I'm missing???

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X close the QSO unilaterally (?)

[jarmo via wsjt-devel]

Thu, 14 Jul 2022 23:02:32 -0300
Marco Calistri via wsjt-devel 
kirjoitti:

> Hello,


> This occurrence causes that WSJT-X logging the QSO then I go to hit
> "OK" and QSO is getting saved on my CQRLOG app.
> 
>  (I'm using Linux).

I'm using also, now question, why you hit OK, if qso is not complete?
I hit again opposite stations report to give again RR73, some cases
move couple Hz TX and hit again RR73. Normally I do this max 5 times and
then hit CANCEL. Can't log unfinished qso.
Normally this means, that someone qrm'ing so much, that opposite
station can't hear anymore me.
 
> But I would like to know if I could adjust something into WSJT-X
> settings, to avoid closing QSO's "unilaterally".

This could ba, as sending that RR73 so long yuo get /# or if not
you cancel qso..


Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing #Hamlib

[jarmo via wsjt-devel]

Thu, 7 Jul 2022 13:51:03 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> I need everyone to test the latest Hamlib please!!
> 
> All known rig bugs have been fixed.
> Testing in Rig Split and Fake It would be appreciated as well as
> rigctld testing. Successes/Failures please report.

With TS-890S and TS-590SG with rigctld, up as a service, fake it
works...  Split as "rig" not tested, no need, when this works :)

With FT-857, very quick test, rigctld no audio out... Radio chosen as
FT-857 PTT as "vox" not working. PTT as "rts" works also with "fake it"

OS, Fedora 36 wsjtx 2.5.4

As said this was very short test, and my time is now quite limited
to test...

Maybe someone test also FT-857

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 2.6.0-rc1

[jarmo via wsjt-devel]

Now few days running 24h (listening) mostly and seen nothing peculiar.
Only first time calling CQ, many stations called me, but autoseq didn't
pick any. Yes, then noticed, CQ NONE... Ok, this let you choose
station, but same thing can be done with autoseq unchecked...
So, "cq: first" and "cq: max dist" could be enough.
Actually liked very much that option "max dist" when called DX...
Didn't neet care EU callers, when called long distance... Very good..

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Fedora Core 36 - usb device rescan issue

[jarmo via wsjt-devel]

Mon, 27 Jun 2022 07:48:18 -0400
Josh Rovero via wsjt-devel  kirjoitti:

> This causes problems with WSJT-X 2.5.4 and 2.6.0-rc1 on Fedora Core
> 36, 64-bit.  The behavior was not present in Fedora Core 35.
> 
> It appears that the system rescans and renumbers/relabels USB devices
> once a day, resulting in hamlib losing control of an operating WSJT-X
> instance. When WSJT-X is restarted, the "new" device names are found,
> can be selected, and operation is normal until the next rescan.
> 

But, man can make UDEV rule, to set rigctld working, even ttyUSBx is
changed. One example... You make /etc/udev/rules.d
99-persistent-usb.rules file and inside something like

#ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="08bb",
ATTRS{idProduct}=="29b3", ATTRS{product}=="05670021A16A", SYMLINK+="rig"

Ofcource you have to look, when plug your radio to usb port, what
device you find there. I think lsusb -v as root, tells you "idVendor"
"idProduct" (product)

Then /usr/local/bin/rigctld -m "your_rig" -r /dev/rig -t 4532 -s baud &
And you choose in wsjtx RADIO as Hamlib Net rigctld, anyway works with
my F36 and wsjtx-2.6.0-rc1 so far... :)

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

[jarmo via wsjt-devel]

Thu, 2 Jun 2022 13:37:07 +0930
Peter Sumner via wsjt-devel 
kirjoitti:

> Hello Jarmo,
>  when 'rig' or 'fake-it' is enabled the transmit frequency is moved to
> improve the location of your TX tones. As a test, try changing your TX
> baseband freq to say 200 Hz and set TX on, note the TX VFO frequency,
> then move baseband TX to 2300Hz and repeat, I would bet that you will
> see the are different frequencies offset on the TX vfo.   For me I
> only use fake-it where the main VFO gets moved when I go to TX and it
> then comes back when I receive, it's all done to fight audio
> harmonics in the TX chain and defeat those masty images across our
> waterfall of people who unwittingly overdrive things.
> 
> Regards,
> Peter, vk5pj

Hi Peter

Yes I understand that, because I have always used "fakeit". I don't
want to mix my system, which is, VFO-A CW/SSB, VFO-B DIGI...
As an age of 70, does not want complicated systems :)

Jarmo, oh1mrr 


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

[jarmo via wsjt-devel]

Wed, 1 Jun 2022 16:13:42 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

Tested, but don't  understand behaviour? Why freq goes -500 Hz when
tx'ing and stays there. I.E. I set 21074, both vfo, when first TX, lets
say vfo-b goes 21073500 and stays there. Where is this "delta" defined?
Ok, I don't use "rig split", because I have other vfo in use cw/ssb,
easy to change, when ever needed. And I don't use memories either...
Only simple things for simple person :)

Jarmo, oh1mrr
> Could you please test the 890S in Rig Split?
> I have a report that the TS590SG works in Rig Split OK.
> Mike W9MDB
> 
>  
> 
> On Wednesday, June 1, 2022, 10:57:51 AM CDT, jarmo via wsjt-devel
>  wrote: 
>  Wed, 1 Jun 2022 08:05:06 -0700
> Jim Preston via wsjt-devel 
> kirjoitti:
> 
> > On 5/31/2022 9:04 AM, Black Michael via wsjt-devel wrote:  
> > > I need everyone to test the latest Hamlib
> > > Testing in Rig Split and Fake It would be appreciated.
> > > Successes/Failures please report.  
> 
> Works ok with TS-590SG and TS-890S. Tested only "fake it". Fedora 36
> 
> Jarmo, oh1mrr
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>   



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

[jarmo via wsjt-devel]

Wed, 1 Jun 2022 08:05:06 -0700
Jim Preston via wsjt-devel  kirjoitti:

> On 5/31/2022 9:04 AM, Black Michael via wsjt-devel wrote:
> > I need everyone to test the latest Hamlib
> > Testing in Rig Split and Fake It would be appreciated.
> > Successes/Failures please report.

Works ok with TS-590SG and TS-890S. Tested only "fake it". Fedora 36

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem with flrig/wsjtx on Ubuntu

[jarmo via wsjt-devel]

Sat, 5 Mar 2022 16:45:28 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> There was a problem with muting that should be fixed in the latest
> hamlib.But I'm not sure this is related to what you're describing
> with rigctld.
> 
> Mike W9MDB

Hi Mike

I compiled latest hamlib and no better.
It can be tested by choosing wsjtx setting first radio as TS590SG or
FT857, default settings, everything works OK, audio out, TX goes
ok.
BUT change radio into Hamlib Net rigctl, start rigctld first with
"script" or manually, then try TX, audio out is muted.
I have not found reason, but as said earlier, this started when took
version 2.5.x of wsjtx in use.
I'm not sure, if Fedora has this fault. Is it change from
ALSA-PULSEAUDIO into ALSA-PIPEWIRE audio system... Hard to test
with my skills...

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem with flrig/wsjtx on Ubuntu

[jarmo via wsjt-devel]

Sat, 5 Mar 2022 08:42:15 +0200
jarmo via wsjt-devel  kirjoitti:


> 
> Not using flrig, but have had this issue with TS-590SG and FT-859D.

Sorry typo NOT FT- 859D, its FT-857D

jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem with flrig/wsjtx on Ubuntu

[jarmo via wsjt-devel]

Fri, 4 Mar 2022 18:22:10 +0100
Juergen Christlieb via wsjt-devel 
kirjoitti:

> After everything worked fine for months, I suddenly no longer get any 
> control on the trx (possibly after an Ubuntu update?). Have meanwhile 
> flrig 1.3.49 and wsjtx 2.5.4 newly installed and of course tried all 
> possible settings. Recording and PTT works perfectly, but the signal 
> from the PC is not transmitted to the trx.
> 
> Who can help?
> 
> Many thanks in advance - Chris

Not using flrig, but have had this issue with TS-590SG and FT-859D.
All started when version 2.5.x came. Os is Fedora 35. I can get
signal out just using RIG as TS-590SG and FT-859, but If I choose RIG as
Hamlib Net rigctl, Signal is muted.
I don't know if it has something to do ALSA/PIPEWIRE, but something
dramatic happened, when 2.5.x version came..

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fw: TS-590SG

[jarmo via wsjt-devel]

Edelleenlähetetty viesti:

Päiväys: Sat, 12 Feb 2022 10:37:52 +0200
Lähettäjä: jarmo 
Vastaanottaja: wsjt-devel@lists.sourceforge.net
Aihe: TS-590SG


Latest Hamlib update from Git.. rigctl Hamlib 4.5~git pe helmi 11
23:46:32 2022 + SHA=ea7eff TS-590Sg stopped working with WSJTX
2.5.4 Hope my picture shows some info. It is sgreenshot taken from
Anydesk, so might not include all info..
Hamlib error: Protocol error
rig_get_vfo: returning -8(Protocol error
 -9:kenwood.c(1051):kenwood_get_if return(-8)

Kind a found and got someway working. Hamlib error was caused, because
of CQRLOG also connecting.
Now, I have CQRLOG set using 2 Hamlib NET rigctl and WSJTX using
TS-590SG.
If I set in WSJTX RIG as HAMLIB NET Rigctl, output audio is MUTED, but
when radio is TS-590SG all is OK.. This "audio syndrome" came with wsjtx
2.5.x version.
Ok, we can live with this configuration...

Hopefully helping others struggling with TS590SG/CQRLOG/WSJTX

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] TS-590SG

[jarmo via wsjt-devel]

Latest Hamlib update from Git.. rigctl Hamlib 4.5~git pe helmi 11 23:46:32 2022 
+ SHA=ea7eff
TS-590Sg stopped working with WSJTX 2.5.4 Hope my picture shows some
info. It is sgreenshot taken from Anydesk, so might not include all
info..
Hamlib error: Protocol error
rig_get_vfo: returning -8(Protocol error
 -9:kenwood.c(1051):kenwood_get_if return(-8) Protocol error
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(635):kenwood_safe_transaction return(-8) Protocol 
error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(635):kenwood_safe_transaction return(-8) Protocol 
error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, rs->rigport.retry=10 
-10:kenwood.c(1673):kenwood_get_vfo_if return(-8) Protocol error
kenwood.c(635):kenwood_safe_transaction return(-8) Protocol error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, rs->rigport.retry=10 
-9:kenwood.c(1051):kenwood_get_if return(-8) Protocol error
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(635):kenwood_safe_transaction return(-8) Protocol 
error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(635):kenwood_safe_transaction return(-8) Protocol 
error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, rs->rigport.retry=10 
-9:kenwood.c(1051):kenwood_get_if return(-8) Protocol error
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(635):kenwood_safe_transaction return(-8) Protocol 
error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for command IF
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood_transaction: retry_read=10, 
rs->rigport.retry=10kenwood.c(635):kenwood_safe_transaction return(-8) Protocol 
error
kenwood_transaction: retry_read=10, rs->rigport.retry=10
kenwood.c(584):kenwood_transaction return(-8) Protocol error
kenwood_transaction: wrong reply A0 for 

[wsjt-devel] Fw: Wsjt-x 2.5.4 FT-857

[jarmo via wsjt-devel]

Edelleenlähetetty viesti:

Päiväys: Mon, 17 Jan 2022 17:01:18 +0200
Lähettäjä: jarmo 
Vastaanottaja: wsjt-devel@lists.sourceforge.net
Aihe: Wsjt-x 2.5.4 FT-857


Has been while, when friend started to test wsjtx (FT8) with
FT-857 rig.
I changed OS from Xubuntu ro Fedora 34. basically all configs
"should" be same, BUT... No worky Don't get CAT working.. 
When try TEST CAT, get Response...

Ok, now got CAT working. Changet serial cable from cheap
China USB serial, to rs-232 serial cable and that helped.
BUT, now have this "output audio is muted" syndrome, with this
FT-857, as Kenwood TS-590SG have had...

jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Wsjt-x 2.5.4 FT-857

[jarmo via wsjt-devel]

Has been while, when friend started to test wsjtx (FT8) with
FT-857 rig.
I changed OS from Xubuntu ro Fedora 34. basically all configs
"should" be same, BUT... No worky Don't get CAT working.. 
When try TEST CAT, get Response...

Hamlib error: Communication timed out
rig_get_vfo: returning -5(Communication timed out
read_string called, rxmax=1024
read_string(): Timed out 0.700 seconds after 0 chars
read_string(): Timed out 0.700 seconds after 0 chars)rig_get_vfo: elapsed=701ms
rig.c(2962):rig_get_vfo return(-5) while testing getting current VFO

TX becomes active and have to stop by power off rig

This is with Hamlib Net rigctl
/usr/local/bin/rigctld  -m 1022 -r /dev/rig -t 4532 -s 4800  &

Also if chosen wsjtx setting rig FT-857 get same error... 
Earlier have had "rts" PTT method, which should be, but
not working, can't even test PTT, because no cat control...

Hamlib version
[root@fedora etc]# rigctl -V
rigctl Hamlib 4.5~git pe tammi 07 13:23:37 2022 + SHA=9731b5

Any ideas???

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.5.3: missing diist tar ball

[jarmo via wsjt-devel]

Fri, 24 Dec 2021 19:00:24 -0600
Gary Rogers via wsjt-devel  kirjoitti:

> Try here:
> 
> wsjtx-2.5.3.tgz
> 

>From my ISP not possible. Blocked. Only with TOR-browser works
I think Joe "could" talk with maintainer of this princeton.edu

Has been over this year unreachable from 109.108.25.x and
equalient inet6 addr.

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x

[jarmo via wsjt-devel]

Mon, 20 Dec 2021 21:04:00 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

I compiled 2.5.3 and confirm, crashes randomly, with NO other
explanations, that nigghtly log. Segmentation fault on these
executables: WSJTX. And there is orphan JT9 pid left after crash...
Fedora 35 XFCE4.
Hamlib does not crash. Rig TS-890s, Logging prog CQRLOG...

Jarmo, oh1mrr

> Well yes it's multi-threaded.  Don't believe that's the underlying
> cause though. Is there a common rig maybe?
> So far we have 1 IC-7300.
> Or a common OS?
> Or a common 32/64-bit version?
> For those that have seen this problem please report
> RigOS32/64 WSJT-XOther software running
> Mike W9MDB
> 
>  
> 
> On Monday, December 20, 2021, 02:54:55 PM CST, DANA MYERS via
> wsjt-devel  wrote: 
>This does sound rather like a Heisenbug, I haven't looked at the
> internal structure of WSJT-X, I bet it's multi-threaded. 73,   Dana
> K6JQ 
>   On 12/20/2021 12:26 PM Reino Talarmo via wsjt-devel
>  wrote: 
>
> Hi Mike,
>  
> I tested one wsjt-x.ini file that was available Saturday 18.12. from
> Al, who has the same “feature”. I used two windows 10  computers and
> set an audio connection between those and used various “/” callsigns.
> I could not repeat the issue at all. There was also available a
> windows error log that indicated that the error was Faulting
> application path: C:\WSJT\wsjtx\bin\wsjtx.exe Faulting module path:
> C:\WINDOWS\SYSTEM32\ntdll.dll I have no idea whether that helps at
> all. Hope that you can find a possible setting issue. 
> 73, Reino OH3mA
>  
>  
>  
>  
>
> From: Black Michael via wsjt-devel
> [mailto:wsjt-devel@lists.sourceforge.net] Sent: 20. joulukuutata 2021
> 21:21 To: wsjt-devel@lists.sourceforge.net
> Cc: Black Michael 
> Subject: Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x
>
> 
> 
> 
> There's a problem duplicating this error...I tried a loopback test
> here and no crashes 
>  
>
> Soquestion for those seeing this problem.
>
>  
>
> For Dana...it sounds like you did a restart of WSJT-X and duplicated
> the problem, right? 
>  
>
> So maybe there's a setting in WSJT_X that is related.
>
>  
>
> Can you send your WSJT_X.ini file?
>
>  
>
> Mike W9MDB
>
>  
> 
>  
>  
>  
>
>  
>   
> On Monday, December 20, 2021, 12:23:32 PM CST, Dana Myers via
> wsjt-devel  wrote: 
>  
>
>  
>   
> Hello,
> 
> I'm seeing a crash - twice a moment ago - when W9YOY/M called me.
> Using 2.5.3. Also running JT-Alert for WSJT-X
> 
> Perhaps related?
> 
> 73,
> Dana  K6JQ
>   
> 
> On 12/17/2021 7:43 AM, Al via wsjt-devel wrote:
>   
> ( wsjt-x 2.5.3, W11 )
> 
> Set mode FT8
> Enter DX call K0VQM/4
> Generate Std Msgs
> select Next 'TX 3'
> enable TX
> WSJT will crash on second or third transmission attempt
> 
> AL, K0VM
> 
> 
> 
> 
>  ___ wsjt-devel mailing
> list wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>  ___ 
> wsjt-devel mailing list 
> wsjt-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
>  
>  ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>   



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Wsjtx crash

[jarmo via wsjt-devel]

Sun, 17 Oct 2021 11:31:05 +0100
Bill Somerville via wsjt-devel 
kirjoitti:


> Hi Jarmo,
> 
> the button to stop collecting reference spectrum data is the one 
> labelled "Stop" on the main window.
> 
> 73
> Bill
> G4WJS.

Hi Bill

How obvious, but never got idea to use it :)
Propably READING could help, not microcrab style
next next next :)

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Wed, 29 Sep 2021 16:15:00 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

Hi Mike

Compiled latest git version 4.4 and no cahnge with TS-590SG.
We can run wsjtx (2.5.0) when radio set as TS-590SG, 9600 rest
as default. Audio goes out.
But again, if I set there /usr/local/bin/rigctld -m 2037 -r /dev/radio
-s 9600, wsjt setting radio set as Hamlib Net Rigctl, audio does not
go out, just tiny sound goes, but no matter how much turn output +
it stays kind of "muted"

Jarmo, OH1MRR
> Also...please the the git clone so you can get any patches I put
> in.The tar file only gets updated overnight.
> 
>  
> 
> On Wednesday, September 29, 2021, 11:03:57 AM CDT, jarmo via
> wsjt-devel  wrote: 
>  Wed, 29 Sep 2021 12:05:31 -0300
> Marco Calistri via wsjt-devel 
> kirjoitti:
> 
> > Il 29/09/21 11:07, Black Michael ha scritto:  
> > > Can you please try the latest hamlib and see if it's fixed now?  
> 
> Unfortunately not working. Compiled
> hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour.
> If try to use NetHamlib rictl, audio does not go into radio.
> Cat control works ok.
> But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works
> ok...
> 
> Jarmo
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>   



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Wsjtx crash

[jarmo via wsjt-devel]

Sun, 17 Oct 2021 04:45:47 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> Probably in the same directory as the wsjtx executable.
> Mike W9MDB

Tnx, I try look...
By the way, renamed refspec.dat and started wsjtx,
now works ok.

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Wsjtx crash

[jarmo via wsjt-devel]

Started to play with ref.spec, started measure, never got
stop measuring, or didn't find stop measuring button.
Wsjtx 2.5.0 self compiled, Fedora 34, latest hamlib 4.4 git version.
Now try start wsjtx, it starts for few seconds and then crash, get
message, if I translate it right from Fin to Eng "memory overflow"
(created core-file).
Where this core-file is created, can't find it?

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Strance behaviour

[jarmo via wsjt-devel]

Fri, 8 Oct 2021 12:15:36 +0100
Bill Somerville via wsjt-devel 
kirjoitti:


> Hi Jarmo,
> 
> further to the above, the FT8 DXpedition User Guide implies (perhaps
> it should state explicitly) that only compound non-standard calls are 
> supported for the Fox station. This is because some messages are 
> constructed with the shorter base call rather than using the full 
> compound call or a hash code. It may be that non-standard Fox calls
> that are not compound calls cannot be catered for in FT8 DXpedition
> Mode.
> 
> https://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
> 
> 73
> Bill
> G4WJS.

Ok, Bill
So, this is station, what can't be worked, because can't get report.
Or can be, but just quessing, what they gave :).
Other thing, still my ISP is blocked from the
https://physics.princeton.edu

Can't connect with Firefox there, have to use TOR-browser.. Not
very good day, but I'll survive :)

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Strance behaviour

[jarmo via wsjt-devel]

When listening 3DA0RU fox/hound mode, i copy
 15m
090130 -10  0.8  297 ~  R5RC 3DA0RU -
090130 -10  0.8  357 ~  UI3A 3DA0RU -
090130  -9  0.8  417 ~  UA1OLM 3DA0RU

No reports??? But this shows

090500  -8  0.8  297 ~  RJ6B RR73; UA6LND <3DA0RU> -18

What I am missing now... Or do 3DA2RU run some Clone
of WSJTX?

My WSJTX version 2.5.0 GA, tried with Fedora package
and Compiled version.
Same results with both

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Wed, 29 Sep 2021 16:15:00 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> Also...please the the git clone so you can get any patches I put
> in.The tar file only gets updated overnight.

I tried this one too, no change.
Strange thing is, that when TX, ptt fires up, so something is going into
radio, because PTT is set as VOX.
And when I monitor same freq, where I set friends system calling CQ,
I can see him there, but signal is VERY low.
We have distance abt 1 mile. If normal, he's coming to me +33,
now -03.
And this if Radio selected Hamlib Net Rigctl. If I select Kenwood
TS-590SG, he's back in +33.

So somehow, tone does dump down if used RIGCTLD... Have to admit, I'm
far out now :)

I tried to go back 2.4.0, but some libraries was too new, for
that version. Huge job downgrade...

Jarmo 


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Thu, 30 Sep 2021 09:25:41 -0300
Marco Calistri via wsjt-devel 
kirjoitti:

> Il 30/09/21 06:20, Reino Talarmo ha scritto:
> >
> > 2) *_AFSK is being regularly produced by WSJT-X through the
> > computer sound card_*, then I guess that there is a sort of
> > "*/software muting/*" of this signal which is blocked in some way
> > to feed the rear data connector of my YAESU FT-100 which in turn
> > doesn't transmit any RF. May be if I would attach the AFSK output
> > directly to the radio mic plug, then the RF transmission would be
> > possible.
> >
> > Hi Marco,
> >
> > This a wild guess as I have no access to YAESU FT-100, but in some 
> > rigs you need to select Mode Data/Pkt not USB in order to get audio 
> > via the rear data connector.
> >
> > 73, Reino OH3mA
> >  
> 
> Yeah Jarmo!!!
> 
> You are right, in fact yesterday I was playing around the modes and I 
> verified that if I select digital and set accordingly my FT-100 menu
> to use "PCT_USB", then my environment works: AFSK reach the rear data
> port and my FT8 signal is being transmitted.
> 
> However I guess DIG mode is not ideal for my setup because it looks
> like nobody is answering to my CQ's (tested some minutes on 40 meters
> band).
> 
> I will try again today the DIG mode on the higher frequencies, where
> is more easy to get a station reply.
> 
> Best regards
> 
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **

Hi

Now, again, question is about version change into 2.5.0. These
Kenwoods, ts590, ts890 have been working like charm. And my TS890 works
OK with 2.5.0.
Audio (afsk) is put into radio USB-A --- USB-B cable, no interfaces
between computer/radio.
Again, if chosen Hamlib Net Rigctl, no TX audio out, PTT fires radio TX
on. RX works perfect.
If chosen KENWOOD TS590SG as RADIO both TX and RX works OK.

This is the problem, I want to use HAMLIB NET RIGCTL, because want to
connect CQRLOG also. AN AGAIN, THIS HAVE BEEN working before..

Only thing, what also made me thinking, if SELINUX does not let
TX-audio out.

Anyway, something dumps audio..

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Thu, 30 Sep 2021 08:06:34 +0200
Claude Frantz via wsjt-devel 
kirjoitti:

> On 9/30/21 5:01 AM, jarmo via wsjt-devel wrote:
> 
> Hi Jarmo & all,

> These rigs may have different USB interfaces and different sound
> chips, so that they appear as different items in pavucontrol.

Yes, I know that and sure have selected right in pavucontrol..

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Wed, 29 Sep 2021 18:23:28 +0200
Claude Frantz via wsjt-devel 
kirjoitti:


> 
> Please debug the audio matter. My suggestion, at first:
> 
> aplay -l
> aplay -L
> arecord -l
> arecord -L
> pactl list

I think, it has nothing to do with souncard. Both radios are connected
directly via USB so wsjtx uses audio codec as input and output.

All have been working with Hamlib Net Rigctl earlier versions
of wsjtx. Now this 2.5.0 somehow rejects. As said, if I choose from
wsjtx prferences Radio TS-590SG instead of Hamlib Net Rigctl, I can get
TX working like charm. RX works with both.
And ONLY with TS-590SG TX does not work, when RADIO is set as Hamlib
Net Rigctl.
With my TS-890S, RADIO set as Hamlib Net Rigctl RX/TX works as
have done all the time.
OS in both cases is Fedora 34 with XFCE4 desktop, hardware is
a bit different, but, as have been working earlier, now vers 2.5.0 of
wsjtx make TX impossible..

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Wed, 29 Sep 2021 12:05:31 -0300
Marco Calistri via wsjt-devel 
kirjoitti:

> Il 29/09/21 11:07, Black Michael ha scritto:
> > Can you please try the latest hamlib and see if it's fixed now?

Unfortunately not working. Compiled
hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour.
If try to use NetHamlib rictl, audio does not go into radio.
Cat control works ok.
But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works
ok...

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Some minor issues.

[jarmo via wsjt-devel]

Tue, 28 Sep 2021 21:08:48 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> #1 Does the rig behave when NOT running cqrlog?#2 Please run rigctld
> like this, duplicate the problem, and send me the log.txt filerigctld
> -m 1021 --vfo -v -Z >log.txt 2>&1
> 
> Mike 

So, problem is, that can't get audio to radio with rigctld from wsjtx.

Upgraded to 2.5.0, strance things seen. With my TS-890s HamlibNet
rigctld works so far, with my Friends TS-590SG does not. Have to
choose in wsjtx settings Kenwood ts590sg, then it works.
With CQRLOG, I have to choose also Rdio Kenwood TS-590SG and from
settings choose "Take freq from WSJTX.
This works...
Shortly, start CQRLOG, choose Remote for WSJTX, it starts wsjtx
and both programs now getting right freq and audio goes out
from radio.

Wsjtx version 2.5.0 Richards experimental Fedora 34 rpm.
Hamlib version 4,4 daily snapshot, does not matter, if I change to
4.2 or 4.3 version, all work ok.

So, with TS-890s works HamliNet rigctld, with TS-590SG does not.

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.5.0-rc6: bug report

[jarmo via wsjt-devel]

Thu, 9 Sep 2021 20:53:45 +0100
John Nelson via wsjt-devel  kirjoitti:

> Hi Mike,
>
> 2.5.0.   No crashes occur and the code is working correctly so I have
> to conclude that there  is a Kenwood problem with hamlib 4.4

I'm using compiled daily snapshot 4.4 and have Ts-890 in use
Fedora 34 wsjyx 2.4.0 and no problems at all, so may be Mac
related

Jarmo, oh1mrr


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Blocked?

[jarmo via wsjt-devel]

Fri, 6 Aug 2021 08:06:36 -0500
Richard Shaw via wsjt-devel 
kirjoitti:

> You can use my COPR test packages if using Fedora, or worst case
> download and unpack the RPM to get the source:
> 
> https://copr.fedorainfracloud.org/coprs/hobbes1069/WSJT/build/2365258/
> 
> $ rpm2cpio .rpm | cpio -idmv
> 
> Thanks,
> Richard
> KF5OIM

Tnx Richard

I wait, when I get normal Fedora update. I'm aware your
site and some times tested from there.
Now have time to calm down a bit and wait official updates
from Fedora.

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Blocked?

[jarmo via wsjt-devel]

Not a big deal, but is my ISP, IP-range 109.108.16.0 - 109.108.31.255
somehow blocked from
https://www.physics.princeton.edu/pulsar/k1jt/index.html ?
If i try connect normally with any browser, never get site
opened.
But if I use TOR-browswr I get connected to site.. Any check?

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Maybe OT

[jarmo via wsjt-devel]

Wed, 28 Jul 2021 13:02:31 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> It's really a hamlib questionFYI...you don't need
> --set-conf=serial_handshake=NoneThat's the default for the rig but it
> won't help this problem. You may want to use the new way as the old
> rc.local is old hat Convert to the new method and see how it
> behaves. https://linuxhint.com/use-etc-rc-local-boot/
> 
> Mike W9MDB
Tnx Mike

That --set-conf... stayed there from earlier hamlibversions, when
I used ts-590s and then it was needed, with CQRLOG logging program.

I have tried, what you suggested, same behaviour. It is there,
just about find it...

HIHO, towards new dissapointments :)

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Maybe OT

[jarmo via wsjt-devel]

Sorry this noise, but kind of WSJTX question?

Has anyone managed to set Rigctld as service
in Fedora 33/34 in boot? If managed, what kind of script
used?
I have problem, after boot, service goes up, kind of, but
radio is not usable... 

● rigctld.service - /etc/rc.local Compatibility
 Loaded: loaded (/usr/lib/systemd/system/rigctld.service; enabled;
vendor preset: disabled) Active: active (exited) since Wed 2021-07-28
09:46:35 EEST; 5min ago Docs: man:systemd-rc-local-generator(8)
Process: 1284 ExecStart=/etc/rc.local start (code=exited,
status=0/SUCCESS) Main PID: 1284 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 9329)
 Memory: 8.2M
CPU: 12ms
 CGroup: /system.slice/rigctld.service

heinä 28 09:46:35 oh1mrr.ampr.org systemd[1]: Started /etc/rc.local
Compatibility. heinä 28 09:46:35 oh1mrr.ampr.org rc.local[1286]:
rigctld.c(272) Startup: /usr/local/bin/rigctld -m 2041 -r /dev/ttyS0 -t
4532 -s 9600 --set-conf=serial_handshake=None heinä 28 09:46:36
oh1mrr.ampr.org rc.local[1286]: rig_open: error = Command rejected by
the rig heinä 28 09:46:36 oh1mrr.ampr.org rc.local[1286]: kenwood_open:
cannot get identification heinä 28 09:46:36 oh1mrr.ampr.org
rc.local[1286]: kenwood.c(873):kenwood_open return(-9) heinä 28
09:46:36 oh1mrr.ampr.org rc.local[1286]: rig.c(1026):rig_open
return(-9) /dev/ttyS0 Success

But, if I run systemctl start rigctld from konsole all starts ok

● rigctld.service - /etc/rc.local Compatibility
 Loaded: loaded (/usr/lib/systemd/system/rigctld.service; enabled;
vendor preset: disabled) Active: active (exited) since Wed 2021-07-28
10:07:43 EEST; 2s ago Docs: man:systemd-rc-local-generator(8)
Process: 2757 ExecStart=/etc/rc.local start (code=exited,
status=0/SUCCESS) Main PID: 2757 (code=exited, status=0/SUCCESS)
  Tasks: 2 (limit: 9329)
 Memory: 3.0M
CPU: 10ms
 CGroup: /system.slice/rigctld.service
 └─2761 /usr/local/bin/rigctld -m 2041 -r /dev/ttyS0 -t
4532 -s 9600 --set-conf=serial_handshake=None

heinä 28 10:07:43 oh1mrr.ampr.org systemd[1]: Started /etc/rc.local
Compatibility. heinä 28 10:07:43 oh1mrr.ampr.org rc.local[2761]:
rigctld.c(272) Startup: /usr/local/bin/rigctld -m 2041 -r /dev/ttyS0 -t
4532 -s 9600 --set-conf=serial_handshake=None

Rigctld.service sript is

[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
Requires=multi-user-target
After=multi-user.target

[Service]
Type=idle
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no

[Install]
WantedBy=multi-user.target

Apologize, if this is far away from list..

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] very infuriating problem with Hamlib for TS-890S

[jarmo via wsjt-devel]

Tue, 20 Jul 2021 06:18:13 +
Conrad PA5Y via wsjt-devel  kirjoitti:

> Hello Jarno. I use an RX/TX sequencer. When I TX the station
> controller/ sequencer takes input from a footswitch (for SSB), WSJT-X
> via a com port to gnd to TX or a Winkeyer.  The sequencer is as
> follows. Relay is energised on RX.
> 
> 1. RX/TX masthead relay
> 2. LNA power
> 3. Transverter (if used)
> 4. PA PTT
> 5. Radio TX
> 
> This way when I TX all bands LNAs are protected. I only operate on
> 6m, 4m,2m, 70cms and 23cms. I can also individually switch the relays
> and LNA voltage off. I run EME on 2m and (soon) 70cms so it is
> important to provide this level of protection.
> 
> I have no RS232 from the sequencer on GND on TX so I use the SS
> input. I had misunderstood the modulation source settings, now all is
> working as expected.
> 
> 73
> 
> Conrad PA5Y

Hi

Ok, I didn't figure your purpose... I'm using mostly on HF, try to get
ES now on 6m, but that's highest...
Anyway, good to get things working...

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] very infuriating problem with Hamlib for TS-890S

[jarmo via wsjt-devel]

Mon, 19 Jul 2021 21:48:01 +
Conrad PA5Y via wsjt-devel  kirjoitti:

> So why does the WSJT-x  software work exactly as I want using the USB
> codec in and out on the K3S? Is it because in the K3S CAT commands
> there is no possibility to use transmit audio source and so therefore
> it does not matter?
> 
> I can key the K3S using the PTT or CAT and still have USB audio.
> 
> I have full CAT control and use RTS for PTT. This keys the rig and
> the TX audio goes via the internal USB audio codec. Just like I want
> it to. It would be more flexible to let the user choose what happens.
> However Kenwood have decided to disable the USB input if the SS (PTT)
> is used. There is no way that I can see to use non-CAT PTT and USB
> Audio in the TS-890S configuration. This is an oversight by Kenwood.
> The rig has hundreds of options but using PTT via the accessory
> socket while still using USB audio is not one of them.
> 
> Currently I am using audio from a UMC202HD soundcard via the ACC2
> socket, I really did not want to do that. I do not like to use CAT
> PTT to drive the sequencer, but I may have to. It is far better to
> have the RF drive go over last – always.
> 
> Anyway, it seems that WSJT-X is behaving correctly and that the
> TS-890S has limitations. So wrong email reflector.
> 
> 73
> 
> Conrad PA5Y

I use TS-890S and it works without any problems. Hamlib2 rigctl.
Cat control via RS-232 PTT-Method VOX, MODE USB, SPLITOP. FAKEIT
So, why not use RS-232?

Jarmo


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel