Stop Python 3 syntax from sneaking into Ignition scripts.
Ignition 8.1 scripting is Jython, not modern CPython. This skill keeps the AI honest about syntax, scope, system.* functions, tag quality, datasets, logging, and readbacks. The current toolkit is tested around Ignition 8.1.53 / Jython 2.7.3.
Why it was made
- Prevents f-strings, walrus operators, Python 3-only APIs, and CPython package assumptions.
- Keeps Perspective, Gateway, Designer, tag-event, and project-library scopes separate.
- Makes older 8.1 projects verify script compatibility in their own Designer/Gateway instead of assuming every minor version behaves the same.
- Pushes QualityCode checks, readbacks, dry-run paths, and logs before trusting tag or database work.
Common use cases
- Project Library helpers that multiple Perspective views can call.
- Perspective button scripts, message handlers, transforms, and custom methods.
- Gateway timer, startup, shutdown, and tag-change scripts.
- Tag read/write, tag configure, dataset, Named Query, and historian helpers.
- Reviewing customer scripts for scope, syntax, Python 3 drift, and unsafe writes.
Proof style
Validate the artifact, not the promise.
The skill treats compile success as only the first gate; behavior still needs tag, query, or log readback in the target Ignition build.
Evidence
Jython validation proof
The graphic is AI-generated for the site. The checks below come from sanitized scriptEval runner evidence: dry-run compile checks, Gateway-scope execution, checked tag reads/writes, bad relative-path probes, dataset readback, and guarded input validation. This is compatibility evidence, not proof every customer script is production-ready.
- scriptEval compiled a Gateway-scope Jython 2.7 fixture before execution.
- The execution path used configurable fully qualified tag paths, checked readBlocking/writeBlocking results, and verified command readback.
- Gateway-scope probes showed relative tag paths such as [~] and [.] are not portable assumptions in that context.
- An unsafe path segment was rejected before any tag path was used.
- A dataset-tag run verified BasicDataset readback, safe access patterns, filtered output, and missing-column handling.
Example prompt
Use the Ignition Jython Script Builder to create a Project Library helper and thin Perspective button event. The helper should check an interlock tag, write a command tag only when allowed, support dryRun, log the result, and verify readback. Use placeholders for provider, root path, project name, and script path.This is the kind of short instruction the skill is designed to make useful. The value is in the checks and Ignition-specific defaults the AI uses after reading the skill.
Expected output
- Produces Jython 2.7-compatible code with no Python 3-only syntax or CPython package assumptions.
- Keeps the Perspective event thin and moves the real logic into a Project Library helper.
- Uses checked readBlocking/writeBlocking patterns, QualityCode checks, logger calls, dry-run output, and readback verification.
- Returns a clear result object the UI can show without pretending the click succeeded.
Related workflows
Skills that pair with this one
Lifetime membership
Want access to this skill?
The one-time membership unlocks this skill, the full Ignition AI Toolkit, the Web Dev runner materials, setup docs, versioned downloads, and future Ignition 8.3 skills as they ship.
No subscription. Lifetime members keep portal access to the current toolkit and future skill releases, including planned Ignition 8.3-focused skills as they are added.