6. INtime Configuration
The standard INtime configuration, as installed from the installation media, will run without modification on any PC compatible host.
There are configuration options to meet specific needs for development and deployment of an INtime system.
Some of the configuration options are linked to INtime itself, e.g., memory used by the kernel, networking, licensing or automatic loading of applications.
Other options are only relevant for the “INtime for Windows” configuration, where you want to specify INtime’s interaction with Windows: in which way should Windows react on faults in INtime nodes, how many processor cores run INtime, is there a need for a virtual Ethernet link between Windows and INtime, which devices get passed from Windows to INtime, or configure the development tools of the SDK (remember they always run on Windows).
Yet other options are only relevant for the “INtime Distributed RTOS” configuration, where you need to care about booting the INtime nodes while the Windows interaction is not relevant.
Configuration is done manually or programmatically using the Local Node Configuration (LNC) API on Windows. The configuration GUI also supports command line options for major configuration activities.
The manual method is capable to configure any node in the distributed system that can be reached by the network. The LNC method always will configure the host where Windows is running.
Manual configuration can be done in two ways: either by Control Panel applications executing on Windows or via a browser accessing the respective configuration pages accessible from a WEB server on that INtime host.