Portmon from Sysinternals (part of Microsoft) may tell you what's going on
with the com ports, assuming Windows OS, and that it picks up the virtual ones.
Alan G0TLK, sent from my mobile device
On 11 June 2020 07:59:53 Tom Ramberg via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
That is: The radio is connected to the computer via the MKII. The COM ports
I refer to are all virtual ports created in Microham's router. As I stated
in my other response, the aim is to keep it as simple as possible for the
new hams in my club. They use N1MM+ for genaral logging, and that is simple
and it works. WSJT-X works great as standalone. If I cannot make the
applications cooperate, so be it. But there had been a lot of talk of
Hamlib errors lately, so that is why I raised the issue. I beg to be
excused if this is not a WSJT-X issue, but rather, as it seems now, a
Microkeyer router thing. My computer skills have, I am afraid, clear
limitations.
73,
Tom OH6VDA
11. jun. 2020 kl. 09:10 skrev Tom Ramberg <oh6...@yahoo.com>:
No. That's it.
73
Tom OH6VDA
Sendt fra min iPad Air 2
10. jun. 2020 kl. 16:20 skrev Bill Somerville <g4...@classdesign.com>:
On 10/06/2020 14:11, Bill Somerville wrote:
On 10/06/2020 14:01, Tom Ramberg wrote:
First it happens when I set the Com port In the radio tab WSJT-X settings
(in this case COM5) and press the "Test CAT" button. It turns red, and a
pop up window appears with the message "Rig Failiure. Hamlib error: I/O
error while opening connection to rig". See screenshot.
Hi Tom,
is COM5 really the serial port of your rig,or do you have something else in
between?
73
Bill
G4WJS.
Other than the microHAM uRouter and interface device.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
