Hi John,
some comments in line below.
On 10/09/2017 02:23, [email protected] wrote:
1.8 rc2 was working fine using FT8 with Windows 7 Pro 64. My rig is a
Hermes SDR.
ok
In trying to set up for possibly working FT8 with a N3JFP VHF contest
logging program I got a "hamlib error". At first it said the serial
port was in use by another program. Nothing seemed to help, so I
selected the default configuration... that made everything worse.
Tried to re-enter the set up, but could never get it to work again.
Even after re-installing rc2.
You cannot have two applications opening the same serial port at the
same time. There are a couple of possible ways to work around this. If
your logging program supports either the Hamlib rig control server
(rigctld) or the OmniRig rig control server then you can use the server
to connect directly to your rig and it allows other applications to
monitor and control the rig by proxy. Another option is that is that
some logging applications themselves have a proxy rig control server
that WSJT-X can access, I don't think that is the case with ACLog.
Others will tell you that you can simply download VSPE an make a virtual
serial port 'Y' cable, don't do this as it doesn't work reliably and
will inevitably lead to rig control errors that we cannot and will not fix.
Launched 1.7 and found everything still screwed up the same way.
I doubt anything is "screwed up" you just need to fix the settings error
you have made.
The transmission boxes were all empty, except for the last one which
had the CQ message (should be the 73 message)
This is normal if no "DX Call" has been entered, it cannot generate
messages until it knows who you QSO partner is. Tx6 is the CQ message
and Tx5 is the signoff (73) message.
Perhaps there is a settings file used by both programs that is
corrupt. Is there a way to start over without losing the logs (I
think they are used by JTalert to tell if a station was worked before,
so I don't want to lose them).
Tell us what error you are getting or what is not working specifically,
it will be much easier to fix the issue rather than throw all the
settings away.
Any suggestions on what I should do? Everything worked fine with
N3JFP's AClog program until I tried to use it with the VHF logging
program.
Try closing down ACLog and getting WSJT-X running stand alone, then
start ACLog and see what goes wrong. If both are trying to access your
rig simultaneously then you need to stop one of them doing that or use a
rig control server solution as mentioned above.
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
