NEXUS TMS SDK

Build a TMS device without
first becoming a DDS® expert.

A C++ library that implements MIL-STD-3071, the Tactical Microgrid Standard, so your engineers can write the part only they can write — reading sensors and driving hardware.

WHY THE STANDARD EXISTS

Every forward base runs on a microgrid.
Few of them run on one language.

Generators, batteries, solar panels and the loads they power have to work together as a single grid. Today those pieces usually come from different vendors and speak different languages, so making them work together means custom integration, one project at a time.

MIL-STD-3071, the Tactical Microgrid Standard, changes that. It is a DoD standard defining one open way for every device on a tactical microgrid to communicate: how it announces itself, how it reports its state, which controller it obeys, and what happens when that controller goes down.

The standard's stated purpose includes “interoperability between manufacturers of tactical microgrid components” and “reduction of procurement, operational, sustainment, and maintenance costs.”

TMS runs over DDS®, the publish/subscribe standard already used in ships, aircraft and ground vehicles. That is where we come in.

THE PROBLEM

Two things to master before writing a line about your generator.

To build a TMS-compliant device today, an engineer has to learn DDS® itself — participants, readers, writers, QoS policies and type systems — and then the standard: hundreds of pages of rules covering heartbeats, controller failover, rate limits, request handling and reply codes, and which of its 37 topics each kind of device must publish.

Get one detail wrong and the device fails to interoperate, often with no visible error at all.

WHAT THE SDK DOES

The protocol is done for you.

Nexus TMS SDK is built on Nexus DDS®. Your code drives the hardware; the library handles the network.

Identity and Heartbeat

The device announces itself and sends the one-second Heartbeat the standard requires.

Controller selection and failover

Tracks the microgrid controllers, chooses which to obey, and moves to the standby when the active one disappears — on the standard's own timers.

Request handling

Validates every command from the controller and replies within the standard's 0.1-second limit, with the correct reply code.

Rate limits and QoS

Every topic published at the rate, and with the quality of service, the standard specifies.

Controller support

For microgrid controllers: a live view of the grid, with every command numbered, paced and matched to its reply.

Traceable to the standard

Every requirement in the code cites the section of MIL-STD-3071 it implements. The data model comes straight from the files published with the standard, unmodified.

SEE IT WORK

A tabletop microgrid.

To show TMS working end to end we are building a 24 V DC tabletop grid from Raspberry Pi devices running the SDK: a generator, a LiFePO4 battery, three loads, and a primary and standby microgrid controller.

Plug and play

A new device joins the grid with no configuration.

Controller failover

Pull the plug on the active controller; the standby takes over and the lights stay on.

Battery runs low

The controller starts the generator, and you see every command and reply.

Nexus Workbench shows each step on screen as it happens on the network. All three scenarios run in simulation today; the hardware build is next.

INTEROPERABILITY

Tested against someone else's stack,
including the parts that did not work.

TMS only matters if devices from different vendors work together, so we test against other DDS® implementations rather than only our own.

OpenDDS

We are testing the SDK against the open-source OpenDDS TMS example in both directions: OpenDDS devices under a Nexus controller, and Nexus devices under an OpenDDS controller.

Working today
The two stacks discover each other, and TMS Heartbeats flow from an OpenDDS device to Nexus.
Issues found
The testing turned up problems on both sides, each reported to the project it belongs to. In the OpenDDS TMS example the power devices were not sending their Heartbeat on Linux and macOS, which we reported with a verified fix. On our side it found two issues in how type information goes on the wire, both being fixed in Nexus.
Next
Full device-information exchange, and controller failover across the two stacks.

eProsima Fast DDS — planned

Fast DDS is one of the most widely deployed DDS® implementations and is next on our interoperability plan, which will have the SDK tested against both major open-source DDS stacks.

We think this is how interoperability should be done: test against an implementation that is not your own, report what breaks to whoever owns it, and test again once it is fixed — including when what breaks is ours.

WHERE WE ARE

Status and roadmap.

Done
Generator, energy storage, loads, and primary and standby microgrid controllers with failover — all running in simulation.
In progress
Interoperability with OpenDDS.
Next
Interoperability with Fast DDS; the tabletop hardware build; a getting-started guide for engineers new to DDS®.
Later
DDS® Security, following the TMS cybersecurity work; more device roles.

Building a TMS device, or evaluating TMS for a program?

Tell us what you are building and we will come back to you.