OK. I figured out my mistake with following the video.
When I run the rigctl-wsjtx.exe, and I try to test with F to get
frequency I get the get_freq: error = Invalid Parmeter.
On 6/2/2020 1:45 PM, Kim gross wrote:
Thanks for the help Mike
For my setup com3 is primary port, and com is
drops back to a
command prompt. I also switched the -r and -R to see if it made a
difference and it still hangs.
Kim Gross
On 6/2/2020 1:20 PM, Black Michael via wsjt-devel wrote:
I need one of the Yaesu owners to follow the directions in this
youtube video and send me their debug.txt
Windows 64 bit, upgraded to GA release I get a hamlib error and can not
do anything. Reinstalled RC3, system works fine. FT991A.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I have not seen this reported yet,
FT-8 on Windows 10 pro version 2004
I have WSJT-X set to put a blank line between decoding periods, and it
is not always doing that. I have had as many as three decoding periods
without a line between them.
This does not effect operation that I can tell,
got it
On 2/16/2018 7:46 AM, Black Michael via wsjt-devel wrote:
Seeing if the devel list is back up after the sourceforge move
de Mike W9MDB
--
Check out the vibrant tech community on one of the world's most
First let me say I would be interested in helping if not doing this, I
know some programing just not enough about this project.
But an option to have it look up all call signs info and giving
heading/distance info in the band activity window off to the right. For
larger enough screens it could b
