1. Manuals
  2. Brands
  3. Dot Origin Manuals
  4. Antenna
  5. VTAP 100
  6. Basic configuration manual

Dot Origin VTAP 100 Basic Configuration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Basic Configuration Guide
Firmware from v1.1.10.2
Revised July 2022 v2.4

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VTAP 100 and is the answer not in the manual?

Questions and answers

Summary of Contents for Dot Origin VTAP 100

  • Page 1 Basic Configuration Guide Firmware from v1.1.10.2 Revised July 2022 v2.4...
  • Page 2 No part of this Configuration Guide may be published or reproduced without the written permission of Dot Origin Ltd except for personal use. This Configuration Guide relates to correct use of the VTAP100 only. No liability can be accepted under any circumstances relating to the operation of the user’s own PC, network or infrastructure.

  • Page 3: Table Of Contents

    Contents 1  Using this guide 2  How VTAP100 works 2.1 Configure VTAP100 2.2 Default operation on factory settings 3  Start reading your own passes 3.1 Edit config.txt 3.2 Send pass data as keyboard emulation over USB 3.3 Extract only part of the pass data 3.4 Control LED and buzzer feedback 4  Read cards or tags 4.1 Extract only part of the card or tag data...

  • Page 4: Using This Guide

    1   Using this guide This guide is for first-time users of the VTAP100, and anyone using the VTAP100 with a direct USB connection to a PC. It will help you configure your VTAP100 for a simple application. Information about maintenance features includes how to update the firmware on your VTAP100 unit, when a new release is available.

  • Page 5: How Vtap100 Works

    2   How VTAP100 works Simply tap your smartphone against the VTAP100 antenna. Your mobile NFC pass will be read and data sent to the connected PC. Since the VTAP100 includes automatic pass selection, you do not need to open your phone and select the pass, the VTAP100 will do that for you.

  • Page 6: Configure Vtap100

    2.1 Configure VTAP100 This is an overview of the steps you need to take in configuring a VTAP100. Figure 2-2 VTAP100 configuration steps The VTAP100 is very flexible, in supporting different data formats for different media and different interfaces. So, we would recommend you follow an incremental approach to setting up and testing your settings.

  • Page 7: Default Operation On Factory Settings

    These steps demonstrate that the hardware can detect and interact with an OriginPass mobile NFC pass, which is ready to work with the default configuration of your VTAP100. 1. Obtain an OriginPass from Dot Origin by visiting https://originpass.com/VTAP/ and add it to your Google Pay or Apple Wallet.

  • Page 8: Start Reading Your Own Passes

    3   Start reading your own passes To read any mobile NFC pass, you will need to provide your pass reading parameters. This means a collector ID or merchant ID and any keys. These allow you to read and decrypt pass data that is held by your users, on their smartphones.
  • Page 9 Step 2: Declare Merchant ID(s)/Collector ID(s) in the config.txt file 1. Open the file config.txt in a text editor (such as Windows Notepad). It already contains parameters for accessing the demo passes, prefixed VAS1 and ST1, both relying on KeySlot 6. You can overwrite these, or keep them in addition to your own pass reading parameters.
  • Page 10 Note: If a VAS#KeySlot parameter is omitted, or set to 0, then all available keys will be compared with the 4 byte hash of the public key for the data, to choose the right key. If the data received by the VTAP100 cannot be decrypted, the Apple iphone will register a pass read, but the data will not be output.

  • Page 11: Edit Config.txt

    3.1 Edit config.txt config.txt is the main file controlling operation of the VTAP100 device. To change any operation: 1. Connect the VTAP100 to your PC, using a USB cable. 2. Browse to the VTAP100 mass storage drive. 3. Open the file config.txt file in a text editor (such as Windows Notepad). Note: If local security settings prevent or limit the use of removable storage devices, or the connection of additional keyboards, an administrator may need to alter those permissions.

  • Page 12: Send Pass Data As Keyboard Emulation Over Usb

    Changes to config.txt usually take effect as soon as the file is saved. (The only exception is when you enable or disable the virtual COM port. In this case you need to reboot the VTAP100 before it takes effect, see Send pass data over a virtual COM port.) Note: If you make changes to your config.txt file from which you cannot recover, copy the config.txt content from Appendix Default Config.txt file and paste it into the config.txt file on your VTAP100 unit.

  • Page 13: Extract Only Part Of The Pass Data

    3.3 Extract only part of the pass data By default the whole pass data payload will be sent, using KBPassMode=0, but you can choose to send only part of the pass data, by setting values in config.txt. Note: The examples in this section use the KBPass prefix on all of the parameters, to control the behaviour of mobile pass NFC data being sent as a keyboard emulation.
  • Page 14 Example: Changes to config.txt using ContentMode 1 and two levels of data separators to extract data !VTAPconfig              KBPassMode=1 KBPassSeparator=| KBPassSection=2 KBPassContentMode=1 KBPassContentSeparator=% KBPassContentSection=1 In this case there are separators to identify sections and content separators within the target section: Figure 3-3 Separator |, Section 2, Content Separator %, Section 1 BASIC CONFIGURATION GUIDE PAGE 11...
  • Page 15 Example: Changes to config.txt using WiegandPassBits for Wiegand data (on VTAP100-PACW only) to extract bit data in a standard format, such as 26bit H10301 !VTAPconfig              WiegandMode=1 WiegandPassMode=1 WiegandPassSeparator=| WiegandPassSection=2 WiegandPassBits=26 In this case the content expected from the pass is a hex number, which represents an H10301 26 bit card ID: an even parity bit (calculated over the 12 most significant bits), a facility code and then the card number, ending with an odd parity bit (calculated over the 12 least significant bits).

  • Page 16: Control Led And Buzzer Feedback

    3.4 Control LED and buzzer feedback The VTAP100 has two diagnostic LEDs, red and green, which provide a heartbeat on the board, for factory use only. There are also status LEDs, on the reverse side of the board, which can provide feedback to end users, through a window in the case. These can show any hex RGB colour.

  • Page 17: Read Cards Or Tags

    4   Read cards or tags VTAP100 is primarily designed to read mobile passes, not cards and tags. You can choose to allow VTAP100 to read particular NFC or MIFARE Classic card or tag types in addition to mobile passes, by making changes in config.txt. Example: Changes to config.txt to allow NFC or MIFARE Classic card or tag types to be read !VTAPconfig...

  • Page 18: Extract Only Part Of The Card Or Tag Data

    4.1 Extract only part of the card or tag data You can extract parts of the card or tag data, or choose to send UID, NFC data or block data, by setting values in config.txt. There are three types of data you might want to extract from a card or tag: UID - The unique identifier of the card/tag.
  • Page 19 To extract part of the block data you need NFCType=B or MIFAREClassic=B, then identify which data block to read, using settings with a TagRead prefix. The following example extracts data in this way: Example: Changes to config.txt to extract a fixed length of data from a particular start point !VTAPconfig  ...

  • Page 20: Connect To Other Systems

    5   Connect to other systems If you want to receive the pass data collected by the VTAP100 in other systems, you will need to enable a virtual COM port, or serial RS232 interface if your hardware permits. Note: The serial RS232 interface is an option on the VTAP100-OEM hardware only. The Wiegand interface is only available on the VTAP100-PACW model.

  • Page 21: Using Vtap100 With Read-A-Card Software

    Note: If your Read-a-Card software does not already have a PC-license, or an e-license from another connected reader, you will need to obtain a Read-a-Card e-license for your VTAP100. Contact Dot Origin about a Read-a-Card eLicense for your VTAP100 quoting the ATCA number, which you can copy from BOOT.TXT on your VTAP100.

  • Page 22: More Advanced Features

    Step 1: Configure your VTAP100 to behave as a virtual COM port by adding the following COM port configuration to config.txt. Example: Extra lines for Config.txt file to make VTAP100 behave as a virtual COM port ComPortEnable=1 ComPortMode=1 ComPortSource=81 ComPortPassMode=1 ComPortPassSeparator=| ComPortPassSection=2 Note: The last two lines of this example assume the pass format is one generated by Pronto, where sections are separated by '|' characters and the payload is in section 2.
  • Page 23 Transfer files in passive mode If you cannot access the VTAP100 as a mass storage device on your PC, you can use the Zmodem protocol to transfer files, such as a firmware update, key update or configuration file. By default the VTAP100 is always listening for Zmodem commands. You could use a free application such as TeraTerm: Simply choose to Transfer a file, select Zmodem, Send and choose the file to send.

  • Page 24: Maintenance Features

    6   Maintenance features This section deals with less frequent operations such as checking status, logs, updating firmware and resetting the device. 6.1 Check status in BOOT.TXT Inspecting BOOT.TXT will give you essential information about your VTAP100 set up, at time of last reboot, which might be helpful when troubleshooting.

  • Page 25: Update Firmware

    6.2 Update firmware To update the firmware of the VTAP100: 1. Copy the firmware image file (firmware.dat) to the VTAP100 mass storage device. 2. Reboot the device, either by briefly disconnecting power or using Reboot, remount, refresh commands. There will be a delay of a couple seconds when the VTAP100 boots up again and performs the update, then it will continue to operate as normal.

  • Page 26: Hardware Lock To Disable Usb Mass Storage Device

    Note: The lock.txt file content is never visible in the VTAP100 file system and the password is hashed and stored securely in the VTAP100 crypto device. BOOT.TXT tells you that the software is locked. When you need to remove the software lock: 1.
  • Page 27 Figure 6-2 Jumper positions on VTAP100 PCB v2 hardware Figure 6-3 Jumper positions on VTAP100 PCB v3a hardware Figure 6-4 Jumper positions on VTAP100 PCB v4a hardware BASIC CONFIGURATION GUIDE PAGE 24...

  • Page 28: Hardware Reset To Use Factory Firmware

    If your VTAP100 board has a daughter board on top, as is the case for a VTAP100-PACW, you will need to lift the daughter board off, to reach these jumpers. When you start the VTAP100, the presence of this jumper means the connected PC will not detect a USB mass storage device.
  • Page 29 Refresh will force the VTAP100 to re-read config.txt. This is needed if you have renamed a file to be config.txt, as renaming is not otherwise noticed. BASIC CONFIGURATION GUIDE PAGE 26...

  • Page 30: A  Default Config.txt File

    A   Default Config.txt file Copy and paste the text from the blue box to your Config.txt file to return to factory default configuration, for a VTAP100-USB-CC: !VTAPconfig   VAS1MerchantID=pass.com.pronto.originpass.demo VAS1KeySlot=6   ST1CollectorID=80644855 ST1KeySlot=6 ST1KeyVersion=1   NFCType2=1   KBLogMode=1 KBSource=81 KBDelayMS=2 KBPassMode=0                     ...
  • Page 31 Copy and paste the text from this box to your Config.txt file to return to factory default configuration, for a VTAP100-PACW-CC: !VTAPconfig   VAS1MerchantID=pass.com.pronto.originpass.demo VAS1KeySlot=6   ST1CollectorID=80644855 ST1KeySlot=6 ST1KeyVersion=1   NFCType2=U MIFAREClassic=U   WiegandMode=1 WiegandSource=81 WiegandPassMode=1 WiegandPassSeparator=| WiegandPassSection=2   LEDDefaultRGB=1EBBCF LEDSelect=1 PassBeep=50,50,2 TagBeep=100,100,1...

Table of Contents