Building Custom PLC symbols, Parametric or Symbol Builder?

[aaron_robertsLV97S]

I need to migrate a bunch of existing AB PLC symbols from AutoCAD to AutoCADE that my company has used for years.

We want to keep the same layout we have always used, is it better to build these symbols as parametric or using the symbol builder?

[rhesusminus]

That all depends on how you use your symbols. If they're used in ladder diagrams, I'd create them in the PLC editor. Else, I'd use the conversion tools to convert them to AcadE blocks.

[aaron_robertsLV97S]

Thanks for the response,

We are not using them in ladder diagrams, so the route forward sounds like the "conversion tools". What do you mean by conversion tools? is that they Symbol Builder or is there a more specific tool to be used for this?

When using the Symbol Builder I created an attribute file that I called AT_VP_PLC-.dwg and added what attributes I needed for my 1756-IA16 card I am attempting to migrate. I looked for other AT files pertaining to PLCs but could not find any, so I am wondering if there are any native files.

In order to get the PLC Edit Dialog Box to appear I save the block as PLCIO_1756-IA16. The correct dialog box appears but I am unable to get anything to properly populate in the box.

[rhesusminus]

They aren't very well documented, but are used to convert AutoCAD blocks into AcadE blocks:
AutoCAD Electrical 2025 Help | About the Tagging and Linking Conversion Tools | Autodesk

[aaron_robertsLV97S]

I believe I was modifying my response when you sent yours, but I did add a part two to my initial response.

[rhesusminus]

Can you post the block you've got so far here?

[aaron_robertsLV97S]

Here you go, let me know if that works. 
It is kind of funny in the fact that I am showing an IFM module, but the concepts should translate.

[arshdeepsingh404 · Accepted solution]

Try the attached symbol.

[aaron_robertsLV97S]

Thanks!

That is what I am going for, can you please breakdown how you accomplished that?

[arshdeepsingh404 · Accepted solution]

No Problem.

The most important thing is the PLCIO_ prefix to the symbol name which you already had.

After that every input needs a specified set of Attributes to make it a PLC input.

TERM##

TAGA##

DESCA##

DESCB##

DESCC##

DESCD##

DESCE##

Replace ## with the number like 01, 02, 03

You don't need to add the description attributes (DESCD##, DESCE##) if you are only planning to use 3

Remember to always pair them together TERM01 is where the PLC module expects TAGA01 (First input) to be. Lay in the PLC connections first and then you add the terminal connections for non IO points like 120VAC, N, 24VDC, 0VDC, etc.

[aaron_robertsLV97S]

Great thanks! 

Last thing, is there an attribute file for PLCs or should I create my own? I can't seem to find one.

Here is my attempt at creating one based off of the information you sent me. Can you take a look at it and trim down any unnecessary attributes or add any that I may be missing?

[arshdeepsingh404 · Accepted solution]

I am not sure if there is attribute file for these, My favorite way to reverse engineer things. I explode a standard ACADE PLC block and try to understand the attributes.

I don't think you need the CONTACT attribute for this symbol, there won't be any child contacts.

You should add DESC, LINE1, LINE2 attributes to make the below fields functional.

[aaron_robertsLV97S]

Thanks