Internal only: This is only visible if you are logged in to confluence 1. The hardware reset pin on the bottom of the reader only reboots the reader and will not change the reader's configuration. Use it to reboot the reader when it freezes
2. If the reader is still able to receive the command, the reboot command 77-05 does the same as the reset pin to power cycle the reader. (TS-19771)
3. Use poll mode (01-01 with appropriate data 02, 03, or 04) for QC mode and 5C with output tags defined in the DFEF5A tag
4. Per Jason Hall on 2/17/2020, VP3300USB with FW range V1.01.135 to V1.01.183 may experience the issue of locking up and becoming un-recoverable. Also, the issue of the reader failing to be recognized on USB if the flash on the device was written too many times immediately after start-up was resolved in the FW V1.01.221. Our recommendation is to update the firmware in all units to the latest released version (See TS-37138)
,
5. To adjust the USB polling speed, in Group 0 include DFEF6F 01 xx, range 0x30~0x35 (default 1200 ms, max: 50000 ms), 0x36 is the fastest(0ms). Include DFEF6E in group 0 for USBKB post-amble in CT/CLTS/MSR transactions
6. The USB model doesn't have an internal battery, only the Audio jack and Bluetooth series have batteries, and the maximum current consumption is 380mA/5V, which is the basic supply of USB, no additional handshake is required per Tony Huang in our engineering
7. For Discover contactless transaction, the CVM result is tag DF52(see NEO IDG and refer to TS-24966)
8. Before using the Android SDK Demo to upgrade FW, make sure to rename the firmware file to the default filename "IDT_Firmware_VP3300_USB.txt" that the SDK Demo uses, and save it in the root directory of the tablet. (TS-24886)
9. Refer to the Set MSR White List (91-10) command in NEO IDG Supplement V1.96 for details (TS-25294). Later, NEO IDG was updated to include this command which supports all 3 interfaces (MSR, CT, and CTLS) starting from V1.10.046
FW.
10. The 3-bytes tags are supported starting from: VP3300 Audio Jack NEO v1.01.193, VP3300 USB NEO v1.01.239, VP3300 Bluetooth NEO v1.01.213 for the old kernel, And the v1.10.037 of the new kernel VP3300 (See CS-3264)
11. For VP3300, the prod RKI-KEK KSN starts with "629949B100". The "FFFFFF0C" is a demo RKI-KEK KSN. Also, v1.01 firmware would use symmetric rev A for RKI and v1.10 would use symmetric rev B
. (TS-27607)
12. User Use DFEE27 value 01 to enable MSR-only mode (disable CT EMV) (refer to TS-28038)
13. Per Kenneth C, all our products support USB 2.0 only, so our standard cable adheres to USB 2.0 standard (TS-31464)
14. Generic USB-C to Micro-USB cables are being verified by the engineering team to work well with VP3300/VP8300 functionally (See TS-31464)
15. Per engineering, our Contact Kernel does not support the CVM Limit, therefore there is no tag to set this value (TS-29135 on 2/7/2023)
16. Per engineering, Tag 9F09 was set to “0096” which was specified by Amex at the time of our certification testing and customers can change the value if Amex now requires it to be a different value (TS-29135 on 2/7/2023)
17. VP3300 and VP8300 key injection (DKI) use the Vivo key injection protocol
18. VP3300's encryption algorithm can be changed between AES and TDES even with the key injected. However, the key variant cannot be changed (between DATA and PIN). Use C7-32-00 to switch to TDES or C7-32-01 to switch to AES and send C7-33 to verify the setting afterward (See TS-32434)
19. Tag DFEF46 can be used to define the additional TLVs desired in the CTLS transaction payload
20. The 04-0A and 04-09 reset commands won't affect the value set by the 01-05 command
.
21. Use the 01-14 command to turn on/off the Quickchip HID mode (which behaves the same as KBQC but in HID mode). This feature is only supported by the VP3300 USB (not the BT or AJ). And 01-01 cmd won't work with this mode being turned on
.
22. Tag DFEF58 can be used to store "User-Defined Data"
falsefalsefalsevp3300, internalfalsefalsedescendingvp3300usbfalsefalsefalsedescendingvp3300
|
