Updating split parametric PLC attributes

[jjstr8]

I have a custom parametric PLC terminal that will usually end up being split from the main module.  Is there anyway to update attributes on the split-off module when the main module is edited?  I tried add LINE1, LINE, and RATINGx to the terminal but they don't update.  The only ones that seem to get updated are INST and LOC.

[testsubject]

I am not 100% sure but I do not think so. PLC symbols are built parametrically so even if you insert the same catalog part number, the symbol block will be different.

[jseefdrumr]

I'm confused.

Which attributes aren't updating? Are they custom as well?

The tag, install, and location are the only things TO update on the split module. The PLC descriptions themselves have to be edited directly on the child (split) component.

[jjstr8]

I was hoping that LINE1 or LINE2 would update on all the splits, since they are on the edit dialog boxes for the main as well as the splits. I wanted an easy way to have some kind description from the main module propagate to the splits. If a split is on another page, I wanted to bring along some additional information besides the tag. Unfortunately, if I did use INST or LOC, ACE adds them to the split in the same relative location as they are in the top terminal. You'd pretty much have to move them down every time you placed a split.

[jseefdrumr]

Well, I *think* I have an idea that could work, but am not having any luck finding out how to do it.

Background, in case you didn't know: When you insert a parametric PLC, there's a process. ACADE takes your parameters, evaluates them, looks for the block files it needs to create the overall symbol, and then builds it for you. during the build phase, ACADE inserts all those blocks, then explodes them, before re-joining everything into your new parametric block.

So, what I'm thinking here is, the process is almost certainly the same for the split. What we see on top of the child part of the module is only the TAG attribute, but if the child is built the same way as the parent, then at one point this was just a block somewhere. So, following that logic, if we could just determine the name of the block that held the TAG attribute for the split, we could try just adding the LINE1 and LINE2 attributes to it, to see if they'll carry over during a split PLC operation.

My problem is, I just can't seem to find out whether my assumption is right, and/or the identity of that block.

I'll keep looking though, and maybe posting this idea will result in someone else chiming in with the knowledge I'm lacking here.

[jjstr8]

Unfortunately, I think the makeup of the module is essentially lost once the blocks are explode and reformed into the single block. As for the splitting, ACE appears to simply split the block in two and add TAG_x, INST, and LOC attributes in the same location relative to the top of the module prior to the split. For example, I didn't like that the tag overlapped the jagged line in a split module, so I moved the attribute down a little in the "Module Info" block. The change affected not only the top terminal, but also the "child" splits.

[alds02]

Just to clarify, it sounds like the following steps occurred:

Insert PLC module

Split the PLC module

Add attributes LINE1, LINE2, RATING, INST, LOC to the new section

Updated parent and only INST and LOC changed on the new section

Is that correct?

Just curious because I thought I had been successful at getting added attributes to update but I can't find an example immediately.

[jjstr8]

@alds02 Only INST, LOC, and TAG_x get added when splitting. My custom terminal also has LINE1 and LINE2, but they don't get updated, nor do they get populated when it's first placed.

Here's an example of an exploded 1756-IB32

[alds02]

OK. But did you add the other attributes later and still find that they couldn't update? I know it is better to find a way to get those attributes included during the split process, but first I am curious if attributes added later are capable of being updated.

[jjstr8]

I tried adding an attribute as you suggested, but it only is affected when doing Edit Component on the split piece.  The "parent" module doesn't see it.  Another thing I found is if I use the split command, the attributes of my custom terminal that are below terminal don't get repositioned correctly with the split piece.  I only split when the module is placed, so it doesn't affect what I'm doing.

[alds02]

OK -  if the attributes you added can't get updated by the parent, then I am wondering, even if you find the way to get them come with the terminal during the split, maybe they still wouldn't update. But from the earlier posts it sounds like it will be hard to figure out how to get those attributes. I am concerned even if you figure it out they still won't update due to the experiment you just did.

Maybe there is a less "correct" workaround. (thinking)

@jseefdrumr might be the top resource for you, he has posted some sophisticated parametric modules for field I/O, he has the skills!

[jallenDBQ7U · Accepted solution]

Do these items update if you edit in Excel with Export to spreadsheet and Import from spreadsheet?  This method would only be convenient time-wise for multiple changes of course.

[jjstr8]

Thanks, that works well. I hadn't used the import/export before. All I had to do was sort by TAGNAME first, then work my way down the list. Pretty straightforward.

[jseefdrumr]

Nice, I'm a little jealous actually, wish I'd thought of that one. Good call!

[pulaFTSXY]

This doesn't seem to work if you want to change the tag names, any ideas on how to do this?