Real-time for deeply embedded x86 applications

Windows has quickly becoming a preferred platform for building highly intelligent automated systems, but specialization in a machine's architecture sometimes requires that some elements of a real-time system be distributed, physically, from the center of logical operation.

The INtime RTOS is not limited to providing real-time services for a single Windows machine. It can also be installed and run on as a standalone embedded platform, remotely communicating with its Windows host as an INtime remote node. INtime remote nodes are distinct independent hardware and software modules (CPU, memory, I/O) that connect to each other or a Windows host via an Ethernet or serial communication link.

An INtime remote node is a special configuration of the INtime RTOS where an instance of the INtime kernel runs on a computer that is physically separate from the Windows workstation.

The INtime remote node configuration is designed for deeply embedded, real-time applications. It gives developers all the advantages of INtime software, along with the ability to scale and distribute real-time applications. Despite running on separate hardware from Windows, the same API is used to allow Windows applications to communicate with real-time processes.

Using INtime remote nodes allows you to implement real-time systems with distributed processing more quickly and inexpensively by leveraging the standard Windows development environment. They also provide scalability and flexibility from a single-processor, Windows-based real-time system to a Windows-centric network of real-time nodes.

Distributed real-time nodes with Windows-based control

With INtime remote nodes, you maintain central control of a system from within a single Windows application while simultaneously allowing for multiple, physically distinct, real-time nodes that are logically controlled by the Windows application. These remote nodes can by networked to the Windows console without losing the tight connection afforded by INtime between hard real-time tasks and non-real-time GUI tasks.

INtime software supports extension of the Windows-to-INtime connection (NTX) across Ethernet or RS-232. Applications can be easily scaled to operate on a single CPU or multiple CPUs with no coding changes.

INtime remote nodes include a local file system, so remote node real-time applications are not dependent on Windows. Application files can be read from a local file system, or loaded from Windows over a network connection, or both.

INtime remote nodes can run independently without any, or with only occasional Windows interaction. The Distributed System Manager (DSM) can be used to manage communication link interaction without a need to burden your real-time applications.