Date: Mon, 09 Jun 2003 08:47:13 -0700 From: Karl Cunningham <karlc@..........> Subject: System Configuration
This is probably a question for Larry, but thought it might have interest
for the gang.
For a while I've been wanting to get away from running the serial cable
between SDR server and Winsdr. It's not that I have anything against
serial cables, but I have an ethernet cable running over the same path and
I'd like to use it for the SDR data connection too. Let me propose a
system configuration and see what you think...
1. Computer A is located near the seismometer, running the A/D card and
SDR Server, powered from an UPS.
2. Computer B, sitting next to Computer A running WinSDR, powered from the
same UPS as Computer A. A short serial cable connects the two. WinSDR is
set to act as a server over TCP/IP. This comptuer has a moderate-size hard
disk and only keeps a few days of record files.
3. Computer C, sitting in the house is running WinSDR, which is configured
as a client to receive data from Computer B. This comptuer has a big hard
disk for a month or two of record files and serves as my main WinSDR
display. It also serves replay requests to WinQuake.
4. Router/Firewall forwards TCP/IP request from WinSDR clients to comptuer
B.
Larry, I think you mentioned something a while back about a future
enhancement where a WinSDR system operating as a client could make requests
to a WinSDR server to fill in gaps in its record files. Did I understand
that correctly? If so, is that still a possibility? If it is, Comptuer C
wouldn't have to have an UPS since it could "catch up" after a power
failure.
What do you think?
Thanks.
Karl Cunningham
.