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

package/CHANGELOG.md

@@ -1,26 +1,34 @@
 # Changelog
 
-## Unreleased
+## 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
-- document the public compatibility change from separate `PLC series` / `frame type` fields to one `PLC type` selector
-- document the public device-scope changes since Flow Library `0.2.3`: `LTS`, `LTC`, `LSTS`, `LSTC`, `LCS`, `LCC`, and `LZ` are now in the high-level surface where the selected PLC type supports them
-- document the current device-matrix flow behavior: one-click run-all read/write buttons, status-lamp feedback, JSONL result logging, `plcFamily` records, and skip/error summary counts
-
-## 0.2.11 - 2026-05-02
-
-- remove the interim device-range catalog helper from the Node-RED package
+
+- 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
+- document the public compatibility change from separate `PLC series` / `frame type` fields to one `PLC type` selector
+- document the public device-scope changes since Flow Library `0.2.3`: `LTS`, `LTC`, `LSTS`, `LSTC`, `LCS`, `LCC`, and `LZ` are now in the high-level surface where the selected PLC type supports them
+- document the current device-matrix flow behavior: one-click run-all read/write buttons, status-lamp feedback, JSONL result logging, `plcFamily` records, and skip/error summary counts
+
+## 0.2.11 - 2026-05-02
+
+- remove the interim device-range catalog helper from the Node-RED package
 - keep ordinary Node-RED read/write validation to address format and protocol constraints, leaving actual device-range errors to the PLC response
 - reject device codes that the selected `plcFamily` does not expose in the public high-level table, aligned with the .NET `DEVICE_RANGES.md` support matrix
 
 - 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
 
@@ -41,7 +49,7 @@
 ## 0.2.7 - 2026-04-14
 
 - require explicit `plcFamily` on the standard packaged client and connection-node route, while keeping manual frame/profile selection only for internal diagnostic paths
-- switch the standard device-range example to the interim catalog helper so the high-level Node surface consistently derives frame, profile, address, and range handling from one family selection
+- switch the standard device-range example to the interim catalog helper so the high-level Node surface consistently derives frame, profile, address, and range handling from one family selection
 
 ## 0.2.6 - 2026-04-14
 
@@ -50,7 +58,7 @@
 
 ## 0.2.5 - 2026-04-14
 
-- add interim device-range catalog helpers and CPU operation-state support to the packaged SLMP client surface
+- add interim device-range catalog helpers and CPU operation-state support to the packaged SLMP client surface
 - add regression tests and README coverage for the new device-range and CPU-state helpers
 
 ## 0.2.4 - 2026-04-13

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.
 
