Pin Assignments for 2nd Terminals on Selector Switches swapped

[mark.electricaldesign]

My selector switch has 2 NO & 1 NC

My Pin List for this switch is as follows and can be defined in an SQL Table or the Component Pin-List. I've tried both.

1,13,14;1,23,24;2,31,32

When I insert the primary (top) contact, it is OK.

When I insert the 2nd NO and 3rd NC contacts the pins are reversed (See attached image)

All pins to the left should end in odd numbers eg 13,23,31 not as shown in the image

Is this a bug?

Mark

[james.mcmillanNYR6A]

How does it work if your coil pins are 13,14 and your pinlist is 1,23,24;2,31,32?

[james.mcmillanNYR6A]

It applies the pinlist to the term attribute in order 1,2,3... 

https://help.autodesk.com/view/ACAD_E/2023/ENU/?guid=GUID-1D760302-1919-43B2-9806-ED59F9F2E8EF

Does this match your block attributes?

[mark.electricaldesign]

Hi, yes I am using both IEC and custom switch symbols. The problem is not
there.
TERM01 left TERM02 right.
The terminal numbers are also reversed in the child to parent assignment
form.

So the bug is in the process of moving the pins numbers from the parent
switches properties form with the pin list, to the child to parent
assignment form.

[mark.electricaldesign]

Hi james.mcmillanNYR6A

That's how I have it configured.

I've added the Database Line entry and the Block Symbols to my original post as verification.

[rhesusminus]

I can just confirm that I've seen this behavior many times, appreciate on contractors, where the contacts have been named "2,1", "3,4" and "5,6". I haven't been able to figure out what happens, but it wasn't consistent, like it sounds like you are seeing.

Does it work that way in the demo project also?

[mark.electricaldesign]

Hi Trond,
I don't have the original demo files. Has this been escalated with Autodesk?

[james.mcmillanNYR6A]

sorry, I wasn't sat infront of CAD when I answered this, and can say mine does as yours. I think I might have got used to picking the required pair from the list (even when the same) and seems to correct itself

[rhesusminus]

I'm pretty sure it's on the "List of issues", which I believe is pretty long at the time of writing.

[ccad2509]

you mean the list

that avergaes about 5 years per bug !!!!!!!!!

bug list in the 100's

so it highy probale it wont be fixed in your lifetime