...
Downloading the definition file
Download the zForce® PDU zForce® PDU definition file Downloads.
Type, Length, Value
All ASN.1 messages are structured by type, length and value:
...
Bit position reserved for | 8th and 7th | 6th | 5th to 1st | ||||||
---|---|---|---|---|---|---|---|---|---|
Specific bit value
| Binary representation | XX00 0000 | 00X0 0000 | 000X XXXX | |||||
Decimal representation | 0, 64, 128, 192 | 0 or 32 | 0 to 30 (31 is reserved, see the table below) | ||||||
Hexadecimal representation | 0x00, 0x40, 0x80, 0xC0 | 0x00 or 0x20 | 0x00 to 0x1E (0x1F is reserved, see the table below) | ||||||
Description | Class tag | Primitive/sequence | Tag number |
...
Step | What to do | Details | Result | The message |
---|---|---|---|---|
1 | Add the code for a request, since the message will be sent from the host to the sensor module: 0xEE 0xXX | EE XX | EE XX | |
2 | Add the device address 0x40 0x02 0x02 0x00 | See Device Address. | 40 02 02 00 | EE XX 40 02 02 00 |
3 | Add the bytes for deviceConfiguration | The command deviceConfiguration has the class tag Application, tag number 19 and is a sequence. | Binary: 0111 0011 | EE XX 40 02 02 00 73 |
4 | Add the bytes for SubTouchActiveArea | SubTouchActiveArea is a context-specific sequence with tag number 2. | Binary: 1010 0010 | EE XX 40 02 02 00 73 XX A2 XX |
5 | Add the variables inside of SubTouchActiveArea.. | All the variables are context-specific and primitive (binary 1000 0000, hexadecimal 0x80). Depending on which variable that is currently being added, add the specific tag number. | Per variable: | EE XX 40 02 02 00 73 XX A2 XX 80 XX 01 F4 81 XX 01 F4 82 XX 07 D0 83 XX 07 D0 |
6 | Add the length bytes of the message. | Add the number of bytes for each specific part of the message. | - | EE 18 40 02 02 00 73 12 A2 10 80 02 01 F4 81 02 01 F4 82 02 07 D0 83 02 07 D0 |
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Read More on Software Integration
Read More
|