26 Oct 2026

Remote Test System Control: How gRPC Transforms PXI Flexibility

What happens when your test engineers are in one location, and your PXI-based automated test system sits in a lab across an ocean? For a growing number of test teams, this isn't a hypothetical. It's the daily reality of distributed development, and it's exposing a fundamental limitation in how we've traditionally architected test and measurement systems.

All PXI systems require your application to run on a Windows or Linux controller physically connected to your modules and chassis. This constraint has become more challenging as development spans continents, CI/CD pipelines run in the cloud, and engineers expect to access shared test resources wherever they're working.

There's now a way to break this constraint without abandoning your existing setup or migrating to an entirely new platform: gRPC, and specifically our Pickering Remote Gateway.

The Distributed Test Problem

Test and measurement infrastructure has historically been local by design. PXI instrumentation sits on a benchtop or in a rack, a controller drives it, and the software stack ties everything to a specific machine, operating system, and often a specific programming language.

This tight coupling creates several problems for modern engineering organizations:

    • Geographic constraints: Teams spread across multiple sites can't easily share centralized test hardware without physically relocating people or duplicating equipment.
    • Scaling friction: As organizations adopt cloud-native development and DevOps practices, on-premises test systems struggle to keep pace with automated, distributed workflows.
    • Language and OS lock-in: Traditional PXI driver ecosystems are language-dependent and OS-specific. A team running a mixed technology stack, some Python here, some LabVIEW there, some Go in the pipeline, hits integration barriers at every turn.
    • Hardware proliferation: The simplest answer to "we need access in more places" has often been "buy more hardware," which increases capital expenditures and complicates maintenance.

For industrial, medical, and automotive test applications, where reliability and control are non-negotiable, these aren't minor inconveniences. They're barriers to productivity and time-to-market.

What gRPC Brings to Test and Measurement

gRPC is a modern, open-source framework that lets a client program run code on a remote server as if it were a local function. In the test and measurement context, the client is your application running on a remote PC, and the server is the PC connected to your PXI chassis.

Until now, test engineers have relied on remote desktop or custom client/server software to access test systems remotely, creating cumbersome workflows and proprietary integrations that are difficult to maintain. gRPC provides a standard, secure, and language-independent interface through which applications can control the test system directly, without requiring engineers to log in to the remote controller.

The industry has adopted gRPC because it addresses three needs simultaneously: remote accessibility, language-agnosticism, and cloud-friendliness. Critically, it does so while preserving the existing drivers vendors have built for their PXI and PXIe instruments.

Here's how it works in practice:

    • Contract-first design: You define a service and its methods in a protobuf (.proto) file, including request and response message types. This file serves as the Interface Definition Language for the framework.
    • Code generation: From that single contract, gRPC tooling generates client and server stubs in multiple languages, including Java, Go, Python, and C#.
    • Modern transport: Calls travel over HTTP/2, which delivers multiplexing, header compression, and built-in streaming.

How the Pickering Remote Gateway Works

Our gRPC solution, Pickering Remote Gateway, integrates PXI products into gRPC-based applications, controlling hardware as network-accessible services that can be driven from almost any language and operating system, without installing full drivers on every client. We follow the same approach as other leading T&M vendors, making remote test systems faster to develop and more consistent across all hardware.

The solution has two core components:

    • A gRPC server process running on the PC physically connected to the hardware. This server receives remote requests and calls the local driver API.
    • Protobuf (.proto) files that define the service methods, request and response messages, enums, and the error model for the remotely callable functions.

Setup is straightforward. On the host side, you install the gRPC server on the PC or embedded controller that has access to the PXI/PXIe cards and chassis, along with the Pickering drivers. Once you initiate the gRPC server, the system is ready to accept remote requests.

On the client side, you use the protobuf file to generate gRPC calls to the server from your client application, in whatever programming language you choose.

Remote control of Pickering PXI/PXIe modules from any language and operating system using gRPC

Figure 1: Illustration of Pickering Remote Gateway gRPC in an Automated Test System

The key detail for distributed teams: only the host system needs Pickering drivers installed. Every other client system is operating-system and language-agnostic. This inverts the traditional model, in which every machine that touches the hardware requires a full driver stack.

