Dialog call:You have opened a project. File > Settings > Projects > "Project name" > Device > Terminals (distributed terminals).
In this dialog, you can specify the default settings for working with distributed terminals.
Overview of the main dialog elements:
In this field you set the function definition that is assigned by default to the distributed terminals during insertion. Click [...] to open the Function definitions dialog and select the function definition you want there.
Placing from number of connection points:
Here you set how many connection points with connection point designations the terminal function must have as a minimum so that distributed terminals are placed when inserting devices or placing terminals from the terminal strip navigator. Connection points without connection point designations are not counted here. If the number of connection point designations of the terminal to be placed is lower than the value stated here, the complete terminal is placed.
Connect associated distributed terminals automatically:
If this check box is activated, distributed terminals from a terminal function are connected automatically even if no drawn connections exist between these. For this internal jumpers are generated when updating the connections between associated distributed terminals (same function definition, same DT, same terminal designation). These automatically generated internal jumpers are each created on the last connection point of the terminal function. The order of the distributed terminals in the terminal strip navigator is key to generating the internal jumpers.
If this check box is deselected, then associated distributed terminals are not automatically connected. In one check run, the distributed terminals that were recognized as associated but not connected are notified.
Note:
The check box Connect associated distributed terminals automatically should be activated by default so that the potential forwarding is guaranteed within the terminal.
If this check box is activated, the graphically drawn connections are not used to create jumpers. The graphical connections only show which distributed terminals are always connected to each other but not between which individual terminals the jumpers exist. For jumper optimization, if possible saddle jumpers rather than wire jumpers are generated between the terminals. The internal jumpers are also re-generated.
The saddle jumpers created when optimizing the jumpers are each placed on the first distributed terminal (with the smallest connection point designation) from the last to the next to last connection point of the terminal. The connection point type that is set in each case for the last terminal connection point determines what type of jumper / connection is created. Normally the last connection point should have the "saddle jumper" connection point type.
If the check box is deselected, the graphically drawn connections are used to create jumpers. The relevant internal jumpers, saddle jumpers or wire jumpers are generated from all of the connections that run between distributed terminals when updating the connections. In this case you yourself must ensure that the required connections are drawn on the schematic.
In this example three terminals are placed as distributed terminals in the schematic and connected multiple times with each other graphically. Terminal 1 is connected with Terminal 3 three times, and Terminal 2 is also connected with Terminal 3 three times. So that associated distributed terminals are connected automatically by internal jumpers when the connections are updated, the Connect associated distributed terminals automatically check box is activated.
During jumper optimization, two saddle jumpers are generated:
One saddle jumper between terminal 1 and terminal 2 and one between terminal 2 and terminal 3.
In addition, associated distributed terminals are connected by automatically generated internal jumpers:
Five internal jumpers are generated between the distributed terminals 1:a and 1:b, 2:a and 2:b, 2:b and 2:c, 3:a and 3:b, 3:b and 3:c. Even if there is no graphic connection between the distributed terminals 2:b and 2:c, these are recognized as being associated (by means of the criteria: identical function definition, identical DT, identical terminal designation).
Note:
Net-based connections cannot be used together with distributed terminal jumper optimization. The two functionalities generate different connections that are incompatible with one another.
See also