Hi,
SuperHound mode crashed with runtime error:
Computer: Raspberry Pi 4
OS: Debian GNU/Linux 12 (bookworm) 64 bit
Radio: ICOM IC7300
I left system running overnight and this morning I was greeted by the
error message above...
73 de Kari, oh2gqc
_
Do a Hamlib update on the Rig tab and if it still doesn't work
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=1
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
Here's
Hi Andy,
Thanks for your report -- it's much appreciated. We're aware of the
problems you identified, and we plan to have them corrected in time for
the next release.
-- Joe, K1JT
On 7/12/2024 2:40 PM, Andy Durbin via wsjt-devel wrote:
WIn 64 bit, OS Win 8.1
ALL.TX log does not co
Have you checked to see that the correct COM port is selected?
73
Fred
K3FRK
On Fri, Jul 12, 2024 at 5:40 PM Peter Wollenberg via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hi
>
> I have operated WSJT V 2.6.1 with great success and no problems for many
> month using a WIN7 laptop in
Hi
I have operated WSJT V 2.6.1 with great success and no problems for many month
using a WIN7 laptop into an ICOM 7600 radio.
Now installed the 2.7.0 RC5 software and the pc now longer communicates with
the radio as the frequencies are not displayed on the software screen, just
showing 0.
All m
I did some further testing.
I have pipewire disabled and am only using alsa. If I use aplay to send
to the FT-710 sound device, it succeeds. If I open any one of the two
serial ports with something like "cat /dev/ttyUSB0", aplay shows reset
errors in syslog.
So, this is not pipewire, wsjtx or ham
WIn 64 bit, OS Win 8.1
ALL.TX log does not correctly record the decode window text and the QSO
frequency: -
Decode window:
181330 -1 0.2 730 K3WYC K8R RR73
181330 -1 0.2 730OZ3AEV K8R RR73
181330 -1 0.2 730G4WFQ K8R -18
181330 -1 0.2 730KA6RWL K8R -12
181330 -1 0.2 730
Hi Laurie,
Thanks for this heads-up. SuperFox features are still in a fairly early
stage of development. We need to get the basic operation right, first,
and to gain some experience from in-the-field operation. We'll hope to
satisfy the need you've identified in the next release.
RC5 does not produce udp decode messages (#2) for SuperFox decodes.
Is this a defect or by design?
Without the decodes there is no way for JTAlert to notify a station they
were called by the fox nor to highlight their callsign (the called
station) in the Activity display.
de Laurie VK3AMA
(J
Yes I have been using without port number, Just the radios host name.
AL, K0VM
On 7/12/2024 6:51 AM, Black Michael wrote:
Good -- you should also find the port# is not necessary and Hamlib will, in
fact, override anything you put in for port#. That's because the Flex protocol
is always on p
Good -- you should also find the port# is not necessary and Hamlib will, in
fact, override anything you put in for port#. That's because the Flex protocol
is always on port 4992. It will also complain with that same message now if
you use 127.0.0.1 with that better error message.
Mike W9MDB
11 matches
Mail list logo
