ACE Asset Tools - User Help & Guide

Server Edition — Accounts, Projects & Sharing

This build runs as a multi-user server application. Instead of each person keeping data in their own browser, everyone connects to one shared server where projects, PLC data, patterns and the audit trail all live in a central SQL database. What you save is visible to your colleagues, and it survives closing the browser.

Signing in

• Open the server address in your browser (for example https://your-server:7443) and sign in with the account your administrator created for you.
• On first sign-in you may be asked to change your password. Access to each tool depends on your role (Administrator, Engineer, Technician, or Operator).

Projects and versions

• Work is organised into Projects, each holding one or more imported versions. The Project and Version pickers sit at the top-left of every page.
• The hub's Process and Save creates a fresh project for each batch of files loaded (named from the loaded controllers — you can rename it in the prompt). Use this when you're onboarding a new site or want a clean snapshot.
• Per-version file editing — on the Projects admin page, the current version's file list gains per-file Remove buttons, checkboxes with Remove selected (multi-file remove creates one new version), and a + Add file control. Removing file(s) auto-forks the version: the original stays as an immutable historical record, and a new current version is created with those file(s) omitted. Adding accepts one or more .L5X/.XBD/.XHW/.ZEF/.XEF files in one picker (each is appended to the current version in place — no fork), parses metadata, and refuses duplicate filenames. This lets you swap or drop controller exports in a large project without re-uploading the whole batch. Every add and remove is recorded in the audit log.
• The Projects page (admin) lists every project, its versions, when they were loaded and by whom, and how much is stored. Deleting a project removes all its versions and data permanently. Administrators can also use Delete all projects… to wipe every project, version, source file and dataset on the server in one step (irreversible; audited). Use it only when retiring a test site or clearing the server before a fresh load.
• Auto-heal: after any Add/Remove File, the hub rebuilds the derived caches (pcsData, Loaded PLC Files manifest, I/O index, CPU report) automatically on next visit from stored .L5X, .XHW and .ZEF/.XEF — you'll see a "Rebuilding processed data…" banner briefly, then everything is ready.

Users & Audit (administrators)

• Users — create, disable, reset and group accounts. Four groups map to roles with increasing access: Operators (read), Technicians (read + reports), Engineers (+ write & reference data), Administrators (everything).
• Audit — a searchable log of who did what: sign-ins, saves, deletes, report generation and exports, plus any access that was denied. Exportable to CSV.

Where your data lives

Unlike the offline edition, data does leave your browser — it is stored on your organisation's server. Individual tool pages still read and write through the same interface, but behind the scenes they save to the server, with a local cache so pages load quickly and only re-download when something has actually changed. If you ever see a red “Not saved to server” banner, your work was kept in the browser only and has not reached the database — re-process, and check the Projects page shows a stored size before closing.

SLC 500 / MicroLogix Support (RSLogix 500)

Alongside Studio 5000 .L5X files, the suite reads RSLogix 500 exports from SLC 500 and MicroLogix processors. These are a different, text-based format (.SLC), but they flow through the same tools — ladder viewer, FD generator, tag search, BOM — because they're translated into the same shape internally on import.

What to upload

• .SLC — the ladder/program export. Drop it in the PLC Files box with your L5X files; it's detected automatically.
• .SY5 / .SY6 — the symbol & comment table. These carry the descriptions the bare .SLC lacks. Upload them alongside the matching .SLC (same base name) and the addresses in your logic pick up their names — e.g. O:2.0/1 shows as SV15. Where both are present, .SY6 is preferred (it's the fuller, newer format).
• .FIX / .FX2 — binary fixup files. These are ignored; they carry no documentation the tools can use.

Honest limitation: if you upload a .SLC without its .SY5/.SY6, the logic and structure are still exact, but operands appear as raw addresses (B3:0/15) rather than names — because the names simply aren't in the .SLC file.

Getting Started: The Home Page

The Home Page is the central hub for the tool suite. All data is loaded here and — in the Server Edition — saved to the shared server (or, in the offline edition, your browser's local database), making it available to all the other tool pages without needing to re-upload.

1. Loading Your Data

1. On the Home Page, use the drag-and-drop zones or click to browse for your files: Asset Report (.csv), PCS Data (.l5x, .xhw, .slc, .xbd, .zef, .xef), FD Patterns (patterns.xml / schneider_patterns.xml), Schneider Tags (.txt), and Lifecycle Data (.csv).
2. You can add multiple PCS data files at once. Rockwell and Schneider files land in the same PLC Files box — they're sorted by extension automatically.
3. After selecting your files, click the Process and Save Data button. New customers can drop the compact samples samples/ACE_Systems_Demo.L5X and samples/ACE_Peer_PLC.L5X here — unlicensed ACE Suite and CSAM allow those demo files (controllers ACE_Systems_Demo and ACE_Peer_PLC) with full tools; other plant files still need a licence. Load both to see resolved produced/consumed links in PCS Messaging.
4. An inline progress bar shows which file is being read and how many remain (large L5X files are read serially so you can see progress).
5. A status message will confirm when data is loaded. This data will persist even if you close the browser tab.
6. Each upload box shows a loaded-status indicator — a green "✅ … loaded" line (with a count) when data of that type is present, or a red "⚠️ No … loaded" line when it isn't — so you can see at a glance what's in the database, including for FD Patterns and Schneider Tags.
7. If you process new PLC files while a project is already loaded, you'll be asked how to apply them: Add to existing merges the new controllers in (a controller/file with the same name is refreshed rather than duplicated), or Clear PLC data & replace removes only the PLC-file data and starts fresh. Your Asset Report, Lifecycle, FD Patterns and Schneider tags are never touched by this choice.

2. Loaded PLC Files panel

Below the upload boxes, the Loaded PLC Files panel sits on the same row as the Schneider tags area and widens into the open space to the right. It lists every controller detected in your uploads with:

• Name — the controller name from the L5X.
• File Name — the source filename that was uploaded (useful when several exports share the same controller name, e.g. …IrrigationOld.L5X vs …Aug28.L5X).
• Platform — Rockwell (L5X) or Schneider (XBD).
• Type / Detail — the processor type (e.g. 1756-L83E) or, for Schneider, the number of FBD networks.
• FW — firmware major/minor revision.
• PLC Standard — the site "code standard" version, auto-detected from a shortlist of common controller tags (Standard_Code, sCodeVersionDeveloped, Site_Standard, S88_Version, CodeVersion), falling back to a combined RevisionMajor/RevisionMinor read.
• Source — encryption status badge:
  • 🔓 Clean — all program routines have visible source.
  • 🔒 N/M enc. — partial encryption; N of M programs are source-protected.
  • 🔒 Fully encrypted (N/N) — every program's routines are stored as <EncodedData>. IO detection, tag search, and utilization figures will be significantly reduced for this PLC because scanners cannot parse the encrypted logic.

Note on encrypted controllers: if a plant's L5X was exported with source protection on, no scanner (this suite or Rockwell's own tools) can pull tag↔IO mappings, ladder logic, or usage counts from those routines. The encryption badge makes this visible so a suspiciously-low utilization or empty search result is easy to explain. Source protection is Rockwell EncodedData / encryption on the routines themselves — not the same as FactoryTalk Security permissions on the export.

3. Navigating the Tools

Once your data is loaded, use the navigation bar at the top or the tiles on the Home page to access the different tools. Hardware tools that work for both Rockwell and Schneider (Report Packager, PCS Asset Map, BOM Viewer, I/O Card Utilization) sit in their own Common / both platforms group. Rockwell-only tools include the Ladder Viewer, Tag Search, Messaging, UDT/AOI Report, and PCS Version Compare. Schneider-only tools stay in their own section. Additional actions in the toolbar row:

• Identify UR20 Modules — quick scan for Weidmuller UR20 IO modules across all loaded L5X.
• Refresh Page — reloads the hub view (useful after you Process new files).
• DB Export / DB Import — save the entire loaded data set to a single .json file (backup or move between machines).
• Delete Database — clears every stored file and cache from the browser.

ClarOTy Asset Map & Inventory

This is the main dashboard for visualizing the structure of your assets based on the ClarOTy Asset Report.

Building Your View

• Add/Remove Assets: Click assets in the Major Asset list on the left to add or remove their diagrams from the canvas.
• Filtering the List: The asset list only shows items identified as racks/chassis (excluding detailed card/address entries).
• Pan and Zoom: Click and drag the background to pan. Use your mouse wheel to zoom.
• Search: Use the search boxes to filter the asset list by name or highlight specific card models on the canvas.

Canvas Actions

• Join Selected Nodes: Select two assets (using Ctrl/Cmd + Click), then click this to draw a dashed line connecting them.
• Unjoin Selected: Select a dashed line and click this to remove it.
• Ghost/Un-ghost Selected: Select an asset to turn it and its children grey. This visually hides them and removes them from the "BOM Summary - ALL" list.
• Clear Canvas & Selections: Removes all assets from the canvas and clears selections.

Inventory / Bill of Materials (BOM)

• Toggle Inventory: Shows/hides the BOM panel on the right.
• The panel displays a combined inventory of all non-ghosted assets currently on the canvas, grouped by model.
• It also provides summaries for each individual major asset.
• Clicking a model row in the summary highlights the corresponding nodes on the canvas.

Exporting

• Export Selected as PDF/ZIP: Generates a PDF file for each major asset currently displayed on the canvas. If multiple assets are selected, they will be combined into a single ZIP file. Each PDF includes the visual diagram and its corresponding BOM.

Your work on this page—including asset selection, joins, and ghosted states—is automatically saved for your browser session.

Architecture Comparison

This tool allows for a side-by-side comparison of the same control system asset as represented in the ClarOTy data and the PCS project data.

How to Use

1. Select ClarOTy Asset: Use the list on the left panel to choose the main ClarOTy asset (PLC/Chassis) you want to visualize. The list is pre-filtered to show relevant assets (excluding detailed card/address entries).
2. Select PCS Controller: Use the list on the right panel to choose the corresponding controller from your uploaded PCS project files.
3. Draw Comparison: Click the Draw Comparison button in the top bar.

Understanding the View

• Left Panel (ClarOTy): Shows the architecture based on the selected ClarOTy asset report data.
• Right Panel (PCS): Shows the architecture based on the selected PCS project file data. Racks marked as hidden in the "PCS Data Viewer" tool will be excluded from this visualization.
• Lifecycle Colors: Border colors on nodes in both diagrams indicate lifecycle status (Green=Active, Orange=End of Life, Red=Discontinued, Grey=Unknown).
• Module Count Comparison: The status bar at the top right (next to the "Done." message) shows the number of modules counted in each view and calculates a percentage representing (ClarOTy Count / PCS Count). This gives a basic quantitative comparison.

PCS Asset Map

This tool provides a visual network diagram of your PLC's hardware configuration based *only* on the PCS project files (`.l5x`, `.xhw`, `.zef`/`.xef`), showing how local and remote racks are connected. Racks marked as hidden in the "PCS Data Viewer" are excluded — and you can Hide / Show the same racks from the drawing itself.

Understanding the Diagram

• Nodes: The diagram shows the **Local Chassis**, its **Local Modules**, and any connected **Remote Racks** with their respective modules.
• Lifecycle Colors: The border color of every component (chassis, racks, and modules) indicates its lifecycle status, matching the legend below.
• Connections: Solid lines show modules on the local backplane. Dashed lines represent network connections from a local communication module to a remote rack (these may need to be added manually). Red lines indicate special connections (e.g., Schneider secondary racks or direct CPU-Rack links).

Hide / Show racks from the drawing

• Hide: Right-click a rack or local chassis node (not an empty slot) and choose Hide. This uses the same Hidden list as PCS Data Quick Navigation, so the rack disappears here and is Hidden there (and vice versa).
• Unhide: Click Hidden (N) — show above the map, then Show on a rack, or Show all on this PLC.
• Hide Empty Slots / Show Empty Slots: Toolbar toggle that hides empty slot placeholders (-- Empty --) on the Asset Map while keeping the rack/chassis visible. This is a view filter only — it does not change the Hidden list or Remove from BOM. Default is Show Empty Slots.
• Remove from BOM: Also on the right-click menu, matching the amber PCS Data toggle. The rack stays on the map; it is only excluded from Total BOM totals. Excluded racks are marked on the drawing with an amber dashed border, a cream background, and an Excl. BOM label suffix, and the tooltip / context menu call out the exclusion so it is obvious without opening the Data Viewer.

Lifecycle Status

• Green: Active
• Orange: End of Life / Limited
• Red: Discontinued / Obsolete
• Grey: Unknown

Creating Manual Links

This feature is essential when the project file does not define the link from a local communication card to a remote rack. It allows you to complete the diagram visually.

1. Hold down the Ctrl key (or Cmd on a Mac).
2. Click on a single communication module in the local chassis (e.g., a 1756-ENBT).
3. While still holding Ctrl/Cmd, click on one or more remote racks.
4. Click the Join Selected button. An orange dashed line will appear, linking the items. This connection is saved locally in your browser.
5. To remove a manual link, simply select the orange dashed line and click the Unjoin Selected button.

Exporting

• Export Current to PDF: Generates a high-resolution, A3-sized PDF of the currently displayed map.
• Export All to PDF: Generates a single PDF containing separate pages for the maps of *all* controllers found in your uploaded PCS files.

PCS Data Viewer

This tool provides a detailed, table-based view of the hardware from your uploaded PCS project files (`.l5x`, `.xhw`). It's ideal for inventory management and detailed analysis.

Key Features

• Controller Selection: Use the dropdown to switch between the PLC projects you've uploaded. Your selection is remembered and carried across to the PCS Asset Map and Ladder Viewer (and back), so you don't have to re-pick a controller each time you move between them.
• Hide / Show racks: The Hide ⚫ buttons in "Quick Navigation" or next to each rack — or right-click a rack on the PCS Asset Map — remove a rack from view and from the Bill of Materials. Because the state is shared, a rack hidden here also drops out of the PCS Asset Map and Architecture Comparison, and hiding from the map updates this page.
• Remove from BOM (keep visible): The amber Remove from BOM ⚫ button excludes a rack from the Total Bill of Materials only — the rack stays fully visible in the tables and on the maps, and is tagged with an "Excluded from BOM" badge. On the PCS Asset Map the same racks also show an amber dashed border and an Excl. BOM label. Use it for spares or comms racks you don't want counted in the materials total. A note under the Total BOM shows how many visible racks are excluded, and the exclusion also applies to the PDF / "Export All" totals.
• Highlight a module across racks: Click any catalogue number — in the Total BOM, a per-rack BOM, or a rack slot row — to highlight every matching module throughout the racks (click again to clear). Clicking from a BOM jumps to the first occurrence in the racks. Ideal for answering "where are all my Discontinued 1756-CNB/E cards?"
• Accurate chassis counting: Each rack is a distinct BOM line (chassis catalog from the L5X Module tree when known, otherwise the rack name — e.g. Peer_Peer remote chassis). Slot modules are listed separately, including remote Slot 0 adapters (CNB, ENBT, AENTR, …) — each remote rack's adapter is a physical card and is counted in addition to any matching local scanner.
• Lifecycle Status Dots: Each component shows a coloured dot for its lifecycle status (see the legend in the PCS Asset Map section).
• Exporting: Export the hardware data for the current PLC:
  • Export Report as CSV: a full component listing for every visible rack (a BOM-excluded rack's modules are still listed — only the aggregated total omits them).
  • Export Report as PDF: a professional PDF with a summary Bill of Materials plus a detailed table per visible rack.
  • Export All Reports: the PDF report for every controller, combined.

PCS CPU Report

A fleet-wide controller resource table built from your uploaded .L5X files. Each row blends the static profile (processor, firmware, nominal memory, tasks, program/routine and code size) with the Online Snapshot — real CPU utilisation, memory usage and connection counts — from the last time the project was online, decoded from Rockwell's L_CPU_20 / L_CPU_10 AOIs. Controllers without the AOI (or exported without decorated data) show their static profile only; nothing is fabricated.

What each row shows

• Processor & firmware, nominal memory, and task count.
• CPU Act%, D/L and I/O memory used, and connections (current / allowed) — colour-coded green / amber / red as they approach their limits.
• Tags, Standard (S88 / v4 chip), Source protection, and whether an Online Snapshot was found.

Detail drill-down

Click any controller row to expand a full breakdown — static profile, task configuration, a CPU-consumer breakdown, memory pools, connection detail, and the snapshot identity (reported processor, serial, time slice, minor fault count). Use Search Controller and the Snapshot filter to narrow the fleet, then Export CSV, Export PDF (page 1 is the KPI overview; following pages are the same per-controller detail as a row click), or Rebuild to regenerate the dataset.

PCS Fleet Health

A single consolidated view across every loaded controller, derived from the same fleet dataset the PCS CPU Report builds (open the CPU Report once, or this page will build it from your .L5X files automatically). Everything is grounded in parsed data or the uploaded Lifecycle CSV — where a figure is absent it shows "-" rather than guessing.

Risk register

Flags controllers that need attention: source-protected (encrypted) programs, controllers with no online snapshot, and any nearing their connection / CPU / memory limits (warning at 80%, critical at 90% — tunable in the code). Inhibited tasks and non-S88/v4 standards are flagged for review.

Obsolescence

Each controller's processor is matched against your uploaded Lifecycle CSV: "End of Life" / "Discontinued" show as critical, mature / NRND as a warning, Active as OK. Firmware is shown for planning. Processors not in the Lifecycle list are shown honestly as "Unknown" — upload the Lifecycle list on the Home hub to populate this.

Spare capacity

Headroom from the online snapshot per controller: spare connections, free CPU, memory used (D/L and I/O), and module count. For per-card used-vs-spare channels, use the I/O Card Utilization tool.

Filters & export

• Search by controller or processor, or filter to just risk / obsolete / no-snapshot controllers.
• Summary tiles at the top give an at-a-glance count of controllers, critical risks, obsolete units and encrypted controllers.
• Export CSV writes the full per-controller health summary for reporting.

Ladder Logic Viewer

A code reader that renders Relay Ladder Logic as proper ladder diagrams, drawn directly from the L5X. It shows contacts (XIC/XIO), coils (OTE/OTL/OTU), branches, and instruction boxes (timers, counters, math, MOV, AOIs, etc.), annotated with each operand's tag description.

Loading logic

• From your uploaded project: the "Load from uploaded project" dropdown lists the controllers already loaded on the Home hub. It follows the shared controller selection, so it opens on whichever controller you last chose in PCS Data / the Asset Map — no re-uploading.
• Ad-hoc file: drag-and-drop (or click to browse) any .L5X / .xml file that isn't part of the loaded project.

Reading the ladder

• Logic is grouped by Program → Routine → Rung; click a program or routine header to expand / collapse it, or use Expand All / Collapse All.
• Toggle Show descriptions and Full tag names, search rung text, and filter by program / routine.
• 🖨️ Print produces a clean, diagram-only printout.

Controller Tag List

The 🏷️ Tag List button opens a slide-over tag browser, like the RSLogix Controller Tags window:

• Lists every tag with its Scope (Controller first, then per-program), Name, Data Type, Description, Initial Value (from the last L5X save — Decorated / L5K data; hover for a fuller detail string), and a Used count of references in the ladder.
• Expand a base tag (▸) to see its members — UDT members are resolved from the L5X data types (nested and hidden-packing members handled), and TIMER / COUNTER / CONTROL / MESSAGE members are built in. Each member has its own usage count; expanded UDT members can show their initial values when present.
• The filter searches members too: typing DN or Speed surfaces the parent tag with the matching sub-member auto-expanded.

Where Used & jump-to-rung

1. Right-click (or click) any tag or sub-member and choose 🔎 Where Used to list every rung that references it, as Program / Routine — Rung N with the rung text.
2. Click a result to jump straight to that rung: its program and routine expand, it scrolls into view, and it stays highlighted in red so you can see exactly where you landed.
3. If it's the wrong rung, use the floating ◀ Results button (bottom-left) to reopen the Where-Used list — the rung you're on is marked "◀ here" — and pick another. Press Esc to close the panel or menu.

Bingo / Matrix arrays

Step-matrix arrays (Rockwell S88 phase logic: *MatrixA, *FaultMatrix, *FaultMons) render as bit-array tables the same way as the FD tool's Bingo section — one row per step, one column per bit, with the raw decimal value and step time on the right. DINT (32-bit), INT (16-bit) and SINT (8-bit) matrices are all recognised.

• 🎯 Bingo in the top toolbar opens a slide-out panel with every matrix in the current controller. The Search tags… box highlights matching column labels; unrelated tables dim. When the term also appears in the ladder, a Find in code ↓ (N) button surfaces — click it to filter the ladder down to those rungs.
• Each routine header that references at least one matrix gets a smaller 🎯 Bingo pill (with a count if more than one). Click it to open the drawer scrolled to just that routine's matrices — unrelated matrices dim automatically via the routine's common tag prefix (e.g. C1005).
• Bit labels above each matrix are auto-derived from the code: the tool finds the MOV(…Matrix[i], DecodeWord) rungs, then scans every DecodeWord.N reference to guess a name for bit N. Blank columns aren't referenced anywhere in logic. Click any label to search that tag.
• Step Time column pulls from the matching *StepTimes array if present — the timer preset is that value × 1000 ms.
• The ✕ close button and clicking outside the panel both dismiss it. Press Esc as usual.

PCS Tag Search

A tile-based search of every tag in every loaded PLC. Enter a partial tag name, description, or type in the search box — results narrow live as you type. Each tile expands to show the tag's UDT/AOI structure with per-instance comment overrides.

What each tile shows

• Tag name, DataType, and Description from the L5X, plus the PLC and scope (Controller / program-name).
• EU Range — automatically detected from named LowEngineer/HighEngineer UDT members, with the field names it read.
• Sub-tags — expandable list of UDT/AOI members with their DataType, per-instance description (if overridden via <Comment Operand>), and decoded value.
• I/O address rows — Rack, Slot, Channel, and module catalog. Each row is badged with the detection source (see below).

How I/O is detected

Not every I/O tag is a direct alias. The Tag Search scans four kinds of reference:

• ALIAS — the tag's AliasFor is a direct module path (Rack:Slot:I.Data.Ch).
• MOV — a MOV, COP, or CPS instruction pairs the tag with a module path.
• BIT MAP — an XIC/XIO to OTE/OTU/OTL/OTM rung wires the tag through to (or from) a channel bit.
• AOI:name — a custom Add-On Instruction passes the tag alongside a module reference.
• ST — a Structured Text := assignment couples the tag with a module path.

Direction-aware I/O display

By default the tile only shows I/O rows whose type matches the tag's inherent direction:

• A Solenoid_Output tag shows only the :O rows — not the same-slot :I feedback surface that every Rockwell output card exposes.
• An AnalogIn_CardScaled shows only the :I channel — not the :C config row that ladder COP distributes on startup.
• Within a matched direction, channel-specific rows are preferred over channel-less "just rack/slot" phantom references.

When rows are hidden, a small "N other references hidden" note appears under the tile so nothing is silently swallowed. Tick the Verbose I/O checkbox in the filter row to see every raw reference (Config + wrong-side + channel-less).

Filters & export

• PLC and Type (UDT / AOI / atomic) dropdowns.
• Has EU Scaling and Has I/O Address checkboxes for quick narrowing.
• Verbose I/O — disables the direction filter for the current view.
• Rebuild Index — re-parses all L5X (only needed after new files are loaded on the hub).
• Export Results (CSV) — exports the currently filtered set, with one row per tag including its primary I/O reference and all reference details.

The first index build parses every L5X sequentially with a progress bar — on a fully loaded plant this takes a handful of seconds. Subsequent visits reuse a LocalForage cache keyed to the loaded file set, so page loads are instant unless files changed.

PCS I/O Card Utilization

Replaces the older comment-per-channel view. For each I/O module in each controller, the page shows a real utilisation figure: how many channels have at least one tag mapped to them out of the card's total channel count. Only physical I/O modules (and module Connection comments) appear here. Produced/Consumed bit aliases and MSG send/receive buffers are shown on PCS Messaging, not as fake “Tag Aliases” cards.

What counts as "used"

• A channel counts as wired only when a real controller/program-scoped tag is mapped to a specific channel — via alias, MOV, XIC/OTE bit-map, AOI parameter pass, or Structured Text assignment.
• Only the tag's own direction is credited: an AnalogIn tile does not inflate an output card's utilization from its incidental fault-bit reference on the same slot's :I side.
• CONFIG references (:C paths) never credit utilization — they're startup defaults, not wiring.
• Unknown module catalogs report "used channels" only, without inventing a total. The scanner will not fabricate a denominator it can't verify.

Reading a card row

• Left stripe colour: green = Input card, red = Output card.
• Utilization %: red means no spare channels (100% committed — concerning); yellow is 40–79% (getting tight); green is under 40% (plenty of spare). The colour scheme is deliberately opposite to a test-coverage scale — utilisation isn't a score to maximise, it's a capacity-remaining indicator.
• Channel map: coloured grid, one square per channel. Green = wired (hover for the tag name + description), grey = unused, red = multi-tag on one channel, grey ? = unknown catalog with wired channels detected.
• Show tags: click to expand a table of channel → tag(s) → description for the card.

Filters

• Controller, Catalog, and Direction (Input / Output / both).
• Min / Max Utilization % — update live as you type. Set 80–100 to surface fully-committed cards, or 0–20 to surface spare-heavy cards.
• Search Tag / Description — find the card containing a specific tag (e.g. type FCV3130 to jump to the card that has it wired).
• Has spare channels and Fully utilised (100%) checkboxes.
• Include unknown catalogs — catalogs not in the built-in lookup (see below) are hidden by default; tick to include them (they'll show used-channel counts only).

Supported module catalogs

Channel counts are known for 55 validated Rockwell catalogs across ControlLogix (1756), FLEX (1794), and POINT (1734):

• 1756 Digital Input: IA16, IB16, IB16D, IB16I, IB32, IH16I, IH16ISOE, IM16, IN16, IV16, IV32.
• 1756 Digital Output: OA8, OA16, OB8, OB16, OB16D, OB16E, OB16I, OB32, OH8I, OW16I, ON8.
• 1756 Analog Input: IF6I, IF8, IF8H, IF16, IF16H, IR6I, IR12, IT6I, IT6I2, IT16.
• 1756 Analog Output: OF4, OF6CI, OF6VI, OF8, OF8I, OF8H.
• 1794 FLEX: IB16, IB32, OB16, OB16P, OB32P, OW8, IE8, IE12, IF4I, IF8IH, IRT8, OE4, OE8, OF4I.
• 1734 POINT: IB4, IB8, OB4, OB8, IE4C, IE8C, OE2C, OE4C.

Any other catalog will show up in the "unknown" bucket — used channels are still counted honestly, but no total or percentage is reported.

Summary tiles & export

The tiles above the card list show, for the currently filtered view: total cards, total channels on known-catalog cards, wired channels, and overall utilisation. Set a filter to see per-plant or per-catalog totals live.

Export CSV saves the current filtered set as one row per card — PLC, rack, slot, direction, catalog, module name, total & wired channels, utilisation %, wired-channel list, and sample tags.

PCS UDT/AOI Report

Consolidates two features that used to be separate hub buttons: the UDT/AOI Summary Report and the S88 Version Compare. Same underlying extraction as the old exports, same Excel workbook output — now viewable on-page with the same column layout and cell colouring.

Summary Report tab

For each controller you select, an Excel-look table lists every UDT and Add-On Instruction with:

• Type — UDT (green badge) or AOI (cyan badge).
• Name and Description.
• Usage Count — how many tags in the controller use this type.
• Revision and Last Edited (AOIs only; UDTs don't carry revision metadata).

The Search box narrows by name or description as you type; the Type dropdown filters to UDT-only or AOI-only. Click any column header to sort ascending; click again for descending. Export to Excel produces one workbook with one sheet per selected file, using the same column widths as the previous hub export.

Encoded AOIs (source-protected) are captured the same as visible AOIs — the definition metadata is still in the L5X even when the ladder is encrypted.

S88 Version Compare tab

Pick one L5X as the Master template (a shortlist auto-selects files whose name matches template, s88, master, or standard), then tick the site controllers to compare against it. The comparison runs live — no separate "Run" button.

Match Summary tiles at the top show, per site: matched %, matched / mismatch / not-in-master / not-in-site counts. This mirrors the REPORT_SHEET tab of the old workbook.

Full Comparison table shows every unique UDT/AOI name across master + all sites, with side-by-side Usage, Revision, Last Edited, and a Status cell per site:

• OK — type exists in both master and site, revisions match.
• MISMATCH — exists in both, revisions differ (mismatched revision cell is also highlighted).
• NOT IN MASTER — site has it, master doesn't (site-specific extra).
• NOT IN SITE — master has it, site doesn't (missing coverage).

The Row filter dropdown narrows to a single status class (typically Only mismatches) so you can focus on drift.

Export to Excel produces the identical workbook the old hub button did: S88_Compare + S88_MISMATCH + REPORT_SHEET sheets, same column widths, same percentage formatting.

PCS Messaging & Produced/Consumed

This page reads the same data you load on the Home page (no re-upload needed) and shows how your controllers exchange data. Everything is built from the Produced/Consumed tags and MESSAGE instructions inside the uploaded .l5x files.

Overview & Status

The summary cards show how many controllers are loaded, how many Produced/Consumed links exist, how many resolve within the loaded set, and how many MSG blocks were found. Each link is one consumed tag — the consuming controller pulls a Remote Tag from a Producer. Links are flagged:

• resolved — the producer and the produced tag were both found in the loaded files.
• missing — the producer is loaded, but it does not actually publish that tag (a likely misconfiguration worth checking).
• external — the producer controller is not among the loaded files (load that PLC to resolve it).

Tip: Load all of your controllers on the Home page so cross-controller links resolve. Anything still showing external just means that producer's L5X hasn't been loaded.

Network Diagram

• Nodes are controllers (solid = loaded, amber dashed = referenced but not loaded). Arrows point from producer to consumer; edge thickness is the number of tags; colour shows status (green resolved, red missing, orange-dashed external).
• Click a controller to highlight only its connections and fade the rest. The same selection also filters the Produced/Consumed tables below. Click empty space or Reset view to clear. Drag nodes to rearrange and scroll to zoom.
• Publish to PDF: Export full diagram (PDF) saves the whole network (A3 landscape). To document a single controller, click its node first, then Export node report (PDF) — this builds a full multi-page report for that controller (see below).

Per-controller PDF report

Select a controller in the diagram and click Export node report (PDF) to generate a multi-page A3 report for just that controller, containing:

• A focused diagram of the controller and the controllers it talks to.
• Consumed by <controller> (incoming) — every block it pulls in, with producer, tags, type, RPI, status and description.
• Individual tag data — for each incoming block, the full bit/word/real cross-reference (Element, Type, Alias Tag, Description, and the routine(s) each element is used in), plus the "whole block referenced in…" line.
• Produced by <controller> (outgoing) — every block it publishes and which controllers consume it.
• MSG blocks defined in that controller.

For a large controller this can take a few seconds to build (it indexes that controller's routines) and can run to several pages. The button shows "Generating…" while it works.

PLC-to-PLC Matrix

A grid where rows are producers and columns are consumers; each cell shows the number of tags flowing that direction — a quick view of who feeds whom.

Produced / Consumed Links

• Filter by Source, Destination, Status, or by text in the tag/description.
• Sort any column by clicking its header (a faint ⇅ marks sortable columns; click toggles ascending ▲ / descending ▼). RPI sorts numerically and tag names sort naturally.
• Bit/Word/Real Xrefs column shows how many elements are documented for each link (used by the ▶ expansion).
• Export links — CSV downloads the current link list; Excel exports an Overview sheet plus a Bit Level sheet.
• Live counts show immediately on page load.

Bit / Word / Real Cross-Reference

Click the ▶ on any link row to expand it and see how that comms block's data is used inside the consuming controller. For each documented element it lists:

• Element (e.g. ...Txi[0].21 for a bit, ...Txr[1] for a word/real) and its Type (Bit, Word, or Real).
• Alias Tag — the friendly tag mapped onto that bit/word, if one exists.
• Description — from the block's per-element comments.
• Used in Routine(s) — the Program/Routine path and the ladder rung numbers that reference that element (via its alias or directly), plus a "whole block referenced in…" line for the COP/copy that distributes it.

The first time you expand a block on a large controller, it parses and indexes that controller's routines, which can take a second or two; after that it is instant. If a controller's logic is FBD/ST (not ladder), elements may show "not used in ladder".

MSG Message Blocks

Lists every MESSAGE (MSG) instruction config: controller, MSG tag, message type, Local Element (the local data buffer — e.g. MK_TR1_D_Send[0]), buffer type (e.g. INT[20]), Remote Element, requested length, connection path, and service code. Click a row to expand the same bit/word/alias cross-reference used for Produced/Consumed blocks. CIP Data Table Read/Write on a peer that has no MSG of its own still appears here on the sending PLC (path + remote element). Sortable headers and an Export MSG to CSV button are provided. Ladder Viewer MSG boxes also show these MessageParameters under the control tag. PID/PIDE boxes similarly show SP, KP/KI/KD, limits and mode bits from the control structure.

Offline note

The diagram uses js/vis-network.min.js and the PDF export uses js/jspdf.umd.min.js. Both ship locally, so the page works fully offline once those files are in your js/ folder.

PCS Version Compare

Compare an older Version A against a newer Version B from the files already loaded on Home (they stay side by side in storage). Unity (.zef/.xef/.xbd) comparison is a later iteration — this build compares L5X.

How to use

1. Load both exports on Home (use Add to existing if a project is already open). Prefer distinct filenames when controller names match.
2. Open PCS Version Compare, pick Version A (older) and Version B (newer), then review the summary chips.
3. Use the Show checkboxes to focus on I/O, Hardware, Code, Initial values, and/or Asset map.

What is compared

• Hardware — modules added, removed, or changed (catalog / parent / slot).
• I/O channels (by tag) — wired tag↔channel moves, renames by description, adds and removes.
• Code — routines added/removed, and modified routines as side-by-side ladder (or text) with optional descriptions and fit-width.
• Initial values — controller- and program-scoped tags whose Decorated/L5K initial data (from the last L5X save) differs. Aliases are skipped. Same value source as the Ladder Viewer Initial Value column.
• Asset map — two independent PCS network drawings (A | B), same engine as the Asset Map page. Pan and zoom each; lifecycle border colours apply. Compare maps show every rack in each file (they do not apply BOM Viewer “hidden” curation).

Initial value changes

• Tags are listed as expandable rows: Name — description (TYPE) [scope], with Changed / Added / Removed badges.
• Expand a tag for an element list like Controller Information / All Tags — e.g. [0] (REAL): 16 // Steam Header Pressure High Alarm Setpoint. Changed members show A → B; unchanged members stay a single value. Element comments and tag descriptions appear when present in the L5X.
• Filter tags — live substring filter (e.g. type Vars) with a showing count and Clear.
• Export CSV — one row per element/member with Change, Scope, Tag, Tag Description, Tag Data Type, Element, Element Data Type, Value A, Value B, and Element Description. Exports the full Initial Value diff (not only the filtered view).

If pane B looks missing on a narrow window, widen the browser — A and B share equal columns. Hard-refresh after an update if an older cached page is still open.

Lifecycle Data Management

This page displays the contents of the Lifecycle CSV file you uploaded on the Home page. This data is used to determine the status colors shown in the PCS Data Viewer and Asset Maps.

• View Data: See the raw mapping between Model/Part Number and Lifecycle Status.
• Search: Filter the table to find specific entries.
• Clear Data: Click Clear Lifecycle Data to remove the current lifecycle information from the browser's storage. You will need to re-upload a CSV on the Home page to add new data.

Parser & FD Generator Tools

Help for the L5X Tag Parser, Functional Description (FD) Generator, and Pattern Validator.

<script>
(async () => {
  if ('storage' in navigator && navigator.storage?.persist) {
    if (!(await navigator.storage.persisted())) {
      console.log('Persistent storage granted?', await navigator.storage.persist());
    }
  }
})();
</script>

[XIC(MB1_RUN) OTE(FF5.Run) ,OTE(FF5.Isolator) ,JSR(_sbrDriveVFD_Digital,1,FF5,FF5) ,XIC(FF5.Out) OTE(MB1_Out) ];

<Pattern>
  <RegexString>...</RegexString>
  <ReturnPattern>...</ReturnPattern>
  <Type>...</Type>
  <ExtendedInfo>...</ExtendedInfo>
</Pattern>