Zum Hauptinhalt springen
K

dsh-engineering

konnectsuite/dsh-engineering

AryaCode engineering bundle: Studio 5000 L5X, FactoryTalk View ME, FactoryTalk Optix, MotionWorks IEC, ECAD drawing reads and RSLogix 500/5 to Logix migration — one install, one row per toolchain.

Installation

dsh plugin --profile web add github:konnectsuite/dsh-engineering

README

AryaCode Engineering

Automation-engineering tools, skills and file viewers for DeepSeek Harness. One install gives an agent the surfaces an automation engineer works in: Studio 5000 (L5X and ACD), FactoryTalk View ME, FactoryTalk Optix, MotionWorks IEC 3, ECAD electrical prints (DXF and DWG), RSLogix 5 (PLC-5) reads, and SLC 500 / PLC-5 → Logix migration. DeepSeek Harness ships as AryaCode; the two names are the same host and this page applies to both.

npm downloads licence Arya plugin market

One bundle: 10 component rows · 190 tools · 6 products · every component is beta

The bundle is one npm package with one install surface. Inside it, each product is a row on the Plugins page: a row is a plugin, so switching one off unloads that product and its tool schemas stop being sent with every request. The components are deliberately fine-grained — one per toolchain — because that is how an engineer adopts them: Studio 5000 this week, Optix next month, ECAD when the prints arrive.

New here? Read Getting started, then open the page for the product you have in front of you.

What you get

ProductToolsDefaultStabilityWhat it addsNeeds
Studio 5000 L5X54onbetaRead, check, compare and document an L5X/ACD; stage ladder edits as a new file; optional Logix Designer SDK work; live EtherNet/IP reads and two approval-gated writesNode; a Logix Designer SDK only for SDK builds; a controller only for live
FactoryTalk View ME51onbetaRead an ME export, run structural checks, edit displays, tags and objects, validate against the vendor schema, and stage a Studio import handoffNode; FactoryTalk View Studio ME for discovery and the handoff
FactoryTalk Optix32onbetaRead and author a loaded Optix Studio project through a bridge, draw operator screens, write and compile NetLogic C#, drive the emulator previewOptix Studio; .NET 8 SDK for compile checks; Tesseract for OCR
MotionWorks IEC24onbetaOperate a running MotionWorks IEC 3 Pro IDE on the real project files: read, edit, compile, diagnose, verifyMotionWorks IEC 3 Pro 1.19
ECAD electrical prints12offbetaRead DXF prints and DWG through the embedded converter: title blocks, index sheet, cross-reference candidates, checks, layout render, compare, review bundleNothing to read; authoring stays in AryaCAD Electrical
SLC 500 and PLC-5 to Logix migration7onbetaAssess a legacy program, lint the .L5K the migration wizard writes, resolve its conversion markers, and write the report a person signs off fromNothing; reads .RSS/.ACH/.RSP or the .SLC export
RSLogix 5 (PLC-5) program reads8offbetaOpen a .RSP hidden and read program files, ladder, symbols, I/O footprint, chassis configuration and processor identityRSLogix 5 for the automation-server path; the container reader needs nothing
Engineering resources2onbetaA local standards corpus (IEC 61131-3, Rockwell, Yaskawa, HMI, Optix, craft rules) and a house-style profile of the open projectAn open L5X or ME project for the profile
Arya Automation Engineer preset0onbetaThe agent preset: engineering-tuned compaction, a work ledger and the five-step contractNothing
Ladder and display previews0onbetaThree file viewers: .l5x/.acd ladder, ME display .xml, and DXF/DWG drawingsNothing

Every component is beta until the bundle is declared 1.0: the tool sets and result contracts may still change between releases, and each component states in components.json what has actually been verified and what has not. Why each is beta.

Install

From the market: open Plugins → Arya Plugin Market → Engineering → Install. The bundle installs its own rows, components, viewers and preset; installing a component package on its own gives you tools without the rows that switch them.

Into a profile you manage yourself:

pnpm add @aryacode/dsh-engineering
// the profile's package.json
"dsh": { "profile": { "bundles": ["@aryacode/dsh-engineering"] } }

