@fa_yoshinobu/node-red-contrib-plc-comm-slmp 0.2.13 → 0.2.14

package/CHANGELOG.md

@@ -1,8 +1,16 @@
 # Changelog
 
-## Unreleased
-
-## 0.2.12 - 2026-05-02
+## 0.2.14 - 2026-06-12
+
+- add an optional `Remote password` credential to `slmp-connection`; configured connections unlock remote-password protection after opening SLMP transport and try to lock it before disconnecting
+- add SLMP end-code name/message helpers backed by the full English communication error-code table, and expose remote-password end-code classification on `SlmpError`
+- add forced remote STOP support through `remoteStop({ force: true })`
+- fix `writeBlock()` payload layout so each `1406` block writes its data immediately after that block's device spec and point count
+- add maintainer notes for the resolved mixed `1406` layout root cause and current no-fallback behavior
+- clarify that `G` and `HG` are intentionally unsupported in the public Node-RED high-level surface, not pending TODO items
+- reject direct `G` and `HG` device names even when no `plcFamily` is supplied, keeping the public surface from sending unitless Extended Specification-only devices
+
+## 0.2.12 - 2026-05-02
 
 - bump the release revision for npm and Node-RED Flow Library publishing; the Flow Library currently shows `0.2.3` as the public baseline
 - refresh README, user-guide, latest-verification, and example-flow docs with compatibility notes from the published Flow Library version
@@ -19,8 +27,8 @@
 - remove stale user-guide and TODO wording that still described `LCS` and `LCC`
   as future support; the high-level helpers route reads through direct bit read
   and writes through random bit write (`0x1402`)
-- keep `G` and `HG` out of the default public device-matrix flow while they
-  remain routed-device follow-up items
+- keep `G` and `HG` out of the default public device-matrix flow because they
+  are not part of the public high-level surface
 
 ## 0.2.10 - 2026-04-27
 

package/README.md

@@ -35,7 +35,7 @@ This package is documented for the high-level Node-RED workflow only:
 ## Quick Start
 
 1. Install the package into your Node-RED user directory and restart Node-RED.
-2. Add one `slmp-connection` config node and set `host`, `port`, `transport`, and `PLC type`.
+2. Add one `slmp-connection` config node and set `host`, `port`, `transport`, and `PLC type`. If the route is protected, set `Remote password`.
 3. Add `slmp-read` for the first smoke test, using a safe address such as `D300`, `D300,4`, or `DSTR320,10`.
 4. When read works, add `slmp-write` and use known-safe test devices before moving to production addresses.
 
@@ -51,7 +51,7 @@ Start with `D` word devices for the first smoke test. Do not start with `slmp-de
 ## Release Information
 
 - package name: `@fa_yoshinobu/node-red-contrib-plc-comm-slmp`
-- package version: `0.2.12`
+- package version: `0.2.14`
 - npm package: <https://www.npmjs.com/package/@fa_yoshinobu/node-red-contrib-plc-comm-slmp>
 - Node-RED requirement: `>=3.0.0`
 - Node.js requirement: `>=18`
@@ -129,6 +129,7 @@ Maintainer-only notes and retained evidence live under `internal_docs/`.
 - connection control via `connect` / `disconnect` / `reinitialize` messages
 
 Set one explicit PLC type for each connection. The node stores it as `plcFamily` internally and derives `frameType`, access profile, and `X/Y` string-address rules from that selection.
+If `Remote password` is set, the connection unlocks the PLC remote-password protection after opening the SLMP transport and tries to lock it again before disconnecting.
 
 Supported canonical PLC type values:
 

package/docsrc/user/GETTING_STARTED.md

@@ -9,7 +9,7 @@ Recommended first path:
 1. Install the package into your Node-RED user directory.
 2. Restart Node-RED.
 3. Add one `slmp-connection` config node.
-4. Set `host`, `port`, `transport`, and `PLC type`.
+4. Set `host`, `port`, `transport`, and `PLC type`. If the PLC route uses remote-password protection, set `Remote password`.
 5. Import `examples/flows/slmp-basic-read-write.json`.
 6. Replace the host and safe test addresses.
 7. Deploy and confirm that one `D` read succeeds.
@@ -43,6 +43,7 @@ Set these fields explicitly on `slmp-connection`:
 - `port`
 - `transport`
 - `PLC type`
+- `Remote password` when required by the PLC route
 - timeout
 
 Canonical `PLC type` values:

package/docsrc/user/USER_GUIDE.md

@@ -15,7 +15,7 @@ See also:
 ## Quick start
 
 1. Install the package into your Node-RED user directory and restart Node-RED.
-2. Create one `slmp-connection` and set `host`, `port`, `transport`, and `PLC type`.
+2. Create one `slmp-connection` and set `host`, `port`, `transport`, and `PLC type`. Set `Remote password` when the PLC route is protected.
 3. Drop in `slmp-read` and try a safe address such as `D300`, `D300,4`, or `DSTR320,10`.
 4. Once reads work, add `slmp-write` and verify with known-safe test devices.
 
@@ -63,9 +63,11 @@ Configure these explicitly on the connection node:
 - port
 - transport: `tcp` or `udp`
 - PLC type: `iq-f`, `iq-r`, `iq-l`, `mx-f`, `mx-r`, `qcpu`, `lcpu`, `qnu`, or `qnudv`
+- Remote password: optional SLMP remote-password credential for protected PLC routes
 - route fields: network, station, module I/O, multidrop
 
 The connection node stores the selection as `plcFamily` internally and derives `frameType`, access profile, and string-address interpretation from the explicit `PLC type`.
+When `Remote password` is configured, the shared connection sends remote-password unlock after opening the SLMP transport and attempts remote-password lock before disconnecting.
 
 Validated PLC models:
 
@@ -114,9 +116,9 @@ Address notes:
 - count and string forms work on supported devices, for example `D300,10`, `M1000,8`, and `DSTR320,10`
 - `LTN`, `LSTN`, and `LCN` default to 32-bit current-value access in the high-level nodes
 - `LCS` and `LCC` state reads use direct bit read; high-level state writes use random bit write (`0x1402`)
-- future routed device support candidates such as `G` and `HG` are tracked in [`TODO.md`](../../TODO.md)
-
-Family-specific unsupported device codes:
+- `G` and `HG` are intentionally unsupported in the public Node-RED high-level surface
+
+Family-specific unsupported device codes:
 
 - all families: `G`, `HG`
 - `iq-r`, `iq-l`, `mx-f`, `mx-r`: none beyond `G`, `HG`