Skip to content
English
  • There are no suggestions because the search field is empty.

.Sub-Touch-Active-Area-v2.4

Customer Documentation

Customer Documentation: Neonode® Touch Sensor Module User's Guide : .Sub Touch Active Area v2.4

Customer Documentation: Neonode® Touch Sensor Module User's Guide : .Sub Touch Active Area v2.4

Introduction

The Touch Sensor Module can be adjusted by changing the module's device configuration. By configuring these settings, the size or orientation of the Touch Active Area (TAA) can for instance be modified. Device Configuration is implemented according to our ASN.1 protocol, and most of the parameters can be configured in Workbench, zForce SDK, or Arduino Library (I2C). The parameters that have been configured using our evaluation tools or your own application, are stored in the ram memory. Meaning that the new configuration will have to be applied after each reboot. Please refer to section Device Configuration List to find all avaliable parameters.

Index

Axis Orientation

When mapping a reported touch from the Touch Active Area to a display, it is important that the orientation of the TAA, as well as the display are taken into account. When positioning a Touch Sensor Module over a display to achieve touch functionality, both systems needs to be co-aligned in order for a reported touch to be projected in the same corresponding position of the screen. If both systems are not oriented in the same way, the reported touches are going to be reversed depending of the setup. Luckily, the orientation of the reported touches can be configured to counter this by using ReverseX/ReverseY or FlipXY in Device Configuration. These settings rotates or flips the given coordinates of the reported touches, which allows the sensor to be mounted at any of the 4 sides of the screen 

Almost all displays has a reference point (or origin) positioned at the upper left corner of the screen, where the x-axis points in the direction to the right, with the y-axis pointing downwards. The origin of the sensor module's Touch Active Area is positioned on the left hand side, when having the TAA facing downwards, with the black side of the sensor module facing outwards.

This means that if a sensor module is positioned above a display, with the black side facing outwards, and its TAA covering the screen - Both coordinates systems would be co-aligned and a reported touch would project on the display seamlessly. But if we were to flip the sensor module to cover the screen from underneath the display, a reported touch would appear to be reversed in y-direction since their coordinate systems would no longer be co-aligned, as illustrated below.



Device Configuration List


Touch Active Area Size

The Low or High Bound of the x- or y-axis can be configured in order to make a Touch Active Area (TAA) smaller, creating a so-called Sub Touch Active Area (SubTAA). This limits the interactive area, and touches would only be reported within the SubTAA.

The SubTAA is measured from its origin, in the range of Low Bound and High Bound, in x- or y-direction



Where,

  • Low Bound X - Start position of the (Sub)TAA in x-direction, measured from the origin of the TAA.
  • High Bound X - End position of the (Sub)TAA in x-direction, measured from the origin of the TAA.
  • Low Bound Y - Start position of the (Sub)TAA in y-direction, measured from the origin of the TAA.
  • High Bound Y - End position of the (Sub)TAA in y-direction, measured from the origin of the TAA.

When projecting a SubTAA to a display within the host system, the projected SubTAA would then be mapped to the display's origin, regardless of its position (as shown in the illustration below).

Reverse X and Y

Reverse X or reverses the coordinates of a reported touch in x- or y-direction, without effecting the orientation of the (Sub) Touch Active Area. When positioning a sensor module, the axes of the Touch Active Area should either be positioned in the same orientation as the display, or have the reported touch coordinates adjusted. Please consider the following example.


Flip XY 

Flip XY swaps the x- with the y-axis of the reported touches, without effecting the orientation of the (Sub) Touch Active Area. When swapping axes, the reported touch data would then be sent to the host system containing the new x- and y coordinates. 

FlipXY together with ReverseX/Y can be used together which allows the Touch Sensor Module to be positioned around all edges of a display. When positioning a sensor module, the axes of the Touch Active Area should either be positioned in the same orientation as the display, or have the reported touch coordinates adjusted. Please consider the following example.


Offset X and Y

Offset X or configures the position of the mapped (Sub) Touch Active Area onto the display for the given axes. When adding the offset to a SubTAA, the position of the projected SubTAA will then be moved according to the following illustration.


Hid Display Size X and  Y

Hid Display Size X or Y represent the width and height of a display in the host system. Hid Display Size is used to scale the reported touches onto the display. The default Hid Display Size values are set to match the size of the sensor module's Touch Active Area, creating a proportional mapping regardless of the display size.

Proportional Mapping

When Hid Display Size is set to the size of the Touch Active Area, the mapping of a reported touch would get projected proportionally, to fit the size of the display.

For instance, if a display within the host system is larger than the TAA, a reported touch will get projected according to the illustration below.



Selective Touch Area

It is possible to create a so-called Selective Touch Area, where only a part of the display have touch functionality.