Per-row enable state lives in the profile, so a row you switch off stays off across updates.

Where it appears

  • Plugins page — ten rows, one per component or surface. Each row has its own Configure page: l5x, ftview, mwi, ecad (off), optix, resources, migration, plc5 (off), preset, and viewers (which mounts the package root and therefore shows the package name and description rather than a product title).
  • File viewers — three entries in Settings → File viewers: Logix project (.l5x, .acd), FactoryTalk View display (.xml), ECAD drawing (.dxf, .dwg). All three come from one browser bundle mounted by the viewers row; switching a product row off does not remove its viewer.
  • Preset picker — Arya Automation Engineer.

First session

Open the workspace folder that holds your export or project and ask in plain language; the agent picks the product's skill and tools. One prompt per product:

ProductSay this
L5X"Open Line.L5X, run the checks, and tell me what would fail a review."
FactoryTalk View"List the FactoryTalk View ME applications and check this export."
Optix"What is open in Optix Studio? Show me the project map."
MotionWorks IEC"Find the MotionWorks projects in this folder and open the line project."
ECAD"Review these drawing prints and give me the findings."
Migration"Assess this .RSS and tell me what the conversion will not carry."
PLC-5"Open this .RSP and give me the program census."

Each product page carries the ordered walkthrough and the boundaries: L5X, FactoryTalk View, Optix, MotionWorks, ECAD, migration, PLC-5.

Switches

A row is a plugin. Disabling it in the profile (or on the Plugins page) unmounts that product, so its tool schemas leave the request. Each product's expensive surfaces are config on the same row, so the cheap decision takes one switch and the fine decision lives one level down.

RowProductDefaultOptions
l5xStudio 5000 L5Xonediting, studio, live, allowWrites (all on)
ftviewFactoryTalk View MEonedit, studio (on)
optixFactoryTalk OptixonbridgeUrls, allowWrites, allowDestructive, allowInvoke, preview, allowPreviewInput, netlogic
mwiMotionWorks IEConworkspace (empty), edit (on)
ecadECAD electrical printsoffwrites (off), bridgeServerName, maxFiles, maxFileBytes, maxEntities
migrationLegacy → Logix migrationonassess, lint, compare, resolve, report, plan (on)
plc5RSLogix 5 readsoffthe eight read tools, one option each
engineering-resourcesStandards corpus and house styleonreference (on)
engineering-presetArya Automation Engineeronnone — the preset's own settings
viewersLadder, display and drawing previewsonnone

Two rows ship off: ECAD, a large surface many profiles do not need, and the RSLogix 5 reads, whose automation-server path wants that product installed. Both stay listed, so one switch enables them without a reinstall.

The default-on surface is budgeted, not accidental: components.json records the tools and the characters of model-visible schema a fresh install may mount (170 tools, 127,423 characters today), and a component that would exceed either ceiling ships off until the ceiling is raised with its measurement. The budget and the field set are documented in the component contract.

What it needs

  • Host: DeepSeek Harness or AryaCode, ^0.2.1-rc.3 || ^0.2.2-alpha.2 (declared as dsh.engines.dsh, so the market states the requirement on the card). Verified on AryaCode 0.2.2-alpha.2, installed from npm into a clean packaged profile: no import or activation error, the market reported the bundle live with diagnostics.findings empty.
  • Node: the bundle's own runtime is Node 22.19+ or 24+.
  • Vendor software is needed only for the surfaces that talk to it: Logix Designer SDK (optional), FactoryTalk View Studio ME (discovery and the manual import), FactoryTalk Optix Studio, MotionWorks IEC 3 Pro, RSLogix 5 for the automation-server reads, AryaCAD Electrical for ECAD authoring. Reads that work from files alone need none of them, and each product page states which is which.

