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 <g4...@classdesign.com>
wrote:
> 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" as "OmniRig RIg 1" (or 2 if
> your Omni-Rug server is set up for port two to connect to your FT-857).
>
> 73
> Bill
> G4WJS.
>
>
> On 18/11/2017 12:32, Unni Tharakkal wrote:
>
> 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
>
> On Sat, Nov 18, 2017 at 5:51 PM, Bill Somerville <g4...@classdesign.com>
> wrote:
>
>> 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 adapters do not store their COM port number and
>> can potentially change just by re-scanning the hardware devices or by
>> plugging into a different USB hub or hub port.
>>
>> 73
>> Bill
>> G4WJS.
>>
>>
>> On 18/11/2017 12:04, Unni Tharakkal wrote:
>>
>> 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. Communication timed out while getting current frequency
>>>>
>>>>
>>>> I tried resetting the configuration No use
>>>>
>>>>
>>
>>> Tried to update Ham lib - could not do it (How hamlib 68bit ver. can be
>>>> updated I am using Win10 68 bit)
>>>>
>>>> Then I tried to get it connected through Omnirig the error report is
>>
>> Omini Rig : Initialization timed out
>>
>> My set up is FT 857D with CH340 (CT62) rig control and a BY make Prolific
>> PTT control
>>
>> Using Win 10 Acer i3 lap top computer
>>
>> Where I have gone wrong Please help. There is lot of opening to my side
>> from Europe and Russia
>>
>> With regards and 73s
>>
>> Unni
>> VU2TE
>>
>>
>>
>
> ------------------------------------------------------------
> ------------------
> 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
> wsjt-devel@lists.sourceforge.net
> 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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
