[LOGic] More on remote operation
K0DAN
k0dan at comcast.net
Thu Dec 4 12:17:52 EST 2008
Hi Dan...
The plan here is to run XP Pro on the remote PC, with as little extra
hardware/software as possible.
The remote station will be in an outbuilding, about 150' from the hamshack
(in order to reduce feedline loss for a VHF/UHF station). The planned
interconnect is indeed wireless, so the issue of having to revive wireless
connections is a concern.
I run a little WIFI in and around the house, and it seems to work OK but I
prefer CAT5 connections. Have never had trouble with losing WIFI connections
around the home, however when I travel, I find WIFI to be very
intermittent...ie the connections come and go, even if the signal strenth is
goo. I've never figured that out...unless it's an interference issue and the
hardware hops frequencies? Lots of variables in a WIFI cloud.
What have you done to beef up the reliability of your WIFI connections?
Other than current hardware, and plenty of signal strength, I don't know
what else can be done?
In my case, should I need to hot/cold/warm reboot the remote PC & station, I
can find software and the previously-mentioned X-10 remotes to do that job.
And hopefully reboot is a measure of last resort.
I too have avoided Vitsa, and hope to continue to, but I think the days of
being able to buy XP on new PC's is coming to a close.
I hope to avoid buying a new PC for the remote station, but have not decided
on the hardware yet. Am waiting to find some kind of cabinet in which to
house the radio & computer equipment. I used to have a bunch of Motorola
Compa cabinets, which would have been ideal for this project, but they're
all gone. The outbuilding doesn't have heat or air (and is not the cleanest
environment, including insects and an occasional rodent) so I need to find a
cabinet with doors to at shelter the hardware to some degree. And a PC which
is small, well filtered and ventilated, and which can withstand summer heat
and winter cold.
73
Dan
K0DAN
----- Original Message -----
From: "Dan Bookwalter" <n8dcj at yahoo.com>
To: "K0DAN" <k0dan at comcast.net>; "LOGic is open to all radio amateurs for
discussion of LOGic logging program" <logic at mailman.qth.net>;
<k6jw at scdxc.org>
Sent: Monday, December 01, 2008 8:40 PM
Subject: Re: [LOGic] More on remote operation
> Dan
>
> As i have mentioned i have had many PC's (Windows OS) running for long
> periods of time , long periods of time i mean > 6 months , a couple for
> much longer than a year with no reboots. I must mention that the OS's were
> Win 2K Pro and XP Pro , the one area that i have had trouble with is when
> they run with wireless Ethernet cards , in this case you either have to
> reboot often or do a repair of the connection. I assume if you are running
> remotely that more than likely you are not running wireless.... although i
> can see where that could happen , if that is the case there are ways to
> reset the wireless Ethernet connection pragmatically. I do not believe i
> have ever had a situation where I had to do a "cold" reboot to
> re-establish connections to peripherals in the kind that would be used for
> a remote site. I will admit that there have been times when i have "warm"
> rebooted just because i thought i should , you know it seems fashionable
> to do it etc.... even
> when i was running a cluster under Linux i did the same thing , why , i
> don't know ....
>
> I think that with the modern Windows OS's you can do it , (meaning W2K Pro
> and XP Pro) , i don't think i would get near Vista with remote stuff ,
> although that is just a feeling , since i have no experience with Vista
> and MS is pushing Windows 7 so hard as a replacement i feel that Vista is
> the Windows ME of late.
>
> There are also many ways to do a soft/warm reboot remotely that i wouldn't
> hesitate to do that either , although on a remote machine i would limit
> the amount of non-essential (to remote operation) software that was
> installed , put a good HARDWARE firewall in front of it and remote desktop
> (on a non standard port) into your machine and you have total control , i
> do it every day between work->work , home->work and work->home machines.
>
> i am sure i missed some of your points/questions with my rambling , if so
> ask me again and i will give you my experiences....
>
> Dan N8DCJ
>
>
>
>
> ----- Original Message ----
> From: K0DAN <k0dan at comcast.net>
> To: LOGic is open to all radio amateurs for discussion of LOGic logging
> program <logic at mailman.qth.net>; k6jw at scdxc.org
> Cc: n8dcj at yahoo.com
> Sent: Monday, December 1, 2008 8:28:43 PM
> Subject: Re: [LOGic] More on remote operation
>
> Dan:
>
> Do you ever need to warm/cold boot the PC's (and peripherals), even if
> momentarily, to break a lockup, reestablish network connections, etc.,
> etc.? Does coldboot actually remove power from the secondaries of the
> power supply?
>
> I'm not trying to give you a hard time here, I'm just trying to explore
> how much "exercise" PC's running 24x7 (especially remote PC's) require.
> And am not so much exporing fire risk (altho that's always worth some
> study) as I am just lockups, debugging, and other voodoo associated with
> networking.
>
> 73
>
> Dan
> K0DAN
>
> ----- Original Message ----- From: "Dan Bookwalter" <n8dcj at yahoo.com>
> To: <k6jw at scdxc.org>
> Cc: <logic at mailman.qth.net>
> Sent: Monday, December 01, 2008 3:36 PM
> Subject: Re: [LOGic] More on remote operation
>
>
>> at home I have 2 pc's and the rig that run 24/7 and have for years.... at
>> work I have 18 or so PC's in the lab that pretty much run 24/7 and all
>> through the plant there are probably 4-500 machines always on and we have
>> never had a fire.... the biggest problem we have is with the few pc's
>> that do get shut off , the hard drives do not like to sit not spinning
>> for very long...
>>
>> just my .02 worth
>>
>> Dan N8DCJ
>>
>> J.A. Wolf, MD, K6JW wrote:
>>> Well...maybe I am being overly cautious. The computer that leaked its
>>> smoke (you know: if the smoke leaks out, the machine won't work anymore)
>>> was new and hadn't been running more than a couple of hours when it
>>> happened. It's true that I've never seen anything like it in any
>>> "run-in" computer I've used over the past 25 years. Maybe I should
>>> reconsider...
>>> Thanks.
>>> --Jeff, K6JW
>>> ----- Original Message ----- From: "Mel Martin" <ve2dc at videotron.ca>
>>> To: "LOGic is open to all radio amateurs for discussion of LOGic logging
>>> program" <logic at mailman.qth.net>
>>> Sent: Monday, December 01, 2008 12:27
>>> Subject: Re: [LOGic] More on remote operation
>>>> Well that's unusual. I have been responsible for literally thousands of
>>>> computers over the years, always left on, and I have never seen or even
>>>> heard of one catching fire. I have seen them fail with some pretty
>>>> funky smells, but never actually catch fire. I know such things can
>>>> happen... but most of the fires I have heard about are to do with
>>>> laptops and their batteries. Perhaps you are being overly cautious. A
>>>> smoke detector coupled to a breaker might be a solution... such things
>>>> must exist.
>>>>
>>>> Regarding security, my caution stands... when you power up after a long
>>>> interval your computer is vulnerable. It takes time for all the updates
>>>> to be done. The biggest risk is OS exploits which need to be patched as
>>>> soon as fixes are available.
>>>>
>>>> J.A. Wolf, MD, K6JW wrote:
>>>>> Hi, Mel!
>>>>> The simple answer to your question is that I once left a computer
>>>>> running that suddenly developed a short in the power supply and caught
>>>>> fire. Fortunately, I was in the house and smelled the smoke before the
>>>>> fire spread. It's made me a bit nervous about leaving town with a
>>>>> computer running. Of course, a fire could happen anytime the computer
>>>>> is running, but it seems to me that the risk would be reduced if it
>>>>> were only running when I was using it.
>>>>> Anti-virus updating is automatic, so that's not really an issue. The
>>>>> UPS is well advised.
>>>>> 73,
>>>>> Jeff, K6JW
>>>>>
>>>>>
>>>>> ----- Original Message ----- From: "Mel Martin" <ve2dc at videotron.ca>
>>>>> To: "LOGic is open to all radio amateurs for discussion of LOGic
>>>>> logging program" <logic at mailman.qth.net>
>>>>> Sent: Monday, December 01, 2008 10:51
>>>>> Subject: Re: [LOGic] More on remote operation
>>>>>
>>>>>
>>>>>> Why would you not leave your computer running? This is the proper
>>>>>> course of action... Shutting down computers on the Internet for a
>>>>>> long period of time means that when you wake them up their OS
>>>>>> patches, virus signatures and such are out of date. Modern computers
>>>>>> can be configured to go into a very low state of activity after a
>>>>>> prolonged period of activity. I would also strongly recommend a UPS
>>>>>> for your computer and router.
>>>>>>
>>>>>> Mel, VE2DC
>>>>>>
>>>>>> J.A. Wolf, MD, K6JW wrote:
>>>>>>> Glad someone opened the general topic on the reflector. I'm using
>>>>>>> TRX-Manager with LOGic8 for rig control with a Mark-V. CW is
>>>>>>> accomplished via parallel port, and sound/voice via Skype. Digital
>>>>>>> modes go through a RIGblaster. Remote access is through logmein.com.
>>>>>>> I've been researching ways to turn on the computer and rig remotely
>>>>>>> but haven't yet settled on a final scheme. There are several
>>>>>>> possibilities and commercially available devices to accomplish this.
>>>>>>> Some work strictly via the internet and some use telephone
>>>>>>> activation.
>>>>>>> Once the computer is booted, it can be used via USB porting very
>>>>>>> easily to trigger relays that will turn on the radio and SteppIR
>>>>>>> controller. The real question is that of the best way to turn on the
>>>>>>> computer. Does anyone on the reflector have any recommendations
>>>>>>> based upon actual experience with the commercially available circuit
>>>>>>> boards that will do this? I hate to go away and leave everything
>>>>>>> running for a week or two at a time with no one at home.
>>>>>>> --Jeff, K6JW
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message ----- From: "N6FM Ben" <n6fm at oregonfast.net>
>>>>>>> To: "'LOGic is open to all radio amateurs for discussion of LOGic
>>>>>>> logging program'" <logic at mailman.qth.net>
>>>>>>> Sent: Sunday, November 30, 2008 13:23
>>>>>>> Subject: RE: [LOGic] LOGic - Remote control and port sharing
>>>>>>>
>>>>>>>
>>>>>>>> Well, then I would suggest a remote desktop application like VNC
>>>>>>>> from which
>>>>>>>> you can shutdown ARCP and start TRX, or merely disconnect the ports
>>>>>>>> from
>>>>>>>> each (they do that) without shutting one down.
>>>>>>>>
>>>>>>>> What specifically do you wish the program to do??
>>>>>>>>
>>>>>>>> Ben
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: logic-bounces at mailman.qth.net
>>>>>>>> [mailto:logic-bounces at mailman.qth.net]
>>>>>>>> On Behalf Of K0DAN
>>>>>>>> Sent: Sunday, November 30, 2008 12:36 PM
>>>>>>>> To: LOGic is open to all radio amateurs for discussion of LOGic
>>>>>>>> logging
>>>>>>>> program
>>>>>>>> Subject: Re: [LOGic] LOGic - Remote control and port sharing
>>>>>>>>
>>>>>>>> Thanks Ben, I have TRX MGR but unfortunately it doesn't do all that
>>>>>>>> ARCP2000 does, nor all that I need.
>>>>>>>>
>>>>>>>> 73
>>>>>>>>
>>>>>>>> Dan
>>>>>>>> K0DAN
>>>>>>>>
>>>>>>>> ----- Original Message ----- From: "N6FM Ben" <n6fm at oregonfast.net>
>>>>>>>> To: "'LOGic is open to all radio amateurs for discussion of LOGic
>>>>>>>> logging
>>>>>>>> program'" <logic at mailman.qth.net>
>>>>>>>> Sent: Sunday, November 30, 2008 2:30 PM
>>>>>>>> Subject: RE: [LOGic] LOGic - Remote control and port sharing
>>>>>>>>
>>>>>>>>
>>>>>>>>> The TS-2000 only has one serial port. You can't control with two
>>>>>>>>> programs
>>>>>>>>> at
>>>>>>>>> the same time.
>>>>>>>>>
>>>>>>>>> I would suggest obtaining TRX-Manager' use that instead of ARCP.
>>>>>>>>> It has a
>>>>>>>>> great number of features to control the 2000 (since the author
>>>>>>>>> owns one)
>>>>>>>>> and
>>>>>>>>> can be linked to Logic. That way, setting the rig in Logic will
>>>>>>>>> cause TRX
>>>>>>>>> to
>>>>>>>>> respond. Only one serial port is required.
>>>>>>>>>
>>>>>>>>> Ben
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: logic-bounces at mailman.qth.net
>>>>>>>>> [mailto:logic-bounces at mailman.qth.net]
>>>>>>>>> On Behalf Of K0DAN
>>>>>>>>> Sent: Sunday, November 30, 2008 9:55 AM
>>>>>>>>> To: LOGic is open to all radio amateurs for discussion of LOGic
>>>>>>>>> logging
>>>>>>>>> program
>>>>>>>>> Subject: [LOGic] LOGic - Remote control and port sharing
>>>>>>>>>
>>>>>>>>> I have two rigs interfaced to LOGIC:
>>>>>>>>> a) An FT1000MP using a derived USB-Serial port
>>>>>>>>> b) A TS2000 using a "real" serial port
>>>>>>>>> Right now every thing is in the hamshack, local control. All this
>>>>>>>>> works
>>>>>>>>> fine.
>>>>>>>>>
>>>>>>>>> I'm in the process of remoting the TS2000 via WIFI.
>>>>>>>>> I'm using Kenwood's ARCP2000 control software, which requires a
>>>>>>>>> serial
>>>>>>>>> port
>>>>>>>>> to interface the rig and PC (this steals the serial port from
>>>>>>>>> LOGIC).
>>>>>>>>>
>>>>>>>>> Need another serial port so the TS2000 can talk to LOGIC while
>>>>>>>>> also
>>>>>>>>> talking
>>>>>>>>> to the ARCP2000 software.
>>>>>>>>>
>>>>>>>>> I searched the LOGIC archives but couldn't find any discussions on
>>>>>>>>> how to
>>>>>>>>> share serial ports. Or add a USB hub plus more derived USB/Serial
>>>>>>>>> ports?
>>>>>>>>>
>>>>>>>>> Any suggestions for "best way" to let the rig control software and
>>>>>>>>> LOGIC
>>>>>>>>> talk to the TS2000 simultaneously? ("Best way" =
>>>>>>>>> cheap/simple/inexpensive/reliable!)
>>>>>>>>>
>>>>>>>>> Tnx
>>>>>>>>> es 73
>>>>>>>>> Dan
>>>>>>>>> K0DAN
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> LOGic mailing list
>>>>>>>>> LOGic at mailman.qth.net
>>>>>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> LOGic mailing list
>>>>>>>>> LOGic at mailman.qth.net
>>>>>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> LOGic mailing list
>>>>>>>> LOGic at mailman.qth.net
>>>>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> LOGic mailing list
>>>>>>>> LOGic at mailman.qth.net
>>>>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> LOGic mailing list
>>>>>>> LOGic at mailman.qth.net
>>>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>>>
>>>>>>
>>>>>> -- Mel, VE2DC
>>>>>> _______________________________________________
>>>>>> LOGic mailing list
>>>>>> LOGic at mailman.qth.net
>>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> LOGic mailing list
>>>>> LOGic at mailman.qth.net
>>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>>
>>>>
>>>> -- Mel, VE2DC
>>>> _______________________________________________
>>>> LOGic mailing list
>>>> LOGic at mailman.qth.net
>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>
>>> _______________________________________________
>>> LOGic mailing list
>>> LOGic at mailman.qth.net
>>> http://mailman.qth.net/mailman/listinfo/logic
>>
>>
>>
>>
>> _______________________________________________
>> LOGic mailing list
>> LOGic at mailman.qth.net
>> http://mailman.qth.net/mailman/listinfo/logic
>>
>
>
>
>
More information about the LOGic
mailing list