• Re: deploying patch cords

    From chrisq@syseng@gfsys.co.uk to sci.electronics.design on Sat Jul 5 14:31:12 2025
    From Newsgroup: sci.electronics.design

    On 7/3/25 15:08, Don Y wrote:
    Next, a reexamination as to whether 8P8Cs are the "right" connectors
    (just because data centers use them doesn't make them suitable for
    use in other applications!).   The telephone "plugboard" would be
    nice (no orientation problems) but may be an issue electrically.

    It looks as though a vertical panel with two rows in the same numerical
    order, with the 'outs' above their corresponding 'ins' and joined by
    very short interconnecting links in the 'normal' configuration would be
    the best arrangement.

    If by "rows" you mean "columns", I think that is right.

    Arrange the connectors to be adjacent with indicators "outboard".
    This would make it easy for sighted/unsighted folks to get a quick
    assessment of the state of everything:

    O [] [] O O [] [] O O [] [] O
    O [] [] O O [] [] O O [] [] O
    O [] [] O O [] [] O O [] [] O
    O [] [] O O [] [] O O [] [] O
    O [] [] O O [] [] O O [] [] O

    where:
       [] connection point
       O  indicator

     Below that could be a horizontal projecting shelf
    with much longer leads  tensioned with weights so that they could be
    pulled up and used to make non-standard interconnections.  When released
    they would retract neatly out of the way.

    I'm assuming any connection of that sort would be infrequent and
    temporary.  So, a single (?) overly long patch cord could do the
    trick.

    As it (and it alone) would skew across the panel, it should be easy
    to identify as an exception.  And, follow to each end.

    That was the system used in telephone manual switchboards and it worked
    very well, with the interconnections being easy to trace and no tangles
    of loose leads.

    If you could justify the design and special manufacturing costs, you
    could go one stage further and make it so that an ''out' and 'in' pair
    of sockets on one 'channel' were automatically connected to each other
    in the absence of a plug.  That would do away with the short
    interconnectors altogether.

    That may be possible.  I had planned on making "singletons" that were effectively edge-stackable as the total number (and configuration)
    would vary from system to system.  "Standardizing" on some arbitrary packaging (dimensions) would likely lead to complications at installation.

    E.g., here, I would arrange things in columns of 36.  Shorter columns
    (e.g., 24) would necessitate more columns (i.e., greater width)
    while longer columns would make them span longer reaches so the points
    at one end were less accessible than the other.

     This method was used by the BBC for their
    apparatus racks, so that only the non-standard interconnections needed
    external leads.

    If standard Post Office Gauge'B' plugs (316-type) and leads could carry
    the signals without degradation, there have been millions of standard
    ready-made jack strips with break-jacks already manufactured which will
    now be lying around as surplus stock.  (Grab them before the government
    tries to buy them all back when they realise manual telephone
    switchboards are EMP-proof.)

    They're (currently) Gbe drops.  So, there is some care needed in their physical termination.  I suspect they will be replaced with CAT6 in
    the not too distant future as Gbe is becoming "old hat".  That may
    pose some problems if the connection points are located too closely
    together
    (minimum bend radius)


    Of course, the ultimate expression of that idea is to use a 90 degree
    xy matrix, a pin at each join, to route any source to any destination.
    Add a Z axis multilayer pin to cover multi path source to destination.

    Chris
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Don Y@blockedofcourse@foo.invalid to sci.electronics.design on Sat Jul 5 09:45:10 2025
    From Newsgroup: sci.electronics.design

    On 7/5/2025 6:31 AM, chrisq wrote:
    Of course, the ultimate expression of that idea is to use a 90 degree
    xy matrix, a pin at each join, to route any source to any destination.
    Add a Z axis multilayer pin to cover multi path source to destination.

    The normal (and nominal) routing is (or can be) to the adjacent
    destination. So, it makes sense to optimize that. The exception
    can be... exceptional (and, likely, only needed to provide
    temporary relief in the event of an equipment failure).

    The user *wants* to be able to sort out where things are routed.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From chrisq@syseng@gfsys.co.uk to sci.electronics.design on Sat Jul 5 18:43:55 2025
    From Newsgroup: sci.electronics.design

    On 7/5/25 17:45, Don Y wrote:
    On 7/5/2025 6:31 AM, chrisq wrote:
    Of course, the ultimate expression of that idea is to use a 90 degree
    xy matrix, a pin at each join, to route any source to any destination.
    Add a Z axis multilayer pin to cover multi path source to destination.

    The normal (and nominal) routing is (or can be) to the adjacent destination.  So, it makes sense to optimize that.  The exception
    can be... exceptional (and, likely, only needed to provide
    temporary relief in the event of an equipment failure).

    The user *wants* to be able to sort out where things are routed.

    Not applicable to all, but have used the small 10x10 x-y matrix
    pin boards in the past to patch comms lines, eg: null modem
    or pin to pin, or combination of such. Visually obvious which pin
    goes to what as well. One of those glued between a pair of 25
    pin D, in one example.

    Chris

    .
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Don Y@blockedofcourse@foo.invalid to sci.electronics.design on Sat Jul 5 11:15:04 2025
    From Newsgroup: sci.electronics.design

    On 7/5/2025 10:43 AM, chrisq wrote:
    On 7/5/25 17:45, Don Y wrote:
    On 7/5/2025 6:31 AM, chrisq wrote:
    Of course, the ultimate expression of that idea is to use a 90 degree
    xy matrix, a pin at each join, to route any source to any destination.
    Add a Z axis multilayer pin to cover multi path source to destination.

    The normal (and nominal) routing is (or can be) to the adjacent
    destination.  So, it makes sense to optimize that.  The exception
    can be... exceptional (and, likely, only needed to provide
    temporary relief in the event of an equipment failure).

    The user *wants* to be able to sort out where things are routed.

    Not applicable to all, but have used the small 10x10 x-y matrix
    pin boards in the past to patch comms lines, eg: null modem
    or pin to pin, or combination of such. Visually obvious which pin
    goes to what as well. One of those glued between a pair of 25
    pin D, in one example.

    [My solution for EIA232-ish "conversions" is to build small
    (2"x2") adapters that permanently hardwire a connector (of
    a specific gender) on one end to another connector (of a
    possibly different gender) on the other end. Then, slap a
    label on the assembly: "Null Modem", "Null Terminal", "Male
    Gender Swap", "Female Gender Swap", "APC UPS", "PLIP", etc.
    The thinking being that if you have to sort out how to connect
    X and Y *today*, you will likely want to connect them, again,
    tomorrow. So, make a specific adapter, document it, and be
    done with it. I only use my "patch board" to sort out how
    to make that first adapter.]

    Here, "visually obvious" is the problem. I need a solution of
    which someone who is blind, physically disabled, etc. can make
    effective use.

    You (likely) can GLANCE at a network switch and see if a
    node is inactive (if you assume all would be active).
    And, can see if there is a network cable plugged into
    that port.

    Close your eyes and do it. Or, confine yourself to a wheelchair
    that limits your reach or the ease with which you can "navigate"
    a panel with hundreds of connections.

    If you were told to swap the cables at connections X and Y,
    would you be able to do it -- correctly? (no peeking!)
    How do you locate X and Y? Hold onto the X cable while
    fiddling for the Y?
    --- Synchronet 3.21a-Linux NewsLink 1.2