Crate roboplc

source ·
Expand description

RoboPLC page page

RoboPLC is an ultimate pack of a framework and tools for creating real-time micro-services, PLCs and industrial-grade robots in Rust.

The crate is designed to let using all its components both separately and together.

RoboPLC is a part of EVA ICS industrial automation platform.

Real-time-safe data synchronization components are re-exported from the RTSC crate which is a part of RoboPLC project and can be used directly, with no requirement to use RoboPLC.

§Technical documentation

Available at


Can be found at


buf::DataBuffer covers a typical data exchange pattern when data frames are collected (cached) from a single or multiple producers, then taken by a single consumer in bulk and submitted, e.g. into a local database or into an external bus.

  • always has got a fixed capacity

  • thread-safe out-of-the-box

  • frames may be forcibly pushed, overriding the previous ones, like in a ring-buffer.


hub::Hub implements a data-hub (in-process pub/sub) model, when multiple clients (usually thread workers) exchange data via a single virtual bus instead of using direct channels.

This brings some additional overhead into data exchange, however makes the architecture significantly clearer, lowers code support costs and brings additional features.

  • classic pub/sub patterns with no data serialization overhead

  • based on pchannel which allows to mix different kinds of data and apply additional policies if required

  • a fully passive model with no “server” thread.

§pdeque and pchannel

A policy-based deque rtsc::pdeque::Deque is a component to build policy-based channels.

pchannel is a channel module, based on the policy-based deque.

Data policies supported:

  • Always a frame is always delivered
  • Latest a frame is always delivered, previous are dropped if no room (acts like a ring-buffer)
  • Optional a frame can be skipped if no room
  • Single a frame must be delivered only once (the latest one)
  • SingleOptional a frame must be delivered only once (the latest one) and is optional

Additionally, components support ordering by data priority and automatically drop expired data if the data type has got an expiration marker method implemented.

pchannel is a real-time safe channel, mean it may be not so fast as popular channel implementations (it may be even slower than channels provided by std::sync::mpsc). But it is completely safe for real-time applications, mean there are no spin loops, data is always delivered with minimal latency and threads do not block each other.


thread_rt::Builder provides a thread builder component, which extends the standard thread builder with real-time capabilities: scheduler policies and CPU affinity (Linux only).

supervisor::Supervisor provides a lightweight task supervisor to manage launched threads.


controller::Controller is the primary component of mixing up all the functionality together.


io module provides a set of tools to work with field devices and SCADA buses.

Currently supported:

§Using on other platforms

The components thread_rt, supervisor and controller can work on Linux machines only.




  • A macro which can be used to match an event with enum for Hub subscription condition




  • Configures stdout logger with the given filter. If started in production mode, does not logs timestamps
  • Immediately kills the current process and all its subprocesses with a message to stderr
  • Returns true if started in production mode (as a systemd unit)
  • Serves the default rvideo server at TCP port
  • Sets panic handler to immediately kill the process and its childs with SIGKILL. The process is killed when panic happens in ANY thread
  • Terminates the current process and all its subprocesses in the specified period of time with SIGKILL command. Useful if a process is unable to shut it down gracefully within a specified period of time.

Type Aliases§

Derive Macros§

  • Automatically implements the DataDeliveryPolicy trait for an enum