Release v4.0.1

[4.0.1] - 2026-07-29

• Release: Bumped npm package and lockfile metadata to 4.0.1.
• Release: GitHub Release drafts now prepend this version's changelog section to generated notes and repair a missing section on workflow reruns.

BREAKING

• Library: Removed the undocumented getProfileFeature root export. Capability feature records remain internal implementation data.
• Library: Malformed qualified addresses with repeated separators are now rejected instead of being normalized implicitly.

Changed

• Library: Simplified named-address dtype normalization by removing a redundant internal wrapper and its unused device argument.
• Library: Device profile upper bounds no longer reject sends in the communication library; syntax, supported-family, command-limit, and wire-width checks remain.
• Docs: Added the existing public availablePlcProfiles() connection-profile enumeration contract to the API reference.
• Tests: Added coverage that availablePlcProfiles() excludes base-only profiles and returns an isolated array.

Fixed

• Library: Public validation failures now use the exported ValueError, and successful node processing clears a stale msg.error value.
• Library: J link-direct extended random read/write and monitor registration now select Q/L subcommands and 11-byte entries; mixed Q/L and iQ-R extended layouts are rejected before transport.
• Node-RED: Closing a connection node during connect or reinitialize now closes any newly opened socket and prevents the closed node from returning to connected state.

What's Changed

• Close completed release acceptance records by @fa-yoshinobu in #41
• Remove unused SLMP internals by @fa-yoshinobu in #42
• Fix Node-RED SLMP validation and link-direct layouts by @fa-yoshinobu in #43
• Release 4.0.1 with changelog-backed GitHub notes by @fa-yoshinobu in #44

Full Changelog: v4.0.0...v4.0.1

Release v4.0.0

v4.0.0 changes

• Release: Bumped npm package and lockfile metadata to 4.0.0.

• Library: Added immutable lifetime traffic snapshots through SlmpClient.trafficStats().

• Library: TCP and UDP responses now require an exact network, station, module I/O, and multidrop match with the snapshotted request target. Structurally valid foreign-route responses are discarded within the original request deadline; malformed responses invalidate the transport.

• Library: Every request timeout now retires its complete TCP or UDP socket generation, including 4E UDP, so delayed data cannot cross into an automatically reconnected request.

• Tests: Added deterministic TCP/UDP and 3E/4E response-correlation coverage, including every route field, foreign-route-only timeout, wrong-serial flooding, matching responses within the deadline, and malformed responses.

• Library: Added the public melsec:mx-r:rj71en71 profile with canonical capability and device-range behavior.

• Tooling: Refreshed canonical SLMP profile fixtures and runtime catalogs for 2026-07-14 and pinned imports to profile tag v2.1.0.

Release v3.1.0

v3.1.0 changes

• Library: Added public monitor registration/cycle, self-test loopback, and fixed Clear Error semantic APIs to the low-level SlmpClient.
• Library: Monitor cycle expected counts must total at least one and stay within the selected profile's monitor-registration limit.
• Library: Monitor cycles require explicit registered counts and never auto-register or retry; self-test verifies declared length, actual length, and exact echo against the transmitted Buffer snapshot.
• Docs: Clarified that U3En\HG never changes or retries the explicitly selected request target.
• Tests: Removed vendored cross-repository vector JSON and its dedicated runner. Cross-implementation comparison is executed independently of this Node-RED package.

BREAKING

• Library: SlmpClient now requires explicit port, transport, concrete plcProfile, and one complete target or defaultTarget; raw request subcommand and payload are required.
• Node-RED editor: Port 1025 and TCP remain only required initial values for a new connection
  node; saved/runtime port and transport are mandatory, and invalid values fail before client
  creation without fallback or transport switching.
• Node-RED editor: The four displayed own-station route values are initial values only. Saved
  connections require all four route fields, and a request route may be omitted as a whole or must
  provide all four fields; partial routes are never merged with defaults.
• Library: Removed public strictProfile, strict_profile, normalizeStrictProfile, profile-helper bypass, user-selected request series and 4E serial, localized end-code message hooks, and the :I, :STRING, and DSTR... address aliases. Profile-guard bypass remains only as a Boolean maintainer-internal constructor input.
• Node-RED: Removed the profile-guard checkbox. Old saved strictProfile: true is ignored safely, while false, aliases, null, blank, and unknown values fail with a migration error before client creation.
• Library: readDevices and writeDevices require Boolean bitUnit; Remote RUN requires Boolean force plus a discoverable RemoteClearMode value, and Remote PAUSE requires Boolean force.
• Library: Extended random APIs now derive route fields from qualified device text and accept only typed SlmpExtendedDevice Z/LZ/indirect modifiers. Raw extension objects, public raw extended encoders, and three-element write tuples are removed.
• Node-RED: Read/write source types, output/metadata/error modes, output count, runtime override shapes, and single-write dtype are now explicit and strictly validated. Single-write dtype must appear exactly once, either in the address or as an exact uppercase msg.dtype; double, missing, invalid, or incomplete selector forms fail before a client call. A present invalid runtime read/write property never falls back to configured addresses or updates.
• Node-RED: Connection/read/write name is optional display-only state. It is trimmed, non-string/blank input means no custom label, duplicates are allowed, and it never changes node identity, connection selection, routing, request bytes, or metadata.
• Node-RED editor: str remains the initial source type for a new read/write node, but missing or
  invalid saved addressesType/updatesType values are no longer silently repaired. Non-literal
  sources fail if their reference cannot be evaluated and never fall back to a literal address or
  update.
