component Assemblies Not Working With PinLists

[dbrblg]

I was trying to be a bit clever and utilising the AssemblyCode and AssemblyList facilities in the database so when I add a push button, I also get the latch and contact.  

There are two problems, that I am seeing (or perhaps lack of setup or understanding, perhaps).  

Let me describe the setup:

Push Button (AssemblyCode - "1,Latch;2,NOContact") 

Latch (AssemblyList - "Latch")

Contact (AssemblyList - "NOContact")

The first one is more of an annoyance.  After selecting the Push Button from the parts catalog, I notice the Latch and Contact are missing until I check "Display subassembly entries only for editing" - why?  why do they disappear because they are subassemblies.  I might want to add them to something else, so why hide them?  A little odd.

The second thing is a problem, the Contact has a PinList entry but when it is a subassembly these pin designations don't appear to come through.  Pin Lists only appear to come through then the contact is added as the 'main' part and not as part of a multiple catalog part.

Has anyone else encountered this or is it a setup issue?

Thanks

[dougmcalexander]

Anytime an assembly code is used it effectively creates a unique component.  For, example, a motor starter with an auxiliary contact will require additional pins.  You will need two entries in the pin list database, one with an assembly code that adds the auxiliary contact pins, and one without the assembly code that only includes the motor starter power contact pins.  This is required in order for the error checking to alert you in case you try to add too many child contacts to a relay or motor starter.  Think of it this way.  Adding an assembly code to a main (i.e. master) component, or an assembly list value to a subassembly component, creates a new part number.  Put another way, the catalog number and the assembly code or assembly list values combine to create a unique part/part number.

The reason you must click to display subassembly items for editing is because once they are associated with a master/main part the idea is to select the main part and automatically you get the subassembly parts when the BOM is generated.  It just keeps the catalog lookup list minimized to only stand-alone parts or master parts, for clarity.  If you still want a version of the subassembly part that can be selected manually, copy or create a new entry in the catalog database that has a blank assembly list field.

Hint:  Once you select a main part number and click OK to assign it to a main component symbol, if you are curious what subassembly parts might be associated with this main part, simply click the icon labeled Catalog Check.  (see attached screen capture)

[Jon.Dean]

Nice one Doug. Hopefully your excellent solution resolved the issue.

Jon.

[dbrblg]

Hi Doug, thanks very much for your explanation 

It is slightly frustrating that making assemblies seems to reduces the functionality and you essentially have to double up on catalog entries but if that is the way it is then that's what I'll have to do!!

Thanks again.

[Icemanau]

To me, it seems the catalog browser has taken quite a few very large steps backwards in functionality...

2014 and prior, you could have multiple main components use the same sub component and the sub component pin list would be added to the main components pin list.

2015 and possibly 2016 now seem to need a new sub component entry for EACH INSTANCE of a main component paired with a sub component, each with their own individual pin list on the main item only.

The 2015 catalog will have massive bloating problems leading to a slowdown in accessing it.

I thought the idea was to cut down on the catalog bloat but it seems that the programmers are working to a different set of standards than those of us who actually use the software.

Regards Brad

[dbrblg]

I'm afraid I tend to agree.  The whole catalog database and Insert/Edit Component dialog is overly complicated for what it's doing.

The catalog assignment of multiple parts is tedious - first, choose main part, second click multiple catalog, select sequence, click catalog lookup etc etc.  In short click here there and every where.

Why not just make it a list with an add/delete button at the top - just build up the list from one place?

Navigating through the database tables to find what you want is a pain.  One part is in this table and associated parts are in another table, yet you require another part from a different table.....

What if all parts were in one table and that table was automatically filtered by the block name (as it currently does to determine which table to use) in the background to cut down on the number of records returned.  Simple.

And then there's pin lists.  What if the parent contains more than two pins?  How difficult it is to assign pins.  I shall not get started here....

Hopefully some of these issues can be addressed in later versions however I get the feeling they're not going by Brads comments, which is a shame.