SCM Microsystems Reference Manual – version 1.
Reference manual SCL010/01X Multiprotocol Contactless Stationary Reader © SCM Microsystems Oskar-Messter-Strasse, 13 85737 Ismaning Germany Phone +49 89 9595 5000 • Fax +49 89 9595 5555
Document history Date Version Description of change 22/12/2008 1.0 Initial version 05/01/2009 1.1 Review and update by product manager 05/03/2009 1.2 Review and update before release 02/04/2009 1.3 Integration of comments and misc. updates before release 18/04/2009 1.4 Integration of comments and misc. updates before release 23/04/2009 1.5 Integration of internal review comments. 03/11/2009 1.6 Added Escape commands, Mifare Plus commands Contact information http://www.scmmicro.
SCL010/01X REFERENCE MANUAL Table of Contents 1. Legal information ............................................................................................................... 7 1.1. Disclaimers..................................................................................................................... 7 1.2. Licenses ......................................................................................................................... 7 1.3. Trademarks ..................................
SCL010/01X REFERENCE MANUAL 5.4.2. 6. Automatic PPS...................................................................................................... 27 Commands description .................................................................................................... 28 6.1. Generic APDU.............................................................................................................. 28 6.1.1. Get UID Command .......................................................................
SCL010/01X REFERENCE MANUAL 7 1. Legal information 1.1. Disclaimers The content published in this document is believed to be accurate. SCM Microsystems does not, however, provide any representation or warranty regarding the accuracy or completeness of its content and regarding the consequences of the use of information contained herein. If this document has the status “Draft”, its content is still under internal review and yet to be formally validated.
SCL010/01X REFERENCE MANUAL 1.4. 8 Federal Communication Commission (FCC) statement Information to user: This device complies with Part 15 of the FCC Rules. Operation of this device is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
SCL010/01X REFERENCE MANUAL 9 2. Introduction to the manual 2.1. Objective of the manual This manual provides an overview of the hardware and software features of the SCL010/01X contactless reader, hereafter referred to as “SCL010/01X”. This manual describes in details interfaces and supported commands available for developers using SCL010/01X in their applications. 2.2. Target audience This document describes the technical implementation of SCL010/01X. The manual targets software developers.
SCL010/01X REFERENCE MANUAL 2.4.
SCL010/01X REFERENCE MANUAL 2.5.
SCL010/01X REFERENCE MANUAL 2.6. Conventions Bits are represented by lower case ‘b’ where followed by a numbering digit. Bytes are represented by upper case ‘B’ where followed by a numbering digit.
SCL010/01X REFERENCE MANUAL 13 3. General information about SCL010/01X 3.1. SCL010/01X key benefits With its combination of a modern slim design and its state of the art multi-protocol feature set, SCL010/01X is the perfect desktop reader choice to support various contactless applications such as electronic ID, payment & public transportation schemes and to interact with NFC-enabled devices.
SCL010/01X REFERENCE MANUAL 3.3. SCL010/01X ordering information Item Part number SCL010/01X 905073 Cradle 905106 Snap-on card holder 905107 Contactless SDK 905124 3.4. 14 It is important to note that those accessories are incompatible with each other – i.e. when the snap-on card holder is fitted on the SCL010/01X, the cradle cannot be used anymore.
SCL010/01X REFERENCE MANUAL 15 3.5. Contactless communication principles and SCL010/01X usage recommendations SCL010/01X is a contactless reader1 designed to communicate with user tokens.
SCL010/01X REFERENCE MANUAL 16 3.5.3. Recommendations The communication between the reader and the user token is sensitive to the presence of material or objects interfering with the magnetic field generated by the reader. The presence of conductive materials like metal in the vicinity of the reader and the user token can severely degrade the communication and even make it impossible.
SCL010/01X REFERENCE MANUAL 3.6. 17 Applications 3.6.1. General SCL010/01X is a transparent reader designed to interface a personal computer host supporting PC/SC interface with 13.56MHz user tokens like public transport cards, contactless banking cards, NFC forum tags, electronic identification documents – e.g. e-passports, e-ID cards, driving licenses etc.
SCL010/01X REFERENCE MANUAL 18 4. SCL010/01X characteristics 4.1. SCL010/01X high level architecture 4.1.1. Block diagram The link between SCL010/01X and the host to which it is connected is the USB interface providing both the power and the communication channel. SCL010/01X has a device controller which is SCM’s STC3 ASIC. This ASIC has several interfaces available.
SCL010/01X REFERENCE MANUAL 4.2. 19 Quick reference data 4.2.1. SCL010/01X dimensions Item Characteristic Value Weight External dimensions Cable length Default color Default logo 70 Grams L 110 mm W 65mm H 8mm 1 Meter Cool gray textured SCM logo SCL010/01X Default label Weight 32 Grams External dimensions L 83mm W 80mm H 40 mm Default color Cool gray Weight 7 Grams Snap-on card holder External dimensions L 72mm W 65mm H 11.
SCL010/01X REFERENCE MANUAL 20 Reader / card errors 100ms ON; 100ms OFF (repeats for 5s) 4.2.3. Other data Parameter Value/Description DC characteristics High bus powered (SCL010/01X draws power from USB bus) Voltage: 5V Max. Current : 300mA Suspend current : 230uA Clock of the device controller RF carrier frequency Modulation 24 MHz 13.
SCL010/01X REFERENCE MANUAL 21 5. Software modules 5.1. Installation SCM provides an installer for Windows. The installer can be used to install the driver as well as some utilities. 5.2.
SCL010/01X REFERENCE MANUAL 22 5.3.3. PC/SC 2.0 compliant ATR When a user token is placed on the reader, initialization and anti-collision is performed. The user token is automatically activated and an ATR is built as defined in the PC/SC specification. For NFC Forum tag types 1 and 3, there is no definition in PC/SC. 5.3.3.1.
SCL010/01X REFERENCE MANUAL 23 0x00 0x00 0x00 0x00 4+n 4 RFU bytes TCK XOR of all previous bytes Example of the ATR built for contactless storage tokens: MIFARE Classic 4K 5.3.3.3. MIFARE Ultralight ATR for an NFC Forum tag type 1 user token (Topaz) Byte# Value Designation Description 0 0x3B Initial header 1 0x82 T0 TD1 present.
SCL010/01X REFERENCE MANUAL 5.3.3.4. 24 ATR for a NFC Forum tag type 3 user token (FeliCa) Byte# Value Designation Description 0 0x3B Initial header 1 0x8C T0 TD1 present.
SCL010/01X REFERENCE MANUAL 5.3.3.5. 25 ATR for ISO/IEC 14443-4 user tokens The user token exposes its ATS or application information which is mapped to an ATR. The table describes how this mapping is done. Byte# Value Designation Description 0 0x3B Initial header 1 0x8n T0 n indicates the number of historical bytes in following ATR 2 0x80 TD1 Nibble8 indicates no TA2, TB2, TC2 Nibble 0 means T=0 3 0x01 TD2 Nibble8 indicates no TA3, TB3, TC3 Nibble 1 means T=1 4...
SCL010/01X REFERENCE MANUAL 5.4. 26 Firmware 5.4.1. CCID-like transport protocol SCL010/01X implements a transport protocol that is compliant with USB Device Class: Smart Card CCID Specification for Integrated Circuit(s) Cards Interface Devices Revision 1.10. This paragraph describes the CCID specification features that are implemented and those that are not implemented. PC/SC 2.
SCL010/01X REFERENCE MANUAL 5.4.1.3. 27 CCID Error Codes Extensive error codes are reported on many conditions during all CCID responses. Most of the error messages are reported by the CCID appropriately. Some of the main error codes are: HW_ERROR XFR_PARITY_ERROR The following sub-sections discuss when and why these error codes are returned: 5.4.1.3.1. HW_ERROR This error code is returned when the self test of PN512 fails. This error code has been defined in the error code table 6.
SCL010/01X REFERENCE MANUAL 28 6. Commands description 6.1. Generic APDU 6.1.1. Get UID Command 6.1.1.1. Description GET UID will retrieve the UID or SNR or PUPI of the user token. This command can be used for all supported technologies. 6.1.1.2. Format CLA INS P1 P2 Lc Data in Le 0xFF 0xCA 0x00 0x00 - - XX Setting Le = 0x00 can be used to request the full UID or PUPI is sent back.(e.g. for ISO14443A single 4 bytes, double 7 bytes, triple 10 bytes, for ISO14443B 4 bytes PUPI). 6.1.1.
SCL010/01X REFERENCE MANUAL 6.1.1.5.
SCL010/01X REFERENCE MANUAL 30 6.1.2. Escape command APDU 6.1.2.1. Description This command can be used to send escape commands to SCL010/01X. For description of escape commands please refer to chapter 6.5 in this manual. 6.1.2.2. Format CLA INS P1 P2 P3 Data in 0xFF 0xCC 0x00 0x00 Lc Input buffer of escape command Lc is the length of the escape command’s input buffer. See escape commands description later in this manual 6.1.2.3. Response Output buffer of the escape command. 6.1.2.4.
SCL010/01X REFERENCE MANUAL 6.2. 31 Set of APDU for contactless storage user tokens 6.2.1. STORAGE_CARD_CMDS_READ_BINARY 6.2.1.1. Description Using this APDU, application can read a memory block on user tokens based on technologies like MIFARE Classic 1K or 4K (block size 0x10 bytes) or MIFARE Ultra light (block size 0x04 bytes). 6.2.1.2.
SCL010/01X REFERENCE MANUAL 0x6C 0xXX 6.2.1.5.
SCL010/01X REFERENCE MANUAL 33 6.2.2. STORAGE_CARD_CMDS_WRITE_BINARY 6.2.2.1. Description This APDU writes data pattern in to a memory address 6.2.2.2. Format CLA INS P1 P2 Lc Data in 0xFF 0xD6 Address MSB Address LSB 0xXX Data Where: P2 indicate the memory block number where data should be written Lc=0x10 for MIFARE Classic 1K/4K.
SCL010/01X REFERENCE MANUAL 6.2.2.5.
SCL010/01X REFERENCE MANUAL 35 6.2.3. STORAGE_CARD_CMDS_LOAD_KEYS 6.2.3.1. Description Some type of user tokens like MIFARE Classic may require that an authentication happens before any data can be read or written. To perform this authentication, keys need to be loaded in the reader’s memory using this command. 6.2.3.2.
SCL010/01X REFERENCE MANUAL 36 6.2.4. STORAGE_CARD_CMDS_AUTHENTICATE 6.2.4.1. Description This command enables to perform authentication for user tokens based on MIFARE Classic 1K or 4K. Before this command can be successfully executed, the STORAGE_CARD_CMDS_LOAD_KEY command must have been executed successfully. 6.2.4.2.
SCL010/01X REFERENCE MANUAL 6.2.4.5. Example For a MIFARE Classic 1K card which has the following memory mapping: Reading sector 0 or sector 1 of this card requires authentication with key A or key B.
SCL010/01X REFERENCE MANUAL 38 6.2.5. STORAGE_CARD_CMDS_VALUE_BLOCK 6.2.5.1. Description This APDU is used to interact with MIFARE Classic e-purse applications. Please refer to MIFARE Classic documentation available from NXP Semiconductors for further details on MIFARE classic memory mapping and commands. 6.2.5.2.
SCL010/01X REFERENCE MANUAL 6.3. 39 Set of APDU for ISO/IEC14443-4 user tokens 6.3.1. T=CL Command Description SCL010/01X can transfer directly ISO/IEC7816-4 APDU to the PICC. SCL010/01X supports user tokens that have both the MIFARE and T=CL partitions. Depending on the APDU sent by the host, the reader switches to the corresponding mode (MIFARE or T=CL) automatically and the command is processed accordingly. 6.3.1.1.
SCL010/01X REFERENCE MANUAL 40 6.3.2. T=CL user command Description This command can be used to send raw data to the user token. 6.3.2.1. Format CLA INS P1 P2 P3 Data 0xFF 0xFE 0x00 0x00 Lraw_data Raw_data 6.3.2.2. Response Data Out PICC response data+ SW1 + SW2 6.3.2.3. SW1 SW2 Status Words Description User should refer to the status words defined by the PICC manufacturer for a description of the status words 6.3.2.4. Example Let’s consider the Select command defined in ISO7816-4.
SCL010/01X REFERENCE MANUAL 6.4. 41 Set of APDU defined by SCM Microsystems 6.4.1. MIFARE DESFire Commands Description This command can be used to send commands to DESFire-based user tokens. For a description of DESFire commands please contact NXP Semiconductors.
SCL010/01X REFERENCE MANUAL 42 6.4.3. Commands for communicating with NFC Forum Tags Type 1 Commands for Static and Dynamic Memory Models Read Identification (RID) Read All Blocks 0 – Eh (RALL) Read Byte (READ) Write-Erase Byte (WRITE-E) Write-No-Erase Byte (WRITE-NE) Commands for Dynamic Memory Model Read Segment (RSEG) Read 8 Bytes (READ8) Write-Erase 8 Bytes (WRITE-E8) Write-No-Erase 8 Bytes (WRITE-NE8) 6.4.3.1.
SCL010/01X REFERENCE MANUAL 6.4.3.2. 43 Read All Blocks (RALL) Description The RALL command reads-out the two header ROM bytes and the whole of the static memory blocks 0x0-0xE.
SCL010/01X REFERENCE MANUAL 6.4.3.3. 44 Read Byte (READ) Description This command reads a single EEPROM memory byte within the static memory model area of blocks 0x0-0xE.
SCL010/01X REFERENCE MANUAL 6.4.3.4. 45 Write-Erase Byte (WRITE-E) Description This commands erases and then writes the value of an individual memory byte within the static memory model area of blocks 0x0-0xE.
SCL010/01X REFERENCE MANUAL 46
SCL010/01X REFERENCE MANUAL 6.4.3.5. 47 Write-No-Erase Byte (WRITE-NE) Description This command writes a byte value on an individual memory byte within the static memory model area of blocks 0x0-0xE. This command does not erase the value of the targeted byte before writing the new data. Execution time of this command by NFC Forum tags type 1, is approximately half that of the normal write command (WRITE-E). Using this command, EEPROM bits can be set but not reset.
SCL010/01X REFERENCE MANUAL 48 Example For an NFC forum tag type 1 which has the following memory dump The following sequence does A READ of the byte # 0x03 in block 0x07 A WRITE NO ERASE of the byte # 0x03 in the block =0x07 with value 0x09 A READ of the byte # 0x03 in block 0x07 One can notice that the value of the byte after the WRITE NO ERASE is not 0x09 but 0x0B because the memory value before the operation was 0x02.
SCL010/01X REFERENCE MANUAL 6.4.3.6. 49 Read Segment (RSEG) Description This command reads out a complete segment (or block) of the memory a Topaz tag with dynamic memory model. Please note that this command only function on those specific Topaz tags. Format CLA INS P1 P2 P3 Data 0xFF 0x5A 0x00 Segment Address 0x00 - P2 – Segment Address - b8 - b5 - Segment (0x0 – 0xF) b4 - b1 - 0 Response Data SW1 SW2 128 bytes of data 0x90 0x00 6.4.3.7.
SCL010/01X REFERENCE MANUAL 6.4.3.8. 50 Write-Erase 8 bytes (WRITE-E8) Description This command writes erases a memory block and then writes a value to it. Format CLA INS P1 P2 P3 Data 0xFF 0x5E 0x00 Block Address 0x08 8 bytes of data to be written P2 – Block Address - b8 - b1 - General block (0x00 – 0xFF) Response Data SW1 SW2 8 bytes of data that have been written 0x90 0x00 6.4.3.9.
SCL010/01X REFERENCE MANUAL 51 6.4.4. Commands for communicating with NFC Forum Tags Type 2 To interact with an NFC Forum tag type 2, the commands defined for memory storage cards are to be used (STORAGE_CMDS_READ_BINARY and STORAGE_CMDS_WRITE_BINARY with block length of 0x04 or 0x10). Please refer to the contactless storage user token APDU’s described already for the command definitions. The user can also refer to NFC Forum tag type 2 specification for definition of the commands to be used. 6.4.5.
SCL010/01X REFERENCE MANUAL 6.4.5.2. 52 Request Service Description On receiving this command an NFC Forum tag 3 type will respond with the area key version of the specified area and the service key version of the specified service. Format CLA INS P1 P2 P3 Data 0xFF 0x42 Number of services/areas 0x00 2 * P1 Service Code List / Area Code List Response Data SW1 SW2 8 bytes IDm + No. of Service or areas(n) + Service version or area version list (2*n) 0x90 0x00 6.4.5.3.
SCL010/01X REFERENCE MANUAL 6.4.5.5. 53 Write Description When an NFC Forum tag type 3 receives this command, it writes the records of the specified service. Format CLA INS P1 P2 P3 Data 0xFF 0x48 Number of services Number of blocks 2*(P1 + P2) + (16 * P2) Service Code List, Block List, Block Data Response Data SW1 SW2 8 bytes IDm + Status Flag 1 + Status Flag 2 0x90 0x00 6.4.5.6.
SCL010/01X REFERENCE MANUAL 6.5. 54 Escape commands 6.5.1. Sending escape commands to SCL010/01X A developer can use 2 methods to send escape commands to SCL010/01X SCardControl method defined in PC/SC API SCardTransmit method defined in PC/SC API in conjunction with the escape command APDU defined earlier in this manual 6.5.2.
SCL010/01X REFERENCE MANUAL 55 6.5.3. READER_GETCARDINFO This escape command is used to get information about the card placed on the reader. The SCL010/01X returns an error if no card is placed on it. The input buffer shall contain the escape command code Input buffer 0x11 The output buffer contents are described below.
SCL010/01X REFERENCE MANUAL 56 6.5.5. READER_LEDCONTROL This escape command is used to turn ON/OFF the LED. This escape command shall work only if LED control by firmware is disabled. The input buffer shall contain 3 bytes Byte # Value Description B0 0x19 Escape command code B1 0x00 LED number B2 0x00 LED ON 0x01 LED OFF The output buffer is Output buffer NULL 6.5.6.
SCL010/01X REFERENCE MANUAL 57 6.5.8. READER_CNTLESS_SET_TYPE This escape command configures the type of cards SCL010/01X will poll for. Using this command can improve the polling efficiency of SCL010/01X for applications where only type A or only type B cards are expected. The default is Type A + Type B + FeliCa (0x1B).
SCL010/01X REFERENCE MANUAL 58 6.5.9. READER_CNTLESS_RF_SWITCH This escape command can be used to retrieve/set the RF state of SCL010/01X. The default RF field state is ON. The input buffer shall contain 2 bytes Byte # Value Description B0 0x96 Escape command code B1 0x00 Switch RF Field OFF 0x01 Switch RF Field ON 0xFF Get current field state After the RF is turned off, to turn the RF ON again, card connect shall be done in direct mode.
SCL010/01X REFERENCE MANUAL 6.5.11. 59 READER_CNTLESS_RAW_XMIT This escape command can only be executed by the firmware once SCL010/01X is put in raw mode using the READER_CNTLESS_RAW_CFG escape command.
SCL010/01X REFERENCE MANUAL 6.5.12. 60 READER_ CNTLESS_DISABLE_PPS By default SCL010/01X does automatic PPS – i.e. it switches the RF communication speed to the highest possible supported by the card. This escape command can be used to switch ON/OFF automatic PPS. When automatic PPS is OFF, then 106Kbps only is available The input buffer is Byte # Value Description B0 0x99 Escape command code B1 0x01 Disable Auto-PPS 0x00 Enable Auto-PPS The output buffer is Output buffer NULL 6.5.13.
SCL010/01X REFERENCE MANUAL 6.5.14. 61 READER_CNTLESS_BAUDRATE This escape command can be used to get the actual operating baud rate of card-reader communication. This escape command is applicable only for Type A and B cards. The input buffer shall contain the escape message value.
SCL010/01X REFERENCE MANUAL 6.5.15. 62 READER_CNTLESS_FORCE_BAUDRATE_PCSC_REV2 This escape command can be used to force baud rate for Contactless cards, it is applicable only for Type A and B cards.
SCL010/01X REFERENCE MANUAL 6.5.16. 63 READER_GETPNPPARAMS This escape command is used to retrieve the VID, PID, serial number and PNP string. The input buffer contains the escape command code Input buffer 0xD3 The output buffer contents are described below. Byte # Description B0-B1 VID(2 Bytes) B2-B3 PID(2 Bytes) B4-B17 Serial Number(14 Bytes) B18 PNP String length (up to 127 bytes) B19 - Bx PNP String (up to 127 bytes) 6.5.17.
SCL010/01X REFERENCE MANUAL 6.5.18. 64 READER_GET_CARD_DETAILS This escape command is used to get details about the PICC placed on the reader.
SCL010/01X REFERENCE MANUAL 65 B14 Read command response time parameter B15 Write command response time parameter Examples MIFARE Ultralight MIFARE 1K MIFARE DESFire Topaz ISO14443-4A ISO14443-4B ISO14443-4A + MIFARE FeliCa 6.5.19. READER_IS_SCL010/01X This escape message may be used to check if the connected device is an SCL010/01X device.
SCL010/01X REFERENCE MANUAL 6.5.20. 66 READER_SEND_ATTRIB_WITH_INF This Escape command may be used to send application layer bytes to a type B card along with the ATTRIB command in the higher layer INF field. The output buffer will contain the higher layer reply from the card, if card provides a reply. Otherwise the reply buffer will be NULL. The input buffer is: Byte # Value Description B0 0xE2 Escape command code B1 onwards INF Bytes 6.5.21.
SCL010/01X REFERENCE MANUAL 67 The input buffer is: Byte # Value Description B0 0xF3 Escape command code B1 onwards Data send to Felica Card The output buffer is: Output buffer Description B0 onwards Data sent from Felica card
SCL010/01X REFERENCE MANUAL 7. Annexes 7.1.
SCL010/01X REFERENCE MANUAL 69 7.2. Annex B – Sample code using escape commands through Escape IOCTL File Name : T_pupi.H #ifdef __cplusplus extern "C" { #endif #define IOCTL_CCID_ESCAPE SCARD_CTL_CODE (0xDAC) #define CCID_GET_PUPI_STATUS 0xFF9B #define CCID_SET_PUPI_ON 0x019B #define CCID_SET_PUPI_OFF 0x009B #define MINTIMEOUT 300 #ifdef __cplusplus } #endif File Name : T_pupi.CPP #include #include #include #include #include "winscard.
SCL010/01X REFERENCE MANUAL SCARD_READERSTATE 70 Reader[1]; // please add the name of the used reader here or use SCardListReaders // to find the right reader name char *ReaderName[] = {"SCM Microsystems Inc.
SCL010/01X REFERENCE MANUAL 71 printf ("\nATR: "); for (i=0; icbAtr; i++) { printf ("%.2x ",Reader->rgbAtr[i]); } printf ("\n----------------------------------------------\n"); /* set actual PUPI status: ON */ printf ("\nenable PUPI "); InBufLen = 2; InWord = CCID_SET_PUPI_ON; ret = SCardControl (CardHandle, IOCTL_CCID_ESCAPE, &InWord, InBufLen, &OutByte, 1, &ResLen); ret = SCardDisconnect(CardHandle, SCARD_RESET_CARD); ret = SCardConnect (ContextHandle, ReaderName[0], SCARD_SHARE_SHARED, SCA
SCL010/01X REFERENCE MANUAL 72 Reader[0].dwCurrentState = SCARD_STATE_UNAWARE; Reader[0].dwEventState = SCARD_STATE_UNAWARE; Reader[0].szReader = ReaderName[0]; ret = SCardGetStatusChange (ContextHandle, MINTIMEOUT, Reader, 1); printf ("\nATR: "); for (i=0; icbAtr; i++) { printf ("%.2x ",Reader->rgbAtr[i]); } printf ("\n----------------------------------------------\n"); /* set actual PUPI status: OFF */ printf ("\ndisable PUPI "); InBufLen = 2; InWord = CCID_SET_PUPI_OFF; ret = SCardControl(Ca
SCL010/01X REFERENCE MANUAL 73 ret = SCardGetStatusChange( ContextHandle, MINTIMEOUT, Reader, 1); printf ("\nATR: "); for (i=0; icbAtr; i++) { printf ("%.2x ",Reader->rgbAtr[i]); } printf ("\n----------------------------------------------\n"); ret = SCardDisconnect(CardHandle, SCARD_RESET_CARD); } else { printf("\n SCardConnect failed with 0x%.8lX",ret); } ret = SCardReleaseContext(ContextHandle); } else { printf("\n SCardEstablishContext failed with %.8lX",ret); } printf("\npress any key to cl
SCL010/01X REFERENCE MANUAL 7.3. Annex C – Mechanical drawings 7.3.1.
SCL010/01X REFERENCE MANUAL 7.3.2.
SCL010/01X REFERENCE MANUAL 7.3.3.
SCL010/01X REFERENCE MANUAL 7.3.4.