For instance, if a Touch Sensor Module is positioned over a larger display, we can create a touch surface over that specific part of the screen. Please refer to Selective Touch Area for further information and examples.











Attachments:

1-1.png (image/png)
1-1hidDisplay.png (image/png)
Asset 10SelectiveAreaTouch.svg (image/svg+xml)
Asset 1ProjectedSubTAA.svg (image/svg+xml)
Asset 2ProjectedSubTAA.svg (image/svg+xml)
Asset 3Device Configuration.svg (image/svg+xml)
Asset 3ProjectedSubTAAWithCoordinates.svg (image/svg+xml)
Asset 4Device Configuration.svg (image/svg+xml)
Asset 4Offset.svg (image/svg+xml)
Asset 5Offset.svg (image/svg+xml)
Asset 5SelectiveAreaTouch.svg (image/svg+xml)
Asset 5SubTAA.svg (image/svg+xml)
Asset 6HidDispSize.svg (image/svg+xml)
Asset 7test.svg (image/svg+xml)
Asset 8SelectiveAreaTouch.svg (image/svg+xml)
Asset 9SelectiveAreaTouch.svg (image/svg+xml)
DevConf.PNG (image/png)
Device Configuration.svg (image/svg+xml)
DeviceConfiguration.png (image/png)
DeviceConfigurationAsset 10FlipReverseExample.svg (image/svg+xml)
DeviceConfigurationAsset 10Offset.svg (image/svg+xml)
DeviceConfigurationAsset 11STA.svg (image/svg+xml)
DeviceConfigurationAsset 12STA.svg (image/svg+xml)
DeviceConfigurationAsset 14STA.svg (image/svg+xml)
DeviceConfigurationAsset 1ReverseXY.svg (image/svg+xml)
DeviceConfigurationAsset 2AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 2ReverseXY.svg (image/svg+xml)
DeviceConfigurationAsset 3ReverseXY.svg (image/svg+xml)
DeviceConfigurationAsset 3SubTAAProjection.svg (image/svg+xml)
DeviceConfigurationAsset 4AxesOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 4AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 4FlipXY.svg (image/svg+xml)
DeviceConfigurationAsset 5AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 5FLIPXY.svg (image/svg+xml)
DeviceConfigurationAsset 5Offset.svg (image/svg+xml)
DeviceConfigurationAsset 5SubTaaProjection.svg (image/svg+xml)
DeviceConfigurationAsset 6AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 6DeviceConfiguratrion.svg (image/svg+xml)
DeviceConfigurationAsset 6Offset.svg (image/svg+xml)
DeviceConfigurationAsset 6ProportionalMapping.svg (image/svg+xml)
DeviceConfigurationAsset 6REVERSEXY.svg (image/svg+xml)
DeviceConfigurationAsset 7AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 7FLIPXY.svg (image/svg+xml)
DeviceConfigurationAsset 7Offset.svg (image/svg+xml)
DeviceConfigurationAsset 7ProportionalMapping.svg (image/svg+xml)
DeviceConfigurationAsset 7SubTAA.svg (image/svg+xml)
DeviceConfigurationAsset 8AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 8DeviceConfigParamets.svg (image/svg+xml)
DeviceConfigurationAsset 8FLIPXY.svg (image/svg+xml)
DeviceConfigurationAsset 9AxisOrientation.svg (image/svg+xml)
DeviceConfigurationAsset 9Offset.svg (image/svg+xml)
DeviceConfigurationAsset 9ReverseExample.svg (image/svg+xml)
DeviceConfigurationAsset 9SubTAA.svg (image/svg+xml)
DispHidSize.PNG (image/png)
Ex2.PNG (image/png)
example1.png (image/png)
Example1Rev.png (image/png)
Example2.png (image/png)
Example4.png (image/png)
Example5_Real.png (image/png)
FlipXRevX.PNG (image/png)
FlipXRevXY.PNG (image/png)
FlipXRevY.PNG (image/png)
image2020-1-20_12-23-56.png (image/png)
image2020-5-26_13-41-3.png (image/png)
Mapping.pdf (application/pdf)
mapping.png (image/png)
Mapping.svg (image/svg+xml)
MappingSketch.png (image/png)
PinoutAsset 4SubTAAProjection.svg (image/svg+xml)
PinoutAsset 8OffsetProjection.svg (image/svg+xml)
PinoutHALFAsset 2AxesOrientation.svg (image/svg+xml)
PinoutHALFAsset 3AxesOrientation.svg (image/svg+xml)
propHidDisplay.png (image/png)
revx.png (image/png)
revyx.png (image/png)
revyyy.png (image/png)
SAT.PNG (image/png)
SubTAA Device Configurations.url (application/octet-stream)
SubTAA.png (image/png)