• Node-RED: A request route override may be omitted as a whole, but a configured route requires an
  explicit source type and one complete route object. Invalid message/configured routes no longer
  fall back to another source or the connection route; metadata records targetSource alongside
  the effective target.
• Node-RED: Read output shapes are fixed: object is always address-keyed, array is always an
  array, and value requires exactly one address; zero/multiple address values fail before the
  client call.
• Node-RED: Metadata modes are exact required values. Full/minimal output clears stale owned fields,
  identifies the current read/write operation, and preserves custom fields; off leaves existing
  msg.slmp untouched and does not represent it as current-result metadata.
• Node-RED: Error mode now uniquely defines the route and terminal count: throw uses no message,
  msg uses output 1, and output2 uses output 2. Saved terminal counts must be exact integers and
  coercible strings/Booleans are rejected as migration conflicts.
• Node-RED: Removed msg.slmpSkipUnsupported and msg.slmp.skipUnsupported. Legacy occurrences emit
  a migration warning but cannot turn a structured capability error into a successful skipped
  message or override the configured error route.
• Node-RED: Remote password use now requires the Use remote password checkbox; when enabled, the credential must be non-empty.
• Library: remotePassword omission or explicit undefined disables managed authentication. Explicit null, empty, non-string, non-printable-ASCII, or profile-invalid credentials now fail during construction; the password is no longer retained as a public client property.
• Library: Removed the public skipRemotePasswordLifecycle connection/request option. Managed unlock/lock uses a private command path and cannot be bypassed through normal or raw request options.
• Library: Explicit remotePasswordUnlock/remotePasswordLock commands are rejected on a client configured for managed authentication; use an unconfigured maintainer client for deliberate manual password commands.
• Library: Managed remote-password state is bound to the concrete TCP/UDP connection generation. A new connection unlocks before its first user command, transport failure invalidates authentication state without replaying the failed command, and an old TCP socket event cannot clear a newer connection.
• Library: close() always attempts local transport closure and now reports password-lock failure. Simultaneous lock and local-close failures are preserved through an aggregate cause; Node-RED shutdown logs the sanitized failure and still completes its close callback.

Added

• Library: Added profileDescriptors() for canonical SLMP profile metadata.

Changed

• Library: Random read keeps the unused word or DWord device list optional, rejects all-empty or invalid supplied collections before transport, and returns an explicit empty object for the unused result category.

• Library: Random word write keeps the unused word or DWord value list optional while rejecting all-empty, malformed, duplicate, overlapping, or invalid values before transport; random bit write remains a separate required-input API.

• Library: Block read/write keeps the unused word or bit block list optional, rejects all-empty or malformed inputs before transport, returns an explicit empty array for the unused read category, and rejects overlapping write ranges.

• Library: Communication timeout defaults to 3000 ms only when omitted; explicitly supplied timeout values must be integers in 1..2147483647 and invalid values are rejected without fallback. The monitoring timer defaults to four seconds (0x0010) only when omitted, accepts exact integers in 0..65535, and preserves explicit zero as PLC-side indefinite processing wait. It remains independent from the client communication timeout. TCP sockets enable keepalive after 30 seconds idle.

• Library: TCP connection setup now fails closed if no-delay or required keepalive configuration throws. The socket is destroyed, the connect promise rejects, and the transport never retains the partially configured socket.

• Library: raiseOnError now defaults to true only when absent and accepts actual Booleans only at connection and request scope. Strings, numbers, null, empty values, objects, and arrays are rejected before transport instead of being coerced.

• Library: The complete connection target is immutable for the client lifetime. Each queued request now validates and snapshots its effective target, monitoring timer, end-code policy, and payload at call time, so later caller mutation cannot change the destination or request bytes.

• Library: readNamed and writeNamed emit one protocol request or reject the complete operation before transport. Compatible random or multi-block word entries may share that request; mixed command families and bit-in-word writes no longer create hidden follow-up requests.

• Library: Remote RESET uses fixed subcommand 0x0000 and payload 0x0001, and completes after sending without waiting for a success response.

• Library: 4E serials are assigned internally and requests sharing one client are serialized.

• Library: UDP timeout detaches and closes the socket generation so delayed datagrams cannot satisfy a later request.

• Release: Bumped npm package and lockfile metadata to 3.1.0.

• Tooling: Pinned canonical SLMP profile imports to published profile tag v2.0.0.

Fixed

