Re: [Hamlib-developer] error in hamlib 3.2 in windows 7

[Dave B <g8k...@go...>]

Hi.

As Bill says, use rigctld (note the d on the end, for daemon mode, that
sits in memory doing it's job in the background.)

With the -T option (host) you can use the name 'localhost' (without the
quotes) and that will guarantee to resolve to the real localhost
address, whatever it might be.

For testing needs (not entirely recommended) just -T on it's own, will
let rigctld to listen on any/all interfaces it can find!  As netstat
-anb (run as admin) will show you.

You also can use any telnet client to connect to it, and check things
out in regards to it's ability to control a radio too, before you let
someone else's code loose on it.. 

Such as :- PuTTY, a universal Telnet and other communications (including
serial) mode too.  (ONLY get that from :-  
https://www.chiark.greenend.org.uk/~sgtatham/putty/   the offical page.)

Windows 7 at least, still supports Telnet, but you have to go and enable
it first.

Make sure you configure Gpredict correctly too, there are a few minor
"gotchas" in there for some rigs too.   See the Gpredict support site if
needed.  Make sure you have the latest version of Gpredict, not sure
what that is for Windows, you may have to figure out how to (or get
someone else to) cross compile it.  (Sorry, I can't help in that respect.)

73.

Dave G8KBV


On 22/05/18 23:58, Bill Somerville wrote:
> On 22/05/2018 22:04, Robert Benedict wrote:
>> Hello
>>    I installed hamlib-w64-3.2 and set the path on my Windows 7
>> laptop. I can run rigctl with the command
>> rigctl -m 122 -s 9600 -r com7
>> and successfully connect to my Yaesu FT-857.
>>
>> Although it appears to be correctly configured, I can not connect
>> Gpredict to the FT-857. When I check using netstat no port 4532 exists.
>>
>> If I restart rigctl including a -t 4532 option it connects to the rig
>> but still no port shows in netstat and I can't connect.
>>
>> If I restart rigctl including a -T 127.0.0.1 option it immediately
>> terminates with a
>> rigctl: unknown option --T
>> ​message.
>>
>>   I am stopped here. I don't see anything else to try.
>>
>>      Bob   KD8CGH​
>>
> Hi Bob,
>
> you should be running rigctld not rigctl if you want the Hamlib rig
> network server.
>
> 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
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

-- 
Created on and sent from a Unix like PC running and using free and open source software: