cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Panel W/D Wire Annotation Format – saved on symbol for only 2 of 3 use-cases

Panel W/D Wire Annotation Format – saved on symbol for only 2 of 3 use-cases

When the schematics of an existing project are touched, it is often necessary to trigger update of the existing panel wiring diagrams. This is to make sure each connection on each wiring diagram symbol accurately maps back to the master connection list generated from the schematics.

 

AcadE gives great flexibility in allowing the user to define the format of this wiring diagram annotation. In fact, the user is free to assign one format on one footprint symbol and a slightly different format on another. One symbol might accept cable connections and the next one is just discrete wiring. The user might want to format the first one to include cable/core annotation and the second one to show just the wire number assignment.

 

This flexibility is supported for panel footprint symbols. The wire connection annotation format to use for the symbol, for example “%W (%2) %G”, is “remembered” on the symbol. It is stored as an Xdata value, tag name “VIA_WD_WXREF_FMT”. This works for the use-case of symbol with TERMxx/WIRENOxx attributes and for the use-case where the annotation is pushed on to a generic wiring diagram symbol in the form of an MTEXT paragraph of text.

 

When the user needs to update a wiring diagram symbol or a bunch of windowed symbols, the “Wire Annotation” command will examine each symbol for its annotation format Xdata value and then regenerate connection annotation per the symbol’s stored Xdata value.

 

Problem: the third use-case, panel graphical wiring diagram representations of Terminal Strips created by the Terminal Strip Editor tool, these do not appear to save the user’s selected annotation format as Xdata on the graphical terminal strip. The format appears to be pulled from the registry. Whatever format was last used by anyone on that machine when creating or editing a Terminal Strip on any project will be the format applied when the terminal strip is rebuilt using TSE.

 

Why a problem?: A user may have spent a lot of time with TSE carefully adjusting his smart wiring diagram terminal strip annotation, left side, right side, cable annotation on one side, discrete wire annotation on the other side. Now, later, when changes are made to the schematics and these affect the wiring diagrams, a wholesale update of the wiring diagram is in order. For regular footprint wiring diagram symbols, it is simple. Pick ‘em and they update per the original saved annotation format value. But, the TSE-smart terminal strips will not remember the carefully formatted annotation used when created. Whatever format was last used on the last project worked on is what will be used for the update. Why? Because the format for TSE-generated wiring diagram annotation is pulled from the registry. It is not stored with the symbol instance as xdata on the terminal strip’s first terminal.

 

Potentially big problem, but simple solution. Keep the registry values but save a copy of the actual used format as Xdata on TSE-generated terminal strips… just like what AcadE does for the other non-TSE wiring diagram footprints.

7 Comments
Anonymous
Not applicable

Actually need to add four Xdata values on to the first terminal of the TSEditor-generated graphical representation to fully enable TSE to later rebuild a given terminal strip and its annotation:

 

VIA_WD_WXREF_TSE_PanLeftFormat

VIA_WD_WXREF_TSE_PanRightFormat

VIA_WD_WXREF_TSE_PanScale

VIA_WD_WXREF_TSE_PanAngle

 

t_chaws
Alumni
Status changed to: Under Review

Hi, 

 

We have noted your idea and included it in our research bucket! 

Thank you.

 

Keep posting new ideas!

 

Best Regards, 
AutoCAD Electrical Team

 

Thanks for this suggestion Nate!  It is very painful to rework terminal strips after a change. I keep the P_TAGSTRIP attribute by default in each block.  When I insert a strip, I unhide the P_TAGSTRIP attribute on the first block and move it to a position where it can be easily seen.  Sometimes this also requires a rotation of the attrinbute.  When changes are made that affect a terminal strip, we have to perform a Rebuild from within TSE.  When I have multiple strips in a panel, this is yet another thing to remember to do after you run the rebuild command, because the terminals are reinserted with the their default settings.  It would be grea if TSE could detect the position and visibility status of existing attrinbutes within the blocks of a strip that is being rebuilt.  Perhaps the attribute location and visibility status could also be written and stored as Xdata.

 

I posted an idea asking for all wire number annotations be updated on all footprints. If wire numbers are updated/changed in the schematic, footprints should be updated to match, much like the bi-directional updates between schematic symbols and footprints when part numbers, descriptions etc., change.  It would also be nice if the software could update the wire annotation of terminals without the need to poerform a rebuild within TSE.  And as a bonus, detect the existence of a wire from/to report in the project and offer to run an update of it, so all references of wire numbers stay in sync.

Anonymous
Not applicable

Regarding your second point where you would like to know when your panel wiring diagrams are out-of-synch with the schematics... right now you don't really know -- if you have any doubt, then you have to trigger a wiring diagram update to cover yourself (and hope that nothing else gets screwed up in the process). What would be nice is to have a "Soft Check" tool that would compare the schematic WFRM2ALL interconnections (i.e. the master) with all the wire connection annotation found on the wiring diagram footprints and terminal strip representations. This "SoftCheck" tool would flag the discrepencies. Then you'd know which (if any) of your wiring diagram representations need to be updated (or manually tweaked if just a few minor text changes).

 

I have developed a tool to do the above but it cannot be completely implemented until Autodesk resolves the "use case 3" mentioned in this Idea Station posting. The tool needs to know the annotation format used in TSEditor-generated terminal strip wiring diagram representations. This will allow the tool to accurately decode the annotation found on TSEditor inserted terminal strips and compare it with the schematic master connection data held in the WFRM2ALL table of the scratch database.

I like it Nate!

Icemanau
Mentor

Along with all that, they need to get the TSE team to sit down with the team that does the schematic and work out how they get the di-directionality to work properly.

 

As an example...

 

Schematic terminal blocks have attributes to set Internal/External connections.

TSE has the ability to also set the Internal/External connections.

 

However, when TSE does a write back to the schematic, it doesn't write that information back to the terminal block attributes. It writes it to XDATA attributes it adds to the first component in the sequence away from the terminal block.

 

This then causes data mismatch problems between the schematic and the TSE if you run the TSE on the same terminal strip again for an update.

 

They really need to sit down and sort this out between the two teams before they go on to add more potential data mismatch problems.

 

Ideally, the TSE should write the Internal/External data to the attributes on the schematic terminal blocks using the attributes provided and then get the TSE to store data as suggested in the idea along with proper live updating of wire numbers and other useful actions.

 

Regards Brad

Status changed to: Future Consideration
 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea