OK on that link, however with the CP2105 comports it is best to wsjtx
select the standard comport instead of CAT for PTT,
and use RTS as KI5GFU has RPTT set.
RPORT gain is better at 7 to 10 rather than 25, as this allows better
wsjtx 'TX pwr' linear control, where small adjustments result in a
From my notes helping somebody else.
FTDX-10 Data/Pkt mode bandwidth not working..had to use USB mode Data
Out Level=0 ()
Some more info
https://ki5gfu.com/2021/10/14/ftdx-10-setting-up-wsjt-x-configuration-for-digital-eg-ft8/
Mike W9MDB
On Thursday, June 23, 2022 at 05:02:
Got the Yaesu FTdx10 a couple of weeks ago and and trying to
> get on FT8 everything said I needed a laptop or PC with windows 10/11.
> So last Monday I went out & caught one with win11 home installed,
> while I was in the shop they got it setup for me with all the updates
> etc. sorted. jobs
It's happened on both my PC's as well Mike, one is running W10 and the
other W11.
73 Tony, ZL3HAM
On 24/06/2022 4:10 am, mpcorey--- via wsjt-devel wrote:
Good afternoon,
I am using the 2.6.0-rc1 release, and generally like the new features
and have encountered no problems. However, today
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
Same infos here with Win 11 + RC1
Keijo OG5O
Lähetetty Windowsin Sähköpostiista
Lähettäjä: mpcorey--- via wsjt-devel
Lähetetty: torstai 23. kesäkuuta 2022 19.13
Vastaanottaja: wsjt-devel@lists.sourceforge.net
Kopio: mpco...@gmail.com
Aihe: [wsjt-devel] Error
Good afternoon,
I am using the 2.
I had this begin to happen on a previously stable version 2.5.3 but a long
delayed upgrade to 2.5.4 got rid of it, W10. Only a week or so ago.
I haven't been able to test the RC yet, but thought I'd report this just in
case it's from the same cause.
Alan G0TLK, sent from my mobile device
On
> 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
Good afternoon,
I am using the 2.6.0-rc1 release, and generally like the new features and
have encountered no problems. However, today while calling CQ on 6 meters
FT8, the program abruptly shut down. There was no indication in the task bar
that it was still running. I tried to restart it an
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
2.6.0-rc1, built from source on Fedora Core 36, 64-bit.
In the WSPR mode, the first transmit cycle (after several normal receive
cycles) ends 95 seconds after the start of the window.. Example - Transmit
window starts at 14:16:00, ends at 14:17:35. WSJT-X stays on the same band
from that point u
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"
In \Users\[username]\AppData\Local\WSJT-X rename the WSJT-X.ini file.
That will allow you to start a new setup.
Mike W9MDB
On Wednesday, June 22, 2022 at 07:06:52 PM CDT, Donhawbaker via wsjt-devel
wrote:
At first RC1 worked fine. But now it boots up, shows the splash beta screen,
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
20 matches
Mail list logo
