NEONODE zForce AIR Touch Sensor User Manual page 59

zForce AIR® Touch Sensor User's Guide
When applying a set of Encoding Rules to the ASN.1 definitions, one gets the data format used for the interchange.
zForce uses the Distinguised Encoding Rules (DER).
In this document, examples will be given with the human readable Generic String Encoding Rules (GSER). Here is
one such example:
request: {
deviceAddress '0200'H,
enable {
enable NULL
}
}
GSER Notation
The examples written down in GSER notation will hopefully be quite easy to read, but some parts are not
necessarily obvious. So, as a lead to it here's a list of used notation:
Sequences and/or sets (items containing sub items) are shown as curly brackets: { <sub elements> }
Values encoded as octet strings are written as hexadecimal octets enclosed within single quotes and suffixed with
H: 'FF9900'H
Bit strings are also shown as octet strings when the number of bits is a multiple of 8, otherwise each bit is shown as
a single 1 or 0, and suffixed with B: '11010101001'B
In a choice element, the selected type is denoted by its name followed by a colon: request:
Full reference at Generic String Encoding Rules (GSER) for ASN.1 Types
Tools
14
The tool FFASN1Dump
ffasn1dump -I gser -O der zforce_pdu_def.asn ProtocolMessage <input file> <output file>

Currently ffasn1dump does not handle identifiers for Integer values. For this reason, they need to be
replaced with numerical values.
Application Interface
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
13
http://www.bellard.org/ffasn1/
14
https://support.neonode.com
can transcode from GSER to DER:
13
.
Software Integration
59