The error isn't showing up in your txt file.Can you re-run rigctld with -vvvvv
and send just the last part that shows the get_vfo call and error?
de Mike W9MDB
On Saturday, October 21, 2017, 4:28:11 PM CDT, Philippe CHARDON (LaPoste)
via wsjt-devel <[email protected]> wrote:
Hello everyone,
You will find the description of the issue that I faced while trying to use the
last 2 releases of WSJT-X. Going back to Rev 1.8 rc1 solves the problem.
- Program version: 1.8.0-rc2 & rc3, hamlib-w64-3.1
- Operating system: Windows 8 64
- Concise description of the problem:
The frequency display background is red,
It is impossible to change the mode,
The selection of the band (rolling list) is not operational,
Opening the preference panel provides no way to solve the issue.
- Exact sequence of steps required to reproduce the problem: It happens as soon
as WSJT-X rc2 & 3 have been started up.
- Rig Information: FTDX1200 & SCU 17
I use the most recent version of Hamlib as a standalone program. WSJT-X
connects to the Hamlib software via the Hamilb NET rigctl selected in the
preference menu.
I could get access to the messages reported by Hamlib during the issue. You
will find a copy attached as well as some pictures of my PC screen.
According to my understanding, rc2 & 3 may send invalid commands to Hamlib.
73 Philippe
F5FDV
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