Real-World Use Cases

One Chassis, Many Cloud Instances

A PC connected to Pickering hardware can serve multiple cloud instances running on platforms like Azure or Google Cloud, all controlled from a single chassis. The hardware stays in one physical location, while the people and processes controlling it can be anywhere. Your validation lab keeps its hardware centralized and secure, while distributed teams and automated pipelines reach it over the network.

Decoupling Test Logic from Hardware Location

You can host PXI/PXIe hardware in a central lab or manufacturing site while running test sequences from distributed development machines or CI/CD runners via gRPC. This suits validation labs and production lines where hardware is shared between multiple teams, each running their own logic without contending for physical access.

Simplifying Software Stacks Across Multiple Users

Pickering's gRPC Server exposes PXI/PXIe modules, switches, DMMs, function generators, and simulation products as gRPC services. Python, LabVIEW, Rust, Go, or C# clients can control them from another PC without installing full drivers, breaking the classic constraint that the application must run on the embedded PXI controller.

Scaling Across Multiple Racks

Each chassis or rack can host a gRPC service that exposes the instruments installed on it. A test controller then discovers services and dynamically allocates resources across your infrastructure, allowing you to scale test capacity without hardware proliferation.

Why This Matters for a Mixed Technology Stack

Larger organizations rarely standardize on a single language or vendor. Once you expose a PXI/PXIe device as a Pickering Remote Gateway, you can talk to it from any environment with gRPC and protobuf support, including Python, LabVIEW, C#, Go, and Rust, rather than using vendor-specific drivers for each language and OS. The strongly typed APIs generated from your protobuf contract keep integration reliable across all of them.

We provide gRPC servers for both Windows and Linux, and the protobuf files let you build client applications in any language and OS. All products supported by the Pickering PXI driver are supported in Pickering Remote Gateway, so you preserve your existing instrument investments.

Practical Implementation Considerations

If you're evaluating this approach, a few points deserve attention during planning:

    • Protobuf contracts define your interface. The .proto file is the single source of truth for service methods, message types, and the error model. Getting this contract right up front pays dividends across every client you generate.
    • Cross-language code generation is a feature, not a workaround. Generating stubs from one contract keeps your Python and C# clients consistent with each other and with the server, reducing integration defects.
    • Deployment flexibility spans Windows and Linux. The server runs on both, and clients can run anywhere, letting you match your existing infrastructure rather than reshaping it.
    • The chassis doesn't have to be exclusively Pickering. The gRPC solution works within mixed setups. Only the host system connected to the Pickering cards needs the Pickering drivers.

The Strategic Payoff

For test engineers weighing infrastructure decisions, the case for gRPC-based remote control comes down to three durable benefits:

    • Reduced time-to-market: Distributed teams can access shared hardware immediately, without waiting for physical access or duplicating setups.
    • Improved team productivity: Engineers work in their preferred languages and operating systems, and automated pipelines integrate cleanly with existing DevOps practices.
    • Future-proof investments: You extend PXI modularity into cloud-native environments while preserving the drivers and instruments you already own, avoiding full platform migration.

This isn't about abandoning proven test infrastructure. It's about extending what you already know to meet the demands of distributed, cloud-connected engineering.

Extending PXI into the Cloud Era

The shift from physical, on-premises test systems toward distributed, cloud-accessible architectures isn't slowing down. Teams will continue to spread across locations, development will continue to move toward cloud-native and DevOps models, and technology stacks will continue to diversify.

Our solution gives PXI users a practical, reliable path to keep pace, one that respects existing driver investments, works across languages and operating systems, and centralizes hardware without constraining who can access it or from where.

To explore how Pickering Remote Gateway fits your test infrastructure:

If you'd like to discuss how this approach aligns with your specific test requirements, our engineers are ready to help you scope it.

RELATED RESOURCES: 

Written by  Alexander Jaiboy
Beta

How can I help?

Hi , I'm TESS - your friendly AI agent

Press Enter to submit

TESS is a moderated, AI agent. TESS can make mistakes, please verify important information independently.


Chat history

Log in or create an account to save & continue your chats with TESS.

Log in

or create an account