the user point. Well perhaps we can sway that a bit.
>
> The first point is "Why have a connector"

1) It's not known until install time what sort of thing is being plugged into
the connector. The connector is a standard i/o control for any of several sensor
s/
controllers.
2) It would be extremely inconvenient to install the sensors if they were perman
ently attached
3) The unit gets removed repeatedly during the install/setup process. Each occas
ion would
mean re-running 6 cables.

> The second is "Who will access the connector"

End user, who is completely untrained.

> The last point "How many times do you expect the connection to be made"

far less than 100

>
> Of course that is only a short list and many other points are to always be
> considered.

Yes - I guess "will the cable be tugged?" should be on there - obviously it's cr
azy
to smt mount a connector whose cable is attached to a person walking around.


> The connector mounted on the hard disk is a classic example, How many times
> is it removed during normal service? What sort of environmental conditions
> does it incur? Perhaps it is in one of the best locations.

I used to telecommute 3 days, come in 2, and solved the "it's on the other compu
ter"
problem by having an external hard drive (this on a mac) that traveled with me
twice a day between SF and Cupertino.  Wonder what the design expectancy is for
DB connectors? They were originally a modem to terminal connection.


--
Anniepoo
Need loco motors?
http://www.idiom.com/~anniepoo/depot/motors.html