Pin List Update

[Icemanau]

Something useful for pinlists concerning multifunction devices would be the ability to pass a text string to an attribute similar to how the Text Value works in the catalog database.

Most multifunction devices can be programmed to operate contacts depending on the various inputs.

These Inputs and Outputs are usually labelled by the manufacturer with some sort of identification.

This identification needs to be shown in most dwgs.

If when filling in the pinlist data, we could add a text string to be passed to a description or other attribute, we would not have to do so manually.

For example, on protection relay contacts I have set up, I have added a DESC4 attribute just for this purpose. I have to go in and fill in this attribute manually.

I can label the I/O in the pin list using *DESC but I can't transfer that label to the contact itself. Being able to do so would cut down the extra work taken by those of us who use these types of relays.

Regards Brad

[Anonymous]

I got around that by adding an extra TERM## attribute with no pin.  Using the pinlist I can push my contact or input description label into that extra TERM## attribute.  Is that what you need?

I also have "extra" attributes to hold the function number and description, but those vary so they can't be pushed from the pinlist.  In the image below the circles indicate the extra term attributes in my drawings.  I have also opened the "Show/Edit Misc." box so you can see the other attribues we used.

The second image is how the pinlist looks.  This example was for a set of current input coils, but you can see several different types of contacts.  We also added new contact types for our protection relays.  They are 4C (Current coils), 4P (Potential coils), 4I (Digital Inputs), 4O (Digital outputs), and 4T for communications ports.

[Icemanau]

I tried that but the had problems with the cross referencing using the identification and one of the terminal numbers instead of the two terminal numbers.

Eventually had to go in and remove the extra TERM attribute and replaced it with a DESC4 attribute. Now the XREF works properly without editing.

It's also why I made the suggestion on having the ability to push data from the pinlist to other attributes.

Regards Brad

[Anonymous]

I haven't ran into that. Then too I don't use the cross reference list on symbols.  Didn't see the need to add that clutter when our people aren't used to it anyway.

[t_chaws]

Hi, 

We have noted your idea and will be looking into it for our future releases! 

Thank you. Keep posting new ideas!

Best Regards, 
AutoCAD Electrical Team

[Anonymous]

This would be very helpful - exactly what I am trying to do at the moment.  I will attempt to use drathank's suggestion, but that is a workaround that labels data as something it is not...

Best case in my very-slightly-ACADE-educated mind would be to pass on the *DESC.