PSN-L Email List Message

Subject: Re: WinSDR Wireless Interference?
From: gpayton@.............
Date: Mon, 12 Sep 2011 17:40:20 -0500


By =E2=80=9Cloosing trace=E2=80=9D, do you mean totally blank screen or =
a line drawn without the seismometer wiggles?

I ask because I had a connection problem arise between my sensor and =
Larry=E2=80=99s A/D box.  For convenience, I had added right-angle =
adapters at the box connectors.  One adapter frequently lost the =
connection from the sensor and all that was displayed on the computer =
was a straight green line.  I removed the adapter and it worked fine.=20

I too am using an old Dell running XP, but do have it connected to the =
LAN.  I know that this probably does not answer your problem, but I =
doubt seriously that it is frequency / antenna problem.

Regards,
Jerry Payton

-------------------------------------------------------------------------=
-------


From: Robert Thomasson=20
Sent: Monday, September 12, 2011 5:01 PM
To: psnlist@.................
Subject: WinSDR Wireless Interference?


I have had some trouble keeping my WinSDR up and running.  It frequently =
shows just a blank screen, with all helicord traces gone.  Just as if =
I'd just opened the software without a seismometer connected to the =
computer.  The computer is an older Dell with a 2 GHz processor and 512 =
Mb RAM, running WinXP with I think service pack 3.

What is interesting about this phenomenon is that there is a wireless =
router in the house (the seismo server has no wireless capability and is =
not connected to the network) and WinSDR will work fine until someone =
sits down at another computer and the wireless network starts exchanging =
traffic.  Then the WinSDR screen loses the displayed data and goes =
blank.

Is it possible that somehow the USB cable from the seismometer to the =
seismo server computer  is acting as an antenna and picking up enough =
interference from the 2++GHz wireless LAN system to crash WinSDR?  =
WinSDR does not actually crash, it just loses the data traces, which =
disappear.  My next step is to dig out some old books and see if I can =
figure out what length the seismo cable would have to be to resonate at =
the wireless LAN frequency.   But I think it would have to be very =
short?

This is another unexpected educational aspect of this hobby!   Just =
wondering if anyone else has experienced this issue? =20

Thanks,

Bob





By =E2=80=9Cloosing trace=E2=80=9D, do you mean totally blank = screen or a line drawn=20 without the seismometer wiggles?
 
I ask because I had a connection problem arise between my sensor = and=20 Larry=E2=80=99s A/D box.  For convenience, I had added right-angle = adapters at the=20 box connectors.  One adapter frequently lost the connection from = the sensor=20 and all that was displayed on the computer was a straight green = line.  I=20 removed the adapter and it worked fine.
 
I too am using an old Dell running XP, but do have it connected to = the=20 LAN.  I know that this probably does not answer your problem, but I = doubt=20 seriously that it is frequency / antenna problem.
 
Regards,
Jerry Payton

 
Sent: Monday, September 12, 2011 5:01 PM
Subject: WinSDR Wireless Interference?
 
 
I have had some trouble keeping my WinSDR up = and=20 running.  It frequently shows just a blank screen, with all = helicord traces=20 gone.  Just as if I'd just opened the software without a = seismometer=20 connected to the computer.  The computer is an older Dell with a 2 = GHz=20 processor and 512 Mb RAM, running WinXP with I think service pack = 3.

What=20 is interesting about this phenomenon is that there is a wireless router = in the=20 house (the seismo server has no wireless capability and is not connected = to the=20 network) and WinSDR will work fine until someone sits down at another = computer=20 and the wireless network starts exchanging traffic.  Then the = WinSDR screen=20 loses the displayed data and goes blank.

Is it possible that = somehow the=20 USB cable from the seismometer to the seismo server computer  is = acting as=20 an antenna and picking up enough interference from the 2++GHz wireless = LAN=20 system to crash WinSDR?  WinSDR does not actually crash, it just = loses the=20 data traces, which disappear.  My next step is to dig out some old = books=20 and see if I can figure out what length the seismo cable would have to = be to=20 resonate at the wireless LAN frequency.   But I think it would = have to=20 be very short?

This is another unexpected educational aspect of = this=20 hobby!   Just wondering if anyone else has experienced this=20 issue? 

Thanks,

Bob


 

[ Top ] [ Back ] [ Home Page ]