PRC.Server.Bundle 1.755.0

PRC.Server.Bundle

Parametric Robot Control (PRC) simulates, programs and controls industrial and collaborative robots. The PRC Server runs the kinematics, the collision checking and the program generation and communicates with the robot controllers. Clients such as the PRC plugin for Grasshopper, or your own software, talk to it over gRPC, and its web UI shows every connected robot with a 3D viewport, the simulation timeline, the driver settings and the generated programs.

PRC.Server.Bundle brings everything an application needs to run robot simulations with PRC in one package: the complete PRC Server, PRC.Library, PRC.GRPC and PRC.Core to work with it, and a launcher. The launcher starts the bundled server as its own process when your application needs it, uses a PRC Server that is already running instead, and stops the server it started when your application is done. The server is the portable build, so the same package works on every operating system and processor architecture that .NET supports.

Projects that reference the package get the server copied into their build output. Hosts that load packages straight from the NuGet folder, such as visual programming environments, start it from there.

The server needs a PRC license, which you activate in its web UI. It shares the license with a PRC Server installed on the same computer. Licenses and the desktop installers are available from portal.robotsinarchitecture.org.

Getting started

using PRC.Server.Bundle;

using var server = BundledServer.Start();   // uses a PRC Server already answering on its port, or starts the bundled one
if (!server.WaitUntilReady(TimeSpan.FromSeconds(30)))
    throw new Exception(server.Error ?? "The PRC Server did not start in time.");   // e.g. the .NET 10 runtime is missing

using var client = new PRC.GRPC.Client.Client();
await client.Connect(BundledServer.Address);
// ... set up robots and send tasks through the client ...
// Disposing `server` stops the server it started; one it found running is left alone (once that
// one stops answering, `HasExited` reads true and a new `Start()` starts the bundled server).

• In hosts with a running main loop, such as visual programming environments or game engines, use SharedBundledServer instead: every handle in the process shares one server, Update(enabled) is cheap enough to call every frame and returns whether the server is ready, failures show in Error instead of exceptions, and the server started here stops shortly after the last handle is disposed, so recreating a handle does not restart it.
• Libraries that bring PRC to a particular host can depend on this package and wrap the launcher in their own nodes or components.
• Stopping the server does not stop a robot under online control: stop the robot first.
• RecentOutput holds the server's last log lines.

The PRC packages

Use the package version that matches your PRC Server. Server and packages share one version scheme and are released together.

Documentation

• Documentation — the PRC manual, including the server's pages and settings.
• PRC Integration Guide — the complete reference of the gRPC API the server exposes: every message and call, coordinate systems, units, settings and worked examples. Written for developers and as context for LLM-assisted integration.
• PRC.Integrations — sample integrations for several platforms and languages, plus the current proto definition.
• Contact: johannes@robotsinarchitecture.org

Requirements

• .NET 8.0 or later for the libraries and the launcher.
• The ASP.NET Core Runtime 10 for the server.

Disclaimer: This software is provided "as is" without any warranties or guarantees. The creators and developers of this software do not accept any liability for any damages or losses arising from its use.