nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Junction Edge Connectivity Rules are not enforcing terminal settings

BryanMay531

Our Electrical UN has these rules about connections allowed to Elbows:

Yet, We have connections to Elbows with None for terminal settings and no errors:

and :

These rules should ensure terminal must be set, right? (I swear they were being enforced recently)

Trouver plus de publications taguées avec

Accepted answers

MikeMillerGIS

The rules show that a 3 phase primary can only connect to line side, since there is not an ambiguous rule, an explicit terminal connection is not required, as the rules define that is can only connect to the one line and not the other.

All comments

MikeMillerGIS

BryanMay531

So should it be an error when 3phase primary is snapped to the elbow and terminal is set to none?

BryanMay531

Oh. So are you saying it is assumed to be line side because that is the only acceptable terminal?

MikeMillerGIS

Correct

RobertKrisher

@BryanMay531 If we didn't have this behavior, you would have to explicitly set the terminal connections for every transformer in your system, which would make editing your conductors tedious.

It makes sense that you wouldn't need to populate the terminals for your elbows, since the line side should always be connected to a conductor/cable and the bus side should always be connected to the bus work.

Your rules may not be as clear cut, depending on your drawing standards. If you allow an elbow can be drawn with buswork or conductor on BOTH sides of the elbow THEN you will need to have rules allowing for this and will need to explicitly populate terminals on each line.

BryanMay531

Thanks Robert, I think I get it. I did all of our development with the full UN model so got in the habit of setting everything. When we went to production I removed a ton of stuff and didn't realize the change. So if I delete ambiguous rules I can get this behavior on other features right? Currently rules allow MV Connectors and conductors to snap to either side of Elbows and then the terminals must be set. But we only want connectors on bus side and conductors on line side. But if I remove the rules for the unwanted connections then we won't have to set them anymore. If I understand this correctly?

RobertKrisher

@BryanMay531 That is correct. If you always have bus on a particular terminal and conductor on the other terminal, setting your rules so there isn't ambiguity means that you don't need to explicitly populate/manage the FromDeviceTerminal and ToDeviceTerminal fields on lines.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Toutes les communautés
Publications récentes
Contenu suivi
Aide communautaire

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.