Please note that the TLP was called “MOIR protocol”
TLP Protocol for Sending Commands and Receiving Responses
Every command and response follows the same basic structure: HEADER DATA TRAILER
The HEADER :<60> followed by . The HEADER consists of <60> followed by <Command Length>. The <Command Length> are two bytes: most significant then least significant byte.
For the setting commands(command ID 0x53), the DATA often consists of the Command ID, Function ID, Function Length, and Function Data.
For get setting commands (command ID 0x52), the DATA consists of the Command ID and one Functional ID.
The TRAILER consists of <LRC> followed by <ETX>.
The maximum size of length is 768 (including envelope bytes). For the setting commands(command ID 0x53), the DATA often consists of the Command ID, Function ID, Function Length, and Function Data. For get setting commands (command ID 0x52), the DATA consists of the Command ID and one Functional ID. The TRAILER consists of followed by . The maximum size of length is 768 (including envelope bytes). 7.1.1
Send Setting Command Command:
...
60<Command Length><Command ID>><FuncSETBLOCK1>…<FuncSETBLOCKn> <LRC><ETX>
Each function-setting block <FuncSETBLOCK> has following format: <FuncID><Len><FuncData>
Where: <Command Length> = is a two-byte count of the bytes in the DATA field
<Command ID> = is a one byte value identifying a specific command ID. See section 7.3 for command ID list. Only ‘0’, ‘1’ or ‘S’ command IDs are allowed for the send setting commands.
<FuncID> = is a one byte Function ID, which identifies the particular function or settings affected
<Len> = is a one-byte length count for the data block “” “
<FuncData>” <FuncData> = is the data block for the function
<LRC> = See Calculation in section below = 03 Copyright © 2015, International Technologies & Systems Corporation. All rights reserved. Page 20 of 96 ID TECH Secure MOIR User Manual 7.1.2 Get Setting Command This Get Setting Command will get the reader’s current setting Host Command Reader Response Status Command: 60 Response: 60 [] Where: = is a two-byte counter from to the end of . = always ‘R’ = is the data block associated with the Response. is a two-byte value indicating the success or failure of a command. The overall LRC (Modulus 2 = Exclusive OR) from 60 to LRC should be zero. See example of LRC calculation below. 7.1.3 Example of LRC Calculation LRC = Longitudinal Redundancy Check. Calculated by taking ‘Exclusive OR’ (Modulus 2) of all characters preceding it, total with LRC is equal to zero. For example, the following command means "Set to 0x30 value”. <60><00><04><53><19><01><30><1F><03> <1F> is the LRC character. It is derived from the following: Characters #1(binary) #2 (binary) <60> 0110 0000 <00> 0000 0000 <04> 0000 0100 <53> 0101 0011 <19> 0001 1001 <01> 0000 0001 <30> 0011 0000 <1F> 0001 1111 7.1.4 Communication Timing The maximum delay for a command to be written into the reader is per configuration. Typical delay is 5ms for one setting one configuration byte. During the command processing time, the reader will not respond to a new command. The reader will accept a new command as soon as it has responded to the previous command. Note: Maximum delay between two characters in a command is 100ms for USB CDC interface, 30ms for USB HID and 10ms for RS232. Copyright © 2015, International Technologies & Systems Corporation. All rights reserved. Page 21 of 96 ID TECH Secure MOIR User Manual During command processing or the reading of a magnetic stripe, the reader will not respond to a new command. The typical delay for the reader to respond to a setting command is less than 20ms with the exception that all settings are being reset to their default settings. Once communication between the host and the reader has been established, sending the appropriate setup commands to the reader from the host application can enter changes into the reader’s settings. Please see the following sections for the explanations and examples of the proper format and command content to send commands to the reader. All commands and characters are expressed in hex format and contained in brackets.There are two protocols for the SecureMOIR. One is the TLP (Turbo Transport Layer Protocol-224), the other is ITP (ID TECH Transport Protocol). These two protocols have different HEADER and TRAILER, but share the same DATA. Please note that the TLP was called “MOIR protocol” and ITP was called “NGA” in previous user manual versions. To choose the reader response protocol when the reader is first powered, just send command in the protocol which you want, and the SecureMOIR will respond in the same protocol as the commands. If no commands have been sent to the reader, for secure output the reader uses the setting of ITP bit
<ETX> = 03
EXAMPLES: