It sounds like you're trying to do port sharing. I'm don't believe the
microham supports that. I believe it does support PTT on one com port and CAT
on another. And it can also echo CAT responses to another COM port for
monitoring...but not CAT control.
So if you turn off N1MM and connect WSJT-X to COM4 it all works OK?
What kind of rig do you have? There are solutions for having multiple programs
(like N1MM and WSJT-X) sharing the rig.
Mike
On Wednesday, June 10, 2020, 08:06:38 AM CDT, Tom Ramberg via wsjt-devel
<[email protected]> 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.
If I ignore the message by pressing OK, The button turns green, and if I exit
the settings and try to change bands, it seems to work okay. But then on a
second try to press the "Test CAT" button, the second error message appears,
saing "Hamlib error: Communication bus colision while trying to get the current
VFO, se screenshot.
On CAT1 (in this case COM4), I am connected to N1MM+.
I have also tried to use Omnirig, but that just makes WSJT-X crash without any
warning messages at all.
Tom OH6VDA
> 10. jun. 2020 kl. 12:44 skrev Bill Somerville <[email protected]>:
>
> On 10/06/2020 07:45, Tom Ramberg via wsjt-devel wrote:
>> Starting WSJT-X with FTdx3000 and using 2nd CAT port in MicroHams device
>> router gives Hamlib error.
>>
>> de OH6VDA TOM
>
> Hi Tom,
>
> what is the full error message, including details, please? When does it
> happen?
>
> 73
> Bill
> G4WJS.
>
>
> _______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
