Source / Destination Naming

dbrblg · ‎08-08-2017

Do source and destination codes need to be unique to the drawing only or unique across the project as a whole?

Thanks

TRLitsey · ‎08-08-2017

Hi there,

For the source it needs to be a unique CODE for the project. The source, or parent, can have many destinations, or children, but only one parent. If I am running a circuit across several pages I will use a tag to make each parent unique. Say for a 120VAC distribution the first parent would have the code 120VAC_1L1_1A, and the next parent would be 120VAC_1L1_2A, then 120VAC_1L1_3A, and so on. Funny thing is you can name two parents with the same source code, at least with older versions of ACE, but when you update the drawing package the references will go haywire.

I should say that the Description can be anything you want. It is just a text string. It can be different on source and destination. The CODE is what links the Parent to its Children.

Good luck

Please mark as a solution if this works for you, kudos are always welcome

jseefdrumr · ‎08-08-2017

Each source code should be unique for the project as a whole. Everything else is derived from that, so it doesn't matter about the destination code (it inherits its info from the source). As TRLitsey pointed out, ACADE could get confused if there are duplicate names in a project.

From ACADE HELP: The wire number from a source-arrowed wire network copies to all associated destination-arrowed wire networks. Enter a code using a unique number, word, or phrase of 32 characters maximum to link the source wire network to all destination wire networks internally.

So, a source code has to be unique.
A source can point to multiple destinations.
A destination can only point to one source.

Our method here is, the signal code is always wirenumber@ladder reference, and the description is for what kind of signal it is. Examples:

537@537: 0V DC
501@537: 24V DC
2115@2115: GP ALARM (this is an alarm for a grease pump)
537@2401: 0V DC BUS

Hope this helps,
Jim

Jim Seefeldt
Electrical Engineering Technician

dbrblg · ‎08-09-2017

Thanks for this guys. I did think I'd read something about a unique code sometime back but was unable to find the passage from the help files which you did, so wasn't sure whether this was the case or whether it was a drawing or project scope.

My problem now is choosing meaningful names for the CODE. We are reluctant to use wire number or component codes as there is the possibility these could change leaving the source with a name which may be incorrect and could lead to confusion as users could look at the name and think it has been incorrectly assigned or the system has labelled something wrong. Unfortunately this way of thinking doesn't actually help as there is little else left without writing an essay for the CODE describing where it goes to, from, function etc...

When I change a source CODE which is being referenced by a destination, I see the destination does not change to point to the new Source code - is it supposed to?

TRLitsey · ‎08-09-2017

Hi again,

Developing the CODE syntax can be a magical mystery tour. What I mean is that it can be tailored to fit just about any style or application. It just boils down to what works best for you. Power distribution can be straight forward but you may need to use a little imagination for multi-contact devices or PLC I/O points or multi-pin connectors. Have a little fun with it.

As far as to/from working correctly, when first inserted they should automatically update cross ref. Later on if you move or edit them you may need to Rebuild Project Database, and THEN run the manual update. And just as a reminder, the arrows use the Sheet reference numbering, which beans if you insert an arrow where there is no Sheet ref. numbers you may only get ?? for the ref. That is normal, ACE is telling you it is pointing somewhere but it does not know where.

Good luck

What it can look like