Merge #625: deferred code-review findings resolved or ruled (S7.Cli verdict, browser CP release, Cluster member events, Sql Detach hoist, docs)
Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe
This commit is contained in:
+5
-1
@@ -57,7 +57,11 @@ operates off a **static, per-site tag list**, not live symbol discovery.
|
||||
pick the family that matches the PLC exactly. `Rack` is almost always `0`
|
||||
(relevant only for distributed S7-400 racks). `Slot` conventions per family:
|
||||
S7-300 = slot 2, S7-400 = slot 2 or 3, S7-1200 / S7-1500 = slot 0 (onboard PN).
|
||||
A wrong slot causes a connection refusal during the handshake. See
|
||||
The `CpuType` JSON strings are `S7300`, `S7400`, `S71200`, `S71500` and the legacy
|
||||
families `S7200` (S7-200), `S7200Smart` (S7-200 Smart) and `Logo0BA8` (LOGO! 0BA8).
|
||||
For the three legacy families S7.Net uses fixed TSAPs, so `Rack` / `Slot` are not
|
||||
consulted — leave them `0` / `0`; support is limited S7comm and unverified against
|
||||
hardware. A wrong slot causes a connection refusal during the handshake. See
|
||||
`src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.S7.Contracts/S7DriverOptions.cs` for the
|
||||
per-field defaults.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user