Hello Joe and everyone, Recently I have been experimenting with the new C implementation of the WSPR decoder on a Raspberry Pi SBC and am getting excellent results in terms of stability and performance. I am now implementing transmitting the code for transmission and for monitoring/controlling the setup remotely. On this regard, I have been thinking that the JT modes, in general, are excellent for remote operations. I believe it would be a very useful and welcome feature if wsjt-x could support remote operations. This could be done in a number of ways, but I believe that one elegant way would be detaching the UI from the control, I/O, and codecs functions.
In a local station setup, the UI coould start a daemon that performs all the current functions and communicate with the daemon using TCP/IP sockets. On a remote station the daemon could be automatically started and a UI could connect to the remote station from anywhere in the world where an Internet access is available. Initially the setup could be implemented for a single user and later multi-user could be considered. For security reasons, some sort of authentication would be required for remote access. A shared key could be an option. Since we are about to start refactoring the wsjt-x code, I thought it would be a good time to present this proposal. Any thoughts? 73, Edson PY2SDR --- - We humans have the capability to do amazing things if we work together. - Nós seres humanos temos a capacidade de fazer coisas incríveis se trabalharmos juntos.
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
