This ETS App must be enabled using a separate license.
This very powerful and complex copy function makes it possible to copy complete project areas (lines) with the ability to influence every element to be copied along with its properties (including among other things, the assignment of PA/IAs) at its destination. Consequently, this also includes "levels" below the element to be copied, such as lines in the topology, when entire areas are copied.
Procedure
Two procedures allow every element being copied to be given settings using a broad array of options:
Generation Logic
Defines options as to whether elements should be generated, discarded or kept during the copying process.
Copy Logic
Defines options for addressing, by counting and/or assigning names (when elements are generated/copied). Copy Logic always references the previously generated element for several elements to be copied, i.e. including copies of copies. Depending on which elements to be copied have been selected, various interdependences arise as a result. One example:
1.A certain number of devices is selected in the topology. The basic objective is the duplication of the devices 1 - n times.
•Obviously, this requires the generation of new device PA/IAs which must be assigned to the copied devices.
•The generation of new lines is not mandatory. Retention of the copied devices in the original line is also a possibility. A further question is whether the group addresses used in the original devices are also to be used in the device copies (e.g. central addresses), or whether new ones should be generated.
All of this creates complex interdependencies. The following table provides an overview of which properties (in dependence on the selected element) can be influenced in the copying procedure.
Interdependencies
#
Source
Target, logic definable for?
1
Area; trade; building part; "All Devices" section
Area, line, devices and their associations (+ new group addresses), buildings, trades
2
Line
Line, devices and their associations (+ new group addresses), buildings, trades
3
Device(s)
Device(s) and their associations (+ new group addresses), buildings, trades
4
Main Groups* (MaG)
MaG,MiG,SuG
5
Middle Groups* (MiG)
MiG,SuG
6
Group Addresses (SuG)
SuG
*
Depending on the group address structure selected, only elements that are available there will be displayed.
Preview
In order to evaluate such complex copy operations in advance, there is a preview option in the copy dialog. A separate window opens in which all of the results are shown "virtually". The preview is given is several parts.
•Topology
•Group Addresses
•Buildings
•Trades
The following display colors are used for this:
#
Color
Preview
1
Black
The copy target can be generated according to the specifications
2
Orange
The copy target can be generated, but not according to the specifications (in this case, the Default Copying Rule is used)
3
Red
The copy target cannot be generated at all (e.g. in case of overflow)
Independent of the preview, the copy procedure generates the copy targets which might have been possible (black / orange) when executed, but a message might indicate that certain (red) parts cannot be generated.
Available Options
Generation Logic
The following generation options are available:
- Discard*
Deletes the elements in the copy which are in the original.
- Keep
Leaves the elements in the copy which are present in the original unchanged.
- Generate**
Generates elements in the copy - default.
*Discard
Associations
All links between devices and group addresses are lost in the copies.
Buildings
All assignments of devices to various buildings (or parts) are lost.
Trades
All assignments of devices to trades are lost.
**Generate
Associations
Are created, according to the GA structure valid in the project; renaming is possible.
Buildings
Are created; renaming is possible.
Copy Logic
The following copy options are available (depending on whether the source supports this property or whether it even makes sense):
- Address
Methods for assigning addresses at the destination, e.g. for lines or devices (PA/IA) if these are generated.
- Rename
Methods for textual replacements, e.g. for lines or building names.
- Extension
Methods for textual prefixes / suffixes as well as automatic numbering.
Address
Identical methods (including the boundary conditions) as for pasting contents, with the addition of options #5 and #6:
#1 Fill up
see Paste Special
#2 Append
see Paste Special
#3 Offset
see Paste Special
#4 Start with
see Paste Special
#5 Fixed
Fixed value; possible forms of logic: - Target areas are variable, target lines are given a fixed assignment (e.g. 5 line copies; areas = Append; Lines = Fixed) - Devices to be copied in the fixed area and line are "concentrated" (e.g. 200 devices from 1..n lines in line 1.12); this form of logic can create overruns (red preview)!
#6 ¨ Existing ...
It is possible to add the group addresses being generated to a previously existing MaG, orMiG or to generate new ones. When enabled, an attempt is made - independently of the method selected above, #1 .. #5 - to include the group address to be generated in an existing MaG, orMiG instead of resorting to the default copying rule/ fallback method for previously existing elements. Example:
•Device with 8 GOs, linked to existing GAs 0/0/1 ... 0/0/8 (only MaG 0,MiG 0 and MiG 4 exist)
•Option þ : Devices - Copy, GA è 0/0/9 ... 0/0/16 to 0/0/41 ... 0/0/48
•Option ¨ :Devices - Copy, GA è 0/1/0 ... 0/1/8 to 0/6/32 ... 0/6/39 (fallback method for existing MiG 0and 4 becomes active)
Rename
The following methods are available:
#1 No Renaming
Leaves the text unchanged; for building parts, for example, the copying rule is used and an XYZ (2) is generated.
#2 Text
Replaces text "A" 1:1 with text "B"; other text apart from "A" is ignored and remains unchanged when replacing; "A" is interpreted as a complete string, e.g. only replaces "eks" in elements in which "eks" occurs 1:1 (A="lur"; B="eks"; Klur è Keks).
#3 Regular Expression*
Option for complex textual replacements using a character string to describe a group of characters.
•?<...> are placeholders for subsequent values; something found like "Line" using (?<find>Line)can be used again later using ${find}.
•The numbers 1-9 are filtered by (?<number>[1-9]) which refers to all numbers from 1 to 9.
Further information about regular expressions and the associated syntax can be found on the Internet.
Extension
The following methods are available:
Text
#1 No Renaming
Leaves the original text unchanged.
#2 Prefix
Adds a prefix text or a numbering prefix in front of the actual (original / renamed) text; the numbering allows for a starting value (starting values which do not conform to the numbering pattern are ignored).
#3 Suffix
Adds a suffix text or a numbering suffix after the actual (original / renamed) text; the numbering allows for a starting value (starting values which do not conform to the numbering pattern are ignored).
Automatic
#1 A B C ... 1 2 3
Counter types
#2 Starting value
Starting value, as of which counting begins; it must correspond to the counter type selected (1,2,3 and A as the starting value is not allowed)!
#4 ¨ Count in every ...
Resets the prefix/ suffix counter according to the counter type, e.g. in newly generated building parts, new lines or for every newly generated MaG, MiG (so as not to ruin the address/logic scheme - usually for a 3-level GA Style - in the new levels).
Notes
•Elements are anything from an entire area in the topology to individual devices.
•When elements are copied, together with the couplers (not repeaters), the corresponding topology nomenclature (PA/IA= x.y.0) must be taken into consideration, even when, according to the desired copy strategy of the coupler (for example, due to an offset parameter), actually a PA/IA with an address >0 would have to be generated.
•Prefix and suffix numbering is continued and not reset when option #4 is not enabled, even when, for example, a new MiG is generated by the creation of new GAs.
