ARCHITECTURE AND COMMUNICATION PROTOCOL FOR HAPTIC OUTPUT DEVICES
First Claim
1. A method for driving a plurality of actuators, each actuator being associated with one of a plurality of user input elements, the method comprising:
- generating a composite drive signal that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier, the first haptic output device associated with a first user input element and the second haptic output device associated with a second user input element;
transmitting, to a controller, the composite drive signal; and
wherein the execution of the first and second drive signals at the controller is based on the packet identifier.
1 Assignment
0 Petitions
Accused Products
Abstract
The embodiments are directed toward an architecture and communication protocol for controlling haptic output devices. According to the embodiments, a composite drive signal is generated that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier. A controller includes the first haptic output device that is associated with a first user input element and the second haptic output device associated with a second user input element. The composite drive signal is transmitted to controller, and the execution order of the first and second drive signals is determined based on the packet identifier.
-
Citations
18 Claims
-
1. A method for driving a plurality of actuators, each actuator being associated with one of a plurality of user input elements, the method comprising:
-
generating a composite drive signal that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier, the first haptic output device associated with a first user input element and the second haptic output device associated with a second user input element; transmitting, to a controller, the composite drive signal; and wherein the execution of the first and second drive signals at the controller is based on the packet identifier. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A device comprising:
-
a processors; and memory storing a program for execution by the processor, the program including instructions for; generating a composite drive signal that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier, the first haptic output device associated with a first user input element and the second haptic output device associated with a second user input element; transmitting, to a controller, the composite drive signal; and wherein the execution of the first and second drive signals at the controller is based on the packet identifier. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A non-transitory computer readable storage medium storing a program configured to be executed by a processor, the program comprising instructions for:
-
generating a composite drive signal that includes a first drive signal to be rendered by a first haptic output device, a second drive signal to be rendered by a second haptic output device, and a packet identifier, the first haptic output device associated with a first user input element and the second haptic output device associated with a second user input element; transmitting, to a controller, the composite drive signal; and wherein the execution of the first and second drive signals at the controller is based on the packet identifier. - View Dependent Claims (14, 15, 16, 17, 18)
-
Specification