Duplication

Overview

Duplication clones uploaded L5X routines across N variants, with per-variant find-and-replace rules. For every input file × every variant, the rules run in order and produce one output file. Sixteen output routines from four uploads × four variants, twelve from two uploads × six variants, and so on.

Common scenarios: producing Line 2 through Line 12 from a Line 1 master with different tag prefixes, cloning a master phase routine for every batch reactor in a plant, or copying an existing zone’s logic into a new zone with the appropriate name changes.

The page has an upload section, a variants editor, and a process action. Output appears as a downloadable ZIP plus a file preview.

Step 1. Upload the L5X files

Drop one or more .L5X files into the upload zone (or click to browse; the file picker accepts multiple selections). The list of uploaded files appears as monospace chips below the dropzone.

A Load Saved panel sits on the right. Saved configurations capture the variants and rules (not the L5X content) so you can apply the same set of replacements to a new file later. Click any saved card to load it, then upload the L5X to process.

The Clear button drops the uploaded files; Add Variant stays available so you can build up the variants before uploading too.

Step 2. Define variants and replacement rules

A variant is one set of substitutions. Each variant has:

• Variant name. Internal label (Variant 1, Line_2, Zone_B, etc.).
• New routine name (optional). Renames the routine inside the output L5X. Only effective on single-routine L5X exports; project-level files show a warning that the rename has no effect.
• Replacement rules. A list of find-and-replace pairs that transform the routine’s text.

Each rule has three fields:

Rules apply in order, top to bottom, against the running output. Rule 2 sees the result of Rule 1.

A typical variant for “Line 2 copied from Line 1” might have:

Find: Line_1     →  Replace: Line_2      (regex: No)
Find: L1_        →  Replace: L2_         (regex: No)
Find: Phase_01   →  Replace: Phase_02    (regex: No)

For pattern matching, regex helps. To rename every Pump_1xx tag to Pump_2xx:

Find: Pump_1(\d+)    →  Replace: Pump_2$1    (regex: Yes)

Worked example

Given a master routine for Line 1 with tags like Line_1.Conveyor and Pump_101.Run, cloned for Line 2 with tags like Line_2.Conveyor and Pump_201.Run:

Variant name:      Line_2
New routine name:  Line_2_MainPhase
Rules:
  Find: Line_1     →  Replace: Line_2     (regex: No)
  Find: Pump_1     →  Replace: Pump_2     (regex: Yes, find as \bPump_1\b, or rely on rule order)

PLCflow runs the rules in order against the master and produces an output L5X named after the variant. Inside the rungs:

XIC(Line_1.Conveyor.Run)OTE(Line_1.Conveyor.Cmd);   →   XIC(Line_2.Conveyor.Run)OTE(Line_2.Conveyor.Cmd);
XIC(Pump_101.Run)OTE(Pump_101.Cmd);                  →   XIC(Pump_201.Run)OTE(Pump_201.Cmd);
// Line_1 startup interlock                          →   // Line_2 startup interlock

Note how the regex \bPump_1\b (or a literal Pump_1 rule ordered before Pump_10-style overlaps) keeps Pump_101 working: the literal Pump_1 match plus the trailing 01 becomes Pump_2 plus 01 = Pump_201.

Three more variants with rules Line_3/Pump_3, Line_4/Pump_4, etc. would produce three more output L5X files alongside Line_2’s, all from the same master upload.

Adding and removing variants

Add Variant appends a new block at the bottom. The trash icon in each variant header removes it (only available when more than one variant exists). The Save and Load buttons in the section header persist the entire variants set so you can reuse it across projects.

Step 3. Process

Click Process Files. The action card at the bottom of the variants section shows the running total (N files × M variants = K outputs) so you can verify the count before committing.

PLCflow runs every variant’s rules against every uploaded file and emits one output L5X per combination. The console streams progress; the output panel appears after the run.

Output

• Output Download. A card per output L5X, plus a Download ZIP for all of them at once.
• File Preview. First 200 lines of the first output file, for spot-checking that the substitutions look right.

If a variant has no rules and no new routine name, it’s skipped (the active variant count in the action card reflects this).

Step 4. Import the variants into Studio 5000

For each downloaded variant L5X:

1. Right-click the program you want the variant to live in.
2. Click Import then Import Routine.
3. Select the variant L5X.
4. Set the routine name if Studio 5000 prompts. If you set a New routine name in the variant editor, that’s the suggested name.
5. Click OK.
6. Review the imported routine before deployment. Open at least one variant in Studio 5000 and confirm tag references substituted as expected. Run Code Analyzer on the variants before commissioning.

Common pitfalls

FAQ

Related

• Precision Replace. For finer-grained, structure-aware substitutions across an entire L5X program, not just routine cloning.
• I/O Code. The generated logic from I/O Code is often the master that gets duplicated across lines.