UA-.NETStandard/samples/CranesHoists

Cranes and Hoists samples

These console applications exercise the released OPC 40020-1 1.00 model through the preview crane runtime and typed client. They do not connect to equipment. There are no motion, control-takeover or safety-bypass commands.

• CranesHoistsServer: one native crane by default, explicit optional capabilities, isolated simulated providers and bounded lifetime.
• CranesHoistsClient: subtype-aware discovery, original values/quality/source times, bounded observation and opt-in limit requests.
• Implementation and conformance guide.

Run a bounded local demonstration

From the repository root, build each project using the repository's .NET 10 SDK:

dotnet build samples\CranesHoists\CranesHoistsServer\CranesHoistsServer.csproj
dotnet build samples\CranesHoists\CranesHoistsClient\CranesHoistsClient.csproj

The projects use $(AppTargetFrameworks): net10.0, net9.0, net8.0, and net48. Select a single build target using the documented CustomTestTarget override.

Start the server in one terminal, then the client in another:

dotnet run --no-build --framework net10.0 `
  --project samples\CranesHoists\CranesHoistsServer -- `
  --port 62557 --seconds 60 --instances 2 --advanced --demo-trust --allow-limit-requests

dotnet run --no-build --framework net10.0 `
  --project samples\CranesHoists\CranesHoistsClient -- `
  --endpoint opc.tcp://localhost:62557/CranesHoistsServer `
  --demo-trust --system Crane1 --seconds 3 --count 3 --events `
  --request-limit 40 --prove-refusal

--demo-trust is an explicit local-test-only certificate trust exception. It does not select an insecure endpoint: the client requires Basic256Sha256/SignAndEncrypt. Do not enable this exception on an exposed host. Without it, administer peer/issuer trust through the existing certificate framework.

The server prints READY with the actual endpoint. --port 0 chooses an available local port; copy the printed endpoint to the client. Selection and binding are separate operations, so a port race fails startup rather than silently changing the advertised endpoint.

For the write demonstration, use a fresh server. Each provider accepts only one request. The first request records 40, independently of the active plus limit 31.5 supplied by the simulation. The second explicit request is refused with BadResourceUnavailable; the client rereads the request and active value and prints REFUSAL_VERIFIED. It never retries an ambiguous write automatically. The second crane's provider and request history remain independent.

Omit both write flags for read-only operation. Omit --advanced on the server and --events on the client to exercise mandatory-only defaults: position is present with BadNoData when unavailable, and unselected optional signals are reported as absent, not as fabricated Good measurements.

Cleanup and security

The server ends after its running window or Ctrl+C. It awaits acquisition and host stop (including startup work), drains the native handles, disposes providers and asynchronously disposes its host. The client verifies its observation subscription count returns to its baseline, closes/disposes the managed session and asynchronously disposes the application host. Errors return a nonzero exit code; empty event windows are reported explicitly.

Certificates are generated by the certificate store infrastructure, not checked into source. Default stores are below artifacts\craneshoists-pki\server and artifacts\craneshoists-pki\client. --pki <directory> selects a different private root. Stores are deliberately retained for trust administration; remove only your demo directories after both processes exit. Use separate roots for server and client.

NativeAOT

The net10 project configuration enables NativeAOT publishing:

dotnet publish samples\CranesHoists\CranesHoistsServer -c Release -f net10.0 -r win-x64 --self-contained true
dotnet publish samples\CranesHoists\CranesHoistsClient -c Release -f net10.0 -r win-x64 --self-contained true

Both win-x64 native sample binaries have also been executed together: native discovery, reads, data/events, accepted/refused requests and natural cleanup passed. A CLR run alone is not native evidence; the full repository and MCP-native matrix remain separate acceptance requirements.