PLC Simulator
Facts 2026-10-04.1
Reviewed 2026-10-04

What changed and when

Product and facts changelog

Dated capability changes and corrections, with product-facts versions separated from marketing copy.

Run the no-account exampleView facts JSON

Changelog scope

Dates below describe source changes that affect public product behavior or product claims. They are not a promise that every staged feature was visible to every account on that date.
Learning evidence and facts 2026-10-04.1
  • Documented partial-program practice, behavior-based scenario completion, progressive help and instructor evidence as one public methodology.
  • Added the reusable VFD function-lab facts and synchronized 2D/3D device boundary to the machine-readable product record.
  • Corrected the dialect documentation to include the ninth KEYENCE KV learning track.
KEYENCE KV learning track
  • Added a ninth runnable learning dialect with KV-style R/MR/DM devices, inverse contacts, SET/RES, timers, counters and arithmetic.
  • Added twelve KEYENCE lesson paths, editor highlighting, sandbox export, comparison examples and public reference vectors.
  • The implementation remains a tested educational subset, not KV STUDIO project-file support or controller-firmware emulation.
Product facts 2026-10-04.1
  • Published a versioned facts artifact with 170 published scenario records, 32 source-tagged free-tier records and 9 dialect tracks.
  • Separated no-account trial access, free-account catalog access and source registry counts.
  • Replaced retired 40/130+/three-dialect claims on priority acquisition surfaces.
3D factory component release
  • Added a public component library and isolated component previews.
  • Kept 3D claims bounded to training scenes rather than production digital-twin validation.
Electrical troubleshooting assessment
  • Added scored fault-diagnosis practice and linked the troubleshooting surfaces.
  • Kept the browser lab positioned as supervised training, not authorization for live electrical work.
Activation and conversion measurement
  • Instrumented simulator activation and conversion paths so acquisition pages can be evaluated beyond clicks.
Mobile HMI and wiring workspace update
  • Improved responsive HMI and wiring workspaces and restored structured-text learning surfaces.
  • The limitations page now states that complex editing is still best on a larger screen.

Current facts receipt

Facts version
2026-10-04.1
Reviewed
2026-10-04
Schema version
1
Machine-readable source
product-facts.json

Found a mismatch?

Send the URL, facts version, expected behavior and observed behavior. Product and documentation corrections are reviewed together.

Report a correction

Technical reference and worked-example guide

PLC Simulation Software changelog: field reference

Direct answer

The reader can interpret release entries by affected surface, behavior, migration need, limitation and a reproducible post-update verification case.

Written for learners, instructors, evaluators and customers checking what changed, when it changed and whether a saved workflow or teaching plan needs retesting.

a controls engineer comparing a plant simulation model, physical training cell, PLC evidence and versioned test records while studying product change history, compatibility and verification
System map / 02

NODE 01observable

Definition

Release date and identifier, affected feature, user-visible behavior, compatibility, migration, known limitation, rollback or support path and verification reference.

NODE 02observable

Signal path

Code or content change through build, deployed route, browser behavior, saved state, test evidence and user-facing release note.

NODE 03observable

Worked example

One affected workflow repeated before and after the update with the declared result and retained artifact.

NODE 04observable

Limits

Stale cache, old browser tab, saved-project version, removed assumption, mobile layout, account tier, rollback and partial deployment.

NODE 05observable

Common mistake

A release-note, version, deployment, cache, migration, saved-state, compatibility, test or communication mismatch.

NODE 06observable

Verification

Entries kept attributable to passing tests and corrected when observed production behavior differs.

Answer surface / 07

What should a software changelog explain?

It should state when a change shipped, what users can observe, who is affected, any migration or limitation and how the result can be verified.

Should I retest saved PLC projects after an update?

Retest the workflows named by the release and any critical saved behavior, especially where parser, runtime, persistence or scenario logic changed.