ID TECH Kiosk V USB-C User Manual
Document Revision: Rev. J, 28 July 2025
Manufacturer: ID TECH
Address: 10721 Walker Street, Cypress, CA 90630-4720
Contact: Tel: (714) 761-6368 | Fax: (714) 761-8880 | www.idtechproducts.com | support@idtechproducts.com
1. Overview
The ID TECH Kiosk V is a compact, one-piece EMV contactless reader, designed to support contactless EMV transactions based on ISO 18092, ISO 14443 Type A/Type B/MiFare compatible cards, fobs, and tags, as well as NFC phones.
The Kiosk V supports USB-C host communication using the protocol defined in the NEO Interface Developers Guide. This comprehensive guide describes all the firmware commands and other features available in NEO-series devices; it is the authoritative source for technical information of interest to systems integrators. Contact your ID TECH representative to obtain a copy of this guide, which is available only on request.
1.1. Universal SDK
A feature-rich Windows-based Universal SDK is available to aid rapid development of applications that communicate with the Kiosk V. The SDK is available for the C# language on Windows and includes sample code for demo applications. To obtain the SDK and other useful utilities, demos, and downloads, visit the Downloads link on the ID TECH Knowledge Base (no registration required).
1.2. Encryption
Kiosk V supports industry-standard Triple DES or AES encryption, with DUKPT-based key management (per ANSI X.9-24). Encryption can be configured to occur with a data variant as desired. ID TECH operates a certified Key Injection Facility, capable of injecting your unit(s) with any required keys. Consult your ID TECH representative to learn about all available options involving key injection.
2. Features
Kiosk V USB-C Non-SRED readers support the following transaction types:
- ISO/IEC 14443 Type A and B
- ISO 18092
- Backwards-compatible to NEO 1 commands used in Kiosk III readers.
- Suitable for transit, kiosks, parking, and various other unattended and attended verticals.
- Consumer Intuitive: Equipped with LEDs and sound to provide visual and audible cues for smooth and seamless transactions.
- Secure: Provides highly secure transactions for financial, pre-paid, loyalty, or gift cards. Data is encrypted at the time of the transaction and never travels in clear-text form.
- Self-contained NFC antenna
- Contactless EMV L1 and L2 Certified
- Ruggedized product made for outdoor use
- USB and Bluetooth interfaces
- Supports TDES & AES
- Supports DUKPT key management
- Supports Remote Key Injection
- Supports remote FW updates
- Supports the latest Visa, Mastercard, American Express, and Discover L2 Kernels
- Supports international certifications like: Interact
- Supports major transit kernels like Visa Ready for transit, Interact Transit
- Supports Apple VAS & Google Smart Tap
2.1. Certifications and Approvals
- EMV CO Contactless L1 3.1a
- Visa 2.2C
- Visa Transit 2.2 C
- Master 3.1.4
- Amex 4.1
- Discover 2.0
- Interac 1.8
- Interac ABM 1.8
- Interact Transit 1.8
- Google SmartTap 2.1
- JCB 1.6
- Felica
- CE
- CE RED
- FCC
- IC
- REACH
- RoHS
- UL
This document assumes that users are familiar with their host systems and all related functions.
3. Kiosk V Specifications
Hardware
Attribute | Details |
---|---|
MTBF | 500,000 hours based on Telcordia Technologies SR-332 modeled at 40° C. |
Transmitter Frequency | 13.56 MHz +/- 0.01% |
Transmitter Modulation | ISO 14443-2 Type A: Rise/Fall Time: 2-3 µsec. Rise, < 1 µsec fall ISO 14443-2 Type B: Rise/Fall Time: < 2 µsec. each; 8% – 14% ASK ISO 18092 |
Receiver Subcarrier Frequency | ISO 21481 (PCD & NFC) 847.5 KHz |
Receiver Subcarrier Data | ISO 14443-2 Type A: Modified Manchester ISO 14443-2 Type B: NRZ-L, BPSK ISO 18092 ISO 21481 (PCD & NFC) |
Typical Read Range | 0-4 cm (0 to 1.5 inches) |
Physical
Attribute | Details |
---|---|
Length | 75 mm (2.95 inches) |
Width | 60 mm (2.36 inches) |
Depth | 11.2 mm (0.44 inches) |
Environmental
Attribute | Details |
---|---|
Operating Temperature | -30°C to 70°C (-22°F to 158° F), max change of 10° C per hour |
Storage Temperature | -30°C to 85°C (-22 °F to 185° F) [non-condensing] |
Operating Humidity | Maximum 95% (non-condensing) |
Storage Humidity | Up to 90% non-condensing, duration 3 months |
Transit Humidity | Maximum 95% (non-condensing) |
Operating Environment | Water resistant for indoor and outdoor use |
IK Rating | IK 07 |
IP Rating | IP 65 |
3.1. USB Specifications
Interface | Attribute | Value |
---|---|---|
USB C Female | Voltage (V) | 4.75 to 5.25 |
Power Supply Requirement Current (A) | 3 | |
Power (W) | 15 | |
Version | 2.0 | |
Protocol | USB Standard | |
USB Speed (Full speed or High Speed) | Full speed | |
PD Support | Not supported | |
USB | USB Role(Host or Device) | Device |
OTG | Not supported | |
Pin Out | No |
USB Power Delivery
Mode of Operation | Voltage | Max Current | Max Power |
---|---|---|---|
USB 1.x / USB 2.0 | 5 V | 0.5 A | 2.5 W |
USB 3.X | 5 V | 0.9 A | 4.5 W |
USB-C (Standard) | 5 V | 3 A | 15 W |
USB-C (PD) | 5 - 20 V | 5 A | 25W - 100W |
3.2. Power Consumption
Information about Kiosk V power consumption:
Operation Mode | Power Consumption Current (mA)* | Wakeup Time (ms)* |
---|---|---|
Transaction Mode | 88.2 mA | N/A |
Idle Mode | 66.8 mA | N/A |
Suspend Mode (USB) | 10.2 mA | < 50 ms |
*Data points are based on ID TECH's test results; minor variations are possible due to test environments.
3.3. 24-Hour Device Reboot
Per PCI Requirements, this device reboots every 24 hours. Contact your device integrator if you need to check the reboot time for your unit.
4. KIOSK V Connectors and Interfaces
The KIOSK V is designed to work with Windows, Android, and iOS via a physical USB C connection and Bluetooth communication.
- USB C communicates with popular Android mobile phones and tablets.
- Bluetooth connection supports both Android and iOS.
When communicating over USB, the KIOSK V's default emulation mode is USB HID.
5. Bluetooth Pairing Instructions
For more information on using an iPad or iPhone with the KIOSK V, refer to the iOS Connectivity section.
- Enable the Bluetooth device search function on the host smart phone or tablet.
- Ensure the host smart phone or tablet supports BLE 5.0 or above. The BLE will operate in secure mode (BLE model 1 and Level 4).
- Ensure the KIOSK V reader is charged or connected to a power source via USB.
- When connected to a power source, KIOSK V readers automatically activate Bluetooth.
- If not connected to a power source, press the KIOSK V's power button to activate Bluetooth.
- On the host smart phone or tablet, find the Bluetooth device named IDTECH-KioskV-XXXXX and select Pair.
- Enter the password for pairing. The default password is 123456. ID TECH strongly recommends changing the password before pairing.
- Follow the payment transaction instructions provided by a compatible payment application maker to complete a transaction.
The KIOSK V will remain connected via Bluetooth to the host device indefinitely when powered via the USB cable.
When connecting to an iOS device, install a compatible payment application and follow its maker's instructions. See the "iOS Connectivity: BLE and KIOSK V" section for more information.
5.1. iOS Connectivity: BLE and KIOSK V
The KIOSK V uses Bluetooth 5.0, also known as Bluetooth BLE (Bluetooth Low Energy). Unlike previous Bluetooth versions, BLE does not require users to first pair devices through the Bluetooth Settings in Apple iOS. If a payment application provider has enabled BLE scanning, Apple iOS scans and locates all BLE devices in range to automatically connect with the KIOSK V.
It is critical to note that if the KIOSK V is paired via the iOS Settings page, it will display as a connected device but will not function with a payment app.
Unlike other operating systems that can detect or specify a BLE device by its MAC address, Apple does NOT allow users to specify a BLE device by MAC address for security reasons. Instead, after a device is selected by its "friendly" name (e.g., IDTECH-BLE-XXXX), Apple iOS calculates a unique identifier to allow that device to make further connections directly. The KIOSK V has a default friendly name of IDTECH-BLE-XXXX, which is used by the ID TECH Universal SDK to connect to the first KIOSK V it encounters if no other friendly name is set or if the iOS-generated device identifier is not provided. See links near the end of this document for information about the Universal SDK.
The Universal SDK is primarily of interest to developers. If an application provider or POS software partner has already provided software to use with the KIOSK V, you do not need to obtain the SDK.
6. KIOSK V LED and Sound State Indicators
The KIOSK V uses the following LEDs and sounds to indicate various statuses, including power management, Bluetooth, transactions, and security.
Device State | LED1 | LED2 | LED3 | LED4 | Beeper¹ |
---|---|---|---|---|---|
Device FW, certificates, or keys self-test failed. | ● | ● | ● | blink | Beeps |
Device Deactivated | off | off | off | blink | Beeps |
Device Activated² | off | off | off | on | Off |
Device Key Missing³ | blink | blink | blink | blink | Off |
Ready for Transaction | on | on | on | off | Off |
Bluetooth Connected | off | off | off | on | Beeps Once |
Bluetooth Connection Failed / Bluetooth Disconnected | off | off | off | on | Beeps Twice |
Transaction Started⁴ | on | off | off | off | Off |
Transaction Successful⁵ | on | on | on | on | Beeps Once |
Transaction Failed | off | off | off | off | Beeps Twice |
Bootloader Mode | off | off | off | on | Off |
¹ Note that “beeps” indicates constant beeping unless the description includes a specific number of beeps (such as "twice").
² The device has loaded certificates successfully and is activated.
³ The device only has LCL-KEK; the required key is not injected.
⁴ The transaction has started and the device is waiting to read a card.
⁵ LEDs remain on for 1000ms.
7. ID TECH Universal SDK
By virtue of its EMV L2 kernel, KIOSK V is designed to be compatible with a wide range of third-party payment applications. ID TECH offers a Universal SDK (available for iOS, Android, or Windows) to enable rapid application development using KIOSK V as the target device. The languages supported include Objective C (on iOS), Java (on Android), and C# (on Windows). The Universal SDK includes rich, powerful libraries that make sending commands to the KIOSK V comparatively easy while greatly facilitating debugging and event handling.
To obtain the Universal SDK free of charge, visit ID TECH's KIOSK V product page and select the version of the SDK that applies to your desired host platform (Android, iOS, Linux, MacOS, or Windows).
Normally, development of applications that take advantage of KIOSK V's capabilities can be done in a high-level language like C# or Java (using convenience objects and data structures defined in the Universal SDK), obviating the need to send byte commands directly. Nevertheless, it is possible to communicate with the device at a low level if necessary. For a command reference for KIOSK V, request the NEO Interface Developers Guide (IDG), P/N 80139403-001. This document includes not only low-level (firmware) commands but error codes, response codes, and information on various default settings.
8. Kiosk V Installation
This section provides information on how to install the Kiosk V on a kiosk.
8.1. Parts List
Verify that you have the following hardware for the installation of the Kiosk V:
- Kiosk V
ID TECH also supplies these USB-C cables:
- 80185215-001 (Standard Straight, lock-in Connector Cable - USB-A to USB-C)
- 80185213-001 (Right-Angled, lock-in Connector Cable - USB-A to USB-C)
8.2. Mounting the Kiosk V
To optimize performance, install Kiosk V readers away from or in front of any metal surfaces or materials that have metallic content, which can interfere with the RF field.
- Kiosk V readers perform optimally when mounted away from metal surfaces.
- ID TECH offers solutions to enhance Kiosk V performance, such as spacers, available for versatile installations.
The default suggested installation uses the drilling template provided on a non-metallic surface.
For installation on metallic surfaces, ID TECH suggests two options:
- Install the Kiosk V with a plastic spacer between the metallic surface and Kiosk V to enhance RF performance.
- Install the Kiosk V using a flush installation embedded into the metallic surface for an integrated flush design and enhance RF performance.
Please contact your ID TECH sales rep for additional help with mounting options and customizations.
Device installers should not mount Kiosk V units directly onto a metallic surface. Be sure to use the plastic spacer mentioned above when mounting devices onto a metallic surface.
Kiosk V Dimensions and Mounting
Kiosk V Part#: IDVK-5XXX
Diagram Description: A side view of the Kiosk V shows dimensions 9.60mm and 11.20mm. The rear view shows mounting holes and dimensions. It indicates four M3 insert nuts (depth 3mm) and two M2 insert nuts (depth 4mm). Certifications like CE, FC, FCC ID, and IC are visible on the rear.
Note: The Kiosk V is post-compatible with Kiosk III and Kiosk IV dimensions. Posts are 36mm apart in the lengthwise direction and 32mm apart widthwise.
Mounting Instructions
Use the following instructions to mount the Kiosk V on the exterior of a kiosk structure:
- Using the Drill Template, locate and mark the four 3.25mm (0.138 inch) mounting holes.
- Verify the orientation of the Kiosk V before marking and drilling the holes. The rectangle hole should be located towards the bottom of the mounting location to ensure that the Kiosk V is oriented correctly with the LEDs at the top.
- Using the Drill Template, locate and mark the 9.95mm*15.77mm (0.392inch*0.621inch) rectangle hole (used for connecting the USB-type C cable to the Kiosk V).
- Align the four M3 screws with the mounting holes and attach the Kiosk V to the outside surface.
- Use the four screws to secure the Kiosk V to the outside surface of the kiosk. Ensure screws are tightened securely so the Kiosk V does not move.
- Route the end of the USB-Type C cable through the rectangle hole into the kiosk and tighten the two M2 screws in the over mode of the USB-Type C cable to ensure the cable is locked reliably.
Diagram Description: A drill template diagram for mounting the Kiosk V. It shows four circular holes marked for mounting screws (4-Ø3.50) and a rectangular hole (4-R2) for the USB-C cable. Dimensions are provided in mm with a tolerance of ±0.5mm. The diagram indicates the orientation of the device, with the rectangle hole towards the bottom.
8.3. Connecting to Power
The Kiosk V can be powered via the USB port.
8.4. Communication via USB
The PID is 4690 (hex).
8.5. Connecting to the Data Port
The Kiosk V connects via USB-C.
8.6. Using the Kiosk V to Make a Purchase
The following describes how to use the Kiosk V to make purchases.
8.6.1. Presenting Cards or NFC Phones
The Kiosk V supports Open Loop and Close Loop payments using Contactless/NFC technology. Present the card/phone in close proximity to the front portion of the Kiosk V, ensuring maximum surface area is parallel to the Kiosk V.
Diagram Description: A hand is shown holding a "vivo pay" contactless test card, presenting it to the front of the ID TECH Kiosk V reader.
Upon successful reading, the Kiosk V should beep, and the four green LEDs should illuminate in sequence, then all will illuminate together briefly (750 msec). This indicates a successful test, verifying the Kiosk V's ability to read the Contactless test card. The reader produces no reaction in case of an unsuccessful test. Using a test card with the Kiosk V allows for a dummy transaction test, which will not be authorized but will confirm end-to-end connectivity. ID TECH's Universal SDK Demo App (uDemo) is available free of charge for this test.
8.7. Installation Suggestions
- The Kiosk V is susceptible to RF and electromagnetic interference. Do not mount the unit within 3 or 4 feet of large electric motors, computer UPS systems, microwave transmitters (Wi-Fi routers), anti-theft devices, radio transmitters, communications equipment, and similar sources.
- Close proximity of metal to the RF-emitting end of the NFC antenna can greatly reduce the NFC antenna's range.
- Tie all cables neatly with nylon cable-ties and route them so they are inaccessible and invisible to customers. Label the cable ends, host, ID TECH, and power to simplify connection testing or component replacement.
- Test the Kiosk V installation using a test card to perform an end-to-end transaction (similar to an actual purchase). The kiosk display panel should show "Requesting Authorization." Even if the transaction is declined (as expected with a test card), it confirms connectivity through the system. If possible, test each Kiosk V regularly (daily or weekly) with a test card to ensure continued operation and functionality. If the kiosk is rebooted regularly, test the contactless reader as soon as possible afterward to ensure continued communication to the kiosk host.
9. RF Interference
Q. Why do I need to know about RF interference?
A. Contactless payment uses radio frequency technology to send card data to a contactless terminal reader.
Q. How can RF interference affect contactless payment?
A. RF interference can cause data errors. If RF interference is present, contactless payment devices may operate intermittently or inconsistently.
Q. Where does RF interference come from?
A. Radio frequency interference (RFI) can originate from a wide number of sources at the point-of-sale (POS). Some examples of sources of RF energy and RF interference include: AM/FM radio, TV transmitters, 2-way radios, pagers, mobile telephones, power lines, transformers, medical equipment, microwaves, and electromechanical switches.
Q. What should I do if I suspect RF interference exists in my environment?
A. Begin by inspecting your environment for possible sources of RF interference.
Q. Do equipment manufacturers test their devices for RF interference?
A. Electronic equipment is tested for RFI sensitivity by the manufacturers. These tests are performed in a controlled laboratory environment and will often not replicate the types of devices that would be encountered in your point-of-sale (POS) environment.
Q. What RF levels will impact RF operations?
A. Factors that can cause RF interference vary case-by-case. There are no set rules defining a single RF level that will cause RFI. RFI depends on the sensitivity of the equipment under consideration, or how low an interpreting signal can be in the presence of the equipment and cause problems. Equipment can be particularly sensitive to very low signal levels of one frequency and yet be quite immune to high signal levels of another frequency - so frequency is an important factor. Some electronic system components are internally shielded and have a very high immunity to interference; but generally, most equipment has not been so engineered.
9.1. Updating Kiosk V Firmware
ID TECH strongly recommends updating firmware via the Universal SDK. Consult the Universal SDK Guide for your desired platform (included in the ZIP file downloaded from the Kiosk V product page) for integration details.
Firmware downloads must be done via a USB-C to USB-A cable or a USB OTG cable for mobile Android devices; Kiosk V readers do not support firmware over Bluetooth.
9.1.1. Universal SDK Demo App
The Universal SDK comes with a rich, fully featured demo app that allows users to run the Kiosk V in USB mode. Visit the Knowledge Base and go to the Kiosk V product page to download the Universal SDK Demo app as a standalone executable, separate from the SDK; the full SDK is not required to use the demo. Check out the Universal Demo QuickStart Guide for more detailed instructions about using the Universal SDK Demo app.
9.2. Using the Demo Application
Follow the steps below to run the Universal SDK Demo app on Windows:
- Plug the Kiosk V into the host device with a USB-to-micro-USB cable (not included).
- Double-click the UniversalSDKDemo.exe file and allow a few seconds for the main window to appear.
Screenshot Description: The ID TECH Universal SDK Demo Application for Windows is shown. The interface features a command tree on the left, displaying available commands. The center and right panels show results, data traces, and status information. Control buttons for executing commands, clearing logs, and managing connections are also visible.
The Universal SDK Demo app displays KIOSK V's available commands in a command tree. Single-click on a command to populate the center panel with optional settings relevant to the command (e.g., Amount and Start EMV Additional Tags). In some cases, text fields appear, allowing users to enter custom values.
To execute a command, double-click it in the command tree or use the "Execute Command" button at the bottom of the window. The command executes in real time, and a data trace appears automatically in the center and/or right-hand panels. Use the "Clear Logs" button to clear both panels.
10. Kiosk V Low-Level Commands
The following are commonly used commands for the Kiosk V. For a full list of available commands, contact your ID TECH representative for the NEO 2 Interface Developer's Guide.
10.1. Activate Transaction Command (02-40)
The Activate Transaction command begins a contactless EMV or contactless MagStripe Card transaction.
While an Activate command is in progress, readers only accept a Cancel or Stop command. Do not send other commands until Activate Transaction has completed, as the reader will interpret them as a Cancel Transaction command.
Command Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 ... Byte 14+n-1 | Byte 14+n | Byte 15+n |
---|---|---|---|---|---|---|---|
Header Tag & Protocol Version | Command | Sub-Command | Data Length (MSB) | Data Length (LSB) | Data | CRC (LSB) | CRC (MSB) |
ViVOtech2\0 | 02h | 40h | See Data Format below | See Data Format below |
Activate Transaction Command Frame Data Format
Data Item | Length (bytes) | Description |
---|---|---|
Timeout | 1 | Time in seconds that the reader waits for a card to be presented before timing out and returning an Error response. The reader will continue to poll for this amount of time if no card is found. Note that if a card is found, the transaction may not complete within the timeout period. This field must be present in the Activate command. |
TLV Data | varies | Format: Binary. See Activate Command TLVs in the NEO IDG. |
Response Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 ... Byte 14+n-1 | Byte 14+n | Byte 15+n |
---|---|---|---|---|---|---|---|
Header Tag & Protocol Version | Command | Status Code | Data Length (MSB) | Data Length (LSB) | Data | CRC (LSB) | CRC (MSB) |
ViVOtech2\0 | 02h | See Status Code Table | See Response Frame Data Format | See Response Frame Data Format |
Note: The information above omits many command details, particularly TLV information. See the NEO Interface Developer's Guide (available from your ID TECH representative) for the full Activate Transaction (02-40) description.
10.2. Set CA Public Key (D0-03)
The Set CA Public Key command adds a new key to the reader.
Command Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 – 18 | Byte 19 | Bytes 19-n | Byte n+1 | Byte n+2 |
---|---|---|---|---|---|---|---|---|---|
Header Tag & Protocol Version | Cmd | Sub Cmd | Length (MSB) | Length (LSB) | RID (5 bytes) | Key Index (1 byte) | Key Data | CRC (LSB) | CRC (MSB) |
ViVOtech2\0 | D0h | 03h | varies | varies | varies | varies | See below | Varies | Varies |
Key Data (all binary)
Byte | Name | Length (bytes) | Description |
---|---|---|---|
0 | Hash Algorithm | 1 | The only algorithm supported is SHA-1. The value is set to 01h. |
1 | Public Key Algorithm | 1 | The encryption algorithm in which this key is used. Currently supports only one type: RSA. The value is set to 01h. |
3-22 | Checksum/Hash | 20 | Checksum calculated using SHA-1 over: RID & KeyIndex & Modulus & Exponent (exponent is 1 or 3 bytes, stored in a 4-byte field). |
23-26 | Public Key Exponent | 4 | Actual exponent length is 1 or 3 bytes. Possible values: 3, or 65537. |
27-28 | Modulus Length | 2 | Length of the next field, MSB followed by LSB. |
29-n | Modulus | Variable | The modulus field of the public key, length specified above. |
Response Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 | Byte 15 |
---|---|---|---|---|---|---|
Header Tag & Protocol Version | Cmd | status | Length (MSB) | Length (LSB) | CRC (LSB) | CRC (MSB) |
ViVOtech2\0 | D0h | See Key Manager status codes | 00h | 00h | Calculated | Calculated |
10.3. Get Module Version Information (09-20)
The Get Module Version Information command retrieves the reader's module information.
Command Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 | Byte 15 |
---|---|---|---|---|---|---|
Header Tag & Protocol Version | Command | Sub-Command | Data Length (MSB) | Data Length (LSB) | CRC (LSB) | CRC (MSB) |
ViVOtech2\0 | 09h | 20h | 00h | 00h |
Response Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte12 | Byte 13 | Byte 14 ... Byte 13+n | Byte 14+n | Byte 15+n |
---|---|---|---|---|---|---|---|
Header Tag & Protocol Version | Command | Status Code | Data Length (MSB) | Data Length (LSB) | Data | CRC (MSB) | CRC (LSB) |
ViVOtech2\0 | 09h | See Status Code Table | See below | See below |
If there is an error, the reader returns the appropriate status code with an empty data field (Data Length = 0000h).
The format for module version information returned is "human readable," consisting of fields separated by commas and lines separated by carriage return and line feed characters:
<module type>,<module name and spec. version>,<implementation version>,<CRLF>
The following example shows the module version information subcommand and the information being returned (in ASCII format):
Command: Get Module Version Information: 56 69 56 4F 74 65 63 68 32 00 09 20 00 00 56 11
Response: 56 69 56 4F 74 65 63 68 32 00 09 00 00 A6 4E 75 74 74 58 2D 31 30 2E 32 2E 30 0D 0A 77 6F 6C 66 53 53 4C 2D 34 2E 37 2E 30 0D 0A 43 4C 20 41 49 44 2C 20 45 4D 56 20 45 50 20 76 32 2E 31 30 2C 20 76 31 2E 30 30 0D 0A 43 4C 20 41 49 44 2C 20 4D 61 73 74 65 72 20 43 32 20 76 32 2E 31 30 0D 0A 43 4C 20 41 49 44 2C 20 56 43 50 53 20 76 32 2E 32 2C 20 76 31 2E 30 30 0D 0A 43 4C 20 41 49 44 2C 20 44 69 73 63 6F 76 65 72 20 44 50 41 53 20 32 2E 30 2C 20 76 31 2E 30 30 0D 0A 43 4C 20 4C 31 2C 20 45 4D 56 33 2E 31 61 2C 20 76 35 2E 32 33 0D 0A 65 29
ASCII translation of the data field: NuttX-10.2.0<CR><LF> wolfSSL-4.7.0<CR><LF> CL AID, EMV EP v2.10, v1.00<CR><LF> CL AID, Master C2 v2.10<CR><LF> CL AID, VCPS v2.2, v1.00<CR><LF> CL AID, Discover DPAS 2.0, v1.00<CR><LF> CL L1, EMV3.1a, v5.23<CR><LF>
10.4. Get Serial Number (12-01)
The Get Serial Number command instructs the Kiosk V to return the 15-digit serial number stored in its non-volatile memory. If a serial number has not been previously set in the reader, this command fails with a "Command Not Allowed" error status. If the command frame is not valid, the reader returns an error response frame.
Command Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 | Byte 15 |
---|---|---|---|---|---|---|
Header Tag & Protocol Version | Command | Sub-Command | Data Length (MSB) | Data Length (LSB) | CRC (LSB) | CRC (MSB) |
ViVOtech2\0 | 12h | 01h | 00h | 0Fh |
The serial number for KV USB-C will be returned tail-padded with 0x30 to a length of 15.
Response Frame
Byte 0-9 | Byte 10 | Byte 11 | Byte 12 | Byte 13 | Byte 14 ... Byte 14+n-1 | Byte 14+n | Byte 15+n |
---|---|---|---|---|---|---|---|
Header Tag & Protocol Version | Command | Status Code | Data Length (MSB) | Data Length (LSB) | Data | CRC (MSB) | CRC (LSB) |
ViVOtech2\0 | 12h | See Status Code Table | 00h | 0Fh | 15-digit Serial Number |
11. Periodic Inspection Instructions
The KIOSK V is an unattended device; contact an ID TECH representative with any questions for the device's daily use.
Users are also required to complete the following checks daily:
- Check the device overlay to make sure it is intact.
- Power on the device to check the beeper and the display message:
- Make sure there is no beeping that indicates the tamper was triggered.
- Read the firmware version to make sure the version number is correct.
12. Troubleshooting
Kiosk V readers are reliable and easy to troubleshoot. The components that may require troubleshooting include the power supply, the reader itself, and the serial cable. If you are unable to resolve the problem, contact support@idtechproducts.com (sending an e-mail to this address will automatically open a support ticket).
Symptom | Possible Cause | Remedy |
---|---|---|
General Issues Reader does not appear to be powered on (no LEDs are lit). Note that when the unit is expecting a transaction, the first LED (on the left) will illuminate continuously. Otherwise, in the idle state, it will blink. | Reader not powered on or incorrect voltage. | Check cable connections. Verify that power is on and correct voltage and current are present. Make sure that the correct pins are utilized. Make sure that the power provided is within the specified range of the Kiosk V reader. Make sure that the correct polarity is observed. For more information, refer to the Input Voltage under the Electrical specification section. |
Improper use of internal power supply provided by the kiosk. | Replace the Kiosk V. | |
Reading Cards/Phones First LED is lit, but beeper is not audible when card/fob presented. | Card/fob/phone not properly presented. | Present card/fob/phone closer to the NFC antenna, and ensure it is parallel to the face of the reader. |
RF interference. | Verify that the card/fob/phone is valid/current. | |
Unsupported card used. | Verify that metal is not interfering with the NFC antenna. | |
Wrong firmware (contact your local support representative). | Test with "ViVOcard Contactless Test Card" part number 241-0015-03 Rev A. Try a different card/fob. Check to see if card/fob is damaged. Verify that correct firmware is loaded on reader (local support representative only). | |
Some cards/fobs read, but not all. | Possible bad card/fob. | Power cable plug is fully inserted. Replace the Kiosk V. |
Unsupported card used. | Check to see if card/fob is damaged. Verify that correct firmware is loaded on reader (local support representative only). | |
Wrong firmware (contact your local support representative). | Present the card in a different orientation. | |
Communication to Kiosk No data is received, or data is garbled. | Faulty or incorrect cable connections. | Check that the cable connection is secure and in the correct port on the Kiosk V. |
Load Firmware Firmware loading software indicate "Load firmware failed" | Device is not well connected to PC | Check the cable connection |
Bootloader firmware in device is destroyed | Contact your local support representative to reload manufacture firmware. | |
Firmware loading software indicates "Send Command failed" |