node-red-contrib-s7-rust 1.4.0 → 1.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,37 @@ All notable changes to this project are documented here. The format follows
|
|
|
6
6
|
|
|
7
7
|
## [Unreleased]
|
|
8
8
|
|
|
9
|
+
## [1.4.1] - 2026-11-17
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
- A write is not sent again when its answer does not come. Before, the client reconnected and
|
|
14
|
+
sent the write again after a timeout, also when the PLC had already done it, and the node
|
|
15
|
+
reported success. A second write can overwrite a value that the PLC changed in the meantime
|
|
16
|
+
(for example a command bit that the PLC reset). Now the write fails with an error that starts
|
|
17
|
+
with `not confirmed`. A failure before the request reaches the socket (a dead connection) is
|
|
18
|
+
still retried. This applies to `s7 write`, the `setClock` action and the clock set of
|
|
19
|
+
`syncClock` (`s7 info`, S7; the clock read of `syncClock` is still retried), to writes and
|
|
20
|
+
alarm acknowledgement (S7CommPlus), and to `Poller::write` of the crate.
|
|
21
|
+
- An answer with another PDU reference than its request is refused (transport error: the
|
|
22
|
+
client reconnects). Before, it was taken as the answer.
|
|
23
|
+
- When a flow is removed or redeployed, a connection attempt in progress stops at once. Before,
|
|
24
|
+
the connection thread made its remaining attempts (for example two COTP connects) after the
|
|
25
|
+
endpoint was closed.
|
|
26
|
+
- Rust crate `s7`: `Client::run_once` (no repeat after the request was sent), `Client::cancel`,
|
|
27
|
+
`Conn::requests_sent`; the fake CPU can lose the answer of a write
|
|
28
|
+
(`set_silent_writes_n`) and answer with a wrong PDU reference (`set_bad_ref_n`).
|
|
29
|
+
|
|
30
|
+
Found by the independent tests of
|
|
31
|
+
[Missel2/s7-compatibility-lab](https://github.com/Missel2/s7-compatibility-lab) (wrong PDU
|
|
32
|
+
reference, lost write acknowledgement, reconnect after flow removal); their tests pass with
|
|
33
|
+
this change.
|
|
34
|
+
|
|
35
|
+
### Changed
|
|
36
|
+
|
|
37
|
+
- CI: `cargo audit` ignores RUSTSEC-2026-0543 (`chrono` is unmaintained; informational, no
|
|
38
|
+
vulnerability) until the move to `jiff` or `time` (#37).
|
|
39
|
+
|
|
9
40
|
## [1.4.0] - 2026-11-13
|
|
10
41
|
|
|
11
42
|
### Added
|
|
@@ -255,7 +286,8 @@ First release: the next generation of `@oriolrius/node-red-contrib-s7`.
|
|
|
255
286
|
- CI: tests on Node-RED 4 and 5, gitleaks, GitGuardian, RustSec and npm audit, CodeQL,
|
|
256
287
|
OpenSSF Scorecard, Dependabot. License LGPL-3.0-only.
|
|
257
288
|
|
|
258
|
-
[Unreleased]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.4.
|
|
289
|
+
[Unreleased]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.4.1...HEAD
|
|
290
|
+
[1.4.1]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.4.0...v1.4.1
|
|
259
291
|
[1.4.0]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.3.0...v1.4.0
|
|
260
292
|
[1.3.0]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.2.2...v1.3.0
|
|
261
293
|
[1.2.2]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.2.1...v1.2.2
|
|
Binary file
|
|
Binary file
|
|
@@ -16,6 +16,9 @@
|
|
|
16
16
|
<h3>Details</h3>
|
|
17
17
|
<p>The message goes out only when all writes are good. Otherwise the node raises an error:
|
|
18
18
|
use a Catch node.</p>
|
|
19
|
+
<p>A write is not sent again when its answer does not come (timeout, lost connection): the PLC
|
|
20
|
+
can have done it. The error then starts with <code>not confirmed</code>: read the tag to see
|
|
21
|
+
the value in the PLC.</p>
|
|
19
22
|
<p>S7CommPlus: a single bit (for example <code>M20.1</code>) cannot be written through absolute
|
|
20
23
|
access. Use a symbol for it.</p>
|
|
21
24
|
</script>
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "node-red-contrib-s7-rust",
|
|
3
|
-
"version": "1.4.
|
|
3
|
+
"version": "1.4.1",
|
|
4
4
|
"description": "Siemens S7 nodes for Node-RED: S7comm and S7CommPlus (S7-1200/1500 symbolic access) clients written in Rust, running in-process (Node-API). Linux x64.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"node-red",
|