Re: [Hamlib-developer] rpcrig (howto)
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: Stephane F. <f4...@fr...> - 2002-06-24 21:43:30
|
On Sun, Jun 16, 2002, Dale E. Edmons wrote: > Just a quick question. My laptop is connected to my rig and is slower > than my main computer. The two computers are connected via > ethernet and allows me to do anything on one the other won't do. > > I believe rpcrig is for control via this type of link. It'd be > convienient > (and really cool) if I could run rigctl remotely via rpcrig. I'm sure If it can be cool, it's a job for ........ Hamlib! hi. > that the development status is not what it wants to be but I'd give > it a go if someone would give the clues I need to run this way. if > it is 100% broken, I won't worry about and just copy stuff over and > use only the laptop. Much has to be done this way regardless. The rpc stuff should work, but so far it's undocumented. Here's a quick start. If you want to play with it and write a mini HOWTO, you're more than welcome! On your laptop, start "rpc.rigd -m 214 -vvvvvv -r /dev/ttySx" Then on your main computer, start "rigctl -m 1901 -vvvvvv -r <laptopname>" You should be able to substitute <laptopname> with the IP address of your laptop. Note that if you don't specify any '-r' option to rigctl, the client will use the RPC server on the localhost. This might come handy if several applications want to share the rig. Just imagine having xlog, grig and your best psk program running at the same time, sharing seamlessly the ressource. Altough rpc.rigd is generally installed in /usr/sbin, it should not require root priviledges. For more info, see man pages rpc.rigd(8) and rigctl(1). I hope this will get you on track, and let us know how it works for you. Cheers, Stephane |