Connect with input sources that other input blocks cannot
The Real-Time Windows Target Other Input block can be used for interfacing input signals that other Real-Time Windows Target input blocks do not accommodate. The Other Input block is rarely used, and for only a few drivers. For details, see the documentation for the driver that you intend to use.
If none of the available blocks, including Other Input, provide what you need, you can create your own I/O blocks to work with Real-Time Windows Target applications. See Custom I/O Driver Blocks for details.
Enter a value representing how frequently you want the block to execute and interact with the I/O hardware. The block will also synchronize your model with the real-time clock at this sample rate.
Enter the number of timer ticks that your model can lag behind the real-time kernel. When the model lags by more than this number, the block reports an error and simulation stops. Otherwise, simulation continues even if some ticks are missed.
Select this check box to display the current number of missed ticks as a block output.
Select this check box to grant other programs more CPU time while the kernel waits for a response from the hardware.
Use this field to enter optional parameters required by the driver.
Set to specify the type of data that the block will output to the model.