Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
blocks:app-note:nexmosphere:handgestures [2023-12-20 15:07]
mattias [Use a Nexmosphere hand gesture sensor to control content in Blocks]
blocks:app-note:nexmosphere:handgestures [2023-12-21 07:30]
mattias [Use a Nexmosphere hand gesture sensor to control content in Blocks]
Line 2: Line 2:
  
 :!:WORK IN PROGRESS:!: :!:WORK IN PROGRESS:!:
-This is an application note that describes how to use the Nexmosphere hand gesture sensor XV-H40 with Blocks.+This is an application note that describes an example how to use the Nexmosphere hand gesture sensor XV-H40 to navigate in some Blocks content.
  
-This note assumes a controller that with built-in serial to usb controller directly to a Pixilab Players USB port (i.e. XN-185).+This note assumes a controller with built-in serial to usb controller directly to a Pixilab Players USB port (i.e. XN-185), but it will work also with a serial controller connected over the network via a serial port server such as Moxa Nport.
  
-:!: This application note is technical and assumes Blocks users with essential knowledge of tasks, propertiesbehaviors.+:!: This application note is technical and assumes Blocks users with essential knowledge of tasks, properties and behaviors.
  
 ====Hardware requirements==== ====Hardware requirements====
Line 33: Line 33:
 The existing Nexmosphere drivers have been updated with extensive support for the XV-H40 hand gesture sensor. The existing Nexmosphere drivers have been updated with extensive support for the XV-H40 hand gesture sensor.
 Update/install the driver in any existing system to gain support for this device.  Update/install the driver in any existing system to gain support for this device. 
-Most required functions have been implemented as callables on the driver. Any other settings can be set by sending a custom command to the element.+Most required functions have been implemented as callables on the driver. Any other settings can be set by sending a custom command to the element by referencing the vendors device manual.
  
 ===Activation Zones=== ===Activation Zones===