OPCFoundation.NetStandard.Opc.Ua.Scales.Server 2.0.2

Prefix Reserved
dotnet add package OPCFoundation.NetStandard.Opc.Ua.Scales.Server --version 2.0.2
                    
NuGet\Install-Package OPCFoundation.NetStandard.Opc.Ua.Scales.Server -Version 2.0.2
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="OPCFoundation.NetStandard.Opc.Ua.Scales.Server" Version="2.0.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="OPCFoundation.NetStandard.Opc.Ua.Scales.Server" Version="2.0.2" />
                    
Directory.Packages.props
<PackageReference Include="OPCFoundation.NetStandard.Opc.Ua.Scales.Server" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add OPCFoundation.NetStandard.Opc.Ua.Scales.Server --version 2.0.2
                    
#r "nuget: OPCFoundation.NetStandard.Opc.Ua.Scales.Server, 2.0.2"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package OPCFoundation.NetStandard.Opc.Ua.Scales.Server@2.0.2
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=OPCFoundation.NetStandard.Opc.Ua.Scales.Server&version=2.0.2
                    
Install as a Cake Addin
#tool nuget:?package=OPCFoundation.NetStandard.Opc.Ua.Scales.Server&version=2.0.2
                    
Install as a Cake Tool

Opc.Ua.Scales.Server

Server hosting for the source-generated OPC 40200 Weighing Technology (Scales) model, version 2.00.

  • AddScales() registers a DI-based node manager that loads the DI, IA, Machinery, PackML and Scales models; ConfigureScales(...) creates scales once the address space is ready.
  • AddScalesToMachinery() and ConfigureScalesFor<MachineryNodeManager>() add the same complete runtime to an existing Machinery owner, without another DI manager. The owner must include MachineryParts.BuildingBlocks.
  • CreateScaleAsync(name, ScaleKind, builder => ...) materialises any of the fourteen concrete scale types into the DeviceSet and the Machinery Machines folder; CreateScaleSystemAsync builds a scale system with its scales.
  • The returned ScaleHandle runs the scale: PublishLoad feeds the raw load, and the runtime derives gross, net and tare, rounds to the weighing range, drives the overload/underload alarms and implements SetZero, SetTare, ClearTare, SetPresetTare and RegisterWeight.
  • Production presets with product selection, management and DI locking; the PackML state machine; scale events and alarms with the Annex C notification ids; and the methods of every scale type - loss-in-weight discharge/refill, piece-counting reference weighing, laboratory draft shields and calibration, vehicle inbound/outbound/one-pass weighing, feeder speed, totalizers and recipe management and processing.
  • Opt-in WithItemProcessing accepts typed registered catchweigher or price-labeler acquisitions with dimensions, zones, source metadata and an injectable price policy. WithCompletedFills counts completed totalizing-hopper downpours against the selected product. Neither path operates physical equipment.
  • Acquisition publication awaits live-node notifications. Runtime calls and OPC UA Value writes retain admission through their complete operations; synchronous writes overlapping awaited publication reject with BadInvalidState. Executor-bound async Value writes require a native async handler or core; otherwise they return BadNotSupported without invoking synchronous handlers. Stock writable variables receive a native async cache-write policy so product targets, tolerances and recipe condition settings remain client-writable. Direct node-property assignments require application serialization, and notification sinks must not await another write or acquisition on the same scale.
  • ConfigureRecipes enables local, registered analog/edge observations explicitly. Timeout leaves the step awaiting operator intervention; manual recipe execution remains the default.
builder.Services.AddOpcUa()
    .AddServer(...)
    .AddScales()
    .ConfigureScales(async context =>
    {
        ScaleHandle scale = await context.Manager.CreateScaleAsync(
            new QualifiedName("Scale1"),
            ScaleKind.Simple,
            b => b
                .WithIdentification(new ScaleIdentification
                {
                    Manufacturer = new LocalizedText("Contoso"),
                    SerialNumber = "0001",
                    ProductInstanceUri = "urn:contoso:scale:0001"
                })
                .WithWeighingRange(new WeighingRangeDefinition(0, 30, 0.005, 0.01))
                .WithWeightDetails()
                .WithZeroAndTare()
                .WithRegisterWeight(),
            context.CancellationToken);
        scale.PublishLoad(1.234);
    });

Shared Machinery owner

Register AddMachinery() followed by AddScalesToMachinery(). Configure with:

serverBuilder.ConfigureScalesFor<MachineryNodeManager>(async (context, ct) =>
{
    ScaleHandle scale = await context.Runtime.CreateScaleAsync(
        new QualifiedName("Scale1", context.Runtime.InstanceNamespaceIndex),
        ScaleKind.Simple,
        b => b.WithIdentification(identification)
            .WithWeighingRange(new WeighingRangeDefinition(0, 30, 0.005, 0.01))
            .WithPackMLState(),
        ct);
    scale.PublishLoad(1.234);
});

ScalesRuntime shares all scale kinds, systems, subdevices and controllers with the standalone manager. Instances and AMB asset additions stay on the same owner, including when Pumps is added with AddPumpsToMachinery(). Nested events reach their system and server subscribers. Shutdown releases file buffers, handles and session lock subscriptions.

For direct construction, pass ScalesMachineryModelProvider to the stock MachineryNodeManager alongside its building-block provider, then call owner.CreateScalesRuntime() after initialization. No inheritance changes are required, and the stock owner manages disposal.

Target frameworks

net48, net8.0, net9.0, net10.0

Additional documentation

See the Scales developer guide.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Framework net48 is compatible.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.2 89 11/11/2026
2.0.1 139 10/12/2026
2.0.0 140 10/7/2026