1. Manuals
  2. Brands
  3. NEONODE Manuals
  4. Accessories
  5. zForce AIR Touch Sensor
  6. User manual

NEONODE zForce AIR Touch Sensor User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

zForce AIR® Touch Sensor
User's Guide
2018-03-12

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the zForce AIR Touch Sensor and is the answer not in the manual?

Questions and answers

Related Manuals for NEONODE zForce AIR Touch Sensor

Summary of Contents for NEONODE zForce AIR Touch Sensor

  • Page 1 zForce AIR® Touch Sensor User's Guide 2018-03-12...
  • Page 2 Neonode components are neither designed nor intended for use in FDA Class III applications, or similar life-critical medical equipment. Customers acknowledge and agree that they will not use any Neonode components in FDA Class III applications, or similar life-critical medical equipment, and that Neonode will not be responsible for any failure to meet the requirements of such applications or equipment.

  • Page 3: Table Of Contents

    Applications Product Design and Components 2.5.1 Sensor Design Exploded view 2.5.2 Sensor Components Product Integration Getting started with zForce AIR Touch Sensor Evaluation ..........16 Evaluation Kit Contents Getting Started Connecting Sensor Communicating with Sensor 3.4.1 Neonode Workbench 3.4.2 USB HID Digitizer Mode 3.4.3...
  • Page 4  zForce AIR® Touch Sensor User's Guide Table of Contents Means of Integration 5.1.1 Horizontal Integration 5.1.2 Vertical Integration 5.1.3 Options for Guiding and Fastening 5.1.4 External Window 5.1.5 External Reflective Surface Touch Applications 5.2.1 Touch Accuracy 5.2.2 Hovering Touches 5.2.3 Assembly Tolerances Translational Tolerances Rotational Tolerances...
  • Page 5  zForce AIR® Touch Sensor User's Guide Table of Contents Presentation Layer 7.3.2 Communication Protocol Quick Start Encoding Integers Enabling Sensors Disabling Sensors Device Configuration Setting Frequency Decoding Touch Notifications 7.3.3 Transport Layer I2C Transport USB HID Transport 7.3.4 Presentation Layer (ASN.1) ASN.1 PDU Description ASN.1 PDU Examples Specifications ........................72...
  • Page 6  zForce AIR® Touch Sensor User's Guide Table of Contents 8.5.2 Recommended Operating Conditions Optical Requirements on External Window 8.6.1 Optical Requirements 8.6.2 Geometrical Constraints Mechanical Data 8.7.1 Physical Dimensions and Position of Origin Top View Side View Test Specifications and Definitions 8.8.1 Reliability Test Specification Overview...
  • Page 7 AIR® Touch Sensor User's Guide Table of Contents https://support.neonode.com ...

  • Page 8: Introduction

    The sensor characteristics are high scanning frequency, low latency, good touch accuracy and the fact that it can be used on any surface or even in mid air. zForce AIR Touch Sensor can be connected to the host system through a standard connector and communicate through a standard I2C or USB interface.

  • Page 9: Sensor Orientation

    2.2.1 Sensor Orientation The zForce AIR Touch Sensor is available in two types, one where the active area emerges straight out from the sensor (0° type) and one where it emerges out from the sensor at a 90° angle (90° type). This enables both vertical and horizontal integration.

  • Page 10: Touch Active Area

    90° Type NNAMC0430PC01 NNAMC0431PC01 43.2 14.9 NNAMC0500PC01 NNAMC0501PC01 50.4 29.8 NNAMC0580PC01 NNAMC0581PC01 57.6 29.8 NNAMC0640PC01 NNAMC0641PC01 64.8 44.7 NNAMC0720PC01 NNAMC0721PC01 44.7 NNAMC0790PC01 NNAMC0791PC01 79.2 59.6 NNAMC0860PC01 NNAMC0861PC01 86.4 59.6 NNAMC0940PC01 NNAMC0941PC01 93.6 74.5 NNAMC1010PC01 NNAMC1011PC01 100.8 74.5 NNAMC1080PC01 NNAMC1081PC01 89.4 https://support.neonode.com ...
  • Page 11 178.7 NNAMC2090PC01 NNAMC2091PC01 208.8 193.6 NNAMC2160PC01 NNAMC2161PC01 193.6 NNAMC2230PC01 NNAMC2231PC01 223.2 208.5 NNAMC2300PC01 NNAMC2301PC01 230.4 208.5 NNAMC2380PC01 NNAMC2381PC01 237.6 208.5 NNAMC2450PC01 NNAMC2451PC01 244.8 208.5 NNAMC2520PC01 NNAMC2521PC01 208.5 NNAMC2590PC01 NNAMC2591PC01 259.2 208.5 NNAMC2660PC01 NNAMC2661PC01 266.4 208.5 NNAMC2740PC01 NNAMC2741PC01 273.6 208.5 https://support.neonode.com ...

  • Page 12: Basic Principles

    IR beams and receiver fields of view within the same apertures. IR light beams are emitted perpendicular to the output window, while receivers field of view is centered at a certain angle left and right. https://support.neonode.com ...

  • Page 13: Applications

    The zForce AIR Touch Sensor is a laser light based touch sensor that can be used for various touch and mid-air detection applications. The sensor is available in varying sizes, see Product Variants (see page 8) 2.5.1 Sensor Design The image below show the sensor design (0° type). The connector is shown to the far right. https://support.neonode.com ...

  • Page 14: Exploded View

    Exploded view The image below shows the sensor (0° type) in an exploded view. Part Decription Cover Adhesive Front light pipe –   straight shooting or 90 degree shooting depending on sensor type Lenses - amount depends on size PCBA https://support.neonode.com ...

  • Page 15: Sensor Components

    • Other passive components 2.6 Product Integration The zForce AIR Touch Sensor can be integrated to any host system through a physical connector with 8 contact pads with support for both I2C and USB HID. The host system can communicate with the sensor through a communication protocol and an SDK developed by Neonode.

  • Page 16: Getting Started With Zforce Air Touch Sensor Evaluation

    Getting started with zForce AIR Touch Sensor Evaluation 3 Getting started with zForce AIR Touch Sensor Evaluation This section describes how to get started with the evaluation of a zForce AIR Touch Sensor. 3.1 Evaluation Kit Contents The evaluation kit includes the following: •...
  • Page 17 Make sure the direction of the pads is straight into the connector, and the pads have reached the end of the connector. 3. To use Neonode Workbench, USB HID Digitizer mode, USB HID Raw mode, or SDK: Connect a USB cable with a Micro USB type B connector to the interface board.
  • Page 18 USB or I2C. The sensor calibrates itself when powered on and an object within the touch active area may interfere with the calibration. 6. To use Neonode Workbench, USB HID Digitizer mode, USB HID Raw mode, or SDK: Insert the USB cable into a computer meeting the requirements of USB HID or SDK, respectively.

  • Page 19: Communicating With Sensor

    3.4 Communicating with Sensor 3.4.1 Neonode Workbench Neonode Workbench is a software tool to use with zForce AIR™ sensors. With Neonode Workbench it is possible to: • Visualize sensor touches. • Temporarily configure sensor characteristics, such as active area and scanning frequency.
  • Page 20 AIR® Touch Sensor User's Guide Getting started with zForce AIR Touch Sensor Evaluation https://support.neonode.com ...

  • Page 21: Multi-Touch Functionality

    Multi-Touch Functionality 4 Multi-Touch Functionality zForce AIR Touch Sensor determine an object's position by signals derived from emitter-receiver pairs and have the capacity to detect and track several objects at the same time. Both the HW and the SW have been optimized in order to support standard touch gestures like, pinch-to-zoom, rotate, swipe and tap. However, some combinations of two or more objects might need special consideration.

  • Page 22: Adjacent Objects

    • it is not vital to track all detected objects 100% in all possible combinations and locations at all time.  • When all objects are likely to be detected by the sensor, for example when it is expected that all objects will be placed along a line that is parallel to the sensor, as in the example below. https://support.neonode.com ...

  • Page 23: Mechanical Integration

    Mechanical Integration 5 Mechanical Integration zForce AIR Touch Sensor can be used for different purposes, such as touch on a surface or motion in mid-air. Assembly requirements differ depending on what purpose the Touch Sensor fulfills. In addition, different industries have different standards and demands to fulfill.

  • Page 24: Vertical Integration

    A (mirror surface). 5.1.3 Options for Guiding and Fastening • Double adhesive tape – for smaller sizes this can be used alone to hold the zForce AIR Touch Sensor. The host system geometry needs to provide a flat supporting surface.

  • Page 25: External Window

    Mechanical Integration The zForce AIR Touch Sensor needs to be protected from outer pressure and forces that can bend the sensor and by that change the direction of the sensor light. The most common cause of bending is when a Touch Sensor is mounted on a non-flat surface, so the host system supporting structure needs to be flat.

  • Page 26: Hovering Touches

    Sensor software adjusts the signal and reports a touch first when the object reaches the surface. Hovering touches is also direct linked to how the zForce AIR Touch Sensor is integrated in the host system. It’s important that the mounting surface has the correct angle compared to the intended touch surface. Twisting and tilting of zForce AIR Touch Sensor should always be avoided.
  • Page 27 Angle "b" The angle "b" is defined as shown in the image below. How sensitive zForce AIR Touch Sensor is for assembly rotations is directly linked to the size. At any given angle b, the touch AA will be tilted twice as much at 200 mm compared to at 100 mm.
  • Page 28 AIR® Touch Sensor User's Guide Mechanical Integration https://support.neonode.com ...

  • Page 29: Electrical Integration

    The Touch Sensor has 8 contact pads and a PCB outline that matches that of a standard 0.3-0.33 mm thick FFC/FPC with 1 mm pitch and top mounted connectors: The contact pads are placed on the backside of the Touch Sensor PCBA. List of supported FFC connectors: Supplier Part number 2005290080 Molex XF3M(1)-0815-1B Omron Electronic Components http://www.molex.com/molex/home https://www.components.omron.com/ https://support.neonode.com ...

  • Page 30: Pin-Out

    I2C data line Requires external pull-up resistor I2C Clock I2C_CLK Input I2C clock line Requires external pull-up resistor USB DM USB D- USB DM line USB 2.0 Compliant USB DP USB D+ USB DP line USB 2.0 Compliant http://www.digikey.com/en/supplier-centers/w/wurth-electronics http://www.almita-connectors.com/ https://support.neonode.com ...

  • Page 31: Interface Configuration

    6.4 Interface Configuration The zForce AIR Touch Sensor provides two interfaces for communication with the host system, I2C and USB HID- device. The user can choose to connect one of them, or both. The typical Touch Sensor connection to a host system is shown in the following diagram: 6.4.1 USB Connection...
  • Page 32 USB full speed timings: the definitions of data signal rise and fall time are presented in the following table and figure: Driver characteristcs Symbol Parameter Conditions Rise time = 50pF Fall time = 50pF Rise/fall time matching Output signal crossover https://support.neonode.com ...

  • Page 33: I2C Connection

    Electrical Integration 6.4.2 I2C Connection The zForce AIR Touch Sensor provides an I2C interface through its 8-pin connector. The interface runs in fast mode, which means the speed is 400kbps. With this interface, more advanced configuration could be performed. PIN 1, 3, 4, 5, 8 ( GND, DR, I2C_DATA, I2C_CLK, VBUS ) are used for this connection. It is recommended to use two 1kΩ...

  • Page 34: Pin 3 ( Dr) Characteristics

    I2C bus. When the read transaction is finished, this DataReady signal will be reset automatically by the zForce AIR Touch Sensor. The following figure shows the timing behavior of a typical I2C transaction: https://support.neonode.com ...

  • Page 35: I2C Reading Sequence

    Delay time from USB init ready to sending/receiving data. Delay time from power on to I2C pins voltage ready. Delay time from I2C pins voltage ready to triggering boot complete packet request. The power on sequence is shown in the following figure. https://support.neonode.com ...

  • Page 36: Software Integration

    ASN.1 PDU Examples  for examples of requests, responses and notifications. (see page 68) How to communicate with the sensor is described in USB HID Transport (see page 44) 7.2.2 I2C Use the following procedure to initialize the sensor over I2C. https://support.neonode.com ...

  • Page 37: Zforce® Communication Protocol

    7.3 zForce® Communication Protocol 7.3.1 Communication Protocol Overview Introduction Neonode sensors communicate through a transport interface with ASN.1 encoded payload, with the exception of the HID Touch Digitizer mode where the payload follows the HID standard. Transport Layer Two transport interfaces are supported: USB and I2C.

  • Page 38: Presentation Layer

    Do the following to disable a sensor, that is, tell a sensor to stop sending touch notifications.  1. Disable the sensor by sending a request with the following command: 08 40 02 02 00 65 02 80 00 This disables the sensor to send touch notifications. https://support.neonode.com ...

  • Page 39: Device Configuration

    ID for request followed by length of total payload (0x1A = 26 bytes) 40 02 02 Device address (always the same for the zForce AIR Touch Sensor) 73 14 ID for Device Configuration followed by the length of the total Device Configuration payload (20...

  • Page 40: Decoding Touch Notifications

    40 02 00 00 68 07 80 02 00 82 01  The zForce AIR Touch Sensor does not support Stylus mode, and setting the stylus frequency does not do anything. Decoding Touch Notifications A packet can contain one, two or three Touches, and optionally a timestamp. On packets where the timestamp is not included, the 58 02 TT TT bytes are missing from the end and the length bytes are adjusted accordingly, For One touch (below), F0 15 in the beginning will be F0 11 and A0 0F in the middle will be A0 0B.

  • Page 41: Transport Layer

    The sensor does not communicate using registers / memory accesses, so the STM32 documentation is not applicable. To maximize performance and minimize the load on the I2C bus, the host is expected to read data in a certain sequence. This ensures a stable and reliable communication. The I2C read sequence is specified below. https://support.neonode.com ...
  • Page 42 All bytes in this section are written in hexadecimal form, if not indicated otherwise. The first two bytes are: EE XX [payload] Where EE is a constant and XX is number of bytes of ASN.1 payload. So, for example, if the ASN.1 payload is 8 bytes long, the I2C Transport Protocol is: https://support.neonode.com ...
  • Page 43 2. Host initiates a 2 byte I2C Read operation for I2C 7-bit Address 0x50. 3. The sensor fills in the 2 Bytes. These two bytes are (as described above) EE XX where XX is the length of the following ASN.1 Payload. https://support.neonode.com ...

  • Page 44: Usb Hid Transport

    • Send data to the sensor by writing to Feature Report 1.  • Input Report 2 indicates that there is data to read • Read data from the sensor by reading from Feature Report 2. Refer to ASN.1 PDU Examples  for examples of requests, responses and notifications. http://confluence.neonode.local/display/ZAMCD/.ASN.1+PDU+Examples+v1.0 https://support.neonode.com ...
  • Page 45     Usage (Contact count) 09 54     Input (Data,Value,Absolute,Bit Field) 81 02     Usage (Scan Time) 09 56     Logical maximum (65 535) 27 FF FF 00 00     Report Size (16) 75 10     Unit Exponent (12) 55 0C     Unit (SI Linear: Time [s]) 66 01 10     Input (Data,Value,Absolute,Bit Field) 81 02     Usage (Finger) 09 22 https://support.neonode.com ...
  • Page 46         Report Size (16) 75 10         Report Count (1) 95 01         Input (Data,Value,Absolute,Bit Field) 81 02         Usage (Y) 09 31         Input (Data,Value,Absolute,Bit Field) 81 02         Usage Page (Digitizer) 05 0D         Unit Exponent (14) 55 0E         Unit (SI Linear: Distance [cm]) 65 11         Usage (Width) 09 48         Usage (Height) 09 49 https://support.neonode.com ...
  • Page 47 95 01         Input (Data,Value,Absolute,Bit Field) 81 02         Usage Page (Generic Desktop) 05 01         Usage (X) 09 30         Logical maximum (65 535) 27 FF FF 00 00         Report Size (16) 75 10         Report Count (1) 95 01         Input (Data,Value,Absolute,Bit Field) 81 02         Usage (Y) 09 31         Input (Data,Value,Absolute,Bit Field) 81 02 https://support.neonode.com ...
  • Page 48         Usage (Contact identifier) 09 51         Logical maximum (127) 25 7F         Report Size (7) 75 07         Report Count (1) 95 01         Input (Data,Value,Absolute,Bit Field) 81 02         Usage Page (Generic Desktop) 05 01         Usage (X) 09 30         Logical maximum (65 535) 27 FF FF 00 00         Report Size (16) 75 10 https://support.neonode.com ...
  • Page 49         Usage (Tip Switch) 09 42         Logical maximum (1) 25 01         Report Size (1) 75 01         Report Count (1) 95 01         Input (Data,Value,Absolute,Bit Field) 81 02         Usage (Contact identifier) 09 51         Logical maximum (127) 25 7F         Report Size (7) 75 07         Report Count (1) 95 01         Input (Data,Value,Absolute,Bit Field) 81 02 https://support.neonode.com ...
  • Page 50         Report Count (2) 95 02         Input (Data,Value,Absolute,Bit Field) 81 02     End Collection C0      Usage (Finger) 09 22     Collection (Logical) A1 02         Usage (Tip Switch) 09 42         Logical maximum (1) 25 01         Report Size (1) 75 01         Report Count (1) 95 01         Input (Data,Value,Absolute,Bit Field) 81 02         Usage (Contact identifier) 09 51 https://support.neonode.com ...
  • Page 51         Unit Exponent (14) 55 0E         Unit (SI Linear: Distance [cm]) 65 11         Usage (Width) 09 48         Usage (Height) 09 49         Report Count (2) 95 02         Input (Data,Value,Absolute,Bit Field) 81 02     End Collection C0      Usage (Finger) 09 22     Collection (Logical) A1 02         Usage (Tip Switch) 09 42         Logical maximum (1) 25 01 https://support.neonode.com ...
  • Page 52         Input (Data,Value,Absolute,Bit Field) 81 02         Usage (Y) 09 31         Input (Data,Value,Absolute,Bit Field) 81 02         Usage Page (Digitizer) 05 0D         Unit Exponent (14) 55 0E         Unit (SI Linear: Distance [cm]) 65 11         Usage (Width) 09 48         Usage (Height) 09 49         Report Count (2) 95 02         Input (Data,Value,Absolute,Bit Field) 81 02 https://support.neonode.com ...
  • Page 53 95 40     Feature (Data,Value,Absolute,Volatile,Buffered Bytes) B2 82 01     Report Id (2) 85 02     Usage (Vendor-defined 0x0001) 09 01     Report Count (1) 95 01     Feature (Data,Value,Absolute,Non-volatile,Bit Field) B1 02     Usage (Vendor-defined 0x0002) 09 02     Report Count (64) 95 40     Feature (Data,Value,Absolute,Volatile,Buffered Bytes) B2 82 01     Usage (Vendor-defined 0x0003) 09 03 https://support.neonode.com ...
  • Page 54     Usage (Vendor-defined 0x0001) 09 01     Feature (Constant,Value,Absolute,Non-volatile,Bit Field) B1 03 End Collection C0  Parsed reports by Report ID Input Report 2 Bit offset Bit count Description Vendor-defined 0x0003 (Not used) Input Report 3 Bit offset Bit count Description Contact count Scan Time https://support.neonode.com ...
  • Page 55 AIR® Touch Sensor User's Guide Software Integration Tip Switch Contact identifier Width Height Tip Switch Contact identifier Width Height Tip Switch Contact identifier Width Height Tip Switch Contact identifier Width Height Tip Switch https://support.neonode.com ...
  • Page 56 Contact identifier Width Height Feature Report 1 Bit offset Bit count Description Vendor-defined 0x0001 Vendor-defined 0x0002 Feature Report 2 Bit offset Bit count Description Vendor-defined 0x0001 Vendor-defined 0x0002 Feature Report 4 Bit offset Bit count Description Contact count maximum https://support.neonode.com ...

  • Page 57: Presentation Layer (Asn.1)

    7.3.4 Presentation Layer (ASN.1) ASN.1 PDU Description PDU Definition Download the ASN.1 PDU definition file from https://support.neonode.com/docs/display/downloads. Introduction This document describes the host interface to a sensor. The host interface is the means for which an outside device can communicate with the sensor. The communication protocol is using ASN.1 (Abstract Syntax Notation One) which is a standard and a notation that is described in ISO/IEC 8824.
  • Page 58 In the response, the command is of the same PDU as in the reponse, but now contains the result or requested information of the request. The   PDU contains the   and the  . Some notifications Notification deviceAddress notificationMessage contain the  notificationTimestamp Encoding Rules http://www.itu.int/ITU-T/studygroups/com17/languages/ http://luca.ntop.org/Teaching/Appunti/asn1.html http://www.oss.com/resources/resources.html http://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx https://support.neonode.com ...
  • Page 59 The application interface specifies what requests can be made and what responses and notifications they activate. Messages will be specified using the templates below, and specifying only: • address • request command • command response • notification https://tools.ietf.org/html/rfc3641#page-6 http://www.bellard.org/ffasn1/ https://support.neonode.com ...
  • Page 60 • 2: Air • 3: Plus • 4: Lighting Eg. '0000'H for platform. timestamp Integer representing int16 counting at 32768 Hz. Platform Platform commands relate to generic system information and settings. These are using the platform address: address '0000'H https://support.neonode.com ...
  • Page 61 • firmware: product FW version • hardware: Product hardware, with configuration and revision • asic: Which type of the Neonode optical scanner ASICs is used, and count • mcuUniqueIdentifier: Identifier created at chip manufacturing • Reference: FW GIT tags or hashes for: •...
  • Page 62 There are a number of different touch sensor products that can co-exist on the same physical device. They have some product-specific commands, but the ones listed here are general. Air will be used as example, which means the device address will be that of the first Air virtual device: https://support.neonode.com ...
  • Page 63 As can be seen gestures is missing in the response. This is valid response, since the device has been built with a subset of the protocol, or an older forward-compatible version. Touch Format Retrieve the binary format of the detected objects.  request command touchFormat { command response touchFormat { https://support.neonode.com ...
  • Page 64 X size for higher precision size-y-byte1 Y size size-y-byte2 Y size for higher precision size-y-byte3 Y size for higher precision size-z-byte1 Z size size-z-byte2 Z size for higher precision size-z-byte3 Z size for higher precision https://support.neonode.com ...
  • Page 65  * 9/16[ ([0, 16383], [0, 9215]).  The zForce AIR Touch Sensor uses Robair, thus the unit is 0.1 mm. Size is in mm. Confidence and pressure is fraction of full in percent. Enable Execution This command will activate the touch sensor, and notifications of detections will start streaming.Enable...
  • Page 66 0=Down; 1=Move; 2=Up; 3=Invalid; 4=Ghost  1 loc-x-byte1 X coordinate  1 loc-x-byte2 X expanded for higher precision 54  loc-y-byte1 Y coordinate 0  loc-y-byte2 Y expanded for higher precision 115  size-x-byte1 X size 10  size-y-byte1 Y size 10  confidence Confidence 100  https://support.neonode.com ...
  • Page 67 For instance, to set object size restrictions only, omit all other items: request command deviceConfiguration { sizeRestriction { maxSizeEnabled TRUE, maxSize 100, minSizeEnabled FALSE The command response contains the state of all configuration items: https://support.neonode.com ...

  • Page 68: Asn.1 Pdu Examples

    • If the integer is between 0 and 127, it is represented by one byte ( • If the integer is between 128 and 32767, it is represented by two bytes ( to   00 80 7F FF https://support.neonode.com ...
  • Page 69 12 80 02 00 81 01 43 82 02 06 98 83 02 04 34 85 01 The message is explained in the table below: Part Description EE 1A ID for "Request" followed by length of total payload (0x1A = 26 bytes) https://support.neonode.com ...
  • Page 70 40 02 00 00 68 07 80 02 00 82 01  The zForce AIR Touch Sensor does not support Stylus mode, and setting the stylus frequency does not do anything. Decoding Touch Notifications A packet can contain one, two or three Touches, and optionally a timestamp. On packets where the timestamp is not included, the 58 02 TT TT bytes are missing from the end and the length bytes are adjusted accordingly, For One touch (below), F0 15 in the beginning will be F0 11 and A0 0F in the middle will be A0 0B.
  • Page 71 40 02 02 00 25 42 09 II VV XX XX YY YY GG HH JJ 42 09 II VV XX XX YY YY GG HH JJ 42 09 II VV XX XX YY YY GG HH JJ 58 02 TT TT https://support.neonode.com ...

  • Page 72: Specifications

    Scanning Frequency (see page 74) 8.1.2 Technical Specification Item  Sensor Variant  Specification  Module size (LxHxW) 0° Type L x 3.46 x 14.5 mm  L depending on product variant. L x 3.46 x 15.45 mm 90° Type L depending on product variant. https://support.neonode.com ...

  • Page 73: Touch Performance

    Definition The touch accuracy of the zForce AIR Touch sensor can be described statistically with the normal distribution and a standard deviation of 2 sigma. This means that the touch position reported by the sensor will deviate less than the specified value in 95% of the cases.

  • Page 74: Specification

    8.2.4 Scanning Frequency The scanning frequency can be set using the Neonode API. The default value is 100 Hz in active mode, that is, when an object is detected or tracked. The default value in idle mode, that is, when no object is detected or tracked, is 25 Hz.

  • Page 75: Power Consumption

    25 Hz, with a clean active area. With higher scanning frequency or more detected objects, the power consumption might slightly higher than the values in the graph. The sensor will only be in active mode when a touch object is being detected or tracked. https://support.neonode.com ...

  • Page 76: Definition

    According to the different working modes of the Touch Sensor, the current consumption value also changes between Active mode and Idle mode. 8.4 Environmental Requirements 8.4.1 Operating and Storage Conditions Condition Operation Storage Temperature –20°C to +65°C –40°C to +85°C Humidity 5% to 95% 0% to 95% ≤5000 m ≤15 km Altitude https://support.neonode.com ...

  • Page 77: Esd Rating

    If light is lost, scattered or diverted it will lead to shorter detection range and lower touch accuracy. 8.6.1 Optical Requirements Window material must be optically clear, without absorption and have optical quality surfaces. • Transmission: > 88 % at 975nm • Haze: < 3% https://support.neonode.com ...

  • Page 78: Geometrical Constraints

    8.6.2 Geometrical Constraints The zForce AIR Touch Sensor is an optical system that both emits and receives IR-light at different incident angles. When the light hits a transparent material, most of the light is transmitted through the material and exit on the other side.

  • Page 79: Mechanical Data

    Product number Measurements (mm) 0° 90° NNAMC0430PC01 NNAMC0431PC01 43.2 14.9 47.2 NNAMC0500PC01 NNAMC0501PC01 50.4 29.8 55.9 NNAMC0580PC01 NNAMC0581PC01 57.6 29.8 61.6 NNAMC0640PC01 NNAMC0641PC01 64.8 44.7 70.3 NNAMC0720PC01 NNAMC0721PC01 44.7 NNAMC0790PC01 NNAMC0791PC01 79.2 59.6 84.7 NNAMC0860PC01 NNAMC0861PC01 86.4 59.6 90.4 https://support.neonode.com ...
  • Page 80 178.7 199.9 NNAMC2020PC01 NNAMC2021PC01 201.6 178.7 205.6 NNAMC2090PC01 NNAMC2091PC01 208.8 193.6 214.3 NNAMC2160PC01 NNAMC2161PC01 193.6 NNAMC2230PC01 NNAMC2231PC01 223.2 208.5 228.7 NNAMC2300PC01 NNAMC2301PC01 230.4 208.5 234.4 NNAMC2380PC01 NNAMC2381PC01 237.6 208.5 243.1 NNAMC2450PC01 NNAMC2451PC01 244.8 208.5 248.8 NNAMC2520PC01 NNAMC2521PC01 208.5 257.5 https://support.neonode.com ...

  • Page 81: Side View

    NNAMC3381PC01 338.4 208.5 343.9 NNAMC3460PC01 NNAMC3461PC01 345.6 208.5 349.6 Side View These measurements are identical for all sensor lenghts but varies some between the 0° and 90 ° types. The position of origin is marked with "zero software".   https://support.neonode.com ...

  • Page 82: Test Specifications And Definitions

    AIR® Touch Sensor User's Guide Specifications 0° Type 90 °  Type 8.8 Test Specifications and Definitions 8.8.1 Reliability Test Specification Overview TEST ITEM TEST CONDITION QUANTIT zForce AIR Touch Sensor: https://support.neonode.com ...
  • Page 83 One time each direction Pressure Intensity  Pressure on surface with a flat ø 10 mm  rod with a force of 10 N. The force should be applied at the center of the PCB. Test for 168 hrs. Power Off https://support.neonode.com ...

  • Page 84: Reliability Test Report

    All purpose cleaning solution containing ammonia (e.g. AJAX Tornado). o Water. EN55024 (61000-4-2) Direct contact discharge: 2,4,8 kV Indirect contact discharge: 2,4,8 kV Air discharge: 4,8,16 kV 8.8.2 Reliability Test Report The reliability test report can be found in Downloads on https://support.neonode.com https://support.neonode.com/ https://support.neonode.com ...

Table of Contents