Allow to define cables in MVR

[petrvanekrobe]

Specific follow up on cables, mentioned in #288

Requirements: allow to exchange information about cables, connecting Connections in MVR.

MVR object: Inventory Item - Cable, it would be similar to FocusPoints. Cable with:

• CrossSection
• Length
• Cable Type
• Each cable connects to the respective MVR Connection of connected devices (detailed specification needed)

Defining cables as GDTF?

• would allow to build a library of inventory items
• would have to be defined for every cable

[petrvanekrobe]

• Add Cable to MVR Table 18 ChildList next to FocusPoint, Fixture, Support...
• Define a new Cable node, probably similar to FocusPoint, but with cable-specific attributes: uuid, name, cableType, signalType, length, crossSection.
• CableEnds: Define CableEnd as linking points
• Linking:
  • 1. CableEnds:
       object = UUID of the connected MVR object.
       geometry = node link to that object’s GDTF WiringObject.
       This reuses/doubles the existing MVR/GDTF connection model
  • Keep existing MVR Connections as logical object-to-object connectivity. A Cable should be the physical realization of that connection. If both are exported, they must agree. Older software can still read Connections; newer software can read actual cables.
  • need to add every cable for every Connection
  • 2. Or, add cable uuid to connection? (do not know where each end is connected)
• PinPatch?
  • Cable-local PinPatch for individual pin mapping, reusing GDTFs definition?
• Impedance?
• 3way cables - length? Pinning?

  <Cable
    uuid="7C6B12E5-0AC9-45B2-99EA-5C7C9D9F5A10"
    name="Power 25m #14"
    cableType="H07RN-F 3G2.5"
    signalType="Power"
    length="25.0"
    crossSection="2.5">

    <CableEnds>
      <CableEnd name="A"
        object="11111111-1111-1111-1111-111111111111"
        geometry="PowerOut_1"
        connectorType="16A-CEE"/>

      <CableEnd name="B"
        object="22222222-2222-2222-2222-222222222222"
        geometry="PowerIn"
        connectorType="16A-CEE"/>
    </CableEnds>

    <PinPatch>
      <Pin fromEnd="A" fromPin="1" toEnd="B" toPin="1"/>
      <Pin fromEnd="A" fromPin="2" toEnd="B" toPin="2"/>
      <Pin fromEnd="A" fromPin="3" toEnd="B" toPin="3"/>
    </PinPatch>
  </Cable>

@kevinrma

[klinzey]

I checked and we consider a cable as only having 2 connectors, 1 start and 1 end. We use a distributor to breakout a single cable to multiple connectors.

[petrvanekrobe]

Cable = physical realization of a connection between two GDTF WiringObjects, defined in ChildList.

Cable has one Start and one End.

Define Cable:

Cable Attributes:

• uuid - uuid
• name string
• cableType - string
• length - float - m

Cable children - Signal

Signal Attributes:

• type - GDTF WiringObject SignalType types
• crossSection - float m
• impedance - float ohm

<Cable
  uuid="7C6B12E5-0AC9-45B2-99EA-5C7C9D9F5A10"
  name="Power 25m #14"
  cableType="H07RN-F 3G2.5"
  length="25.0">

  <Signal
    type="Power"
    crossSection="2.5"/>
</Cable>

<Cable
  uuid="..."
  name="Hybrid FOH"
  cableType="Hybrid"
  length="30.0">

  <Signal
    type="Power"
    crossSection="2.5"/>

  <Signal
    type="DMX512"
    impedance="50"/>
</Cable>

Extend the Connection Node Attributes and add Cable UUID - link to the Cable.

<Connection
  own="DMXOut"
  other="DMXIn"
  toObject="..."
  cable="hybrid-cable-uuid"/>