Components with same Tag name Different location code

[Thomasbatson]

Apparently out of the box ACADE recognizes if 2 schematic symbols have the same tag number they are the same components but that is causing some of our large clients a little issue.  I am wondering if there is a way for components to also look at the location code.

Example would be we separate the panel names by process.  Lets say Process 1 and Process 2.  so I would have a panel in Process 1 starting with P1-E1 and panel in Process 2 as P2-E1.  These are both sheet number 1 and occasionally we have the same component on the same sheet in different panels.  Maybe ethernet switch, so sheet 5 in the same place it would be tagged the same.  Sometimes even years later we do a project that will need both of these panels in 1 project, we update 1 it wants to update the other even though the location codes are different (P1 and P2).

Can someone let me know of a way this is possible? 

Thank you.

[jseefdrumr]

You don't have to do anything to make ACADE 'look' at the location codes; if they're populated, then ACADE takes those values into consideration when deciding whether or not a duplicate tag is an actual duplicate, or if it's a whole other component.

To make this work, you'll have to designate location and installation codes to use, and then go through your project drawings and assign them.

When you're drawing from scratch, you can have LOC and INST codes assigned automatically to every component you insert, by setting those values in drawing properties. However, this capability isn't retroactive, meaning that it won't work for things that already exist in a drawing.

There is a trick to changing all the location/installation codes for existing components at once, if they're in the same drawing. You would do this by drawing a location box around the whole drawing and then checking the box for 'Update existing parent symbol values to match location box'.

[Thomasbatson]

I've got something else going on with the software and isn't new as is was like this here when using 2018 and 2020.  If I have the location code set up in drawing properties already, it does not auto-fill in the components that I am inserting.  It has also always updated components with the same tag number but different location codes here anyway.  

I just did these with a test project and is acting the way I have seen it here. I have 2 sheets set up in 1 project and I put 2 push buttons and 2 ethernet switches (1 of each on each sheet).  I put P1 on the location code on the sheet 1 stuff and P2 location on the sheet 2 stuff. If I update 1 it brings up the dialog box to update the other one. 

Also, I put the Drawing property with a location code and is not auto-filling.  But, this has been the case since 2018 here.  So, why would this be different?

[jseefdrumr · Accepted solution]

Whoops, there's another setting beyond the one in Drawing Properties, my bad.

Under the 'Components' tab in Project Properties, there is a check box for "Upon insert: automatic fill installation/location with drawing default or last used" ..... this box has to be checked also. Sorry, forgot about that part.

Try toggling that on, and then have another go at it to see if it works. Remember that the drawing properties have to have the LOC/INST values set before you insert any components.

When you do run in to instances where ACADE still thinks that two same-tagged components are the SAME component, you can work around it:

1. Edit the first component and change its LOC/INST values.

2. After clicking OK you'll be prompted to update the other one. Skip it and don't update.

3. Go to the second component and change its LOC/INST values.

4. After clicking OK you'll most likely be prompted again to update the other symbol. Skip it and don't update.

5. Immediately rebuild the project database.

6. The two components should now be unlinked and seen as separate objects by ACADE.

[Thomasbatson]

There are 2 there that I have not even seen (well I can't say that, I have overlooked).  Component TAG options we have never had the one you are referencing OR the Combines Installation/Location tag mode checked.  

With the one you mention being checked it now updates.  I just thought since we've used this it is how it is and is so rare it comes up never really has caused a problem big enough we couldn't get around. 

With the Combined Installing/Location mode checked, the Edit Components dialog box is now different but with that checked it now works BOTH ways as expected.

Thank you for the quick help!