Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 205 Next »


Target Project

VP3300 Bluetooth, 2017

<Legacy> BTPay - Mini, 2016

Inherited from UniPay III

  • (minus) No Audio Jack
  • (plus) Add Blue tooth Low Energy Module , SPS protocol type

Mobile App DL Link


TI - 80149207

RevisionDateDescriptionApproved by

Rev G

80149207-TI-Rev_G_VP3300BT_signed.pdf


80149207-TI-Rev G_Unsigned.docx


 

Rev G,

Update the path for the TQM log file.


 

Rev F,

ICC Test Card Replacement. (80005217-001 Rev. A)


 

Rev E,

Renew this Rev since the Arena BOM's Rev D being modified by

PJM Kenneth.


 

Rev E, Signed

 

  • 1.TQM Test Supported

1.a RFID Test; 1.b ICC Test

  • 2.QC mode – Test Result Summary Log Information
  • 3.Update ICC Test Card.


VP3300 Bluetooth (Legacy: BTPay-Mini) Firmware Web Page

F/W Release Page


TS Fixed JIRA

TE-246 - Getting issue details... STATUS



Jason Files

DatePart Number.Json

 

IDMR-BT93933P-C3

CFG-CLEAR01-01-0.json





DL Link

VersionDate

Comment


Note for Model Number Definition.

  1. The Model Number is accupied by “V” => New BT Chip Equipped Required, from Vendor “Avnet”, 2nd Source

  2.The MN has no following “V” => Legacy BT Chip, Enzytek, Native Source



Approved by Who
w/ FW Version (Web Link)


Part Number List Updated

V 2.03.005

  TE-1929 - Getting issue details... STATUS

-C01.zip


Shawn.Huang

See ReleaseNote.txt in detail.


V 2.03.004

  TE-1637 - Getting issue details... STATUS

-C01.zip


Shawn.Huang 

See ReleaseNote.txt in detail

1. Fixing bug of "Ignored_tlvs".


V 2.03.003

 

TE-1560

SWT-840


-C04.zip


Shawn.Huang 

See ReleaseNote.txt in detail

1. Fixing bug of "Ignored_tlvs".



Shawn.Huang 
Add "x_" to each folder of the PartNumbers have been OBS.



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>".



Shawn.Huang 

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


 

goofy.liu 

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)



 

goofy.liu 

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


 

goofy.liu 

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

Mindy Yang  
Test report



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>
Rx_OK:<0x0D><Friendly Name><0x0D>

Ex: <0x0D>Enzytek SPS_C<0x0D>

AS / CGet Friendly Name
02

Tx: AT+BLN=<Friendly Name><0x0D>

Ex: AT+BLN=IDTECH-BTPay Mini<0x0D>

Rx_OK: <0x0D>OK<0x0D>

AS / C

Set Friendly Name

(Production Mode ONLY in TS166)

(*02)

03

Tx: ATI4<0x0D>

Rx_OK: <0x0D><BLE Addr><0x0D>

Ex: 001C97121002<0x0D>

AS / CGet BLE Module Address
04

Tx: AT<0x0D>

Rx_OK: <0x0D>OK<0x0D>

AS / CClient / Server Alive Check
05

Tx: ATI0<0x0D>
Rx_OK: <0x0D>< information string ><0x0D>

Rx_OK_Example:
<0x0D>F-Serial_Port-v1.027_Golden<0x0D>

AS / CGet FW Version
06

Tx:^^^<0x0D>

Rx_OK: <0x0D>BLE DOWN<0x0D>

BC

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)



  • No labels