Skip to main content

Customer Login

This content is for Speedgoat customer only. Log in to see content.

Forgot your password?

Don't have a Speedgoat account? Create an account.


Interrupt Setup

Interrupt Setup


Simulink Real-Time - Speedgoat/Utilities


This block represents hardware interrupts from Speedgoat I/O modules. It can be used to asynchronously trigger a subsystem or provide the pulse for the model’s base rate.


This block cannot be used in a referenced model or in variant subsystems.

Supported I/O Modules

All Speedgoat I/O modules with interrupt functionality can be used with this block.



If the Use as Model Trigger checkbox is unchecked, the Interrupt Setup block has one output port which can be connected to a Function-Call Subsystem block.

Refer to the usage notes if you want to use the interrupt in a referenced model.


Selected Interrupt

The Select Interrupt button opens a MATLAB Application which allows you to select one of the available interrupt sources.

Choose your interrupt source using the Select Interrupt drop-down menu. The list is generated based on all the Setup blocks of interrupt-capable I/O modules in your model.

If you have more than one of the selected I/O modules in your model, select the appropriate Module ID.

If you have more than one interrupt channel available, select the appropriate Channel .

If you are using the Interrupt Setup block in combination with a Simulink-programmable FPGA I/O module targeting the HDL Coder workflow, you will only be able to select your interrupt source in the generated model once you run through the HDL Workflow Advisor.

Use as Model Trigger

Check this box if you want to trigger your model’s base rate with this interrupt source instead of the CPU timer. Only one Interrupt Setup block per model can have this functionality enabled. This parameter replaces the setting which used to be in the model’s configuration properties.

Thread Priority

If you use the interrupt to trigger an asynchronous subsystem, you can decide at which priority it will be executed:

  • High: The subsystem will execute with a priority higher than the base rate of the model. Use this if a very quick reaction time is required and the computational load is low. Priority value = 254

  • Low: The subsystem will execute at a lower priority, similar to the slowest rate in your model. Use this for less time-critical background tasks. Priority value = 193

  • Manual: Set the priority value directly

Manual Priority

If you set the Thread priority to Manual, enter the desired value here. Refer to the MathWorks integrated or web documentation for more information.