FAMILY for Symbols with no predefined Table

[jallenDBQ7U]

I need some advice on creation of symbols for devices without a predefined FAMILY attribute.  My specific example is Ethernet.  If the TAG attribute does not match the FAMILY attribute does this create problems when using automation features in the software?

I've noticed that some people use DN as the FAMILY while others use custom labels or even leave it blank.  Most of our drawings use ETH for the TAG numbering.  Does this difference cause issues if FAMILY is DN?  I know that a three letter acronym is not allowed for the file naming used on symbols so FAMILY can not be ETH.

Most individuals at my employer do not use the catalog.  We also do not share libraries.  I am currently implementing the catalog on my computer because I am tired of manually filling in details on Reports.

[rhesusminus]

What is "an ethernet"? Is it a ethernet cable? A switch? A media converter?

[jseefdrumr · Accepted solution]

I tend to use DN (device network) for anything ethernet-related that can't be a subassembly to another part. For instance, data access ports, ethernet switches, NAT or VPN routers, etc.

As far as I know there is no widely accepted standard for doing this in North America.

As for the issue with tags and families, see in HELP: "To Map the Family Codes Used in Component Tags". This will teach you how to create the wd_fam.dat file, which changes the default family code for a component type.

As an aside, your company is wasting money on ACADE using it like this. It's like they went out and bought a refrigerated semi trailer but then they only use it to run to the convenience store for a gallon of milk, lol. You're on the right track, trying to increase functionality for yourself. Hopefully, once everyone sees how easy things get for, they'll all jump aboard.

[jallenDBQ7U]

I am speaking of independent Ethernet devices which would be switches, routers, gateway modules, etc.  For cables we use CBL tags.  For PLC rack Ethernet modules we with PLC tags.

We like to give Ethernet switches their own category because we have a huge amount of Ethernet/IP links on our systems.

[jallenDBQ7U]

We don't like to use DN for Ethernet devices because we have a large number of Ethernet switches on each project.  Ethernet communications is placed on a separate section of drawings in the project.  Devices (welders, testers, etc) are categorized by voltage and placed in their own section as well.

Thanks for the advice on the wd_fam.dat file.  I'll look it up.  It makes no sense to not use the catalog to me (especially if the parts are used on multiple projects).  On my first project at this company I spent a large amount of time modifying BOM's in Excel because each time we altered the project AE would create a report with half the items missing descriptions.  Unfortunately I wasn't quite up to speed on AE at that time to feel comfortable messing with the database and settings.

[rhesusminus]

You should also read up on the WDBLKNAME attribute. Using this in your symbols, you can make AcadE lookup into a custom table for that exact symbol.

[jallenDBQ7U]

I'm not getting this to work very well. 

I know everyone is complaining about AutoDESK not doing anything to advance it so my options may be very limited.  I found a built in command to add a table to the Default catalog.  It worked so I now have a new blank table called ET.  When I create a new symbol and use ET for the family it still maps to DV (HDV1_xxx).  Is this because I failed to do something or is this just not possible?

I looked at the wd_fam.dat option.  If I do a file for ETH tag names do I put ETH,ET in it?  I know I don't want DN,ET since that would possibly map all devices to the new table.  Ignoring the three letter attempt for tag names I can't even get a new two letter option to map to a different table.

I also tried to put ET as a value for WDBLKNAM attribute, but it also doesn't use the new table name.  I made the value of this attribute ET.  Should it be different?

I couldn't find much information in searches for either of the above options or anything that matched a solution for this issue so I am back at square one with my Ethernet devices still mapped to DV Generic table.

EDIT* I did exit AE and restart it.  The empty catalog table does show up in the browser.  I just can't get Symbol builder to let me choose it for a new symbol.  I did figure out that WDBLKNAM won't help me on the creation (use as filter).