@@ -50,12 +50,12 @@ 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`
-- 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`
-- changelog: <https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/CHANGELOG.md>
+- package name: `@fa_yoshinobu/node-red-contrib-plc-comm-slmp`
+- 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`
+- changelog: <https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/CHANGELOG.md>
 
 Install from npm:
 
@@ -79,20 +79,20 @@ npm run smoke:editor
 
 This command installs the local package into an isolated temporary userDir, starts a temporary Node-RED runtime, imports `slmp-basic-read-write.json`, verifies the flow starts, and then shuts the runtime down again.
 
-Legacy note:
-
-- the original unscoped `node-red-contrib-plc-comm-slmp@0.2.0` remains on npm, but new releases move to the scoped package name above
-
-### Changes Since Flow Library 0.2.3
-
-The Node-RED Flow Library currently shows `0.2.3` as the published baseline for this scoped package. Check these changes before updating an existing flow:
-
-- `slmp-connection` now uses one `PLC type` selector. Older `PLC series` and `frame type` fields from Flow Library `0.2.3` flows must be reselected after import.
-- `X/Y` string addresses are PLC-type-specific: iQ-F uses octal `X/Y`, while the other supported PLC types use hexadecimal `X/Y`.
-- `LTS`, `LTC`, `LSTS`, `LSTC`, `LCS`, `LCC`, and `LZ` are now in the high-level surface where the selected PLC type supports them.
-- Device codes unsupported by the selected PLC type are errors by default. The `slmp-device-matrix.json` sample can instead log them as `SKIPPED` records when it sends `slmpSkipUnsupported`.
-
-## Supported PLC Registers
+Legacy note:
+
+- the original unscoped `node-red-contrib-plc-comm-slmp@0.2.0` remains on npm, but new releases move to the scoped package name above
+
+### Changes Since Flow Library 0.2.3
+
+The Node-RED Flow Library currently shows `0.2.3` as the published baseline for this scoped package. Check these changes before updating an existing flow:
+
+- `slmp-connection` now uses one `PLC type` selector. Older `PLC series` and `frame type` fields from Flow Library `0.2.3` flows must be reselected after import.
+- `X/Y` string addresses are PLC-type-specific: iQ-F uses octal `X/Y`, while the other supported PLC types use hexadecimal `X/Y`.
+- `LTS`, `LTC`, `LSTS`, `LSTC`, `LCS`, `LCC`, and `LZ` are now in the high-level surface where the selected PLC type supports them.
+- Device codes unsupported by the selected PLC type are errors by default. The `slmp-device-matrix.json` sample can instead log them as `SKIPPED` records when it sends `slmpSkipUnsupported`.
+
+## Supported PLC Registers
 
 Start with these register/device families first:
 
@@ -128,9 +128,10 @@ Maintainer-only notes and retained evidence live under `internal_docs/`.
 - configurable error handling with throw / `msg.error` / second output
 - 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.
+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:
+Supported canonical PLC type values:
 
 - `iq-f`
 - `iq-r`
@@ -171,9 +172,9 @@ If an address is outside the connected PLC's actual range, the PLC response is r
 - string/count views: `,count`, `:STR`, `DSTR`
 - word-bit view: `.bit`
 
-Public device-code support by `plcFamily`:
-
-| PLC type | Public device codes accepted by the high-level API and Node-RED editor |
+Public device-code support by `plcFamily`:
+
+| PLC type | Public device codes accepted by the high-level API and Node-RED editor |
 | --- | --- |
 | `iq-r`, `iq-l`, `mx-f`, `mx-r` | `SM`, `SD`, `X`, `Y`, `M`, `L`, `F`, `V`, `B`, `D`, `W`, `TS`, `TC`, `TN`, `LTS`, `LTC`, `LTN`, `STS`, `STC`, `STN`, `LSTS`, `LSTC`, `LSTN`, `CS`, `CC`, `CN`, `LCS`, `LCC`, `LCN`, `SB`, `SW`, `DX`, `DY`, `Z`, `LZ`, `R`, `ZR`, `RD` |
 | `iq-f` | `SM`, `SD`, `X`, `Y`, `M`, `L`, `F`, `B`, `D`, `W`, `TS`, `TC`, `TN`, `STS`, `STC`, `STN`, `CS`, `CC`, `CN`, `LCS`, `LCC`, `LCN`, `SB`, `SW`, `Z`, `LZ`, `R` |
@@ -192,15 +193,15 @@ Validated public hardware summary:
 - [`slmp-basic-read-write.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-basic-read-write.json): scalar, float, and bit read/write over TCP
 - [`slmp-array-string.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-array-string.json): array and string read/write over TCP
 - [`slmp-control-error.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-control-error.json): control messages, `msg` source, and second-output errors
