When I was programming my own
seismic receiver using the
serial Com1 port on a typical PC
I ran into a problem relating to
timing and control of the serial
communications that caused similar
symptoms.
 The way I beat it was a long time
ago and I never recorded it so
I cant tell you what I did to beat it.
I think I had to run the program under DOS
only and not windows to solve the problem
but I am not sure about that.
It is so very important to write a proper
error checking for any program
using the serial ports or you get these
funny glitches because something wrong
has happened in the conversion or
transfer of data resulting in an
erroneous data giving you those glitches.

That is everything I know about
what those glitches might be.

In my program I just check for any errors at all
and count them so that I know if that is the
problem if I get any glitches in my data.
It is very difficult to include a proper
error checking program.
I think Windows is a time sharing thing
and that will alone mess up the timing
and control of asynchronous serial communications.

Not certain about any of this
but I no longer get these glitches or errors
running under DOS in Windows 95.

Sincerely;
gmvoeth
----- Original Message ----- 
From: "Jón Frímann" 
To: 
Sent: Saturday, June 03, 2006 8:42 PM
Subject: RE: spike problem


> Hi Steve
>
> Yes, I have cordless telephone. But thease spikes happen even if the
> phone is not ringing at all.
>
> Regards.
> -- 
> Jón Frímann
> http://www.jonfr.com
> http://www.simnet.is/jonfr500/earthquake/
>
> __________________________________________________________
>
> Public Seismic Network Mailing List (PSN-L)
>
> To leave this list email PSN-L-REQUEST@.............. with
> the body of the message (first line only): unsubscribe
> See http://www.seismicnet.com/maillist.html for more information.
> 
__________________________________________________________

Public Seismic Network Mailing List (PSN-L)