[drats_users] Test patterns

[Arnold Harding]

>
> I hear ya.  In telco, there are a number of pre-defined test 
> patterns
> that start/stop can easily be found via mathmatical functions... so 
> if
> one "sequence" is blown, the whole sequence is marked "bad", and the
> next "start of frame" sequence is looked for.
>
> <http://www.telect.com/downloads/ResourceCenter/Copper%20Connectivity%20Patch%20Panels%20Systems/T1-DS1-E1%20Installation%20and%20General%20Usage/DS1%20Digital%20Test%20Patterns.pdf>
>
> Problem is, at 1200 bps... most of these would take a long time...
>

Rather than spending a bunch of time trying to find out if a path 
might work with a bunch of test patterns, wouldn't it be more 
efficient to just try sending the file?  Sure, we can determine what 
bits got blown if we want, but what's the point.  If we do a medium 
size ping and reply (my request), and get a decent reply, then go for 
it.  If the medium ping doesn't work that well, then try something 
else.  I think that's the point of Pipeline parameters; to do the 
retries to get the message through.  The only way you can ever expect 
to get a perfect message through every time is to have a direct coax 
or fiber connection from end to end.  Rarely will you ever have a 
perfect connection.  If you are really trying to get a message 
through, and spend an excessive amount of time testing everything, 
then the message will never go, but you will annoy everyone else 
wanting the frequency.  (Just s--- and get off the pot.)

My 2 cents.

Arnold
KQ6DI