1

Closed

Multiple Socket of the same Types issue.

description

I've created a module that requires two Y socket.

The designer didn't draw it properly and it is not possible to drag the connection in the deisgner.
        <Socket Left="10" Top="45" Orientation="90" ConstructorOrder="1" TypesLabel="Y">
          <Types>
            <Type>Y</Type>            
          </Types>
          <Pins>            
            <Pin Shared="false">4</Pin>
            <Pin Shared="false">5</Pin>
            <Pin Shared="false">6</Pin>
            <Pin Shared="false">7</Pin>
            <Pin Shared="false">8</Pin>
            <Pin Shared="false">9</Pin>
          </Pins>
        </Socket>
        
        <Socket Left="30" Top="45" Orientation="90" ConstructorOrder="2" TypesLabel="Y">
          <Types>
            <Type>Y</Type>
          </Types>
          <Pins>
            <Pin Shared="false">3</Pin>
            <Pin Shared="false">4</Pin>
            <Pin Shared="false">5</Pin>
            <Pin Shared="false">6</Pin>
            <Pin Shared="false">7</Pin>
          </Pins>
        </Socket>

      </Sockets>
For example if i ask for a socket X and an Y it works!
        <!-- This example socket is compatible with socket types XY which has electrical connections to pins 3 and 4 -->
        <Socket Left="10" Top="45" Orientation="90" ConstructorOrder="1" TypesLabel="X">
          <Types>
            <Type>X</Type>            
          </Types>
          <Pins>            
            <Pin Shared="false">4</Pin>
            <Pin Shared="false">5</Pin>
            <Pin Shared="false">6</Pin>
            <Pin Shared="false">7</Pin>
            <Pin Shared="false">8</Pin>
            <Pin Shared="false">9</Pin>
          </Pins>
        </Socket>
        
        <Socket Left="30" Top="45" Orientation="90" ConstructorOrder="2" TypesLabel="Y">
          <Types>
            <Type>Y</Type>
          </Types>
          <Pins>
            <Pin Shared="false">3</Pin>
            <Pin Shared="false">4</Pin>
            <Pin Shared="false">5</Pin>
            <Pin Shared="false">6</Pin>
            <Pin Shared="false">7</Pin>
          </Pins>
        </Socket>
Closed Nov 13, 2015 at 3:29 PM by JanKuceraMSFT
Fixed in 2.44.1100.

comments

SandeX wrote Mar 12, 2015 at 9:58 PM

I figured out that the "TypesLabel" attribute must be unique in the module.

Ok good, if it was documented properly would be better.

Said that, system didn't throw exceptions or notify the user of this error in the module.

Would be nice to add this kind of notification.

JanKucera wrote Mar 12, 2015 at 10:39 PM

Your observation is correct, the TypesLabel is currently the only way how to reference the individual sockets in the definition and while you probably would like to distinguish between your sockets on your board and in your documentation too, I agree it could have been mentioned at least in the schema.

wrote Nov 13, 2015 at 3:29 PM