mirror of
https://github.com/OPCFoundation/UA-.NETStandard.git
synced 2026-10-24 11:01:55 +08:00
Marc SchierandCopilot
c48c8b93dd
**Stack 3/5** — base #4124. Part of the #4096 split; see #4096 for the overall picture. > Review after #4123 and #4124. ## What this is The OPC 10000-210 Relative Spatial Location and OPC 10000-211 Global Positioning companion models, with their server and client libraries, plus the ISA-95 migration onto the shared geolocation seam. ## Why it is one change A deployment writes **one** provider implementation and both OPC 10000-211 and OPC 10030 are served from it. The specifications disagree on representation, not on content: - GPOS publishes the structured `GlobalLocationDataType` and validates the EPSG code against the configured CRS. - ISA-95 publishes the same sample as the `String` array that OPC 10030 §8.3.2.2 requires. Splitting them would mean two provider interfaces for one physical sensor, which is exactly what this avoids. The seam itself lives in `Opc.Ua.Server` and landed in 1/5. ## Contents - `Opc.Ua.Positioning`, `.Server` and `.Client`. - `Opc.Ua.ISA95.Server` moves onto `IGeoLocationProvider`; the three ISA-95-specific provider files are removed because the shared seam and its in-memory implementation replace them. - **Fixes a conformance gap**: the ISA-95 binder wrote a scalar where the type declares `ValueRank` OneOrMoreDimensions. It now writes `String[]`. - **Fixes a liveness bug**: a provider that cannot push is polled at the Variable's `MinimumSamplingInterval` rather than installed once, so a non-pushing provider no longer serves its start-up sample with `Good` status forever. - `samples/MinimalIsa95Server`. ## Validation `dotnet build UA.slnx` — 0 errors. | Suite | Result | | --- | --- | | Opc.Ua.Positioning.Tests | 69 / 0 | | Opc.Ua.ISA95.Tests | 136 / 0 | | Opc.Ua.Di.Tests | 304 / 0 | --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8cbb8cd0-f0cb-4ab0-bea2-6202fbf69485
Minimal ISA-95 Server
This sample hosts the OPC-10030 ISA-95 common model together with OPC-10031-4 Job Control V1 and V2.
It uses the typed common-model builder, a provider-backed GeoSpatialLocationType, and the reusable in-memory Job Control provider. The seeded V2 job demonstrates the StoreAndStart and automatic AllowedToStart to Running transition.
Running
dotnet run --project samples\MinimalIsa95Server\MinimalIsa95Server.csproj
The server listens on opc.tcp://localhost:62545/MinimalIsa95Server by default (override with --port).
What this sample demonstrates
- Server registration via
services.AddOpcUa().AddServer(...).AddIsa95Server().ConfigureModel(...). - Populating the OPC-10030 common model: Personnel, Equipment, PhysicalAsset, and the full Material class/definition/lot/sublot hierarchy, including
DefinedByMaterialClassandMadeUpOfMaterialSublot. - Binding a
GeoSpatialLocationTypeinstance to the sharedInMemoryGeoLocationProvider, seeded with a fixed WGS84 position that is published as WKT. - Seeding a Job Control V2 job order (
DemoJobSeeder) withStoreAndStartfollowed by the automatic execution-controllerBeginExecutiontransition toRunning.
See the ISA-95 developer guide for the full hosting model, the Job Control V1/V2 state engine, the two documented normative NodeSet repairs, and a conformance matrix.