Safety

  • Read-only by default. Reading, checks, comparison and the viewers never change a controller.
  • Edits write new files. draft_apply writes one new L5X beside the source and refuses to overwrite; ftview_apply writes a new export folder; MotionWorks edits write the real workspace project after one verified backup.
  • One backup tree. Every product backs up to <workspace>/backups/<product>/<subject>/<UTC stamp>/ with a backup-manifest.json naming each copied file and its SHA-256, so "back up this project" means the same place in every skill.
  • Controller changes need a human. Upload, mode change and download require per-call approval; a download accepts only the verification id produced by a passed build. Live tag and clock writes need the row's allowWrites switch and approval for that exact write, and report the value the controller reads back.
  • Coverage is stated. Every result names what it cannot establish — including whether online logic matches an export.

Skills

The bundle ships eight skills, each attached to the row that can act on it. The agent loads one when the work matches, so the tool schemas and the method arrive together: rockwell-l5x, factorytalk-view, factorytalk-optix, motionworks-iec, legacy-to-logix-migration, rslogix-5, ecad-review, engineering-standards. Each product page says when its skill engages, and the resource skill is cross-toolchain: it is what the other seven reach for when a question is about house style or a standard rather than a tool.

Known limits

  • Live reads, SDK builds and live writes cannot prove that online logic matches the export; every result says so in coverage.
  • FactoryTalk View import and runtime creation are Studio steps: the bundle exports through the vendor engine, authors and schema-validates the displays, writes the BatchImport manifest and verifies the import object by object afterwards, but does not import or build a .mer.
  • The vendor export does not include the HMI tag CSV, so tag bindings cannot be checked from a fresh export unless that database is exported separately.
  • The generated tool reference covers the 158 tools built from this repository; the 32 vendored Optix tools are not generated from source here, so their descriptions live in their own definitions and in the Optix pages.
  • ECAD support is measured, not assumed: cross-reference rows are candidates with a confidence, unsupported entities are reported per sheet, and geometry beyond the planar drawing assumption is reported as approximate. Proxy objects, ACIS bodies and xrefs remain unmeasured and are reported through the converter's diagnostics.
  • FBD and SFC semantics are not exercised.
  • All ten components are beta, and each one records in components.json what is not proved yet.

Documentation

Start here: Getting started · Documentation map · Architecture

ProductPages
Studio 5000 L5XL5X · Live controller work
FactoryTalk View MEFactoryTalk View · Cross-referencing HMI to PLC
FactoryTalk OptixOptix · NetLogic · Screens · Project model · Artwork · Production readiness
MotionWorks IECMotionWorks IEC
ECAD electrical printsECAD · AryaCAD bridge
MigrationSLC 500 / PLC-5 to Logix
RSLogix 5 readsPLC-5
Support and surfaceResources · Preset · Components
AreaPages
ReferenceEvery tool (generated) · Components · HMI design · Standards checks
EvidenceCapabilities, shown · Workflow handbook (PDF) · Examples
DevelopmentContributing · Packaging · Retirement · Changelog

Links point at GitHub because npm renders the README without the repository's other files.

Development

pnpm install
pnpm -r build        # workspace packages (their lib/ is gitignored)
pnpm test            # the release gate: one child process per spec file
pnpm docs:tools      # regenerate docs/reference/tools.md and tools.json
pnpm docs:check      # fail when the generated reference is stale
pnpm check:package   # what the tarball ships, and how big it is
pnpm build:client    # rebuild the one browser bundle from its faces

The suite includes the prose-to-code contracts: a row id that the README does not mention, a component document that no page links, a tool a skill cites that no longer exists, a files entry that a mount would need but the tarball omits — each fails pnpm test. See Contributing and AGENTS.md for the rules that keep it that way.

Removing the bundle

Remove the row from the profile's bundle list (or disable it on the Plugins page), then pnpm remove @aryacode/dsh-engineering in the profile. Rows, viewers and the preset unload with it. Nothing the bundle wrote into a workspace is touched: drafts, exports, backups and .migration/ plans stay where they are.

Licence

MIT — see LICENSE. The tarball embeds third-party code (acadrust, the Optix bridge, upstream snapshots); every notice travels with it in NOTICE.md. Rockwell Automation, FactoryTalk, Studio 5000, RSLogix, Allen-Bradley, MotionWorks and Yaskawa are trademarks of their owners; this project is not affiliated with or endorsed by them.

Ähnliche Plugins