Bulk Insert

The 2-minute path

These four steps produce an L5X ready for Studio 5000 import. The full guide below covers every option in detail.

1 Upload · L5X program file. Phase routines are auto-detected.
2 Configure · Pick the operation. Set the rung logic, comment, and target.
3 Process · Apply the operation to every phase routine in the file.
4 Import · Download the updated L5X and re-import into Studio 5000.

Overview

Bulk Insert applies the same rung-level change across every phase routine in an L5X program: inserting a fault-reset rung, replacing a setpoint-load rung, or standardizing an interlock pattern across an entire phase library.

It is specifically scoped to phase routines in the uploaded L5X. The page parses the file, identifies every phase routine inside it, and applies the configured operation to all of them at once. There is no per-routine picker; the operation hits every phase routine the parser finds.

Common scenarios: standardizing a fault-reset pattern across every phase in a 40-phase library, adding a specific rung required by a customer change, or replacing a wrong rung that appears in every phase of an inherited project.

Before you start. You need an L5X program export from Studio 5000 that contains phase routines. Pro tier and above. The output is a single updated L5X with every modified routine baked in.

Step 1. Upload the L5X program

Open Bulk Insert from the dashboard. With no file loaded, two side-by-side options:

Upload L5X Program. Drop an .L5X file into the dropzone or click to browse.
Load Saved. Previously-saved Bulk Insert configurations show as cards on the right. A saved configuration captures the operation parameters but not the L5X. Load it, then upload an L5X to apply.

After upload, the page shows the file name, file size, and detected phase routine count. Below that, the routine names appear as monospace chips (capped at 12 with a “+N more” indicator) so you can confirm the file contains what you expected.

The Clear button at the top of the file info row resets the upload without losing your saved-config state.

Step 2. Configure the operation

Once a file is loaded, the Configuration card appears. The fields:

Phase Rename (optional). If you also want to rename the phase routines as part of the operation, enter the new name here. Leave blank to keep current names.

Operation. Pick one of three:

Operation	When to use it
Insert At Position	Insert a new rung at a specific rung number (0-indexed) in each phase routine
Insert After Comment	Find a rung by its comment text and insert a new rung directly after it
Replace at Comment	Find a rung by its comment text and replace the logic in-place

Rung Identifier. For Insert After Comment and Replace at Comment, the text Bulk Insert searches for inside rung comments. Required for those modes.

Rung Number. For Insert At Position only. The 0-indexed position where the new rung lands.

Rung Comment. The comment text attached to the new or replaced rung. For Replace, leaving this blank keeps the original comment intact.

Rung Logic. The ladder logic for the rung, in Logix text form (e.g. XIC(In1)OTE(Out1);). The same syntax Studio 5000 uses internally.

Worked examples

Insert At Position: add a fault-reset at the top of every phase

Operation:      Insert At Position
Rung Number:    0
Rung Comment:   PLCflow: auto-reset phase fault on start
Rung Logic:     XIC(Phase.SC.Reset)OTU(Phase.SC.Fault);

Before:
  rung 0:  XIC(Phase.SC.Start)OTL(Phase.Running);
  rung 1:  ... existing logic ...

After:
  rung 0:  // PLCflow: auto-reset phase fault on start
           XIC(Phase.SC.Reset)OTU(Phase.SC.Fault);
  rung 1:  XIC(Phase.SC.Start)OTL(Phase.Running);
  rung 2:  ... existing logic ...

Insert After Comment: drop a new interlock after a specific marker rung

Operation:      Insert After Comment
Rung Identifier: Safety_Interlock_Block
Rung Comment:    PLCflow: added remote-stop interlock
Rung Logic:      XIO(Remote_Stop.Active)OTE(Phase.Allowed);

Before:
  rung 4:  // Safety_Interlock_Block — E-stop and door switch
           XIC(EStop.OK)XIC(Door.Closed)OTE(Safety_OK);
  rung 5:  XIC(Safety_OK)XIC(Phase.SC.Start)OTL(Phase.Running);

After:
  rung 4:  // Safety_Interlock_Block — E-stop and door switch
           XIC(EStop.OK)XIC(Door.Closed)OTE(Safety_OK);
  rung 5:  // PLCflow: added remote-stop interlock
           XIO(Remote_Stop.Active)OTE(Phase.Allowed);
  rung 6:  XIC(Safety_OK)XIC(Phase.SC.Start)OTL(Phase.Running);

Routines without a rung comment containing Safety_Interlock_Block are skipped (with a console message). Position-fallback is intentional: a safety-related rung shouldn’t land in an arbitrary spot just because the marker comment was missing.

