ModelingEvolution.RocketWelder.StationManagement

rw2 as one piece of a station environment (epic-107, docs/epics/epic-107-station-twin/). Built on ModelingEvolution.StationManagement — the foundation that knows containers, networks and waits, and no domain nouns.

This package is a client of rw2: of its container image and of its published REST language. It references no rw2 application project, and no vendor or simulator package.

await using var host = await StationHost.Start("pamet-01");          // one station = one network, fixed IPs
var store = await host.EventStore("rw2-store", reachableFromHost: true);
var rw    = await host.RocketWelder("2.21.34", store, simulatorTrack: true, sinkPorts: [17002]);
//          ↑ always a container; add build: "../rocket-welder2/bin/Debug" to mount the branch under test over /app

var fr20 = await rw.Devices.Ensure(real.Robot("FR20").SimulatedBy(Simulator.Robot, sim));
await rw.Devices.Ensure(real.Track("7th Axis").SimulatedBy(Simulator.Track, sim)
                                              .Keeping(x => x.Travel, x => x.Speed, x => x.Tolerance));
await rw.Cameras.Ensure(real.Camera("41943012").SimulatedBy(Mjpeg.Camera, sim.Preview,
                            pipeline: "pipelines/sim-camera.gpipe", sinkPort: 17002, boundTo: fr20));

var run = await rw.Programs.Run("AxisThenArm");
await run.ShouldFinishWithin(2.Minutes());

Console.WriteLine(host.Differences.Render());

How it matches the station

Real() · EmulatedBy(endpoint) · SimulatedBy(deviceType, endpoint) · .Keeping(x => …) produce both the rw2 registration and a Match, so a twin always says how alike it is:

FR20      simulated  Simulator                not: the Fairino driver
7th Axis  simulated  SimulatorTrack           not: the FairinoTrack driver, travel, speed, tolerance (rw2 refused: 400 …)
Megmeet   simulated  SimulatorWeldingMachine  not: the MegmeetWeldingMachine_ArtsenPlusPro driver
Plasma    simulated  SimulatorWeldingMachine  not: the FairinoDoWeldingMachine driver
41943012  simulated  MjpegCamera              calibration kept · not: the Camera driver

The travel, speed, tolerance (rw2 refused: …) line is RW-1: POST /api/peripheral-devices validates against the registered property types rather than the device type's own schema, so SimulatorTrack's declared TravelMinMm, MaxSpeedMmPerSecond and ToleranceMm are answered with 400. The device is registered without them and the twin says so. When RW-1 lands, those three move to kept with no change to a station script.

Only rw2's OWN device types live here (Simulator, SimulatorTrack, SimulatorWeldingMachine, SimulatorDistanceSensor, MjpegCamera). A vendor's device type is a string in the station's description — this package never references a vendor package.

Test

dotnet test src/ModelingEvolution.RocketWelder.StationManagement.Tests --filter "Category!=Docker"   # pure logic
dotnet test src/ModelingEvolution.RocketWelder.StationManagement.Tests --filter "Category=Docker"    # a real station

The Docker suite brings a whole twin up on a developer machine — it needs the rw2 image (20 GB) and modelingevolution/simulator:local, so it never runs in CI.

Which rw2 it works against

Minimum: rw2 2.21.18. That is the first release carrying the headless POST /api/repositories/{repoId}/programs this package creates its own programs with (git tag --contains 3a2d6395). It also needs PATCH /api/pipeline/{id}/autostart, POST /api/pipeline/import, and — for Cameras.Ensure to bind a calibration — POST /api/cameras/calibration/seed-handeye, which rw2 serves only in the Development environment (the host sets ASPNETCORE_ENVIRONMENT=Development for exactly that reason).

Proven against 2.21.34, the version the integration suite runs. Anything between 2.21.18 and that is untested.

Published

Internal feed only (nuget.modelingevolution.com) — never nuget.org.

The package carries its own version, not rw2's image version: its surface moves when rw2's REST language moves, which is much rarer than an image build. What ties it to rw2 is the minimum version stated above.