Charlie: I discovered something that had nothing to do with the Hamlib error that I thought I fixed. So I was operating FT 8 successfully the night after I thought I fixed the problem. Well the next night I went to operate and bingo the Hamlib error pops up. I am using the N3FJP logging program
Hi Malcolm
Great that you have it working again.
Please now contact the Hamlib developers with the details of the problem
you had and details of your setup, and how you fixed the problem. By doing
this, hopefully the problem can be fixed so you (and others) won't face the
same problem in future
Charlie it worked. I am using 2.7.0 successfully now. It took me a bit to understand what I was doing, but your instructions were right on. Hope to copy you on the air soon!Thanks! 73Malcolm PelhamWF5KOn Jul 8, 2025, at 11:36 AM, Malcolm Pelham wrote:Thanks I will try that, and I am using the Y
Thanks I will try that, and I am using the Yaseu FTdx10. I will let you know if that works. I am not very computer literate, but good enough to try things even if I am not sure what I am doing. I’ll keep you posted.Malcolm PelhamWF5KOn Jul 8, 2025, at 10:58 AM, Charles Suckling via wsjt-devel w
Hi Malcolm
If you mean this file libhamlib-4.dll (in the 2.8.1 bin folder) then a
first step is to rename that to something else and then copy/paste the file
with the same name in your 2.2.1 bin folder into the 2.8.1 bin folder.
If this works, please let us know.
I am not absolutely certain if
I just downloaded 2.8.1 from 2.2.1 and I am getting an error message for
Hamlib. It is a very long message that lists all of the things it controls. I
see the dll file in the WSJT folder, but unaware what to do to fix the error.
Malcolm Pelham
WF5K
On Wed, Mar 5, 2025 at 8:42 AM Brian Morrison via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> On Wed, 5 Mar 2025 04:29:24 -0700
> Jim Reisert AD1C via wsjt-devel
> wrote:
>
> > I just tried to update the data files in WSJT-X 2.7.0 in this order:
> >
> > 1. CTY.DAT
> > 2. LoTW
> > 3.
On Wed, 5 Mar 2025 04:29:24 -0700
Jim Reisert AD1C via wsjt-devel
wrote:
> I just tried to update the data files in WSJT-X 2.7.0 in this order:
>
> 1. CTY.DAT
> 2. LoTW
> 3. HamLib
>
> Both #1 and #2 updated without any problems. But when I tried to
> update Hamlib, I received the following
I just tried to update the data files in WSJT-X 2.7.0 in this order:
1. CTY.DAT
2. LoTW
3. HamLib
Both #1 and #2 updated without any problems. But when I tried to update
Hamlib, I received the following error. What does CTY.DAT have to do with
updating Hamlib?
[image: wsjtx_2025-03-05_04-25-
Unfortunately my health is not doing well and I need a volunteer to take over
Hamlib development.
Primary language is C -- pretty advanced with threading and complex/complicated
code and such.
So fluency in C is pretty much mandatory or very eager to learn.
Some side work is currently underway
Yes just check the contents etc show the same ;
, so that your script procedure works.
I have done it here for hamlib updates.
73
vk4tux
On 6/12/24 12:17, Marco Calistri via wsjt-devel wrote:
Il 05/12/24 20:14, Adrian via wsjt-devel ha scritto:
Just substitute the extracted hamlib compon
Il 05/12/24 20:14, Adrian via wsjt-devel ha scritto:
Just substitute the extracted hamlib component with that of github, in
the same path.
Then compile.
73
Very logic and straightforward answer, Adrian!
I just have to check carefully how to apply your suggestion in practice,
but you en-
Just substitute the extracted hamlib component with that of github, in
the same path.
Then compile.
73
vk4tux
On 6/12/24 06:19, Marco Calistri via wsjt-devel wrote:
If I want to to build hamlib from GIT and keep using the classic
method to compile WSJT-X, how to proceed?
Or better: how ca
Il 05/12/24 18:06, Black Michael ha scritto:
What do you mean "classic method" ?
Mike W9MDB
As I wrote in previous e-mail, I use the following syntax and I get the
Hamlib included into the WSJT-X archive:
marco@linux-turion64:~/WSJT-X_build/build>
rm -rf /home/marco/WSJT-X_build/build/wsjt
What do you mean "classic method" ?
Mike W9MDB
On Thursday, December 5, 2024 at 02:22:16 PM CST, Marco Calistri via wsjt-devel
wrote:
If I want to to build hamlib from GIT and keep using the classic method to
compile WSJT-X, how to proceed?
Or better: how can I switch to hamlib
If I want to to build hamlib from GIT and keep using the classic method
to compile WSJT-X, how to proceed?
Or better: how can I switch to hamlib GIT and ignore the hamlib version
which comes with WSJT-X tar?
This is not yet clear to me!
Thanks for any guidance in this regard.
Regards,
---
Thankyou, Is it possible to package Uwe's 'improved' versions too please ?
73
vk4tux
On 27/11/24 00:49, Hibby wrote:
You can see them directly at [1] - I've put that up temporarily, I meant to put
the plumbing in place to get that on the website proper, I'll do that later
today as I'm movi
You can see them directly at [1] - I've put that up temporarily, I meant to put
the plumbing in place to get that on the website proper, I'll do that later
today as I'm moving away from github for various reasons.
It's all a subset of the debian hamradio metapackages [2] both the packages and
t
I did not see wsjtx in your github packages list, Where are the packages
offered listed please ?
73
Adrian ... vk4tux
On 27/11/24 00:06, Hibby wrote:
that looks right - you should be able to 'apt install wsjtx' and be on
the latest with hamlib also installed.
As two alternatives to self building for the latest and greatest: if you're on
Raspi OS 12 (bookworm) 64 bit, you can enable debian backports [1] and install
a pretty up to date copy of wsjtx.
If you're not on bookworm 64bit, I maintain a private repo called hibbian [2]
in which I maintian and
Hi MIke!
I use the following procedure to compile WSJT-X on my Linux:
marco@linux-turion64:~/WSJT-X_build/build>
rm -rf /home/marco/WSJT-X_build/build/wsjtx-2.7.0/
tar -xzvf /home/marco/Scaricati/wsjtx-2.7.0-rc7.tgz -C
/home/marco/WSJT-X_build/build/
cd /home/marco/WSJT-X_build/build/wsjtx-2.7.
That information is out-of-date
$ mkdir ~/hamlib-prefix
$ cd ~/hamlib-prefix
$ git clone https://github.com/Hamlib/Hamlib src
$ cd src
$ ./bootstrap
$ mkdir ../build
$ cd ../build
$ ../src/configure --prefix=$HOME/hamlib-prefix \
--without-cxx-binding --disable-winradio \
CFLAGS="-g -O2" \
I am building on a Raspberry Pi.
INSTALL file says clone Hamlib and checkout "integration" branch.
I cannot find integration branch, or any mention of it on Hamlib repo.
Am I missing something?
Mark
___
wsjt-devel mailing list
wsjt-devel@list
evel@lists.sourceforge.net
Cc: Jeff Stillinger
Subject: Re: [wsjt-devel] Hamlib error
As Mike has already said, USB is not a valid com port. So the error message
says exactly what the problem is.
Linux should be something similar to this: /dev/ttyUSB0 or /dev/ttyUSB1.
My Icom 7100 is set to /dev/tty
As Mike has already said, USB is not a valid com port. So the error
message says exactly what the problem is.
Linux should be something similar to this: /dev/ttyUSB0 or /dev/ttyUSB1.
My Icom 7100 is set to /dev/ttyUSB0 for cat control.
Windows is a completely different beast. Again, the er
Is the port you selected actually named "USB" ? If so that's not a valid port
name in either Linux or Windows.
Mike W9MDB
On Sunday, April 28, 2024 at 05:53:18 PM CDT, Eric Lundstrom via wsjt-devel
wrote:
Installed wsjtx_2.6.1_amd64.deb on a lubuntu OS and received the hamlib
Installed wsjtx_2.6.1_amd64.deb on a lubuntu OS and received the hamlib error
shown below.
Installed wsjtx-2.6.1-win64.exe on a windows 10 OS and received basically the
same error.
The hamlib DLL on the Windows machine has a file date of 1/10/2023, a size of
9.7 mb, and a file name of libhamli
On Tue, Nov 7, 2023 at 4:27 PM Matt Melling via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hi,
>
> I am hacking on the WSJT-X package in NixOS, and looking at how we can
> split out the hamlib fork in to a separate package that can be shared
> with our js8call package.
>
On Fedora we
Debian has been building wsjtx with the stock upstream hamlib for ages
without issues.
Mageia also.
We build against the system version.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsj
Re: Matt Melling via wsjt-devel
> Thanks Mike l. My understanding is that at some point in the past there were
> some patches needed for Hamlib. Is that no longer the case?
Debian has been building wsjtx with the stock upstream hamlib for ages
without issues.
Christoph DF7CB
__
Thanks Mike l. My understanding is that at some point in the past there were
some patches needed for Hamlib. Is that no longer the case?
On 8 November 2023 00:51:00 GMT, Black Michael via wsjt-devel
wrote:
>That sourceforge link is no good anymore since Bill is SK.
>Here is the master repo http
That sourceforge link is no good anymore since Bill is SK.
Here is the master repo https://github.com/Hamlib/Hamlib
And here are the packages -- https://n0nb.users.sourceforge.net/
Mike W9MDB
> On Nov 7, 2023, at 4:27 PM, Matt Melling via wsjt-devel
> wrote:
>
> Hi,
>
> I am hacking on the W
Hi,
I am hacking on the WSJT-X package in NixOS, and looking at how we can
split out the hamlib fork in to a separate package that can be shared
with our js8call package.
The INSTALL references
https://sourceforge.net/u/bsomervi/hamlib/ci/master/tree/ where the
latest tag is 4.3.1. The master bra
Will do it Mike,
I will do it when radio is still cold, in order to avoid to have the
thermal drift as a possible cause, since I think the reason is another.
Regards,
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
Il 12/06/23 17:27, Black Michael ha scritto:
Please place this file as descri
Black Michael wrote:
> Need people to test the latest Hamlib please
it works fine for me with an FT-991 on Debian 12
--
73 de IU5HKX Daniele
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ws
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
For Linux put it in
~/.config
The WSJT-X_Rigcontrol.log file will
Tested new version compiled from git repository and on my old YAESU
FT-100 I see same behavior I saw with previous Hamlib versions.
I use WSJT-X 2.7.0 RC1 with settings Split=RIG and Mode= Data Packet and
at the very beginning of the operation, the VFO A (Transmitter) and VFO
B (Receiver) beha
Both were connected to dummy loads, not antenna.
I just repeated now with Multi- Control knob setting power to zero watts output
on both the IC-7300 and the IC-705 radios with same results.
Question for you, was I to use the WSJT-X v2.7.0-rc1 as originally released or
was there another versio
Sounds like RFI Problems due to noise on the USB cable
Tests
If problems are occurring only during transmit:
#1 Reduce power to zero and see if the problem stops -- if it does stop
than it is definitely RFI. You will see certain higher power levels on certain
bands that cause problems.
The
*_Testing IC-7300/IC-705, IC-7610 Results_*
Mike, on the IC-7610 so far the new *libhamlib-4.dll* seems to work.
On the IC-705 and the IC-7300 however:
The WSJT-X program /*crashes */if I start either radio from 7.074 MHz or
higher and THEN change the band setting drop down to 80m e.g., 3.573
Need people to test the latest Hamlib please
https://n0nb.users.sourceforge.net/
#1 Backwards compatibility with WSJT-X has been fixed.
#2 Notable speedups for Windows operations
Here's an FT-991 comparison
Old:
1:rig_get_freq: elapsed=16ms
1:rig_get_freq: elapsed=17ms
1:rig_get_split_vfo: ela
George
What operating system are you using?
Since you're the first with a 7610, I"d like to include you as a tester.
Dennis W1UE
On Sat, May 13, 2023 at 5:01 PM WB5JJJ via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> This also affected the IC-7610, but the new file fixed the prob
This also affected the IC-7610, but the new file fixed the problem.
73's
George - WB5JJJ
HoIP - 100105
On Sat, May 13, 2023 at 3:29 AM Tom M0LTE via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hey Uwe
>
> While manual testing could probably never be eliminated in the case of
> hamli
I agree on Uwes position over '''Rejnos, certainty...
On 13/5/23 22:59, Tom M0LTE via wsjt-devel wrote:
Hey Reino
I fully understand your concerns. Clearly this idea has been
considered. Conceptually I believe a slightly different approach might
overcome some of those difficulties, however I
Hi all,
As a help for those of you having problems with CAT control of your rig
with v2.7.0-rc1, I have copied the latest hamlib hotfixes to the folder
listed below. You will find there not only files for Windows but also
for macOS and Raspberry Pi.
https://sourceforge.net/projects/wsjt-x-improv
Hey Reino
I fully understand your concerns. Clearly this idea has been considered.
Conceptually I believe a slightly different approach might overcome some of
those difficulties, however I am conscious of derailing Uwe’s thread, so I
won’t.
Uwe, good luck with the search.
Best wishes
Tom
On Sat
I have been writing simulators but they do not have the nuances that the rigs
do. There's all sorts of oddities.
Butthe plan is to eventually incorporate those simulators in the "make
test" in Hamlib that should catch big mistakes.
It's on my to-do list but don't hold your breath...it's a
> From: Tom M0LTE via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
> Sent: lauantai 13. toukokuuta 2023 10.58
>While manual testing could probably never be eliminated in the case of hamlib,
>has there been any consideration of creating test harnesses to remove/reduce
>the need for manual
Hey Uwe
While manual testing could probably never be eliminated in the case of
hamlib, has there been any consideration of creating test harnesses to
remove/reduce the need for manual testing?
It strikes me that there could be potential to capture test cases from
manual testing with real rigs, th
Dear WSJT-X users,
Please allow me to summarize again here on this email reflector a topic
that is very important to me and to all of us. My original post was on
https://groups.io/g/wsjtgroup, so maybe it's best if you join the
discussion there.
Despite great personal commitment of the hamlib de
Try the latest hamlib
New hamlib for installation directions
#1 Shut down WSJTX
#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX -- hopefully your browser doesn't block it but may warn you multiple
times.
If you can do a "Save As" you can save it directl
I noticed today for the K3 if a band on the radio is set to DATA_REV (MD9), the
mode is not changed to DATA (MD6) when changing bands like it is if the mode is
any other setting. Looks like Mode 6 or 9 are considered accepted. Is this
intentional? I would think DATA (MD6;) should always be ch
I’ve compiled 4.5.2 for Mac here:
https://www.dropbox.com/s/ycqzp7uen1ktsrs/libhamlib.4.dylib?dl=0
> On Dec 21, 2022, at 9:12 AM, Charles Suckling via wsjt-devel
> wrote:
>
> Hi Mike
>
> Also tested SDR-Console and my IC202 (that uses G4JNT IC756 emulator in a
> PIC). So, happy here.
>
>
And here's a tar file too for compiling if any Unix users want to test
https://www.dropbox.com/s/q2cf6xb50pgsr61/hamlib-4.5.2-20221220.zip?dl=0
Mike W9MDB
On Tue, 20 Dec 2022 at 16:03, Black Michael via wsjt-devel
wrote:
Hamlib 4.5.2 is due to be released this week.All known bugs have been fi
Hi Mike
Also tested SDR-Console and my IC202 (that uses G4JNT IC756 emulator in a
PIC). So, happy here.
Charlie DL3WDG
On Tue, 20 Dec 2022 at 16:03, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hamlib 4.5.2 is due to be released this week.
> All known bugs have bee
Same here.
Also OK with HDSDR.
Charlie DL3WDG
On Tue, 20 Dec 2022 at 19:43, Al via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Mike,
> Looks ok with Flex 6xxx/2.6.0-rc5 so far..
> AL, K0VM
>
>
> On 12/20/2022 8:56 AM, Black Michael via wsjt-devel wrote:
>
> Hamlib 4.5.2 is due to
Sorry for the omission, Mike. Same version as previous. Running RC5 since it
came out.
> On Dec 20, 2022, at 21:23, Black Michael via wsjt-devel
> wrote:
>
> What version of WSJT-X do you have? I'm running 2.6.0-rc5 and can switch
> from FT8 to FT4 and back without a problem.
>
> Hamlib i
What version of WSJT-X do you have? I'm running 2.6.0-rc5 and can switch from
FT8 to FT4 and back without a problem.
Hamlib is not involved in decoding at all.
Mike W9MDB
On Tuesday, December 20, 2022 at 07:51:16 PM CST, Gary McDuffie via wsjt-devel
wrote:
> On Dec 20, 2022, a
> On Dec 20, 2022, at 17:13, Dennis Younker NE6I via wsjt-devel
> wrote:
>
> Hamlib 4.5.2 is due to be released this week.
> All known bugs have been fixed.
I don’t remember if this was Hamlib problem, or something else, but the decode
problem has risen its head again on my system. I commen
;mailto:m...@wsjtx.groups.io>; WSJT Software Development
<mailto:wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mailto:mdblac...@yahoo.com>
Subject: [wsjt-devel] Hamlib 4.5.2 test #hamlib
Hamlib 4.5.2 is due to be released this week.
All known bugs have been fixed.
Please test
Again without the html formatting.
Hamlib 4.5.2 is due to be released this week.
All known bugs have been fixed.
Please test and ensure everything is workingor report any bad behavior.
This will likely be the hamlib in the WSJT-X release.
Here is a zip file for the 64-bit binaries.
https:
Seems to be working fine here: Yaesu FTDX-101MP running WSJT-X v2.6.0-rc5.
--Dennis NE6I
From: Black Michael via wsjt-devel
Sent: Tuesday, December 20, 2022 6:56 AM
To: WSJTX Group ; WSJT Software Development
Cc: Black Michael
Subject: [wsjt-devel] Hamlib 4.5.2 test #hamlib
Hamlib
Mike,
Looks ok with Flex 6xxx/2.6.0-rc5 so far..
AL, K0VM
On 12/20/2022 8:56 AM, Black Michael via wsjt-devel wrote:
Hamlib 4.5.2 is due to be released this week.
All known bugs have been fixed.
Please test and ensure everything is workingor report any bad
behavior. This will likely be
Hamlib 4.5.2 is due to be released this week.All known bugs have been fixed.
Please test and ensure everything is workingor report any bad behavior.
This will likely be the hamlib in the WSJT-X release.
Here is a zip file for the 64-bit
binaries.https://www.dropbox.com/s/q2cf6xb50pgsr61/haml
Il 14/09/22 19:04, Black Michael via wsjt-devel ha scritto:
If everyone running RC4 would please check their wsjtx_syslog.log file
and see if there are any hamlib errors I would appreciate it. If
errors/warning are seen please send the log to me
Getting ready to release Hamlib 4.5 and would l
309][00:00:04.210114][error] icom_set_vfo:
Mapping VFOA=Main
[RIGCTRL][2022-09-14 16:16:37.439312][00:00:04.345583][error] rig_get_vfo: no
get_vfo
From: Black Michael via wsjt-devel
Sent: Wednesday, September 14, 2022 6:05 PM
To: WSJT Software Development
Cc: Black Michael
Subject: [wsjt-dev
Hi Mike,
Following copied from Syslog file. Pages of such errors. Kenwood TS590S
and W10.
[RIGCTRL][2022-03-01 06:01:50.482824][06:43:10.816962][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[SYSLOG][2022-03-01 06:01:54.042227][06:43:14.376024][warning] Detected
dropped audio s
Hi Mike,
Using 'rigctld-wsjtx' self compiled from source 'wsjtx-2.6.0-rc4.tgz' on
Ubuntu Linux 18.04.
There is no file named 'wsjtx_syslog.dat' anywhere.
However there is logfile 'wsjtx_syslog/_2022-09.log/' in directory
'/home/[username]/.local/share/WSJT-X/*logs*'
Upon startup one erro
Hi Michael --
I have only so far seen warnings about dropped audio samples as shown
below. I guess these have nothing in particular to do with Hamlib, but if
you want more details, please let me know. 73, Paul K6PO
[SYSLOG][2022-09-15 04:46:35.661153][00:00:00.000650][info] Log Start
[SYSLOG][20
No errors re hamlib. Line like the following at startup:
[RIGCTRL][2022-09-14 00:12:04.983628][00:00:00.272132][info] Hamlib
version: Hamlib 4.5~git Sun Sep 04 16:38:41 2022 + SHA=6c746c
w8lvn
On Wed, Sep 14, 2022 at 5:13 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wr
If everyone running RC4 would please check their wsjtx_syslog.log file and see
if there are any hamlib errors I would appreciate it. If errors/warning are
seen please send the log to me
Getting ready to release Hamlib 4.5 and would like to ensure all is working
well.
For WindowsC:\Users\[userna
rate setting could be changed or COM port number.
73, Reino OH3mA
-Original Message-
From: Marty Wayne via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 23. heinäkuutata 2022 4:29
To: WSJT software development
Cc: Marty Wayne
Subject: Re: [wsjt-devel] Hamlib Error
I can’t
I can’t even get the radio and wsjt-x to communicate. I misspoke when I said
that the Hamlib error happened while using FT8. Actually, I had taken a short
break. I believe I shut down wsjt-x and restarted when I returned. That is
when aI started getting the Hamlib error. I hadn’t changed th
As a diagnostic..
While sending CQ for example..
Reduce the transmit power,
by both audio and transmitter settings and see
if the phenomenon goes away at lower powers.
If with the output minimized the phenomenon
persists then it is probably not RFI related.
If you find a reduced output power th
If it runs at startup but fails during/after transmit than it is probably RFI.
Here are some potential solutions -- ordered by cost.
#1 Free - Move USB cables to another port -- some ports are more susceptible
than others.#2 Free -- Check your grounding system. rod-outside-the-shack is a
common
I used a RasPi4 2.6.0 rc1 and a FTDI to control my 1996 ft1000mp
with a USB audio dongle for field day.
The RadPi4 was headless using No Machine so I could
operate remotely from the TV room with my Android phone
or laptop.
FTDI has less problems especially with some other software
works very well
Marty,
I have used a simple USB to RS-232 converter cable with my FT-1000MP for CAT
control. You have already Signalink for audio audio/PTT.
73, Reino OH3mA
-Original Message-
Marty,
In your list of equipment, I don't see a CAT interface. The Signalink is
only a sound card interface. T
Marty,
In your list of equipment, I don't see a CAT interface. The Signalink is
only a sound card interface. There is no CAT interface. The error
message shows that WSJT-X was trying to access the FT-1000MP's CAT. To
get around this, In WSJT-X, go to Settings - Radio. Near the top, where
it s
Likely to be an RF ingress issue, vs a software problem.
George J Molnar
College Park, Maryland
KF2TFM19ma
> On Jul 21, 2022, at 1:28 PM, Marty Wayne via wsjt-devel
> wrote:
>
> I tried operating with WSJTx 2.5.2 and 2.5.4 with same issue.
>
> 73,
>
> Marty, W6NEV
> _ . . . . _ _
I tried operating with WSJTx 2.5.2 and 2.5.4 with same issue.
73,
Marty, W6NEV
_ . . . . _ _ _ . . . . _ . . . . . _
mcway...@comcast.net
408-234-8023
> On Jul 21, 2022, at 10:23 AM, Marty Wayne wrote:
>
> I was working 20 Meter FT-4 and at one point I got a Hamlib error,
> commun
I was working 20 Meter FT-4 and at one point I got a Hamlib error,
communication timed out. See report below. Im not computer savvy. What might
be the issue?
Rig-FT-1000MP
iOS 12.5
SignaLink USB interface
WSJTx 2.5.2
WSJTx 2.5.4
Hamlib error: Communication timed out
rig_get_vfo: returning -5
; WSJTX Group
Cc: Black Michael
Subject: [wsjt-devel] Hamlib testing #Hamlib
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.
Some recent
Software Development ; WSJTX Group
Cc: Black Michael
Subject: [wsjt-devel] Hamlib testing #Hamlib
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
Hi Al,
Please be so kind and test it again with this test version of WSJT-X:
https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.6.0/Tests/wsjtx-2.6.0-rc1-win64_with_patch_for_IC7100_and_IC7610.exe
It is our current WSJT-X v2.6.0-rc1, but with one additional patch,
which hopefully f
I tested the new vn of hamlib on my IC7100 and attached is the syslog file.
It still shows the VFO B error and it now shows a file not found error.
Al AF4FA
[SYSLOG][2022-07-08 16:25:21.484458][00:00:00.000399][info] Log Start
[SYSLOG][2022-07-08 16:25:21.484458][00:00:00.000437][info] WSJT-X
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
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.
Some recent important fixes are IC-9700 in split mode should work better now
and split opera
Hamlib PTT issue seems to be a regression in Hamlib.
I was running Hamlib built from github master. When I built hamlib from the
4.4 release instead of master, PTT works fine over hamlib network
connection.
It was my mistake to oversee that github master was not the latest released
version.
Than
> On the Pi, or any Linux based system, you have to be a member of the
dialout group in order to have access to the serial port. So if all of the
software is being denied access to the serial port, most likely, your not a
member of group dialout.
Thank you for the suggestion Jeff. This is not the
When pressing Test CAT a connection is opened from WSJT-X to rigctld and
closed very quickly as WSJT-X displays the error message in my original
email
This is the part of the log after I press Test CAT. I'll send you the log
directly as I do not think the mailing list allows them.
2022-06-23T15:05
On the Pi, or any Linux based system, you have to be a member of the
dialout group in order to have access to the serial port. So if all of
the software is being denied access to the serial port, most likely,
your not a member of group dialout.
sudo -a -G dialout
Reboot to be safe, but logg
All 5-v
On Thursday, June 23, 2022 at 09:18:14 AM CDT, Hrafnkell Eiriksson via
wsjt-devel wrote:
I'll get you that log later today. What verbose level do you need on rigctld
(how many v)?
Thanks Hrafnkell TF3HR
On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel
wrot
I'll get you that log later today. What verbose level do you need on
rigctld (how many v)?
Thanks
Hrafnkell TF3HR
On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1"
And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1" to
the rigctld line.
rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532
--set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1
--ptt-type=RTS -Z >log.txt 2>&1
Then send me the
Then PTT CAT should work. WSJTX should send the "T" command to rigctld and
rigctld then uses the RTS keying.
I just confirmed that works.
2022-06-23T08:37:29.191879-0600: rigctl(d): T 'currVFO' '3' ''
''2022-06-23T08:37:29.191879-0600: rigctl_parse:
vfo_opt=02022-06-23T08:37:29.191879-0600:
It works fine when I'm running WSJT-X on the same computer as hamlib
rigctld and I can set it to access the serial port directly for PTT.
But in this case I'm running WSJT-X on Windows but running hamlib rigctld
on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the
raspberry pi.
WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1
port.
Just tested it here and it uses it correctly (though I tested on Windows).
Mike W9MDB
On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via
wsjt-devel wrote:
> Why do you have rst_
> Why do you have rst_state=ON? That conflicts with ptt-type=RTS and
might be why it's not working.
I have rts_state and dts_state ON to power the CAT cable. The --set_conf
option only seems to apply to the rig-file device, not the ptt device. I
can remove the rts_state=ON, it has no effect on PT
The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work.
Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be
why it's not working.
And dtr_state=ON would only be needed if your CAT cable needs power from the
computer to work.
Mike W9MDB
On Wednesd
Hi
I'm running WSJT-X v2.5.4 on a Win10 computer.
I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected it
to my Icom706mk2g.
I'm using two com ports from the RPi, one for CAT control and one for PTT.
I've set WSJT-X to use hamlib for rig control and pointed it to the
ip:port
1 - 100 of 277 matches
Mail list logo