-- [`slmp-device-matrix.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-device-matrix.json): one-by-one and run-all high-level read, write, and readback across the matrix catalog with one outstanding request at a time, status lamp feedback, completed-result history, run summary, unsupported-device skip records, and JSONL logging in `Node-RED userDir/logs/slmp-device-matrix-<session>.jsonl`
-- [`slmp-routing.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-routing.json): per-request routing with `msg.target`
-- [`slmp-udp-read-write.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-udp-read-write.json): basic UDP read/write
-
-The device-matrix flow records `plcFamily` in each JSONL result, keeps one outstanding request at a time, and summarizes `OK`, `SKIPPED`, `NG`, mismatch, timeout, and pending counts.
-
-## Known Limitations
-
-- the high-level Node-RED surface requires explicit PLC type selection
+- [`slmp-device-matrix.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-device-matrix.json): one-by-one and run-all high-level read, write, and readback across the matrix catalog with one outstanding request at a time, status lamp feedback, completed-result history, run summary, unsupported-device skip records, and JSONL logging in `Node-RED userDir/logs/slmp-device-matrix-<session>.jsonl`
+- [`slmp-routing.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-routing.json): per-request routing with `msg.target`
+- [`slmp-udp-read-write.json`](https://github.com/fa-yoshinobu/node-red-contrib-plc-comm-slmp/blob/main/examples/flows/slmp-udp-read-write.json): basic UDP read/write
+
+The device-matrix flow records `plcFamily` in each JSONL result, keeps one outstanding request at a time, and summarizes `OK`, `SKIPPED`, `NG`, mismatch, timeout, and pending counts.
+
+## Known Limitations
+
+- the high-level Node-RED surface requires explicit PLC type selection
 - `.bit,count` is not supported
 - a single client connection keeps requests serialized by default
 - the read and write nodes keep the caller-visible logical request shape and do not silently retry with a different fallback split semantics
@@ -223,6 +224,6 @@ cmd /c npm.cmd test
 - `LTS`, `LTC`, `LSTS`, and `LSTC` state reads use the long timer 4-word decode helpers
 - `LCS` and `LCC` state reads use direct bit read; high-level state writes use random bit write (`0x1402`)
 - low-level direct bit writes are guarded for `LTS`/`LTC`/`LSTS`/`LSTC`/`LCS`/`LCC`
-- `X/Y` string addresses require explicit PLC type selection
+- `X/Y` string addresses require explicit PLC type selection
 - `iq-f` interprets `X/Y` string addresses in octal, while other supported families use hexadecimal `X/Y`
 - random read batching follows the Python helper layer for batchable word devices

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.
@@ -42,10 +42,11 @@ Set these fields explicitly on `slmp-connection`:
 - `host`
 - `port`
 - `transport`
-- `PLC type`
+- `PLC type`
+- `Remote password` when required by the PLC route
 - timeout
 
-Canonical `PLC type` values:
+Canonical `PLC type` values:
 
 - `iq-f`
 - `iq-r`
@@ -87,7 +88,7 @@ After the basic flow succeeds:
 
 If the first read fails, check these in order:
 
-- correct `PLC type`
+- correct `PLC type`
 - correct `tcp` or `udp` selection
 - a simple `D` address instead of a typed, count, or string form
 - editor validation messages before deploy

package/docsrc/user/LATEST_COMMUNICATION_VERIFICATION.md

@@ -2,19 +2,19 @@
 
 This page keeps the current public summary only. Older detailed notes are not kept in the public documentation set.
 
-## Current Retained Summary
-
-- current Flow Library baseline checked for release notes: `0.2.3`
-- current release-prep target: `0.2.12`
-- verified PLC models: `FX5UC-32MT/D`, `Q06UDVCPU`, `R08CPU`
-- verified transports: `TCP`, `UDP`
-- verified public nodes: `slmp-connection`, `slmp-read`, `slmp-write`
-- retained first-run smoke path: `slmp-basic-read-write.json`
-- 2026-05-01 iQ-R live check: `R08CPU` at `192.168.250.100:1025` over TCP
-  returned `LCS10=false` and `LCC10=false` through `readNamed`
-- 2026-05-02 release-prep docs align the Node-RED matrix flow with one-click run-all read/write, status-lamp feedback, JSONL logging, `plcFamily` result records, and PLC-type-unsupported `SKIPPED` records
-
-## Confirmed Public Register Scope
+## Current Retained Summary
+
+- current Flow Library baseline checked for release notes: `0.2.3`
+- current release-prep target: `0.2.12`
+- verified PLC models: `FX5UC-32MT/D`, `Q06UDVCPU`, `R08CPU`
+- verified transports: `TCP`, `UDP`
+- verified public nodes: `slmp-connection`, `slmp-read`, `slmp-write`
+- retained first-run smoke path: `slmp-basic-read-write.json`
+- 2026-05-01 iQ-R live check: `R08CPU` at `192.168.250.100:1025` over TCP
+  returned `LCS10=false` and `LCC10=false` through `readNamed`
+- 2026-05-02 release-prep docs align the Node-RED matrix flow with one-click run-all read/write, status-lamp feedback, JSONL logging, `plcFamily` result records, and PLC-type-unsupported `SKIPPED` records
+
+## Confirmed Public Register Scope
 
 - bit devices: `SM`, `X`, `Y`, `M`, `L`, `F`, `V`, `B`, `TS`, `TC`, `LTS`, `LTC`, `STS`, `STC`, `LSTS`, `LSTC`, `CS`, `CC`, `LCS`, `LCC`, `SB`, `DX`, `DY`
 - word devices: `SD`, `D`, `W`, `TN`, `LTN`, `STN`, `LSTN`, `CN`, `LCN`, `SW`, `Z`, `LZ`, `R`, `ZR`, `RD`
@@ -23,12 +23,12 @@ This page keeps the current public summary only. Older detailed notes are not ke
 
 ## Practical Cautions
 
-- set one explicit `PLC type` for every connection
-- older Flow Library `0.2.3` flows must be updated from `PLC series` / `frame type` to `PLC type`
-- start with `D` reads before using typed, counted, or string forms
-- keep `slmp-device-matrix.json` for later verification, not for the first smoke test
-- do not rely on Node-RED for PLC model-specific range or upper-bound checks; format errors are local, range errors come from the PLC/runtime response
-- `.bit,count` is not part of the current public high-level surface
+- set one explicit `PLC type` for every connection
+- older Flow Library `0.2.3` flows must be updated from `PLC series` / `frame type` to `PLC type`
+- start with `D` reads before using typed, counted, or string forms
+- keep `slmp-device-matrix.json` for later verification, not for the first smoke test
+- do not rely on Node-RED for PLC model-specific range or upper-bound checks; format errors are local, range errors come from the PLC/runtime response
+- `.bit,count` is not part of the current public high-level surface
 
 ## Where Older Evidence Went
 

package/docsrc/user/SUPPORTED_REGISTERS.md

@@ -83,7 +83,7 @@ This page is the canonical public register/device table for the Node-RED high-le
 
 These are device-code support rules only. The editor and helper APIs use them to reject or skip device codes that the selected family does not expose in the public surface; they are not address upper-bound checks.
 
-| PLC type | Unsupported device codes in the public Node-RED surface |
+| PLC type | Unsupported device codes in the public Node-RED surface |
 | --- | --- |
 | all families | `G`, `HG` |
 | `iq-r`, `iq-l`, `mx-f`, `mx-r` | none beyond `G`, `HG` |
@@ -93,6 +93,39 @@ These are device-code support rules only. The editor and helper APIs use them to
 
 This table follows only the supported/unsupported device-code portion of the .NET library's `DEVICE_RANGES.md`; Node-RED does not use it for PLC range or upper-bound validation.
 
+## iQ-R SD Range Maximum Reference
+
+For iQ-R-series targets, the PLC-configured current point count is read from
+the family-specific `SD` range registers by libraries that expose a device range
+catalog. The maximum below is the cap for that SD-derived point count:
+
+`point_count = min(SD point count, max_point_count)`
+
+The displayed upper bound is then `point_count - 1`. Node-RED keeps this as a
+reference table only; it still does not pre-check PLC model-specific address
+upper bounds. If an address exceeds the connected PLC's actual configured
+range, the PLC response is returned as the runtime error.
+
+| Item | Node-RED device codes | Max address | max_point_count | Setting unit |
+| --- | --- | --- | --- | --- |
+| `X` | `X` | `X2FFF` | `12288` (`0x3000`) | n/a |
+| `Y` | `Y` | `Y2FFF` | `12288` (`0x3000`) | n/a |
+| `M` | `M` | `M94674943` | `94674944` (`0x5A4A000`) | 64 points |
+| `B` | `B` | `B5A49FFF` | `94674944` (`0x5A4A000`) | 64 points |
+| `F` | `F` | `F32767` | `32768` | 64 points |
+| `SB` | `SB` | `SB5A49FFF` | `94674944` (`0x5A4A000`) | 64 points |
+| `V` | `V` | `V32767` | `32768` | 64 points |
+| `L` | `L` | `L32767` | `32768` | 64 points |
+| `T` | `TS`, `TC`, `TN` | `T5259711` | `5259712` | 32 points |
+| `ST` | `STS`, `STC`, `STN` | `ST5259711` | `5259712` | 32 points |
+| `LT` | `LTS`, `LTC`, `LTN` | `LT1479295` | `1479296` | 1 point |
+| `LST` | `LSTS`, `LSTC`, `LSTN` | `LST1479295` | `1479296` | 1 point |
+| `C` | `CS`, `CC`, `CN` | `C5259711` | `5259712` | 32 points |
+| `LC` | `LCS`, `LCC`, `LCN` | `LC2784543` | `2784544` | 32 points |
+| `D` | `D` | `D5917183` | `5917184` (`0x5A4A00`) | 4 points |
+| `W` | `W` | `W5A49FF` | `5917184` (`0x5A4A00`) | 4 points |
+| `SW` | `SW` | `SW5A49FF` | `5917184` (`0x5A4A00`) | 4 points |
+
 ## Not Currently in the Public Surface
 
 - `G`

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.
 
@@ -62,27 +62,29 @@ Configure these explicitly on the connection node:
 - host
 - port
 - transport: `tcp` or `udp`
-- PLC type: `iq-f`, `iq-r`, `iq-l`, `mx-f`, `mx-r`, `qcpu`, `lcpu`, `qnu`, or `qnudv`
+- 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`.
-
-Validated PLC models:
+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:
 
 - `FX5UC-32MT/D`
-- `Q06UDVCPU`
-- `R08CPU`
-
-## Changes since Flow Library 0.2.3
-
-The Node-RED Flow Library currently shows `0.2.3` as the published baseline for this scoped package.
-
-- Existing `0.2.3` flows used `PLC series` and `frame type`; current flows must use one explicit `PLC type` on every `slmp-connection`.
-- `X/Y` string addresses are PLC-type-specific. Use `iq-f` for octal `X/Y`; other supported PLC types use hexadecimal `X/Y`.
-- `LTS`, `LTC`, `LSTS`, `LSTC`, `LCS`, `LCC`, and `LZ` are now in the high-level surface where the selected PLC type supports them.
-- Device codes unsupported by the selected PLC type are rejected by default. The device-matrix sample can log them as `SKIPPED` records when it sends `slmpSkipUnsupported`.
-
-## Supported devices
+- `Q06UDVCPU`
+- `R08CPU`
+
+## Changes since Flow Library 0.2.3
+
+The Node-RED Flow Library currently shows `0.2.3` as the published baseline for this scoped package.
+
+- Existing `0.2.3` flows used `PLC series` and `frame type`; current flows must use one explicit `PLC type` on every `slmp-connection`.
+- `X/Y` string addresses are PLC-type-specific. Use `iq-f` for octal `X/Y`; other supported PLC types use hexadecimal `X/Y`.
+- `LTS`, `LTC`, `LSTS`, `LSTC`, `LCS`, `LCC`, and `LZ` are now in the high-level surface where the selected PLC type supports them.
+- Device codes unsupported by the selected PLC type are rejected by default. The device-matrix sample can log them as `SKIPPED` records when it sends `slmpSkipUnsupported`.
+
+## Supported devices
 
 Supported bit devices:
 
@@ -103,20 +105,20 @@ Supported word devices:
 Address notes:
 
 - `B`, `W`, `SB`, `SW`, `DX`, and `DY` use hexadecimal numbering
-- `X` and `Y` require explicit `PLC type`
+- `X` and `Y` require explicit `PLC type`
 - `iq-f` interprets string `X/Y` addresses in octal
 - all other supported families interpret string `X/Y` addresses in hexadecimal
 - most other devices use decimal numbering
 - Node-RED input validation checks address format and protocol constraints, not PLC model-specific device ranges or upper bounds
 - if an address is outside the connected PLC's actual range, the PLC response is returned as the runtime error
-- Node-RED input validation does reject device codes that the selected `PLC type` does not expose in the public device table
+- Node-RED input validation does reject device codes that the selected `PLC type` does not expose in the public device table
 - word devices support `.bit`, for example `D50.3`
 - 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`
@@ -253,9 +255,9 @@ Import one of these into Node-RED, then update the connection host, port, transp
 - [`slmp-basic-read-write.json`](../../examples/flows/slmp-basic-read-write.json): scalar, float, and bit read/write over TCP
 - [`slmp-array-string.json`](../../examples/flows/slmp-array-string.json): array and string read/write over TCP
 - [`slmp-control-error.json`](../../examples/flows/slmp-control-error.json): control messages, configured `msg` source, and second-output errors
-- [`slmp-device-matrix.json`](../../examples/flows/slmp-device-matrix.json): one-by-one and run-all high-level read, write, and readback across the matrix catalog with one outstanding request at a time, status lamp feedback, completed-result history, run summary, unsupported-device skip records, and JSONL logging under `Node-RED userDir/logs/slmp-device-matrix-<session>.jsonl`
-- [`slmp-routing.json`](../../examples/flows/slmp-routing.json): per-request routing with `msg.target`
-- [`slmp-udp-read-write.json`](../../examples/flows/slmp-udp-read-write.json): basic UDP read/write
+- [`slmp-device-matrix.json`](../../examples/flows/slmp-device-matrix.json): one-by-one and run-all high-level read, write, and readback across the matrix catalog with one outstanding request at a time, status lamp feedback, completed-result history, run summary, unsupported-device skip records, and JSONL logging under `Node-RED userDir/logs/slmp-device-matrix-<session>.jsonl`
+- [`slmp-routing.json`](../../examples/flows/slmp-routing.json): per-request routing with `msg.target`
+- [`slmp-udp-read-write.json`](../../examples/flows/slmp-udp-read-write.json): basic UDP read/write
 
 Recommended first import:
 
@@ -270,6 +272,6 @@ Recommended first import:
 - `.bit,count` is not supported
 - direct bit devices should be addressed directly as `M1000`, `X1F`, or `Y20`
 - a single client connection keeps requests serialized by default
-- the read and write nodes keep the caller-visible logical request shape and do not silently switch to a different fallback split behavior
-- read/write errors can throw, attach to `msg.error`, or go to a second output
-- the editor validates connection fields, literal address lists, literal update payloads, and literal route JSON before save
+- the read and write nodes keep the caller-visible logical request shape and do not silently switch to a different fallback split behavior
+- read/write errors can throw, attach to `msg.error`, or go to a second output
+- the editor validates connection fields, literal address lists, literal update payloads, and literal route JSON before save

package/examples/flows/README.md

@@ -33,9 +33,9 @@ Available flows:
 - [`slmp-routing.json`](slmp-routing.json): per-request routing using `msg.lookup` and `msg.target`
 - [`slmp-udp-read-write.json`](slmp-udp-read-write.json): basic UDP read and write example
 
-Notes:
-
-- The flow nodes keep the caller-visible logical request shape and do not silently switch to a different fallback split behavior.
-- In `slmp-device-matrix.json`, `Run all reads` and `Run all writes` are the auto-run buttons. The `Auto run status lamp` shows active, pending, idle, and error state in the editor.
-- Family-unsupported device codes are sent with `slmpSkipUnsupported` by the matrix flow, so they become yellow `SKIPPED` result records instead of red node failures.
-- Each matrix JSONL result includes `plcFamily` near the top of the record, followed by request, operation, address, status, and timing fields.
+Notes:
+
+- The flow nodes keep the caller-visible logical request shape and do not silently switch to a different fallback split behavior.
+- In `slmp-device-matrix.json`, `Run all reads` and `Run all writes` are the auto-run buttons. The `Auto run status lamp` shows active, pending, idle, and error state in the editor.
+- Family-unsupported device codes are sent with `slmpSkipUnsupported` by the matrix flow, so they become yellow `SKIPPED` result records instead of red node failures.
+- Each matrix JSONL result includes `plcFamily` near the top of the record, followed by request, operation, address, status, and timing fields.