Toggle NO/NC Problem

[hkim]

There is a problem with the contact toggle command for a part that has form-C contacts in the pinlist. For example, when the first NO contact of a part that has two form-C contacts in the pinlist is inserted, Acade correctly assigns the correct pin numbers. However, when the toggle NO/NC command is used on the contact, Acade changes the pin numbers to the NC contact of the second contact. When the toggle command is used again, Acade changes the pin numbers to the NO contact of the first contact. Additionally, when the second contact is inserted and the toggle command is used, Acade blanks out the pin numbers because there are no more free contacts for it to which it can switch.

[Anonymous]

hkim Can you provide sample drawings with very detailed information on the problem you are seeing and steps to reproduce. I have tried using the TOGGLE NO/NC command on the default Form-C symbols and I do not see any problems.......I will be more that happy to take a look at your examples..... Please also provide information on your expectations or the way you would like to see it function when you select a Form-C contact. -- Regards, Jared Bunch Technical Support Specialist Autodesk, Inc "hkim" wrote in message news:2353591.1076032514132.JavaMail.jive@jiveforum1.autodesk.com... > There is a problem with the contact toggle command for a part that has form-C contacts in the pinlist. For example, when the first NO contact of a part that has two form-C contacts in the pinlist is inserted, Acade correctly assigns the correct pin numbers. However, when the toggle NO/NC command is used on the contact, Acade changes the pin numbers to the NC contact of the second contact. When the toggle command is used again, Acade changes the pin numbers to the NO contact of the first contact. Additionally, when the second contact is inserted and the toggle command is used, Acade blanks out the pin numbers because there are no more free contacts for it to which it can switch.

[hkim]

The parent coil of the relay in the attached drawing has a pinlist with 3 form-C contacts. The drawing also contain one NO & one NC children contacts associated with the parent coil (CR1). When the toggle command is used on any of the child contacts, the terminal number changes to another set of contact numbers.

For example, use the toggle command on the NO contact with pins 1&3. The child should change to a NC contact with pins 1&4, but instead changes to pins 11&8 (the pins of the last unused contact).

Now if the toggle command is used on the original NC contact with pins 6&5, the child is changed to a NO contact with pins of the original NO contact (because the is now the unused contact).

If another child contact is inserted into the drawing and is associated with the parent, it will take the pins of the last unused contact. Now, if the toggle command is used on any of the contacts, the symbol will change but the pin numbers will disappear because there are no more available contacts.

The toggle command should keep the common pin the same and only change the NO to NC, or vise versa, not change the pin numbers to a totally different set of contacts.

Regards,
Hyun Kim
Powell Electrical Mfg. Co.

[Anonymous]

Hyun, You are exactly right. I found a related problem with convertible contacts too. This has been logged as a fairly high priority defect. Thanks for the report. Nate. defect #559063 1. Toggle NO/NC on form-C contact in some cases will either flip pin numbers to a different, unused form-C contact even if the opposite "state" of the form-C is not used. At other times it can double up pin numbers. 2. Toggle NO/NC on a converible contact that has only a single set of pin numbers for both NO and NC states can either flip to a different unused convertible contact or can blank out the pins. The existing pins should be maintained when there is only a single set of pins for both NO and NC states.