• Library: Random, extended-random, and block writes reject duplicate or overlapping destinations before transport.
• Library: Direct, random, extended-random, block, memory, and extend-unit write paths reject coercible strings, fractional values, Boolean-as-word values, truthy bit values, and out-of-range integers instead of masking or converting them.
• Library: writeNamed rejects overlapping word/DWord and normalized-address destinations; Extended Device random-read keys include Z/LZ/indirect modification so distinct operands cannot overwrite each other.
• Library: Send-only remote reset closes its transport generation after the frame is written, TCP busy rejection occurs before socket write, unlock failure preserves the primary error even when local close also fails, and LZ modifiers accept only index 0 or 1.
• Library: Removed inert end-code message properties; numeric end code, stable end-code key, structured error informati...

v2.0.0

v2.0.0

BREAKING

Short ModuleIONo aliases were removed in favor of canonical module I/O names.

Old name	New name
CONTROL_CPU, CONNECTED_CPU, DEFAULT	OWN_STATION
ACTIVE_CPU	CONTROL_SYSTEM_CPU
STANDBY_CPU	STANDBY_SYSTEM_CPU
TYPE_A_CPU	SYSTEM_A_CPU
TYPE_B_CPU	SYSTEM_B_CPU
CPU_1 to CPU_4	MULTIPLE_CPU_1 to MULTIPLE_CPU_4

Package Name

Registry	Package
npm	@fa_yoshinobu/node-red-contrib-plc-comm-slmp unchanged

Highlights

• npm package metadata bumped to 2.0.0.
• Added 008x extended random APIs and refreshed SLMP profile data.
• README links to the plc-comm package matrix.

Package matrix: https://fa-yoshinobu.github.io/plc-comm-docs-site/package-matrix/

Release v1.2.0

What's Changed

• [codex] Align SLMP guard policy by @fa-yoshinobu in #21
• [codex] Guard Q-series block access by @fa-yoshinobu in #22
• [codex] Fix SLMP spec audit findings by @fa-yoshinobu in #23
• [codex] Add SLMP profile capability guards by @fa-yoshinobu in #24
• [codex] Improve sample navigation and reconnect examples by @fa-yoshinobu in #26
• [codex] update SLMP profile limits v1.1.0 by @fa-yoshinobu in #25
• [codex] Add operational polling flow by @fa-yoshinobu in #27
• [codex] Document Node-RED CSV persistence recipe by @fa-yoshinobu in #28

Full Changelog: v1.1.1...v1.2.0

v1.1.1

[1.1.1] - 2026-06-29

Changed

• Release: Bumped npm package metadata to 1.1.1.
• Node-RED editor: Updated read/write address validators and placeholders to require explicit dtype suffixes such as :U and :BIT.
• Docs: Documented explicit SLMP address dtype requirements in existing user docs.
• Samples: Updated example flows to use explicit dtype suffixes.

v1.1.0

Changed

• Release: Bumped npm package metadata to 1.1.0 for stricter Node-RED input validation changes.
• Library: Made named-address parsing require explicit dtype suffixes such as :U, :S, :D, :L, :F, or :BIT; bare devices no longer default to U, BIT, or long-timer D.
• Library: Removed msg.payload fallback for read/write parameters; read messages must use msg.addresses, and write messages must use msg.updates or msg.address plus msg.value.
• Node-RED editor: Static write updates now require a JSON object; address=value line parsing and scalar value fallback are no longer accepted.
• Library: Write clustering now validates that every clustered slot has an explicit source value instead of filling unspecified bit/word slots with false or 0.
• Library: Removed embedded SLMP end-code message text; end-code helpers now return stable code-derived keys while message lookup hooks return undefined.
• Docs: Updated SLMP Node-RED usage guidance for explicit message fields, JSON-only static updates, and explicit dtype suffixes.

Fixed

• Library: Reject unknown dtype suffixes such as :BOGUS instead of treating them as word values.
• Library: Made BIT_IN_WORD helper addresses require an explicit bit index such as D100.0 through D100.F; D100:BIT_IN_WORD now fails in parseAddress, readNamed, and writeNamed instead of silently reading or writing bit 0.
• Tests: Added coverage for rejecting BIT_IN_WORD addresses without an explicit bit index.
• Tests: Updated high-level and node tests for explicit dtype requirements, unknown dtype rejection, no msg.payload fallback, JSON-only static updates, write-cluster slot validation, and non-embedded end-code messages.

v1.0.1

Changed

• Bump Node-RED package metadata to 1.0.1.
• Remove the legacy family profile alias from SLMP device parsing and high-level helpers.
• Require explicit PLC type selection in the Node-RED SLMP connection editor.

Fixed

• Align the UDP read/write example flow with UDP sample port 1035.

Validation

• npm test

Release v1.0.0

What's Changed

• [codex] release 1.0.0 alignment by @fa-yoshinobu in #18

Full Changelog: v0.8.0...v1.0.0

Release v0.2.14

Library release v0.2.14.

• Release metadata and changelog are updated on main.
• Local validation and package-content checks were completed before tagging.
• Package registry publication is intentionally left as the manual human step.