Target Project
VP3300 Bluetooth, 2017
<Legacy> BTPay - Mini, 2016
Inherited from UniPay III
No Audio Jack
Add Blue tooth Low Energy Module , SPS protocol type
Mobile App DL Link
- USDK Test Apps(Universal SDK)
- /wiki/spaces/SOF/pages/58426425(Shanghai)
TI - 80149207
| Revision | Date | Description | Approved by |
|---|---|---|---|
Rev E, renew80149207-TI-Rev E_Unsigned.docx |
| Rev E, Renew this Rev since the Arena BOM's Rev D being modified by PJM Kenneth. | |
| Rev E, Signed | ||
|
1.a RFID Test; 1.b ICC Test
| ||
Rev C |
| ||
Rev B |
| ||
Rev 50 |
| Initial version |
VP3300 Bluetooth (Legacy: BTPay-Mini) Firmware Web Page
F/W Release Page
TS Fixed JIRA
TE-246 - Getting issue details... STATUS
Jason Files
| Date | Part Number | .Json |
|---|---|---|
| IDMR-BT93933P-C3 | CFG-CLEAR01-01-0.json |
DL Link
| Version | Date | Comment Note for Model Number Definition.
2.The MN has no following “V” => Legacy BT Chip, Enzytek, Native Source | Approved by Who Part Number List Updated |
|---|---|---|---|
V 2.03.003 |
| TE-1560 SWT-840 | |
Shawn.Huang | |||
Ignored TLVs update: The CustCfg.xml file in each PartNumber add "<Ignored_tlvs set="0">0_9A_9F21_9F41_DFEE3A_9F1E</Ignored_tlvs>". | |||
See ReleaseNote.txt in detail 1. KSN Value Issue (SWT-826) 2. APDU command step update (SWT-833) 3. Summary log update (SWT-840) 4. Ignored TLVs update 5. TQM Log file path update | |||
V 2.03.002 | TE-1440 SWT-760 | ||
| 1.Model Numbers Updated -IDMR-BT93233APW2 been removed. +IDMR-BT93233APW2-L1, AES, MSR/MSD ON, EMV ON, No DEK, Json File : LatPay-VP3300-AUD-AU-EMV-010-BT.json Currency: AUD, 5F2A(0036), 9F1A(0036)
+IDMR-BT93233APW2-L2, AES, MSR/MSD ON, EMV ON, No DEK, Json File : LatPay-VP3300-GBP-GB-EMV-010-BT.json Currency: GBP, 5F2A(0826), 9F1A(0826)
| ||
| 1.Model Numbers Updated +IDMR-BT93233APW2，AES, MSR/MSD ON, EMV ON
+IDMR-BT93233APW2-L1-K348, AES, MSR/MSD ON, EMV ON, QC Mode Checking DEK (DKI by Secure Room HSM) by Pop-up Dialog box Json File : LatPay-VP3300-AUD-AU-EMV-010-BT.json Currency: AUD, 5F2A(0036), 9F1A(0036)
+IDMR-BT93233APW2-L2-K348, AES, MSR/MSD ON, EMV ON, QC Mode Checking DEK (DKI by Secure Room HSM) by Pop-up Dialog box Json File : LatPay-VP3300-GBP-GB-EMV-010-BT.json Currency: GBP, 5F2A(0826), 9F1A(0826) ~~~[For Developer Notes]~~~ 1.CustCfg.xml.encryption.dukpt_admin_key.@val definition updated. According to following points A~C >>> A. 0_PROD = Production Mode, Do nothing since Production DEK must be injected by HSM machine in Security Room. QC Mode, Must Check DEK existance & Display KSN Info. B. 1_DEMO = Production Mode, Do Demo DEK Injection. QC Mode, Must Check DEK existance & Display KSN Info. C. Alos see TestTM011_LoadKeyAdmin() Validation. <<< | ||
V 2.03.001 | TE-1217 SWT-575 | ||
| 1.Model Numbers Updated +IDMR-BT93133P2-F1: TDES, MSR/MSD ON, EMV ON; Json: CFG-FORTI01-01-0 +IDMR-BT93133PV2-F1: TDES, MSR/MSD ON, EMV ON; Json: CFG-FORTI01-01-0
2. Time Check Update, - QC Mode ONLY
- Ask User to allow the Time Diff Value more than tolerance. - Select 'Yes', 1 time only and keep ignoring the error, but have logged info. - Select 'No', 1 time only and acts as normal error process.
-Effected Model Numbers. ALL Model Numbers
3.[UI]Rename Form04 Window's Top Tool Bar label. Production --> Production; Sum Log QC-Mode --> QC-Mode; Sum Log
*Mouse RightButton-Clicking on this lable to open summary log file updated after all test items done.
4. QC Mode "FWInfo" Item Ignored spec multiple TLVs during tags verification. -9F41 Transaction Counter. -9F21 Transaction Time. -9A Transaction Date. -DFEE3A USBInterface HID/KB Indicator.
5.Enhanced ICC Test ICC Card - 80005221-001, current - 80005217-001, VP5300M , dual MSRs and ICC | ||
V 2.02.004 | TE-1161 Jira Ticket: TE-1113 | ||
|
- External Tool Updated: Updated IDT, Rollback to old one. Version : 1.0.1.30 (Oct 10 2021 Updated) --> 1.0.1.20
- Effected Model Number and Json File. IDMR-BT93933P-C3; CFG-CLEAR01-01-0_D2A8C3.json; with Arena BOM Frmw;K21;W/BL;VP3300 Bluetooth NEO v1.01.192
IDMR-BT93133PW2-F1; CFG-FORTI01-01-0.json; with Arena BOM Frmw;K21;W/BL;VP3300 Bluetooth NEO v1.10.031 | ||
|
- Frmw;K21;W/BL;VP3300 Bluetooth NEO v1.01.206
| ||
| 1. Model Number Updated List, Fixed Issue. IDMR-93133P2, Remove Json File from Production / QC Mode | ||
|
Note02: These Model Numbers are NEW Added !! ---------------- Error : Reader's BT Chip info can't meet current Model Number's criteria --------------- case 01 : using 1st kind BT reader to run TS w/ 2nd kind model number. case 02 : vice versa. | Git Hash = 626fb3216911ae0012f38d30a3a3f850fa3456b5 | |
V 2.02.003 | TE-1077 | ||
|
| ||
V 2.02.002 | TE-1007 | ||
| 1.BLE Test Wrong BT MAC Address Issue. - Fixed , Retrying 30-10 2+ times to get correct BT MAC Address. - Old & New BT Chips, both of them are *ALL* compatible in TS. - BT MAC Format List Old Prefix = 001C*, 001C97154B0A, Legacy V01, Enzytek, New Prefix = 60C0*, 60C0BF25C96C, V02, Avnet ******* Firmware Known Issue ********** 30-10 Get BT MAC Address sometimes will provide BT Chip FW Version or Friendly Name in Random. Workaround = TS sends 30-10 2+ times to get correct BT MAC by Vendor's MAC prefixing DUT Info: [FWInfo] VP3300 Bluetooth NEO v1.10.045 BL Version = VP3300 Bluetooth-BL-V3.10.003 [BLE Module Frmw Info] = IDTECH_Port-v0.005, BT Chip vendor: Avnet 2022 Jan 07 | ||
| |||
V 2.02.001 | SQA Test Req JIRA Tkt. TE-934 | ||
|
*Note: Please execute the TS166 from the server (ex: rd-fileserver) in the Test PC. Please click Yes/Execute Button to continue...
Executing UTS from the remote side (LAN server, ) example. The Windows will prompt the warning dialog box (the upper Fig.) before External App01 and App02 execution. | ||
V 2.01.004 | |||
| |||
|
Repeated [Backspace] key-down to delete input P/N text until empty at round 2+ will cause P/N auto-selection failed. | ||
|
P/N input typing reached full matched P/N, then it should automatically select right one in the list box. Ctrl+A --> Del --> No Auto Selection & ListBox Selection problem. | ||
|
Removal Card Waiting Period Fine-tune. | ||
|
| ||
V 2.01.003 | |||
| 1.RFID Test Updated , Type A+Type B : 0cm+4cm Tests Objective - TQM-Visa Request : 0cm+4cm && CL Type A+B , 4-step items required. Test Requested Ticket : TE-427 - Getting issue details... STATUS | ||
V 2.01.002 | |||
|
[+] IDMR-BT93133AP2D: AES, MSR/MSD ON, EMV ON Demo RKI-KEK, Demo DEK Requested e-mail: FW ECN-008643.msg
old: start QC mode --> FWInfo --> several test items passed --> RTC check --> certain (S/N check) --> Done. new: start QC mode --> FWInfo --> RTC Set/Check --> several test items passed --> RTC check --> certain (S/N check) --> Done. TE-410 - Getting issue details... STATUS | ||
|
[+] IDMR-BT93133P-U1: TDES, MSR/MSD ON, EMV ON [+] IDMR-BT93933P-C3, old: [-] Buzzer Test, new: [+] Buzzer Test, Added
Ex01: UI-LED Source = External --> Inform the operator at 1st time & pass LED test. Ex02: UI-Buzzer Source = Internal --> Normal Buzzer Test. 2.1 Note: Reconnecting the DUT will renew the UI Source Information. 2.2 Effected UI Test Item list Scope : LED/LCD/Buzzer Tips01 P/N Input : keyword typing to haste the P/N item seeking... JIRA-TE : TE-409 - Getting issue details... STATUS | ||
V 2.01.001 | |||
|
[+] IDMR-BT93133APW2: AES, MSR/MSD ON, EMV ON [+] IDMR-BT93133P2D: TDES, MSR/MSD ON, EMV ON; Demo RKI-KEK, Demo DEK | ||
| |||
|
IDMR-BT93933P-C3 : old: json file support. No Buzzer Test. new: No Buzzer Test. <noted> (a) No more supporting json file supports since VivoConfig Tool takes care the json file loading job. (b) No Beep function depending on Json file configuration. Operators could check Buzzer Beeps on [BLE Conn Test] Rebooting step. | ||
| 1.P/N List Updated IDMR-BT93933P-C3 : + json file support, No Buzzer Test. No Buzzer Test Since Json file configuration. If you still wanna check the buzzer status, you could verify it during Bluetooth Test Connection (Ping + 1 Beep). --- 1.ViVO Config Tool: ViVOConfig_Setup.msi 2.ViVO Config Tool - MFG Version : ViVOConfig_MFG.zip The MFG version needs the network UNC path access right "\\192.168.1.26\DocumentControl\ViVOconfig.MFG" account: its\servicecenter pwd: scenter 3. The new json file for IDMR-BT93933P-C3 : CFG-CLEAR01-01-0.json If update the ViVO Config Tool from time to time. | ||
V 2.00.009 | |||
|
Example: Summary-202061-IDVP-12P2_TM.log
| ||
V 2.00.008 | |||
| SHA-512: F5F4D335CD93B8642FBC87FB7A4E15EBD2C6F743108B5007AD19A9BBABB17EDEF091D7486FB93411B964AAC6731F393DB7B7124B70B60EF9D0E7C495CCF16194 | ||
|
1.a) Abbreviation: ICC Card - Type 01 = CLXSU004J4/T=0 ICC Card - Type 02 = CLXSU064KCS/T=0ED 1.b) Test Scenario: We have use both of Types (01+02) for ICC Test. Let's see as the following steps. old: Insert Type 02 --> Remove Type 02 --> Done. new: Insert Type 01 --> Remove Type 01 --> Insert Type 02 --> Remove Type 02 --> Done. | ||
|
(+)IDMR-BT93133P-E1: TDES, MSR ON, EMV ON
2.A RFID = 0cm+4cm <Type 01>
< Type 02 >
| ||
V 2.00.007 |
| N List Updated1.ID-80149008-001 : TDES, Encryption MSR/MSD ON; EMV ON [X] LEDs Test Item (Power,Tri-Color), Removed. <White housing> 2.IDMR-BT73100W: TDES;MSR ON;EMV OFF; NO MSR 3.IDMR-BT93133W 4.IDMR-BT93133PW: TDES, MSR ON, EMV ON 5.IDMR-BT93133NW: TDES, MSR OFF, EMV OFF 6.IDMR-BT93133APW: AES, MSR ON, EMV ON 7.IDMR-BT93133AW: AES, MSR ON, EMV OFF <Black Housing> 8.IDMR-BT93133P: TDES, MSR ON, EMV ON 9.IDMR-BT93133N: TDES, MSR OFF, EMV OFF 10.IDMR-BT93133AP: AES, MSR ON, EMV ON 11.IDMR-BT93133A: AES, MSR ON, EMV OFF 12.IDMR-BT93133: TDES;MSR ON, EMV OFF; 13.IDMR-BT93933P-C1: TDES, MSR ON, EMV ON 14.IDMR-BT93933P-C2: TDES, MSR ON, EMV ON 15.IDMR-BT93933P-C3: TDES, MSR ON, EMV ON 16.IDMR-BT93933P-C4: TDES, MSR ON, EMV ON | |
| @P/N Updated (+)IDMR-BT93933P-C2: TDES, MSR ON, EMV ON (+)IDMR-BT93933P-C3: TDES, MSR ON, EMV ON (+)IDMR-BT93933P-C4: TDES, MSR ON, EMV ON Note01 : No Any Change in Software Source Code. New P/Ns Inherited from ALL Settings of "IDMR-BT93933P-C1". | SHA-512: E147E02C4BCE6A817CC95BA434F7D334A647F24267D9CEA0F647DB978705C19FE438F8C1ABA144FC1B2813A2280553DACF5A19E0B4BF51F7400FB8517BD0B7EE(Double-Click to Select All) | |
|
| RE TS166BTPayMini VP3300-BLE V2.00.007-C01 Released.msg SHA-512:
| |
V 2.00.006 | |||
|
1.a QC Mode Friendly Name Setting Check Issues 1.b FW Info BLE FW Version Check Issues. | ||
|
Location : .\99_Output\VP3300BLE_SN_BLEAddr_Part Number_yyyy-mm-dd.txt 1.a Right-Click [BLE Test] to open the folder “99_Output” 1.b BLE Test passed à S/N Passed à TS generates (S/N,BLE Address) data in the text file. ex: ".\99_Output\VP3300BLE_SN_BLEAddr_IDMR-BT93133A_2018-11-15.txt" --<File Content>-- "123T456789,001C9714FD36," "123T456781,001C9714FD35," VP3300BLE_SN_BLEAddr_IDMR-BT93133A_2018-11-15.txt
| ||
V 2.00.005 | |||
|
Old: New: ID-80149008-001 Settings: TDES, Encryption MSR/MSD ON; EMV ON [X] LEDs Test Item (Power,Tri-Color), Removed. BLE Friendly Name : IDTECH-VP3300 | ||
V 2.00.004 | |||
|
IDMR-BT93133PW-U1 : TDES;MSR and EMV encrypt on, + Excluded LEDs Test (Power, Tri-Color) But it still performs RFID LEDs x 4 Test !! | ||
| |||
V 2.00.003 | |||
|
IDMR-BT93133PW-U1 : TDES;MSR and EMV encrypt on IDMR-BT73100W : TDES;MSR encrypt on and EMV encrypt off; no MSR | Request : TS146 TS166 TS new PN creation .msg | |
V 2.00.002 | |||
2017 Sept 13, goofy_liu V 2.00.002-C01 1.New P/N are added. White housing: IDMR-BT93133PW: TDES, MSR ON, EMV ON IDMR-BT93133NW: TDES, MSR OFF, EMV OFF IDMR-BT93133APW: AES, MSR ON, EMV ON IDMR-BT93133AW: AES, MSR ON, EMV OFF Black Housing: IDMR-BT93133P: TDES, MSR ON, EMV ON IDMR-BT93133N: TDES, MSR OFF, EMV OFF IDMR-BT93133AP: AES, MSR ON, EMV ON IDMR-BT93133A: AES, MSR ON, EMV OFF | 2017 Sept 14, Approved by Kate Hung | ||
V 2.00.001 | |||
2017 Aug 1, goofy_liu 1.Rename Product is a Major Change. TS Version V1.XX.XXX --> V2.XX.XXX | |||
V 1.01.007 | |||
2017 July 31, goofy_liu 1.Rename USB_HID_IDTW.dll to USB_HID_IDTW_32bit.dll 2.Append the last 5~10 chars to the friendly name for more precisely BLE reader identification. Ex: old friendly name = IDTECH-VP3300 new = IDTECH-VP3300-23468 where S/N = 728T123468, XML file's frdly name = IDTECH-VP3300 3.Rename Keyword "VP3300" --> "VP3300Bluetooth" as reader ID. | |||
V 1.01.006 | |||
2017 June 27, goofy_liu 1.Add P/N IDMR-BT93133. | |||
2017 June 22, goofy_liu 1.Add Retrying Process while getting BLE Friendly Info. | |||
V 1.01.006-C01 | 2017 June 22, goofy_liu 1.Rename TS Title : Old = BTPay-Mini New = VP3300 2.Rename default BLE Friendly Name. Old: "IDTECH-BTPay Mini" New: "VP3300". 3.Key Injection Tool - HW/FW Info Verification Keywords Changed. V 1.10.004 Released, File Name: AdminKey_Injection.exe 4.BLE Test Fixture COM Port Selection, default baudrate being changed. Old = 2400 New = 9600 | ||
V 1.01.005-C02, 2017 May 02 1.Add Retrying Mechanism while getting BLE Module Version. | |||
V 1.01.005-C01 | V 1.01.005-C01, 2017 May 02 1.Add delay time after rebooting DUT behavior in BLE Test. | ||
V 1.01.004-C01, 2017 April 24 1.Add BLE Module Frmw Version in FW Info Check Item. see Red Line ----[ 1st DUT Firmware Data ]---- P/N =IDMR-BT93133W =========================== [ProcessorType] = ARM Cortex-M4/ K21 Family =========================== [Hardware Info] = HW,VPBTPay Mini K21F Rev9 =========================== [FWInfo] = BTPAY MINI NEO v1.01.041 BTPAY_MINI-BL-V3.00.01 =========================== [BLE Module Frmw Info] = IDTECH_Port-v1.028 | |||
V 1.01.003-C01 | V 1.01.003-C01, 2017 Mar 23 1.[Eng Mode] Adjust UI, Cursor movement to button center in Std Form 2.[Eng Mode] Add BLE Test Items in a group page. for debugging. 3.BLE (Enzytek) Friendly Name Setting. Value = "IDTECH-BTPay Mini" 4.Blue tooth test Item - Improved, get BLE Address from Reader by NEO Command. | [FWInfo] = BTPAY MINI NEO v1.01.039 BTPAY_MINI-BL-V3.00.01 | |
V 1.01.002-C02 | 1.Add Bluetooth device scanning function for user selection. 2.<TODO> a) Get Bluetooth Address by issuing NEO Command b) Add supported config settings for Bluetooth broadcast naming ID "Enzytek..." to customized one (Ex: "IDTECH BTPay Mini"). | SW = BTPAY MINI NEO v1.01.037; BTPAY_MINI-BL-V3.00.01; SQA = | |
V 1.00.002-C01 | V 1.01.002-C01, 2017 Feb 20 1.Improved BLE Test. old = Using Enzytek Golden SPS PIO11 Pin to disconnect BLE new = Using Data Mode Cmd "^^^<CR>" to disconnect BLE <Info> Data Mode = BLE Connected Status AT Cmd Mode = BLE Disconnected Status | SW = BTPAY MINI NEO v1.01.037; BTPAY_MINI-BL-V3.00.01; SQA = | |
V 1.01.001-C03 | V 1.01.001-C03, 2017 Feb 10 1.Fixed Error Handler during Bluetooth communication Timeout case ; Cancel action case; | ||
V 1.01.001-C01 | V 1.01.001-C01, 2017 Feb 10 1.Blue tooth Test Item Update. Using Enzytek Golden SPS_C as Host's BLE Jig over RS232 Interface. 2.Display Encryption & DUKPT Info in QC Mode [FWInfo] Item This is request from Greg, Cypress Ex: [Encryption-DUKPT Keys Info] = Encryption-Algorithm: TDES Encryption - EMV: Disable Encryption - MSR: Enable Admin DUKPT Key : Valid MAC DUKPT Key : N/A Account DUKPT Key : Unused 3.Correct to one of P/N From old: IDMR-BT90133W new: IDMR-BT93133W | ||
HW Test, V 1.00.001-C04 | 2016 Dec 28
| ||
V 1.00.001-C03 | 2016 Dec 21 1.Modify BLE Test Information | ||
V 1.00.001-C02 | 1.Modify BLE Test Information old : UniPay III Demo new : UniPay III BLE SPS | ||
V1.00.001-C01Internal Test | 2016 Dec 20 1.Initial Version 2.P/N- IDMR-BT90133W | ||
V1.01.005-C99Internal Test | Internal Test ONLY |
Ref Doc / Materials
1.Blue tooth Test Topology
2.EnzyTek AT Commands for BLE Module (Server) & BLE Golden (Client)
Used AT Command Table, defined in EnzyTek SPS BLE Module User Guide V1.4.pdf
| # | AT Commands for Server / Client (*01) | Compatible Run Mode (*03) A.Command Mode (BLE Disconnected) B.Data Mode (BLE Connected) | Server(S) / Client(C) Supported ? | Comment |
|---|---|---|---|---|
| 01 | Tx: AT+BLN?<0x0D> Ex: <0x0D>Enzytek SPS_C<0x0D> | A | S / C | Get Friendly Name |
| 02 | Tx: AT+BLN=<Friendly Name><0x0D> Ex: AT+BLN=IDTECH-BTPay Mini<0x0D> Rx_OK: <0x0D>OK<0x0D> | A | S / C | Set Friendly Name (Production Mode ONLY in TS166) (*02) |
| 03 | Tx: ATI4<0x0D> Rx_OK: <0x0D><BLE Addr><0x0D> Ex: 001C97121002<0x0D> | A | S / C | Get BLE Module Address |
| 04 | Tx: AT<0x0D> Rx_OK: <0x0D>OK<0x0D> | A | S / C | Client / Server Alive Check |
| 05 | Tx: ATI0<0x0D> Rx_OK_Example: | A | S / C | Get FW Version |
| 06 | Tx:^^^<0x0D> Rx_OK: <0x0D>BLE DOWN<0x0D> | B | C | Disconnect BLE Communication in data mode. |
*= Note
*01 : Server = BLE Module; Client = BLE Golden (i.e. Test Jig/Fixture)
*02 : Set Friendly Name in Server Side (BLE Module inside reader) will cause Blue tooth protocol restart
since broadcasting message contains Friendly Name.
*03 : Check BLE Module LED Indicator blinking behavior to know Reader's Blue tooth Connection Status
Disconnected Status = Slow Blinking, long period (LED ON)
Connected Status = Fast Blinking, short period (LED ON)