The Phidget Architecture : Rapid Development of Physical User Interfaces

s the communication layer for all phidgets, this is the only architectural component that would have to be extended to support other communication links, such as X10, Ethernet, wireless, or RF. the string “GlabServo”), and an identification number that is unique for a phidget instance of that type (Point 3 in requirements). Each device also transmits information specific to its type e.g., particular events that indicate the device state. Similarly, the host computer can transmit device-specific requests. For example, a host can tell the GlabServo device to set a motor’s position to a given angle. The PhidgetManager is a COM object. It includes an event-based API available to end-programmers for connection management (Point 2 in requirements). Its major API elements include: