TouchSense modules use a position sensor, actuator, amplifier, microprocessor with firmware controls, and optional push-to-select switch to provide precise and reliable response that won’t degrade over time.

Haptic effect files, co-created with Advanced Input Systems and your engineering staff, form the system’s haptic effect library, which is embedded in the host Application or called by the Application from a separate file. Given position or selection information from the Rotary API, the Application updates the user interface, display screen, or device state, determines the need for control action, and requests those actions be communicated to the module by the Rotary Application Programming Interface (API).

The Rotary API, software that manages haptic effects, runs under the host system’s application, typically on the same CPU. The API receives event notifications from the rotary module’s kernel through device drivers, notifies the host application of these events, and receives instructions from the application to send back to the kernel.

The Kernel initiates haptic effects and scenes and executes them by sending control signals to the module’s Actuator. The Sensor, such as an optical encoder, determines the module’s rotary position and sends the information back through the kernel to the API, which sends them on to the host Application.