1. internal command which is not in the NEO II IDG
2. KPI Demo data key KSN starts with FF FF FF 02 00; the LCLKEK KSN starts with FF FF FF 14 00 and the pairing key KSN starts with FF FF FF 0A 00
3. NEO II products can hold multiple DEK while the Augusta can only have one (TS-17546)
4. If MSR quit working after the FW upgrading, send 04-21 with "06" to re-initialize the MSR key. This may happen to the very old version VP5300 per Kevin Vo
5. CTL2: Contact level 2
6. CRL: CAPK Revocation List
7. Tag DFEE23 encrypted MSR data
8. Get FW: 29-00
9. Set time of reset: 25-07
10. Reboot device: 77-05
11. Get group xx config: 03-06 with value: DFEE2D01xx
12. Set/config a tag: 04-00 CMD (e.g. 04 00 with value 9F530152 to set the 9F53 tag with value 52)
13. Set BT name & pswd: 77-81 with data as "ASCII of the name\00"+"6 bytes old pswd"+ "6 bytes new pswd", use 77-82 to retrieve the BT friendly name
14. CT LCD display: 61-01
15. CTLS Ping: 18-01
16. For NEO II, the DFEE2D group number tag must be the first tag in the Set Configurable AID: 04-02.  For NEO I, the group tag is  FFE4  
17. Toggle On/Off pass through 2C-01
18. In pass-through mode, if send Power On ICC, the seated switch notification won't work. after the Power Off ICC, it will work again (TS-20534)
19. VP5300 by default has both the V 1.10.037 and V1.20.038 (Kernal 2) loaded. Use the command 60-18, data = 01 to switch to the 1.20.038 kernel. 
20. Use the 2C-1B command to set the reader mode to ISO7816  (default is EMV)
21. To get tamper status, send 04-22 with data 02, response "01" indicates the unit has tampered
22. Send C7-3A to get DSR info, the response contains the 3 bytes blocks in . Check NEO II IDG for detail
23. Use C7-36 to enable data encryption
24. Use "Execute RKI" in uDemo to do the RKI once the SN is being registered in our PKI RKI server.  If the SN is not being registered correctly, uDemo will show: "RKI Error: Unknown Failure, Unrecognized device protocol". If RKI is done successfully, the result is "RKI Update Finished: Success"
25. The default MSR Encrypted output is different between the Spectrum Pro & VP5300 (per Kevin Vo). With the Spectrum Pro, it's the same enhanced encryption output as the SecureMag (not in TLV), but the VP5300 MSR Encrypted output is in the TLV format under the DFEE23 tag with the value to be the same encrypted data as the Spectrum Pro's
26. firmware page in CF https://idtechproducts.atlassian.net/wiki/display/NEOII/VP5300+Firmware+Release+Page
27. To avoid the reader's function from being impacted by the certificate expiration (on or after 8/9/22), the firmware needs to be upgraded to V1.01.022.0434.S or higher
28. VP5300 Low Power mode (F0-03) only works in RS232 with ADF disabled (TS-29991)
29. Before V1.00.057.0338, the FW naming was VP5300_v1.00.057.0338.S_Test to represent the demo version, the current naming rule was started from VP5300_v1.00.058.0338.T (TS-26409)
30. Tag DFEF7D can be used to control the number of chip attempts before falling back to MSR. By default, it is 3 with an acceptable range from 1 to 5
31. DFEE22 Byte 1 in terminal data can be adjusted to reduce the waiting time with cards prompt for user selection, the current default value is 0x32 or use the DF10 tag to set the default language in terminal data to skip the language selection prompt during CT EMV transaction(TS-31444)

32. When IDT_Device.getDeviceType() sometimes returns IDT_DEVICE_NEO2 and sometimes returns IDT_DEVICE_NONE (although the VP5300 credit card reader is connected), try the rescan of the USB bus by executing the IDTDevice.discoverDevice() (TS-33273)

33. DFEC33 tag defines MSR reading direction: 0: Read on insert and withdrawal  1: Read on withdrawal  and the default is 0 confirmed with Kenneth Chung on 11/9/2023
34. DFED46 defines whether Interac ATC will be checked or not. When not added in Config, it is equivalent to the DFED46 setting value 0 (disabled) and ATC will not be checked
35. VP5300 supports 8-digit IIN starting from firmware version 1.02.503.0495.T or later (TS-36068)

falsevp5300

falsefalsefalsedescendingvp5300