The Trials and Tribulations of Setting Up a Remote Station

I was finally able to set-up a client-server arrangement for N4PY such that the N4PY control software is operating at the control end computer rather than the remote desktop option of taking over a remote computer on the internet.  The problem with remote desktop is latency - perhaps 25 to 50 milliseconds.  It may not seem like a lot but the shorter the latency the better.  I was able to test all the functionality from within the network:

(1) Functionality of the Griffin Powermate Knob on the client (control) computer
(2) Functionality and speed tests on tuning the VFO and sending CW over the network.

Now I was  eager to exercise this option from outside the LAN.  I fired up the LogmeIn client and found that the remote desktop is offline.   What happened?  Did the computer sleep?  The only way to find out is to go home.  Now to figure out a way to wake the computer from the internet - a concept called Wake on LAN (Local Area Network).

Upon returning home - the computer was in sleep mode.  I set up Windows device manager to wake the computer up via the Local Network or LAN - we will see how that works

In the video below I demo using the Griffin Powermate as a tuning knob.  The small Microsoft Surface tablet is the Client computer on the control end.  There is no need for a remote desktop connection. There is a need still for audio voice over IP (VOIP) through Skype.