Replace at Comment: swap a setpoint-load rung across every phase

Operation:      Replace at Comment
Rung Identifier: Setpoint_Load
Rung Comment:                              (blank → keep original)
Rung Logic:     MOV(Recipe.Active.SP_v2, Phase.Setpoint);

Before:
  rung 3:  // Setpoint_Load
           MOV(Recipe.Active.SP, Phase.Setpoint);

After:
  rung 3:  // Setpoint_Load                    (comment preserved — Rung Comment was blank)
           MOV(Recipe.Active.SP_v2, Phase.Setpoint);

Step 3. Process and download

The action card at the bottom of the Configuration section summarizes what’s about to happen (“N routines will be processed”) and exposes the Process File button.

Click Process File. The console streams progress; the result panel shows:

Output Download. The updated L5X with a single Download button. Filename is generated server-side.
A summary: routines processed, rungs updated, rungs inserted, routines skipped (with reasons).
File Preview. The lines of the output L5X for spot-checking or copy-paste adding.

If anything looks wrong, adjust the configuration and click Process File again. The action is non-destructive against the uploaded file; you can iterate as many times as needed.

Saving configurations

The Save button in the Configuration header stores the current operation parameters (operation type, rung logic, rung comment, rung identifier or number, phase rename) under a name. The L5X is not included in the save. Loading a saved config restores those parameters; upload the L5X to apply.

Step 4. Import the updated L5X back into Studio 5000

Right-click the program the phase routines came from in your Studio 5000 project.
Click Import.
Select the updated L5X downloaded from PLCflow.
For each modified routine, Studio 5000 asks how to handle the name collision; choose Replace to overwrite, or Use Existing to skip.
Click OK.
Review your code before deployment. Open a handful of modified phase routines in Studio 5000. Verify the inserted or replaced rungs are where you expect.

Always take a backup before importing a bulk-modified L5X. Bulk Insert can update dozens of routines in one apply. Studio 5000 has no global undo for an import. If something is wrong, the recovery path is to restore from your last backup.

Common pitfalls

The marker comment isn’t in every routine. For Insert After Comment and Replace at Comment, routines without a matching comment are skipped. The console reports the skip count; check it against the routine count to confirm the operation hit what you expected.
Insert position out of range. For Insert At Position, if you specify a rung number greater than a routine’s rung count, the insert is treated as an append at the end. Read the console summary.
Rung syntax error. The rung logic field expects valid Logix text. Typos in instruction names or mismatched parentheses cause processing to fail with an error in the console. Test your syntax on one routine in Studio 5000 first if you’re unsure.
Operation applied to safety routines. Bulk Insert applies to every phase routine in the file, including safety-related ones. PLCflow is not certified for safety review. Strip safety routines from the L5X before uploading if your change shouldn’t touch them.
Phase Rename used with non-phase routines. The Phase Rename only takes effect on routines the backend recognizes as phase routines. Non-phase routines in the L5X are untouched by the rename and by the operation.

FAQ

Can Bulk Insert apply to a subset of routines?

Not in the current build. The operation applies to every phase routine in the uploaded L5X. For finer-grained or non-phase operations, Precision Replace has a per-routine scope picker.

Can I run two different operations in one upload?

Run them sequentially: configure the first operation, process, download the output L5X, upload that as the new source, configure the second operation, process. Saved configurations make this clean. Save each operation under a name and load them one at a time.

What's the difference between Bulk Insert and Precision Replace?

Bulk Insert operates at the rung level (insert a whole new rung, replace an existing rung as a unit) and is scoped to phase routines. Precision Replace operates within rungs (rename a tag across all uses, swap instructions, shift array indices) and applies to any routine, scoped via a routine picker.

Does it preserve comments on existing rungs?

Yes for inserts: existing rungs shift down by one position and their content (including comments) is preserved. For Replace at Comment with the Rung Comment field left blank, the original comment is preserved; with text in Rung Comment, the original is replaced.

Does it work on Structured Text or Function Block routines?

Currently optimized for ladder logic in phase routines. ST/FB routines in the same L5X are parsed but not modifiable through Bulk Insert.

Duplication. When you need to clone a routine with variations rather than modify multiple routines in place.
Precision Replace. When the change is within rungs (tag renames, instruction swaps) rather than at the rung level, or when you need to scope to non-phase routines.

What's next

Related modules

Was this helpful?

Honest feedback. We read all of it.

Email support Talk to an engineer