1.7.1-devel r8195
de Mike W9MDB
On Saturday, November 18, 2017, 4:46:32 AM CST, Wolfgang
wrote:
Hello Mike,
looks interresting, thanks for that ;-)
The patch is based on which source release ?
73's de OE1MWW
Wolfgang
Friday, November 17, 2017, 10:08:47 PM, you
Hi Unni,
It may be that Windows Update has installed a broken Prolific driver,
check the update logs to see if it has been changed, if so you could try
rolling back the Prolific USB to serial port driver.
73
Bill
G4WJS.
On 18/11/2017 12:46, Unni Tharakkal wrote:
Thank you Bill.
Rig
Thank you Bill.
Rig settings are checked Com connections are checked cables checked. All
are ok
Will middle around and see to it and will let you know also
With regards
Unni
On Sat, Nov 18, 2017 at 6:07 PM, Bill Somerville
wrote:
> Hi Unni,
>
> if the COM port number
Hi Unni,
if the COM port number is correct then there may be an issue with the
remaining settings like baud rate or handshaking.
Also check that your FT-857 had it's port set to CAT mode and not ATU
mode. Check your physical cable connections.
To use Omni-Rig select "Settings->Radio->Rig"
Dear Bill
Thanks for the suggestions. The com connections are perfect and use to
check frequently for its numbers. I feel the problem is something with
Hamlib.
Is there any way to connect through Omnirig to FT857 to try whether the
problem is with Hamlib or not?
With regards and 73s
Unni
VU2TE
Hi Unni,
those errors imply that the COM port number has changed, perhaps due to
a Windows update causing hardware devices to be re-scanned. Check that
the COM port number for your CAT interface is correct by locating it in
the Windows Device Manager application.
Prolific USB to serial
Reboot the computer in case WIN10 has messed with settings. Check com ports in
Device manager to be sure they still match the software. de W4WNT
Sent from Yahoo Mail on Android
On Sat, Nov 18, 2017 at 7:05 AM, Unni Tharakkal
wrote: Dear All
I was using the WSJTX
Is there some reason you’re using RC3 and not the latest version? I’d
recommend going that path first.
Jim S.
N2ADV
From: Unni Tharakkal [mailto:unnitharak...@gmail.com]
Sent: Saturday, November 18, 2017 7:05 AM
To: WSJT software development
Subject: [wsjt-devel] WSJTx ver 1.8-rc3
Is there some reason you’re using RC3 and not the latest version? I’d
recommend going that path first.
Jim S.
N2ADV
From: Unni Tharakkal [mailto:unnitharak...@gmail.com]
Sent: Saturday, November 18, 2017 7:05 AM
To: WSJT software development
Subject: [wsjt-devel] WSJTx ver 1.8-rc3
Dear All
I was using the WSJTX ver. 1.8 rc3 peacefully with some problem with Hamlib.
So I unstalled everyting and installed again Now my problems are
1. the Hamlib doesn't connect the program. The errors I am getting are
2. Hamlib error : I/O error while opening connection to rig
>>
>> 3.
Hello Mike,
looks interresting, thanks for that ;-)
The patch is based on which source release ?
73's de OE1MWW
Wolfgang
Friday, November 17, 2017, 10:08:47 PM, you wrote:
Implements single-click on decoded text. Removes double-click tx enable config
item.
Double-click behaves as before
11 matches
Mail list logo